As I had quite a few troubles installing Windows Server 2k22 on Proxmox, I wanted to let everybody else know, how I managed to get it running.
I started with SeaBIOS and i440fx machine type (standard settings...), the VirtIO paravirtualized network interface and tried from the start a hard disk with SCSI bus (as it was mentioned in some videos just to select the vioscsi driver in the 2k19 folder from virtio-win-0.1.208.iso).
This occasionally gave me the error message that the drive cannot be used when selecting the drive for the OS installation. But I also managed to continue with the installation. Interestingly, at least when I set the administrator password, it was not just the VM that froze, but the entire Proxmox host. So it had to be a driver problem.
Still with SeaBIOS and i440fx machine, I changed the boot drive to IDE bus and I got the OS installed. Going on with installing the virtio win guest tools, the guest agent and the missing drivers in the Device Manager, I couldn't get the network adapter working, as well as a second mounted hard drive with SCSI bus for testing purpose. Installing the driver for the hard drive ended up with a 'driver installed with warnings', that the catalogue tables still needs to be implemented, or something like that.
I than read about using the q35 machine type, and ... oh wondering ... with an IDE bus drive I managed to install the OS and got the network adapter working with the same virtio-win drivers. But still had problems with the secondary mounted SCSI hard drive (drive offline, drive not dynamic, no option to initialize...). Till I stumbled over the amd64 folder in root of the iso mounted CD-ROM of the virt-io, where in 2k19 the vioscsi driver as well as the viostor driver is located. I read about the viostor driver in a post as well, so I just installed both drivers (vioscsi again and the viostor additionally), and my SCSI drive has allowed to be initiallized.
Just to mention: I changed the BIOS as well to OVMF (UEFI). And as you don't need the virtio-win-*.iso while installing the OS, I only had one disc drive (and the one OS hard drive on IDE bus).
At least I shut down the VM, unmounted the OS drive (IDE), changed the bus type to SCSI, mounted the drive again and activated it in the boot order again. Now I have a running Windows Server 2022 system with SCSI hard drives and VirtIO network adapter.
My config when installing:
agent: 1
bios: ovmf
boot: order=ide2;ide0;net0
cores: 8
efidisk0: hdd_2400gb_raid1:vm-201-disk-1,size=4M
ide0: hdd_2400gb_raid1:vm-201-disk-0,size=64G
ide2: local:iso/virtio-20348.169.210806-2348.fe_release_svc_refresh_SERVER_EVAL_x64FRE_de-de.iso,media=cdrom,size=5467348K //(resp. the virtio-win-0.1.208.iso)
machine: pc-q35-6.0
memory: 16384
name: fks2k22
net0: virtio=82:FA:4A:BB:94:4C,bridge=vmbr1,firewall=1
numa: 0
ostype: win10
scsi1: hdd_2400gb_raid1:vm-201-disk-2,size=1000G
scsihw: virtio-scsi-pci
smbios1: uuid=f06b8ad2-e522-4824-b623-55cfcd683ce6
sockets: 1
vmgenid: 5f3fb4cf-6cc9-45e2-b671-98d2b474a7d3
My final config:
agent: 1
bios: ovmf
boot: order=ide2;scsi0;net0
cores: 8
efidisk0: hdd_2400gb_raid1:vm-201-disk-1,size=4M
ide2: none,media=cdrom
machine: pc-q35-6.0
memory: 16384
name: fks2k22
net0: virtio=82:FA:4A:BB:94:4C,bridge=vmbr1,firewall=1
numa: 0
ostype: win10
scsi0: hdd_2400gb_raid1:vm-201-disk-0,size=64G
scsi1: hdd_2400gb_raid1:vm-201-disk-2,size=1000G
scsihw: virtio-scsi-pci
smbios1: uuid=f06b8ad2-e522-4824-b623-55cfcd683ce6
sockets: 1
vmgenid: 5f3fb4cf-6cc9-45e2-b671-98d2b474a7d3
I started with SeaBIOS and i440fx machine type (standard settings...), the VirtIO paravirtualized network interface and tried from the start a hard disk with SCSI bus (as it was mentioned in some videos just to select the vioscsi driver in the 2k19 folder from virtio-win-0.1.208.iso).
This occasionally gave me the error message that the drive cannot be used when selecting the drive for the OS installation. But I also managed to continue with the installation. Interestingly, at least when I set the administrator password, it was not just the VM that froze, but the entire Proxmox host. So it had to be a driver problem.
Still with SeaBIOS and i440fx machine, I changed the boot drive to IDE bus and I got the OS installed. Going on with installing the virtio win guest tools, the guest agent and the missing drivers in the Device Manager, I couldn't get the network adapter working, as well as a second mounted hard drive with SCSI bus for testing purpose. Installing the driver for the hard drive ended up with a 'driver installed with warnings', that the catalogue tables still needs to be implemented, or something like that.
I than read about using the q35 machine type, and ... oh wondering ... with an IDE bus drive I managed to install the OS and got the network adapter working with the same virtio-win drivers. But still had problems with the secondary mounted SCSI hard drive (drive offline, drive not dynamic, no option to initialize...). Till I stumbled over the amd64 folder in root of the iso mounted CD-ROM of the virt-io, where in 2k19 the vioscsi driver as well as the viostor driver is located. I read about the viostor driver in a post as well, so I just installed both drivers (vioscsi again and the viostor additionally), and my SCSI drive has allowed to be initiallized.
Just to mention: I changed the BIOS as well to OVMF (UEFI). And as you don't need the virtio-win-*.iso while installing the OS, I only had one disc drive (and the one OS hard drive on IDE bus).
At least I shut down the VM, unmounted the OS drive (IDE), changed the bus type to SCSI, mounted the drive again and activated it in the boot order again. Now I have a running Windows Server 2022 system with SCSI hard drives and VirtIO network adapter.
My config when installing:
agent: 1
bios: ovmf
boot: order=ide2;ide0;net0
cores: 8
efidisk0: hdd_2400gb_raid1:vm-201-disk-1,size=4M
ide0: hdd_2400gb_raid1:vm-201-disk-0,size=64G
ide2: local:iso/virtio-20348.169.210806-2348.fe_release_svc_refresh_SERVER_EVAL_x64FRE_de-de.iso,media=cdrom,size=5467348K //(resp. the virtio-win-0.1.208.iso)
machine: pc-q35-6.0
memory: 16384
name: fks2k22
net0: virtio=82:FA:4A:BB:94:4C,bridge=vmbr1,firewall=1
numa: 0
ostype: win10
scsi1: hdd_2400gb_raid1:vm-201-disk-2,size=1000G
scsihw: virtio-scsi-pci
smbios1: uuid=f06b8ad2-e522-4824-b623-55cfcd683ce6
sockets: 1
vmgenid: 5f3fb4cf-6cc9-45e2-b671-98d2b474a7d3
My final config:
agent: 1
bios: ovmf
boot: order=ide2;scsi0;net0
cores: 8
efidisk0: hdd_2400gb_raid1:vm-201-disk-1,size=4M
ide2: none,media=cdrom
machine: pc-q35-6.0
memory: 16384
name: fks2k22
net0: virtio=82:FA:4A:BB:94:4C,bridge=vmbr1,firewall=1
numa: 0
ostype: win10
scsi0: hdd_2400gb_raid1:vm-201-disk-0,size=64G
scsi1: hdd_2400gb_raid1:vm-201-disk-2,size=1000G
scsihw: virtio-scsi-pci
smbios1: uuid=f06b8ad2-e522-4824-b623-55cfcd683ce6
sockets: 1
vmgenid: 5f3fb4cf-6cc9-45e2-b671-98d2b474a7d3
