Bug#900381: Fails to boot cirros QEMU image with tuned running

2021-01-01 Thread Evgeni Golov
On Fri, Jan 01, 2021 at 11:04:44AM +0100, Evgeni Golov wrote: > On Mon, Dec 21, 2020 at 09:40:15AM +0100, Martin Pitt wrote: > > 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

Bug#900381: Fails to boot cirros QEMU image with tuned running

2021-01-01 Thread Evgeni Golov
On Mon, Dec 21, 2020 at 09:40:15AM +0100, Martin Pitt wrote: > 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

Bug#900381: Fails to boot cirros QEMU image with tuned running

2020-12-31 Thread Evgeni Golov
On Wed, Dec 30, 2020 at 08:33:09PM +0100, Evgeni Golov wrote: > > And the tuned line that breaks the whole thing is > > > > [sysctl] > > kernel.sched_wakeup_granularity_ns = 1500 > > This also happens on seabios 1.13.0-1 from snapshot.d.o. > > I originally wanted to go and bisect that with

Bug#900381: Fails to boot cirros QEMU image with tuned running

2020-12-30 Thread Evgeni Golov
On Wed, Dec 30, 2020 at 01:06:45PM +0100, Evgeni Golov wrote: > > This doesn't happen on the buster cloud images, and a few "apt install" > > invocations later I could bisect the issue to be the upgrade of seabios > > from 1.12.0-1 to 1.14.0-2. > > > > I also can't repro this in vagrant (by using

Bug#900381: Fails to boot cirros QEMU image with tuned running

2020-12-30 Thread Evgeni Golov
On Wed, Dec 30, 2020 at 12:49:03PM +0100, Evgeni Golov wrote: > On Sun, Dec 27, 2020 at 03:46:27PM +0100, Evgeni Golov wrote: > > 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,

Bug#900381: Fails to boot cirros QEMU image with tuned running

2020-12-30 Thread Evgeni Golov
On Sun, Dec 27, 2020 at 03:46:27PM +0100, Evgeni Golov wrote: > 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

Bug#900381: Fails to boot cirros QEMU image with tuned running

2020-12-27 Thread Evgeni Golov
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 >

Bug#900381: Fails to boot cirros QEMU image with tuned running

2020-12-21 Thread Martin Pitt
Hello Evgeni, as this bug report is quite old, I first re-checked this with the versions in testing from a few days ago: qemu-system-x86 1:5.1+dfsg-4+b2 tuned2.10.0-1 linux-image-5.9.0-4-cloud-amd64 5.9.11-1 Without tuned, cirros boots,

Bug#900381: Fails to boot cirros QEMU image with tuned running

2020-12-13 Thread Evgeni Golov
Hi Martin, On Tue, May 29, 2018 at 10:48:48PM +0200, Martin Pitt wrote: > Package: tuned > Version: 2.9.0-1 > > As soon as you install tuned (which auto-starts tuned.service), booting at > least some QEMU images does not work any more: > > $ wget

Bug#900381: Fails to boot cirros QEMU image with tuned running

2018-05-29 Thread Martin Pitt
Package: tuned Version: 2.9.0-1 As soon as you install tuned (which auto-starts tuned.service), booting at least some QEMU images does not work any more: $ wget https://download.cirros-cloud.net/0.3.5/cirros-0.3.5-i386-disk.img $ qemu-system-x86_64 -enable-kvm -nographic