Discuss the 4.3.4 release

[frank]

Discuss the 4.3.4 release here.
You can download it from here.

[Etepetete]

The MD5 and SHA256 checksums do not seem to be correctly listed in the MD5SUMS and SHA256SUMS files for UserManual.pdf and VBoxGuestAdditions_4.3.4.iso.

I've downloaded both files twice at different times and checked ther checksums with two different programs and my results are:

UserManual.pdf
d37f0d386c5062b002d4599cb6b6f821
07b1957a175a81b8881d4a97662a07af09ce64144bdbddb2718af414e12441b9

VBoxGuestAdditions_4.3.4.iso
a566ae116f3275ea5cd6abee92691705
b01d41e484c9cb94d407c2c0767131aeb0a7cbe1a5540e71dbdc61dca349c50e

[frank]

Please download both files again. We replaced the files on the server within the first hours after uploading but before we published the 4.3.4 release. The servers usually take some time to refresh the files. I just downloaded the files and the checksums are correct.

[JonFleming]

Every time I open a VM now there's a banner at the top saying "The virtual machine reports that the guest OS supports mouse pointer integration...". I can close it but when I open the VM again it's back.

I don't need to be told this every time. How do I get rid of it?

[Perryg]

Click in the banner to open it. There is a checkbox lower left that will disable the warning.

[$roman]

Bug.
Just upgraded from version 2.something (probably VirtualBox-4.2.18-88781-Win) and now all of my VMs fail to load with error VT-x is disabled in BIOS.
(VERR_VMX_MSR_VMXON_DISABLED). Result code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

VM guest OSes: Ubuntu, Vyatta (router emulator), Windows 7, Windows Server 2008 R2

Host OS: Windows 7

I do not see anything in the BIOS configuration about VT-x. CPU: Intel Core i7-3770

[socratis]

I do not see anything in the BIOS configuration about VT-x. CPU: Intel Core i7-3770

My gut feeling is that you're either using XP mode or you have Hyper-V enabled.

[mpack]

Bug.
Just upgraded from version 2.something (probably VirtualBox-4.2.18-88781-Win) and now all of my VMs fail to load with error VT-x is disabled in BIOS.
(VERR_VMX_MSR_VMXON_DISABLED). Result code: E_FAIL (0x80004005)

This sounds like the same issue that's existed in all previous 4.3.x releases (see earlier "discuss release" topics), and actually the bug is in 4.2.x and earlier, not in 4.3.x.

The problem is that when you installed VMs to begin with, the template had VT-x enabled by default, but grayed out since it wasn't available. It's now considered an error for your VM recipe to ask for VT-x on hosts which don't support VT-x. You need to turn it off. This mainly seems to be apply to XP guests, though you haven't said which of your guests is affected.

Unfortunately, all of my PCs support VT-x so I can't test this suggestion: if you find that the VT-x checkbox is still grayed out then you can turn it off using VBoxManage :-

Code: Select all

VBoxManage modifyvm <vmname|UUID> --longmode off

[P0rridge]

I always take the latest release updates, which last happened the 30th Nov.

Yesterday I tried to access the tomcat running inside my Ubuntu client in my usual way - but got "no response" message.

So I looked at everything I could think of, which all looked fine:
- correct IP address in the Preferences->Network->Host only Networks-> Edit host only network
- tomcat up and running inside Ubuntu
- ping Ubuntu from Windows

So I reverted back to VB 4.3.2 and I had my life back again.

I think there is something wrong with the latest release.

The client is Windows 64bit, all patches applied
The client is Ubuntu, whatever the prior release is, with all patches applied.

[jimpoison]

i still have the same problem with 4.3.4 that i had with all 4.3.x versions before:
i can't check for updates.
an error message appears that says "the network operation failed with the following error: ssl authentication failed".
my host system is windows 7 ultimate 64bit.

i tried to reproduce the error on another computer and so i installed virtualbox 4.3.4 on my netbook with windows 7 starter 32bit, but there the update check works without problems.

could it be that the error has something to do with 64bit windows?

[DavidN]

Upgrading to 4.3.4 broke my Windows Server 2008 R2 guest. It was working under 4.3.2 and previous.

The guest reboots itself shortly after login, before the desktop is displayed. If booted into safe mode, the guest blue screens with 0x0000001E itself before completing the loading of drivers. Is this a known issue?

[APC]

I have had exactly the same problem as P0rridge and $roman. I upgraded from 4.3.2 to 4.3.4 and now I I try to open my VM I get VERR_VMX_MSR_VMXON_DISBABLED.

I have reverted to 4.3.2 which has fixed the issue. So clearly it's a problem with the new version.

Cheers, APC