[et-mgmt-tools] virt-manager 0.3.0 can't see inactive vms?

[Mark Cave-Ayland]

On Thu, 2007-02-15 at 11:58 +0000, Daniel P. Berrange wrote:

> > Another quick couple of questions: firstly is there a way to bypass
> > "Open Connection" dialog on startup so that it assumes that the default
> > "Local Xen Host" is selected? I can see the -C option for a URI but
> > can't see a way to specify the equivalent of "Local Xen Host" on the
> > command line?
> 
>   virt-manager  --connect Xen
> 
> Will do the trick IIRC.


Actually, I've just found out this doesn't work. I've finally got around
to creating a menu entry in Ubuntu which reads: "gksu virt-manager
--connect Xen" and when selected, it does bypass the selection dialog
and go straight to the list of virtual machines. However, when I try and
start my Windows XP virtual machine, nothing happens!

I eventually tried running "virt-manager --connect Xen" directly and got
the following message on the console: "libvir: Domain error winxp:
operation virDomainCreate forbidden for read only access". However, if I
I just execute "virt-manager" and select "Local host" and hit "Connect",
then I can start the VMs fine.

The only conclusion I can come to is that if you specify "--connect Xen"
on the command line for virt-manager that it behaves the same as if you
tick the "Read only" checkbox in the "Open Connection" dialog. Am I
right in thinking this is a bug?

FWIW, I'm using the latest versions of everything: libvirt 0.2.0,
virtinst-0.101.0 and virt-manager 0.3.1.


Many thanks,

Mark.