hyper-v tuning reccomendations

[dweberwr]

Are there any? I see there are for vmware.

[dweberwr]

I forgot to add, from what I can see I'm not seeing any issues, just more curious to see if I can squeek out any extra bit of performance out of this thing.

[Gr-R]

You can use the same settings as vmware:

1. From the console, press CTRL+ALT+W,
2. Select Tuning options -> iSCSI daemon options -> Target options,
3. Select the target in question,
4. change the MaxRecvDataSegmentLength and MaxXmitDataSegmentLength values to the
maximal required data size (check w/ the initiator to match).
maxRecvDataSegmentLen=262144
MaxBurstLength=16776192
Maxxmitdatasegment=262144
FirstBurstLength=65536
DataDigest=None
maxoutstandingr2t=8
InitialR2T=No
ImmediateData=Yes
headerDigest=None
Wthreads=8

[webguyz]

If you change these settings does it restart the NIC? Will I drop my connections to the virtual IP from my hosts? or is it very fast?

Have a production environment and don't want to screw it up.

[Gr-R]

The connections will be reset because of the frame size changes.
Since you need to check the initiators and adjust if needed, its advised to pause the host.(to be safe).
Normally, if you make the adjustments when an update is applied or other maintenance, its not an issue, since your likely to reboot at this point for some reason or another.
If in failover config, both nodes need to match, before failing over.

[To-M]

Changing these settings wont reset the nics or VIP but I would not do them while using the Failover, best to have this done first then enable the Failover.

[webguyz]

I wish there were a way to keep the Virtual IPs even when you don't have autofailover active. What I mean is being able to go into the secondary and turn off failover task and then go back to primary and turn off failover but have an option checkbox to keep the virtual IP's active on that primary server instead of reverting back to what they were originally. This way you could do things like change your ping nodes and other failover related items without shutting down the hosts that are connected to those Virtual IP's on VSS.

[To-M]

That is something the engineers have talked about and is a good request - this will take more time to have this VIP still beaconing out so the VM's dont have to be restarted - give us time on this. Thanks Webguyz!

[shawngrass]

You can use the same settings as vmware:

1. From the console, press CTRL+ALT+W,
2. Select Tuning options -> iSCSI daemon options -> Target options,
3. Select the target in question,
4. change the MaxRecvDataSegmentLength and MaxXmitDataSegmentLength values to the
maximal required data size (check w/ the initiator to match).
maxRecvDataSegmentLen=262144
MaxBurstLength=16776192
Maxxmitdatasegment=262144
FirstBurstLength=65536
DataDigest=None
maxoutstandingr2t=8
InitialR2T=No
ImmediateData=Yes
headerDigest=None
Wthreads=8

Do the above changes work on for XenServer 5.6?

[Gr-R]

Yes, working on Xen too.