Opened 14 years ago
Closed 13 years ago
#8284 closed defect (fixed)
running tracepath inside VM crashes virtualbox
Reported by: | Sam Morris | Owned by: | |
---|---|---|---|
Component: | network/hostif | Version: | VirtualBox 4.0.0 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Windows |
Description
Running the 'tracepath' command from iputils 3:20100418-3 inside a VM running Debian 6.0 (linux 2.6.32) causes VirtualBox to instantly freeze, in such a severe manner that it is not even possible to kill it via the task manager. The host must be rebooted in order to recover.
Attachments (2)
Change History (12)
by , 14 years ago
Attachment: | wintermute.xml added |
---|
comment:1 by , 14 years ago
Component: | other → network/hostif |
---|
comment:3 by , 14 years ago
I can also confirm that this is present as a problem on Virtualbox 4.0.4 with a gentoo host and gentoo client.
comment:4 by , 13 years ago
I can confirm this bug on Gentoo Linux (host) running VirtualBox 4.0.8 r71778 with two Scientific Linux 6.0 (RHEL fork) guests tracepath-ing each other via an internal network using paravirtualized network devices.
comment:5 by , 13 years ago
Confirmed, at the end I was stuck with a zombie process consuming almost all CPU - had to force reboot using Sysrq since even the host wouldn't go down.
Virtualbox 4.1.2 64bit host, 32 bit guests, virtio_net. Using recent kernels and userland.
comment:6 by , 13 years ago
Can't reproduce. Since there are reports for various host OSes I assume this plays no role, and I made my test with Debian 5.0 as the host, and Debian 6.0 as the guest. Networking mode was "bridged", and I used a wired Gbit ethernet card. I could get paths with up to 21 hops, without any trouble. Tried 4.0.14 and latest svn sources.
comment:7 by , 13 years ago
I had the same problem with 4.0.12. Updated to 4.1.4 and the problem is gone. It looks like this bug can be closed as fixed.
comment:8 by , 13 years ago
Does (or was) it depend on attachment of device to wireless or ethernet one?
comment:10 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
VM configuration