From: Ben Guthro <bguthro@virtualiron.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH 0/4] VHD Support addition
Date: Tue, 19 Jun 2007 09:16:09 -0400 [thread overview]
Message-ID: <4677D719.8030605@virtualiron.com> (raw)
[PATCH 0/4] VHD Support addition
The patches that follow implement Microsoft's VHD format support, and
apply to xen-unstable.hg CS 15281:356588dda4bc
This is based on the VHD format spec covered by Microsoft's "Open
Specification Promise":
http://www.microsoft.com/interop/osp/default.mspx
MS VHD Spec can be found at the following link:
http://download.microsoft.com/download/f/f/e/ffef50a5-07dd-4cf8-aaa3-442c0673a029/Virtual%20Hard%20Disk%20Format%20Spec_10_18_06.doc
It is divided up into the following patches:
qemu-vhd-support.patch [1/4]
tapdisk-vhd-support.patch [2/4]
blktap-fixes.patch [3/4]
vdisk-support.patch [4/4]
### libvdisk ####
These patches implement a shared library (libvdisk) between qemu, and
blktap which can be explanded upon for additional formats in the future.
This was done in order to avoid code duplcation between the two areas.
At this time, it only supports the vhd format.
### vdisk_tool ###
The vdisk_tool provides a means of creating, and converting vhd files.
Like libvdisk, it is designed with future support of additional formats
in mind, but currently only supports vhd.
Usage: vdisk_tool OPTIONS -# <format-specific options> <filename>
OPTIONS:
[-f <format>] [-C] [-H] [-M] [-D <block> [-b <num_blocks>] -o outfile]]
-C Create a vdisk
-H Read vdisk headers from file
-M Modify a vdisk
-D Dump a vhd
block first block to read (required)
num_blocks number of blocks to read. If not
specified, whole file will be read
outfile output file. If not specified,
stdout is used
With this, you can convert foo.vhd to raw volume /dev/foo/bar:
vdisk_tool -D 0 -o /dev/foo/bar foo.vhd
To convert foo.vhd to fixed bar.vhd
vdisk_tool -D 0 -o bar.vhd foo.vhd
vdisk_tool -C -# -S <sizeB> -f bar.vhd
To read blocks 2 through 6 from foo.vhd to stdout:
vdisk_tool -D 2 -b 5 foo.vhd
reply other threads:[~2007-06-19 13:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4677D719.8030605@virtualiron.com \
--to=bguthro@virtualiron.com \
--cc=xen-devel@lists.xensource.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.