Replies: 2 comments
-
You don't have to add anything (i.e. you can remove it), unless you actually want to change a value... The new template will populate it with the default values automatically, if you leave # Specify desired QEMU CPU type for each arch.
# You can see what options are available for host emulation with: `qemu-system-$(arch) -cpu help`.
# Setting of instructions is supported like this: "qemu64,+ssse3".
# 🟢 Builtin default: hard-coded arch map with type (see the output of `limactl info | jq .defaultTemplate.cpuType`)
cpuType:
# aarch64: "max" # (or "host" when running on aarch64 host)
# armv7l: "max" # (or "host" when running on armv7l host)
# riscv64: "max" # (or "host" when running on riscv64 host)
# x86_64: "max" # (or "host" when running on x86_64 host; additional options are appended on Intel Mac) Also it doesn't actually do anything, with |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks !! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I was using 1.0.7 version earlier and in docker template. I was adding
arch: "x86_64"
memory: "21GiB"
cpuType:
Builtin default: "cortex-a72" (or "host" when running on aarch64 host)
aarch64: null
Builtin default: "cortex-a7" (or "host" when running on armv7l host)
armv7l: null
Builtin default: "qemu64" (or "host,-pdpe1gb" when running on x86_64 host)
x86_64: "Nehalem-v1,+abm,+acpi,+adx,+aes,+apic,+arat,+bmi1,+bmi2,+clflush,+clflushopt,+clwb,+cmov,+cr8legacy,+cx16,+cx8,+de,+erms,+fpu,+fsgsbase,+full-width-write,+hypervisor,+la57"
But with new template i am confused. Where and whether to add or not.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions