Jump to content
Welcome to our new Citrix community!

AMD EPYC support for Netscaler VPX 12/13 on XenServer


Konrad Ruess

Recommended Posts

Hello, I hope everybody is doing well in those crazy days....

 

Does anyone have any insights regarding the missing support for AMD EPYC CPU's in Citrix XenServer - oops, sorry: Hypervisor?

Is that something that is being worked on? I still can't believe that this support is not given and according to my investigations it's really only applying for XenServer but no other hypervisor. :57_cry:

 

Any hints, ideas, insights are welcome.

BfN, Konrad

Link to comment
Share on other sites

25 minutes ago, Konrad Ruess said:

Hello, I hope everybody is doing well in those crazy days....

 

Does anyone have any insights regarding the missing support for AMD EPYC CPU's in Citrix XenServer - oops, sorry: Hypervisor?

Is that something that is being worked on? I still can't believe that this support is not given and according to my investigations it's really only applying for XenServer but no other hypervisor. :57_cry:

 

Any hints, ideas, insights are welcome.

BfN, Konrad

 

Your information about Hypervisors is correct. It's not just limited to Citriox Hypervisor.

 

NetScaler VPX requires:

Processor requirements: Dual core server with Intel VTx.

Memory available: 2GB RAM(4GB in case of VPX running on 13.0 firmware), 20 GB hard drive 

Hypervisor: Citrix XenServer 5.6 or later; VMWare ESX/ESXi 3.5 or later, Windows Server 2008 R2 with Hyper-V

Connectivity: 100 Mbps minimum; 1 Gbps recommended

A network interface card compatible with the hypervisor

Note: AMD processors are not Supported.

 

The rumours I have heard about this restriction is: It seems to be due to SSL processing. AMD has a significantly different code set than Intel, and the code is optimized for Intel. I never tried, but as far as I know, it runs on ADM, but it detects very old Intel CPUs (so SSL performance is poor).

 

cheers

 

Johannes Norz

CTA, CCI, CCE-N

Link to comment
Share on other sites

Pfüet'di Johannes! :-)

 

Thank you for sharing your information. So, this does not sound really promising... :-(

 

The requirements listed in docs.citrix.com are very vague for some hypervisors (from ADC 13.0, but 12.1 looks pretty similar):

- XenServer: in the specific notes, it states that AMD is not supported

- ESXi: it only references Intel-VT, but no explicit denial of AMD

- Hyper-V: It does not explicitely name Intel nor AMD, also no virtualisation technology referenced (AMD-V / Intel-VT)

- KVM: Docs explicitely name AMD-V and Intel-VT as required platform, no unsupported items listed

- Azure: no references to either technology or hardware (but Azure offers both, Intel & AMD metals)

 

The way it behaves on our infrastructure:

- Management vCPU is running flat out for the 'pitboss' process

- No graceful shutdown possible

- Soon after starting the VPX, no SSH connection is possible, anymore

- Web GUI is still functional

- ADC services are running well (LB, vServer, SF proxy, ICA tunneling)

 

Interestingly, the Citrix ADM also causes head-aches (sshd terminates quickly after startup, GUI not accessible, 1 vCPU fully loaded), but for that VPX, we cannot find any restrictions regarding AMD EPYC or so.

 

Bleib gesund, Konrad

Link to comment
Share on other sites

4 minutes ago, Konrad Ruess said:

Pfüet'di Johannes! :-)

 

Thank you for sharing your information. So, this does not sound really promising... :-(

 

The requirements listed in docs.citrix.com are very vague for some hypervisors (from ADC 13.0, but 12.1 looks pretty similar):

- XenServer: in the specific notes, it states that AMD is not supported

- ESXi: it only references Intel-VT, but no explicit denial of AMD

- Hyper-V: It does not explicitely name Intel nor AMD, also no virtualisation technology referenced (AMD-V / Intel-VT)

- KVM: Docs explicitely name AMD-V and Intel-VT as required platform, no unsupported items listed

- Azure: no references to either technology or hardware (but Azure offers both, Intel & AMD metals)

 

The way it behaves on our infrastructure:

- Management vCPU is running flat out for the 'pitboss' process

- No graceful shutdown possible

- Soon after starting the VPX, no SSH connection is possible, anymore

- Web GUI is still functional

- ADC services are running well (LB, vServer, SF proxy, ICA tunneling)

 

Interestingly, the Citrix ADM also causes head-aches (sshd terminates quickly after startup, GUI not accessible, 1 vCPU fully loaded), but for that VPX, we cannot find any restrictions regarding AMD EPYC or so.

 

Bleib gesund, Konrad

 

Konrad, sure, you're right. I just found a note for HyperV (what ever this is). N note for VMWare or KVM (the biggest deployments I know - with more than 120 VPX in parallel) are deployed on KVM and VMWare).

Unfortunately it's not possible to give feedback to the guides any more.

 

Servus

 

Johannes

Link to comment
Share on other sites

  • 2 months later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...