Re: [Fedora-xen] Peculiar errors with libvirt/virt-manager/xen in F18
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 has deps to ensure that you have all the recommended packages required to run libvirt + xen together. libvirt-daemon-driver-xen, is just the bare minimum libvirt driver and nothing else, so is not what users typically want. 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, at least not in versions where the libxl libvirt driver is known to be broken? Dario -- This happens because I choose it to happen! (Raistlin Majere) - Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli Senior Software Engineer, Citrix Systems RD Ltd., Cambridge (UK) signature.asc Description: This is a digitally signed message part -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Updating xen package does not 'refresh' grub.cfg
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 root='hd0,msdos8'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos8
--hint-efi=hd0,msdos8 --hint-baremetal=ahci0,msdos8
20f18f9a-c006-4d92-93d2-bf053c163638
else
search --no-floppy --fs-uuid --set=root
20f18f9a-c006-4d92-93d2-bf053c163638
fi
echo'Loading Xen xen ...'
multiboot /xen.gz placeholder
echo'Loading Linux 3.7.6-201.fc18.x86_64 ...'
module /vmlinuz-3.7.6-201.fc18.x86_64 placeholder
root=/dev/mapper/host-fedora_root ro
}
Did you update the kernel at the same time?
Well, it can definitely be. In this specific case, I `yum upgrade'-ed
the system after a while and it installed both a new kernel and a new
Xen (along with a bunch of other stuff, of course).
That looks like what you might
get with grubby which is run (which doesn't handle xen very well, which is
why xen-hypervisor runs grub2-mkconfig).
Mmm... I see. Well, I think it's quite possible that a kernel and a xen
update happen at the same time, so this seems quite an issue to me... Am
I wrong?
What can we do to improve the situation? Should I open a bug against
grubby?
Thanks and Regards,
Dario
--
This happens because I choose it to happen! (Raistlin Majere)
-
Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli
Senior Software Engineer, Citrix Systems RD Ltd., Cambridge (UK)
signature.asc
Description: This is a digitally signed message part
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Peculiar errors with libvirt/virt-manager/xen in F18
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 want to be installing 'libvirt-daemon-xen' in most circumstances. This has deps to ensure that you have all the recommended packages required to run libvirt + xen together. libvirt-daemon-driver-xen, is just the bare minimum libvirt driver and nothing else, so is not what users typically want. 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, at least not in versions where the libxl libvirt driver is known to be broken? 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. Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Peculiar errors with libvirt/virt-manager/xen in F18
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 is working perfectly with this package set:
# rpmquery --queryformat %{NAME}\n -a | egrep libvirt|xen | sort
libvirt-client
libvirt-daemon
libvirt-daemon-config-network
libvirt-daemon-config-nwfilter
libvirt-daemon-driver-interface
libvirt-daemon-driver-lxc
libvirt-daemon-driver-network
libvirt-daemon-driver-nodedev
libvirt-daemon-driver-nwfilter
libvirt-daemon-driver-qemu
libvirt-daemon-driver-secret
libvirt-daemon-driver-storage
libvirt-daemon-driver-uml
libvirt-daemon-driver-xen
libvirt-python
xen
xen-hypervisor
xen-libs
xen-licenses
xen-runtime
Installing libvirt-daemon-xen brings in libvirt-daemon-driver-libxl as a
dependency and that's when things begin to break.
Yep, exact same thing here, on any Fedora installation from 16 to 18
that I was able to test up to now.
Dario
--
This happens because I choose it to happen! (Raistlin Majere)
-
Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli
Senior Software Engineer, Citrix Systems RD Ltd., Cambridge (UK)
signature.asc
Description: This is a digitally signed message part
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Peculiar errors with libvirt/virt-manager/xen in F18
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, at least not in versions where the libxl libvirt driver is known to be broken? 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. Could someone provide more details of exactly what happens and preferably submit a bug report to http://bugzilla.redhat.com/ so it can be looked at properly. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Peculiar errors with libvirt/virt-manager/xen in F18
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
libvirt-daemon-config-nwfilter
libvirt-daemon-driver-interface
libvirt-daemon-driver-lxc
libvirt-daemon-driver-network
libvirt-daemon-driver-nodedev
libvirt-daemon-driver-nwfilter
libvirt-daemon-driver-qemu
libvirt-daemon-driver-secret
libvirt-daemon-driver-storage
libvirt-daemon-driver-uml
libvirt-daemon-driver-xen
libvirt-python
xen
xen-hypervisor
xen-libs
xen-licenses
xen-runtime
And with this configuration you have xend starting automatically either
at startup, or at libvirt startup, or when you first try to connect to
xen://, or something like that?
I mean, are you able to create VMs with virt-manager and/or virt-install
_without_ having to start xend by hand?
I'm asking because I'm not! :-(
Installing libvirt-daemon-xen brings in libvirt-daemon-driver-libxl as a
dependency and that's when things begin to break.
Yes, again, that is the same here, and I also see the libxenlight
related errors you where talking about. Problem is that, for me, just
removing libvirt-daemon-driver-libxl and restarting libvirtd is not at
all enough, as xend is not started...
Thanks and 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 RD Ltd., Cambridge (UK)
signature.asc
Description: This is a digitally signed message part
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Peculiar errors with libvirt/virt-manager/xen in F18
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 things I'm missing) is whether libxl should be enabled or disabled in F18. Looking at it from a Xen POV, it should be enabled, because F18 ships Xen 4.2, and libxl is the default toolstack for 4.2, while Xend is formally deprecated. However, installing what we get with libvirt-daemon-driver-libxl does not work, hence the confusion. :-/ Also, at least in my case, even _without_ libvirt-daemon-driver-libxl and with _only_ libvirt-daemon-driver-xen, I can't use libvirt, as xend does not starts properly, as it was used o do just a couple of months ago (for sure it was starting in F16 and F17). Hope this (and the other mails I sent) clarify the thing a bit... :-) Thanks and 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 RD Ltd., Cambridge (UK) signature.asc Description: This is a digitally signed message part -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Peculiar errors with libvirt/virt-manager/xen in F18
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. Indeed, while identifying and fixing/helping to fix was my first and main intent. I'm think this is still related to what we were discussing here: https://bugzilla.redhat.com/show_bug.cgi?id=893699, although that took so many different directions that it is now very difficult to make any sense out of it! If I'm not providing enough or good enough feedback and suggestions, I'm sorry, but really, my primary concern is to see all this working! :-) Could someone provide more details of exactly what happens and preferably submit a bug report to http://bugzilla.redhat.com/ so it can be looked at properly. 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 xen 3. reboot 4. ps aux | grep xend [nothing found] 5. creating a domain with xl[_works_] 6. yum install libvirt-daemon-xen virt-manager virt-viewer \ python-virt-inst libvirt-daemon-config-network 7. rpm -qa | grep daemon-driver-libxl [yes, 0.10.2.3-1] 8. rpm -qa | grep daemon-driver-xen [yes, 0.10.2.3-1] 9. reboot (just in case!) 10. ps aux | grep xend [nothing found] 11. systemctl status libvirtd.service [active (running)] 12. start virt manager [connected to xen:// (I can't see Dom0, but that is fine, IIRC)] 13. ps aux | grep xend [nothing found] 14. creating a domain with xl [_works_] 15. creating a domain with virt-install [_DOES_NOT_ work (*)] Check /var/log/libvirt/libxl/libxl.log to see what went wrong. I have done some testing and in my case it seems it defaults to trying the blktap driver for disks, which won't work with the Fedora kernel. There may be some way to get it to use file, phy or other driver as you can with an xl configuration file, but I haven't found a way that works yet. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Peculiar errors with libvirt/virt-manager/xen in F18
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 xen 3. reboot 4. ps aux | grep xend [nothing found] 5. creating a domain with xl[_works_] 6. yum install libvirt-daemon-xen virt-manager virt-viewer \ python-virt-inst libvirt-daemon-config-network 7. rpm -qa | grep daemon-driver-libxl [yes, 0.10.2.3-1] 8. rpm -qa | grep daemon-driver-xen [yes, 0.10.2.3-1] 9. reboot (just in case!) 10. ps aux | grep xend [nothing found] 11. systemctl status libvirtd.service [active (running)] 12. start virt manager [connected to xen:// (I can't see Dom0, but that is fine, IIRC)] 13. ps aux | grep xend [nothing found] 14. creating a domain with xl [_works_] 15. creating a domain with virt-install [_DOES_NOT_ work (*)] Check /var/log/libvirt/libxl/libxl.log to see what went wrong. I have done some testing and in my case it seems it defaults to trying the blktap driver for disks, which won't work with the Fedora kernel. There may be some way to get it to use file, phy or other driver as you can with an xl configuration file, but I haven't found a way that works yet. Actually, in your case you could try --disk path=/dev/vms/F18_x64,driver_name=phy . Unfortunately driver_name=file doesn't work for a disk image file as it seems that uses blktap, which is arguably a libvirt libxl driver bug. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
