

Even with a desktop CPU upgrade, there is the risk that my existing motherboard won’t support valuable Xeon features (e.g., ECC RAM). It seems ESXi won’t work on my existing computers. If ESXi doesn’t work, Proxmox may be my best alternative.Īfter that, the following sections explain and explore relevant hardware components. These materials prompt me to consider ESXi the one that I might find easiest to learn, at least for my relatively simple purposes.

In pursuit of that objective, the text proceeds to review comments and issues affecting various type 1 hypervisors. The Win10 VM might still be a primary workspace, but I could continue to get work done in other spaces when Win10 was unavailable or uncooperative.

If I could run other VMs independently of Win10, I could perhaps assign some functions to Win7 or even WinXP VMs that would keep running their assigned tasks I could perhaps improve browsing security by doing my browsing in an Ubuntu VM. For one thing, if I ran Win10 in a VM, other functions could carry on even if Win10 crashed, was targeted by malware, or had to reboot to install updates. The Background section explains that I saw a type 1 hypervisor as a potential help in reducing my dependence on Windows 10. This post works through the search for hardware compatible with VMware’s ESXi type 1 hypervisor, for the purpose of running virtual machines (VMs) on a desktop computer.
