From: Kevin Wolf <kwolf@redhat.com>
To: Jeff Cody <jcody@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 2/5] block: vhdx header for the QEMU support of VHDX images
Date: Thu, 25 Apr 2013 15:05:37 +0200 [thread overview]
Message-ID: <20130425130537.GC3156@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <f57fdf4c8563d591b0c4992151ebcd22abef5175.1366726446.git.jcody@redhat.com>
Am 23.04.2013 um 16:24 hat Jeff Cody geschrieben:
> This is based on Microsoft's VHDX specification:
> "VHDX Format Specification v0.95", published 4/12/2012
> https://www.microsoft.com/en-us/download/details.aspx?id=29681
>
> These structures define the various header, metadata, and other
> block structures defined in the VHDX specification.
>
> Signed-off-by: Jeff Cody <jcody@redhat.com>
> ---
> block/vhdx.h | 327 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 327 insertions(+)
> create mode 100644 block/vhdx.h
> +typedef struct QEMU_PACKED vhdx_page83_data {
> + uint8_t page_83_data[16]; /* unique id for scsi devices that
> + support page 0x83 */
> +} vhdx_page83_data;
Why uint8_t[16] instead of ms_guid?
> +
> +typedef struct QEMU_PACKED vhdx_virtual_disk_logical_sector_size {
> + uint32_t logical_sector_size; /* virtual disk sector size (in bytes).
> + Can only be 512 or 4096 bytes */
> +} vhdx_virtual_disk_logical_sector_size;
> +
> +typedef struct QEMU_PACKED vhdx_virtual_disk_physical_sector_size {
> + uint32_t physical_sector_size; /* physical sector size (in bytes).
> + Can only be 512 or 4096 bytes */
> +} vhdx_virtual_disk_physical_sector_size;
> +
> +typedef struct QEMU_PACKED vhdx_parent_locator_header {
> + uint8_t locator_type[16]; /* type of the parent virtual disk. */
Same question here.
> + uint16_t reserved;
> + uint16_t key_value_count; /* number of key/value pairs for this
> + locator */
> +} vhdx_parent_locator_header;
Kevin
next prev parent reply other threads:[~2013-04-25 13:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 14:24 [Qemu-devel] [PATCH v2 0/5] Initial VHDX support Jeff Cody
2013-04-23 14:24 ` [Qemu-devel] [PATCH v2 1/5] qemu: add castagnoli crc32c checksum algorithm Jeff Cody
2013-04-23 14:24 ` [Qemu-devel] [PATCH v2 2/5] block: vhdx header for the QEMU support of VHDX images Jeff Cody
2013-04-23 15:10 ` Kevin Wolf
2013-04-23 16:32 ` Jeff Cody
2013-04-24 12:31 ` Stefan Hajnoczi
2013-04-24 12:34 ` Jeff Cody
2013-04-25 13:05 ` Kevin Wolf [this message]
2013-04-25 14:29 ` Jeff Cody
2013-04-23 14:24 ` [Qemu-devel] [PATCH v2 3/5] block: initial VHDX driver support framework - supports open and probe Jeff Cody
2013-04-23 15:46 ` Kevin Wolf
2013-04-23 16:11 ` Jeff Cody
2013-04-23 16:18 ` Kevin Wolf
2013-04-24 13:21 ` Stefan Hajnoczi
2013-04-24 13:40 ` Jeff Cody
2013-04-25 13:04 ` Kevin Wolf
2013-04-25 15:03 ` Jeff Cody
2013-04-25 16:52 ` Kevin Wolf
2013-04-28 7:29 ` Fam Zheng
2013-04-29 17:25 ` Jeff Cody
2013-04-28 9:58 ` Fam Zheng
2013-04-29 17:24 ` Jeff Cody
2013-04-23 14:24 ` [Qemu-devel] [PATCH v2 4/5] block: add read-only support to VHDX image format Jeff Cody
2013-04-24 14:38 ` Stefan Hajnoczi
2013-04-23 14:24 ` [Qemu-devel] [PATCH v2 5/5] block: add header update capability for VHDX images Jeff Cody
2013-04-24 14:47 ` Stefan Hajnoczi
2013-04-24 14:56 ` Jeff Cody
2013-04-25 7:20 ` Stefan Hajnoczi
2013-04-28 10:05 ` Fam Zheng
2013-04-29 17:19 ` Jeff Cody
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=20130425130537.GC3156@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=jcody@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).