On Mon, 2013-02-11 at 18:00 +, Daniel P. Berrange wrote:
Ok, so it seems the package we want (for now) to be installed is
libvirt-daemon-driver-xen, and not libvirt-daemon-xen... Does that
sounds right?
No, people want to be installing 'libvirt-daemon-xen' in most
circumstances. This
On Mon, 2013-02-11 at 20:37 +, M A Young wrote:
menuentry 'Fedora, with Xen hypervisor' --class gnu-linux --class gnu
--class os --class xen $menuentry_id_option
'xen-gnulinux-simple-86a900c9-aa88-49f1-a007-0facdf17b732' {
insmod part_msdos
insmod ext2
set
On Tue, Feb 12, 2013 at 10:13:41AM +0100, Dario Faggioli wrote:
On Mon, 2013-02-11 at 18:00 +, Daniel P. Berrange wrote:
Ok, so it seems the package we want (for now) to be installed is
libvirt-daemon-driver-xen, and not libvirt-daemon-xen... Does that
sounds right?
No, people
On Mon, 2013-02-11 at 12:19 -0600, Major Hayden wrote:
On Feb 11, 2013, at 11:54 AM, Dario Faggioli raist...@linux.it wrote:
Ok, so it seems the package we want (for now) to be installed is
libvirt-daemon-driver-xen, and not libvirt-daemon-xen... Does that
sounds right?
FWIW, my system
On Tue, 12 Feb 2013, Dario Faggioli wrote:
Well, this is a very fair point, with the only issue being that, if you
install 'libvirt-daemon-xen', things break! :-(
How can we change that and make it work? Perhaps libvirt-daemon-xen
shouldn't bring in, as dependency, libvirt-daemon-driver-libxl,
On Mon, 2013-02-11 at 12:19 -0600, Major Hayden wrote:
FWIW, my system is working perfectly with this package set:
Ok, just one more question...
# rpmquery --queryformat %{NAME}\n -a | egrep libvirt|xen | sort
libvirt-client
libvirt-daemon
libvirt-daemon-config-network
On Tue, 2013-02-12 at 10:31 +, Daniel P. Berrange wrote:
The libxl driver should be disabled in Fedora versions whre it does
not work. AFAIK, that was already done, so libxl is only used when
built against newest Xen.
Yes, I remember that being the plan. What I'm missing (well, one of the
On Tue, 12 Feb 2013, Dario Faggioli wrote:
On Tue, 2013-02-12 at 10:48 +, M A Young wrote:
It seems to me this thread has been focussing on a work around for an
undisclosed problem rather than identifying what the problem actually is
and solving it, or coming up with a better workaround.
On Tue, 12 Feb 2013, M A Young wrote:
Let me try (again), repeating all the steps, starting from a fresh F18
install. After that, we'll decide if we want to stick with 893699
bugzilla entry, or create a new one, or whatever else we want to do...
Ok, here I am.
1. Install F18
2. yum install
