So the next attempt is to try QEmu\/KVM on linux. QEmu\/KVM pretty much operate as a simple executable with a gazillion command line switches. Anything you can find that are a little user friendly are just a wrapper that passes the correct command line switches. <\/p>\n\n\n\n
Most of the UIs, do not polish the UI to organize the available features into intuitively arranged common use cases like HP\/Agilent\/Keysight\/Windows does. Most of the time it takes as much effort understanding the man pages spit out by –help switch as using their interface, and there’s a lot of common use scenarios overlooked that the user will end up having to look up the switches or enter the commands in the shell themselves.<\/p>\n\n\n\n
Libvrt is simply an XML tree that’s a near-direct translation of the command line arguments so you feel the entry looked more professional than saving the command line text is a shell script or batch file. I’m not impressed as it’s just more fluff as the structure do not help the users avoid studying the command line switches’ manual pages. <\/p>\n\n\n\n
QtEmu had promise (the interface looked like a half-developed version of VirtualBox’s Manager) but the project was not maintained anymore and Qemu’s command line switches’ evolution has escaped them so a lot of the functions are broken or missing.<\/p>\n\n\n\n
virt-manager do not have a compiled Windows binaries port. They have a virt-viewer for connecting to the sessions in Windows but it’s command line like SPICE. This is beyond frustrating. If you want something polished like a Hyper-V manager on Windows to manage Proxmox or linux QEmu clusters, forget about it.<\/p>\n\n\n\n
Proxmox is very incomplete when compared with Microsoft’s offerings, but it’s still better than nothing. At least it has a web interface that VNCs the screen back to you. <\/p>\n\n\n\n
You still cannot avoid actually understanding the long list of Qemu command switches as the UI only translates a few basic use cases into raw command switches which they show the raw string to you with the expectation that you’d figure out what to fix if they accidentally generated invalid combinations. <\/p>\n\n\n\n There are quite a lot of features (like setting up TAP) that still require shell command line entries, which they provided the interface so you don’t have to SSH separately into the Linux<\/p>\n\n\n\n Remember whatever Proxmox provided, it’s largely a pass through of the command line (switches) interface. Don’t get your hopes up assuming all the things a normal user would expect are there. You are expected to fill in the gaps by a lot of Googling. The UI is useful only if you know what you are looking for.<\/p>\n\n\n\n There are a few things Proxmox did right but overall it’s not an experience comparable to Microsoft’s management interface.<\/p>\n\n\n\n I have to give Proxmox credit for implementing PCI and USB passthrough\/mapping, which is often a pain in the butt to get the unique string from command line and hack together the right reference to mount the hardware.<\/p>\n\n\n\n I often hate people for squeezing all the UIs in a browsers when they shouldn’t. VNC is one of them. The reason is that when you are remote controlling another computer, you need to make sure most keystrokes goes to the VM, not the host, unless released. You cannot do this from within in a browser as the Alt-F4 closes the client’s browser, not the guest VM’s Windows!<\/p>\n![\"\"](\"https:\/\/wonghoi.humgar.com\/blog\/wp-content\/uploads\/2023\/09\/image-2-1024x385.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/wonghoi.humgar.com\/blog\/wp-content\/uploads\/2023\/09\/image-3.png\")
<\/figure>\n\n\n\nUSB mapping<\/h2>\n\n\n\n
![\"\"](\"https:\/\/wonghoi.humgar.com\/blog\/wp-content\/uploads\/2023\/09\/image-26-1024x616.png\")
<\/figure>\n\n\n\nVNC over WebUI is horrendous<\/h2>\n\n\n\n