You're not going to get much scale if you're dedicating NICs and spindles to ever single VM regardless of whether they need that kind of resource allocation...
Thanks, Brian Desmond [email protected] c - 312.731.3132 -----Original Message----- From: Bob Fronk [mailto:[email protected]] Sent: Monday, May 09, 2011 12:52 PM To: NT System Admin Issues Subject: RE: Configuring Hyper-V Server R2 Jim, A few things I do. (Running many HyperV hosts, each with two VMs. - A couple have more, but they are all very low resource) I like to have a dedicated NIC per each VM. You set this in the Virtual Network Manager. I do not share them with the OS. Remote management of the Host is done via a separate NIC. I like to have dedicated disk for each VM to keep the IO limited to that VM. I use servers that allow me to create a RAID1 with dedicated volume and place each VM on its own volume. All my hosts have at least 48GB Ram, and I share this fairly equally between OS and VMs. Some of the Hosts have more CPU available, but I try to judge the number of CPUs per VM based off the hardware available. Most of mine are at least dual CPU, dual core. Some have more due to the host having greater CPU numbers and cores. Is this the kind of information you are asking? BF -----Original Message----- From: Jim Majorowicz [mailto:[email protected]] Sent: Monday, May 09, 2011 11:54 AM To: NT System Admin Issues Subject: Configuring Hyper-V Server R2 I'm starting my trip into the world of hyper-visors, and because of my company status as a Microsoft partner and costs involve I chose Microsoft Hyper-V Server R2 as my hyper-visor platform of choice. I've got to say the documentation on the software leaves a bit it be desired. I realize I'm getting what I paid for it here, but I can't actually find squat about how to actually configure the base hardware beyond the basic install. I've downloaded, read and used "Microsoft Hyper-V Server 2008 R2 Getting Started Guide", "Hyper-V Server 2008 Setup and Configuration Tool Guide" and made great use of John Howard's "Hyper-V Remote Management Configuration Utility" and the blogs surrounding it, but I can't find squat about how to work with hardware after the software is installed. Do I really have to use DISKPART to setup and configure additional drive volumes? How would I address iSCSI and/or SAS volumes? I thought when I first set this up I'd be able to use a Remote Management GUI, which I admit, I am really kinda used to, but unfortunately I get the "RPC server is unavailable" message. Is this because I'm using the server in Workgroup mode? I'd rather not use Hyper-V on top of Windows 2008 R2 if I don't have too. I don't think that layer is necessary anymore, but I can't seem to find documentation that is helping me do what I want here. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
