[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Re: [PATCH 04/22] savevm: do_loadvm(): Always resume th
From: |
Jamie Lokier |
Subject: |
Re: [Qemu-devel] Re: [PATCH 04/22] savevm: do_loadvm(): Always resume the VM |
Date: |
Wed, 21 Apr 2010 18:50:30 +0100 |
User-agent: |
Mutt/1.5.13 (2006-08-11) |
Juan Quintela wrote:
> Luiz Capitulino <address@hidden> wrote:
> > On Wed, 21 Apr 2010 15:28:16 +0200
> > Kevin Wolf <address@hidden> wrote:
> I tried a variation of this in the past, and was not a clear agreement.
>
> Basically, after a working migration to other host, you don't want to
> allow "cont" on the source node (it target has ever changed anything, it
> would give disk corruption).
This is not true if the target is using a copy of the disk.
Making copies is cheap on some hosts (Linux btrfs with it's COW features).
Forking a guest can be handy for testing things, starting from a known
run state. The only thing to get confused is networking because of
duplicate addresses, and there are host-side ways around that (Linux
network namespaces).
If I understand correctly, we can already do this by migrating to a
file and copying the files. There's no reason to block the live
equivalent, provided there is a way to copy the disk image when it's
quiesced.
So it's wrong to block "cont" on the source, but
"cont --I_know_what_I_am_doing" might be good advice :-)
> But my suggestion to disable "cont" after that got complains that people
> wanted a "I_know_what_I_am_doing_cont". (not the real syntax). Perhaps
> it is time to revise this issue?
-- Jamie
- [Qemu-devel] Re: [PATCH 04/22] savevm: do_loadvm(): Always resume the VM, (continued)
- [Qemu-devel] Re: [PATCH 04/22] savevm: do_loadvm(): Always resume the VM, Juan Quintela, 2010/04/21
- [Qemu-devel] Re: [PATCH 04/22] savevm: do_loadvm(): Always resume the VM, Luiz Capitulino, 2010/04/21
- [Qemu-devel] Re: [PATCH 04/22] savevm: do_loadvm(): Always resume the VM, Juan Quintela, 2010/04/21
- [Qemu-devel] Re: [PATCH 04/22] savevm: do_loadvm(): Always resume the VM, Kevin Wolf, 2010/04/21
- [Qemu-devel] Re: [PATCH 04/22] savevm: do_loadvm(): Always resume the VM, Luiz Capitulino, 2010/04/22
[Qemu-devel] Re: [PATCH 04/22] savevm: do_loadvm(): Always resume the VM, Kevin Wolf, 2010/04/21
[Qemu-devel] Re: [PATCH 04/22] savevm: do_loadvm(): Always resume the VM, Juan Quintela, 2010/04/21
Re: [Qemu-devel] Re: [PATCH 04/22] savevm: do_loadvm(): Always resume the VM,
Jamie Lokier <=
[Qemu-devel] [PATCH 09/22] QError: New QERR_SNAPSHOT_DELETE_FAILED, Luiz Capitulino, 2010/04/20
[Qemu-devel] [PATCH 12/22] QError: New QERR_STATEVM_SAVE_FAILED, Luiz Capitulino, 2010/04/20
[Qemu-devel] [PATCH 10/22] QError: New QERR_SNAPSHOT_CREATE_FAILED, Luiz Capitulino, 2010/04/20
[Qemu-devel] [PATCH 08/22] QError: New QERR_SNAPSHOT_NO_DEVICE, Luiz Capitulino, 2010/04/20
[Qemu-devel] [PATCH 11/22] QError: New QERR_SNAPSHOT_ACTIVATE_FAILED, Luiz Capitulino, 2010/04/20
[Qemu-devel] [PATCH 15/22] QError: New QERR_SNAPSHOT_NOT_FOUND, Luiz Capitulino, 2010/04/20
[Qemu-devel] [PATCH 14/22] QError: New QERR_DEVICE_NO_SNAPSHOT, Luiz Capitulino, 2010/04/20
[Qemu-devel] [PATCH 13/22] QError: New QERR_STATEVM_LOAD_FAILED, Luiz Capitulino, 2010/04/20