Bug 2003910 - The vm with 12 vfs can not be started successfully.
Summary: The vm with 12 vfs can not be started successfully.
Keywords:
Status: CLOSED DUPLICATE of bug 2001630
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: qemu-kvm
Version: 9.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Yanghang Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-14 06:53 UTC by Yanghang Liu
Modified: 2021-09-15 02:03 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-09-14 07:25:58 UTC
Type: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-97054 0 None None None 2021-09-14 06:53:42 UTC

Description Yanghang Liu 2021-09-14 06:53:22 UTC 
Description of problem:
The vm with multiple vfs (vf numbers > 12)can not be started successfully.

Version-Release number of selected component (if applicable):
host:
5.14.0-1.el9.x86_64
qemu-kvm-6.1.0-2.el9.x86_64
guest:
5.14.0-1.el9.x86_64

How reproducible:
100%

Steps to Reproduce:

1. create 12 VFs

echo 12 > /sys/bus/pci/devices/0000\:06\:00.1/sriov_numvfs 

2. start a RHEL90 vm with 12 VFs

The domaim xml is in the attachment

Actual results:
The vm is stuck on "Guest has not initialized the diaplay (yet)" page

Expected results:
The vm can be started successfully

Additional info:
(1) The vm with 11 vfs can be started successfully.
Comment 2 Yanghang Liu 2021-09-14 07:23:03 UTC 
This bug can be reproduced in qemu-kvm-6.1.0-1.el9.x86_64 and qemu-kvm-6.1.0-2.el9.x86_64.

The bug can not be reproduced in qemu-kvm-6.0.0-12.el9.x86_64
Comment 3 Yanghang Liu 2021-09-14 07:25:58 UTC 
This bug should be a duplicate bug of Bug 2001630 - [WRB][virtual network][qemu-6.1.0-1]Can not boot up guest with 14 devices via pcie-root-port.

*** This bug has been marked as a duplicate of bug 2001630 ***
Note You need to log in before you can comment on or make changes to this bug.