Getting error upgrading to version 10.7.0-1

Support Install / Uninstall
1

Hello, I am trying to install the Upgrade from 10.6.37-1 to 10.7.0-1 and I get a error after install trying to start Axigen.

CPU ISA level is lower than required

Did a change to CPU requirements happen between the versions? I rolled back to 10.6.37-1 and everything is working fine.

I am running .deb

Please help thanks

MT1

2

Hello,

Starting with Axigen 10.7.0, the Linux packages are compiled with the target architecture raised from x86-64 (v1) to x86-64-v2. This lets us take advantage of modern CPU instructions for improved performance.

Virtually all physical processors released after 2011/2012 (Intel Nehalem/Westmere or newer, AMD Bulldozer or newer) support x86-64-v2.

You can check if your current OS sees the required x86-64-v2 flags by running:

cat /proc/cpuinfo | grep -m1 flags | grep -o -E "sse4_1|sse4_2|ssse3|popcnt|cx16|lahf_lm" | sort -u

This will print whichever of the six required flags your CPU has. All six need to be present — if any are missing from the output, your CPU (or virtual CPU) doesn’t meet the x86-64-v2 requirement.

If one or more flags are missing, here is how to resolve it based on your setup:

  1. If you are running Axigen inside a Virtual Machine (VM): Most hypervisors (Proxmox, KVM, VMware, Hyper-V) default to a legacy virtual CPU model (like kvm64 or qemu64) that hides newer instruction sets from the guest OS. You can fix this by changing the VM’s CPU type to “Host” (or enabling Host CPU Passthrough). Important: a simple reboot from inside the guest OS is usually not enough — CPU flags are negotiated when the VM process itself starts. Please fully stop the VM, then start it again (not just restart/reboot the guest) for the new CPU type to take effect.

  2. If you are running on Bare Metal (Physical Hardware): The underlying hardware is physically missing one or more of the x86-64-v2 instruction sets. In this case, version 10.7.0 cannot run on this specific hardware, and you would need to either migrate to a newer CPU/server or remain on the 10.6.x branch.

Let us know if adjusting the VM settings (with a full stop/start) fixes it for you!

HTH,
Ioan

3

That did fix my issue. (Setting CPU to HOST) For some reason I had to update the cert on my phone but it is working. Thanks for the quick reply.

MT1