Vbox cannot find newly registered machines

steqve · Post by **steqve** » 18. Sep 2008, 23:24

Virtualbox 2.0.2:

VirtualBox Command Line Management Interface Version 2.0.2
(C) 2005-2008 Sun Microsystems, Inc.
All rights reserved.

VBoxManage createvm -name vmDNS -register -basefolder /raid/virt/vmDNS

Virtual machine 'vmDNS' is created and registered.
UUID: d042ecd1-6306-49e7-87b0-158b3b62389a
Settings file: '/raid/virt/vmDNS/vmDNS/vmDNS.xml'
VirtualBox Command Line Management Interface Version 2.0.2
(C) 2005-2008 Sun Microsystems, Inc.
All rights reserved.

VBoxManage modifyvm wmDNS -usb on -vrdp on -memory "348MB" -vram "4MB"

[!] FAILED calling virtualBox->FindMachine(Bstr(argv[0]), machine.asOutParam()) at line 4474!
[!] Primary RC = NS_ERROR_INVALID_ARG (0x80070057) - Invalid argument value
[!] Full error info present: true , basic error info present: true
[!] Result Code = NS_ERROR_INVALID_ARG (0x80070057) - Invalid argument value
[!] Text = Could not find a registered machine named 'wmDNS'
[!] Component = VirtualBox, Interface: IVirtualBox, {557a07bc-e6ae-4520-a361-4a8493199137}
[!] Callee = IVirtualBox, {557a07bc-e6ae-4520-a361-4a8493199137}

These commands are executed after each other. First the registration is sucessful, then the machine isn't found.

Any ideas? Fresh installed debian host which used to serve as VM-host before. Was using 1.5.x and the same commands worked fine then....

Post by **TerryE** » 19. Sep 2008, 00:38

Just out of interest try a

VBoxManage modifyvm d042ecd1-6306-49e7-87b0-158b3b62389a -usb on -vrdp on -memory 348 -vram 4

It's just that sometimes it can fail to pick up the VM by name. BTW, the vram and memory options do an atoi on their arguments. In other words its taken as an integer number of Mbytes and the postfix is ignored, so 128Gbytes would still allocate 128 Mbyte.

steqve · Post by **steqve** » 19. Sep 2008, 14:52

i'll give it a try.

How is vbox looking for registered vm:s? There is a .Virtualbox folder for the admin user and inside there is information about the machine...or at least the name, uuid and path to xml.

Post by **TerryE** » 19. Sep 2008, 15:03

The VirtualBox.xml file in this directory and is in effect the registry for VBox, and the UUID is the main key.

steqve · Post by **steqve** » 19. Sep 2008, 21:17

seems to work fine. But not useful for me as i run without GUI and want to have address the machines with their name.

Anyway it doesn't matter since I cannot compile the vboxdrv. It says it cannot find my source dir....but I have installed everything as I did with 1.6

2.0.2 is very different? Nothing seems to work as expected.

WHY does it not find my kernel sources? How does it look for them? by uname -r?

I do not think I should have to set the KERN_DIR cause before I could compile the driver...