From: Dario Faggioli <dario.faggioli@citrix.com>
To: Gizmo Chicken <gizmochicken@gmail.com>
Cc: ranjith krishnan <ranjithkrishnan1@gmail.com>, xen-devel@lists.xen.org
Subject: Re: Xen 4.1 compile from source and install on Fedora 17
Date: Thu, 13 Jun 2013 01:44:21 +0200 [thread overview]
Message-ID: <1371080661.3298.8.camel@Abyss> (raw)
In-Reply-To: <CAHdVSpmOVyUtAXgrzpDRPEgxJKVEzJswPk_fHRQDM9ewQwym1A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1857 bytes --]
On mer, 2013-06-12 at 09:22 -0400, Gizmo Chicken wrote:
> Not sure if the comment is correct, but based on Comment #9 to my bug
> report, Debian/Ubuntu seems to package Xen in such a way that certain
> components (such as libxenlight.so) are installed differently compared
> to other distros. See Comment #9 at
> https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1180281
>
That is possible, I guess... I'm sorry, but as I said already, I know
nothing of using both the packaged version of Xen and libvirt on Debian
or Ubuntu. :-(
> I haven't spent much time with virt-manager on Fedora 19 beta, so I
> can't provide details. But if I recall correctly, I also got
> something like "Unable to connect to libvirt" when attempting to use
> virt-manager with Xen and the XL toolstack. XL was definitely
> running, and near as I could tell, XM/xend was not running. I didn't
> try virt-manager with the XM toolstack.
>
Well, without the details, it's hard to say anything more than what has
been said already. I do test Xen on Fedora regularly, and that includes
basic libvirt (both virt-install and virt-manager) operations. Both
Fedora 18 and Fedora 19 work pretty well for me, and I haven't seen any
issues in connecting to libvirtd.
If you get the chance to try it again, feel free to ask for help,
providing all the needed details on what is that your are seeing, either
here, or on xen@lists.fedoraproject.org, or on
virt@lists.fedoraproject.org, or on libvir-list@redhat.com, depending on
where you think the problem could be. :-)
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-06-12 23:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 21:44 Xen 4.1 compile from source and install on Fedora 17 ranjith krishnan
2013-06-12 6:07 ` Pasi Kärkkäinen
2013-06-12 8:33 ` Dario Faggioli
2013-06-12 9:02 ` Gizmo Chicken
2013-06-12 9:35 ` Dario Faggioli
2013-06-12 13:22 ` Gizmo Chicken
2013-06-12 16:06 ` ranjith krishnan
2013-06-12 17:48 ` M A Young
2013-06-12 23:44 ` Dario Faggioli [this message]
2013-06-18 6:31 ` ranjith krishnan
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=1371080661.3298.8.camel@Abyss \
--to=dario.faggioli@citrix.com \
--cc=gizmochicken@gmail.com \
--cc=ranjithkrishnan1@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).