Uploading an image from Hyper-V is extremely slow
-
@loosus456 does this server have Broadcom NICs in it by chance? If so, you can look into disabling Virtual Machine Queues.
-
Haven’t had a chance to look at everything just yet, but the version of FOG is 6321.
In regards to it being FastEthernet: it sometimes bursts as high as gig does, which is what makes me believe there is an issue.
-
@loosus456 Any news on this? Did you have time to look into all the suggestions and try things out?
-
@loosus456 Any resolution? Exact same symptoms here. Thanks.
-
@rdw I remember that there is a specific linux kernel argument for Hyper-V. I would guess that this would really help out - definitely wouldn’t hurt anything. I’ll see if I can find it…
-
https://technet.microsoft.com/en-us/library/dn720239.aspx
Since FOS (fog operating system) is linux, all that stuff could apply potentiall.
There is a kernel argument though. I have to get on a actual computer to find it…
-
If it is Hyper-V 2012 R2 and you are running a Generation 1 VM which uses the Legacy Network Adapter for PXE booting then 100 Mb is all you will get as the Legacy Network Adapter is only a 100 Mb NIC.
Having said that, some kernels in the past have on occasion switched to the 1Gb NIC for uploading … including right now. I just rolled back to 4.1.4 from 4.6.2 and I’m getting Gb.
-
I know it’s been a while, but I just came across this: http://www.funtoo.org/HyperV_Kernel_Configuration
These are the Hyper-V kernel arguments listed on that page, just so they aren’t lost in the depths of the internet:
HyperV Kernel Configuration
For a Hyper-V generation 2 system, you’ll need certain options enabled in the Kernel in this order because latter options aren’t available until earlier options are enabled:
CONFIG_HYPERVISOR_GUEST: Processor type and featueres > Linux Guest Support CONFIG_PARAVIRT: Processor type and features > Linux Guest Support > Enable paravirtualization code CONFIG_PARAVIRT_SPINLOCKS: Processor type and features > Linux Guest Support > Paravirtualization layer for spinlocks CONFIG_HYPERV: Device Drivers > Microsoft Hyper-V guest support > Microsoft Hyper-V client drivers CONFIG_HYPERV_UTILS: Device Drivers > Microsoft Hyper-V guest support > Microsoft Hyper-V Utilities driver CONFIG_HYPERV_BALLOON: Device Drivers > Microsoft Hyper-V guest support > Microsoft Hyper-V Balloon driver CONFIG_HYPERV_NET: Device Drivers > Network device support > Microsoft Hyper-V virtual network driver CONFIG_HYPERV_STORAGE: Device Drivers > SCSI device support > SCSI low-level drivers > Microsoft Hyper-V virtual storage driver CONFIG_HYPERV_KEYBOARD: Device Drivers > Input device support > Hardware I/O ports > Microsoft Synthetic Keyboard driver CONFIG_FB_HYPERV: Device Drivers > Graphics support > Frame buffer Devices > Microsoft Hyper-V Synthetic Video support CONFIG_HID_HYPERV_MOUSE: Device Drivers > HID support > Special HID drivers > Microsoft Hyper-V mouse driver
-
@Wayne-Workman This is what we have in the current config:
grep -e HYPERV -e PARAVIRT TomElliott.config.asc CONFIG_HYPERVISOR_GUEST=y CONFIG_PARAVIRT=y # CONFIG_PARAVIRT_DEBUG is not set # CONFIG_PARAVIRT_SPINLOCKS is not set # CONFIG_PARAVIRT_TIME_ACCOUNTING is not set # CONFIG_PCI_HYPERV is not set # CONFIG_SYS_HYPERVISOR is not set CONFIG_HYPERV_STORAGE=y CONFIG_HYPERV_NET=y CONFIG_HYPERV_KEYBOARD=y CONFIG_FB_HYPERV=y # CONFIG_HID_HYPERV_MOUSE is not set CONFIG_HYPERV=y CONFIG_HYPERV_BALLOON=y
Are you keen to compare those and let us know if we should any option.
-
Any update on this? I have just started universal imaging using Hyper-V, which is working great. However, the upload speed from VM to FOG-server is slow. Currently uploading now, and am getting >300MB/min