Bug 2064569

Summary: VM BSOD during heavy network traffic after execute Set-NetAdapterrss
Product: Red Hat Enterprise Linux 9 Reporter: leidwang <leidwang>
Component: virtio-winAssignee: Yvugenfi <yvugenfi>
virtio-win sub component: virtio-win-prewhql QA Contact: Ke Ma <mama>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: coli, jinzhao, juzhang, qizhu, yvugenfi
Version: 9.0Keywords: Triaged
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Windows   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-15 10:45:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description leidwang@redhat.com 2022-03-16 07:43:09 UTC
Description of problem:
VM BSOD during heavy network traffic after execute Set-NetAdapterrss

Version-Release number of selected component (if applicable):
qemu-kvm-6.2.0-11.el9.x86_64
kernel-5.14.0-70.el9.x86_64
virtio-win-prewhql-0.1-215.iso
en_windows_server_2016_updated_feb_2018_x64_dvd_11636692.iso

How reproducible:
100%

Steps to Reproduce:
1:boot up a Win2016 guest
/usr/libexec/qemu-kvm \
-name 'avocado-vt-vm1'  \
-sandbox on  \
-machine pc,memory-backend=mem-machine_mem  \
-nodefaults \
-device VGA,bus=pci.0,addr=0x2 \
-m 14336 \
-object memory-backend-ram,size=14336M,id=mem-machine_mem  \
-smp 4,cores=1,threads=1,sockets=4  \
-cpu 'Broadwell',vme=on,ss=on,vmx=on,pdcm=on,f16c=on,rdrand=on,hypervisor=on,arat=on,tsc-adjust=on,umip=on,arch-capabilities=on,xsaveopt=on,pdpe1gb=on,abm=on,skip-l1dfl-vmentry=on,pschange-mc-no=on,hv_stimer,hv_synic,hv_vpindex,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_frequencies,hv_runtime,hv_tlbflush,hv_reenlightenment,hv_stimer_direct,hv_ipi,kvm_pv_unhalt=on \
-device pvpanic,ioport=0x505,id=id1G3jXD \
-device ich9-usb-ehci1,id=usb1,addr=0x1d.0x7,multifunction=on,bus=pci.0 \
-device ich9-usb-uhci1,id=usb1.0,multifunction=on,masterbus=usb1.0,addr=0x1d.0x0,firstport=0,bus=pci.0 \
-device ich9-usb-uhci2,id=usb1.1,multifunction=on,masterbus=usb1.0,addr=0x1d.0x2,firstport=2,bus=pci.0 \
-device ich9-usb-uhci3,id=usb1.2,multifunction=on,masterbus=usb1.0,addr=0x1d.0x4,firstport=4,bus=pci.0 \
-device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \
-device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=0x3 \
-blockdev node-name=file_image1,driver=file,auto-read-only=on,discard=unmap,aio=threads,filename=/home/win2016-64-virtio-scsi.qcow2,cache.direct=on,cache.no-flush=off \
-blockdev node-name=drive_image1,driver=qcow2,read-only=off,cache.direct=on,cache.no-flush=off,file=file_image1 \
-device scsi-hd,id=image1,drive=drive_image1,write-cache=on \
-device virtio-net-pci,mac=9a:46:ad:13:3a:bc,id=id6xTotb,netdev=idd4hdGS,bus=pci.0,addr=0x4,vectors=10  \
-netdev tap,id=idd4hdGS,vhost=on,queues=4 \
-monitor stdio \
-vnc :0  \
-rtc base=localtime,clock=host,driftfix=slew  \
-boot menu=off,order=cdn,once=c,strict=off \
-enable-kvm

2:execute the command in guest
Set-NetAdapterrss -name Ethernet -NumberOfReceiveQueues 1 -MaxProcessors 1 -Profile Conservative

3:Use speedtest to trigger some network traffic.


Actual results:
VM hit BSOD.

Expected results:
VM works well.

Additional info:

Comment 3 Yvugenfi@redhat.com 2022-03-16 10:07:15 UTC
Upstream PR: https://github.com/virtio-win/kvm-guest-drivers-windows/pull/734

Comment 9 errata-xmlrpc 2022-11-15 10:45:57 UTC
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 (virtio-win bug fix and enhancement update), 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/RHBA-2022:8261