On Sun, Jul 31, 2011 at 07:15:21PM -0500, Anthony Liguori wrote: > I think we've set the bar too low historically for introducing new > interfaces. I think Avi's new memory API is a good example of how we > should approach these things--do the vast majority of the thankless work up > front before initial merge.
Yes, that seems to work a bit better. So how will we sort out and finalized the vmstate bits, QMP, and making sure we have one sort of error reporting? For vmstate I'd agree to Dor and principle and just drop support for old-style load/save functions after converting everything that matters to vmstate.
