Re: [VBox-users] Third try for answers: Why VBoxManager cannot list vms

[Pau G. i Q. <pgq...@el...>]

Hi,

Sounds like $HOME is not returning the location of the .VirtualBox
directory. That's why VBoxManage does not list anything: it looks for
.VirtualBox, finds none (or an empty one), then lists nothing.


On Fri, Nov 25, 2011 at 5:07 PM, Harry Putnam <re...@ne...> wrote:
> I've attempted to get some help on this twice before recently.  I got
> one replay informing me that the posting user could run VBoxManager
> from cygwin shell and successfully `list vms'
>
> Is there no one here who has an idea how to debug this?
> Is the content of my posts too lame to deserve attention?
>
> My setup must be very similar to the one reply I got about cygwin:
>
> Lan with linux and windows7 machines,  One windows7 machine has 2 vms
> installed from Vbox.  Both are running some kind of solaris guests.
> That win7 box also has cygwin installed.
>
> My usage usually would be to ssh into the windows box, which puts me
> in a cygwin shell.
>
>   echo $SHELL
>  /bin/bash
>
> And cygwin bash is the only one installed.
>
> And `which VboxManage' shows:
>   which VboxManage
>  /cygdrive/c/Program Files/Oracle/VirtualBox/VboxManage
>
> I think I've updated twice.. and now running:
>
>   VboxManage -v
>   4.1.6r74713
>
> These commands (below) used to get the expected responses...
>
> In that shell the command `VboxManage list vms' pauses a moment and
> then returns me to the shell prompt... no output.
>
> Something like `VboxManage startvm voi', returns output that seems to
> indicate that VboxManage does not know anything about any vms
> installed and seems to indicate there is some registering process.
>
> Ditto for VboxManage list -l runningvms
>  Again no output at all, even though two vms are currently running
>
> Is it possible to re-register or whatever, the installed vms so that
> VboxManage knows about them
>
>  VboxManage startvm voi
>  VboxManage.exe: error: Could not find a registered machine named 'voi'
>
>  VboxManage.exe: error: Details: code VBOX_E_OBJECT_NOT_FOUND
>  (0x80bb0001), component VirtualBox, interface IVirtualBox, callee
>  IUnknown Context: "FindMachine(Bstr(pszVM).raw(),
>  machine.asOutParam())" at line 544 of file VBoxManageMisc.cpp
>
> The VboxManage tool is so involved its not so easy to see how to get
> some better debug information or how to debug this situation.
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> VBox-users-community mailing list
> VBo...@li...
> https://lists.sourceforge.net/lists/listinfo/vbox-users-community
>



-- 
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)