Ticket #8973 (new defect)

Opened 3 years ago

Last modified 3 years ago

"VBoxManage modifyvm --name" fails to rename config file

Reported by: neuron Owned by:
Priority: major Component: other
Version: VirtualBox 4.0.8 Keywords:
Cc: Guest type: other
Host type: other


Machine exists and has correct config file

$ VBoxManage showvminfo appliance.2010.q3.1.0 | grep Config\ file
Config file:     /dir/user/test/appliance.2010.q3.1.0.vbox

$ VBoxManage modifyvm appliance.2010.q3.1.0 --name test

... no issue there

$  VBoxManage modifyvm appliance.2010.q3.1.0 --name test
VBoxManage: error: Could not find a registered machine named 'appliance.2010.q3.1.0'
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox, interface IVirtualBox, callee nsISupports
Context: "FindMachine(Bstr(a->argv[0]).raw(), machine.asOutParam())" at line 336 of file VBoxManageModifyVM.cpp

... The configuration file is set still to the same path:

$ cat $VBOX_USER_HOME/*xml | grep MachineEntry
      <MachineEntry uuid="{84e0c697-7a89-70c1-2dbb-76dd396a90e9}" src="/dir/user/test/appliance.2010.q3.1.0.vbox"/>

... But it was actually renamed:

$ ls /dir/user/test/*.vbox

Changing the $VBOX_USER_HOME/VirtualBox.xml so that it points to test.vbox fixes things.

It might be releated, I don't have my .VirtualBox in standard path, but I'm rather using


Thank you --


Change History

comment:1 Changed 3 years ago by neuron

One more comment, shortly after renaming, while VBoxSVC is still running, all seems to be good. But once VBoxSVC terminates and later is forced to re-read configuration, the problem appears.

comment:2 Changed 3 years ago by neuron

This is still true with VirtualBox 4.0.8 . It seems that the problem appears only when the machine config xml file has suffix *.xml . If it has suffix *.vobx , I haven't seen the problem yet. It appears randomly, I haven't found a way to reproduce the issue reliably...

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use