Thanks Kellen, I took your kernel/initrd and IPXE booted it fine via http from qemu's IPXE on a 2G guest. In the past we tried more (use squash, use tftp instead of http, use the same parmlines as maas, ...), but it all comes down to the same thing every time - only occurs inside Maas.
Therefore we are again back at my request to the Maas team to help me with this issue as it continues to not show up without Maas being involved. We had many discussions about this in the past, but I realized that with Mike many of these thoughts might have left. In a perfect world a Maas team member would set up a system using the Artifacts that @Krenshaw provided to reliable recreate the issue (with Maas) on an internal. Then we'd start a full afternoon debugging together (hangout with both of us on the same system) to one by one replace components of the Maas setup in order to finally get this to be debuggable without Maas (or have an idea where/what in side Maas things might break). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
