Hello,
I followed this thread on the list archives.
I've just installed Fedora 18 and now I want to run the VM images I previously run on Fedora 16 (xen 4.1 + libvirt).
So, I would like to know what is the current status of xen/libvirt integration.
From the xen wiki (http://wiki.xen.org/wiki/Fedora_Host_Installation), it
seems that it is still unsafe to use libvirt with the xl toolstack. But the last update is on Febraury 2013. So some time is passed. Is it still true?
Furthermore, do you know what changes one has to do to a libvirt VM configuration XML file that was used to define VM for the xend toolstack?
Thank you very much for the help!
Best,
-- Marco
On Wed, Apr 17, 2013 at 4:23 PM, sguazt marco.guazzone@gmail.com wrote:
Hello,
I followed this thread on the list archives.
I've just installed Fedora 18 and now I want to run the VM images I previously run on Fedora 16 (xen 4.1 + libvirt).
So, I would like to know what is the current status of xen/libvirt integration. From the xen wiki (http://wiki.xen.org/wiki/Fedora_Host_Installation), it seems that it is still unsafe to use libvirt with the xl toolstack. But the last update is on Febraury 2013. So some time is passed. Is it still true?
Furthermore, do you know what changes one has to do to a libvirt VM configuration XML file that was used to define VM for the xend toolstack?
Thank you very much for the help!
Best,
Hello,
Just to add some other info.
I've tried to use the xend toolstack in the way suggested in the Xen wiki and in this thread. 1. Disable SELinux (just in case...) 2. Removed libvirt-daemon-driver-libxml package (rpm -e --no-deps ...) 3. Enabled/started xend via systemctl 4. Rebooted the host
After the boot I've done some safety check: $ systemctl is-enabled xend.service enabled
$ ps -furoot | grep -i xen root 31 2 0 17:20 ? 00:00:00 [xenwatch] root 32 2 0 17:20 ? 00:00:00 [xenbus] root 523 1 0 17:20 ? 00:00:00 /usr/sbin/xenstored --pid-file /var/run/xenstored.pid root 592 1 0 17:20 ? 00:00:00 /usr/sbin/xenconsoled --log=none --log-dir=/var/log/xen/console root 705 1 0 17:20 ? 00:00:04 /usr/bin/python -Es /usr/sbin/xend
Then I've tried the following command (as root)
$ virt-install -v -c iso/CentOS-6.4-x86_64-minimal.iso --ram 1024 --disk path=./images/test-c63_64-xen.img,size=10 --name test-c64_64 --graphics vnc --debug
And I got the following error
libvirtError: POST operation failed: xend_post: error from xen daemon: (xend.err 'Device 768 (vbd) could not be connected. Hotplug scripts not working.')
Any idea?
Thanks,
-- Marco
On Wed, Apr 17, 2013 at 5:39 PM, sguazt marco.guazzone@gmail.com wrote:
On Wed, Apr 17, 2013 at 4:23 PM, sguazt marco.guazzone@gmail.com wrote:
Hello,
I followed this thread on the list archives.
I've just installed Fedora 18 and now I want to run the VM images I previously run on Fedora 16 (xen 4.1 + libvirt).
So, I would like to know what is the current status of xen/libvirt integration. From the xen wiki (http://wiki.xen.org/wiki/Fedora_Host_Installation), it seems that it is still unsafe to use libvirt with the xl toolstack. But the last update is on Febraury 2013. So some time is passed. Is it still true?
Furthermore, do you know what changes one has to do to a libvirt VM configuration XML file that was used to define VM for the xend toolstack?
Thank you very much for the help!
Best,
Hello,
Just to add some other info.
I've tried to use the xend toolstack in the way suggested in the Xen wiki and in this thread.
- Disable SELinux (just in case...)
- Removed libvirt-daemon-driver-libxml package (rpm -e --no-deps ...)
- Enabled/started xend via systemctl
- Rebooted the host
After the boot I've done some safety check: $ systemctl is-enabled xend.service enabled
$ ps -furoot | grep -i xen root 31 2 0 17:20 ? 00:00:00 [xenwatch] root 32 2 0 17:20 ? 00:00:00 [xenbus] root 523 1 0 17:20 ? 00:00:00 /usr/sbin/xenstored --pid-file /var/run/xenstored.pid root 592 1 0 17:20 ? 00:00:00 /usr/sbin/xenconsoled --log=none --log-dir=/var/log/xen/console root 705 1 0 17:20 ? 00:00:04 /usr/bin/python -Es /usr/sbin/xend
Then I've tried the following command (as root)
$ virt-install -v -c iso/CentOS-6.4-x86_64-minimal.iso --ram 1024 --disk path=./images/test-c63_64-xen.img,size=10 --name test-c64_64 --graphics vnc --debug
And I got the following error
libvirtError: POST operation failed: xend_post: error from xen daemon: (xend.err 'Device 768 (vbd) could not be connected. Hotplug scripts not working.')
Any idea?
Thanks,
-- Marco
Hello again,
I reinstalled Fedora 18 and used the Virtualization Preview Repository ( http://fedoraproject.org/wiki/Virtualization_Preview_Repository). While libvirtd+libxl still has problems (e.g., I got "error: internal error libxenlight failed to create new domain"), the combination libvirtd+xend seems to work.
Actually, I still get problem with virt-viewer but I can live without it by using a VNC viewer.
I hope to see Virtualization Preview package move soon in the official F18 repository :)
Best,
-- Marco
On gio, 2013-04-18 at 16:30 +0200, sguazt wrote:
Hello again,
I reinstalled Fedora 18 and used the Virtualization Preview Repository (http://fedoraproject.org/wiki/Virtualization_Preview_Repository).
Mmm... weird that you needed VirtPreview to get libvirt+xend to work. It used, should, and actually does work for me on a "plain" F18 (i.e., no VirtPreview).
While libvirtd+libxl still has problems (e.g., I got "error: internal error libxenlight failed to create new domain"), the combination libvirtd+xend seems to work.
Yep, that's the status. One bugfix for one of the causes of the issue you're seeing should be "in-flight", but I'm not sure whether there are other bugs hanging around. :-(
Again, with or without VirtPreview, using xend (which means just making sure it starts, as libvirt's libxl driver won't load if it find it running) everything should be fine.
Actually, I still get problem with virt-viewer but I can live without it by using a VNC viewer.
What problem? Can you be more specific? Again, with xend, I don't have problem of an kind, not even with virt-viewer.
I hope to see Virtualization Preview package move soon in the official F18 repository :)
Mmm... I might be wrong, but I'm not sure that's ever going to happen. My understanding is that VirtPreview hosts the packages that are in rawhide, although built for F18 (in this case). This means that most of what you see there will end up in F19, and very few of it will involve F18. However, if you find and rise a bug, unless the backport to the libvirt version that ships with F18 is impossible, it shouldn't be a big deal to have it fixed there too...
Thanks for sharing your experience. Dario
Hello Dario,
On Thu, Apr 25, 2013 at 12:28 AM, Dario Faggioli raistlin@linux.it wrote:
On gio, 2013-04-18 at 16:30 +0200, sguazt wrote:
Hello again,
I reinstalled Fedora 18 and used the Virtualization Preview Repository (http://fedoraproject.org/wiki/Virtualization_Preview_Repository).
Mmm... weird that you needed VirtPreview to get libvirt+xend to work. It used, should, and actually does work for me on a "plain" F18 (i.e., no VirtPreview).
Don't know why, but without the VirtPreview repo I get the following error:
"libvirtError: POST operation failed: xend_post: error from xen daemon: (xend.err 'Device 768 (vbd) could not be connected. Hotplug scripts not working.')"
Actually, I still get problem with virt-viewer but I can live without it by using a VNC viewer.
What problem? Can you be more specific? Again, with xend, I don't have problem of an kind, not even with virt-viewer.
If I run
$ virt-viewer rubis-web
where "rubis-web" is the name of my domU
I get a dialog box with this error message
"Unable to connect to libvirt with URI [none] "
and on the console terminal I get this message
** (virt-viewer:4506): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-giWEeisA4Z: Connection refused
(but I don't know if they are related, because the above message is only a warning, while the former is an error.)
Instead, if I use a VNC viewer (actually, tigervnc) it works without problems:
$ vncviewer 127.0.0.1:5900
If I look in the XML of my domU:
$ virsh dumpxml rubis-web
I can see the entry for VNC:
... <graphics type='vnc' port='5900' autoport='yes' keymap='en-us'/> ...
I hope to see Virtualization Preview package move soon in the official
F18 repository :)
Mmm... I might be wrong, but I'm not sure that's ever going to happen. My understanding is that VirtPreview hosts the packages that are in rawhide, although built for F18 (in this case). This means that most of what you see there will end up in F19, and very few of it will involve F18. However, if you find and rise a bug, unless the backport to the libvirt version that ships with F18 is impossible, it shouldn't be a big deal to have it fixed there too...
I see
Thanks for sharing your experience. Dario
Thank you for the feedback!
Best,
-- Marco
On mer, 2013-04-17 at 16:23 +0200, sguazt wrote:
Hello,
Hi,
So, I would like to know what is the current status of xen/libvirt integration. From the xen wiki (http://wiki.xen.org/wiki/Fedora_Host_Installation), it seems that it is still unsafe to use libvirt with the xl toolstack.
But the last update is on Febraury 2013. So some time is passed.
Well, progress have been made, but I think xend should still be considered the preferred wa of interacting with libvirt.
Furthermore, do you know what changes one has to do to a libvirt VM configuration XML file that was used to define VM for the xend toolstack?
I'm shooting a bit in the dark here, but I'd say it should work without changing anything? :-O
Thanks and Regards, Dario
xen@lists.stg.fedoraproject.org