Changes between Initial Version and Version 2 of Ticket #14897
- Timestamp:
- Dec 7, 2015 3:24:05 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #14897
- Property Priority blocker → major
-
Ticket #14897 – Description
initial v2 3 3 When using VBoxManage.exe to import or list vms (possibly others), the following happens: 4 4 5 1)The item is reported to be imported successfully6 2)The .vbox file shows in \VirtualBox VMs\xx.vbox7 3)The new VM is NOT added to the GUI8 4)Typing5 1. The item is reported to be imported successfully 6 2. The .vbox file shows in \VirtualBox VMs\xx.vbox 7 3. The new VM is NOT added to the GUI 8 4. Typing 9 9 {{{ 10 10 vboxmanage.exe list vms 11 11 }}} 12 12 shows 0 vms 13 5)Trying to manage the VM using vboxmanage.exe fails since the VM isn't detected14 6)However, if I were to elevate my prompt and type13 5. Trying to manage the VM using vboxmanage.exe fails since the VM isn't detected 14 6. However, if I were to elevate my prompt and type 15 15 {{{ 16 16 vboxmanage list vms 17 17 }}} 18 18 , the vm shows up. 19 7)As a workaround, if I were to double click the \VirtualBox VMs\xx.vbox file, it would add it successfully to the GUI and19 7. As a workaround, if I were to double click the \VirtualBox VMs\xx.vbox file, it would add it successfully to the GUI and 20 20 {{{ 21 21 vboxmanage.exe list vms

