Still way more fiddley than need be. IMO. And he wants for it to be for use as his regular machine too if I read his first post correctly. So he’s going to be mapping his virtual web/audio/video/storage IO. Not every Windows app plays well with that arrangement. I’ve seen some popular financial apps get a little weird running in a VM. Also the same for apps with a lot of disk write and buffering activity. If the VM writes to the virtual HD and that doesn’t eventually get correctly pushed to the physical HD, you can get data corruption when you shutdown the VM. The giveaway is when you open an app in the VM and it immediately asks if you want to repair its database almost every single time. Drives are cheap, and muti-booting just seems easier and less subject to bad surprises to me when it comes to home use. In an enterprise environment where you’re running full virtualization on a Type-1 hypervisor with hardware and software failover, VMs are the only way to go. But for home use and a non-geek user, I think they’re still not quite the everyday solution they’re claimed to be.