From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jim Fehlig Subject: Re: Error : libxenlight state driver is not active Date: Wed, 26 Dec 2012 10:18:34 -0700 Message-ID: <50DB316A.6040704@suse.com> References: <20121226125940.GQ8912@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20121226125940.GQ8912@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: Rohit Damkondwar , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org Pasi K=E4rkk=E4inen wrote: > On Wed, Dec 26, 2012 at 01:39:58AM +0530, Rohit Damkondwar wrote: > = >> Hi all. I recently compiled xen 4.1.3 on Fedora 17(64 bit). The xen e= ntry >> appears in the grub. Inspite of booting Fedora, with xen hypervisor e= ntry >> , when I start virt-manager, I get an error >> " Internal Error : libxenlight state driver is not active " >> >> Can anyone help me on this? >> = > > Are you using xm/xend toolstack? is xend running? if yes, then configure = libvirt to use xm/xend driver. > = FYI, there is no configuration knob in libvirt for selecting the legacy xen driver (primarily xend-based) vs the libxl driver. Assuming both drivers are included in your libvirt installation, libvirtd will load the legacy driver if xend is running, otherwise load the libxl driver. = Changing the configured xen toolstack requires a libvirtd restart. > I wouldn't recommend using xl/libxl (libxenlight) in Xen 4.1.x, it was a = tech preview there, > and it's more mature in Xen 4.2.x+ > = Agreed. You will need libvirt >=3D 1.0.1 to work with Xen 4.2.x libxl. = And recall that the libxl driver is missing some functionality wrt the legacy xend driver, e.g. migration. Regards, Jim