Re: [libvirt] [PATCH v2 2/6] virsh: add support for VIR_DOMAIN_CONSOLE_FORCE flag

2011-12-14 Thread Peter Krempa
Dňa 14.12.2011 1:14, Eric Blake wrote / napísal(a): Hmm, wondering about back-compat - what happens if we are talking to an older libvirt that does not know VIR_DOMAIN_CONSOLE_FORCE, but also which does not prevent multiple connections when flags==0? At first glance, it looks like we're stuck

Re: [libvirt] [PATCH v2 2/6] virsh: add support for VIR_DOMAIN_CONSOLE_FORCE flag

2011-12-14 Thread Eric Blake
On 12/14/2011 01:46 AM, Peter Krempa wrote: But maybe we could add a new API, to allow probing whether a console is in use. If the API exists, then we know whether the console is in use (and we also know whether --force will work); if the API does not exist, the we know we are talking to an

Re: [libvirt] [PATCH v2 2/6] virsh: add support for VIR_DOMAIN_CONSOLE_FORCE flag

2011-12-13 Thread Eric Blake
On 12/07/2011 11:08 AM, Peter Krempa wrote: This patch adds support for the newly introduced VIR_DOMAIN_CONSOLE s/$/_FORCE/ flag. The console command now has an optional parameter --force that specifies that the user wants to forcibly interrupt an ongoing console session and create a new

[libvirt] [PATCH v2 2/6] virsh: add support for VIR_DOMAIN_CONSOLE_FORCE flag

2011-12-07 Thread Peter Krempa
This patch adds support for the newly introduced VIR_DOMAIN_CONSOLE flag. The console command now has an optional parameter --force that specifies that the user wants to forcibly interrupt an ongoing console session and create a new one. The behaviour to this point was, that the daemon openend two