From: Stefan Hajnoczi <stefanha@gmail.com>
To: David Weber <wb@munzinger.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Stange problems with raw_co_get_block_status lseek path
Date: Wed, 3 Jun 2015 15:06:58 +0100 [thread overview]
Message-ID: <20150603140658.GD20862@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <DIIE.0000003C00056111@pegasus.munzinger.de>
[-- Attachment #1: Type: text/plain, Size: 561 bytes --]
On Tue, Jun 02, 2015 at 11:25:18AM +0000, David Weber wrote:
> I'm currently evaluating to switch our virtualization servers to a newer OS. This includes a switch from qemu 1.7 to 2.2 or 2.3.
> Our system heavily relies on big sparse images and drive_mirror. While testing, I experienced some problems with that combination.
> The strange thing is, that everything works flawlessly on my workstation but fails on my servers.
I replied to the second email you sent later. It sometimes takes a
while for emails to show up on the mailing list.
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-06-03 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 11:25 [Qemu-devel] Stange problems with raw_co_get_block_status lseek path David Weber
2015-06-03 14:06 ` Stefan Hajnoczi [this message]
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=20150603140658.GD20862@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=wb@munzinger.de \
/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).