Created attachment 1608973 [details] PrtSc for guest Description of problem: After installed and write a tmp file in the guest based on RBD, there is some error msg in in guest. Version-Release number of selected component (if applicable): qemu-kvm-4.1.0-4.module+el8.1.0+4020+16089f93 kernel-4.18.0-135.el8 How reproducible: 2/2 Steps to Reproduce: 1. Create qcow2 image file over RBD # qemu-img create -f qcow2 rbd:kvmtest-pool/base.qcow2 20G 2. Install guest on it # /usr/libexec/qemu-kvm \ -name 'guest-rhel8.0' \ -machine q35 \ -nodefaults \ -vga qxl \ -drive id=drive_cd1,if=none,snapshot=off,aio=threads,cache=unsafe,media=cdrom,file=RHEL-7.6-20181010.0-Server-x86_64-dvd1.iso \ -device ide-cd,id=cd1,drive=drive_cd1,bus=ide.0,unit=0 \ -drive id=drive_image1,if=none,snapshot=off,aio=threads,cache=none,format=qcow2,file=rbd:kvmtest-pool/base.qcow2 \ -device virtio-blk-pci,id=virtio_blk_pci0,drive=drive_image1,bus=pcie.0,addr=05,bootindex=0 \ -vnc :0 \ -monitor stdio \ -m 8192 \ -smp 8 \ -device virtio-net-pci,mac=9a:b5:b6:b1:b2:b3,id=idMmq1jH,vectors=4,netdev=idxgXAlm,bus=pcie.0,addr=0x9 \ -netdev tap,id=idxgXAlm \ -chardev socket,id=qmp_id_qmpmonitor1,path=/var/tmp/timao/monitor-qmpmonitor1-20180220-094308-h9I6hRsI,server,nowait \ -mon chardev=qmp_id_qmpmonitor1,mode=control \ 3. Write a tmp file in the guest. Actual results: 1. There is some error msg in the guest. Check the attachment, please. 2. And the guest hangs frequently. And there is warning in the HMP like below: (qemu) qemu-kvm: warning: no scancode found for keysym 65323 qemu-kvm: warning: no scancode found for keysym 65323 qemu-kvm: warning: no scancode found for keysym 65323 qemu-kvm: warning: no scancode found for keysym 65323 qemu-kvm: warning: no scancode found for keysym 65323 qemu-kvm: warning: no scancode found for keysym 65323 Expected results: No error msg in the guest. Additional info: For raw image with rbd, there is no the issue.
(In reply to Tingting Mao from comment #0) > Created attachment 1608973 [details] > PrtSc for guest Please attach images directly (as .jpg or .png files) instead of embedding them in a docx file. > > Actual results: > 1. There is some error msg in the guest. Check the attachment, please. > > 2. And the guest hangs frequently. And there is warning in the HMP like > below: > (qemu) qemu-kvm: warning: no scancode found for keysym 65323 > qemu-kvm: warning: no scancode found for keysym 65323 > qemu-kvm: warning: no scancode found for keysym 65323 > qemu-kvm: warning: no scancode found for keysym 65323 > qemu-kvm: warning: no scancode found for keysym 65323 > qemu-kvm: warning: no scancode found for keysym 65323 > This message is related to keyboard mappings or emulation, It probably doesn't have relation to rbd/raw.
Created attachment 1615233 [details] PrtSc for guest PrtSc for guest with png format, check please.
QEMU has been recently split into sub-components and as a one-time operation to avoid breakage of tools, we are setting the QEMU sub-component of this BZ to "General". Please review and change the sub-component if necessary the next time you review this BZ. Thanks
As discussed upstream [1], QCOW2 on RBD is not really well supported and it is expected to be removed. This is also because there doesn't seem to be much advantage to using QCOW2 on RBD. If there is a specific use case where it is useful to use QCOW2 on RBD, please open a new BZ where the requirements are explained. AFAIK layered products, such as OpenStack, do not use QCOW2 with in-QEMU RBD. [1] https://lists.gnu.org/archive/html/qemu-devel/2021-03/msg01045.html
(In reply to Stefano Garzarella from comment #9) > As discussed upstream [1], QCOW2 on RBD is not really well supported and it > is expected to be removed. > This is also because there doesn't seem to be much advantage to using QCOW2 > on RBD. > > If there is a specific use case where it is useful to use QCOW2 on RBD, > please open a new BZ where the requirements are explained. > > AFAIK layered products, such as OpenStack, do not use QCOW2 with in-QEMU RBD. > > [1] https://lists.gnu.org/archive/html/qemu-devel/2021-03/msg01045.html QE agrees to close. Thanks.