On Tue, 2013-02-12 at 10:48 +0000, 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,]
8. rpm -qa | grep daemon-driver-xen         [yes,]
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 (*)]
16. creating a domain with virt-manager     [_DOES_NOT_ work (**)]
17. systemctl stop libvirtd.service
18. yum remove libvirt-daemon-driver-libxl
19. systemctl start libvirtd.service
20. ps aux | grep xend                      [nothing found]
21. start virt-manager                      [_COULD_NOT_ connect
                                             to xen://]
22. sudo xend
23. start virt-manager                      [connected to xen://]
24. creating a domain with virt-install     [_works_]
25. creating a domain with virt-manager     [_works_]
26. creating a domain with xl               [_works_ (**)]
27. reboot
28. ps aux | grep xend                      [nothing found]
29. start virt-manager                      [_COULD_NOT_ connect
                                             to xen://]
30. creating a domain with virt-manager     [_DOES_NOT_ work
                                             (of course!)]
31. creating a domain with virt-install     [_DOES_NOT_ work
                                             (of course!)]
32. creating a domain with xl               [_works_]

Ok, I think I'm done and I really hope this could be helpful!

It seems to me that:

1) if libvirt-daemon-driver-libxl is present, libxl driver is correctly 
   loaded, but it still has some bugs that prevent actually using it

2) if libvirt-daemon-driver-libxl is _not_ present we (I ?) are still
   seeing at least some of the issues described in the 893699 bugzilla 
   above. Am I the only one seeing this? Who is supposed to start xend 
   and when should hat happen?

The net effect is that, right now, I can't use libvirt with Xen at all,
on F18, neither with -driver-libxl nor with -driver-xen... Again, am I
the only one?

(*) # virt-install -l 
http://fedora.mirror.constant.com/linux/releases/18/Fedora/x86_64/os/ --ram 
1024 --disk /dev/vms/F18_x64 --name F18_x64

Starting install...
Retrieving file .treeinfo...                                                    
                                                      | 2.2 kB  00:00:00 !!! 
Retrieving file vmlinuz...                                                      
                                                      | 9.3 MB  00:00:06 !!! 
Retrieving file initrd.img...                                                   
                                                      |  53 MB  00:00:34 !!! 
ERROR    internal error libxenlight failed to create new domain 'F16_x64'
Domain installation does not appear to have been successful.

(**) It shouldn't. Starting from Xen 4.2 we have a check in xl that
looks for a lock file (by default in /var/lock/subsys/xend) and disallow
xl to do anything if xend is running. Here, the fact that I have to
started xend by hand messes that up. In fact, there should be an
initscript of some sort for xend... Where is it and what package is
supposed to provide it?

Thanks and Regards,

<<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: signature.asc
Description: This is a digitally signed message part

xen mailing list

Reply via email to