[Solved] VirtualBox PUEL Crashes on VM Launch

CaptainKirk · 2010-01-13 00:32:39

I have VirtualBox PUEL Version 3.1.2 r56127, the latest. I use PUEL because I need USB support.

Just today, however, if I start either of my Windows VMs (one Vista one XP) and it says "spawning process 0%" and then doesn't move beyond 0%.

I then run top in a shell and first it responds with one line "Killed" and then I run top again and the system freezes up--no mouse, no caps lock response on keyboard. So I reboot.

Basically that's it--doing other things while I have the "spawning process 0%" also will cause the freeze, but anyhow it seems that since the latest update, I now have this problem. My guess is that it has to do with the new kernel or kernel headers because I think that until today I haven't run VB since I got those.

This what I see in /var/log/messages.log

Jan 13 02:16:21 localhost dhcpcd: eth0: acknowledged 10.0.0.1 from 10.0.0.138
Jan 13 02:16:21 localhost dhcpcd: eth0: leased 10.0.0.1 for 86400 seconds
Jan 13 02:16:22 localhost kernel: oss_hdaudio 0000:00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Jan 13 02:16:22 localhost kernel: usbcore: registered new interface driver oss_usb
Jan 13 02:16:39 localhost kernel: fuse init (API version 7.13)
Jan 13 02:16:49 localhost kernel: NET: Registered protocol family 10
Jan 13 02:16:49 localhost kernel: lo: Disabled Privacy Extensions
Jan 13 02:18:04 localhost kernel: process `skype' is using obsolete setsockopt SO_BSDCOMPAT
Jan 13 02:18:30 localhost kernel: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
Jan 13 02:20:23 localhost kernel: Linux version 2.6.32-ARCH (tobias@T-POWA-LX) (gcc version 4.4.2 20091208 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Jan 7 22:19:56 UTC 2010
Jan 13 02:20:23 localhost kernel: KERNEL supported cpus:
Jan 13 02:20:23 localhost kernel: Intel GenuineIntel
Jan 13 02:20:23 localhost kernel: AMD AuthenticAMD
Jan 13 02:20:23 localhost kernel: NSC Geode by NSC
Jan 13 02:20:23 localhost kernel: Cyrix CyrixInstead
Jan 13 02:20:23 localhost kernel: Centaur CentaurHauls
Jan 13 02:20:23 localhost kernel: Transmeta GenuineTMx86
Jan 13 02:20:23 localhost kernel: Transmeta TransmetaCPU
Jan 13 02:20:23 localhost kernel: UMC UMC UMC UMC
Jan 13 02:20:23 localhost kernel: BIOS-provided physical RAM map:
Jan 13 02:20:23 localhost kernel: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)

I don't understand most of this but it would appear that the time span between 02:18:30 and 02:20:23 is the freeze and reboot sequence. Thus the last message is:

warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)

I see other issues with this message on Google, but for most folks it's just an error message, not a crash. So I'm not sure if that's really it.

But anyhow I can't run my VMs. I haven't yet tried to make a fresh one, but it seems that just initial boot of the VM doesn't start so a fresh machine probably won't help.

Last edited by CaptainKirk (2010-01-13 08:47:09)

wonder · 2010-01-13 00:36:56

rebuild the modules. it was a known problem with external modules and kernel 2.6.32.3

CaptainKirk · 2010-01-13 08:50:14

Yes, this is actually documented on the wiki: http://wiki.archlinux.org/index.php/Vir … drv_Module but I was not aware of it until your post. I rebuilt and now it works (after I rebooted my PC that is).

Thank you very much.

Arch Linux

#1 2010-01-13 00:32:39

[Solved] VirtualBox PUEL Crashes on VM Launch

#2 2010-01-13 00:36:56

Re: [Solved] VirtualBox PUEL Crashes on VM Launch

#3 2010-01-13 08:50:14

Re: [Solved] VirtualBox PUEL Crashes on VM Launch

Board footer