@sfeole Thanks for the Dup hit that as well now - as all others I ask you to please help to catch the data needed to finally recreate and debug this.
>From IRC: [07:00] <cpaelzer> sfeole: please attach your guest XML, and the used initrd and kernel to the bug [07:02] <cpaelzer> best would be also the pxeconfig that is provided @MAAS Team So far this only occurred with MAAS and all other tries to recreate worked. I wonder if either TFTP or the PXE loader used could be the trigger of the bug. Therefore (from IRC as well): [07:02] <cpaelzer> roaksoax: on this bug one of the components we still have to verify if it is related is the way you provide the TFP [07:02] <cpaelzer> could you outline on the bug how users once they hit the bug could extract that and attach it to the bug [07:03] <cpaelzer> that way we can hopefully finally recreate the case I tried so back in comment #31, but that was only trying to recreate your setup. For PXEconfig (I was guessing) and TFTP (I used the normal tftpd package) we could still get more similar to your setup. I'll add a section to the description of the bug what users are supposed to attach, it would be great if you could help to outline how users can get those. @MAAS Team [07:03] <cpaelzer> and IIRC you don't use tftpd or such but something maas internal for tftpd is that right - could you outline how one could use/setup this so that we can compare tftpd vs maas-tftpd as well? That is an extra question to that above, if you could help here as well that would be great. ** Description changed: 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) -- 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
