From: "Andreas Färber" <afaerber@suse.de>
To: Neil Skrypuch <neil@tembosocial.com>, qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] Live migration results in non-working virtio-net device (sometimes)
Date: Wed, 05 Mar 2014 16:59:24 +0100 [thread overview]
Message-ID: <531749DC.6090402@suse.de> (raw)
In-Reply-To: <1729828.TVLplOUlZS@skrypuch>
Am 30.01.2014 19:23, schrieb Neil Skrypuch:
> First, let me briefly outline the way we use live migration, as it is probably
> not typical. We use live migration (with block migration) to make backups of
> VMs with zero downtime. The basic process goes like this:
>
> 1) migrate src VM -> dest VM
> 2) migration completes
> 3) cont src VM
> 4) gracefully shut down dest VM
> 5) dest VM's disk image is now a valid backup
>
> In general, this works very well.
>
> Up until now we have been using qemu-kvm 1.1.2 and have not had any issues
> with the above process. I am now attempting to upgrade us to a newer version
> of qemu, but all newer versions I've tried occasionally result in the virtio-
> net device ceasing to function on the src VM after step 3.
While I don't know this particular symptom, I can definitely tell you
that migrating from qemu-kvm to qemu is bound to fail unless you enable
at least a version_id change in piix4.c, possibly also in kvmvapic.c.
Such errors would lead to migration not successfully completing though,
with cryptic error on the dest side.
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2014-03-05 16:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 18:23 [Qemu-devel] Live migration results in non-working virtio-net device (sometimes) Neil Skrypuch
2014-02-28 20:14 ` Neil Skrypuch
2014-03-01 2:34 ` 陈梁
2014-03-03 20:15 ` Neil Skrypuch
2014-03-05 15:59 ` Andreas Färber [this message]
2014-03-05 18:32 ` Neil Skrypuch
2014-03-08 15:02 ` Stefan Hajnoczi
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=531749DC.6090402@suse.de \
--to=afaerber@suse.de \
--cc=neil@tembosocial.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@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).