This board is a bit special since it's not "statically" available for a given target, but a combination of host + target. >From meson.build, we can see it's present only when CONFIG_MULTIPROCESS is set. From Kconfig, we can see it's set when PCI && PCI_EXPRESS && KVM. CONFIG_KVM is defined for specific host/targets combination.
Signed-off-by: Pierrick Bouvier <[email protected]> --- hw/remote/machine.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/hw/remote/machine.c b/hw/remote/machine.c index 88d38b75d52..fa750368df2 100644 --- a/hw/remote/machine.c +++ b/hw/remote/machine.c @@ -124,6 +124,7 @@ static void remote_machine_dev_unplug_cb(HotplugHandler *hotplug_dev, static void remote_machine_class_init(ObjectClass *oc, const void *data) { + TARGET_SPECIFIC_CLASS(oc)->is_available = target_config_multiprocess; MachineClass *mc = MACHINE_CLASS(oc); HotplugHandlerClass *hc = HOTPLUG_HANDLER_CLASS(oc); @@ -149,6 +150,7 @@ static const TypeInfo remote_machine = { .class_init = remote_machine_class_init, .interfaces = (const InterfaceInfo[]) { { TYPE_HOTPLUG_HANDLER }, + { TYPE_TARGET_SPECIFIC }, { TYPE_TARGET_AARCH64_MACHINE }, { } } -- 2.43.0
