Bug 1336

Additional info
The same Linux Guest worked with 'Oracle VirtualBOX' for Fedora 13 x86_64 as host.

Hi all,

Same here, I updated from VirtualBox OSE 3.1.8-2.fc13 (x86_64) to VirtualBox-OSE-3.2.6-2.fc13.x86_64 (Fedora 13 x86_64 host, up to date) and :
- all my x86_64 guests don't work anymore, even after reboots.

I checked the configuration of the guests: it's OK, plus I didn't change anything in the guests configuration before/during/after the update.

I tried with several LiveCDs and installed distros :
- Fedora 12 i386 netinstall : OK
- Fedora 12 x86_64 netinstall: FAILED
- Fedora-13-i686-Live-LXDE : OK
- Fedora-13-x86_64-Live-LXDE: FAILED
- Ubuntu i686 install : OK
- Ubuntu x86_64 install: FAILED
- Existing F13 i386 (installed before update): OK
- Existing F13 x86_64 (installed before update): FAILED
- geexbox-2.0-alpha2-en.i386.eglibc : OK
- geexbox-2.0-alpha2-en.x86_64.eglibc: FAILED

So it seems to be something with 64bits support (for me at least).

I removed VirtualBox OSE (all including kmod-Virtualbox*) then installed VirtualBox from its website (OracleVM) : all is working well.

I removed VirtualBox (the OracleVM version) then reinstalled VirtualBox OSE : none of the 64bits guest are booting, but no prob. with 32bits guests.

the boot process of 64bits guest with VirtualBox OSE goes like this:
- VBox starting screen "F12 to select boot device"
- Grub displays the menu, I can change the settings for any of the menu items,
- I choose a boot menu-item and tells grub to boot ("Enter" or "b" keys)
- the screen goes black, with an unblinking cursor on the left up corner,
- nothing else happens, one of my CPU core is 50% used by VBox process until I close the guest.

Bye for now.

Changed severity to "Major" as there is a loss of functionality...

Well in fact for me it's unusable as I need 64bits guests in my 64bits host: I had to switch back to OracleVM VirtualBox.

Also changed Priority to P3 as for me it's unusable.

++

I can confirm it.


Quick hotfix (for the record):

rpm -ivh http://download.virtualbox.org/virtualbox/3.2.8/VirtualBox-3.2-3.2.8_64453_fedora13-1.x86_64.rpm
OR
rpm -ivh http://download.virtualbox.org/virtualbox/3.2.8/VirtualBox-3.2-3.2.8_64453_fedora13-1.i686.rpm

(In reply to comment #4)
> I can confirm it.
> 
> 
> Quick hotfix (for the record):
> 
> rpm -ivh
> http://download.virtualbox.org/virtualbox/3.2.8/VirtualBox-3.2-3.2.8_64453_fedora13-1.x86_64.rpm
> OR
> rpm -ivh
> http://download.virtualbox.org/virtualbox/3.2.8/VirtualBox-3.2-3.2.8_64453_fedora13-1.i686.rpm
> 

file /usr/bin/VBox from install of VirtualBox-3.2-3.2.8_64453_fedora13-1.x86_64 conflicts with file from package VirtualBox-OSE-3.2.6-2.fc13.x86_64

(In reply to comment #5)
> (In reply to comment #4)
> > I can confirm it.
> > 
> > 
> > Quick hotfix (for the record):
> > 
> > rpm -ivh
> > http://download.virtualbox.org/virtualbox/3.2.8/VirtualBox-3.2-3.2.8_64453_fedora13-1.x86_64.rpm
> > OR
> > rpm -ivh
> > http://download.virtualbox.org/virtualbox/3.2.8/VirtualBox-3.2-3.2.8_64453_fedora13-1.i686.rpm
> > 
> 
> file /usr/bin/VBox from install of VirtualBox-3.2-3.2.8_64453_fedora13-1.x86_64
> conflicts with file from package VirtualBox-OSE-3.2.6-2.fc13.x86_64
> 

ah, sorry it works but you just see that error message when installing the rpm.

Ok, I update this bug report:

tested today with:

kernel-2.6.34.6-47.fc13.x86_64
kmod-VirtualBox-OSE-3.2.6-1.fc13.5.x86_64
VirtualBox-OSE-3.2.6-2.fc13.x86_64
kmod-VirtualBox-OSE-2.6.34.6-47.fc13.x86_64-3.2.6-1.fc13.5.x86_64


So it seems that the kernel module version is different from the VirtualBox version:
3.2.6-2 != 3.2.6-1


Maybe that's why VirtualBox won't start my 64bits guests ?

Anyway, the bug is still there.

And the use of the quick fix (installing proprietary and non-commercial Oracle VM) is still necessary.

Bye for now

This problem is pretty much serious.
It would be fine to schedule an update to 3.2.8.

I expect the problem to be fixed in current release.
But I won't test because I'm using the Oracle version since lack of maintainer.