|
From: | Anthony Liguori |
Subject: | Re: [Qemu-devel] [RFC] New Migration Protocol using Visitor Interface |
Date: | Mon, 03 Oct 2011 11:05:02 -0500 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.21) Gecko/20110831 Lightning/1.0b2 Thunderbird/3.1.13 |
On 10/03/2011 10:45 AM, Michael S. Tsirkin wrote:
BTW, putting this info properly into migration stats would probably be pretty useful. Regards, Anthony LiguoriProblem is adding anything to monitor makes me worry about future compatibility so much I usually just give up. IMO we really need a namespace for in-development experimental commands, like "unsupported-XXX", this would belong.
Or just make all of QMP unsupported across any given version. I'm not kidding about that actually.
If we document what the protocol is for any given version, then a layer like libvirt can deal with providing a consistent interface.
I often wonder who we're trying to preserve compatibility for. Part of libvirt's mission statement is providing a stable API so why not leverage that mission and get us out of the compatibility business.
Regards, Anthony Liguori
[Prev in Thread] | Current Thread | [Next in Thread] |