On Tue, Mar 23, 2010 at 03:00:28AM +0700, Antoine Martin wrote: > On 03/23/2010 02:15 AM, Anthony Liguori wrote: > >On 03/22/2010 12:55 PM, Avi Kivity wrote: > >>>Lets look at the ${HOME}/.qemu/qmp/ enumeration method suggested by > >>>Anthony. > >>>There's numerous ways that this can break: > >> > >>I don't like it either. We have libvirt for enumerating guests. > > > >We're stuck in a rut with libvirt and I think a lot of the > >dissatisfaction with qemu is rooted in that. It's not libvirt that's > >the probably, but the relationship between qemu and libvirt. > +1 > The obvious reason why so many people still use shell scripts rather > than libvirt is because if it just doesn't provide what they need. > Every time I've looked at it (and I've been looking for a better > solution for many years), it seems that it would have provided most of > the things I needed, but the remaining bits were unsolvable. If you happen to remember what missing features prevented you choosing libvirt, that would be invaluable information for us, to see if there are quick wins that will help out. We got very useful feedback when recently asking people this same question http://rwmj.wordpress.com/2010/01/07/quick-quiz-what-stops-you-from-using-libvirt/ Allowing arbitrary passthrough of QEMU commands/args will solve some of these issues, but certainly far from solving all of them. eg guest cut+ paste, host side control of guest screen resolution, easier x509/TLS configuration for remote management, soft reboot, Windows desktop support for virt-manager, host network interface management/setup, etc Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html