From: Ashijeet Acharya <ashijeetacharya@gmail.com>
To: John Snow <jsnow@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>, Fam Zheng <famz@redhat.com>,
Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Peter Wu <peter@lekensteyn.nl>
Subject: Re: [Qemu-devel] DMG chunk size independence
Date: Tue, 25 Apr 2017 10:50:51 +0530 [thread overview]
Message-ID: <CAC2QTZaxvkug1xDadmOhrKCF0XkWWy1OgbTkCpp+ee2oY9ooMw@mail.gmail.com> (raw)
In-Reply-To: <e91d0cfe-407a-ab3b-ee9a-e32d570668a4@redhat.com>
>> For testing I am first converting the images to raw format and then
>> comparing the resulting image with the one converted using v2.9.0 DMG
>> driver and after battling for 2 days with my code, it finally prints
>> "Images are identical." According to John, that should be pretty
>> conclusive and I completely agree.
>>
>
> Yes, comparing a sample.dmg against a raw file generated from the 2.9.0
> qemu-img tool should be reasonably good evidence that you have not
> altered the behavior of the tool.
>
>> Now, the real thing I wanted to ask was, if someone is aware of a DMG
>> file which has a chunk size above 64 MiB so that I can test those too.
>> If yes, please share the download link with me.
>> Currently I am testing the ones posted by Peter Wu while submitting
>> his DMG work in 2014.
>> Here -> https://lists.nongnu.org/archive/html/qemu-devel/2014-12/msg03606.html
>>
>
> Are any of those over 64MB? I assume you're implying that they aren't.
No, they are not. Because none of them crash while converting with
using the qemu-img tool as in 2.9.0(as it has a limitation of 64MiB).
>
> Maybe Peter knows?...
Yes, I contacted him and he has been of great help so far :-)
Ashijeet
next prev parent reply other threads:[~2017-04-25 5:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-15 8:38 [Qemu-devel] DMG chunk size independence Ashijeet Acharya
2017-04-17 20:29 ` John Snow
2017-04-18 10:21 ` Ashijeet Acharya
2017-04-18 17:05 ` John Snow
2017-04-18 17:43 ` Ashijeet Acharya
2017-04-23 9:03 ` Ashijeet Acharya
2017-04-24 21:19 ` John Snow
2017-04-25 5:20 ` Ashijeet Acharya [this message]
2017-04-25 9:50 ` Peter Wu
2017-04-18 10:29 ` Kevin Wolf
2017-04-25 10:48 ` Ashijeet Acharya
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=CAC2QTZaxvkug1xDadmOhrKCF0XkWWy1OgbTkCpp+ee2oY9ooMw@mail.gmail.com \
--to=ashijeetacharya@gmail.com \
--cc=famz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=peter@lekensteyn.nl \
--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.