Discuss the 4.2.16 release

[michaln]

In the meantime, I'll spend my time enjoying other programs which ran fine on Windows 8 AND CONTINUE to run on 8.1.

If you insist on running unreleased software, it's not like you have any other choice. Enjoy

[gpaCook]

Bottom line - 4.2.16 is working OK now.

I reinstalled version 4.2.16, then the extension package. Things were already working, but I displayed session info to find additions were at 4.2.12.

When trying to install additions as non-root, ran into can't mount the additions iso file do I want to force. I went straight to login as root to install additions, got the same message, did the force, got the additions directory and ran the run file. The terminal window that it was running in disappeared prematurely, so I repeated the process, got successful mount and succesful run. Sessions info now shows additions = 4.2.16, and things work.

I did look up the log file to learn where it is and what it looks like before I lose this thread.

Thank you for the help,

[holger]

4.2.16 is the worst VirtualBox release ever...

Mouse and display integration does not work in FreeBSD 9.1. I had to downgrade to 4.2.14. This is the first time I have to revert VB, and I've been using VB for many years. The most unstable release ever.

Do not even try to install it, save your efforts for the next release (hopefully a better one).

[mpack]

Mouse and display integration does not work in FreeBSD 9.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]

Mouse and display integration does not work in FreeBSD 9.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?

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]

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?

[holger]

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?

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.

[Perryg]

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.

[holger]

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.

If I did not change the virtual machine... I just upgraded the VB... then where is the problem ?

Well, this is probably a pointless discussion. A more interesting thing is that I spent like 8 hours and drilled down to the problem. Somehow, my FreeBSD 9.1 VM does not like/recognize ACPI settings in the recent VB release. I had to trick it to use ACPI, like in the previous releases.

Now it works perfectly well - at least in terms of display/mouse.

[holger]

All my numerous Linuxes, the older and the new ones, 32-bits and 64-bits, run fine with 4.2.16. My older (pre-9.1) FreeBSDs also run fine.

Something is in between 4.2.16 and FreeBSD 9.1. I fixed the problem by enforcing ACPI in the FreeBSD, but it took significant time to discover the problem.

My main development machine is PC-BSD 9.1, so I was unpleasantly excited after the upgrade.

I wish FreeBSD would be supported, officially.

Thanks !
Oleg

[mpack]

Minor issue just exposed which the devs should probably know about: the VBoxUSBMon driver triggers a Driver Verifier fault on Windows hosts, as discussed in this thread. I imagine the fix is trivial - and of course the workaround is to disable driver verifier.

[VVD]

after upgrade to 4.2.16 it even could not connect to phpvirtualbox web management console (4.2.14 still work perfectly)

Work fine for me with phpvirtualbox 4.2-5/6/trunk.

on 4.2.14 it already could not self assign VNC port number instead of autoprobing the VNC port to 5900

Same with 4.2.16-ose - VNC port always 5900.

[VVD]

on 4.2.14 it already could not self assign VNC port number instead of autoprobing the VNC port to 5900

Same with 4.2.16-ose - VNC port always 5900.

Made ticket: https://www.virtualbox.org/ticket/12019
viewtopic.php?f=1&t=56311

[mhpjon]

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

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.
Also problems when I moved to 4.2.16 are that
- shared folders sometimes don't work automatically (from Windows Favorites)
- the fan runs a lot more and the laptop runs a lot hotter.

I'm going to revert VirtualBox on the host to 4.2.14 and see what happens.

Jon

[VVD]

on 4.2.14 it already could not self assign VNC port number instead of autoprobing the VNC port to 5900

Same with 4.2.16-ose - VNC port always 5900.

Made ticket: https://www.virtualbox.org/ticket/12019
viewtopic.php?f=1&t=56311

«- 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=327110