ASP.NET and Virtual Machines

I am beginning to install Hyper-V on one of my machines and set up a few virtual machines. I wanted to get some discussion going on if others are using this technology and what kind of issues you are having with ASP.NET.

This could be either development issues or production ones depending on what stage you are using virtualization for. One of my thoughts was to create multiple platforms for testing and staging as it would allow you to simulate a lot of different things without having to have multiple machines involved.

I am also interested in what type of hardware you are using to host your virtualizations. So let me know what you think and how you have things setup and of course problems you have come across. I will answer any questions that I can and I plan to post more as I get deeper into it with my own testing.

Published 28 May 08 12:18 by Tom

Filed under: ASP.NET, Hyper-V

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

# DotNetKicks.com said on May 28, 2008 12:19 PM:

You've been kicked (a good thing) - Trackback from DotNetKicks.com

# kjopc said on May 28, 2008 1:38 PM:

I'm thinking of using Windows 2008 Server as my development workstation because I could (potentially) run more powerful virtual machines.

I could use info on the recommended PC hardware requirements to run Hyper-V as a workstation tool.

Ken

MVP [ASP.NET]

# Tom said on May 28, 2008 3:11 PM:

Ken,

You can get the requirements from the Release Notes:

http://go.microsoft.com/fwlink/?LinkId=120241

Remember RAM is a good thing for virtualization

# Chris Jones said on May 28, 2008 11:02 PM:

We have just recently moved our development environment in house. We currently host approx 10 virtual machines on one host, obviously the box is beefy. It's got a terabyte raid 5 sata array, 8gb of ram and dual quad core processors.

We do asp.net development pretty much exclusively and have run into no major problems.

If you do have any questions let me know as well

# Saif Khan said on May 29, 2008 12:47 AM:

Don't forget disk IO. Think of it as the "rear end"...when he locks up everything gets blue :)

# 8bit said on May 29, 2008 11:10 AM:

I'm running on Mac Leopard here with VMWare Fusion -- works like a champ. I'm on a Macbook 2.16 C2D with 2 gigs of ram.

# Tanner said on May 29, 2008 3:07 PM:

My work environment could sure use some virtual machines to make life and development a bit easier to handle.

I look forward to your notes and findings, they will help me when it comes time to implement.

# Anthony Grace said on May 30, 2008 7:15 PM:

VMWare Workstation... using VS 2008 and ASP.NET 3.5, etc. Working like a charm :-)

# ASP.NET Debugging said on June 3, 2008 2:29 PM:

So I have begun working with Hyper-V, see my previous post here .  And it is really quiet an easy

# kjopc said on June 3, 2008 8:56 PM:

> You can get the requirements from the Release Notes:

It's easy to get the official list of pricey 64-bit name brand machines that support Hyper-V. However, I was thinking of saving money by buying a barebones system. It's hard to tell which processors are usable with Hyper-V.

# Tom said on June 4, 2008 9:57 AM:

Kjopc,

Hyper-V requires an x64-based processor, hardware-assisted virtualization, and hardware data execution protection. The Windows Server catalog, which can be found at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=111228), lists systems that are certified for Windows Server 2008. Systems supporting the x64 architecture and supporting Hyper-V can be identified by the additional maker under the text “Certified for Windows”.

Name (required)
Your URL (optional)
Comments (required)

Enter Code Here: Required
Remember Me?

Search

This Blog

Home
Email

All my posts are provided "AS IS" with no warranties, and confer no rights. All the expressions expressed herein are entirely my own and not necessarily those of Microsoft. In addition, thoughts and opinions often change. Because a weblog is intended to provide a semi-permanent point-in-time snapshot, you should not consider out of date posts to reflect current thoughts and opinions.

Your country's flag: