Hyper-V Support For More Than 7 Virtual Cores Or More Than 30 GB RAM

Last Modified

Mon Jun 17 14:57 GMT 2019

Description

• There is a bug with the Linux Kernel and Hyper-V that it cannot handle more than one NUMA node. https://technet.microsoft.com/en-us/library/dn720239.aspx.

Environment

• N-able N-central 10.0 and later
• Microsoft Hyper-V

Solution

• If you use Hyper-V to host N-able N-central , and you have more than 7 cores or more than 30 GB of RAM configured, please open a case to have Support disable NUMA in the kernel.

If you are upgrading from N-able N-central 9.x and you are using Hyper-V, deploying newly on Hyper-V, or simply upgrading resources, perform the following check:

1. Open up the Hyper-V Manager and locate the N-able N-central VM.
2. Shut down N-able N-central .
3. Edit the Settings of the VM.
4. Expand out the Processor section on the left.
5. Under the NUMA section, adjust the Maximum number of NUMA nodes allowed on a socket, Maximum number of processors and Maximum amount of memory until you are able to adjust the NUMA nodes listed in the top section to 1.
6. Click OK to save.
7. Start up N-able N-central and proceed with the upgrade.
8. Once upgraded, open a case with Support to disable NUMA in the Kernel on your server.
9. Once confirmed that Support has made the change, shut down N-able N-central and set your memory and CPU limits back where you need them for as per our System Requirements Guide.