Nothing missed—that is another option.  Much easier to do in 2012 as well!

From: [email protected] [mailto:[email protected]] On 
Behalf Of Melvin Backus
Sent: Tuesday, August 19, 2014 5:31 AM
To: '[email protected]'
Subject: RE: [NTSysADM] Hyper-V versus VMWare

I could be mixing this with something else since it’s been quite some time 
since I looked at it, but I believe you can do NIC teaming on the host and 
point that vswitch to the team in order to increase the available capacity.

--
There are 10 kinds of people in the world...
         those who understand binary and those who don't.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Miller Bonnie L.
Sent: Tuesday, August 19, 2014 8:19 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [NTSysADM] Hyper-V versus VMWare

Yes it could, but depends on how many machines you put there.
1) If the machines are all communicating within the same host (for example, an 
MS NLB cluster), the traffic never leaves the box to even go out over the wire.
2)  If you need another virtual switch connection on the same network, you 
would have to connect another physical NIC and assign machines to that.  For 
example, for “Network Main” you want to add a second connection.  You plug in 
your cabling, and name them like “Network Main A” and “Network Main B”.  Then, 
alternate machines assigned to the switches based on what you need.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of CSSU NetAdmin
Sent: Tuesday, August 19, 2014 4:43 AM
To: [email protected]<mailto:[email protected]>
Subject: Re: [NTSysADM] Hyper-V versus VMWare

I checked out the HyperV course and it was quite helpful.  I am working with 
HyperV on Win2K12.  I don't get the virtual switches.  Creating one assigns 
only one physical nic to it yet you can have multiple VM's assigned to it.  
Does this create a bottleneck?  This is different than VMWare.

On Sun, Aug 10, 2014 at 10:16 PM, Damien Solodow 
<[email protected]<mailto:[email protected]>> wrote:
"It depends".
Which version of Hyper-V are you looking at? (Assuming 2012 R2)
What guest OS(es) do you need to support?
How many host servers do you have?
Do you have System Center licenses?

The reason for System Center is that System Center Virtual Machine Manager is 
the approximate equivalent for vCenter Server.
There is a Microsoft Virtual Academy course (free) that's HyperV & System 
Center for VMware admins that I'd highly suggest checking out.

DAMIEN SOLODOW
Systems Engineer
317.447.6033<tel:317.447.6033> (office)
317.447.6014<tel:317.447.6014> (fax)
HARRISON COLLEGE

________________________________________
From: [email protected]<mailto:[email protected]> 
[[email protected]<mailto:[email protected]>] on 
behalf of Kurt Buff [[email protected]<mailto:[email protected]>]
Sent: Sunday, August 10, 2014 10:08 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [NTSysADM] Hyper-V versus VMWare

I'll be very interested in hearing about this as well.

We're running VMware standard in production, but we're about to put up
Hyper-V in our DMZ, for the experience, if nothing else.

Kurt

On Sun, Aug 10, 2014 at 5:15 PM, CSSU NetAdmin 
<[email protected]<mailto:[email protected]>> wrote:
> We are exploring the benefits of VMWare vs. Hyper-V.  We currently use
> VMWare but it seems the Hyper-V might be more cost effective.  Anyone move
> from one to the other?
>
> Thanks for any input!!


Reply via email to