Hey all-
I’m trying to build my packages for EPEL-9 on my up-to-date F35 machine using Mock. I checked /etc/mock but can’t find any specific epel-9 config so I went with centos-stream+epel-next-9. Okay, fine, but when I run the job, it fails immediately with the error “Fatal glibc error: CPU does not support x86-64-v2”. The machine is a VM under ESXi with the following cpu info:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 42 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 8
On-line CPU(s) list: 0-7
Vendor ID: GenuineIntel
Model name: Intel(R) Xeon(R) CPU X7350 @ 2.93GHz
CPU family: 6
Model: 15
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 2
Stepping: 11
BogoMIPS: 5851.73
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts mmx fxsr sse sse2 ht syscall nx lm constant_t
sc arch_perfmon pebs bts nopl tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni ssse3 cx16 x2apic tsc_deadline_timer h
ypervisor lahf_lm pti tsc_adjust dtherm
Virtualization features:
Hypervisor vendor: VMware
Virtualization type: full
Caches (sum of all):
L1d: 256 KiB (8 instances)
L1i: 256 KiB (8 instances)
L2: 8 MiB (2 instances)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-7
Vulnerabilities:
Itlb multihit: KVM: Mitigation: VMX unsupported
L1tf: Mitigation; PTE Inversion
Mds: Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host state unknown
Meltdown: Mitigation; PTI
Spec store bypass: Vulnerable
Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Spectre v2: Mitigation; Full generic retpoline, STIBP disabled, RSB filling
Srbds: Not affected
Tsx async abort: Not affected
I guess there was some CPU requirement change that I didn’t catch; is this going to make creating Fedora-based VMs difficult going forward? I don’t have the money to upgrade my equipment. :(
Ron
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
