e155baefb0
The existing Nova's default machine type for ARMv7 ('vexpress-15') was
added more than four years ago (in commit: 5b27fe7: "libvirt: Allow
specification of default machine type"). The 'vexpress-15' board is a
specific development board, which has hardware limitations (like only
single ethernet adapter).
The upstream QEMU recommendation[1] for the past couple of years is to
use the 'virt' machine type for both ARMv7, and AArch64, which was
specifically designed to be used with virutal machines. Quoting a
write-up[2] from QEMU's ARM subsystem maintainer:
"Why the 'virt' board?
"QEMU has models of nearly 50 different ARM boards, which makes it
difficult for new users to pick one which is right for their
purposes. This wild profusion reflects a similar diversity in the
real hardware world: ARM systems come in many different flavours
with very different hardware components and capabilities. A kernel
which is expecting to run on one system will likely not run on
another. Many of QEMU’s models are annoyingly limited because the
real hardware was also limited — there’s no PCI bus on most mobile
devices, after all, and a fifteen year old development board
wouldn’t have had a gigabyte of RAM on it.
"My recommendation is that if you don’t know for certain that you
want a model of a specific device, you should choose the “virt”
board. This is a purely virtual platform designed for use in virtual
machines, and it supports PCI, virtio, a recent ARM CPU and large
amounts of RAM. The only thing it doesn’t have out of the box is
graphics, but graphical programs on a fully emulated system run very
slowly anyway so are best avoided."
So, change the default machine type for ARMv7 arch to be 'virt'.
[1] https://wiki.qemu.org/Documentation/Platforms/ARM
[2] https://translatedcode.wordpress.com/2016/11/03/installing-debian-on-qemus-32-bit-arm-virt-board/
Change-Id: If9ffa5a019f67734a9f30ccaf3ab96ff41262dc8
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
Team and repository tags
OpenStack Nova
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer, OpenStack Ironic and PowerVM.
Use the following resources to learn more.
API
To learn how to use Nova's API, consult the documentation available online at:
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst.
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests.
Further developer focused documentation is available at:
Other Information
During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for nova can be found at: