Closed manofthepeace closed 1 year ago
Please try a build passing -march=compatibility
to the native image build.
Please try a build passing -march=compatibility to the native image build.
That worked, thanks. I wonder if that should be a default in quarkus? or configurable separately.
@manofthepeace can you tell me where did you try to deploy? I've tested a few EC2 instance types, without any issues.
The image was built using azure pipelines and was deployed in an private internal lab/k8s cluster we have. That lab have older blades / cpus and could be the issue. I will be on PTO next week but will see if I can try in azure, where we usually deploy and I can report back, but I think that might be a non issue there as well as you found in aws.
Actual cpu(s);
[root@worker-node1 ~]# lshw -class cpu
*-cpu:0
description: CPU
product: Intel(R) Xeon(R) CPU E5-2658 0 @ 2.10GHz
vendor: Intel Corp.
vendor_id: GenuineIntel
physical id: 4
bus info: cpu@0
version: 6.45.7
slot: CPU socket #0
size: 2100MHz
capacity: 4230MHz
width: 64 bits
capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts mmx fxsr sse sse2 ss ht syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts nopl xtopology tsc_reliable nonstop_tsc aperfmperf eagerfpu pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 popcnt aes xsave avx hypervisor lahf_lm epb dtherm ida arat pln pts
configuration: microcode=0
I am using the following image to build
quay.io/quarkus/ubi-quarkus-graalvmce-builder-image
in a multistage build that then is used withquay.io/quarkus/quarkus-micro-image:2.0
When using
quay.io/quarkus/ubi-quarkus-graalvmce-builder-image:22.3.2-java17
and all the previous ones everything works, but when switching toquay.io/quarkus/ubi-quarkus-graalvmce-builder-image:jdk-17.0.7
I get the following.