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

Luiz Capitulino lcapitulino at redhat.com
Wed Mar 24 16:42:50 UTC 2010

On Wed, 24 Mar 2010 12:42:16 +0200
Avi Kivity <avi at redhat.com> wrote:

> So, at best qemud is a toy for people who are annoyed by libvirt.

 Is the reason for doing this in qemu because libvirt is annoying? I don't see
how adding yet another layer/daemon is going to improve ours and user's life
(the same applies for libqemu).

 If I got it right, there were two complaints from the kvm-devel flamewar:

1. Qemu has usability problems
2. There's no way an external tool can get /proc/kallsyms info from Qemu

 I don't see how libqemu can help with 1) and having qemud doesn't seem
the best solution for 2) either.

 Still talking about 2), what's wrong in getting the PID or having a QMP
connection in a well known location as suggested by Anthony?

More information about the libvir-list mailing list