Public bug reported:
virsh qemu-monitor-command ${DOMAIN} '{ "execute" : "drive-backup" ,
"arguments" : { "device" : "drive-virtio-disk0" , "sync" : "top" ,
"target" : "iscsi://192.168.1.100:3260/iqn.2019-01.com.iaas/0" } }'
When the drive-backup is running, I manually crash the iscsi server（or
i
Thanks, all:
I only want to know:
1. Is this a bug?
2. Which qemu version will fix the bug?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1814418
Title:
persistent bitmap will be inconsistent whe
Public bug reported:
I use iscsi protocol to drive-backup:
---iscsi target---
yum -y install targetcli python-rtslib
systemctl start target
systemctl enable target
targetcli /iscsi create iqn.2019-01.com.iaas
targetcli /iscsi/iqn.2019-01.com.iaas/tpg1 set attribute authentication=0
demo_mode_wri
** Description changed:
Follow these steps to reappear the bug:
1. start qemu
2. add persistent bitmap: '{ "execute": "block-dirty-bitmap-add",
"arguments": {"node": "drive-virtio-disk1","name": "bitmap0", "persistent":true
}}'
3. stop qemu (Friendly shutdown)
4. re-start qemu
5.
** Description changed:
Follow these steps to reappear the bug:
1. start qemu
2. add persistent bitmap: '{ "execute": "block-dirty-bitmap-add",
"arguments": {"node": "drive-virtio-disk1","name": "bitmap0", "persistent":true
}}'
- 3. kill -9 qemu (simulate Host crash, eg. lose power)
- 4
Public bug reported:
Follow these steps to reappear the bug:
1. start qemu
2. add persistent bitmap: '{ "execute": "block-dirty-bitmap-add", "arguments":
{"node": "drive-virtio-disk1","name": "bitmap0", "persistent":true }}'
3. kill -9 qemu (simulate Host crash, eg. lose power)
4. restart qemu
