yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #88065
[Bug 1863728] Re: Nova can't create instances for a different arch
Reviewed: https://review.opendev.org/c/openstack/nova-specs/+/824044
Committed: https://opendev.org/openstack/nova-specs/commit/69ddbf090ef8c3c26aeb471a5c60bbf64536aa44
Submitter: "Zuul (22348)"
Branch: master
commit 69ddbf090ef8c3c26aeb471a5c60bbf64536aa44
Author: Jonathan Race <jrace@xxxxxxxxxxx>
Date: Mon Jan 10 13:13:12 2022 -0500
Adds Pick guest CPU architecture based on host arch in libvirt driver support
Implement new image meta property that allows for the selection of the
correct QEMU binary, cpu architecture, and machine type for a guest
architecture that is different than the host architecture; An x86_64
guest running on an AArch64 host, and vice versa.
Expanded and added content for nova scheduler and os-traits to
be leveraged by the prefilter, and added current support for proposed
architectures.
Implements: blueprint pick-guest-arch-based-on-host-arch-in-libvirt-driver
Closes-Bug: 1863728
Signed-off-by: Jonathan Race <jrace@xxxxxxxxxxx>
Change-Id: Iccfa53e06b44be3f8a70de6082fe0990b2ed23e8
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1863728
Title:
Nova can't create instances for a different arch
Status in OpenStack Compute (nova):
Fix Released
Bug description:
This is more a wish feature than a bug but considering the use cases
I'm surprised that it's not supported by nova.
*Support to create instances for a different architecture than the
host architecture*
My use case: Running ARM instances in x86_64 compute nodes.
This is not possible because nova always assume the host architecture.
Also, there's different assumptions considering the different architectures.
Some examples:
- cpu_mode for AARC64 is passthrough (not good if trying to emulate).
- Nova always checks the cpu_model against the host so is not possible to define an ARM cpu.
- architecture image property is not used for defining instance domain
(...)
This is mostly for discussion and to see if the community is
interested in supporting this use case.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1863728/+subscriptions
References