virtualbox.org

I noticed on both Windows guests and Linux guests, when you eject the Guest Additions .iso from the guest, although in the guest it looks like it was ejected, after shutting down, the .iso is still attached. I tried it with Windows 7 & 8.1 guests and a few Linux guests.

edit: I believe it was doing this in 4.3.8 as well.

apparently VirtualBox was confused because I had downloaded a different version of the guest additions .iso. It also wouldn't forget it existed even when removing it from the media manager until I deleted the file.

loukingjr wrote:I noticed on both Windows guests and Linux guests, when you eject the Guest Additions .iso from the guest, although in the guest it looks like it was ejected, after shutting down, the .iso is still attached. I tried it with Windows 7 & 8.1 guests and a few Linux guests.

edit: I believe it was doing this in 4.3.8 as well.

i've been seeing that for quite a while - 4.3.6 or even earlier

sej7278 wrote:
i've been seeing that for quite a while - 4.3.6 or even earlier

I couldn't remember how far back it was happening. but, it does seem to be a problem only if you download the guest additions .iso as opposed to just mounting the one included in the package.

My host is Windows 7 64bit. After I upgraded to 4.3.10 yesterday, all my old guest machines is dead!! It says "Cannot access the kernel driver. Make sure the kernel module has been loaded successfully". Why I did the upgrade ...

Frank Mehnert wrote:

thump wrote: This is still broken. Running Ubuntu 12.04 LTS host. Installed "virtualbox-4.3_4.3.10-93012~Ubuntu~precise_amd64.deb" via apt, then upgraded guest additions on 2 guests (also 12.04) using "./VBoxLinuxAdditions.run --nox11". Now neither guest can boot. Guest console hangs on "EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro"....

This is a different problem. Please open a new ticket in the bug tracker.

Yup.. got it working now. Turns out it was the broken symlink bug in guest additions installer. Pretty nasty in it's own right given that it makes the guest VMs non-bootable. Rescue requires either offline VDI editing or a VDI restore from backup. Not sure how that one slipped through testing.

Ron Lee wrote:My host is Windows 7 64bit. After I upgraded to 4.3.10 yesterday, all my old guest machines is dead!! It says "Cannot access the kernel driver. Make sure the kernel module has been loaded successfully". Why I did the upgrade ...

Ron - are the guests Debian based (Deb, ubuntu, etc)?.. and did this happen right after installing Guest Additions?

Ron Lee wrote:My host is Windows 7 64bit. After I upgraded to 4.3.10 yesterday, all my old guest machines is dead!! It says "Cannot access the kernel driver. Make sure the kernel module has been loaded successfully". Why I did the upgrade ...

Did you reboot ? I had that message before a reboot, and yes it did say to reboot and I didn't. After a reboot it was fine (for me)

After I reboot, all the goodness and justice come back. I'm so sorry...
(My pc usually doesn't shutdown, after one night, I totally forgot this reboot thing.)

loukingjr wrote:

sej7278 wrote:
i've been seeing that for quite a while - 4.3.6 or even earlier

I couldn't remember how far back it was happening. but, it does seem to be a problem only if you download the guest additions .iso as opposed to just mounting the one included in the package.

no, i've never downloaded the iso, always use the one from the package via the "insert guest additions cd image" menu option.

I have two PC's running VirtualBox 4.3.10.93012 on Windows 7 with a Fedora 20 guest on each PC. On both setups VirtualBox crashes when I open a browser, either FireFox or SeaMonkey, in the guest. Is there any further information I can provide?