mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-07-17 07:07:16 +00:00
d4c39bad85
At this moment it is not possible to launch a 'riscv64' domain if a CPU
definition is presented in the domain. For example, adding this CPU
definition:
<cpu mode='custom' match='exact' check='none'>
<model fallback='forbid'>rv64</model>
</cpu>
Will trigger the following error:
$ sudo ./run tools/virsh start riscv-virt1
error: Failed to start domain 'riscv-virt1'
error: this function is not supported by the connection driver:
cannot update guest CPU for riscv64 architecture
The error comes from virCPUUpdate(), via qemuProcessUpdateGuestCPU(),
and it's caused by the absence of the 'update' API in the existing
RISC-V driver.
Add an 'update' API impl to the RISC-V driver to allow for CPU
definitions to be declared in RISC-V domains. This API was copied from
the ARM driver (virCPUarmUpdate()) since it's a good enough
implementation to get us going.
Signed-off-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Reviewed-by: Andrea Bolognani <abologna@redhat.com>
|
||
|---|---|---|
| .. | ||
| cpu_arm_data.h | ||
| cpu_arm.c | ||
| cpu_arm.h | ||
| cpu_map.c | ||
| cpu_map.h | ||
| cpu_ppc64_data.h | ||
| cpu_ppc64.c | ||
| cpu_ppc64.h | ||
| cpu_riscv64.c | ||
| cpu_riscv64.h | ||
| cpu_s390.c | ||
| cpu_s390.h | ||
| cpu_x86_data.h | ||
| cpu_x86.c | ||
| cpu_x86.h | ||
| cpu.c | ||
| cpu.h | ||
| meson.build | ||