From: Scott Moser <1819182@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1819182] Re: info does not recognize file format of vpc with subformat=fixed
Date: Tue, 20 Apr 2021 14:40:04 -0000 [thread overview]
Message-ID: <161892960484.32508.17110058413073783652.malone@soybean.canonical.com> (raw)
In-Reply-To: 155205925919.27918.10336996226499931700.malonedeb@soybean.canonical.com
@Thomas,
Is there really no way to detect the format other than relying on
extension? :-(
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1819182
Title:
info does not recognize file format of vpc with subformat=fixed
Status in QEMU:
Confirmed
Bug description:
After creating or converting an image to vpc with 'subformat=fixed'
'qemu-img info' incorrectly identifies the image as 'raw' format.
$ qemu-img --version
qemu-img version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.10)
Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
$ qemu-img create -f vpc -o subformat=fixed my.vpc 2G
Formatting 'my.vpc', fmt=vpc size=2147483648 subformat=fixed
$ qemu-img info my.vpc
image: my.vpc
file format: raw
virtual size: 2.0G (2147992064 bytes)
disk size: 4.0K
$ qemu-img info -f vpc my.vpc
image: my.vpc
file format: vpc
virtual size: 2.0G (2147991552 bytes)
disk size: 4.0K
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1819182/+subscriptions
next prev parent reply other threads:[~2021-04-20 14:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 15:34 [Qemu-devel] [Bug 1819182] [NEW] info does not recognize file format of vpc with subformat=fixed Scott Moser
2019-03-08 15:35 ` [Qemu-devel] [Bug 1819182] " Scott Moser
2021-04-20 12:31 ` Thomas Huth
2021-04-20 14:40 ` Scott Moser [this message]
2021-04-20 16:11 ` Thomas Huth
2021-05-11 5:12 ` Thomas Huth
2021-08-25 7:31 ` 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=161892960484.32508.17110058413073783652.malone@soybean.canonical.com \
--to=1819182@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 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.