** Changed in: qemu
Status: Incomplete => 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/1401798
Title:
Qemu 2.2.0 savevm crash.
Status in QEMU:
Fix Released
Bug description:
Triaging old bug tickets... can you still reproduce this issue with the
latest version of QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QE
I think I get the reason.
>From Qemu 2.2.0, in qcow2_open: l2_cache_size =
>MAX(DEFAULT_L2_CACHE_BYTE_SIZE/s->cluster_size, MIN_L2_CACHE_SIZE);
Here DEFAULT_L2_CACHE_BYTE_SIZE=1M, MIN_L2_CACHE_SIZE=1.
If the cluster_size < 1M, the l2_cache_size will be greater than 1, it
is ok.
If the cluster
The bug can be reproduced every time.
1. I install a Ubuntu 14.04 guest.
2. The monitor command is (qemu) snapshot_blkdev_internal drive-virtio-disk0 s1
3. Or (qemu) savevm s1
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://
Maybe bdrv_snapshot_create() should take s->lock but it's not clear yet
what causes all qcow2 cache entries to be referenced.
How do you reproduce this crash? Please give exact steps including what
commands to run inside the guest and what QEMU monitor commands to run.
Is the crash deterministic
