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.
Created attachment 1973947[details]
the xml of guest
Created attachment 1973947[details]
the xml of guest
Description of problem:
According to https://bugzilla.redhat.com/show_bug.cgi?id=2214147#c3 and https://bugzilla.redhat.com/show_bug.cgi?id=2214147#c4:
The guest crashed when only starting with one unbootable disk
Version-Release number of selected component (if applicable):
libvirt-9.5.0-0rc1.1.el9.s390x
qemu-kvm-8.0.0-5.el9.s390x
How reproducible:
100%
Steps to Reproduce:
1. Prepare a block disk by using scsi_debug or targetcli.
# modprobe scsi_debug dev_size_mb=500
# lsscsi
[0:0:0:0] disk Linux scsi_debug 0191 /dev/sda
2. Edit the guest only with block disk.
# virsh dumpxml rhel --xpath //disk
<disk type="block" device="disk">
<driver name="qemu" type="raw"/>
<source dev="/dev/sda"/>
<target dev="vdb" bus="virtio"/>
<address type="ccw" cssid="0xfe" ssid="0x0" devno="0x0000"/>
</disk>
3. Start the guest.
# virsh start rhel
Domain 'rhel' started
# virsh list --all
Id Name State
---------------------------------
- rhel shut off
or
1. Create a qcow2 file
qemu-img create -f qcow2 /var/lib/avocado/data/avocado-vt/images/vdb.qcow2 100M
2. Define the guest with below disk config xml:
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2'/>
<source file='/var/lib/avocado/data/avocado-vt/images/vdb.qcow2'/>
<backingStore/>
<target dev='vda' bus='virtio'/>
<address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0000'/>
</disk>
3. Start the guest
# virsh start avocado-vt-vm1
Domain 'avocado-vt-vm1' started
4. Check the guest status
# virsh list --all
Id Name State
---------------------------------
- avocado-vt-vm1 shut off
Actual results:
The guest crashed
Expected results:
The guest need to be running
Additional info:
Check all the related log in attachment
The guest firmware initiates a panic of the VM:
2023-07-04 07:28:33.514+0000: panic s390: core='0' psw-mask='0x0002000180000000' psw-addr='0x0000000000000000' reason='disabled-wait'
Which leads to the termination of the VM. I think this is desired behaviour since it's done by the firmware. I guess the only remedy is to disable the panic device if possible.
I think this is NOTABUG on s390x
Yes, this is expected (and wanted) behavior on s390x - the firmware panics if it can't boot, since there is no way to proceed any further. Thus closing as NOTABUG.