Both the 18.04 & 16.04 Ubuntu Minimal cloud images use the kvm kernel by
default, so we need this fix applied to those kernels as well. Are
there plans for that so that we can use those Minimal images in LXD?
--
You received this bug notification because you are a member of Kernel
Packages,
This bug was fixed in the package linux-kvm - 5.4.0-1020.20
---
linux-kvm (5.4.0-1020.20) focal; urgency=medium
* focal/linux-kvm: 5.4.0-1020.20 -proposed tracker (LP: #1887063)
[ Ubuntu: 5.4.0-42.46 ]
* focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)
* linux
We weren't planning to as the previous releases (xenial and bionic) did
not have "-kvm" image and their default image includes an initrd making
them boot just fine under LXD.
So it's really just groovy+focal that we need before we can start using those
images.
focal has been taken care of so
Hey all, will we get backports of this to previous releases?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1873809
Title:
Make linux-kvm bootable in LXD VMs
Status in
This bug was fixed in the package linux-kvm - 5.4.0-1018.18
---
linux-kvm (5.4.0-1018.18) focal; urgency=medium
* focal/linux-kvm: 5.4.0-1018.18 -proposed tracker (LP: #1885099)
* LXD 4.2 broken on linux-kvm due to missing VLAN filtering (LP: #1882955)
- [Config] kvm:
@Stéphane, right now (and that might be for a while still) the linux-kvm
kernel in Groovy is a copy-forward from Focal. So once this releases,
you should be able to use it there as well. I started to have annotated
config enforcement for the adjusted config which hopefully will survive
when the
Confirmed, 1018 boots fine here under Secure Boot, all good!
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
@smb what's the state of groovy, did you push the config update there
too?
For the cloud images, we'll want to switch over to those using linux-kvm
in groovy first, then focal, so just want to make sure we'll get a
working kernel on there too!
--
You received this bug notification because you
Note that for me the latest kernel works past the decoding failed stage.
But it would be good to have a second verification is possible.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
Latest version: 5.4.0-1018-kvm
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still
Alright, at least partially understanding things now. So it looks like
"Decoding failed" happens generally on some platforms (and I do not
understand still why this is). The difference between the generic kernel
and the kvm kernel is that the kvm kernel has a built-in BLK_DEV_RAM of
size (4096)
Ok, so with the same software versions installed but on a different hw
platform, I did at least once get this incomplete write error. The
working box is an AMD/BIOS one and the non-working an Intel/EFI. Not
sure why that has any impact.
--
You received this bug notification because you are a
Hm, and maybe also relevant: what kind of pool is used? My setup was
"lxd init --auto" which is a file based image backend.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1873809
@Stéphane, I have now followed your steps from commant #38 (was using the
official ubuntu image before with cloud-init and that does a initrd-less boot
first which is successful for me) but this does not show me the error you see
either. And a break=top does work (with some complaints about
It's not the log above clearly shows the kernel loading an initrd.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1873809
Title:
Make linux-kvm bootable in LXD VMs
Status in
I'm not sure if it's related, but maybe worth the mention: could this be
due to the initrd-less boot? I've noticed that in some VMs, it first
fails to boot (it tries an initrd-less boot), reboots and then loads the
initrd. This is an Ubuntu grub-thing, and you can prevent that by
deleting a file
"""
stgraber@castiana:~$ lxc launch images:ubuntu/focal f1 --vm
Creating f1
Starting f1
stgraber@castiana:~$ lxc exec f1 bash
root@f1:~# echo "deb http://archive.ubuntu.com/ubuntu focal-proposed main
restricted universe multiverse" >> /etc/apt/sources.list
root@f1:~# apt-get update
Hit:1
https://paste.ubuntu.com/p/7yHDCFt75m/ for additional proof that the
initrd is never executed (break=top would immediately drop to a shell).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
@smb Can you confirm that your system indeed goes through the initrd and
isn't just silently falling back to directly mounting and booting /?
Booting with break=mount would likely be a valid way to test this
(should drop you in a shell).
--
You received this bug notification because you are a
Hmm, actually no luck at booting either 1015 or 1017 on
security.secureboot=false here, poked at grub and it does load both
kernel and initrd...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
"""
Loading Linux 5.4.0-1015-kvm ...
Loading initial ramdisk ...
Linux version 5.4.0-1015-kvm (buildd@lcy01-amd64-027) (gcc version 9.3.0
(Ubuntu 9.3.0-10ubuntu2)) #15-Ubuntu SMP Fri Jun 5 00:55:20 UTC 2020 (Ubuntu
5.4.0-1015.15-kvm 5.4.41)
Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1015-kvm
Yeah, I think you're right, I also had the exact same panic happen now
on 1015, so it's likely some grub weirdness rather than kernel
regression.
It just so happened that in my last test I managed to get a working grub
config after moving to 1015 and not with 1017. Looks like we'll need to
poke
@Stéphane, the uncompress message appears to be something that may
happen if blocks are not aligned but not harming anything. By now I have
played around with both a self created secureboot VM on bionic and also
(following your turorial) a LXD 4.0 vM. And for both I could not repeat
what you saw.
@Stefan, so actually this is an actual regression.
1015 will boot just fine in LXD with secureboot disabled.
1017 will not boot at all in LXD with or without secureboot disabled.
I don't know if it's switching to a signed kernel which causes the lz4
issue but the result is a clear regression so
@Stephane, if this bug was not phrased that generically I would feel
inclined to say it verified ok if the kernel image can be booted in
secureboot mode and has the requested config options set. And treat the
initrd issue as a separate one on the path to completion.
For us, I would propose to
"""
Jun 18 13:56:15 f1 kernel: [0.383207] Trying to unpack rootfs image as
initramfs...
Jun 18 13:56:15 f1 kernel: [0.463102] Initramfs unpacking failed: Decoding
failed
"""
Is what we're getting on current generic kernel, though boot continues after
that.
I don't know if when that
Trying to boot the proposed kernel in LXD:
"""
BdsDxe: loading Boot0007 "ubuntu" from
HD(1,GPT,25633192-5DBD-412A-8A50-E29B79F72A50,0x800,0x32000)/\EFI\ubuntu\shimx64.efi
BdsDxe: starting Boot0007 "ubuntu" from
HD(1,GPT,25633192-5DBD-412A-8A50-E29B79F72A50,0x800,0x32000)/\EFI\ubuntu\shimx64.efi
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
** Changed in: linux-kvm (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1873809
Title:
Make linux-kvm bootable in LXD VMs
** Also affects: linux-kvm (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-kvm (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux-kvm (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-kvm (Ubuntu Focal)
Assignee:
Pinged in #ubuntu-kernel today for an update. It'd be good to have
groovy signed soon so we can then roll this out to focal users.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
Re-opening as I'm not seeing any mention of this being signed now.
** Changed in: linux-kvm (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
This bug was fixed in the package linux-kvm - 5.3.0-1017.19
---
linux-kvm (5.3.0-1017.19) eoan; urgency=medium
* eoan/linux-kvm: 5.3.0-1017.18 -proposed tracker (LP: #1877951)
* Packaging resync (LP: #1786013)
- [Packaging] resync dkms-build and family
- [Packaging] add
@stgraber sorry I should have clarified that I'm referring to Eoan specifically.
In Eoan, EFI_STUB is still not enabled. Is it needed there?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
@Khaled yes, it is and we have it now. What's still needed is for the
kernel to be signed so it can be used under secureboot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1873809
@stgraber I'm getting mixed messages from the last few comments about
whether CONFIG_EFI_STUB is needed or not - can you please clarify?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
Hello,
Just tested the latest image in ./current and it boots fine :
root@focal-ok:~# uname -a
Linux focal-ok 5.4.0-1009-kvm #9-Ubuntu SMP Mon Apr 20 20:23:56 UTC 2020 x86_64
x86_64 x86_64 GNU/Linux
root@focal-ok:~# cat /etc/cloud/build.info
build_name: server
serial: 20200421
root@focal-ok:~#
Ok, fixed the bug tasks and re-opened the bug as we still need this
kernel to get signed.
** Changed in: linux-kvm (Ubuntu)
Status: Fix Released => Triaged
** Changed in: cloud-images
Assignee: Roufique Hossain (roufique) => (unassigned)
** Changed in: linux-kvm (Ubuntu)
Hmm, actually, CONFIG_EFI_STUB is the one we were missing and I'm not
seeing that in your VM either, which makes me wonder how it was booted
in the first place :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
Thanks Louis, so our testing may in fact have been accurate and things
regressed afterwards :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1873809
Title:
Make linux-kvm bootable
This bug was fixed in the package linux-kvm - 5.4.0-1009.9
---
linux-kvm (5.4.0-1009.9) focal; urgency=medium
* focal/linux-kvm: 5.4.0-1009.9 -proposed tracker (LP: #1873934)
* multipathd.service fails to start with linux-kvm kernel (LP: #1873912)
- [Config] Enable
Hello,
thanks for the quick turnaround.
For the record, some EFI configs did exist in prior 5.3 images :
root@focal:/boot# cat /etc/cloud/build.info
build_name: server
serial: 20200223
root@focal:/boot# uname -r
5.3.0-1009-kvm
root@focal:/boot# grep -i ^CONFIG_EFI config-5.3.0-1009-kvm
** Changed in: cloud-images
Status: Invalid => Confirmed
** Changed in: cloud-images
Assignee: (unassigned) => Roufique Hossain (roufique)
** Changed in: linux-kvm (Ubuntu)
Assignee: Colin Ian King (colin-king) => Roufique Hossain (roufique)
** Changed in: linux-kvm (Ubuntu)
** Changed in: linux-kvm (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux-kvm (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
Just tested it now, confirmed that this still boots fine and that this
time the LXD agent successfully starts too.
So this config seems suitable for us. That + enabling kernel signing
will get us working images.
Thanks!
--
You received this bug notification because you are a member of Kernel
** Description changed:
The `disk-kvm.img` images which are to be preferred when run under
- virtualization, completely fail to boot under UEFI.
+ virtualization, currently completely fail to boot under UEFI.
- This is a critical issue as those are the images that LXD is now pulling
- by
Test build with the vsock options:
https://people.canonical.com/~sforshee/lp1873809/linux-
kvm-5.4.0-1008-kvm/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1873809
Title:
Make
47 matches
Mail list logo
