Throughput Hyper-V

falumas · Oct 26, 2014, 11:12 AM

CentOS7 to CentOS7 both under Hyper-V 2012R2

–----------------------------------------------------------
[ 3] local 192.168.1.xxx port 55167 connected with 192.168.1.xxx port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 718 MBytes 602 Mbits/sec

pfSense to CentOS7 both under Hyper-V 2012R2

–----------------------------------------------------------
[ 9] local 192.168.1.xxx port 49626 connected with 192.168.1.xxx port 5001
[ ID] Interval Transfer Bandwidth
[ 9] 0.0-10.0 sec 174 MBytes 146 Mbits/sec

pfSense version
2.2-BETA (amd64)
built on Sat Oct 25 21:39:21 CDT 2014

FreeBSD 10.1-RC3

heper · Oct 26, 2014, 11:51 AM

what kind of virtual nics are you using? the legacy ones are crappy

falumas · Oct 26, 2014, 12:17 PM

I am using the once simply called Network Adapter (and not the ones called legacy adapters) for all my VMs.

hege · Oct 27, 2014, 6:11 PM

@falumas:

pfSense to CentOS7 both under Hyper-V 2012R2

[ 9] 0.0-10.0 sec 174 MBytes 146 Mbits/sec

That's really weak, any special configuration with the hyper-v network adapters?
(SR-IOV / Vlan / Enabled Bandwidth management / NIC Teaming / Disabled virtual machine queue / Disabled IPsec task offloading) ;D

Did you specify the MTU value manually, within pfSense?

falumas · Oct 27, 2014, 6:36 PM

My computer doesn't support VT-D so no SR-IOV.

I have tried both with and without VMQ and without gives me a 20Mbit lower value.

No NIC-teaming, IPsec task offloading is disabled.

MTU is untouched in pfSense.

hege · Oct 28, 2014, 11:29 AM

ok than I am out, sorry I have no idea what's the issue here. (but I don't think, that's a issue with pfSense)

falumas · Oct 28, 2014, 9:13 PM

Found this in the log of the Hyper-V server. I am using a fully updated Hyper-V 2012R2 core.

2.2-BETA (amd64)
built on Tue Oct 28 06:49:37 CDT 2014

FreeBSD 10.1-RC3

Networking driver in PfSense2.2 loaded but has a different version from the server. Server version 5.0 Client version 3.2 (Virtual machine ID C4EC369E-xxxx-xxxx-8A85-9DBFB85BFB0B). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.

Do I need to install integration services in pfSense 2.2 or are they included?

falumas · Oct 29, 2014, 8:28 AM

This is another thing I found in the logs which most likely didn't cause my problem, but it seems like the Hyper-V components need a boost.

A storage device in 'pfsense2.2' loaded but has a different version from the server. Server version 6.0 Client version 2.0 (Virtual machine ID 6D28DD84-xxxx-xxxxx-B799-AECCE8AF44E6). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.

Kofl · Oct 29, 2014, 9:10 AM

@falumas:

This is another thing I found in the logs which most likely didn't cause my problem, but it seems like the Hyper-V components need a boost.

A storage device in 'pfsense2.2' loaded but has a different version from the server. Server version 6.0 Client version 2.0 (Virtual machine ID 6D28DD84-xxxx-xxxxx-B799-AECCE8AF44E6). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.

That message can be ignored: http://support.microsoft.com/kb/2737297 (its not only valid for Windows but also for *inux, *BSD)

falumas · Oct 29, 2014, 9:42 AM

I do not have that message for any Win7, Win8, Win10 or CentOS7 guest.

Kofl · Oct 29, 2014, 9:58 AM

@falumas:

I do not have that message for any Win7, Win8, Win10 or CentOS7 guest.

Thats because for Win you are able to install the latest integration components directly from the Hyper-V host (which I assumed you did).
Try to run CentOS5 or 6 and you will get the same error/info message, because the Hyper-V server compares the Hyper-V Integration components version of the VM with that one, which is delivered directly with Hyper-V.

falumas · Oct 29, 2014, 10:16 AM

I am running CentOS6.5 as well but with the latest integration components installed.

This works fine for CentOS6.5
http://www.microsoft.com/en-us/download/details.aspx?id=41554

falumas · Oct 29, 2014, 10:23 AM

If any pfSense developer reads this thread here are instructions for the integration services for freeBSD.

https://wiki.freebsd.org/HyperV

falumas · Oct 31, 2014, 7:19 AM

I installed the FreeBSD 10.1RC3 yesterday and it is the same networkdriver included in that one.

Installing packageges in the RC3 is a nightmare, so I hope there are som FreeBSD gurus in the pfSense team that can install the Hyper-V package.

heper · Oct 31, 2014, 9:55 AM

there is little chance that integration services will improve your throughput.

falumas · Nov 2, 2014, 11:36 AM

No sadly not. I just got it installed on my FreeBSD10.1RC4

A storage device in 'FreeBSD10.1RC4' loaded but has a different version from the server. Server version 6.0 Client version 2.0 (Virtual machine ID E9446715-BC5D-4107-AE2E-D0D0C84F8415). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.

and still the same.

Seems that we have to wait until FreeBSD11 untill full Hyper-V support is there. But what we have now is still a hugh step forward for the pfSense Hyper-V support.

/Karl

falumas · Nov 2, 2014, 1:06 PM

It seems to be that the problem is biggest on low Power machines.

I have two hyper-v test machines one with a Atom S1260 (Dual Core + HT) and a Celeron J1900 (Quad core).

On the Atom I still get a throughput around 150Mbit, but today I tested on the Celeron and there I got around 500mbit.

/Karl

falumas · Nov 6, 2014, 1:02 PM

I did a fresh install of pfsense

2.2-BETA (amd64)
built on Wed Nov 05 21:26:57 CST 2014

FreeBSD 10.1-RC4-p1

This gave me slightly higher througput, I now have 260Mbit.

gjurriens · Nov 14, 2014, 6:40 AM

@Kofl:

@falumas:

This is another thing I found in the logs which most likely didn't cause my problem, but it seems like the Hyper-V components need a boost.

A storage device in 'pfsense2.2' loaded but has a different version from the server. Server version 6.0 Client version 2.0 (Virtual machine ID 6D28DD84-xxxx-xxxxx-B799-AECCE8AF44E6). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.

That message can be ignored: http://support.microsoft.com/kb/2737297 (its not only valid for Windows but also for *inux, *BSD)

Are you shure about this? The MS kb article talks about the client having a higher version of the intergration services than the server.
In the logs it's posted the other way around, so that would indicate there is room for inprovement !!