From: yuxh <yuxinghai@cn.fujitsu.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-img problem when create a file larger than fs's size
Date: Thu, 09 May 2013 16:22:11 +0800 [thread overview]
Message-ID: <518B5CB3.70201@cn.fujitsu.com> (raw)
In-Reply-To: <20130509074407.GG1074@stefanha-thinkpad.redhat.com>
On 05/09/2013 03:44 PM, Stefan Hajnoczi wrote:
> On Wed, May 08, 2013 at 01:18:17PM +0800, yuxh wrote:
>> I have to consult you a qemu-img's problem.
>>
>> Is this reasonable to create a file which is larger than the
>> available size of the fs by qemu-img cmd ?
>>
>> When I use qemu-img create a file which is larger than the available
>> size of the fs, the creation is completed succesfully.
>>
>> However when I use this file in guest as a guest's disk, and write
>> beyond the size the host file can provides, the guest was paused by
>> qemu-kvm or libvirt and was in maybe a infinite circle where the
>> guest just can't be used except I detach the disk from guest or
>> destroy the guest.
>
> You can change the ENOSPC policy with -drive werror=,rerror=. See the
> QEMU man page.
>
> The default behavior is to pause the guest so the host admin can free up
> or add space. Then the guest can be continued - this will retry the
> I/O.
>
> But you can also tell QEMU to pass the error through to the guest using
> the -drive werror=,rerror= options.
>
> Stefan
>
>
Oh, understand now.
Thank you so much for your explanation.
Yu
prev parent reply other threads:[~2013-05-09 8:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 5:18 [Qemu-devel] qemu-img problem when create a file larger than fs's size yuxh
2013-05-08 6:36 ` Fam Zheng
2013-05-08 7:34 ` yuxh
2013-05-08 8:20 ` Fam Zheng
2013-05-08 8:36 ` yuxh
2013-05-09 7:44 ` Stefan Hajnoczi
2013-05-09 8:22 ` yuxh [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=518B5CB3.70201@cn.fujitsu.com \
--to=yuxinghai@cn.fujitsu.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.