From: Jim Fehlig <jfehlig@suse.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: Rohit Damkondwar <genius.rsd@gmail.com>, xen-devel@lists.xen.org
Subject: Re: Error : libxenlight state driver is not active
Date: Wed, 26 Dec 2012 10:18:34 -0700 [thread overview]
Message-ID: <50DB316A.6040704@suse.com> (raw)
In-Reply-To: <20121226125940.GQ8912@reaktio.net>
Pasi Kärkkäinen 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 entry
>> appears in the grub. Inspite of booting Fedora, with xen hypervisor entry
>> , 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 >= 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
next prev parent reply other threads:[~2012-12-26 17:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-25 20:09 Error : libxenlight state driver is not active Rohit Damkondwar
2012-12-26 12:59 ` Pasi Kärkkäinen
2012-12-26 17:18 ` Jim Fehlig [this message]
2012-12-27 8:17 ` Rohit Damkondwar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50DB316A.6040704@suse.com \
--to=jfehlig@suse.com \
--cc=genius.rsd@gmail.com \
--cc=pasik@iki.fi \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.