Using ESXi since 4.1, 2 update problems because of "inperfect" HP ESXi plugins...
Also update problems when using the NUT component in ESXi (Removed NUT, updated, reinstall NUT works)
Never any problems, restored several Windows Servers, PCs running as Servers and several Windows boxes using proxmox's built in Backup System.
Migration from ESXi is also very fast for Windows boxes:
* - Make sure you have the .vmdk file (usually the LARGE *-flat.vmdk file)
* - Make a Backup of your VM to your NAS or whatever.
* - Remove VMTools
* - Reboot the VM
* - Load IDEmerge.exe
* - Load the three RedHat VirtIO drivers (NetKVM, Ballooning, VirtIO (SCSI)
* - Shut down the VM in ESXi (cleanly!)
* - Create a VM in Proxmox with roughly the same specs as your server had in ESXi (CPUs, RAM, Disksize!) but use VirtIO for Disk, RAM and Ballooning.
* - Take a note of the VM ID (A three digit number) Don't start this VM
* - Move the *-flat.vmdf file to the Prxmox Storage used (Either NAS or local) with whatever you prefer (SSH, Web...) to the folder containing your newly created VM with the right ID number. Usually something like /mnt/pve/DiskImage/images/123 or whatever ID you used.
* - Login to your ProxMox as root
* - cd to the folder (cd /mnt/pve/DiskImage/images/123 ...)
* - check the contents (!)
* - rename the existing *.qcow2 to *.qcow2_old
* - run the command "qemu-img convert YOUR-VM-DISKFILE-flat.vmdk -O qcow2 USE_THE_EXISTING_NAME.qcow2" to convert your VMDK to QCOW2 format. qemu-img automatically recognizes the VMDK format, I usually had problems if specifing the "-f vmdk" flag as often suggested.
This takes only a few moments!
Then fire up your VM in Proxmox and check for unusual stuff.
I've used this procedure to migrate XP, Win200 Server til Win2012 Server and Win7 / Win81 Workstations. Not yet tested with Win10, but should work too!
That usually needs a full Windows vCenter, but it's not surprising...
MS bought their way in (around 2006...) and has two Board members. Guess why after VMWare Server, with everything available for Windows AND Linux (UI and Server) there wasn't much linux momentum anymore?
And the WebUI is really crappy and sluggish, compared to the ESXi Console on Windows...
Grab the latest from here (fairly far down...): https://fedoraproject.org/wiki/Windows_Virtio_Drivers
These work VERY well! More Important is the MergeIDE, as Windows "identifies" IDE Disks by a SID like Number, and won't accept a change of controller. Grab it from here: https://pve.proxmox.com/wiki/File:Mergeide.zip
https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices (there's also one for Win7, 8...)
I'm running a small home ProxMox cluster with two Nodes version 5x, a third is coming soon. This provides a means to test Fail-Over and stability. A fail-over time of 1:30 Minutes is quite good, considering I'm using quite dated hardware servers, and my NAS and LAN aren't close to what's thought optimal. Like seperation of Normal-LAN from the Cluster-LAN and even a seperate Storage NAS / Backup NAS. But the setup works GREAT and stable.
My Home ProxMox Testing environment:
Here are two examples for a ProxMox environment, without any other LAN Stuff displayed...
As a "Wiener", german shouldn't be a problem, I'll provide english versons later...
Most of my SME clients are using a variant of Scheme Nr 1 (Simple)... And performance is very good!
Ideally, the ProxMox Storage would be on a fast NAS, with RAID10 (4 * WD Red Pro 4TB) and one for HotSpare inside a Synology DS1715+, for example.
Due to the fact that the VM Disks are stored on a NAS and redundant, the ProxMox could run say on a single SSD with 250 GB, these come fairly cheap now.
Activating SNMP (For say Zabbix ) on ProxMox is just as easy as installing NUT (or mc, screen, nano). It's Debian based, so the same apt-get install XXX as on a Raspberry works!
As to being "off Topic" - Best Practices in running your NethServer should never be considered Off topic!
In case anyone was wondering: I virtualised my last Win311 desktop sometime in 2000 (The disk still ran)
Had that in ESXi (Only VGA) and in Parallels (SVGA) and now in ProxMox (Still VGA, but SVGA possible). So that's what it looked like (With Norton Desktop):
Hope that satisfies your questions - go for it!