Launchpad has imported 6 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1824722.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2020-04-16T12:16:12+00:00 pkrempa wrote: Description of problem: state of cdrom tray is not updated (changed to 'closed') when resetting a VM, but the internal tray state in qemu is actually changed to 'closed' without emission of the tray-changed event. Version-Release number of selected component (if applicable): 6.2.0/upstream How reproducible: always Steps to Reproduce: 1. boot VM with cdrom 2. issue 'eject' in the guest OS on the cdrom 3. virsh reset VM 4. check tray state in qemu and in libvirt: Actual results: $ virsh dumpxml upstream | grep tray <target dev='sda' bus='scsi' tray='open'/> $ virsh qemu-monitor-command --hmp upstream info block libvirt-3-format: /var/lib/libvirt/images/systemrescuecd-amd64-6.1.2.iso (raw, read-only) Attached to: ide0-0-0 Removable device: locked, tray closed Cache mode: writeback libvirt-2-format: /tmp/blocktest/cd.iso (raw, read-only) Attached to: scsi0-0-0 Removable device: not locked, tray open Cache mode: writeback $ virsh reset upstream Domain upstream-bj was reset $ virsh dumpxml upstream | grep tray <target dev='sda' bus='scsi' tray='open'/> $ virsh qemu-monitor-command --hmp upstream info block libvirt-3-format: /var/lib/libvirt/images/systemrescuecd-amd64-6.1.2.iso (raw, read-only) Attached to: ide0-0-0 Removable device: not locked, tray closed Cache mode: writeback libvirt-2-format: /tmp/blocktest/cd.iso (raw, read-only) Attached to: scsi0-0-0 Removable device: not locked, tray closed Cache mode: writeback Expected results: Tray state in the XML matches the tray state in qemu. Additional info: Same situation happens on 'reboot' initiated from the guest OS. Reply at: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1930398/comments/0 ------------------------------------------------------------------------ On 2020-09-10T09:27:19+00:00 hhan wrote: Created attachment 1714397 the libvirtd log of step4 Hello, I found the cdrom media cannot be updated or eject after retore Version: libvirt-6.6.0-4.module+el8.3.0+7883+3d717aa8.x86_64 qemu-kvm-5.1.0-5.module+el8.3.0+7975+b80d25f1.x86_64 or libvirt-6.0.0-25.2.module+el8.2.1+7722+a9e38cf3.x86_64 qemu-kvm-4.2.0-29.module+el8.2.1+7990+27f1e480.4.x86_6 Steps: 1. Start an VM with cdrom 2. Save it by virsh save 3. Restore it from the saved file by virsh restore 4. Try to eject or update the media ➜ ~ virsh change-media ide sda --eject error: Failed to complete action eject on media error: internal error: unable to execute QEMU command 'blockdev-remove-medium': Tray of device 'scsi0-0-0-0' is not open ➜ ~ virsh change-media ide sda --update /var/lib/libvirt/images/BOOT.iso error: Failed to complete action update on media error: internal error: unable to execute QEMU command 'blockdev-remove-medium': Tray of device 'scsi0-0-0-0' is not open ➜ ~ ➜ ~ virsh qemu-monitor-command ide --hmp info block libvirt-2-format: /var/lib/libvirt/images/ide.qcow2 (qcow2) Attached to: ide0-0-0 Cache mode: writeback libvirt-1-format: /var/lib/libvirt/images/boot.iso (raw, read-only) Attached to: scsi0-0-0-0 Removable device: locked, tray closed Cache mode: writeback Reply at: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1930398/comments/1 ------------------------------------------------------------------------ On 2020-09-10T09:28:42+00:00 hhan wrote: Please help check if comment1 is the same issue of this bug Reply at: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1930398/comments/2 ------------------------------------------------------------------------ On 2020-09-10T13:55:23+00:00 pkrempa wrote: Possibly. You didn't attach the state in the XML along with the 'info block' output and also didn't check it prior to issuing 'virsh change- media', so I'm not sure whether the root cause is similar. Reply at: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1930398/comments/3 ------------------------------------------------------------------------ On 2020-09-11T10:53:02+00:00 hhan wrote: Created attachment 1714549 the xml of VM in each step Detailed Steps: ➜ ~ virsh qemu-monitor-command ide --hmp info block libvirt-2-format: /var/lib/libvirt/images/ide.qcow2 (qcow2) Attached to: ide0-0-0 Cache mode: writeback libvirt-1-format: /var/lib/libvirt/images/boot.iso (raw, read-only) Attached to: scsi0-0-0-0 Removable device: locked, tray closed Cache mode: writeback ➜ ~ virsh save ide /tmp/ide Domain ide saved to /tmp/ide ➜ ~ virsh restore /tmp/ide Domain restored from /tmp/ide ➜ ~ virsh qemu-monitor-command ide --hmp info block libvirt-2-format: /var/lib/libvirt/images/ide.qcow2 (qcow2) Attached to: ide0-0-0 Cache mode: writeback libvirt-1-format: /var/lib/libvirt/images/boot.iso (raw, read-only) Attached to: scsi0-0-0-0 Removable device: locked, tray closed Cache mode: writeback ➜ ~ virsh change-media ide sda --eject error: Failed to complete action eject on media error: internal error: unable to execute QEMU command 'blockdev-remove-medium': Tray of device 'scsi0-0-0-0' is not open ➜ ~ virsh qemu-monitor-command ide --hmp info block libvirt-2-format: /var/lib/libvirt/images/ide.qcow2 (qcow2) Attached to: ide0-0-0 Cache mode: writeback libvirt-1-format: /var/lib/libvirt/images/boot.iso (raw, read-only) Attached to: scsi0-0-0-0 Removable device: locked, tray closed Cache mode: writeback Reply at: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1930398/comments/4 ------------------------------------------------------------------------ On 2021-09-08T13:31:26+00:00 jferlan wrote: Bulk update: Move RHEL-AV bugs to RHEL9. If necessary to resolve in RHEL8, then clone to the current RHEL8 release. Reply at: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1930398/comments/17 ** Changed in: libvirt (Fedora) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930398 Title: libvirtd unable to execute QEMU command 'blockdev-remove-medium' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1930398/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
