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.
After referring to the comments of the bug :https://bugzilla.redhat.com/show_bug.cgi?id=1256626
and tried on win2016 guest. The vlan-table is filled from 0~4095 too.
Therefore, I think this bug should be closed as NOTABUG
Description of problem: boot guest with "Ctrl_vlan=on" in cmd and check vlan table in rx-filter information when guest starts.It turns out that the vlan table is filled from 0~4095. Version-Release number of selected component (if applicable): host version: virtio-win-prewhql-162 kernel-4.18.0-48.el8.x86_64 qemu-kvm-3.1.0-0.module+el8+2266+616cf026 seabios-1.11.1-2.module+el8+2179+85112f94.src.rpm Guest: win2019-q35 How reproducible: 100% Steps to Reproduce: 1.boot a win2019 guest with cmd: /usr/libexec/qemu-kvm \ -M q35,kernel-irqchip=split \ -cpu host,+kvm_pv_unhalt,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time -name NIC2019x8664q35 -enable-kvm \ -m 3G -smp 4 -uuid cd270a7c-fdd8-11e8-bec6-1866daf23dc8 -nodefaults -rtc base=localtime,driftfix=slew -boot order=cd,menu=on \ -device piix3-usb-uhci,id=usb,bus=pcie.0 \ -drive file=net.raw,if=none,id=drive-ide0-0-0,format=raw,cache=none \ -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,share-rw=on -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=isa_serial0 -device usb-tablet,id=input0 \ -vnc 0.0.0.0:0 -vga std \ -qmp tcp:0:4445,server,nowait -monitor stdio \ -device pcie-root-port,id=pcie.0-root-port-4,slot=4,chassis=4,addr=0x4,bus=pcie.0 \ -netdev tap,script=/etc/qemu-ifup,downscript=no,id=hostnet0,vhost=on,queues=4 \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:52:3b:35:88:00,mq=on,vectors=10,bus=pcie.0-root-port-4,status=on,ctrl_vlan=on \ -cdrom /home/kvm_autotest_root/iso/ISO/Win2019/en_windows_server_2019_x64_dvd_4cb967d8.iso \ -drive file=virtio-win-prewhql-0.1-162.iso,format=raw,if=none,id=drive2,media=cdrom,readonly=off -device ide-drive,drive=drive2,bus=ide.1,unit=0,id=cdrom \ 2.check vlan table in rx-filter information in QMP: {"QMP": {"version": {"qemu": {"micro": 92, "minor": 0, "major": 3}, "package": "qemu-kvm-3.1.0-0.module+el8+2266+616cf026.next.candidate"}, "capabilities": []}} { "execute": "qmp_capabilities" } {"return": {}} {"timestamp": {"seconds": 1544674318, "microseconds": 301614}, "event": "NIC_RX_FILTER_CHANGED", "data": {"name": "net0", "path": "/machine/peripheral/net0/virtio-backend"}} { "execute": "query-rx-filter", "arguments": { "name": "net0" } } Actual results: {"return": [{"promiscuous": false, "name": "net0", "main-mac": "00:52:3b:35:88:00", "unicast": "normal", "vlan": "normal", "vlan-table": [4095, 4094, 4093, 4092, 4091, 4090, 4089, 4088, 4087, 4086, 4085, 4084, 4083, 4082, 4081, 4080, 4079, 4078, 4077, 4076, 4075, 4074, 4073, 4072, 4071, 4070, 4069, 4068, 4067, ...................... 54, 53, 52, 51, 50, 49, 48, 47, 46, 45, 44, 43, 42, 41, 40, 39, 38, 37, 36, 35, 34, 33, 32, 31, 30, 29, 28, 27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0], "unicast-table": [], "multicast": "normal", "multicast-overflow": false, "unicast-overflow": false, "multicast-table": ["33:33:ff:8b:8b:db", "01:00:5e:00:00:01", "33:33:00:00:00:01"], "broadcast-allowed": false}]} {"timestamp": {"seconds": 1544674326, "microseconds": 399397}, "event": "NIC_RX_FILTER_CHANGED", "data": {"name": "net0", "path": "/machine/peripheral/net0/virtio-backend"}} Expected results: vlan-table is [] for RHEL8.0 guest. Additional info: 1)After doing the steps mentioned above and then set vlan id =1 in device manager,check the vlan-table again , the result is: "vlan-table": [1] Then shutdown and boot guest with "ctrl_vlan=off", check the vlan-table again , the result is: the vlan-table is filled from 0~4095. 2)for rhel7.6 guest, not hit this issue, with "ctrl_vlan=on" in cmd and then check vlan-table info in QMP , the result is : {"return": [{"promiscuous": false, "name": "net0", "main-mac": "00:52:3b:35:88:00", "unicast": "normal", "vlan": "normal", "vlan-table": [0], "unicast-table": [], "multicast": "normal", "multicast-overflow": false, "unicast-overflow": false, "multicast-table": ["01:00:5e:00:00:fb", "33:33:ff:35:88:00", "33:33:00:00:00:01", "01:00:5e:00:00:01"], "broadcast-allowed": false}]}