ACK/Cmnt: [SRU][I/raspi][F/raspi][B/raspi-5.4][PATCH 0/1] Kernel fails to boot in ScalingStack (LP: #1959102)

[Tim Gardner]

Acked-by: Tim Gardner <tim.gardner at canonical.com>

I'm curious why the original policy passed the config test when 
CONFIG_VIRTIO_PCI was not set, e.g.,

CONFIG_VIRTIO_PCI policy<{'amd64': 'y', 'arm64': 'y', 'armhf': 'y', 
'i386': 'y', 'ppc64el': 'y', 's390x': 'y'}>

rtg

On 2/10/22 3:38 AM, Juerg Haefliger wrote:
> [ Impact ]
> 
> The raspi kernel fails to boot in ScalingStack which is our OpenStack cluster for running ADT/autopkgtest tests.
> 
> [ Test Case ]
> 
> Boot a VM in ScalingStack, install raspi kernel, reboot. VM won't come back.
> 
> [ Fix ]
> 
> Enable VIRTIO PCI driver. ScalingStack uses virtio so the guest kernel needs to support that.
> 
> [ Where Problems Could Occur ]
> 
> New module means new code which could trigger kernel problems when loaded.
> 
> Juerg Haefliger (1):
>    UBUNTU: [Config] raspi: Set VIRTIO_PCI=m
> 
>   debian.raspi/config/annotations          | 2 ++
>   debian.raspi/config/config.common.ubuntu | 3 ++-
>   2 files changed, 4 insertions(+), 1 deletion(-)
> 

-- 
-----------
Tim Gardner
Canonical, Inc