You are not logged in.

#1 2009-07-06 17:32:53

djg1971
Member
Registered: 2008-09-11
Posts: 185

kernel 2.26.30.1-1 and VirtualBox 3.0.0

Hopefully this is the right forum for this question:

After pacman -Su this morning, VirtualBox (recently upgraded to latest edition (3.0)) will no longer work.  Has anyone else observed this?

The kernel module compiles and loads, the startup gui launches, and the virtual machine appears to try and boot.  At that point windows declares that it has to check the disk, which it does, and then it proceeds assuming everything is fine only it isn't - machine never boots, just black screen and 100% cpu usage forever.  If you kill it and try again, it just does the same thing over and over.  It seems that you can boot into safe mode, though several things (screen size, etc.) don't work right, so it is not an acceptable workaround for the time being.

Just wondering if anyone else has seen this.  There are some posts (eg. on the fedora12 bleeding edge forum) which say that the latest linux kernel is not compatible with VirtualBox 3.0.0 anymore, but they are using 2.26.31 already.  Would be nice to know if I should wait for a VirtualBox update (i.e. enough people experience this that it will prompt a fix sometime soon) or look for a workaround, or just assume VB is hosed until things really sort themselves out.

thanks to anyone who can comment.

Offline

#2 2009-07-06 17:42:04

wonder
Developer
From: Bucharest, Romania
Registered: 2006-07-05
Posts: 5,941
Website

Re: kernel 2.26.30.1-1 and VirtualBox 3.0.0

yes. is a bug in virtualbox and guests with kernel 2.6.30
http://www.virtualbox.org/ticket/2149


Give what you have. To someone, it may be better than you dare to think.

Offline

#3 2009-07-07 20:14:17

hamelg
Member
From: France
Registered: 2008-06-19
Posts: 128

Re: kernel 2.26.30.1-1 and VirtualBox 3.0.0

Here, I don't have this bug, but another very annoying  :
http://www.virtualbox.org/ticket/4343

so, I downgraded to VB 2.2.4 and now all work fine with the latest kernel.

Offline

#4 2009-07-08 21:45:40

tkdfighter
Member
From: Switzerland
Registered: 2009-01-28
Posts: 126

Re: kernel 2.26.30.1-1 and VirtualBox 3.0.0

Hmm, just Su'd an hour ago, tried what the OP said. Windows 7 RC and XP boot just fine. I'm running Kernel 2.6.30.1 and Virtualbox 3.0.0.

Offline

#5 2009-07-08 21:59:55

jota
Member
Registered: 2009-06-10
Posts: 1

Re: kernel 2.26.30.1-1 and VirtualBox 3.0.0

Just updated 2.6.28 > Kernel 2.6.30.1 with VBox 2.2.4,this message error 0x80000003 software exception location 0x01850f0a2 pops up.
With kernel 2.6.28 all is well,haven't tried 2.6.29.

Windows XP Pro SP3 host
Arch Linux 2000.02 guest

00:17:06.545 PATM: patmR3RefreshPatch: succeeded to refresh patch at c0141a45
00:17:06.586 PATM: patmR3RefreshPatch: succeeded to refresh patch at c03d4170
00:17:06.615 PATM: Failed to refresh dirty patch at c0141690. Disabling it.
00:17:06.659 PATM: patmR3RefreshPatch: succeeded to refresh patch at c03d47a0
00:17:06.671 PATM: patmR3RefreshPatch: succeeded to refresh patch at c01084b0
00:17:06.760 PATM: Failed to refresh dirty patch at c0163ac0. Disabling it.
00:17:07.094 PIT: mode=0 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:17:08.460 PATM: Failed to refresh dirty patch at c01256e0. Disabling it.
00:17:09.150 PATM: Disable block at c04f154c - write c04f15da-c04f15de
00:17:09.195 PATM: Disable block at c050f0e4 - write c050f154-c050f158
00:17:16.284
00:17:16.285 !!Assertion Failed!!
00:17:16.285 Expression: pVM->patm.s.pGCStateHC->fPIF == 1
00:17:16.285 Location  : C:\vbox\branch\win-2.2\src\VBox\VMM\PATM\PATM.cpp(6137) PATMR3HandleTrap
00:17:16.285 Crash in patch code ff0c18ef (c0307aa8) esp=d5bc9d08
00:17:16.285 Patch state=4 flags=10c0081 fDirty=4
00:17:16.285 <NULL>

VirtualBox 3.0.2 did'nt fix this problem,hope it get fixed soon.

Latest 3.0.6 beta has fixed it.

Last edited by jota (2009-09-03 12:30:21)

Offline

#6 2009-07-08 22:17:50

tkdfighter
Member
From: Switzerland
Registered: 2009-01-28
Posts: 126

Re: kernel 2.26.30.1-1 and VirtualBox 3.0.0

You guys did do a vbox_build_module after updating, right?

Offline

Board footer

Powered by FluxBB