KVM call minutes for Oct 19

Chris Wright
2010-10-19T15:14:44Z

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

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)
- works over legacy or virtio serial
- simple RPC mechanism between host/guest
- allows host initiated reboot, for example
- can be place to do host driven snahpshot too
- Matahari?
- can deal w/ block/net/UUID/cluster/etc
- too heavyweight?
- be sure to coordinate

threadlets and concurrency model (for virtfs)
- prior discussions
- 1st model: http://www.mail-archive.com/qemu-devel@nongnu.org/msg43838.html
- 2nd model: http://www.mail-archive.com/qemu-devel@nongnu.org/msg43921.html
- threadlets: http://www.mail-archive.com/qemu-devel@nongnu.org/msg43842.html
- please review and continue discussion on the list
- concurrency model questions
- async state machine is easiest to merge right now
- future work could push it to cooperative coroutines

usb-ccid (aka external device modules such as vtpm)
- isolating device specific interface from qemu device internals is hard
- usb-ccid description...(go read the patches)
- technical complexity with external emulation
- version skew
- live migration
- same complextiy as full plug-in