From: "Thomas Irlet" <iksiloev@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] bdrv_flush error handling
Date: Thu, 21 Feb 2008 08:10:48 +0100 [thread overview]
Message-ID: <9e72fb5d0802202310o72503b88q99170bd96227fba3@mail.gmail.com> (raw)
In-Reply-To: <200802201355.48502.rickv@hobi.com>
[-- Attachment #1: Type: text/plain, Size: 533 bytes --]
Sometimes the guest intentionally seeks the error. Example?
TrueCrypt 5.0 supports encryption of the full system disk. To get the real
size of the disk, the truecrypt driver queries the number of blocks of the
disk, but then tries to read after the last block, until it gets an error.
Qemu hangs in this operation. So, for me, the blockdriver has to give the
errors back to the guest (in this case, reading behind eof). In no cases,
qemu should die because of that.
Tom
PS: I had to patch truecrypt because of this qemu feature.
[-- Attachment #2: Type: text/html, Size: 559 bytes --]
next prev parent reply other threads:[~2008-02-21 7:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 15:53 [Qemu-devel] [PATCH] bdrv_flush error handling Ian Jackson
2008-02-20 16:04 ` Daniel P. Berrange
2008-02-20 16:13 ` Ian Jackson
2008-02-20 16:19 ` Paul Brook
2008-02-20 16:23 ` Avi Kivity
2008-02-20 16:37 ` Ian Jackson
2008-02-20 16:46 ` Paul Brook
2008-02-20 16:53 ` Ian Jackson
2008-02-20 16:31 ` Jamie Lokier
2008-02-20 18:17 ` Paul Brook
2008-02-20 16:38 ` Jamie Lokier
2008-02-20 18:22 ` Daniel P. Berrange
2008-02-20 19:01 ` Anthony Liguori
2008-02-20 19:55 ` Rick Vernam
2008-02-21 7:10 ` Thomas Irlet [this message]
2008-02-21 17:19 ` Ben Taylor
2008-02-21 17:24 ` Daniel P. Berrange
2008-02-21 17:28 ` risc
2008-02-21 18:24 ` Daniel P. Berrange
2008-03-28 17:19 ` [Qemu-devel] " Ian Jackson
2008-04-26 15:15 ` andrzej zaborowski
2008-04-29 16:27 ` Ian Jackson
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=9e72fb5d0802202310o72503b88q99170bd96227fba3@mail.gmail.com \
--to=iksiloev@gmail.com \
--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).