Eric Blake writes:
> On 07/29/2014 12:12 AM, Markus Armbruster wrote:
>
>>> Libvirt probably won't use it for normal guests (we don't want to kill
>>> qemu just because the monitor disconnects), but does have the notion of
>>> an autodestroy guest where it might be useful (we WANT the guest to go
On 07/29/2014 12:12 AM, Markus Armbruster wrote:
>> Libvirt probably won't use it for normal guests (we don't want to kill
>> qemu just because the monitor disconnects), but does have the notion of
>> an autodestroy guest where it might be useful (we WANT the guest to go
>> away if libvirtd dies e
Eric Blake writes:
> On 07/25/2014 02:12 AM, Markus Armbruster wrote:
>> Stefan Hajnoczi writes:
>>
>>> When QEMU is executed as part of a test case or from a script, it is
>>> usually desirable to exit if the parent process terminates. This
>>> ensures that "leaked" QEMU processes do not cont
On 07/25/2014 02:12 AM, Markus Armbruster wrote:
> Stefan Hajnoczi writes:
>
>> When QEMU is executed as part of a test case or from a script, it is
>> usually desirable to exit if the parent process terminates. This
>> ensures that "leaked" QEMU processes do not continue consuming resources
>>
On Fri, Jul 25, 2014 at 9:12 AM, Markus Armbruster wrote:
> Stefan Hajnoczi writes:
>
>> When QEMU is executed as part of a test case or from a script, it is
>> usually desirable to exit if the parent process terminates. This
>> ensures that "leaked" QEMU processes do not continue consuming reso
Stefan Hajnoczi writes:
> When QEMU is executed as part of a test case or from a script, it is
> usually desirable to exit if the parent process terminates. This
> ensures that "leaked" QEMU processes do not continue consuming resources
> after their parent has died.
>
> This patch adds the -cha
When QEMU is executed as part of a test case or from a script, it is
usually desirable to exit if the parent process terminates. This
ensures that "leaked" QEMU processes do not continue consuming resources
after their parent has died.
This patch adds the -chardev exit-on-eof option causing socke
