[Users] libvirt dependency vs. a way to have Solaris hosts in ovirt-engine
Hi, as you know Solaris (Open Indiana) has qemu-kvm although they don't use libvirt (in fact libvirt tighted to much to Linux specifics). If vdsm whould interact with qemu-kvm without libvirt it would open a way to have Solaris hosts in ovirt-engine. libvirt is another abstraction after vdsm layer, or if vdsm could use "plugins" to interact with qemu-kvm (libvirt, "native", solaris-style), it could use current mode, bypass libvirt and use solaris tools to talk to their qemu-kvm. jbelka
On Tue, Jan 08, 2013 at 10:02:05AM +0100, Jiri Belka wrote:
Hi,
as you know Solaris (Open Indiana) has qemu-kvm although they don't use libvirt (in fact libvirt tighted to much to Linux specifics).
If vdsm whould interact with qemu-kvm without libvirt it would open a way to have Solaris hosts in ovirt-engine.
libvirt is another abstraction after vdsm layer, or if vdsm could use "plugins" to interact with qemu-kvm (libvirt, "native", solaris-style), it could use current mode, bypass libvirt and use solaris tools to talk to their qemu-kvm.
In the old days, vdsm used to work with qemu processes directly. We moved to be using libvirt's abstraction in order to gain then-new qmp code "for free", and to make it easier for 3rd party applications poll oVirt VMs over the libvirt api. We also use the libvirt dom xml as an API for vdsm extension hooks. Beyond that, there are a few Linuxisms in Vdsm itself. I would first want to see it ported to non-Fedora-flavor Linuxes (did someone say Ubuntu?), and only later to Solaris. Dan.
On Thu, Jan 10, 2013 at 11:51:56AM +0200, Dan Kenigsberg wrote:
On Tue, Jan 08, 2013 at 10:02:05AM +0100, Jiri Belka wrote:
Hi,
as you know Solaris (Open Indiana) has qemu-kvm although they don't use libvirt (in fact libvirt tighted to much to Linux specifics).
I'm kind of surprised to hear you say that. One of libvirt's goals is portability, so if it doesn't work on Solaris now, you should mention it on libvir-list, and I wouldn't expect getting it to work would be that troublesome. Personally I don't use Solaris, but if it's something you want, you should ask and see what other people's experience is. Dave
If vdsm whould interact with qemu-kvm without libvirt it would open a way to have Solaris hosts in ovirt-engine.
libvirt is another abstraction after vdsm layer, or if vdsm could use "plugins" to interact with qemu-kvm (libvirt, "native", solaris-style), it could use current mode, bypass libvirt and use solaris tools to talk to their qemu-kvm.
In the old days, vdsm used to work with qemu processes directly. We moved to be using libvirt's abstraction in order to gain then-new qmp code "for free", and to make it easier for 3rd party applications poll oVirt VMs over the libvirt api. We also use the libvirt dom xml as an API for vdsm extension hooks.
Beyond that, there are a few Linuxisms in Vdsm itself. I would first want to see it ported to non-Fedora-flavor Linuxes (did someone say Ubuntu?), and only later to Solaris.
Dan. _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Thu, 10 Jan 2013 09:29:58 -0500 Dave Allan <dallan@redhat.com> wrote:
On Thu, Jan 10, 2013 at 11:51:56AM +0200, Dan Kenigsberg wrote:
On Tue, Jan 08, 2013 at 10:02:05AM +0100, Jiri Belka wrote:
Hi,
as you know Solaris (Open Indiana) has qemu-kvm although they don't use libvirt (in fact libvirt tighted to much to Linux specifics).
I'm kind of surprised to hear you say that. One of libvirt's goals is portability, so if it doesn't work on Solaris now, you should mention it on libvir-list, and I wouldn't expect getting it to work would be that troublesome. Personally I don't use Solaris, but if it's something you want, you should ask and see what other people's experience is.
OK, I thought it just client is portable, I will need to read more ;) jbelka
participants (3)
-
Dan Kenigsberg -
Dave Allan -
Jiri Belka