-
Notifications
You must be signed in to change notification settings - Fork 612
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
templates: add centos-stream-10 #3047
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've confirmed that the template works on aarch64, but shouldn't the image for x86_64 be commented out if it is known to be broken?
It still may work on somebody's machine? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, LGTM
May, but sounds unlikely. It is easy enough to uncomment the image setting to try. In the end we do want to know when it is working, and having to uncomment the image would give them a hint to let us know. But if you want to merge as-is, then go ahead. |
It did work in QEMU, on Linux |
Maybe it would help to disable the AVX512 support in the cpuType (i.e. not use "host") and go for AVX2 only? EL10 is known to not run on a lot of older Intel, which is why AlmaLinux re-enabled the support for "v2" https://almalinux.org/blog/2024-10-22-introducing-almalinux-os-kitten/
|
def895e
to
9ef71fd
Compare
9ef71fd
to
932bc9d
Compare
3ff6650
to
9ab2c69
Compare
Signed-off-by: Akihiro Suda <[email protected]>
9ab2c69
to
497b8e2
Compare
The same emulation issue also exists for centos-stream-9 (but didn't for centos-stream-8)
cpuType:
# Does not seem to boot with "qemu64"
x86_64: "Haswell-v4"
Edit: My bad, "Haswell-v4" does not mean x86_64-v4. |
Let's fix this separately in: |
No description provided.