From: Kevin Wolf <kwolf@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] vmdk: Fix format specific information (create type) for streamOptimized
Date: Thu, 23 Jan 2014 15:42:32 +0100 [thread overview]
Message-ID: <20140123144232.GF8474@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <1390461052-6840-1-git-send-email-famz@redhat.com>
Am 23.01.2014 um 08:10 hat Fam Zheng geschrieben:
> Previously the field is wrong:
>
> $ ./qemu-img create -f vmdk -o subformat=streamOptimized /tmp/a.vmdk 1G
>
> $ ./qemu-img info /tmp/a.vmdk
> image: /tmp/a.vmdk
> file format: vmdk
> virtual size: 1.0G (1073741824 bytes)
> disk size: 12K
> Format specific information:
> cid: 1390460459
> parent cid: 4294967295
> >>> create type: monolithicSparse
> <snip>
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
Thanks, applied to the block branch.
By the way, I tried converting a raw image to streamOptimised and got
this:
qemu-img: Could not write to allocated cluster for streamOptimized
qemu-img: error while writing sector 63: Input/output error
The problem seems to be that qemu-img tries to be clever and doesn't
write out sparse parts, which breaks up the first cluster into multiple
write requests. Adding -S 64 makes it work. Should we change something
to get a working default?
Kevin
next prev parent reply other threads:[~2014-01-23 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 7:10 [Qemu-devel] [PATCH] vmdk: Fix format specific information (create type) for streamOptimized Fam Zheng
2014-01-23 14:42 ` Kevin Wolf [this message]
2014-01-24 7:51 ` Fam Zheng
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=20140123144232.GF8474@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 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).