qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: Eric Blake <eblake@redhat.com>, "Denis V. Lunev" <den@openvz.org>
Cc: John Snow <jsnow@redhat.com>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/1] parallels: add format spec
Date: Wed, 18 Nov 2015 09:15:35 +0300	[thread overview]
Message-ID: <564C1787.8040500@virtuozzo.com> (raw)
In-Reply-To: <564B4DB4.1070005@redhat.com>

On 17.11.2015 18:54, Eric Blake wrote:
> On 11/16/2015 04:52 AM, Denis V. Lunev wrote:
>> From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
>>
>> This specifies Parallels image format as implemented in Parallels Cloud
>> Server 6.10
> Are we the canonical location of the specification?  If not, do we risk
> getting out of sync with the canonical Parallels Cloud Server
> documentation, in which case, wouldn't it be better to point to a URL of
> the externally-maintained spec rather than duplicating it here?
>
>> +++ b/docs/specs/parallels.txt
>> @@ -0,0 +1,218 @@
>> += Parallels Expandable Image File Format =
>> +
> Is this document okay under the default GPLv2+ license, or does it need
> to explicitly call out a different license?
>
>
>> +== Header ==
>> +
>> +The header is placed at the start of an image and contains the following
>> +fields:
>> +
>> +    char      magic[16]
>> +              Must contain "WithoutFreeSpace" or "WithouFreSpacExt".
>> +
>> +    uint32    version
>> +              Must be 2.
>> +
> You may want to compare to the qcow2 spec, which also lists expected
> byte offsets for each field (rather than having to count how many
> earlier fields of which widths were specified).

I've compared qed spec with qcow2 spec and like the first one. What the 
need of specifying each offset? Creating a c-structure is simpler when 
you see types. and than offsetof and sizeof may be used if needed. 
Nobody will #define numeric offsets I think.



-- 
Best regards,
Vladimir
* now, @virtuozzo.com instead of @parallels.com. Sorry for this inconvenience.

  parent reply	other threads:[~2015-11-18  6:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-16 11:52 [Qemu-devel] [PATCH 1/1] parallels: add format spec Denis V. Lunev
2015-11-17 15:54 ` Eric Blake
2015-11-17 16:46   ` Denis V. Lunev
2015-11-18  6:15   ` Vladimir Sementsov-Ogievskiy [this message]
2015-11-18  6:39     ` Eric Blake
2015-11-18  7:13       ` Vladimir Sementsov-Ogievskiy

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=564C1787.8040500@virtuozzo.com \
    --to=vsementsov@virtuozzo.com \
    --cc=den@openvz.org \
    --cc=eblake@redhat.com \
    --cc=jsnow@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).