VirtualBox 3.0.6 sees invalid cd/dvd data after an eject / load on Solaris => Fixed in SVN

[Roger Fujii]

VirtualBox gets incorrect data from a CD. Running an xp VM on a Solaris snv_123 host. To duplicate, load a DVD and look in the VM. Now eject the DVD from the VM. Then load a different DVD and notice how the Volume name didn't change.

Looking through the source, it seems there are 2 issues. The first is that the Solaris drvHostBaseOpen uses different calls (relies on RTFileOpen) than the linux drvHostBaseOpen (which is based on open(2) ). Secondly (and more importantly), drvHostBaseReopen doesn't close the previous descriptors before opening the new one. This might cause some oddities (just a guess) since the open instance count never goes down to zero.

[Ramshankar Venkataraman]

Thank you for the report. This has been fixed in SVN.

[Mike Riley]

Sorry for my ignorance, but what does SVN stand for?

[Ramshankar Venkataraman]

SVN is Subversion - our source control/repository. Essentially what I mean is, it's fixed internally and should be available in the next release. I tested by changing physical DVDs from a VM and they work after the fix I made.

[Klaus Espenlaub]

Just FYI... the fix is in 3.0.8, and causes a total breakage of the host DVD support on Solaris 10. Will be fixed for 3.0.10.

[Mike Riley]

Just FYI back... I am using 3.0.8 on SXCE snv_123 and it does not even see an inserted CD now. Solaris sees the CD just fine though. If I change my settings for the CD/DVD drive to enable passthrough I get this error when I try and start up the VM:

Failed to start the virtual machine WindowsXP. Cannot open host device '/devices/pci@0,0/pci-ide@4/ide@0/sd@0,0:c,raw' for read/write access. Check the permissions of that device (VERR_ACCESS_DENIED). Unknown error creating VM (VERR_ACCESS_DENIED).

Details: Result Code: NS_ERROR_FAILURE (0x80004005) Component: Console Interface: IConsole {0a51994b-cbc6-4686-94eb-d4e4023280e2}

Disabling passthough allows, while leaving the drive enabled, it to come up - yet it does not see a disc inserted into the drive after it is up and running. So this fix seems to have made it even more broken. At least before you would see the first disc you inserted into the drive.