VBoxManage showvminfo segfault in 6.0.x -> fixed in releases after 6.0.4
|Reported by:||gizero||Owned by:||pentagonik|
|Guest type:||Linux||Host type:||Linux|
After upgrading to 6.0, already existing VMs that used USB passthrough (at least one filter enabled) stopped being controllable by vagrant. After quick inspection I noticed this is not an issue with vagrant itself, but a consequence of it running
VBoxManage showvminfo behind the scenes for its own purposes.
Indeed the above command is segfault-ing systematically on my host. This happens after it prompts "Currently Attached USB Devices:". This seems consistent with the fact that I don't have any issue with VMs that are not configured for using USB passthrough. Adding the
--machinereadable option has no effect.
While this is a problem with tools relying on
VBoxManage showvminfo for their own VMs lifecycle management, on the hypervisor VirtualBox side of things the VMs are apparently starting correctly and the USB passthrough itself seems to be working if devices are connected after boot. Still
VBoxManage showvminfo is segfault-ing at every run.
Currently verified on an Ubuntu 16.04.5 host with latest updates. Same happens with latest VirtualBox 6.0.2.
Here is the segfault context I have collected so far.
VBoxManage: segfault at 0 ip 000000000045cf0d sp 00007ffe37e1e550 error 4 in VBoxManage[400000+10a000]
Things I tried already, with no noticeable result:
- upgraded to latest 6.0.2
- created fresh machines with different (recent) guest OSs and USB passthrough enabled (all fail)
- configured USB filters for a couple of different devices
Let me know if I can provide more context or how to proceed with further testing.
Change History (18)
comment:17 by , 4 years ago
|Status:||closed → reopened|
|Summary:||VBoxManage showvminfo segfault in 6.0.x → VBoxManage showvminfo segfault in 6.0.x -> fixed in releases after 6.0.4|