On 11/15/2010 08:52 AM, Juan Quintela wrote:
"Michael S. Tsirkin"<m...@redhat.com> wrote:
There's no reason for tap to run when VM is stopped.
If we let it, it confuses the bridge on TX
and corrupts DMA memory on RX.
Signed-off-by: Michael S. Tsirkin<m...@redhat.com>
once here, what handlers make sense to run while stopped?
/me can think of the normal console, non live migration, loadvm and not
much more. Perhaps it is easier to just move the other way around?
I'm not sure I concur that this is really a problem.
Semantically, I don't think that stop has to imply that the guest memory
no longer changes.
Regards,
Anthony Liguori
Later, Juan.
