VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (127 - 129 of 16363)

Ticket Resolution Summary Owner Reporter
#18341 fixed VBoxManage showvminfo segfault in 6.0.x -> fixed in releases after 6.0.4 pentagonik gizero
Description

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[3754]: 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.

#18494 fixed VBoxManage modifyvm --recording ... : Crash, Documentation wrong -> fixed after 6.0.4 pentagonik HaukeH
Description

Hi,

I'm running VBox 6.0.4 on Ubuntu 18.04 amd64.

Recording video by using VBoxManage doesn't work for several reasons:

  1. The options shown in the help screen (VBoxManage --help) don't exist and aren't accepted by VBoxManage (eg. "--recording filename").
  2. By playing with spelling variants of the options I figured out, that eg. "--recordingfile" is accepted by VBoxManage.
  3. In my tests I used the options like in the following example:

VBoxManage modifyvm "myVM" --recording on --recordingfile="/tmp/test.webm" --recordingvideores="1024x756" --recordingvideorate=1024 --recordingvideofps=25

After modifying a (turned off) VM with these options the following happens:

  1. The VM will crash on next start attempt. This can only be fixed by turning off recording (VBoxManage modifyvm "myVM" --recording off).
  2. The CPU will jump to 100% for a few seconds.
  3. All VMs aren't available via the VBox GUI. Something like "No information available" is shown where the VM settings are shown usually.

Maybe there are combinations of options that enable recording, but I couldn't find any.

Thank you for your previous work on VirtualBox :-)

Hauke

#18658 duplicate Copy/Paste is broken for OSX guests after 6.0.4 pentagonik Socratis
Description

It's really simple, the title says it all. Tested on a 10.11.6 OSX host with two VMs, 10.13 and 10.9.

6.0.2, .4 GAs work fine, 6.0.6, .8 and later don't.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy