** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Title:
ubuntu/focal64 very slow to boot and reboots
Attached are some prints and logs. lshw shows that it's using a scsi
storage control with the mptspi driver. serial console logs show that
initramfsless boots using a a generic scsi driver which appears to fail
to load the root device. initramfs pulls in the mptspi driver properly,
and things
** Package changed: linux (Ubuntu) => livecd-rootfs (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Title:
ubuntu/focal64 very slow to boot and reboots once
Status in
May 22nd was made available when I commented. Not sure why your update
didn't find it. Maybe there's lag with specific mirrors. Official
listings show them available:
https://app.vagrantup.com/ubuntu/boxes/focal64
https://app.vagrantup.com/ubuntu/boxes/eoan64
--
You received this bug
apologies -- the 0518 Focal image has the fix as well. That may not have
been clear since the comments came on the 19th, and I updated on the
22nd. The eoan 22nd made it up on the 22nd, but there was lag with the
Focal 0522 serial syncing on our end. It's up there now.
--
You received this bug
I've set the kernel component to confirmed to move this ticket forward.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
was passed a related issue:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1879290
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Title:
ubuntu/focal64 very slow to boot
Was able to recreate the slow boot. Put together a clean environment,
made a simple focal Vagrantfile only pulling the box, saw the same
things. Confirmed on a Focal host.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
is this post updating the boxes? could you please post which boxes are
still kernel panicking, as that should have been fixed with
https://bugs.launchpad.net/cloud-images/+bug/1873506
I'm having a bear of a time trying to reproduce the slow boots. I'm
wondering if it's host specific to MacOS and
** Changed in: cloud-images
Assignee: (unassigned) => John Chittum (jchittum)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1873506
Title:
ubuntu/focal64 fails to mount Vagr
Vagrant boxes with updated kernels have been pushed. My current tests
are showing boot times in the 30s range.
Could folks commenting on slow boot speeds in Focal and Eoan please run
a `vagrant box update` on their current setups?
Focal and Eoan boxes with the above kernels have been pushed to Vagrant
and verified. Please run a `vagrant box update` to get the latest
versions.
** Changed in: cloud-images
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
For all new commenters -- what you're experiencing is a new bug with
similar symptoms, though slightly different root cause. Note the
original bug was "no device found" and this is "Invalid argument."
This appears to be a new bug. I don't see an identical bug to this new
issues, so i've opened
livecd-rootfs 23.10.55 for mantic is currently migrating, and has
apparmor changes as well (mounting different features in the build
chroot). To help rule out some issues, I built a a qcow2 image and a
squashfs for mantic using livecd-rootfs 23.10.55
Running the mantic host, and launching a
Marking cloud-images and maas-images as fixed with the roll of util-
linux, and confirmation from fginther
** Changed in: maas-images
Status: Confirmed => Fix Released
** Changed in: cloud-images
Status: New => Fix Released
--
You received this bug notification because you are a
Did the following:
1. launched a new VM from the custom build
lxc launch mantic-20231005 --vm --device root,size=20GiB mantic-cust-vm
2. pushed squashfs and lxc metadata from same custom build
lxc file push build.output/livecd.ubuntu-cpc.squashfs mantic-cust-vm/root/
lxc file push
Repeating a bit with a Jammy container (hence new comment)
### PRE CONDITION
this is using the custom Mantic VM _and_ has
apparmor_restrict_unprivileged_unconfined disabled
sudo bash -c "echo 0 >
/proc/sys/kernel/apparmor_restrict_unprivileged_unconfined"
1. start a jammy container
lxc launch
on my machine (specs at the end) running Jammy as the host, and
launching a Jammy container:
1. lxc launch ubuntu:jammy test-jammy-on-jammy
from journal
Oct 06 07:36:47 j5awry-sys76 kernel: audit: type=1400
audit(1696595807.223:51559): apparmor="DENIED" operation="mount" class="mount"
We are actively working on the issue. This also affects more than the
`linux-aws` kernel, as we've been able to reproduce on 5.13 versions of:
linux-oracle
linux-azure
linux-gcp
linux-aws
This appears to be confined to the latest 5.13 kernel update. We will
provide more updates shortly on all
** Also affects: linux-kvm (Ubuntu)
Importance: Undecided
Status: New
--
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/1993814
Title:
net sched missing from Jammy KVM image
> I think the main use case is to bootstrap cloud images so that they
can then install other kernels as quickly as possible, right?
This is incorrect. the linux-kvm kernel is lightweight kernel meant for
minimal applications running in virtualized environments. The only image
it is present on
FYI, bit of a necro -- we're seeing this currently on the 20.04 5.15
kernel and the 23.04 5.19 kernel. I haven't checked on the proposed 6.2
kernel yet.
this can be reproduced on AWS
Reproduction step:
1. Create an AWS instance with AMI `ami-056a67ea1b8ffa0fc` (Linux
5.15.0-1022-aws) in
Question -- this has landed in various jammy-5.15 kernels. This rolled
downstream to the focal HWE kernels (specifically the cloud kernels)
1. was this intentional?
2. if so, could we add an affects for focal as well? it'll help us with
tracking downstream dependency changes, specifically in
23 matches
Mail list logo
