From: Mark Zealey <1854910@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1854910] [NEW] Support VHDX differencing images (ie images with backing)
Date: Tue, 03 Dec 2019 09:08:34 -0000 [thread overview]
Message-ID: <157536411466.21582.6322448957009703198.malonedeb@soybean.canonical.com> (raw)
Public bug reported:
The qemu vhdx driver does not support type 2 (differencing) vhdx images
(usually stored with file extension .avhdx). This means that any hyperv
images with snapshots are not supported by qemu-img. It would be great
to be able to convert to a new qcow image from a backing + set of
differencing images from hyperv, and/or convert an individual
differencing vhdx image to a qcow2 image with a backing file specified.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1854910
Title:
Support VHDX differencing images (ie images with backing)
Status in QEMU:
New
Bug description:
The qemu vhdx driver does not support type 2 (differencing) vhdx
images (usually stored with file extension .avhdx). This means that
any hyperv images with snapshots are not supported by qemu-img. It
would be great to be able to convert to a new qcow image from a
backing + set of differencing images from hyperv, and/or convert an
individual differencing vhdx image to a qcow2 image with a backing
file specified.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1854910/+subscriptions
next reply other threads:[~2019-12-03 9:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 9:08 Mark Zealey [this message]
2021-04-22 9:04 ` [Bug 1854910] Re: Support VHDX differencing images (ie images with backing) Thomas Huth
2021-06-22 4:18 ` Launchpad Bug Tracker
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=157536411466.21582.6322448957009703198.malonedeb@soybean.canonical.com \
--to=1854910@bugs.launchpad.net \
--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).