Bug 2020133 - Boot the windows 11 guest with 256 queues, qemu core dump
Summary: Boot the windows 11 guest with 256 queues, qemu core dump
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: qemu-kvm
Version: 8.6
Hardware: Unspecified
OS: Windows
Target Milestone: rc
: ---
Assignee: Marek Kedzierski
QA Contact: Lei Yang
Daniel Vozenilek
: 2139259 (view as bug list)
Depends On:
Blocks: 2020146 2025898
TreeView+ depends on / blocked
Reported: 2021-11-04 05:55 UTC by Lei Yang
Modified: 2022-12-29 16:25 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
.Using a large number of queues might cause Windows virtual machines to fail Windows virtual machines (VMs) might fail when the virtual Trusted Platform Module (vTPM) device is enabled and the _multi-queue virtio-net_ feature is configured to use more than 250 queues. This problem is caused by a limitation in the vTPM device. The vTPM device has a hardcoded limit on the maximum number of opened file descriptors. Since multiple file descriptors are opened for every new queue, the internal vTPM limit can be exceeded, causing the VM to fail. To work around this problem, choose one of the following two options: * Keep the vTPM device enabled, but use less than 250 queues. * Disable the vTPM device to use more than 250 queues.
Clone Of:
: 2020146 (view as bug list)
Last Closed:
Type: ---
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-101706 0 None None None 2021-11-04 05:56:09 UTC

Comment 7 John Ferlan 2021-11-24 12:51:46 UTC
NB: The zstream request above is essentially to have a RHEL-AV z-stream bug created back to include AV-8.4.0 and AV-8.5.0, see bug 2025898. A determination will need to be made at resolution time whether that request can be fulfilled and then the process to clone can be done.

Comment 22 Ke Ma 2022-11-03 09:44:29 UTC
*** Bug 2139259 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.