Bug#906263: cloud.debian.org: Cloud images do not boot (KVM) without a video device

[Thomas Goirand <zigo@debian.org>]

On 08/18/2018 04:08 AM, Max Khon wrote:
> Thomas,
> 
> On Sat, 18 Aug 2018 at 02:56, Thomas Goirand <zigo@debian.org
> <mailto:zigo@debian.org>> wrote:
> 
>     On 08/16/2018 10:18 AM, Max Khon wrote:
>     > Debian 9 cloud images do not boot if a KVM VM does not have a
>     video device
>     > (OpenStack creates such VMs if remote console is not configured in
>     > nova-compute):
>     > qemu-system-x86_64 consumes 100% CPU and the VM is not booted.
>     >
>     > The fix is to uncomment "GRUB_TERMINAL=console" in
>     /etc/default/grub and
>     > run "update-grub"
>     >
>     > Note that Ubuntu cloud images have the following configuration in
>     > /etc/default/grub:
>     > GRUB_TERMINAL="serial console"
>     > GRUB_SERIAL_COMMAND="serial --speed=115200"
> 
>     Hi Max,
> 
>     Why would one want to configure OpenStack to not provide a video console
>     using VNC / SPICE? I don't get it...
> 
> 
> 1) OpenStack juju charms by default have VNC/SPICE unconfigured
> 
> 2) There was no such issue in Debian 8 cloud images. Not to mention
> Ubuntu and CentOS
> 
> 3) Why do we want to have an
> image that sometimes does not work - it took
> me a while to figure out why Debian 9 is the only image that does not
> boot in our private cloud
> 
> 4) Any serious reasons to be different on this matter to other major
> Linux distributions?
> 
> Max

Hi Max,

Thanks for the details.

While it's easy to update the testing image, it's not to update the
Stable one, as I'll have to deal with the stable release team approval
for this update to happen. This is why I needed some more info.

I'll fix the image in Testing soon, and I'll try to make it happen also
in Stable. Though for stable, it will unfortunately only happen after
the next point release at least, and only *if* the release team approves
the change.

Cheers,

Thomas Goirand (zigo)