Originally Posted by Miyuki
Well, not just for TO alone, you can actually performs some "experiments" on the virtual OS, like "wreak havoc" on system configurations, or maybe try out some those antivirus software as well [just be careful]
Oh, I do that all the time, though most of my normal day-to-day virtualization takes place on two VMware vSphere (formerly known as "ESXi") boxen. I run tests on changes I plan to implement on my main production servers there (plus I run several VMs which handle my e-mail, DNS, routing, and phone system locally). Smaller-scale stuff that doesn't necessarily need to be on the vSphere boxen, I do on my desktop using VB
, like putz around with different OSes as well as have a bridge back to a Windows environment if I'm running a Unix-like system as a VM.
That said, I have several "builder" VMs whose sole purpose is for me to make sure crap doesn't break when I go to implement. If it works, great. If it breaks, I can figure out how to fix it to make it work, figuring what kind of "gotchas" might be in store so I can be ready when I do go live with those changes.
And I meant "irrelevant" in that one doesn't have to worry about putzing with Windows XP guest + drivers for Trickster's sake, now that the game can now be played directly under Windows 7 on the (hopefully) "bare metal" of the machine. Virtualization, as you and I astutely observe, is still very handy.