From: Zixuan Wang <1759522@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1759522] Re: windows qemu-img create vpc/vhdx error
Date: Wed, 19 Feb 2020 06:08:28 -0000 [thread overview]
Message-ID: <158209250842.28930.13710187546742376715.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 152222836105.21062.2375148895134658603.malonedeb@chaenomeles.canonical.com
I remembered asking a QEMU developer about this. He suggested me to send
an email to the developer mailing list, or send messages to IRC channel.
I don't have time to do this right now, but if someone else finds this
bug report and wants to get the help, please email them instead.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1759522
Title:
windows qemu-img create vpc/vhdx error
Status in QEMU:
New
Bug description:
On windows, using qemu-img (version 2.11.90) to create vpc/vhdx
virtual disk tends to fail. Here's the way to reproduce:
1. Install qemu-w64-setup-20180321.exe
2. Use `qemu-img create -f vhdx -o subformat=fixed disk.vhdx 512M` to create a vhdx:
Formatting 'disk.vhdx', fmt=vhdx size=536870912 log_size=1048576 block_size=0 subformat=fixed
3. Execute `qemu-img info disk.vhdx` gives the result, (note the `disk size` is incorrect):
image: disk.vhdx
file format: vhdx
virtual size: 512M (536870912 bytes)
disk size: 1.4M
cluster_size: 8388608
4. On Windows 10 (V1709), double click disk.vhdx gives an error:
Make sure the file is in an NTFS volume and isn't in a compressed folder or volume.
Using Disk Management -> Action -> Attach VHD gives an error:
The requested operation could not be completed due to a virtual disk system limitation. Virtual hard disk files must be uncompressed and uneccrypted and must not be sparse.
Comparison with Windows 10 created VHDX:
1. Using Disk Management -> Action -> Create VHD:
File name: win.vhdx
Virtual hard disk size: 512MB
Virtual hard disk format: VHDX
Virtual hard disk type: Fixed size
2. Detach VHDX
3. Execute `qemu-img info win.vhdx` gives the result:
image: win.vhdx
file format: vhdx
virtual size: 512M (536870912 bytes)
disk size: 516M
cluster_size: 33554432
Comparison with qemu-img under Ubuntu:
1. Version: qemu-img version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.16),
Copyright (c) 2004-2008 Fabrice Bellard
2. qemu-img create -f vhdx -o subformat=fixed lin.vhdx 512M
Formatting 'lin.vhdx', fmt=vhdx size=536870912 log_size=1048576 block_size=0 subformat=fixed
3. qemu-img info lin.vhdx
image: lin.vhdx
file format: vhdx
virtual size: 512M (536870912 bytes)
disk size: 520M
cluster_size: 8388608
4. Load lin.vhdx under Windows 10 is ok
The same thing happens on `vpc` format with or without
`oformat=fixed`, it seems that windows version of qemu-img has some
incorrect operation? My guess is that windows version of qemu-img
doesn't handle the description field of vpc/vhdx, which leads to an
incorrect `disk size` field.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1759522/+subscriptions
next prev parent reply other threads:[~2020-02-19 6:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 9:12 [Qemu-devel] [Bug 1759522] [NEW] windows qemu-img create vpc/vhdx error Zixuan Wang
2018-03-28 9:16 ` [Qemu-devel] [Bug 1759522] " Zixuan Wang
2018-03-28 10:27 ` Zixuan Wang
2019-10-27 6:17 ` Adam Baxter
2020-02-10 6:25 ` Qi Zhou
2020-02-19 6:08 ` Zixuan Wang [this message]
2020-02-29 0:14 ` maro
2021-04-12 14:59 ` Albert Kao
2021-04-21 6:31 ` Thomas Huth
2021-04-21 11:39 ` Albert Kao
2021-05-05 5:16 ` Thomas Huth
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=158209250842.28930.13710187546742376715.malone@chaenomeles.canonical.com \
--to=1759522@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).