• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

hyper-v

Snooper

n00b
Joined
May 20, 2006
Messages
15
I have a question for the hyper-v enthusiasts on the H forums before I run off to maybe technet or some place...

Alright lets say I have a Hyper-V server with 2 quad port network adapters, I set 4 ports in an LACP group and connect them to 1 switch and the other 4 I do the same thing but connect to another switch and install proset on a guest vm, team the 2 connections in an slb group... Would this work, has anyone tried it?

I know hyper-v creates a virtual intel adapter so i was thinking proset would allow me to create a team, maybe!
 
There is a virtualization forum that is probably a better place for this, but that being said, being set up for a team at the guest level is going to require two separate vrtual swtiches going into the same network at the host level. I don't think that follow MS best practice for Hyper-V...

Anyway, the adapter emulated by the legacy driver emulation is a DEC 21140 10/100TX 100 MB (Intel based, but not Intel branded). It has much higher overhead than the Hyper-V optimized driver which is Microsoft's own creation from the ground up...

It is not actually limited to 100 Mbps, but it is way more resource intensive.

Ideally, you'd want to team the NICs at the host level rather than the guest level, and have them on one virtual switch. Then a single virtual NIC in the guest would be able to utilize all the connectivity redundancy.

If what you really need is the additional transmit or receive capacity rather than the redundancy, what you are planning to put in your VM isn't a good candidate for being a VM in the first place.
 
Back
Top