Opened 11 years ago
Last modified 11 years ago
#11310 closed defect
VBoxManage does not see VMs — at Initial Version
| Reported by: | spectroman | Owned by: | |
|---|---|---|---|
| Component: | VM control | Version: | VirtualBox 4.2.4 |
| Keywords: | VBoxManage list uuid vmname | Cc: | |
| Guest type: | Linux | Host type: | Linux |
Description
Using the latest Linux 4.2.4 r81684, I was trying to use:
root@apophis:~# VBoxManage bandwidthctl "dc8af638-248c-4b2b-806a-40558e017114" set Limit --limit 1G VBoxManage: error: Could not find a registered machine with UUID {dc8af638-248c-4b2b-806a-40558e017114} VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox, interface IVirtualBox, callee nsISupports VBoxManage: error: Context: "FindMachine(Bstr(a->argv[0]).raw(), machine.asOutParam())" at line 309 of file VBoxManageBandwidthControl.cpp
While I can see:
root@apophis:~# ps aux | grep -i virtualbox 1000 11116 0.2 0.0 9512 4176 ? S 09:35 0:18 /opt/VirtualBox/VBoxXPCOMIPCD 1000 11121 0.2 0.0 24304 12268 ? Sl 09:35 0:18 /opt/VirtualBox/VBoxSVC --auto-shutdown 1000 12571 0.7 0.4 123788 59336 ? Sl 10:39 0:30 /opt/VirtualBox/VirtualBox 1000 14636 65.0 6.0 341631068 746532 ? SLl 10:40 43:01 /opt/VirtualBox/VirtualBox --comment XO3b --startvm dc8af638-248c-4b2b-806a-40558e017114 --no-startvm-errormsgbox
If I use the name "XO3b" I get the same result.
Then I realized that "VBoxManage list vms" or anything that would consult or use a VMname name or UUID does not work.
As I already searched in the forums and here, I could only find a similar problem with no apparent solution.
So I can only see this as a bug. Let me know if I am wrong.
