D
Deleted member 116138
Guest
Hi @all.
Microsoft has released Windows Server 2022 (fe_release) build 20348.169.
I've set up 2 VMs running Server 2022 on two different PVEs (7.0-11), each VM with identical ressource mappings.
- 1 CPU socket, 2 cores
- 4GB static ram (no ballooning)
- BIOS: OVMF
- Machine: Q35-6.0
- VirtIO SCSI controller
- 1x HDD (scsi0) + 1x EFI Disk on SSD
- Network device: 1x VirtIO (paravirtualized), tagged VLAN 123 (< example only)
- Guest agent activated
- VirtIO windows drivers (ISO): 0.1.204
So setup went smooth without problems, added NetKVM, VIOSCSI and VIOSERIAL drivers during setup without problems. Within the PE i already could perform basic network commands after adding the NetKVM driver. Windows didn't have any undetected hardware and the guest-agent also worked.
At first I didn't realize any problems with the VirtIO NIC in each VM but then I decided to set up a test Active Directory environment. The first DC setup completed but as soon as I wanted to add the second VM as another DC (set VM1 as the primary and only DNS for VM2) Windows yelled that there is no DNS lookup for this domain possible. I could ping the IPv4 addresses from both VMs but VM2 couldn't perform any DNS operations with VM1 set as DNS server. Only IPv6 responses came back from VM1. Disabling IPv6 on both VMs didn't help for test purposes. Pings and nslookups of external hosts also failed from VM2 when querying VM1.
I tried with no luck:
- manually added the VLAN tag in each VM's NIC properties
- unticked the firewall options for each NIC within PVE
- removed the VLAN tags within PVE
- tried the previous VirtIO drivers (0.1.196)
- set up both VMs on two other PVEs
In the end I had to change the NIC model to Intel E1000 and everything worked without any problems.
Microsoft has released Windows Server 2022 (fe_release) build 20348.169.
I've set up 2 VMs running Server 2022 on two different PVEs (7.0-11), each VM with identical ressource mappings.
- 1 CPU socket, 2 cores
- 4GB static ram (no ballooning)
- BIOS: OVMF
- Machine: Q35-6.0
- VirtIO SCSI controller
- 1x HDD (scsi0) + 1x EFI Disk on SSD
- Network device: 1x VirtIO (paravirtualized), tagged VLAN 123 (< example only)
- Guest agent activated
- VirtIO windows drivers (ISO): 0.1.204
So setup went smooth without problems, added NetKVM, VIOSCSI and VIOSERIAL drivers during setup without problems. Within the PE i already could perform basic network commands after adding the NetKVM driver. Windows didn't have any undetected hardware and the guest-agent also worked.
At first I didn't realize any problems with the VirtIO NIC in each VM but then I decided to set up a test Active Directory environment. The first DC setup completed but as soon as I wanted to add the second VM as another DC (set VM1 as the primary and only DNS for VM2) Windows yelled that there is no DNS lookup for this domain possible. I could ping the IPv4 addresses from both VMs but VM2 couldn't perform any DNS operations with VM1 set as DNS server. Only IPv6 responses came back from VM1. Disabling IPv6 on both VMs didn't help for test purposes. Pings and nslookups of external hosts also failed from VM2 when querying VM1.
I tried with no luck:
- manually added the VLAN tag in each VM's NIC properties
- unticked the firewall options for each NIC within PVE
- removed the VLAN tags within PVE
- tried the previous VirtIO drivers (0.1.196)
- set up both VMs on two other PVEs
In the end I had to change the NIC model to Intel E1000 and everything worked without any problems.
Last edited by a moderator:
