Opened 14 years ago
Closed 13 years ago
#5558 closed defect (fixed)
Error while trying to registervm in vboxmanage.
Reported by: | Cristobal Escamilla | Owned by: | |
---|---|---|---|
Component: | VM control | Version: | VirtualBox 3.0.12 |
Keywords: | vboximage registervm | Cc: | |
Guest type: | Linux | Host type: | Windows |
Description
I read all of those http://www.virtualbox.org/search?q=vboxmanage+registervm&noquickjump=1&ticket=on none of them apply.
I'm trying to run a headless vm, so I'm using vboxheadless.exe but it can't find the vm as it says "Invalid machine name!", no wonder, the service is running as a different user.
Then I told the service to also run '"C:\Program Files\Sun\VirtualBox\VBoxManage.exe" registervm C:\Ubuntu.xml >> vbox.log' and I got this reply: VirtualBox Command Line Management Interface Version 3.0.12 (C) 2005-2009 Sun Microsystems, Inc. All rights reserved.
ERROR: Assertion failed at 'C:\vbox\branch\win-3.0\src\VBox\Main\MachineImpl.cpp' (5048) in Machine::loadSettings. Unexpected exception 'class xml::EInvalidArg' (In 'xml::File::File', 'C:\vbox\branch\win-3.0\src\VBox\Main\xml\xml.cpp' at #207). Please contact the product vendor! Details: code E_FAIL (0x80004005), component VirtualBox, interface IVirtualBox, callee IUnknown Context: "OpenMachine(Bstr(a->argv[0]), machine.asOutParam())" at line 219 of file VBoxManage.cpp
I have tried registering the xml file from a cmd command line and it works just fine, I had to remove the drive images (and I have no issues with that, just wonder how can I them later, but I'll try that when I can register the vm).
I will attach the batch file, the output screen and the xml file.
Please note that I will not remove the <AttachedDevice> section even though I did remove the whole <AttachedDevice type="HardDisk" port="0" device="0"><Image uuid="{962b6b54-41b8-4018-b79f-35bcb5836042}"/></AttachedDevice> section.
Attachments (3)
Change History (6)
by , 14 years ago
Attachment: | Ubuntu.xml added |
---|
comment:1 by , 14 years ago
I added the "whoami" command and it shows that the service is being run as "nt authority\system" or my user name (according to the logon credentials, this is expected). but even tough I have the Ubuntu vm registered it shows that it could not find it.
I know that the 80004005 is a "Registry key can't be accessed" but I would really like to know what registry key this thing is talking about.
comment:2 by , 14 years ago
0x80004005 is the generic COM error E_FAIL. Nothing to do with the registry.
comment:3 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Please reopen if still relevant with VBox 4.0.4.
The configuration file for the VM