From: Jeff Cody <jcody@redhat.com>
To: "Lokesha, Amulya" <Amulya.Lokesha@emc.com>
Cc: "kwolf@redhat.com" <kwolf@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"stefanha@redhat.com" <stefanha@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 4/4] block: vhdx - set .bdrv_has_zero_init to bdrv_has_zero_init_1
Date: Fri, 12 Dec 2014 10:17:42 -0500 [thread overview]
Message-ID: <20141212151742.GA15426@localhost.localdomain> (raw)
In-Reply-To: <E290E274B295904D9D81F0BC84559D0B65D664166E@MX10A.corp.emc.com>
On Fri, Dec 12, 2014 at 09:43:16AM -0500, Lokesha, Amulya wrote:
> Hi Max,
>
>
Please reply in-line, it makes it easier to follow technical
discussions - thanks :)
>
> We applied all the 5 patches from the mail chain I got since the last
> week. Please find attached the patches used by us.
>
> We were unable to apply the patch3 as it failed with the following error
>
>
>
> # patch -p1 < patch3
>
> patching file block/vhdx.c
>
> patch: **** malformed patch at line 17: error_setg_errno(errp,
> EINVAL, "Image size too large; max of 64TB"); @@ -1936,7 +1936,9 @@ static
> QemuOptsList vhdx_create_opts = {
>
>
It looks like however you saved the patch file, it was corrupted.
Looking at your attached patch 3, it split line 9 across 2 lines.
Your patch also has whitespace differences from the patch I sent.
You also attached 5 patches - Why are you using patch 0? You should
only be applying patches 1-4. This should not be causing any actual
issues, however.
Are you using git for your qemu version? If so, 'git am' is the
preferred method of applying the patches - just save each of the patch
emails (the whole email should be fine), and run 'git am' on each
file.
>
>
>
> Hence, we manually added the patch3 changes and recompiled the qemu. We
> then used the patched qemu-img to convert our vmdk image to dynamic VHDX
> format. We found that the image created this time had a considerable
> decrease in its size from 50GB to 12GB.
>
Could you tell me the file size of the VMDK image you were converting?
Is it roughly 12GB as well?
> However, when we deployed it into our SCVMM 2012, the import of the VHDX
> image failed with a "syntax error" as below
>
>
>
> Information (10804)
>
> Unable to import \\Test.com\Library\VHDs\Test-disk1.vhdx because of a
> syntax error in the file.
>
>
If you run qemu-img info on Test-disk1.vhdx, what does it say?
>
> Please let us know if we missed anything.
>
>
>
> Thanks,
>
> Amulya
>
>
>
[...]
Jeff
next prev parent reply other threads:[~2014-12-12 15:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 6:07 [Qemu-devel] [PATCH 0/4] VHDX Fixes for zero init Jeff Cody
2014-12-08 6:07 ` [Qemu-devel] [PATCH 1/4] block: vhdx - remove redundant comments Jeff Cody
2014-12-08 8:42 ` Max Reitz
2014-12-12 13:28 ` Stefan Hajnoczi
2014-12-15 9:04 ` Markus Armbruster
2014-12-08 6:07 ` [Qemu-devel] [PATCH 2/4] block: vhdx - update PAYLOAD_BLOCK_UNMAPPED value to match 1.00 spec Jeff Cody
2014-12-08 8:44 ` Max Reitz
2014-12-08 6:07 ` [Qemu-devel] [PATCH 3/4] block: vhdx - change .vhdx_create default block state to ZERO Jeff Cody
2014-12-08 8:48 ` Max Reitz
2014-12-08 6:07 ` [Qemu-devel] [PATCH 4/4] block: vhdx - set .bdrv_has_zero_init to bdrv_has_zero_init_1 Jeff Cody
2014-12-08 8:50 ` Max Reitz
2014-12-11 4:21 ` Lokesha, Amulya
2014-12-11 9:06 ` Max Reitz
2014-12-12 14:43 ` Lokesha, Amulya
2014-12-12 15:17 ` Jeff Cody [this message]
2014-12-12 15:59 ` Lokesha, Amulya
2014-12-17 10:46 ` Lokesha, Amulya
2014-12-17 12:14 ` Jeff Cody
2014-12-23 10:07 ` Lokesha, Amulya
2014-12-23 14:03 ` Jeff Cody
2015-01-06 10:30 ` Lokesha, Amulya
2014-12-12 15:44 ` [Qemu-devel] [PATCH 0/4] VHDX Fixes for zero init Stefan Hajnoczi
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=20141212151742.GA15426@localhost.localdomain \
--to=jcody@redhat.com \
--cc=Amulya.Lokesha@emc.com \
--cc=kwolf@redhat.com \
--cc=mreitz@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).