The video demonstrates step by step a Windows 2016 server installation on Proxmox VE. If your distribution does not provide binary drivers for Windows, you can use the package from the Fedora Project. These drivers are digitally signed, and will work on 64-bit versions of Windows: Latest VirtIO drivers for Windows from Fedora. Code signing drivers for the Windows 64bit platforms. Drivers should be signed for Windows 64bit.
A (hopefully) fool-proof guide on how to install a Windows 10 installation on Proxmox VE. The right way. Given:. A Windows 10 ISO (Need one? I suggest looking at the Media Creation tool ). A stable VirtIO ISO (Start by looking ). A Proxmox VE Installation Instructions:.
Upload both the Windows 10 and VirtIO ISOs to your node’s local storage. Click on “Create VM”. Assign VMID and Name, click “Next” to go to the OS tab. Select “Windows 10/2016”, click “Next” to go to the CD/DVD tab.
Select your Windows 10 ISO, click “Next” to go to the Hard Disk tab. Choose “VirtIO” as your Bus. Specify your storage location and size. Remember, the minumum storage is 16 GB for a 32-bit OS and 20 GB for a 64-bit OS. Under cache, select “Write back” (this increases performance, but is slightly riskier).
Click “Next” to go to the CPU tab. Assign as many sockets and cores as your environment permits. 2 cores and 2 sockets is often optimal, under normal circumstances, depending on your environment. Click “Next” to go to the Memory tab. Assign Ram as needed. Remember, the minimum memory is 1 gigabyte (GB) for 32-bit and 2 GB for 64-bit. Click “Next” to go to the Network tab.
Select “VirtIO (paravirtualized)” as the Model. All other settings are subject to your environment. Click “Next” to go to the Confirm tab.
Confirm all settings and click “Finish”. After your new VM tab appears on the left, look at its hardware settings. Add a second CD/DVD, choose the VirtIO iso as the image.
Boot your VM, open the console. The VM should boot the Windows 10 ISO. Proceed with the installation as normal. When you hit the “Which type of installation do you want?”, select “Custom: Install Windows only (advanced)”. You will get a notice that you don’t have the storage drivers necessary for Windows to detect a hard drive.
Select “Load Driver”, then browse to the virt-win CD. Drill down to viostor w10 amd64 and click “OK”. Windows will detect the “Red Hat VirtIO SCSI controller” driver.
Click “Next”. The hard drive will now appear. Partition the drive as you see fit, or just click “Next”. Windows will begin the installation process.
Depending on your environment, this may take a few minutes. The installation will reboot. At this point, you may remove the Windows 10 ISO (or the entire CD/DVD Drive) via the Hardware tab in Proxmox, but keep the VirtIO ISO. We’ll need it for networking and the memory balloon drivers.
Continue setting up Windows by configuring your location, keyboard, username, password, password hint, privacy settings, etc. You’ll notice that when the “connect to a network” tab appears, there’s no options available. Once you have an actual desktop, open up the Device Manager. You’ll notice two devices with missing drivers: Ethernet Controller (The VirtIO Network Card) and PCI Device (Memory Ballooning). Update the Ethernet Controller driver by navigating to the virtio-win CD. Drill down to NetKVM w10 amd64 and click “OK”.
Windows should detect and install the “Red Hat VirtIO Ethernet Adapter”. Your VM should be able to access network features, provided your hardware was appropriately configured. Update the PCI Device driver by by navigating to the virtio-win CD. Drill down to Balloon w10 amd64 and click “OK”. Windows should detect and install the “VirtIO Balloon Driver”. You can remove the virtio-win CD (or the CD/DVD Device) in the VM’s Hardware tab on the Proxmox GUI. Bear in mind that you can remove the ISO immediately.
Removing the device requires you to shutdown the VM. The Red lines will be there until you shutdown and start the VM from Proxmox. Posted on Author Categories, Tags. Sam, Yes, I paid for a subscription, but only because I took the Proxmox course in DC and it was offered at a discount. Let’s see if we can’t solve your issue: By default, you should be able to upload ISOs to your local storage (not local-lvm). If that’s not the case, check out your Datacenter view and click storage. Double click your local storage.
Look at the content drop down and ensure that “ISO image” is selected (this drop down is multi select). See the screenshot below. Hopefully this helps.
I use Ubuntu 12.04 64-bit and KVM, my CPU is Core i5 3.3 GHz and I have 8 GB of DDR3 RAM. I run Windows 7 in KVM and it's extremely slow. My co-worker use Debian on the same PC configuration and can run Windows 7 extremely fast! Where can be my problem?
guyfawkes@guyfawkes-pc /work$ sudo cat /etc/libvirt/qemu/windows.xml
Changes to this xml configuration should be made using: virsh edit windows or other application using the libvirt API. windows 5c685175-baea-0ca6-591f-8269d923ffb8 20152 1 hvm destroy restart restart /usr/bin/kvm UPD: I've enabled Intel-VT before installing KVM. I've successfully installed VirtIO drivers, and it gave me a few of performance, but, for example, when I open Firefox in Windows, even mouse moves very slowly, and GUI is very slow too. Thx - the - Storage format: raw - Cache mode: none (not default!) - I/O mode: native - + Disk bus: SATA did it.
'Expanding Windows files' during Win7 Installation did start counting up immediately after the change instead of hanging around @ 0% for hours. I wonder why disabling caching does the trick, as I tried first attempt with SATA NATIVE and Caching (Writeback), which sucked completely, and SATA NATIVE with caching set to NONE solved it obviously.Normally I'd expect a performance gain from writeback caching?
– user97113 Jan 5 '15 at 15:12. For a start, you've got the VM configured to be emulating an IDE bus, which is pretty slow. Try changing it to a SATA bus. Better yet, install the in Windows 7, and change it to a virtio bus. NOTE: Windows may complain about the hardware being changed underneath it, and may have difficulty finding the boot disk after it has changed from IDE to SATA or Virtio. Similarly, you will get improved network performance if you change the NIC type to virtio. What version of KVM and kernel are you running on ubuntu?
And what version of same on debian? One other thing worth checking is: is your co-worker using a disk-image for the VM, same as you are, or are they using a raw disk partition or an LVM volume or similar? Disk-images are very slow compared to partitions or LVM. Using all your answers, I found my way in this order: Installation: HDD configuration like Sergey said. When creating the VM with virt-manager, don't create the disk immediately (unclick 'enable storage.' ), clic 'customize configuration before install' on the next screen, and create the HDD manually just after, with this options: - Storage format: raw - Cache mode: none (not default!) - I/O mode: native - + Disk bus: SATA For me, the installation is done in less than 15min (rather than 27% of progression after more than 2H with default parameters) First reboot: - Disk bus: IDE (or windows will not boot) - Installation of the latest drivers1 (For that, devices management/install old components/type: storage) Halt the system, rechange the disk bus to virtio, reboot, that's it!