Roberto Sassu wrote:
Hi everyone
I'm using Ubuntu 12.04.3 LTS with the Xen hypervisor installed (package version: 4.1.2-2ubuntu2.10), and Libvirt v0.10.2.2 (that interacts with Xen through the libxl driver).
I performed some adjustments to have the required features:
- Switch from Xend to libxl: I created upstart jobs for xenstored and xenconsoled so that necessary daemons are started earlier enough and Libvirt can contact the hypervisor through libxl.
- Add support for Open vSwitch: I added the script 'vif-openvswitch', taken from the master branch of the GIT repository, to the /etc/xen/scripts directory in order to plug network interfaces to Open vSwitch switches.
I know that the support for libxl is experimental in Xen 4.1, but I'm wondering if someone has a solution to the following issues:
Note that in libvirt 1.0.1, I removed support for Xen 4.1 libxl from the libvirt libxl driver when adding support for libxl in Xen 4.2 and beyond https://www.redhat.com/archives/libvir-list/2012-November/msg01582.html The libxl interface underwent several incompatible changes between 4.1 and 4.2, and since libxl in 4.1 was experimental I saw no reason to clutter the libvirt libxl driver with support both. For Xen <= 4.1, you should use the legacy xen libvirt driver, which has been around for years and is quite stable. If you are interested in libxl, can you use a more recent Xen (>= 4.2) and libvirt (preferably 1.1.2 since it contains console support you mention below)? IMO, I don't think we should waste time investigating issues in a configuration no longer supported. Regards, Jim
1) On domain destroy, the host configuration is not clean: if the flag 'force' is set to 0 some entries in the xenstored database are not removed (console, ...) if the flag 'force' is set to 1 (as it is done in Libvirt), the event 'online' associated to the network interface is not triggered and, thus, the vif is not removed from the Open vSwitch switch. To fix this issue, I temporarily added a call to vif-openvswitch into the xen-hotplug-cleanup script.
2) When a domain is started from Libvirt, the console source path does not appear in the output of the command 'virsh dumpxml instance-00000381'
3) Sometimes, a domU is not started at all. If I start a virtual machine from Libvirt through virsh or directly through xl, these tools report that the virtual machine is running but I see no messages coming from the console and the CPU time remains fixed.
I'm attaching some files that may be useful to understand the problem:
- libvirt.xml: domain specifications (Libvirt format) - domain.xl: domain specifications (Xen format) - libvirt_virsh_dumpxml.log: output of the command 'virsh dumpxml instance-00000381' - xl_create.log: output of the command 'xl create -d domain.xl' - xl_info.log: output of the command 'xl info' - qemu-dm-instance-00000381.log: qemu-dm log - syslog_vif6_0.log: vif attach/detach logs from /var/log/syslog - xenstore-db-not-clean.log: xenstore db entries not removed after 'xl destroy' - libvirt_libxl.log: log from /var/log/libvirt/libxl.log after the execution of the command 'virsh create libvirt.xml'
Lastly, I want to add that the image I'm using for the tests is Ubuntu Precise 12.04.3 LTS, taken from the URL:
http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64...
and the kernel is taken from the URL:
http://cloud-images.ubuntu.com/precise/current/unpacked/precise-server-cloud...
Thanks
Roberto Sassu