From: Stefan Hajnoczi <stefanha@gmail.com>
To: Bug 1422307 <1422307@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1422307] Re: qemu-nbd corrupts files
Date: Wed, 18 Feb 2015 13:58:16 +0000 [thread overview]
Message-ID: <20150218135816.GG7629@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <20150218091157.20997.96270.malone@wampee.canonical.com>
[-- Attachment #1: Type: text/plain, Size: 407 bytes --]
On Wed, Feb 18, 2015 at 09:11:57AM -0000, Pierre Schweitzer wrote:
> Does that mean it can also affect VMs running with VDI disk(s)?
Yes, that's what Max's example showed.
Note that only raw, qcow2, and qed support in QEMU is designed for
running guests. The other formats like vmdk and vdi are mainly for
qemu-img convert and will perform poorly because they don't handle
parallel I/O requests.
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-02-18 13:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 10:05 [Qemu-devel] [Bug 1422307] [NEW] qemu-nbd corrupts files Pierre Schweitzer
2015-02-17 14:50 ` [Qemu-devel] [Bug 1422307] " Max Reitz
2015-02-17 14:50 ` Max Reitz
2015-02-17 17:18 ` Max Reitz
2015-02-17 18:22 ` Max Reitz
2015-02-17 19:21 ` Max Reitz
2015-02-17 21:25 ` Max Reitz
2015-02-18 9:11 ` Pierre Schweitzer
2015-02-18 13:58 ` Stefan Hajnoczi [this message]
2015-02-19 17:48 ` Pierre Schweitzer
2015-02-23 10:42 ` Stefan Hajnoczi
2015-04-09 8:00 ` Pierre Schweitzer
2015-07-06 11:40 ` Nicolas Rüegg
2015-07-06 13:46 ` Max Reitz
2015-07-06 14:46 ` Pierre Schweitzer
2015-08-17 10:29 ` Robie Basak
2015-08-17 10:30 ` Robie Basak
2015-08-19 7:28 ` Pierre Schweitzer
2015-08-26 16:49 ` Serge Hallyn
2015-08-26 21:32 ` Serge Hallyn
2015-08-27 22:41 ` Brian Murray
2015-08-28 6:29 ` Pierre Schweitzer
2015-08-28 6:42 ` Pierre Schweitzer
2015-09-09 1:28 ` Launchpad Bug Tracker
2015-09-09 1:28 ` [Qemu-devel] [Bug 1422307] Update Released Chris Halse Rogers
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=20150218135816.GG7629@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=1422307@bugs.launchpad.net \
--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).