About a year ago I started to use VirtualPC 2007 on my Vista x64 box to allow me to run other instances of OS's within isolation without requiring me to purchase anymore hardware for my desk. It's actually rather simple to do and makes it extremely easy to roll back any of your systems to a previous state in case they get screwed up by installing beta software or for any other reason.
Benefits of Virtualization
To backup a virtual machine, all you do is burn the virtual machines files to a DVD. And, to restore, all you do is copy those backups over the existing files, and things are restored to a previous state. Simple, clean and straight forward.
Also, another benefit to using virtual machines is you only have to install and activate Windows XP or Vista once. Once you've installed and activated, all you need to do to install a new instance is copy the virtual machine files for the "fresh" install from your backup to a folder of their own on your machine and you have a whole new virtual machine to play around with.
How I've been using Virtualization
One thing that's been lacking in my use of virtualization (using VirtualPC 2007) is the fact that I have still been using the main installation on my machine for my own general purpose (development, testing, some games, etc.) use. And, the only thing I've been using virtualization for, thus far, is for testing out new software or beta software. This is fine and all, but it still puts my machine at risk of getting messed up from the usual install and uninstall of random things, and getting full of alot of software being installed that just plain slows down the machine and such.
What's new in Virtualization?
The latest from Microsoft is Hyper-V for Windows Server 2008. I'm still reading up on exactly what Hyper-V is, and what it's benefit are over Virtual Server 2005 and VirtualPC 2007.
According to Microsoft, Windows Server 2008 Hyper-V is:
"Windows Server 2008 Hyper-V, the next-generation hypervisor-based server virtualization technology, allows you to make the best use of your server hardware investments by consolidating multiple server roles as seperate virtual machines (VMs) running on a single physical machine. With Hyper-V, you can also efficiently run multiple different operating systems – Windows, Linux and others – in parallel, on a single server, and fully leverage the power of x64 computing."
Here are some links so you can learn more about Windows Server 2008 Hyper-V:
What I'm looking to do with Virtualization
Lately, I've been thinking about using Windows Server 2008 as the host OS on my main machine and using Vista and XP as guest OS's using virtualization. I'm looking to break out each of the roles I perform into separate virtual machines. So, basically I'm looking to having virtual machines for the following roles:
- Development - Mainly Visual Studio and SQL Express using Vista
- Testing - Probably have two virtual machines for this, one Vista and the other XP
- General Purpose - Mainly Office 2007 and CD/DVD burning software
- Playground - Use for testing new software and beta/alpha software. Probably have a couple VM's for this, including one with Visual Studio for testing out "found code" and open source code downloaded from internet.
- Gaming - Install any games I play here
You may be thinking that I could use Virtual Server 2005 to do this, but it doesn't support Vista as the host OS and you can't see Vista's "Aero" Glass while using remote desktop from a non-Vista OS. And, I just plain like the way Vista looks, so that's out of the question.
I can use VirtualPC 2007 with Vista as the host OS to do all this, and everything will be just dandy. However, since we now have Windows Server 2008 and Hyper-V, I might as well look at that as an option.
I'll post an update once I decide what I'm going to do to fill my virtualization needs.
But until then, if you have any virtualization suggestions and/or tips using VirtualPC, Virtual Server or Hyper-V, please post them in the comments.
This blog post is licensed under the Creative Commons Attribution 3.0 United States License, unless explicitly stated otherwise within the blog post content. All other content on this website is not licensed under Creative Commons licensing.