You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 28, 2023. It is now read-only.
QEMU uses the HAX_MAX_VCPUS. This is my patch for the QEMU to allocate the hax_vcpu_state as much as necessary (I tested this on the Linux host / Linux guest). I'm not sure other software using HAXM.
Is there anything to consider?
Currently, HAXM supports max 16 vCPUs per VM.
Considering recent multi-core CPUs (e.g., Xeon scalable processor), I think the current limit is small. KVM supports max 288 vCPUs.
It seems on NetBSD,
HAX_MAX_VMS * HAX_MAX_VCPUSpseudo devices are created at the module initialization, but on other platforms, a pseudo device is created when creating a vCPU (i.e., in thehax_vcpu_create_host()). So I think except for NetBSD, increasingHAX_MAX_VCPUShas no side effects.QEMU uses the
HAX_MAX_VCPUS. This is my patch for the QEMU to allocate thehax_vcpu_stateas much as necessary (I tested this on the Linux host / Linux guest). I'm not sure other software using HAXM.Is there anything to consider?