jrapdx,
I was really interested in you explanation of Hyper-V and the VM's you created. Based on what you experienced, and assuming basic OS installation (specifically FreeBSD), would setting this up on my SP1 be workable? I am concerned about performance in relation to the limited 4GB RAM on the SP1. I know that upgrading to a SP2 would be in my best interests and I am working on that. I was hoping that for now I could at least play with Hyper-V and run just one VM at a time. Your thoughts and feedback are welcomed.
ATM I've got FBSD running in a VM, this browser (Firefox), and a few other processes under Win8.1, and according to Task Manager ~32% of RAM is used, or 2.6GB out of 8GB on this SP2. So 4GB RAM should be enough to run at least 1 VM without too much strain.
Factors other than RAM could affect performance, but are not "show-stoppers" depending on goals for using the VM facility. I wanted to be able to develop/maintain server software for our business. Ability to fix bugs, add features, etc., remotely was important. The goal was not running a complete desktop environment in the VM--that would be too resource intensive, slow and unnecessary for the purpose.
OTOH it is really cool to connect to the server running in the VM from Windows as it gives a realistic emulation of remote connection on the internet, yet in a contained environment. If the server crashes, it can be debugged in the VM--no harm done in the real world.
There are a few slightly tricky issues making this work, e.g., setting up network connections from the VM to Windows host, and to the "outside" internet at the same time. It's not too complicated once it's figured out. I'm happy to share the arcane details if you're interested.
Bottom line is running a not-too-fancy FBSD installation in a Hyper-V VM is quite practical for me, and very useful. There's zero penalty for trying it--it's completely reversible if it turns out not to work for you. As I said, glad to give pointers re: getting things to work, at least the parts I know about.