On 9/29/26 18:22, axel zeuner wrote:
Hi All,
the flags were -cpu
EPYC-Rome-v4,fma4=off,tbm=off,xop=off,fsrm=off,erms=off,pcid=off,misalignsse=off,sse4a=off,cr8legacy=off,xsaves=off,mmxext=off,fxsr-opt=off,osvw=off,sha-ni=off,svm=off,vmx=off,cmov,cx8,fpu,fxsr,syscall,sse,sse2,cx16,lahf-lm,popcnt,sse3,ssse3,sse4.1,sse4.2,avx,avx2,bmi1,bmi2,f16c,fma,abm,movbe,xsave,xsaveopt,adx,aes,fsgsbase,rdrand,rdseed,rdtscp,x2apic,ibpb,stibp,virt-ssbd,amd-ssbd
For me, win11 guest does not boot in qemu 11.0 with just
`-cpu EPYC-Rome-v4`, while boots okay in qemu 10.0.
Where this cpu type come from?
There's no boot loop, it just sits there spinning CPU at 100% and nothing
seems to happen. Maybe this CPU type (the EPYC one) is not suitable for
my host (which is AMD Ryzen Zen3), and this is why it doesn't boot.
I dunno if this is the same problem as you're seeing, but here we go.
Holger, can you show which cpu/flags did you have which broke? I guess
your issue is different because it started with a later version of qemu.
But at least I can try to bisect the boot hang which I have, maybe
something will show up.
Thanks,
/mjt
