Tom Parrott

Yep that made it work

> @tomponline Are my steps and files still necessary? Well I was wondering how you used the non-rust virtiofsd from qemu when its not provided anymore from 8.x (I forget)...

Thanks for your help. We decided to switch to using `--sandbox=chroot` for 5.0 series to restore compatibility with 4.15 kernel.

> > Well I was wondering how you used the non-rust virtiofsd from qemu when its not provided anymore from 8.x (I forget) onwards? > > I didn't do anything...

OK thanks. So to summarise: 1. `4.15.0-213.224` kernel didn't work. 2. `5.4.0-150-generic` did work. 3. Enabling `migration.stateful=true` on `4.15.0-213.224` kernel did work. This lead to the incorrect theory that it...

> We need to replace this with some sort of configuration option that can be set per target when in a cluster. Could you elaborate a bit on how you...

> To examplify further, what if you wanted to use resources from both PFs? Would you put both `enp129s0f0np0` and `enp129s0f1np1` into the same bridge? Yes I vaguely recall that...

Ah in that case it would likely need to be part of a member-specific config on the ovn network itself or perhaps uplink network's configuration: https://documentation.ubuntu.com/lxd/en/latest/reference/network_ovn/#configuration-options https://documentation.ubuntu.com/lxd/en/latest/reference/network_physical/#configuration-options This could then...

@fnordahl I've marked this as blocked as we don't have access to hardware anymore to develop/test a fix for this. If this is something you could help us with that...

@fnordahl as discussed in meeting, we'll get a partner cloud setup to work on this issue.