From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] migration question: disk images on nfs server
Date: Fri, 07 Feb 2014 15:35:36 +1100 [thread overview]
Message-ID: <52F46298.8020602@ozlabs.ru> (raw)
Hi!
I have yet another problem with migration. Or NFS.
There is one NFS server and 2 test POWER8 machines. There is a shared NFS
folder on the server, mounted to both test hosts. There is an qcow2 image
(abc.qcow2) in that shared folder.
We start a guest with this abc.qcow2 on the test machine #1. And start
another guest on the test machine #2 with "-incoming ..." and same abc.qcow2.
Now we start migration. In most cases it goes fine. But if we put some load
on machine #1, the destination guest sometime crashes.
I blame out-of-sync NFS on the test machines. I looked a bit further in
QEMU and could not find a spot where it would fflush(abc.qcow2) or close it
or do any other sync so it is up to the host NFS mountpoint to decide when
to sync and it definitely does not get a clue when to do this.
I do not really understand why the abc.qcow2 image is still open, should
not it be closed after migration succeeded?
What do I miss here? Should we switch from NFS to GlusterFS (is it always
syncronized)? Or if we want NFS, should we just boot our guests with
"root=/dev/nfs ip=dhcp nfsroot=..." and avoid using disk images in network
disks? Thanks!
--
Alexey
next reply other threads:[~2014-02-07 4:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 4:35 Alexey Kardashevskiy [this message]
2014-02-07 7:46 ` [Qemu-devel] migration question: disk images on nfs server Orit Wasserman
2014-02-07 9:41 ` Marcin Gibuła
2014-02-07 12:26 ` Paolo Bonzini
2014-02-07 12:10 ` Alexey Kardashevskiy
2014-02-07 12:47 ` Orit Wasserman
2014-02-07 12:54 ` Marcin Gibuła
2014-02-07 13:36 ` Orit Wasserman
2014-02-07 13:44 ` Marcin Gibuła
2014-02-07 13:57 ` Orit Wasserman
2014-02-08 8:30 ` 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=52F46298.8020602@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=qemu-devel@nongnu.org \
/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).