Hi Martin,
tuned is usually not installed, at least not on the new guest you are booting, so to be sure are we talking about this setup:
Host
- KVM-Host
- not so important, but what OS is this?
Guest1
- KVM-Guest
- runs an Ubuntu Cosmic Image
- also KVM-Nested-Host
- tuned runs here in virt-guest profile
Guest2
- nested KVM-Guest
- runs CirrOS image
- Booting this guest hangs with the newer tuned
I assume tuned runs in the default config here.
So it spawns its service, has a dbus listener but none of the specials (like kernel commandline changes).
But if I not miss something the virt-guest profile should then by default only change vm.dirty_ratio and vm.swappiness - none of these should be super important.
I'm trying to recreate now with above assumptions, let me know if anything differs.
Hi Martin,
tuned is usually not installed, at least not on the new guest you are booting, so to be sure are we talking about this setup:
Host
- KVM-Host
- not so important, but what OS is this?
Guest1
- KVM-Guest
- runs an Ubuntu Cosmic Image
- also KVM-Nested-Host
- tuned runs here in virt-guest profile
Guest2
- nested KVM-Guest
- runs CirrOS image
- Booting this guest hangs with the newer tuned
I assume tuned runs in the default config here.
So it spawns its service, has a dbus listener but none of the specials (like kernel commandline changes).
But if I not miss something the virt-guest profile should then by default only change vm.dirty_ratio and vm.swappiness - none of these should be super important.
I'm trying to recreate now with above assumptions, let me know if anything differs.