** Changed in: qemu
Status: Fix Committed => Fix Released
--
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:
Fixed here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=804359b8b90f
** Changed in: qemu
Status: New => Fix Committed
--
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-i
Sent a patch: https://lists.nongnu.org/archive/html/qemu-
block/2020-01/msg00376.html
--
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 nam
Hi Max,
It last worked in (previous version we used):
[root@c15 ~]# qemu-img --version
qemu-img version 3.1.1 (qemu-3.1.1-2.fc30)
Copyright (c) 2003-2018 Fabrice Bellard and the QEMU Project developers
Yes, unfortunately Launchpad doesn't seem to support any literal
formatting which is why I trie
I’ve just seen that launchpad collapses the spaces in the snapshot...
All I can say is that diff tells me the output from 2.12.0 and 4.1.1 is
exactly the same, with only one difference: 2.12.0 prints the VM SIZE as
“0” (without a unit), whereas 4.1.1 prints “0 B”.
But now I just realized you proba
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
** Description changed:
- On Qemu 4.1.1 the output of snalshots breaks if the chosen state name is
+ 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:
IDTAG V
