Running VM on the native-OS drive...Brave, man, brave. Anyway, welcome to kernel-based virtualization. If you ever wanted to know why people still pay money for VMware Workstation, you just found out.
I wanted to get away from both VMware and VirtualBox. They both served their purpose; VMware had the near-native Windows VM UI/graphics performance they specialize in, and VirtualBox did some neat oddball stuff for old-school nerds like me who were around when IBM still made both desktops and an OS to run on them. Alas, both are proprietary (no one uses VBox without the extensions, don't even go there). VMware can tank on you by doing one kernel update too many, and VBox is an Oracle property which means it can vanish at any time because they aren't profiting from it. I already had KVM in my own rack--first oVirt, then (and currently) Proxmox--and just wait until you find out how easy it is to spin up a VM on your desktop for testing and deploy it to the stack for server-type duties *without making any changes*. Ohhh, yeah.
Oh and that whole Windows VM graphics performance thing? I have witnessed VFIO and all its capabilities. To paraphrase Han Solo shortly before his kid shivved him: "It's true. All of it."
When bridged, I only do it with a machine about to be redone and without any pertinent data to worry about. But yeah, I would have been brave otherwise. :)
Running VM on the native-OS drive...Brave, man, brave. Anyway, welcome to kernel-based virtualization. If you ever wanted to know why people still pay money for VMware Workstation, you just found out.
I wanted to get away from both VMware and VirtualBox. They both served their purpose; VMware had the near-native Windows VM UI/graphics performance they specialize in, and VirtualBox did some neat oddball stuff for old-school nerds like me who were around when IBM still made both desktops and an OS to run on them. Alas, both are proprietary (no one uses VBox without the extensions, don't even go there). VMware can tank on you by doing one kernel update too many, and VBox is an Oracle property which means it can vanish at any time because they aren't profiting from it. I already had KVM in my own rack--first oVirt, then (and currently) Proxmox--and just wait until you find out how easy it is to spin up a VM on your desktop for testing and deploy it to the stack for server-type duties *without making any changes*. Ohhh, yeah.
Oh and that whole Windows VM graphics performance thing? I have witnessed VFIO and all its capabilities. To paraphrase Han Solo shortly before his kid shivved him: "It's true. All of it."
When bridged, I only do it with a machine about to be redone and without any pertinent data to worry about. But yeah, I would have been brave otherwise. :)
Excellent vm insights. Thanks for the comments.