3f63c68195
The USB-based tablet is often the only USB device in an x86 instance, while the USB-based keyboard is often the only such device in an AArch64 instance (x86 have PS2 keyboards and mice). Replacing these with virtio-based devices can eliminate the need to have a USB host adapter in the instance. Enable just that possibility by adding a new value image metadata property, 'hw_input_bus'. This allows us to specify not only virtio-based pointer and keyboard input devices but also USB equivalents. Note that this also fixes one instance of a particular class of bugs, whereby we have checks for *guest* architecture-specific behavior that are being toggled based on the *host* architecture. In this instance, we were attempting to add a keyboard device on AArch64 guests since they don't have one by default, but we were determining the architecture by looking at the CPU architecture reported in the host capabilities. By replacing this check of the host capabilities with a call to the 'nova.virt.libvirt.utils.get_arch' helper, we correctly handle requests to create non-host architecture guests via the 'hw_architecture' image metadata property. There are many other instances of this bug and those can be resolved separately. Change-Id: If9f3ede3e8449f9a6c8d1da927974c0a73923d51 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
11 lines
533 B
YAML
11 lines
533 B
YAML
---
|
|
features:
|
|
- |
|
|
A new image metadata property, ``hw_input_bus``, has been added. This
|
|
allows you to specify the bus used for input devices - a pointer and
|
|
keyboard - which are attached to the instance when graphics are enabled
|
|
on compute nodes using the libvirt virt driver. Two values are currently
|
|
accepted: ``usb`` and ``virtio``. This image metadata property effectively
|
|
replaced the ``hw_pointer_model`` image metadata property, which is
|
|
nontheless retained for backwards compatibility purposes.
|