From: Max Reitz <1859989@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1859989] Re: qemu-img has broken output with large snapshot names
Date: Fri, 17 Jan 2020 09:54:21 -0000 [thread overview]
Message-ID: <157925486126.22238.8438655040751396856.malone@gac.canonical.com> (raw)
In-Reply-To: 157918316689.4864.12553262908100217782.malonedeb@wampee.canonical.com
Hi,
When did this work last for you? I tried every .0 release down to
2.12.0, and all showed this kind of broken output. (I wasn’t able to
compile 2.11.0 and earlier.)
Here was my test case:
$ ./qemu-img create -f qcow2 foo.qcow2 64M
Formatting 'foo.qcow2', fmt=qcow2 size=67108864 cluster_size=65536 lazy_refcounts=off refcount_bits=16
$ ./qemu-img snapshot -c foofoofoofoofoofoofoofoofoofoo foo.qcow2
$ ./qemu-img snapshot -l foo.qcow2
Snapshot list:
ID TAG VM SIZE DATE VM CLOCK
1 foofoofoofoofoofoofoofoofoofoo 0 2020-01-17 10:53:17 00:00:00.000
$ ./qemu-img --version
qemu-img version 2.12.0 (v2.12.0)
Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
Max
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1859989
Title:
qemu-img has broken output with large snapshot names
Status in QEMU:
New
Bug description:
On Qemu 4.1.1 the output of snapshots breaks if the chosen state name
is too long:
```
# qemu-img snapshot -l /mnt/local/some_image.qcow2
Snapshot list:
ID TAG VM SIZE DATE VM CLOCK
1 online_provider_with_dhcp747 MiB 2020-01-15 12:05:01 00:00:45.873
```
Prior to 4.1.1 this used to work with extra tabs for the VM SIZE
values. The collision is also disabling us from using a regex on top
of this output to detect the snapshot.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1859989/+subscriptions
next prev parent reply other threads:[~2020-01-17 10:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 13:59 [Bug 1859989] [NEW] qemu-img has broken output with large snapshot names pevogam
2020-01-16 18:49 ` [Bug 1859989] " pevogam
2020-01-17 9:54 ` Max Reitz [this message]
2020-01-17 10:13 ` Max Reitz
2020-01-17 10:42 ` pevogam
2020-01-17 11:08 ` Max Reitz
2020-03-10 9:12 ` Laurent Vivier
2020-04-30 13:42 ` Laurent Vivier
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=157925486126.22238.8438655040751396856.malone@gac.canonical.com \
--to=1859989@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.