Open simondeziel opened 10 months ago
@simondeziel this is due to this section:
https://github.com/canonical/lxd/blob/main/lxd/device/device_utils_disk.go#L454-L458
I've tested on our s390x machine (which runs Focal) and although the virtiofsd daemon starts on the host, there is some issue in the guest (running Jammy) that means the agent doesn't start properly (likely because it cannot mount the config drive).
So I'm happy that this isn't a LXD 5.0.3 or LXD 24.04 release blocker.
Although it would be interesting to speak to IS about getting our s390x system upgraded to Jammy and see if its still an issue so we can remove the restriction in 6.0.
@tomponline I made the request to get us a few LPARs running Jammy and tentatively Noble. Depending on how it goes, should we remove virtiofsd
from the non-amd64 snap?
In a
s390x
VM, trying to mount theconfig
drive fails:LXD logs contain:
Looking at https://github.com/canonical/lxd/blob/main/lxd/instance/drivers/driver_qemu.go#L1358, failure to start
virtiofsd
seems to be why the qemu config does not have thedev-qemu_config-drive-virtio-fs
device one would expect:While on
amd64
it's present:but the snap has the binary built for it and has no apparent problem running this simple version check:
Additional information:
This affects both
latest/edge
and5.0/edge
: