All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Hahn <hahn@univention.de>
To: Fabio Fantoni <fabio.fantoni@m2r.biz>,
	Juergen Gross <jgross@suse.com>,
	xen-devel@lists.xenproject.org
Subject: Re: pvops upstream status - VHD
Date: Tue, 24 Jun 2014 07:21:40 +0200	[thread overview]
Message-ID: <53A90AE4.4060708@univention.de> (raw)
In-Reply-To: <53A050A9.9010502@m2r.biz>

Hello,

On 17.06.2014 16:28, Fabio Fantoni wrote:
> My test was only with raw image, for what I read time ago probably the
> only problem should be with vhd format they said needed improvements on
> qemu but they might have done in the meantime (if I remember good I read
> it 2 year ago).

VHD in QEMU had very little changes, differencing images are still not
supported (I have a WIP patch which supports reading, but write seems to
be broken). What's also missing it support for the journaling extension,
which vhd-utils supports.
VHDX support seems to be a lot better in QEMU (and non-existent in
chd-utils), which AFAIK has removed some limitations of VHD (image size,
journaling support), so my personal opinion would classify VHD as
legacy, for which read support is good to have, but write support is
less important.

Philipp

  reply	other threads:[~2014-06-24  6:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17  9:52 pvops upstream status Juergen Gross
2014-06-17 10:25 ` Konrad Rzeszutek Wilk
2014-06-17 10:55 ` Fabio Fantoni
2014-06-17 13:34   ` Juergen Gross
2014-06-17 14:28     ` Sander Eikelenboom
2014-06-17 15:55       ` Stefano Stabellini
2014-06-17 14:28     ` Fabio Fantoni
2014-06-24  5:21       ` Philipp Hahn [this message]
2014-06-17 15:25 ` Daniel Kiper

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=53A90AE4.4060708@univention.de \
    --to=hahn@univention.de \
    --cc=fabio.fantoni@m2r.biz \
    --cc=jgross@suse.com \
    --cc=xen-devel@lists.xenproject.org \
    /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.