[libvirt] [Qemu-devel] Re: Supporting hypervisor specific APIs in libvirt

Avi Kivity avi at redhat.com
Fri Mar 26 16:01:10 UTC 2010

On 03/25/2010 10:18 AM, Alexander Graf wrote:
>> libqemu.so would be a C API.  C is not the first choice for writing GUIs or management applications.  So it would need to be further wrapped.
>> We also need to allow qemu to control the display directly, without going through vnc.
> For the current functionality I tend to disagree. All that we need is an shm vnc extension that allows the GUI and qemu to not send image data over the wire, but only the dirtyness information.

It still means an extra copy.  I don't think we want to share the guest 
framebuffer (it includes offscreen bitmaps), so we'll need to copy it 
somewhere else.  It's even worse with qxl/spice where there is no 

> As soon as we get to 3D things might start to look different.

Very different.

Do not meddle in the internals of kernels, for they are subtle and quick to panic.

More information about the libvir-list mailing list