How to speed up the work of a virtual machine on Proxmox?

Question

Virtualization

Hey!
There is a cluster of servers on Proxmox. They have virtual machines, mostly on Linux, but there are also on Windows (2013, 2019)
I ran into a problem that the speed of accessing disks on windows virtual machines is no. No more than 40MB/s for writing and 80MB/s for reading
I tried to install VirtIO drivers: - it got even worse. The write speed dropped to 8MB / s
Tell me, what are your virtual machine parameters and what actions did you do to make the disk speed normal? And then this, well, no way

The nominal speed of disks on the host, after installation, was around 500 MB / s

Colleagues! If you do not have Windows virtual machines - do not waste my time and yours.
I just need virtualok parameters and what drivers were installed.

Answer 1

Half a year ago I assembled a Proxmox cluster of three servers on old intel hardware.
There is no iron raid array, software and hardware is not supported. Installed Debian 10, assembled a soft Raid-1 array, LVM did not do it, because. I planned to replace 2 disks of 500 GB with 1 TB disks. LVM - not needed, because I decided to do such things in virtual machines, and not to pick the host system once again, and to increase productivity and avoid any hemorrhoids. Plus, soft Raid-1 on mdraid can be rearranged to any equipment, tk. FIG knows how long these old servers will live.
In general, Proxmox is designed to use remote file storage for flexible migration of VMs and containers. I have such happiness in the budget was not included.
Next, I tested the work of client OS:
1. WinXPSP3 - no firewood, not supported, forgotten (x32)
2. Win7SP1Pro (0EndOfSupport) - works fine, you can put firewood into the distribution via susprep (X64)
3. Windows 10 Enterprise 1803 - perfect (x64)
Conclusion: Virtual desktop it is possible to organize, but not yet necessary)
Naturally, first of all, server OS were tested:
1. Openwrt - for 128 MB of RAM - this is a miracle, and tor-proxy and routing - ideal for bypassing any Roskomnadzor protection and organizing a VPN to the system administrator's apartment. Be sure to use, little crap, a lot of buns.
2. Windows Server 2008 R2 - works like Win7, but is morally obsolete both as a Domain Controller and as a member server in general.
3. Windows Server 2012 R2 - ideal in terms of functionality, performance and goodies
4. Windows Server 2016 - I tried to use it under WSUS for a couple of months, it consumes a lot of resources, while it's still raw, more updates are needed for stable operation, but there are none yet, like in 2012R2. WSUS had to be abandoned and the VM removed.
5. Windows Server 2019 is a very raw and demanding OS, and my goal is to minimize disk space and RAM consumption, maximize performance and benefit.
6. Debian 9 - excellent, we take it into service.
7. Debian 8 - excellent, we take it into service.
8. CentOS 7 - excellent, I'm working on a mail server.
9. Windows Server 2003R2 - somehow, while drunk, I still managed to install some drivers and optimize the system, and even release an image for running ancient DOS applications)).
Conclusion: there are no problems with Linux, Windows2012R2 is an ideal option for both file and everything else.
After a three-month flight, I noticed that proxmox is actively using the swap of the host system, although there is more than half of the free physical RAM, and, as it turned out, this is also configurable.
In general, after working with VMWare Vsphere (ESXI) and Hyper-V, proxmox seemed to me to be a sysadmin's dream, and recently a proxmox backup server has also appeared.

Answer 2

Soft raid lvm virtio everything flies on Windows ten and 2019