Ran into this today, attaching the information requested in #51. Unable to commission/install 18.04 with "No minimum kernel"
MAAS version: maas 2.5.3-7533-g65952b418-0ubuntu1~18.04.1 all Guests kernel paniced on two hosts (host1 and host2), dpkg -l attached for each host. Console output from each failed guest (vm*_console.log) Libvirt xml from each failed guest (vm*.xml) attaching squashfs, boot-kernel, and boot-initrd used by MAAS for the failed boots. Running host kernels: host1: Linux host1 5.0.0-17-generic #18~18.04.1-Ubuntu SMP Wed Jun 5 12:43:23 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux host2: Linux host2 4.15.0-52-generic #56-Ubuntu SMP Tue Jun 4 22:49:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux regiond log of latest image download: 2019-06-22 23:14:06 regiond: [info] 127.0.0.1 GET /MAAS/images-stream/streams/v1/maas:v2:download.json HTTP/1.1 --> 200 OK (referrer: -; agent: python-simplestreams/0.1) 2019-06-22 23:14:09 regiond: [info] 127.0.0.1 GET /MAAS/images-stream/ubuntu/amd64/ga-18.04-lowlatency/bionic/20190621/boot-initrd HTTP/1 .1 --> 200 OK (referrer: -; agent: python-simplestreams/0.1) 2019-06-22 23:14:09 regiond: [info] 127.0.0.1 GET /MAAS/images-stream/ubuntu/amd64/ga-18.04-lowlatency/bionic/20190621/boot-kernel HTTP/1 .1 --> 200 OK (referrer: -; agent: python-simplestreams/0.1) 2019-06-22 23:14:19 regiond: [info] 127.0.0.1 GET /MAAS/images-stream/ubuntu/amd64/ga-18.04-lowlatency/bionic/20190621/squashfs HTTP/1.1 --> 200 OK (referrer: -; agent: python-simplestreams/0.1) 2019-06-22 23:14:22 regiond: [info] 127.0.0.1 GET /MAAS/images-stream/ubuntu/amd64/ga-18.04/bionic/20190621/boot-initrd HTTP/1.1 --> 200 OK (referrer: -; agent: python-simplestreams/0.1) 2019-06-22 23:14:23 regiond: [info] 127.0.0.1 GET /MAAS/images-stream/ubuntu/amd64/ga-18.04/bionic/20190621/boot-kernel HTTP/1.1 --> 200 OK (referrer: -; agent: python-simplestreams/0.1) 2019-06-22 23:14:27 regiond: [info] 127.0.0.1 GET /MAAS/images-stream/ubuntu/amd64/hwe-18.04-edge/bionic/20190621/boot-initrd HTTP/1.1 -- > 200 OK (referrer: -; agent: python-simplestreams/0.1) 2019-06-22 23:14:27 regiond: [info] 127.0.0.1 GET /MAAS/images-stream/ubuntu/amd64/hwe-18.04-edge/bionic/20190621/boot-kernel HTTP/1.1 -- > 200 OK (referrer: -; agent: python-simplestreams/0.1) 2019-06-22 23:14:30 regiond: [info] 127.0.0.1 GET /MAAS/images-stream/ubuntu/amd64/hwe-18.04-lowlatency-edge/bionic/20190621/boot-initrd HTTP/1.1 --> 200 OK (referrer: -; agent: python-simplestreams/0.1) 2019-06-22 23:14:31 regiond: [info] 127.0.0.1 GET /MAAS/images-stream/ubuntu/amd64/hwe-18.04-lowlatency-edge/bionic/20190621/boot-kernel HTTP/1.1 --> 200 OK (referrer: -; agent: python-simplestreams/0.1) 2019-06-22 23:14:31 regiond: [info] 127.0.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservi ce.ClusterClientService) 2019-06-22 23:14:35 regiond: [info] 127.0.0.1 GET /MAAS/images-stream/ubuntu/amd64/hwe-18.04-lowlatency/bionic/20190621/boot-initrd HTTP/ 1.1 --> 200 OK (referrer: -; agent: python-simplestreams/0.1) 2019-06-22 23:14:35 regiond: [info] 127.0.0.1 GET /MAAS/images-stream/ubuntu/amd64/hwe-18.04-lowlatency/bionic/20190621/boot-kernel HTTP/ 1.1 --> 200 OK (referrer: -; agent: python-simplestreams/0.1) 2019-06-22 23:14:39 regiond: [info] 127.0.0.1 GET /MAAS/images-stream/ubuntu/amd64/hwe-18.04/bionic/20190621/boot-initrd HTTP/1.1 --> 200 OK (referrer: -; agent: python-simplestreams/0.1) 2019-06-22 23:14:39 regiond: [info] 127.0.0.1 GET /MAAS/images-stream/ubuntu/amd64/hwe-18.04/bionic/20190621/boot-kernel HTTP/1.1 --> 200 OK (referrer: -; agent: python-simplestreams/0.1) -- 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Confirmed Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. So far this only occurred in MAAS environments and often went away with e.g. the next daily images. Therefore to reproduce and finally debug/fix this issue we'd need data from anyone being affected. This list will grow as we identify more that is needed. If you are affected, please attach to the bug - the kernel used to boot the guest - the initrd used to boot the guest - libvirt guest XML used to define the guest - PXE config provided to the guest - the cloud image used to start the guest (That will likely not fit as bug attachment, consider storing it somewhere and contact us) TODO: The Maas Team will outline how to get all these artifacts. TODO: add reference to the comment outlining this (once added) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
