Re: [Qemu-devel] Signal handling and qcow2 image corruption

2008-03-05 Thread Avi Kivity
Anthony Liguori wrote: David Barrett wrote: I'm tracking down a image corruption issue and I'm curious if you can answer the following: 1) Is there any difference between sending a "TERM" signal to the QEMU process and typing "quit" at the monitor? Yes. Since QEMU is single threaded, when

Re: [Qemu-devel] Signal handling and qcow2 image corruption

2008-03-05 Thread David Barrett
Ah thanks, that makes a lot of sense. Unfortunately, -snapshot doesn't appear to work with -loadvm: any VM snapshots created outside of snapshot mode are suppressed, and any VM snapshots created inside snapshot mode disappear on close (even if you try to commit): = I have a snapshot VM na

Re: [Qemu-devel] Signal handling and qcow2 image corruption

2008-03-05 Thread Anthony Liguori
David Barrett wrote: I'm tracking down a image corruption issue and I'm curious if you can answer the following: 1) Is there any difference between sending a "TERM" signal to the QEMU process and typing "quit" at the monitor? Yes. Since QEMU is single threaded, when you issue a quit, you kn

[Qemu-devel] Signal handling and qcow2 image corruption

2008-03-05 Thread David Barrett
I'm tracking down a image corruption issue and I'm curious if you can answer the following: 1) Is there any difference between sending a "TERM" signal to the QEMU process and typing "quit" at the monitor? 2) Will sending TERM corrupt the 'gcow2' image (in ways other than normal guest OS dirt