Hi martin, On Mon, Dec 21, 2020 at 09:40:15AM +0100, Martin Pitt wrote: > I re-tested this straight from the current official cloud images: > > curl -o sid.qcow2 > https://cloud.debian.org/images/cloud/sid/daily/20201220-490/debian-sid-nocloud-amd64-daily-20201220-490.qcow2 > qemu-system-x86_64 -cpu host -nographic -m 2048 -device virtio-rng-pci > -drive file=sid.qcow2,if=virtio -snapshot > > The `-cpu host` option is necessary to provide /dev/kvm inside the VM (the > default "QEMU Virtual CPU" does not). > > Log in as "root" (no password), then run > > apt update > apt install -y --no-install-recommends qemu-system-x86 tuned > > curl -L -O > https://download.cirros-cloud.net/0.3.5/cirros-0.3.5-i386-disk.img > qemu-system-x86_64 -enable-kvm -nographic cirros-0.3.5-i386-disk.img > -snapshot > > The boot hangs as above. Again, when not installing or stopping tuned, it > works.
Thanks for re-testing and the detailed instructions. It somehow missed my mind that this is nested-virt. I can repro this now with your instructions, and have made the following observations: 1. qemu will happily continue booting cirros when you stop tuned *after* starting qemu 2. it boots fine if you use the "default" (which is not default anymore, but a legacy fallback) or the "balanced" profiles. 3. it hangs as you describe in the "throughput-performance", "virtual-guest" and "virtual-host" profiles -- I didn't test any others 4. using any of the problematic profiles on my laptop doesn't make it freeze in the non-nested case Still, not a fix, but at least a direction ;-)
