Avi Kivity wrote:
I'm not sure I understand your questions. Multiple monitor
sessions are
like multiple shell sessions. I don't think a control program should
use more than one session, but it should allow a developer to connect to
issue 'info registers' and 'x/20i' commands. Of course if a developer
issues 'quit' or a hotunplug command, things will break.
In most cases I think commands like 'stop' or a hotunplug command
shouldn't break libvirt or other control program. As long as there's
a way for libvirt to query the current hotplug state and be notified
of changes, why shouldn't it behave much the same as if you asked
libvirt to do do the same action itself?
-- Jamie