From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NzAer-0007nk-B5
	for qemu-devel@nongnu.org; Tue, 06 Apr 2010 11:25:41 -0400
Received: from [140.186.70.92] (port=56709 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NzAeo-0006rP-8E
	for qemu-devel@nongnu.org; Tue, 06 Apr 2010 11:25:41 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <chrisw@redhat.com>) id 1NzATZ-0003zt-UC
	for qemu-devel@nongnu.org; Tue, 06 Apr 2010 11:14:04 -0400
Received: from mx1.redhat.com ([209.132.183.28]:36427)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <chrisw@redhat.com>) id 1NzATZ-0003zm-Kt
	for qemu-devel@nongnu.org; Tue, 06 Apr 2010 11:14:01 -0400
Date: Tue, 6 Apr 2010 08:13:58 -0700
From: Chris Wright <chrisw@redhat.com>
Message-ID: <20100406151358.GC7088@x200.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Subject: [Qemu-devel] KVM call minutes for Apr 6
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: kvm@vger.kernel.org
Cc: qemu-devel@nongnu.org

Management stack again
- qemud?
- external mgmt stack, qemu/kvm devs less inclined to care
  - "Oh, you're using virsh, try #virt on OFTC"
- standard libvirt issues
  - concern about speed of adopting kvm features
  - complicated, XML hard to understand
  - being slowed by hv agnositc
  - ...
  - but...clearly have done a lot of work and widely used/deployed/etc...
- libvirt is still useful, so need to play well w/ libvirt
- qemud
  - qemu registers
  - have enumeration
  - have access to all qemu features (QMP based)
  - runs privileged, can deal w/ bridge, tap setup
  - really good UI magically appears </sarcasm>
  - regressions (we'd lose these w/ qemud):
    - sVirt
    - networking
    - storage pools, etc
    - device assignment
    - hotplug
    - large pages
    - cgroups
    - stable mgmt ABI
  - what's needed global/privileged?
    - guest enumeration
    - network setup
    - device hotplug
  - need good single VM UI
    - but...as soon as you want 2 VMs, or 2 hosts...
    - no need to reinvent the wheel
- qemu project push features up towards mgmt stack, but doesn't make
  those features exist in mgmt stack
- automated interface creation (remove barrier to adding libvirt features)
- QtEmu as example of nice interface that suffered because programming to qemu cli is too hard
- libvirt has made a lot of effort, nobody is discouting that, what's un
- strong agreement is that libvirt is needed long term
- we should focus on making qemu easy to manage not on writing mgmt tools
  - qmp + libvirt
  - define requirements for layering
    - needs for global scope and privilege requirements