VirtualBox

Opened 9 years ago

Last modified 9 years ago

#14897 new defect

Windows 10 handles VBoxManage.exe incorrectly when importing and listing

Reported by: dylanh724 Owned by:
Component: other Version: VirtualBox 5.0.10
Keywords: Cc:
Guest type: other Host type: other

Description (last modified by Frank Mehnert)

I was able to reproduce this with 2 PC's, both Windows 10, trying both an older version (4.3.20) and latest version (5.0.10):

When using VBoxManage.exe to import or list vms (possibly others), the following happens:

  1. The item is reported to be imported successfully
  2. The .vbox file shows in \VirtualBox VMs\xx.vbox
  3. The new VM is NOT added to the GUI
  4. Typing
    vboxmanage.exe list vms
    
    shows 0 vms
  5. Trying to manage the VM using vboxmanage.exe fails since the VM isn't detected
  6. However, if I were to elevate my prompt and type
    vboxmanage list vms
    

, the vm shows up.

  1. As a workaround, if I were to double click the \VirtualBox VMs\xx.vbox file, it would add it successfully to the GUI and
    vboxmanage.exe list vms
    
    would then list them successfully in non-elevated prompt.

This blocker bug breaks all batch files that use vboxmanage to import a VM and configure it. The only workaround is to launch the .vbox file directly, but that will launch the GUI and is very unprofessional when using scripting.

Change History (6)

comment:1 by dylanh724, 9 years ago

To follow up, this is pretty much with all commands with vboxmanage -- starting it won't work either, even though it successfully says it started.

This is REALLY bad ... I'll start it, say it's started, and doesn't show in GUI and nothing in the BG

comment:2 by Frank Mehnert, 9 years ago

Description: modified (diff)
priority: blockermajor

comment:3 by Frank Mehnert, 9 years ago

Which Windows 10 version are you using and how did you import the VM?

I just did the following:

  1. Windows 10 / build 10585, VirtualBox 5.0.10
  2. Started the VM selector, went to File / Import Appliance, selected the VM to import (name foo1.ova)
  3. After importing, the VM was successfully listed
  4. Going to cmd.exe and did \Program files\Oracle\VirtualBox\VBoxManage list vms shows all VMs I have including the VM I just imported.

So I wonder what's different in your setup.

in reply to:  3 comment:4 by dylanh724, 9 years ago

Replying to frank:

Which Windows 10 version are you using and how did you import the VM?

I just did the following:

  1. Windows 10 / build 10585, VirtualBox 5.0.10
  2. Started the VM selector, went to File / Import Appliance, selected the VM to import (name foo1.ova)
  3. After importing, the VM was successfully listed
  4. Going to cmd.exe and did \Program files\Oracle\VirtualBox\VBoxManage list vms shows all VMs I have including the VM I just imported.

So I wonder what's different in your setup.

Like I mentioned in the OP, you need to use vboxmanage (their CLI tool), not the GUI. The GUI works fine, but this is a blocker (100% "blocker", not a "major bug") for any Windows 10 user solely using scripting for VirtualBox use (for example, use with headless VMs). Do the exact same steps you just did, only via the CLI "vboxmanage.exe", and that is how I reproduced this on multiple computers.

Related: https://www.reddit.com/r/virtualbox/comments/3vr7me/win10_vboxmanageexe_does_not_work_50_does_not/

Version 0, edited 9 years ago by dylanh724 (next)

comment:5 by Frank Mehnert, 9 years ago

First, I will not discuss the priority of this ticket. There is an alternative solution (use the GUI), therefore the priority is not higher than major. Second, I cannot reproduce your problem on my Windows 10 / 10585 box. I did exactly what you described. I import a VM with VBoxManage import foo1.ova and a VBoxManage list vms shows the VM which I just imported (foo1). And I'm also able to start the VM with VBoxManage startvm foo1.

Do you have some VBox-specific environment variables set in your cmd.exe windows and/or globally, for example VBOX_USER_HOME?

comment:6 by Klaus Espenlaub, 9 years ago

Also, are you trying to use VirtualBox simultaneously as admin and non-admin role by the same user? Or do you use it over a RDP session to the Windows Terminal Service and on the console concurrently, again by one user?

Note: See TracTickets for help on using tickets.

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