Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Block node is read-only when start a qcow2 image on https server and with auto-read-only=on set on its file node
Version-Release number of selected component (if applicable):
qemu-kvm-rhev version:qemu-kvm-rhev-2.12.0-24.el7.x86_64
kernel version:3.10.0-993.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Create a qcow2 image on https server.
（https server）#qemu-img create -f qcow2 base 1G
2.Start vm with a qcow2 image on https server with auto-read-only=on set on its file node.
/usr/libexec/qemu-kvm \
-name 'avocado-vt-vm1' \
-machine pc \
-nodefaults \
-device VGA,bus=pci.0,addr=0x2 \
-blockdev node-name=file_base,driver=https,sslverify=off,url=https://10.66.144.33/base,auto-read-only=on \
-blockdev driver=qcow2,file=file_base,node-name=base,auto-read-only=on \
-qmp tcp:0:3000,server,nowait \
-vnc :0 \
-monitor stdio \
Actual results:
After step1, vm failed to start with qemu info:
qemu-kvm: -blockdev driver=qcow2,file=file_base,node-name=base,auto-read-only=on: Block node is read-only
Expected results:
VM can start successfully.
Additional info:
1. When start vm with file node param "read-only=on", vm can start successfully.
-blockdev node-name=file_base,driver=https,sslverify=off,url=https://10.66.144.33/base,auto-read-only=on \
-blockdev driver=qcow2,file=file_base,node-name=base,read-only=on \
2. With backend: localfs and qcow2 image + auto-read-only=on, vm can also start suceessfully.
-blockdev node-name=file_base,driver=file,filename=/home/base,auto-read-only=on \
-blockdev driver=qcow2,file=file_base,node-name=base,auto-read-only=on \