qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] KVM call minutes for Oct 19


From: Dor Laor
Subject: Re: [Qemu-devel] KVM call minutes for Oct 19
Date: Wed, 20 Oct 2010 14:16:23 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.9) Gecko/20100921 Fedora/3.1.4-1.fc13 Lightning/1.0b3pre Thunderbird/3.1.4 ThunderBrowse/3.3.2

On 10/20/2010 10:21 AM, Alexander Graf wrote:

On 19.10.2010, at 17:14, Chris Wright wrote:

0.13.X -stable
- Anthony will send note to qemu-devel on this
- move 0.13.X -stable to a separate tree
- driven independently of main qemu tree
- challenge is always in the porting and testing of backported fixes
- looking for volunteers

0.14
- would like to do this before end of the year
- 0.13 forked off a while back (~July),
- 0.14 features
  - QMP stabilized
    - 0.13.0 ->  0.14 QMP
    - hard attempt not to break compatibility
    - new commands, rework, async, human monitor passthrough
    - goal getting to libvirt not needing human monitor at all
    - QMP KVM autotest test suite submitted
- in-kernel apic, tpr patching still outstanding
- QED coroutine concurrency

Would it be realistic to declare deprecating the qemu-kvm fork for 0.14 as goal?

Live snapshots
- merge snapshot?
  - already supported, question about mgmt of snapshot chain
- integrate with fsfreeze (and windows alternative)

Guest Agent
- have one coming RSN (poke Anthony for details)

Would there be a chance to have a single agent for everyone, so that we 
actually form a Qemu agent instead of a dozen individual ones? I'm mainly 
thinking Spice here.

More important than the number of instances is the usage of common framework. Here is the link to the Matahari project:
https://fedorahosted.org/matahari/wiki/API





Alex






reply via email to

[Prev in Thread] Current Thread [Next in Thread]