|
| From: | Avi Kivity |
| Subject: | Re: [Qemu-devel] Supporting hypervisor specific APIs in libvirt |
| Date: | Wed, 24 Mar 2010 06:53:02 +0200 |
| User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100301 Fedora/3.0.3-1.fc12 Thunderbird/3.0.3 |
On 03/23/2010 09:31 PM, Anthony Liguori wrote:
One problem is that this is libvirt version specific. For example, libvirt x doesn't support spice so we control that thorough qmp. But libvirt x+1 does support spice and now it gets confused about all the spice messages.That's only a problem if we only support a single QMP session. This is exactly why we need to support multiple QMP sessions (and do).
It's unrelated to the number of sessions. libvirt expects state that it manages in qemu not to change randomly. Users know that, so they will only manage non-libvirt state in their private session. But a new version of libvirt may expand its scope and start managing this area, leading to conflicts.
-- Do not meddle in the internals of kernels, for they are subtle and quick to panic.
| [Prev in Thread] | Current Thread | [Next in Thread] |