[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in li
From: |
Jamie Lokier |
Subject: |
Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in libvirt |
Date: |
Tue, 23 Mar 2010 23:22:30 +0000 |
User-agent: |
Mutt/1.5.13 (2006-08-11) |
Anthony Liguori wrote:
> On 03/23/2010 10:57 AM, Paul Brook wrote:
> >I thought the monitor protocol *was* our API. If not, why not?
>
> It is. But our API is missing key components like guest enumeration.
Is that simply enumerating running qemu instances, and asking each one
about things like it's name, VNC port, etc.?
Having each qemu publish itself through D-Bus or Avahi (to find the
list of running instances), and every info query go through the
monitor, would seem a clean solution to that.
Are there any other missing key components?
-- Jamie
- Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in libvirt, (continued)
- Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in libvirt, Daniel P. Berrange, 2010/03/23
- Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in libvirt, Anthony Liguori, 2010/03/23
- Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in libvirt, Avi Kivity, 2010/03/24
- Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in libvirt, Paul Brook, 2010/03/24
- Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in libvirt, Avi Kivity, 2010/03/24
- Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in libvirt, Paul Brook, 2010/03/24
- Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in libvirt, Markus Armbruster, 2010/03/24
- Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in libvirt, Paul Brook, 2010/03/24
- Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in libvirt,
Jamie Lokier <=
Re: [Qemu-devel] Supporting hypervisor specific APIs in libvirt, Avi Kivity, 2010/03/23