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.
Please re-test with latest bits. I believe you will reproduce bug 1045175, but not be able to reproduce the call traces here. If so, please mark this a duplicate of 1045175.
(In reply to Alex Williamson from comment #4)
> Please re-test with latest bits. I believe you will reproduce bug 1045175,
> but not be able to reproduce the call traces here. If so, please mark this
> a duplicate of 1045175.
I cannot reproduce the call trace, neither deadlocks after removing ixgbe module from host.
And reload ixgbe in host doesn't trigger host crash any more mentioned in Comment 3.
slice of dmesg:
Dec 23 15:59:08 intel-e5530-8-2 kernel: [ 623.955585] kvm: zapping shadow pages for mmio generation wraparound
Dec 23 15:59:14 intel-e5530-8-2 kernel: [ 630.146021] ixgbe 0000:05:00.0 enp5s0f0: VF Reset msg received from vf 0
Dec 23 15:59:14 intel-e5530-8-2 kernel: [ 630.170367] ixgbe 0000:05:00.0 enp5s0f0: VF Reset msg received from vf 1
Dec 23 15:59:14 intel-e5530-8-2 kernel: [ 630.194683] ixgbe 0000:05:00.0 enp5s0f0: VF Reset msg received from vf 2
Dec 23 15:59:14 intel-e5530-8-2 kernel: [ 630.220211] ixgbe 0000:05:00.0 enp5s0f0: VF Reset msg received from vf 3
Dec 23 15:59:14 intel-e5530-8-2 kernel: [ 630.247088] ixgbe 0000:05:00.0 enp5s0f0: VF Reset msg received from vf 4
Dec 23 15:59:14 intel-e5530-8-2 kernel: [ 630.272430] ixgbe 0000:05:00.0 enp5s0f0: VF Reset msg received from vf 5
Dec 23 15:59:57 intel-e5530-8-2 avahi-daemon[833]: Withdrawing workstation service for enp5s0f1.
Dec 23 15:59:57 intel-e5530-8-2 kernel: [ 673.579630] ixgbe 0000:05:00.1: complete
Dec 23 15:59:57 intel-e5530-8-2 kernel: [ 673.603527] ixgbe 0000:05:00.0: removed PHC on enp5s0f0
Dec 23 15:59:57 intel-e5530-8-2 avahi-daemon[833]: Withdrawing address record for fe80::21b:21ff:fec3:d03c on enp5s0f0.
Dec 23 15:59:57 intel-e5530-8-2 avahi-daemon[833]: Withdrawing workstation service for enp5s0f0.
Dec 23 15:59:58 intel-e5530-8-2 kernel: [ 673.722832] ixgbe 0000:05:00.0: complete
Created attachment 710490 [details] host call trace on ixgbe removal Description of problem: Booted a guest with many 82599 VFs assigned, removing ixgbe on host triggered host call trace. Version-Release number of selected component (if applicable): qemu-kvm-1.4.0-1.el7.x86_64 3.8.0-0.40.el7.x86_64 How reproducible: 1/1 Steps to Reproduce: 1. boot a guest with 82599 VFs assigned 2. remove ixgbe on host 3. Actual results: Expected results: Additional info: /usr/libexec/qemu-kvm -name SR-IOV -M pc-i440fx-1.4 -cpu Nehalem -enable-kvm -m 4096 -smp 4,sockets=4,cores=1,threads=1 -uuid 8caf1895-52ef-4231-e4ec-73171b8b265b -nodefaults -rtc base=utc -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-scsi-pci,id=scsi0,bus=pci.0 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/root/sriov.raw,if=none,id=drive-scsi0-0-0,format=raw -device scsi-hd,bus=scsi0.0,scsi-id=0,drive=drive-scsi0-0-0,id=scsi0-0-0,bootindex=1 -netdev tap,id=hostnet0,vhost=on -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:6c:08:46,bus=pci.0 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0 -spice port=5900,disable-ticketing,seamless-migration=on -vga qxl -global qxl-vga.ram_size=67108864 -global qxl-vga.vram_size=67108864 -device intel-hda,id=sound0,bus=pci.0 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -balloon none -monitor stdio -device vfio-pci,host=06:1f.4,id=vf_061f4 -device vfio-pci,host=06:1f.2,id=vf_061f2 -device vfio-pci,host=06:1f.0,id=vf_061f0 -device vfio-pci,host=06:1e.6,id=vf_061e6 -device vfio-pci,host=06:1e.4,id=vf_061e4 -device vfio-pci,host=06:1e.2,id=vf_061e2 -device vfio-pci,host=06:1e.0,id=vf_061e0 -device vfio-pci,host=06:1d.6,id=vf_061d6 -device vfio-pci,host=06:1d.4,id=vf_061d4