From: "Denis V. Lunev" <den@openvz.org>
Cc: Kevin Wolf <kwolf@redhat.com>, Jeff Cody <jcody@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Roman Kagan <rkagan@parallels.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/7] parallels format support improvements
Date: Tue, 2 Dec 2014 13:33:40 +0300 [thread overview]
Message-ID: <547D9584.7060901@openvz.org> (raw)
In-Reply-To: <1415278478-19384-1-git-send-email-den@openvz.org>
On 06/11/14 15:54, Denis V. Lunev wrote:
> The patchset implements additional compatibility bits for Parallels
> format:
> - initial support of parsing of Parallels DiskDeskriptor.xml
> Typically Parallels disk bundle consists of several images which are
> glued by XML disk descriptor. Also XML hides inside several important
> parameters which are not available in the image header.
> - support for padded Parallels images.
> For the time being Parallels was created an optimization for such OSes
> in its desktop product. Desktop users are not qualified enough to create
> properly aligned installations. Thus Parallels makes a blind guess
> on a customer behalf and creates so-called "padded" images if guest
> OS type is specified as WinXP, Win2k and Win2k3.
>
> The code uses approach from VMDK support, either image or XML descriptor
> could be used. Though there is temporary hack in the opening code:
> BlockDriverState->file is being reopened inside parallels_open. I prefer
> to keep this code in this state till proper Parallels snapshots support
> in order to minimize current changes.
>
> Changes from v2:
> - (patch 1) changed libxml2 addition as suggested by Michael Tokarev
> - (patch 2) changed API of xml_find/xml_get_text to avoid memcpy to variable
> on stack
> - (patch 2) dropped predefined value for PARALLELS_XML/PARALLELS_IMAGE
> - (patch 2) other minor changes (spelling, placement)
> - (patch 3) quoted TEST_IMG as suggested by Jeff Cody
> - (patches 4, 6) quoted TEST_IMG as suggested by Jeff Cody
>
> Changes from v1:
> - dropped already merged part (original patches 1-3)
>
> CC: Jeff Cody <jcody@redhat.com>
> CC: Kevin Wolf <kwolf@redhat.com>
> CC: Stefan Hajnoczi <stefanha@redhat.com>
> CC: Roman Kagan <rkagan@parallels.com>
> CC: Denis V. Lunev <den@openvz.org>
>
ping
prev parent reply other threads:[~2014-12-02 10:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 12:54 [Qemu-devel] [PATCH v3 0/7] parallels format support improvements Denis V. Lunev
2014-11-06 12:54 ` [Qemu-devel] [PATCH 1/7] configure: add dependency from libxml2 Denis V. Lunev
2014-11-06 12:54 ` [Qemu-devel] [PATCH 2/7] block/parallels: allow to specify DiskDescriptor.xml instead of image file Denis V. Lunev
2014-11-06 12:54 ` [Qemu-devel] [PATCH 3/7] iotests, parallels: quote TEST_IMG in 076 test to be path-safe Denis V. Lunev
2014-11-06 12:54 ` [Qemu-devel] [PATCH 4/7] iotests: simple parallels XML disk descriptor file test added Denis V. Lunev
2014-11-06 12:54 ` [Qemu-devel] [PATCH 5/7] block/parallels: support padded Parallels images Denis V. Lunev
2014-11-06 12:54 ` [Qemu-devel] [PATCH 6/7] iotests: padded parallels image test Denis V. Lunev
2014-11-06 12:54 ` [Qemu-devel] [PATCH 7/7] parallels: change copyright information in the image header Denis V. Lunev
2014-12-02 10:33 ` Denis V. Lunev [this message]
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=547D9584.7060901@openvz.org \
--to=den@openvz.org \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkagan@parallels.com \
--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 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.