** Also affects: linux-gcp (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2063315
Title:
Suspend & Resume functionality
** Changed in: snapd (Ubuntu Noble)
Status: New => Invalid
** Changed in: linux-aws (Ubuntu Noble)
Status: New => Fix Released
** Changed in: linux-azure (Ubuntu Noble)
Status: New => Fix Released
** Changed in: linux-gcp (Ubuntu Noble)
Status: New => Fix Released
** Also affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oracle (Ubuntu)
Importance:
** Also affects: chrony (Ubuntu)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: chrony (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Noble)
Importance:
Public bug reported:
* Canonical Public Cloud discovered that `chronyc -c sources` now fails with
`506 Cannot talk to daemon` with the latest kernels. We are seeing this in
linux-azure and linux-gcp kernels (6.8.0-1005.5)
* Disabling AppArmor (`sudo systemctl stop apparmor`) completely results
I have reproduced with @amalmostafa's updated script with a separate
disk too. I see no segfault and no EXT4 errors but the regression in
performance is still present but not as great as in my previous tests.
```
### Ubuntu 20.04 with 5.4 kernel and data disk
ubuntu@cloudimg:~$ sudo fio
I am NOT seeing the same on 22.04
```
ubuntu@cloudimg:~$ uname --kernel-release
5.15.0-87-generic
ubuntu@cloudimg:~$ cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.3 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
@kamalmostafa indeed yes. I had missed this.
See below for the output from 20.04 with 5.15 kernel.
```
ubuntu@cloudimg:~$ sudo fio --ioengine=libaio --blocksize=4k --readwrite=write
--filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting
--numjobs=8 --name=fiojob1
Providing exact reproducer steps using Qemu locally -
Launch script:
https://gist.github.com/philroche/8242106415ef35b446d7e625b6d60c90 and
cloud image I used for testing @ http://cloud-
images.ubuntu.com/minimal/releases/focal/release/
```
# Download the VM launch script
wget
Google have provided a non synthetic `fio` impact
> Performance was severally degraded when accessing Persistent Volumes
provided by Portworx/PureStorage.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
For reference, I also tried on a 22.04 cloud image with 5.15 kernel
```
ubuntu@cloudimg:~$ sudo fio --ioengine=libaio --blocksize=4k --readwrite=write
--filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting
--numjobs=8 --name=fiojob1 --filename=/dev/sda
fiojob1: (g=0): rw=write,
Public bug reported:
We in the Canonical Public Cloud team have received report from our
colleagues in Google regarding a potential performance regression with
the 5.15 kernel vs the 5.4 kernel on ubuntu 20.04. Their test were
performed using the linux-gkeop and linux-gkeop-5.15 kernels.
I have
https://bugs.launchpad.net/cloud-images/+bug/2038894 is a related bug to
track specifically the introduction of listening port 5353
--
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/2032933
cloud minimized and non minimized images have now been tested with
6.5.0-9 kernel from -proposed and pass our lxd-start-stop test suite
which was failing and which is the test suite which prompted this whole
thread. +1
--
You received this bug notification because you are a member of Kernel
Public bug reported:
Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing
a regression in our cloud image tests. The test runs the following:
```
lxd init --auto --storage-backend dir
lxc launch ubuntu-daily:mantic mantic
lxc info mantic
lxc exec mantic -- cloud-init status
I have also successfully verified that -proposed amd64 kernel
`6.5.0-7-generic` results in successful network configuration when
tested using qemu on an amd64 host with older hardware (ThinkPad T460
with 6th gen intel i5 which is the same hardware which we were able to
reproduce the issue on
@xnox I have successfully verified that -proposed arm64 kernel
`6.5.0-7-generic` results in successful network configuration when
tested using qemu on an amd64 host. See
https://people.canonical.com/~philroche/20231003-mantic-minimal-
proposed-kernel/ for cloud-init logs, some debug output and
I have confirmed that this issue with not being able to capture kernel
dump with a mantic arm64 kernel is not new. using the arm64 6.5 kernel
(6.5.0-5) in the release pocket I captured the following during test.
```
ubuntu@cloudimg:~$ sudo kdump-config show
DUMP_MODE: kdump
Public bug reported:
While testing the 6.5.0-6-generic proposed arm64 generic kernel I
encountered issues being able to use kdump.
After enabling -proposed and installing the -proposed 6.5.0-6 kernel and
rebooting I encountered the following:
`kdump-config show` shows `current state:Not
cloud-init bug filed @ https://github.com/canonical/cloud-
init/issues/4451
** Bug watch added: github.com/canonical/cloud-init/issues #4451
https://github.com/canonical/cloud-init/issues/4451
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Description changed:
Following a recent change from linux-kvm kernel to linux-generic kernel
- in the mantic minimized images there is a reproducable bug where a guest
- VM does not have an IP address assigned as part of cloud-init
+ in the mantic minimized images, there is a reproducable
There is a related bug @
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036968 which might
have affected boot speed.
--
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/2032933
Title:
** 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/2036968
Title:
Mantic minimized/minimal cloud images do not
@paelzer agreed. Good plan.
--
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/2032933
Title:
Mantic (23.10) minimal images increase in memory consumption, port
usage and processes
@paelzer given the above findings and discussion, I would like to mark
this as Invalid for cloud-images project and continue the conversation
in the context of kernel only. +1 / -1 ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
** Description changed:
- The Mantic (Ubuntu 23.10) images are undergoing some big changes prior
- to 23.10 release in October.
+ The Mantic (Ubuntu 23.10) download/qcow2 images available @
https://cloud-images.ubuntu.com/minimal/
+ are undergoing some big changes prior to 23.10 release in
I have uploaded further data now to
https://people.canonical.com/~philroche/20230824-manticl-minimal-
LP2032933/server-metrics/ with kernelmodules, kernelconfig, services,
timers etc. for each of the three images being inspected. This
additional data was gathered with a modified fork of the
@paelzer
> The change of the image build sadly combined it all
See the description noting
https://people.canonical.com/~philroche/20230824-manticl-minimal-
LP2032933/ which should help in determining where the changes were
introduced as I have provided three images across the various stages of
The diff in process count from kernel change image -> kernel change +
seed change image is actually a reduction in processes - see diff @
https://pastebin.ubuntu.com/p/PXtQM9gB2K/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
CPC are seeing this issue in _all_ minimal cloud images testing with LXD
snap version 4.2 or greater. This blocks promotion of all minimal cloud
download images and blocks build and publication of both daily and
release cloud images.
--
You received this bug notification because you are a member
It appears that a bug was already filed against netcat
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1780316
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1861704
Public bug reported:
Following some debug of the docker.io package in universe, we (Canonical
CPC) discovered that the ubuntu-fan package from main and the netcat-
traditional package from universe were being installed.
This was due to the following dependency/recommends tree:
* docker.io (in
Myself and @kamalmostafa spoke and the issue is not obvious especially
as linux-azure is installed in the base image too which does not exhibit
the issue.
Although not obvious @kamalmostafa did suspect the issue to lie
somewhere with random number generation and a related package/kernel
patch.
@kamalmostafa @mhcerri
I noticed that linux-azure 4.18.0.1003.3 was uploaded to cosmic-proposed
so I built a new test image.
For convenience I have imported your SSH keys to 'ssh
ubuntu@51.140.217.58'.
All logs and VHD etc. have been uploaded to https://private-
On request on IRC I have tried a new image with linux-azure
4.18.0.1002.2 from cosmic-proposed.
This too exhibited the slow boot
5min 19.070s (kernel) + 41.724s (userspace) = 6min 794ms
Full logs @ https://private-fileshare.canonical.com/~philroche/azure-
cosmic-20181001/
--
You received this
** Attachment added: "cosmic minimal image with linux-azure 4.18.0.1002.2 (from
cosmic-proposed) boot log"
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1795017/+attachment/5195337/+files/chohv4Va7Ahx7-vm-imagedebug-boot.log
--
You received this bug notification because you are
Public bug reported:
Hi,
We're planning to share a new Cosmic minimal image for Azure including
the linux-azure custom kernel.
I have found boot speed increase from ~55s in non minimal image to over
6mins for minimal image.
I have gathered boot log, systemd logs and cloud-init logs for this
The meta-packages have been rolled back and the fix is in progress of
being applied and uploaded.
--
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/1779961
Title:
Boot delays with
Public bug reported:
We (Canonical CPC) are seeing an issue with today's build of the bionic
minimal cloud images. Boot stops at "Starting Initial cloud-init job
(metadata service crawler)..." for nearly 5 minutes (booting on
scalingstack and locally with kvm) this is with a new kernel, but
39 matches
Mail list logo
