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?
For general use perhaps, device assignment might need another cycle. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
