Tips for Windows Server 2016 installation on Virtualization Station with virtio disk

English Container & Virtualization
1

I’ve spent a lot of times to find a way to install Windows Server 2016 in virtualization station.
My NAS is TS-453D with 32Gb ram. Firmware QTS 5.2.4.3079. Virtualization Station v4.0.0.270.

  1. virtio disks cannot boot from legacy BIOS
  2. Windows Server 2016 doesn’t have virtio drivers
  3. if you select UEFI Bios, it seems that Windows Server 2016 ISO doesn’t boot.

After hours of tests, I’ve found the way:

  1. select UEFI bios type
  2. in the VM configuration, select virtio as controller type for your boot drive
  3. create two CD devices and select IDE for controller type
  4. first CD .iso must be Windows Server, second must be virtio iso downloaded from RedHat. I’ve downloaded from Index of /groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.271-1 (virtio-win-0.1.271.iso)
  5. start the VM; boot will fail
  6. if you run the console, you will be in the UEFI shell
  7. Type in FS0: and hit enter
  8. You have to find the .efi file from where boot. In my case, I’ve typed:
    cd EFI
    cd BOOT
    dir
    Here is a .efi file. In my case:
    BOOTX64.EFI
  9. Now you will see the prompt "Press any key… ". Press it.
  10. The operating system starts installing.
  11. Proceed until it asks where do you want to install the OS; no disks will be present in the list
  12. Click on load driver and OK
  13. You should find a list of compatible drivers. Select the one for 2K16.
  14. Now the disk device should be available.

When OS is installed, I suggest to install all virtio drivers package from the iso. There is an executable in it.

Giacomo

1 Like
2

I installed a virtual Server 2019 not too long ago (TVS-h1288X) and the only thing I did, was to enable nested virtualization.

But I think on a low end Celeron NAS, it’s would just be a proof of concept…it would be slow as molasses

3

I didn’t try 2019. My test was on 2016.
Furthermore, if you have not selected VirtIO as controller type, there is no problems.
Last, it depends on where and how you use the server. If you install a server for domain controller, policies, for a small domain with few users, especially if you select a core installation without desktop experience, it works.

G