unsupported configuration in virsh command

[Marian Gasparovic]

When defining virsh pods we are getting this error.

2023-02-07-17:51:00 root ERROR [localhost] Command failed: maas root vm-host compose 1 hostname=elastic-1 cores=2 memory=8192 storage=50.0 zone=2
2023-02-07-17:51:00 root ERROR [localhost] STDOUT follows:
Unable to compose machine because: Failed talking to pod: Virsh command ['define', '/tmp/tmpyi19uj_i'] failed: Failed to define domain from /tmp/tmpyi19uj_i
error: unsupported configuration: ps2 is not supported by this QEMU binary

It is MAAS 3.3.0 snap on jammy on arm64. Exactly this worked fine on focal on arm64 during 3.3.0 RC tests.
Logs show it is 3.3/candidate but it is currently the same as stable and it behaves the same on stable.

Logs - https://oil-jenkins.canonical.com/artifacts/28b0568f-ebe2-4228-9665-19de3611dbbe/generated/generated/maas/logs-2023-02-07-17.51.34.tgz

[Alexsander de Souza (alexsander-souza)]

The PS/2 bus is only available in some architectures (e.g. x86). Old versions of virsh silently ignore this option when the bus is not available, but the current version raises an error.

We need to review the domain templates in src/provisioningserver/drivers/pod/virsh.py

[Jerzy Husakowski (jhusakowski)]

Virsh is "soft-deprecated" since MAAS 3.1, with the advice to use LXD for VM hosting. The UI points that out, but this is not clearly captured in documentation and release notes yet. We will fix the reported issue, and also make sure we update the documentation to encourage using LXD over virsh.