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.
(In reply to David Gibson from comment #3)
> Please check if the same error occurs on x86, this seems relatively unlikely
> to be powerpc specific.
It's already mentioned in the description, under "Additional info" - seems like it is powerpc specific indeed.
Verified with:
qemu-kvm-rhev-2.9.0-10.el7.x86_64
kernel-3.10.0-679.el7.x86_64
Steps exactly same as comment0.
Result:
As expected, qmp prompts error and does not perform any block job:
{"error": {"class": "GenericError", "desc": "Could not create file: No such file or directory"}}
(In reply to Qianqian Zhu from comment #13)
> Verified with:
> qemu-kvm-rhev-2.9.0-10.el7.x86_64
> kernel-3.10.0-679.el7.x86_64
>
> Steps exactly same as comment0.
> Result:
> As expected, qmp prompts error and does not perform any block job:
> {"error": {"class": "GenericError", "desc": "Could not create file: No such
> file or directory"}}
Setting VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2017:2392
Description of problem: qemu abort when live snapshot for multiple block device simultaneously with transaction and one is to a non-exist path. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Launch guest with two block device. # gdb /usr/libexec/qemu-kvm (gdb) run -drive file=/home/rhel74-64-virtio-scsi.qcow2,format=qcow2,if=none,id=drive-scsi-disk0,werror=stop,rerror=stop,cache=none -device virtio-scsi-pci,id=scsi0 -device scsi-hd,drive=drive-scsi-disk0,bus=scsi0.0,scsi-id=0,lun=0,id=scsi-disk0 -monitor stdio -qmp tcp:0:5555,server,nowait -vnc :3 -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=70:e2:84:14:0e:15 -drive file=/home/test.qcow2,format=qcow2,if=none,id=drive-scsi-disk1,werror=stop,rerror=stop,cache=none -device scsi-hd,drive=drive-scsi-disk1,bus=scsi0.0,scsi-id=1,lun=1,id=scsi-disk1 2. live snapshot simultaneously with transaction, "/home/test/test/test" below does not exist. { "execute": "transaction", "arguments": { "actions": [ { 'type': 'blockdev-snapshot-sync', 'data' : { "device": "drive-scsi-disk0","snapshot-file": "/home/sn1-a.qcow2","mode": "absolute-paths", "format": "qcow2" } }, { 'type': 'blockdev-snapshot-sync', 'data' : { "device": "drive-scsi-disk1","snapshot-file": "/home/test/test/test","mode": "absolute-paths", "format": "qcow2" } }]}} Actual results: qemu abort. (qemu) [Thread 0x3fffb47eea80 (LWP 11890) exited] Formatting '/home/sn1-a.qcow2', fmt=qcow2 size=21474836480 backing_file=/home/rhel74-64-virtio-scsi.qcow2 backing_fmt=qcow2 encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16 [New Thread 0x3fffb47eea80 (LWP 11968)] Formatting '/home/test/test/test', fmt=qcow2 size=21474836480 backing_file=/home/test.qcow2 backing_fmt=qcow2 encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16 Unexpected error in bdrv_check_update_perm() at block.c:1611: Conflicts with use by drive-scsi-disk0 as 'backing', which does not allow 'write' on #block198 Program received signal SIGABRT, Aborted. 0x00003fffb6f2ef90 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig); Expected results: qmp prompt error like: {"error": {"class": "GenericError", "desc": "Could not create file: No such file or directory"}} Additional info: 1. This issue is ppc only, x86 works well. 2. qmp prompts error as expect and qemu works normally if replace step 2 with either: { "execute": 'blockdev-snapshot-sync', "arguments": { "device": "drive-scsi-disk1","snapshot-file": "/home/test/test/test","mode": "absolute-paths", "format": "qcow2" } } or: { "execute": "transaction", "arguments": { "actions": [ { 'type': 'blockdev-snapshot-sync', 'data' : { "device": "drive-scsi-disk1","snapshot-file": "/home/test/test/test","mode": "absolute-paths", "format": "qcow2" } }]}}