Ticket #6384 (closed defect: fixed)
Virtualbox OSE 3.1.4 runs in circles when guest Linux tries to attach to IPv6 socket before initialization completes
|Reported by:||Zugschlus||Owned by:|
this is an annoying issue of virtualbox 3.1.4 OSE when starting a guest Linux (Debian lenny and Debian sid) running any kernel later than 2.6.32, including 2.6.33. My host OS is Debian sid as well. I am not using the distribution kernels but am building from vanilla sources myself. The last guest kernel that doesn't show this issue is kernel 126.96.36.199.
When the ipv6 module is started, it takes a few seconds (much longer than on real hardware) until ipv6 autonegotiation begins. If any application tries to create an IPv6 socket before this autonegotiation, the virtualbox process begins to run around in circles, taking one available CPU, until the guest is aborted manually.
I may think that this is a kernel bug (which is reported to the LKML as http://marc.info/?l=linux-kernel&m=126313553029280&w=4 and http://bugzilla.kernel.org/show_bug.cgi?id=15042), but as I am only seeing this on virtual hosts, this may also be an issue of virtualbox not being able to cope with some new way of the Linux 2.6.32 kernel to do things.
Has anybody seen this behavior from virtualbox recently? What can I do to fix this?
I would also be interested in obtaining a sysrq-t dump of the running guest system, or some other way to get a memory image from the virtualbox system that I could feed to crash(8). If somebody could tell me how to do this with virtualbox, I might be able to further pursue this with the kernel people.
Any hints will be appreciated.
Vbox.log attached. All log entries in the first minute of the log are from the machine coming up, the entries from minute 02 are the system aborting.