On Tue, Mar 11, 2008 at 03:18:04PM -0000, Soren Hansen wrote:
> > Anyone trying to use Virtmanager for the first time, with default
> > options, will always get this error and won't be able to do anything
> > until libvirtd is running (which is contained in the libvirt-bin
> > package, not installed by default).
> Erm, no. Anyone trying to use virt-manager for the first time, with
> default options, will get an entirely *different* error, namely a
> failure to connect to Xen.
Sorry, my mistake. That used to be the case, but I seem to have fixed
that already. You don't get an error until you actively try to connect
to the hypervisor, though.
--
Soren Hansen |
Virtualisation specialist | Ubuntu Server Team
Canonical Ltd. | http://www.ubuntu.com/
On Tue, Mar 11, 2008 at 03:18:04PM -0000, Soren Hansen wrote:
> > Anyone trying to use Virtmanager for the first time, with default
> > options, will always get this error and won't be able to do anything
> > until libvirtd is running (which is contained in the libvirt-bin
> > package, not installed by default).
> Erm, no. Anyone trying to use virt-manager for the first time, with
> default options, will get an entirely *different* error, namely a
> failure to connect to Xen.
Sorry, my mistake. That used to be the case, but I seem to have fixed
that already. You don't get an error until you actively try to connect
to the hypervisor, though.
-- www.ubuntu. com/
Soren Hansen |
Virtualisation specialist | Ubuntu Server Team
Canonical Ltd. | http://