End user forums for VirtualBox
https://forums.virtualbox.org/
If you insist on running unreleased software, it's not like you have any other choice. EnjoyTimInSacto wrote:In the meantime, I'll spend my time enjoying other programs which ran fine on Windows 8 AND CONTINUE to run on 8.1.
I'm not a FreeBSD user of any description, but the manual says that GAs are not available for FreeBSD guests - which of course would mean no mouse integration (not sure what "display integration" means). Is the manual incorrect?holger wrote:Mouse and display integration does not work in FreeBSD 9.1
Yes, it was working fine up until 4.2.16, with compiled guest additions. Now nothing helps. Older or newer guest additions do not work.mpack wrote:I'm not a FreeBSD user of any description, but the manual says that GAs are not available for FreeBSD guests - which of course would mean no mouse integration (not sure what "display integration" means). Is the manual incorrect?holger wrote:Mouse and display integration does not work in FreeBSD 9.1
It is perfectly correct. Something (totally reasonable) was working before. Now it is not working. So the statement that "this release is worse then the previous releases" is totally correct - unless you want to go into brain tricks and unnecessary mental exercises.mpack wrote:But it remains a documented fact that FreeBSD is not a supported guest right? Therefore it is incorrect to complain that it isn't supported?
If I did not change the virtual machine... I just upgraded the VB... then where is the problem ?Perryg wrote:No brain tricks and unnecessary mental exercises. FreeBSD ports their own version of the guest additions. You need to ask the FreeBSD people to fix what is causing your issues.
Work fine for me with phpvirtualbox 4.2-5/6/trunk.Paul-LKW wrote:after upgrade to 4.2.16 it even could not connect to phpvirtualbox web management console (4.2.14 still work perfectly)
Same with 4.2.16-ose - VNC port always 5900.Paul-LKW wrote:on 4.2.14 it already could not self assign VNC port number instead of autoprobing the VNC port to 5900
Made ticket: https://www.virtualbox.org/ticket/12019VVD wrote:Same with 4.2.16-ose - VNC port always 5900.Paul-LKW wrote:on 4.2.14 it already could not self assign VNC port number instead of autoprobing the VNC port to 5900
I see something similar. This is with Windows 7 Enterprise (from a raw filesystem) as the Guest on Ubuntu. It doesn't matter what size the window is on Ubuntu, the Windows Desktop is the same size with either scroll bars or blank grey areas around the Desktop.gpaCook wrote:I didn't see any existing topic addressing this specifically, so:
vbox on OSX Mountain Lion, Ubuntu Studio guest.
Everything fine on 4.2.12, 4.2.14. I installed 4.2.16 and experienced the following:
- Guest window would resize in scale or non-scale as before, but contents remained original size (Ubuntu screen stayed small, tho guest screen would stretch).
- Cursor behavior was incorrect. Cursor had to be clicked to appear when moving between guest and host, regardless of the mouse integration mode. And cursor position did not correspond between the two.
I did install guest additions and extensions.
I went back to 4.2.14, and things are good (I notice my guest additions are still 4.2.16, but things still work fine).
Not sure if bug or user error, but wanted to share asap incase others encounter, and if solved.
Thanks,
gpaCook
Posts: 1
Joined: 7. Jul 2013, 16:56
«- Revert VNC IPv6 patch because it causes an incompatibility. Per default the VNC ports are stored in "TCP/Ports" but with that change "VNCAddress4", "VNCPort4", "VNCAddress6" and "VNCPort6" are used which breaks phpvirtualbox and also confused VBoxManage/VBoxHeadless.» © http://svnweb.freebsd.org/ports?view=re ... ion=327110VVD wrote:Made ticket: https://www.virtualbox.org/ticket/12019VVD wrote:Same with 4.2.16-ose - VNC port always 5900.Paul-LKW wrote:on 4.2.14 it already could not self assign VNC port number instead of autoprobing the VNC port to 5900
viewtopic.php?f=1&t=56311