On Tue, 2013-02-12 at 22:32 +0000, M A Young wrote:
> 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.
Same here, and using 'driver_name=phy' as you suggest in the other mail
works. I also agree we should point libvirt-libxl people to this (and I
will).
libxl: verbose: libxl_create.c:158:libxl__domain_build_info_setdefault: qemu-xen is
unavailable, use qemu-xen-traditional instead: No such file or directory
libxl: debug: libxl_create.c:1174:do_domain_create: ao 0x7f784c0011a0: create: how=(nil)
callback=(nil) poller=0x7f784c001200
libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda
spec.backend=tap
libxl: debug: libxl_device.c:184:disk_try_backend: Disk vdev=xvda, backend tap unsuitable
because blktap not available
libxl: error: libxl_device.c:269:libxl__device_disk_set_backend: no suitable backend for
disk xvda
libxl: debug: libxl_event.c:1499:libxl__ao_complete: ao 0x7f784c0011a0: complete, rc=-3
libxl: debug: libxl_create.c:1187:do_domain_create: ao 0x7f784c0011a0: inprogress:
poller=0x7f784c001200, flags=ic
libxl: debug: libxl_event.c:1471:libxl__ao__destroy: ao 0x7f784c0011a0: destroy
Now, after having had small SELinux and bridging issues, I've got an
installation going... Let's see where it breaks! :-P
That being said, what do you think about the xend issues I was also
talking about in the original mail (which are more or less the same that
were already here
https://bugzilla.redhat.com/show_bug.cgi?id=893699) ?
I'm talking about steps 18 to 32 there, where I say that I'm still not
able to get xend starting properly and automatically ? I'd really prefer
libxl to work and xend to "die", but until we're not there, I think we
should have at least one which is working! :-O
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 R&D Ltd., Cambridge (UK)