Ok, so the fact that we thought this worked is clearly the result from bad testing on our part, probably because of our simplestreams parsing code we fixed yesterday...
We obviously still need to move LXD onto this images as booting the non- kvm images takes twice as long as it should (due to them panic + reboot every time) AND also breaks cloud-init, at least in the way we'd like to use it. Now realistically this can't be fixed in time for 20.04, so what we've done is submitted a change to simplestreams to force all LXD users onto the non-kvm image: https://code.launchpad.net/~stgraber/simplestreams/+git/simplestreams/+merge/382597 We'll also tell all users of `ubuntu:` and `ubuntu-daily:` that they need to do: - lxc config device add NAME config disk source=cloud-init:config Which passes a stable config drive to cloud-init, avoiding the cloud- init issue they'd be getting out of the box. Moving forward, we'd like the -kvm kernel to be both EFI enabled AND signed. This will then allow those images to work properly inside LXD, at which point we can undo the simplestreams change and have those images used once again by our users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: disk-kvm.img aren't UEFI bootable To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1873809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
