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.
When a sata virtual disk bind to a PCI **function='0x1'** without having a **function='0x0' multifunction='on'** dev, libvirt doesn't report error and guest just cannot be booted
Description:
When a sata virtual disk bind to a PCI **function='0x1'** without having a **function='0x0' multifunction='on'** dev, libvirt doesn't report error and guest just cannot be booted
Versions:
libvirt-3.2.0-2.el7.x86_64
qemu-kvm-rhev-2.9.0-1.el7.x86_64
How reproducible:
100%
Steps:
#virsh dumpxml vm
...
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2'/>
<source file='/var/lib/libvirt/images/RHEL-7.4-x86_64-latest.qcow2'/>
<backingStore/>
<target dev='sda' bus='sata'/>
<alias name='sata0-0-0'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
...
<controller type='sata' index='0'>
<alias name='sata0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
</controller>
# virsh start vm
Domain vm started
In virt-viewer, the guest just shows:
No bootable device
Actual result:
As above
Expected result:
If having a dev with **function='0x0' multifunction='on'** is mandatory to use **function='0x1/2/3...'** on a pci slot, libvirt should do the check and report error at first before vm start. This issue can be met when I deleted an existing devicec as follow:
<memballoon model='virtio'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
</memballoon>
And it's tricky to find out what happened.
Comment 2Jaroslav Suchanek
2017-04-26 14:55:35 UTC
Description: When a sata virtual disk bind to a PCI **function='0x1'** without having a **function='0x0' multifunction='on'** dev, libvirt doesn't report error and guest just cannot be booted Versions: libvirt-3.2.0-2.el7.x86_64 qemu-kvm-rhev-2.9.0-1.el7.x86_64 How reproducible: 100% Steps: #virsh dumpxml vm ... <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/var/lib/libvirt/images/RHEL-7.4-x86_64-latest.qcow2'/> <backingStore/> <target dev='sda' bus='sata'/> <alias name='sata0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> ... <controller type='sata' index='0'> <alias name='sata0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> # virsh start vm Domain vm started In virt-viewer, the guest just shows: No bootable device Actual result: As above Expected result: If having a dev with **function='0x0' multifunction='on'** is mandatory to use **function='0x1/2/3...'** on a pci slot, libvirt should do the check and report error at first before vm start. This issue can be met when I deleted an existing devicec as follow: <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </memballoon> And it's tricky to find out what happened.