qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: qi zhou <atmgnd@outlook.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Qemu-block <qemu-block@nongnu.org>
Subject: Re: How to create vhdx differencing disk using qemu-img
Date: Thu, 18 Mar 2021 15:49:54 -0400	[thread overview]
Message-ID: <3585d6b8-a94e-bd2e-5a38-6ddfc2fe089d@redhat.com> (raw)
In-Reply-To: <ME3P282MB16654DBBEAE47620226F448DC9699@ME3P282MB1665.AUSP282.PROD.OUTLOOK.COM>

On 3/17/21 10:37 PM, qi zhou wrote:
> When I create vhdx differencing disk using qemu-img, It says
>   qemu-img: xxx.vhd Backing file not supported for file format 'vhdx'
> 
> The command I used is
> qemu-img create -f vhdx -b test.vhdx test-snapshot.vhdx
> 
> Here is my questions
> 1. Is vhdx format [full] supported by qemu ?

We support raw and qcow2 fully, read-write.

Everything else is "read-only", though write support might work, we 
don't encourage its use in production environments.

> 2. If not, is there any easy way to implement differencing disk of vhdx in qemu-img ?

the -b flag is generally for qcow2 files; I am not very familiar with 
VHDX but it appears as though we don't support it here.

I imagine it's 
https://www.altaro.com/hyper-v/hyper-v-differencing-disks-explained/ ?

I don't think we support those... ah, yeah, in block/vhdx.c:

typedef enum VHDXImageType {
     VHDX_TYPE_DYNAMIC = 0,
     VHDX_TYPE_FIXED,
     VHDX_TYPE_DIFFERENCING,   /* Currently unsupported */
} VHDXImageType;

> 3. Is there any other tools support vhdx on linux ?
> 

Not that I'm aware of, but I can't say I've looked before.



      reply	other threads:[~2021-03-18 19:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18  2:37 How to create vhdx differencing disk using qemu-img qi zhou
2021-03-18 19:49 ` John Snow [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=3585d6b8-a94e-bd2e-5a38-6ddfc2fe089d@redhat.com \
    --to=jsnow@redhat.com \
    --cc=atmgnd@outlook.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.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 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).