carry over from IRC »·just putting this here for tomorrow: https://bugs.launchpad.net/charm-nova-compute/+bug/1891203 »·looked at the bug - doesn't ring a known bell »·maybe a dependency change »·so this is Ussuri - so we are talking about the Focal backported to Bionic here right? »·bionic ussuri, right - focal ussuri works fine with that same version »·also if you could compare dpkg -l 'qemu*' 'libvirt*' on the working focal-ussuri vs bionuc-ussuri »·will do »·I'm concerned if just an extra qemu-something-arm might be missing »·heh right »·and for arm that also includes packages like ovmf or such »·what else then ovmf might come to ming ... »·mind »·maybe just be brutal and Diff full `dpkg -l` among the systemd »·systems »·in particular »·your armv6l has this »· /usr/bin/qemu-system-arm »·whatever the good system has as emulator for aarch64 really needs to be there »·also I've seen the capability prober processes fail, so if nothing of the above helps check the logs of libvirt for failing qemu processes »·right if i downgrade to prev version »·i do have »· hvm »· »· 32 »· /usr/bin/qemu-system-aarch64 bionic has libvirt 6.0.0-0ubuntu8.2 and focal 6.0.0-0ubuntu8.3 nothing else obvious w qemu or libvirt packages hmm there were a few things I mentioned to james that need to be removed/reverted on backport I mostly send these mails to allow my brain forgetting about them * cpaelzer tries to search what I have mentioned there yeah updating libvirt to that latest (...8.3) didnt work there are no libvirt/qemu logs either come tot hink about it, it feels as if there is a binary which reports the version and that aarch64 that is missing somehow that how it 'feels' .....without understanding how it 'works' on startup libvirt probes for binaries of qemu then it calls all those asking for HW/Features they support that is what builds that "capabilities" output right so if it cant probe those bins, it wont get the version or the caps hence I'm saying you might want to debug a restart of libvirtd cos the error is 'not min ver' but it is maybe one of these processes dies off right how debug?· I found my old mails BTW - we were only aware of x86 changes that need to be reverted ont he backport enable this https://wiki.libvirt.org/page/DebugLogs ah then delete all files in /var/cache/libvirt/qemu/capabilities/ that forces libvirt to re-probe for sure then systemctl restart libvirtd then read the log and hope to find something it is quite verbose, so you have to search a while (that is normal) you look for qemu processes started for this probing in the log and how they worked out best maybe is to do the same on F-ussuri vs B-ussuri as that will help to ignore the bits that didn't change