What would be a recommended initial virtual hardware configuration for Windows guests, under PROXMOX-VE?
While testing with Win10 and Win_srv_2019 guests, so far I got the following:
- if machine=q35, I don't get mouse in the installer
- SPICE won't work properly at the installation phase
- SPICE display will work well with SPICE console after installation+drivers, but noVNC console becomes unusable (mouse issues)
- display = standard VGA
- no storage controller from the list (LSI 53C895; LSI 53C810; Vmware PVSCSI) without additional drivers (MegaRAID SAS 8708 works with win_server)
-
I can install Windows guest as follows: (initial hardware)
- machine=i440fx; display=vga standard; storage = virtio; network=virtio; cdrom1 = windows installer ISO; cdrom2 = virtio drivers ISO
boot the machine, start the installation process. It won't find any storage devices, so you have to provide drivers for it. Browse to the virtio scsi for your windows version.
Installer does it's job.
First boot into the OS, go to virtio drivers CD, install the whole suite, including agent.
After this, I can change display to SPICE and benefit from the SPICE client, but have mouse problems if I am constrained to noVNC.
I presume virtio would be preferred as the most efficient given the KVM architecture behind it, while other hardware need additional emulation.
I also presume, should I want to migrate an existing windows VM from the likes of vmware to proxmox, I would first have to make a full install of drivers from virtio ISO in the guest, prior to migration.
My initial quest was for the hardware config that yields the simplest initial setup.
Also, combination of virtual hardware and steps doing this with the least issues along the way.
Does anyone have better suggestion(s) ? Thank you.
While testing with Win10 and Win_srv_2019 guests, so far I got the following:
- if machine=q35, I don't get mouse in the installer
- SPICE won't work properly at the installation phase
- SPICE display will work well with SPICE console after installation+drivers, but noVNC console becomes unusable (mouse issues)
- display = standard VGA
- no storage controller from the list (LSI 53C895; LSI 53C810; Vmware PVSCSI) without additional drivers (MegaRAID SAS 8708 works with win_server)
-
I can install Windows guest as follows: (initial hardware)
- machine=i440fx; display=vga standard; storage = virtio; network=virtio; cdrom1 = windows installer ISO; cdrom2 = virtio drivers ISO
boot the machine, start the installation process. It won't find any storage devices, so you have to provide drivers for it. Browse to the virtio scsi for your windows version.
Installer does it's job.
First boot into the OS, go to virtio drivers CD, install the whole suite, including agent.
After this, I can change display to SPICE and benefit from the SPICE client, but have mouse problems if I am constrained to noVNC.
I presume virtio would be preferred as the most efficient given the KVM architecture behind it, while other hardware need additional emulation.
I also presume, should I want to migrate an existing windows VM from the likes of vmware to proxmox, I would first have to make a full install of drivers from virtio ISO in the guest, prior to migration.
My initial quest was for the hardware config that yields the simplest initial setup.
Also, combination of virtual hardware and steps doing this with the least issues along the way.
Does anyone have better suggestion(s) ? Thank you.
