Virtualbox Redhat no valid drive

Kenneth Kirchner ken at kirchners.com
Thu May 6 05:19:10 UTC 2010


On May 5, 2010, at 9:37 PM, sync wrote:

> On Fri, Apr 30, 2010 at 6:36 PM, Carl T. Miller <carl at carltm.com> wrote:
> 
>> sync wrote:
>>> But I did that you said , the output was these:
>>> VirtualBox Command Line Management Interface Version 3.1.0
>>> (C) 2005-2009 Sun Microsystems, Inc.
>>> All rights reserved.
>>> 
>>> ERROR: Could not find a registered machine named 'Redhat'
>>> Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox,
>>> interface IVirtualBox, callee nsISupports
>>> Context: "FindMachine (Bstr(VMNameOrUuid), machine.asOutParam())" at line
>>> 2017 of file VBoxManageInfo.cpp
> 
> Okay. The following messages are the result of the above commands:
> 
> $ VBoxManage -q list vms
> "fedora" {d841751d-8be3-41af-9cef-2a22eae97017}
> "WinXP" {a23bf0e6-4009-4924-8864-4dbe1dda5adf}
> "Solaris" {fd4dc940-9f15-49b7-9310-dc6e11e61f82}
> "centos" {026d2d1c-8e8a-4a6c-9651-adcd6663d61e}
> "RedHat" {46782ab5-b2a8-489a-8003-f512469495aa}


Could it be that your command says "Redhat" but the VM name is "RedHat" (note the capital H)?  Sometimes case matters, but I dont know how picky this app is.

-KK


More information about the redhat-list mailing list