Failed on OSX 10.6.6

[jimrubenstein]

Below is the output after running the ievsm.sh script. (Other output is missing because I'd run it a few times before, and found I needed to upgrade my version of VBox, so I already had some things downloaded.)

VBox Version: 4.0.12 r72916

thanks!

Administrators-iMac-2:HardDisks Admin$ curl -s https://raw.github.com/xdissent/ievms/master/ievms.sh | bash
Checking for VirtualBox
Checking for Oracle VM VirtualBox Extension Pack
Pack no. 0:   Oracle VM VirtualBox Extension Pack
Building IE7 VM
Checking for existing VHD at /Users/Admin/.ievms/vhd/IE7/Windows Vista.vhd
Checking for existing IE7 VM
VBoxManage: error: Could not find a registered machine named 'IE7'
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox, interface IVirtualBox, callee nsISupports
Context: "FindMachine(Bstr(VMNameOrUuid).raw(), machine.asOutParam())" at line 2158 of file VBoxManageInfo.cpp
Creating IE7 VM
Virtual machine 'IE7' is created and registered.
UUID: af538717-e19b-49c3-b135-1af50796dfc8
Settings file: '/Users/Admin/VirtualBox VMs/IE7/IE7.vbox'
Oracle VM VirtualBox Command Line Management Interface Version 4.0.12
(C) 2005-2011 Oracle Corporation
All rights reserved.

Usage:

VBoxManage storageattach    <uuid|vmname>
                            --storagectl <name>
                            [--port <number>]
                            [--device <number>]
                            [--type dvddrive|hdd|fdd]
                            [--medium none|emptydrive|
                                      <uuid>|<filename>|host:<drive>|iscsi]
                            [--mtype normal|writethrough|immutable|shareable|
                                     readonly|multiattach]
                            [--comment <text>]
                            [--passthrough on|off]
                            [--bandwidthgroup <name>]
                            [--forceunmount]
                            [--server <name>|<ip>]
                            [--target <target>]
                            [--tport <port>]
                            [--lun <lun>]
                            [--encodedlun <lun>]
                            [--username <username>]
                            [--password <password>]
                            [--intnet]

VBoxManage: error: Unknown option: --setuuid

[xdissent]

It looks like the setuuid option might have been added in VirtualBox 4.1. I'll figure out what the 4.0.12 equivalent is and modify the command based on whichever version is installed. Thanks for the bug report!

[tjarratt]

Looks like the option was previously --uuid.

[xdissent]

You know, the setuuid bit is really only there to prevent an error if someone already has the MS VMs installed in Virtualbox. If you try to install multiple instances of the same VM image, Virtualbox will complain about duplicate UUIDs. So while I'm debating whether to remove the UUID handling altogether, you can simply comment out --setuuid "" to avoid the error with no ill effect.

[Bastes]

Same problem using Ubuntu 11.04

[xdissent]

Hey Michel, thanks for reminding me about this bug. I tested the uuids branch this weekend and it seemed to do the trick for versions of VirtualBox that don't include the --setuuid option. Note that a bug may still exist related to extension packs under Ubuntu when using older versions of VirtualBox. Check the linux-extpacks branch for a fix that I'll roll out soon.

[sprankhub]

Unfortunately, on Ubuntu 11.10 and VirtualBox 4.1.6, I still get this error:

Checking for existing IE7 VM
VBoxManage: error: Could not find a registered machine named 'IE7'
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox, interface IVirtualBox, callee nsISupports
Context: "FindMachine(Bstr(VMNameOrUuid).raw(), machine.asOutParam())" at line 2333 of file VBoxManageInfo.cpp
Creating IE7 VM
VBoxManage: error: Machine settings file '/home/simon/VirtualBox VMs/IE7/IE7.vbox' already exists
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component Machine, interface IMachine, callee nsISupports
Context: "CreateMachine(bstrSettingsFile.raw(), name.raw(), osTypeId.raw(), Guid(id).toUtf16().raw(), FALSE , machine.asOutParam())" at line 249 of file VBoxManageMisc.cpp

Does anybody know how to fix this? Thank you in advance!

[darKoram]

Yup, this bug is still there as of 11.10 and VBox 4.1.8

VBoxManage -v

4.1.8r75467

I tried starting the vm using name and then uuid, both failed.

sudo VBoxManage startvm winxp
VBoxManage: error: Could not find a registered machine named 'winxp'
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox, interface IVirtualBox, callee nsISupports
Context: "FindMachine(Bstr(pszVM).raw(), machine.asOutParam())" at line 544 of file VBoxManageMisc.cpp
kesten@kesten-K42Jr:~$ sudo VBoxManage startvm 0ddcecdc-137d-4498-bbc6-6190b469e3b8
VBoxManage: error: Could not find a registered machine with UUID {0ddcecdc-137d-4498-bbc6-6190b469e3b8}
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox, interface IVirtualBox, callee nsISupports
Context: "FindMachine(Bstr(pszVM).raw(), machine.asOutParam())" at line 544 of file VBoxManageMisc.cpp

winxp is in ~/VirtualBox VMs/

[xdissent]

"winxp" wouldn't be the name of an ievms-created VM. Not sure what's going on there. However, I do need to spin up another bootable Ubuntu 11.10 partition to confirm that issue is still closed.

[darKoram]

Found the answer on the vitrualbox.org forums

I had this problem too.
The answer might be the user you are running VBoxManage as.
If I run VBoxManage as root (or via sudo) it only knows about virtual machines registered as root.
You need to run it as the same user who created the virtual machines.

I was running with sudo because I thought i might be having usb problems due to permissions issues.
However, running as sudo means VBoxManage doesn't find vm's installed by me as a regular user.

I'd still say there's a bug there in the error message:
it should mention permissions and give a hint about vm's installed as root vs user when trying to launch with sudo.

kesten