VirtualBox

Changes between Initial Version and Version 2 of Ticket #14897


Ignore:
Timestamp:
Dec 7, 2015 3:24:05 PM (9 years ago)
Author:
Frank Mehnert
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #14897

    • Property Priority blockermajor
  • Ticket #14897 – Description

    initial v2  
    33When using VBoxManage.exe to import or list vms (possibly others), the following happens:
    44
    5 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
     5 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
    99{{{
    1010vboxmanage.exe list vms
    1111}}}
    1212 shows 0 vms
    13 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
     13 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
    1515{{{
    1616vboxmanage list vms
    1717}}}
    1818, 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 and
     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 and
    2020{{{
    2121vboxmanage.exe list vms

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