Something that could be attempted in parallel to follow a different hint: Deploy a second instance and for that openstack instance create a file /etc/modprobe.d/kvm.conf with the following line:
options kvm tdp_mmu=false
Instead of "false" I hear "0" might work. For me "false" was good. In any way, when you reboot the instance you should get a "N" from "cat /sys/module/kvm/parameters/tdp_mmu". Then you could deploy the juju runner VM inside the openstack instance and see how that works.
I have uploaded a test kernel to ppa:smb/jammy (https:/ /launchpad. net/~smb/ +archive/ ubuntu/ jammy). The build is still ongoing at this time.
Something that could be attempted in parallel to follow a different hint: Deploy a second instance and for that openstack instance create a file /etc/modprobe. d/kvm.conf with the following line:
options kvm tdp_mmu=false
Instead of "false" I hear "0" might work. For me "false" was good. In any way, when you reboot the instance you should get a "N" from "cat /sys/module/ kvm/parameters/ tdp_mmu" . Then you could deploy the juju runner VM inside the openstack instance and see how that works.