Windows 7 guest locks up using 100% cpu

[harry eaton]

Sometimes when I leave the system running overnight, in the morning, the guest OS (Windows 7) is unresponsive. The host shows VirtualBox consuming 100% of cpu. Choosing Machine->Reset and answering yes locks it up further (the host menu no longer functions after that) and still shows 100% cpu consumption.

I think this only (and always) happens when a USB device is plugged in to the guest, but I'm not 100% certain. It can certainly run all day long with the USB device without incident, as long as the system is actively used. The crash always occurs with the system idling.

At the original freeze, strace shows VirtualBox in a tight loop calling poll() followed by 3 read calls each of which returns EAGAIN.

After Machine->Reset, strace shows VirtualBox stuck in futex(), still using 100% cpu. Attaching with gdb (after the machine->reset) gives the following backtrace:

#0 0x00007fb79543785c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x00007fb79447564e in RTSemEventWait () from /usr/lib/virtualbox/VBoxRT.so #2 0x00007fb78ffe8912 in VMR3ReqWait () from /usr/lib/virtualbox/VBoxVMM.so #3 0x00007fb78ffe99bc in VMR3ReqCallVU () from /usr/lib/virtualbox/VBoxVMM.so #4 0x00007fb78ffe9f6f in VMR3ReqCallWait () from /usr/lib/virtualbox/VBoxVMM.so #5 0x00007fb78ffee07c in VMMR3EmtRendezvous () from /usr/lib/virtualbox/VBoxVMM.so ...

[harry eaton]

Vbox.log

[Frank Mehnert]

Please reopen if still relevant with VBox 4.3.2.