|
From: | Arndt Kritzner |
Subject: | Network interface problem with Windows Server 2016, 2019, 2022 and Windows 10 21H1 (qemu 6.1.0-5) |
Date: | Thu, 25 Nov 2021 22:55:49 +0100 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.14) Gecko/20080522 Thunderbird/2.0.0.14 Mnenhy/0.7.5.0 |
Hi,in my virtualization installation (current Arch linux, kvm, AMD, qemu 6.1.0-5, virtio 0.1.208.1-1) the guests network is configured with tun/tap interfaces and a network bridge. This works on W2012R2 Server guests with e1000 and virtio virtual network cards. W2012R2 guests get adresses via DHCP and can communicate (see first two attached screenshots). Newer Windows versions (2016S, 2019S, 2022S and 10 21H1) can't communicate - neither with virtual e1000 nor with virtio NIC (see last two screenshots).
This effect persists with all these different quemu parametrization variants: -net nic,model=virtio-net,macaddr=$macaddr -net tap,ifname=$IFACE -nic tap,model=virtio-net-pci,mac=$macaddr,ifname=$IFACE -netdev tap,id=n4,ifname=$IFACE -device virtio-net,netdev=n4,mac=$macaddr -netdev tap,id=vnet4,ifname=$IFACE,script=no,downscript=no -device virtio-net,netdev=vnet4,mac=$macaddr Any ideas to solve this problem or to investigate further in this? Kind regards Arndt
W2012R2S.e1000.2021-11-25_21-49-12.png
Description: PNG image
W2012R2S.virtio.2021-11-25_21-49-12.png
Description: PNG image
W2016S.e1000.2021-11-25_21-35-01.png
Description: PNG image
W2016S.virtio.2021-11-25_21-35-01.png
Description: PNG image
[Prev in Thread] | Current Thread | [Next in Thread] |