qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kwolf@redhat.com, quintela@redhat.com, qemu-devel@nongnu.org,
	lcapitulino@redhat.com, laine@redhat.com
Subject: Re: [Qemu-devel] [RFC 0/7] Optional toplevel sections
Date: Mon, 20 Oct 2014 15:59:57 +0100	[thread overview]
Message-ID: <20141020145956.GL2517@work-vm> (raw)
In-Reply-To: <54411C74.2010407@redhat.com>

* Paolo Bonzini (pbonzini@redhat.com) wrote:
> Il 15/10/2014 17:59, Juan Quintela ha scritto:
> > My idea here is that, if you don't use libvirt, you just start without
> > -S.
> 
> If you don't use libvirt or any other QEMU management layer, you're not
> going to do migration except for debugging purposes.  There's just too
> much state going on to be able to do it reliably.

I'm not sure that's entirely true - while I agree that most users will
use libvirt, migration with shared disk is pretty easy; the only thing
that you need to do is bring up the tap on the destination, and I'm
not sure libvirt gets the timing ideal for it.

Dave


> 
> > If you use libvirt, and you *don't* need to do anything special to run
> > after migration, you shouldn't use -S.
> 
> Is this a real requirement, or just "it sounds nicer that way"?  How
> much time really passes between the end of migration and the issuing of
> the "-cont" command?
> 
> And the $1,000,000 questionL.aAre you _absolutely_ sure that an
> automatic restart is entirely robust against a failure of the connection
> between the two libvirtd instances?  Could you end up with the VM
> running on two hosts?  Using -S gets QEMU completely out of the
> equation, which is nice.
> 
> By the way, some of the states (I can think of io-error, guest-panicked,
> watchdog) can be detected on the destination and restored.  Migrating a
> machine with io-error state is definitely something that you want to do
> no matter what versions of QEMU you have.  It may be the only way to
> recover for a network partition like this:
> 
>            DISK
>           /    \
>          |      \
>          X       |
>          |       |
>         SRC --- DEST
> 
> (not impossible: e.g. the SRC->DISK is fibre channel, but the SRC->DEST
> link is Ethernet.  Or you have a replicated disk setup, some daemon
> fails in SRC's replica but not DEST's).
> 
> > And I would emit an event saying
> > "migration was finished".
> 
> The event should be emitted nevertheless. :)
> 
> Paolo
> 
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  reply	other threads:[~2014-10-20 15:00 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-15  7:55 [Qemu-devel] [RFC 0/7] Optional toplevel sections Juan Quintela
2014-10-15  7:55 ` [Qemu-devel] [PATCH 1/7] migration: Create optional sections Juan Quintela
2014-10-15  7:55 ` [Qemu-devel] [PATCH 2/7] runstate: Add runstate store Juan Quintela
2014-10-20 10:24   ` Dr. David Alan Gilbert
2014-10-20 10:52     ` Juan Quintela
2014-10-20 15:18       ` Eric Blake
2014-10-22 11:18         ` Dr. David Alan Gilbert
2014-10-22 11:40           ` Markus Armbruster
2014-10-22 15:52             ` Eric Blake
2014-10-15  7:55 ` [Qemu-devel] [PATCH 3/7] runstate: create runstate_index function Juan Quintela
2014-10-15  7:55 ` [Qemu-devel] [PATCH 4/7] runstate: migration allows more transitions now Juan Quintela
2014-10-15 14:42   ` Eric Blake
2014-10-15 15:50     ` Juan Quintela
2014-11-03 12:46   ` Amit Shah
2014-10-15  7:55 ` [Qemu-devel] [PATCH 5/7] migration: create now section to store global state Juan Quintela
2014-10-20 10:52   ` Dr. David Alan Gilbert
2014-10-20 11:11   ` Kevin Wolf
2014-10-15  7:55 ` [Qemu-devel] [PATCH 6/7] global_state: Make section optional Juan Quintela
2014-10-15  7:55 ` [Qemu-devel] [PATCH 7/7] vmstate: Create optional sections Juan Quintela
2014-10-15 14:45   ` Eric Blake
2014-10-15 14:57 ` [Qemu-devel] [RFC 0/7] Optional toplevel sections Eric Blake
2014-10-15 15:59   ` Juan Quintela
2014-10-15 16:37     ` Eric Blake
2014-10-17 13:41     ` Paolo Bonzini
2014-10-20 14:59       ` Dr. David Alan Gilbert [this message]
2014-10-20 11:29 ` Kevin Wolf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141020145956.GL2517@work-vm \
    --to=dgilbert@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=laine@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).