Date: Sun, 15 Dec 2024 19:21:16 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 283352] Hyper-V and VLAN dont work Message-ID: <bug-283352-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283352 Bug ID: 283352 Summary: Hyper-V and VLAN dont work Product: Base System Version: 14.2-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: michael.adm@gmail.com A certain bug was found, but it is not clear in what part of the system. Windows server 2022 21H2 (latest updates) Hyper-V and HPE Ethernet 10/25Gb 2-port 640FLR-SFP28 Adapter (firmware version 14.32.1900). Many virtual machines with different FreeBSD OS versions (14.2-STABLE and 15.0-CURRENT). With Mellanox windows driver version 23.x.xxx (HPE Mellanox CX4LX and CX5 Driver W2K22 v23.4.26054.0 Sep 12, 2023 - cp056041, HPE Mellanox CX4LX and = CX5 Driver W2K22 v23.10.26252.0 Apr 8, 2024 - cp059093) --> all works perfectly. With Mellanox windows driver version 24.x.xxx (HPE Mellanox CX4LX and CX5 Driver W2K22 v24.4.26429.0 Jul 15, 2024 - cp061096, HPE Mellanox CX4LX and = CX5 Driver W2K22 v24.7.26520.0 Nov 22, 2024 - cp062823) --> vlans in these VMs = can communicate with each other (only on the same Hyper-V switch), but not with other VMs on other hypervisors and not even from a VM on another virtual sw= itch of the same hypervisor. Networks in all VMs are configured according to this template: ifconfig_hn1=3D"inet 192.168.0.130 netmask 255.255.255.0" vlans_hn1=3D"128 172 ... ..." ifconfig_hn1_128=3D"inet 192.168.168.130 netmask 255.255.255.0" ifconfig_hn1_128_alias0=3D"inet 10.208.128.130 netmask 255.255.255.0" ifconfig_hn1_172=3D"inet 172.22.22.130 netmask 255.255.255.0" ifconfig_hn1_...=3D"..." >ifconfig: hn1: flags=3D1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metri= c 0 mtu 1500 options=3D8051b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4,LRO,LINK= STATE> ether 1a:1a:01:28:00:15 inet 192.168.0.130 netmask 0xffffff00 broadcast 192.168.0.255 media: Ethernet autoselect (10Gbase-T <full-duplex>) status: active nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> hn1.128: flags=3D1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> m= etric 0 mtu 1500 options=3D80000<LINKSTATE> ether 1a:1a:01:28:00:15 inet 192.168.168.130 netmask 0xffffff00 broadcast 192.168.168.255 inet 10.208.128.130 netmask 0xffffff00 broadcast 10.208.128.255 groups: vlan vlan: 128 vlanproto: 802.1q vlanpcp: 0 parent interface: hn1 media: Ethernet autoselect (10Gbase-T <full-duplex>) status: active nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> hn1.172: flags=3D1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> m= etric 0 mtu 1500 options=3D80000<LINKSTATE> ether 1a:1a:01:28:00:15 inet 172.22.22.130 netmask 0xffffff00 broadcast 172.22.22.255 groups: vlan vlan: 172 vlanproto: 802.1q vlanpcp: 0 parent interface: hn1 media: Ethernet autoselect (10Gbase-T <full-duplex>) status: active nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> External Switch is Brocade, configured as usual: ... interface TenGigabitEthernet 60/0/59 fabric isl enable fabric trunk enable switchport switchport mode trunk switchport trunk allowed vlan all switchport trunk tag native-vlan spanning-tree shutdown no shutdown ... VM network cards added like this: Add-VMNetworkAdapter -SwitchName R25G_P2 -VMName "zFRtest14-2" -Name "eth_test_vm_P0" -StaticMacAddress "1A-1A-01-28-00-16" Set-VMNetworkAdaptervlan -VMName "zFRtest14-2" -VMNetworkAdapterName "eth_test_vm_P0" -Trunk -AllowedVlanIdList "128,172" -NativeVlanId 1 If this is a HP bug then someone tell them about it because Hewlett Packard doesn't pay attention to ordinary people like me. Thanks in advance for your help. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-283352-227>