From: "Daniel P. Berrange" <berrange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: QEMU / KVM support in libvirt & virt-manager
Date: Sun, 25 Feb 2007 15:50:25 +0000 [thread overview]
Message-ID: <20070225155025.GB4132@redhat.com> (raw)
In-Reply-To: <45E11F8A.8080306-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
On Sun, Feb 25, 2007 at 07:32:58AM +0200, Avi Kivity wrote:
> Daniel P. Berrange wrote:
> >FYI, as of libvirt 0.2.0 and virt-manager 0.3.1 there is now
> >(experimental!)
> >support for managing virtual machines running under QEMU or KVM
> >virtualization
> >platforms, as well as the existing Xen support.
> >
> >
>
> Great; as I see it hit FC6-updates I'll give it a shot.
>
> One thing I saw is that it pulls in Xen as part of the dependencies;
> perhaps a libvirt-xen and libvirt-kvm subpackage split is called for?
Yeah, we've not figured out exactly how to address that dependancy
issue yet - the libvirt.so has to link to libxenstore as part of the
Xen driver, so even if you only want to manage QEMU instances we still
end up pulling in Xen. We're certainly going to make it possible to
turn off the Xen stuff at compile time. Not clear how we'd address the
RPM dep issue though because the Fedora builds of libvirt will include
both Xen & QEMU support. Perhaps we'll have to try a dlopen() approach.
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-02-25 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 22:16 QEMU / KVM support in libvirt & virt-manager Daniel P. Berrange
[not found] ` <20070222221654.GR22473-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2007-02-25 5:32 ` Avi Kivity
[not found] ` <45E11F8A.8080306-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-02-25 8:34 ` Avi Kivity
[not found] ` <45E14A07.6090207-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-02-25 16:29 ` Daniel P. Berrange
[not found] ` <20070225162945.GA13570-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2007-02-27 15:20 ` Avi Kivity
[not found] ` <45E44C3B.3010305-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-02-27 15:31 ` Daniel P. Berrange
2007-02-25 15:50 ` Daniel P. Berrange [this message]
[not found] ` <20070225155025.GB4132-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2007-02-25 16:48 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070225155025.GB4132@redhat.com \
--to=berrange-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox