Skip to content
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.

Sign up for GitHub

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

Jump to bottom

VMs running via QEMU only expose SSE and SSE2 CPU features #60

Closed
kobalicek opened this issue Aug 6, 2023 · 2 comments
Closed

VMs running via QEMU only expose SSE and SSE2 CPU features #60

kobalicek opened this issue Aug 6, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@kobalicek
Copy link

Even when the host machine supports more advanced instruction sets like AVX/AVX2 - VMs only expose SSE and SSE2. At the moment it's not possible to test AVX code in these VMs. Xhyve exposes features up to AVX, but not AVX2, even when the host supports these extensions.

Is there any plan to perhaps add an option that would influence how many CPU features would be provided to the guest machine? I think at least AVX as exposed by xhyve would be great.
@jacob-carlborg
Copy link
Contributor

I can see if I can add more CPU features when using QEMU. As long as the OS boots I don't think it needs to be an option.

@jacob-carlborg jacob-carlborg added the enhancement New feature or request label Aug 6, 2023
jacob-carlborg added a commit that referenced this issue Aug 13, 2023
@jacob-carlborg
Fix #60: VMs running via QEMU only expose SSE and SSE2 CPU features
9ac53b7 
This changes the machine to `q35` and the CPU to `max`, for x86-64.
jacob-carlborg added a commit that referenced this issue Aug 13, 2023
@jacob-carlborg
fixup! Fix #60: VMs running via QEMU only expose SSE and SSE2 CPU fea…
5785003 
…tures
jacob-carlborg added a commit that referenced this issue Aug 13, 2023
@jacob-carlborg
fixup! Fix #60: VMs running via QEMU only expose SSE and SSE2 CPU fea…
d6465d2 
…tures
jacob-carlborg added a commit that referenced this issue Aug 13, 2023
@jacob-carlborg
fixup! Fix #60: VMs running via QEMU only expose SSE and SSE2 CPU fea…
f1862cd 
…tures
jacob-carlborg added a commit that referenced this issue Aug 13, 2023
@jacob-carlborg
fixup! Fix #60: VMs running via QEMU only expose SSE and SSE2 CPU fea…
5715872 
…tures
jacob-carlborg added a commit that referenced this issue Aug 13, 2023
@jacob-carlborg
fixup! Fix #60: VMs running via QEMU only expose SSE and SSE2 CPU fea…
7437e7e 
…tures
jacob-carlborg added a commit that referenced this issue Aug 17, 2023
@jacob-carlborg
fixup! Fix #60: VMs running via QEMU only expose SSE and SSE2 CPU fea…
7050b55 
…tures
@jacob-carlborg
Copy link
Contributor

Available now in v0.19.0.

jacob-carlborg added a commit that referenced this issue Oct 6, 2023
@jacob-carlborg
Fix #60: NetBSD - VM doesn't start after a 120s timeout
5abf98e
jacob-carlborg added a commit that referenced this issue Oct 6, 2023
@jacob-carlborg
fixup! Fix #60: NetBSD - VM doesn't start after a 120s timeout
3422a14
jacob-carlborg added a commit that referenced this issue Oct 7, 2023
@jacob-carlborg
Fix #60: NetBSD - VM doesn't start after a 120s timeout
9d8705d
korli added a commit to korli/action that referenced this issue Mar 15, 2024
@korli
Merge tag 'v0.19.0' into merge
b36786a 
Release 0.19.0

Changed
- VMs running via QEMU only expose SSE and SSE2 CPU features ([cross-platform-actions#60](cross-platform-actions#60)).
    This changes the machine to `q35` and the cpu to `max`, for x86-64 using
    the QEMU hypervisor. This adds more CPU features like AVX and AVX2.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jacob-carlborg @kobalicek