Daniel P. Berrange wrote:
>> Multiple monitor instances would be very useful anyway.
>>
>> Right now there is no way to use the monitor for libvirt-managed qemu
>> instances because libvirt uses the monitor. Being able to both use
>> libvirt *and* have a monitor prompt to type commands would be great.
>
> I disagree - that means you'll no longer be able to trust what libvirt
> tells you about the VM, and libvirt won't have a guarenteed consistent
> view of the VM's state because things will be changed behind its back.
It is *not* the only purpose of the monitor to confuse libvirt. The
whole 'info <foo>' command family is very useful for development and
debugging purposes and it will not interfere at all with libvirt.
I can't stand your attitude to refuse any feature just because you fear
users might abuse it. That applies to almost any feature which makes
life easier for developers. Which in turn means using libvirt for
development is either a bit complicated or impossible.
cheers,
 Gerd
-- 
http://kraxel.fedorapeople.org/xenner/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel