Discuss the 4.3.10 release

[bettor]

I can confirm that after upgrading this morning I also see this error and VMs won't start:

Code: Select all

0:02:15.573375 nspr-4   ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={480cf695-2d8d-4256-9c7c-cce4184fa048} aComponent={SessionMachine} aText={This machine does not have any snapshots}, preserve=false
00:02:16.656112 nspr-5   ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={480cf695-2d8d-4256-9c7c-cce4184fa048} aComponent={SessionMachine} aText={No storage device attached to device slot 1 on port 0 of controller 'IDE Controller'}, preserve=false
00:02:16.656506 nspr-4   ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={480cf695-2d8d-4256-9c7c-cce4184fa048} aComponent={SessionMachine} aText={No storage device attached to device slot 1 on port 0 of controller 'IDE Controller'}, preserve=false
00:02:16.657976 nspr-4   ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={480cf695-2d8d-4256-9c7c-cce4184fa048} aComponent={SessionMachine} aText={No storage device attached to device slot 1 on port 1 of controller 'IDE Controller'}, preserve=false
00:02:16.658343 nspr-5   ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={480cf695-2d8d-4256-9c7c-cce4184fa048} aComponent={SessionMachine} aText={No storage device attached to device slot 1 on port 1 of controller 'IDE Controller'}, preserve=false
00:02:16.659277 nspr-3   ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={480cf695-2d8d-4256-9c7c-cce4184fa048} aComponent={SessionMachine} aText={No storage device attached to device slot 0 on port 0 of controller 'SATA Controller'}, preserve=false
00:02:16.659650 nspr-2   ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={480cf695-2d8d-4256-9c7c-cce4184fa048} aComponent={SessionMachine} aText={No storage device attached to device slot 0 on port 0 of controller 'SATA Controller'}, preserve=false
00:02:16.674907 nspr-5   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:02:16.675290 nspr-3   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:02:16.688348 nspr-5   ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={480cf695-2d8d-4256-9c7c-cce4184fa048} aComponent={SessionMachine} aText={This machine does not have any snapshots}, preserve=false
00:02:28.411330 nspr-3   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:02:28.412844 nspr-4   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:02:28.532310 nspr-5   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:02:28.533387 nspr-3   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:02:31.874179 nspr-2   ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={480cf695-2d8d-4256-9c7c-cce4184fa048} aComponent={Machine} aText={Machine is not locked for session (session state: Unlocked)}, preserve=false
00:02:31.932448 nspr-4   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:02:31.933538 nspr-5   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:02:32.145133 nspr-5   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:02:32.145191 nspr-3   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:02:32.146491 nspr-3   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:02:32.157024 nspr-3   WARNING [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={93269330-48ca-4096-b4a2-1189df336267} aComponent={Host} aText={VirtualBox is not currently allowed to access USB devices.  You can change this by adding your user to the 'vboxusers' group.  Please see the user manual for a more detailed explanation}, preserve=true 
00:02:32.158108 nspr-4   ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={3295e6ce-b051-47b2-9514-2c588bfe7554} aComponent={ExtPackManager} aText={No extension pack by the name 'Oracle VM VirtualBox Extension Pack' was found}, preserve=false
00:02:32.179198 nspr-2   ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={480cf695-2d8d-4256-9c7c-cce4184fa048} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false

This is just part of the error. Hopefully I've not missed anything vital

That is on Ubuntu 12.04

[frank]

Actually we found the problem. Very nasty, will require to redo the 4.3.10 release :-/
But thank you for the report!

Is there any change in the source code to fix this problem? I see you have redone the binary release more than once but the source package stays the same. Unfortunately I have to compile from source because I need to apply a patch, otherwise VirtualBox does not work on my system.

Indeed, we should change the version numbering of the source code tarballs. For now they are just named .tar.bz2. Please make sure to download the current .tar.bz2 from the server, it contains the fix.

To verify that your VirtualBox-4.3.10.tar.bz2 tarball is the correct one, have a look at Config.kmk and verify that VBOX_SVN_REV_FALLBACK contains 93012.

[guanx]

Indeed, we should change the version numbering of the source code tarballs. For now they are just named .tar.bz2. Please make sure to download the current .tar.bz2 from the server, it contains the fix.

To verify that your VirtualBox-4.3.10.tar.bz2 tarball is the correct one, have a look at Config.kmk and verify that VBOX_SVN_REV_FALLBACK contains 93012.

Thank you, Frank! Now I see the update in the source tarball. Yesterday I downloaded too early when the new source had not been uploaded.

[Legorol]

Since the new r93012 revision, the UserManual.pdf download does not match the MD5/SHA256 checksums. It does not match the old r92957 checksums either.

[cerberos]

Actually we found the problem. Very nasty, will require to redo the 4.3.10 release :-/
But thank you for the report!

Since the new r93012 revision, the UserManual.pdf download does not match the MD5/SHA256 checksums. It does not match the old r92957 checksums either.

I think the checksums need to be updated.
http://download.virtualbox.org/virtualb ... SHA256SUMS is saying that the checksum for http://download.virtualbox.org/virtualb ... 4.3.10.iso is 247e15e9a205dcd4761f6cb547ceca2a61e8d6905c1930870939fd323f4cd1ae but the file I'm downloading has a checksum of 2b31a2b5327ed6babd510ff7edf7deb86c4286e6720357185049bbd1625ca934

I created a ticket before I found this post.

[robatino]

I verified that when downgrading from VirtualBox-4.3-4.3.10_93012_fedora18-1.x86_64 to VirtualBox-4.3-4.3.8_92456_fedora18-1.x86_64, or when updating back to 93012, the proper vboxhost modules are created on the host. Unfortunately, since VirtualBox-4.3-4.3.10_92957_fedora18-1.x86_64.rpm is no longer available, I'm unable to reproduce the bug that updating from 92957 to 93012 fails to create the vboxhost modules. Can someone who still has a copy make it available, or test it themselves?

P.S. When I updated from 92957 to 93012, the terminal output made it appear that the modules were in fact created. It was only by running "dkms status" that I could tell that they weren't.

[frank]

Since the new r93012 revision, the UserManual.pdf download does not match the MD5/SHA256 checksums. It does not match the old r92957 checksums either.

Please use the chechsums which are linked from the download site. The checksums in download.virtualbox.org/virtualbox were updated yesterday and as usual it takes ages until the download server actually delivers the new checksums.

[Legorol]

Since the new r93012 revision, the UserManual.pdf download does not match the MD5/SHA256 checksums. It does not match the old r92957 checksums either.

Please use the chechsums which are linked from the download site. The checksums in download.virtualbox.org/virtualbox were updated yesterday and as usual it takes ages until the download server actually delivers the new checksums.

I apologise but now I am confused about your answer. Which one are you referring to as the "download site", and which one is the "download server"?

I know about these two locations for obtaining the downloads:
https://www.virtualbox.org/wiki/Downloads
http://download.virtualbox.org/virtualbox/4.3.10/

I tried just now, and the MD5SUMS file is identical in both places. Both of the files seem to refer to the r93012 release, and contain the correct checksum for example for VirtualBox-4.3.10-93012-Win.exe (which is 1a87b7c6073b3db300e27947cf2b05a9). Both of them contain cd6d2ddac7f115717a3fe788000acbb8 as the checksum for UserManual.pdf. Is that the correct value?

[Legorol]

Ok, I see now what's happening with UserManual.pdf. There is nothing wrong with the checksum files. There was an intermediate version of UserManual.pdf briefly available for download earlier today. I now have the following three versions of it:

1) released with r92957, MD5 of 09e8885248080e9147ecd0cdd56c7fc4
2) released with r93012, MD5 of a0520fb09531058055c5cdda62c89394
3) re-released with r93012, MD5 of cd6d2ddac7f115717a3fe788000acbb8

I got all three of them from https://www.virtualbox.org/wiki/Downloads at different points in time.

The difference between them is in the text of the Change log, starting on page 231. First one contains "Version 4.3.10 (2014-03-25)". Second one contains "Version 4.3.10 (2014-03-26)". Third one also contains "Version 4.3.10 (2014-03-26)", but has an additional entry in the change list "Windows Additions/WDDM: fixed crashes with 2D video acceleration enabled (4.3.8 regression; bug #12745)" which the second one doesn't contain.

In conclusion, I was seeing issues with the checksums because there were in fact two versions released for r93012. The third version is the most current one, and the checksum files contain the correct checksum for it.

[frank]

In conclusion, I was seeing issues with the checksums because there were in fact two versions released for r93012. The third version is the most current one, and the checksum files contain the correct checksum for it.

Please be aware that the user manual does not have a revision in its file name. It is true that UserManual.pdf was updated twice but only the latest one was revision 93012. And I don't think that he user manual is important enough to satisfy complex hash checking. The user manual is part of every package and it's only placed in the download directory for convenience.

[cerberos]

Frank Mehnert, would you be able to update the checksums on this page http://download.virtualbox.org/virtualb ... SHA256SUMS, the guest additions one is wrong (maybe more as well)?

Thanks

[zk1234]

Well.. I wanted to post something, but (as a new member) I have to wait 24hours, so see you tomorrow

[frank]

Frank Mehnert, would you be able to update the checksums on this page http://download.virtualbox.org/virtualb ... SHA256SUMS, the guest additions one is wrong (maybe more as well)?

Already tried this yesterday but the download server needs some time to replace a file. Just checked and now the hashes are consistent.

[cerberos]

Already tried this yesterday but the download server needs some time to replace a file. Just checked and now the hashes are consistent.

The hashes are good now (the ones I'm using at least).

Thanks

[sej7278]

using the 93012 debian wheezy build and extensions, there's no longer a mount.vboxsf command so i can't mount shares under linux guests. tried reinstalling the additions twice.

ah seems to be a known issue, symlink is wrong.