Jason, thanks for chiming in - so far this was non-reproducible every time we looked at it. We had plenty of approaches with the MAAS team to this and later on with Thiago, but still miss the right data to continue.
Last time I asked - I think it was still Mike - that I'd really like to get the full set of binaries involved, but then IIRC he couldn't reproduce it with the newer images/kernel of that day. Maybe we can use this issue hitting you now as a new chance to get what we need to continue debugging to reach a resolution. @Jason - can I get from you the full set of elements used when you hit it? That would be: - which release are you on? - which qemu/libvirt/seabios/ovmf do you have installed exactly - can you share the XML that the guest is defined with We have the above from different cases, but it might be important to know which ones exactly are active in your case, so better check them. Finally - and that was what was missing before so far: - can you attach the set of binaries that are used which should be - cloud-img - kernel (as maas provides that directly to the guest in guest XML) - initrd (as maas provides that directly to the guest in guest XML) - describe your KVM Host server HW (so that we can test on something similar) As an alternative - can you provide a login on such a host which has a breaking guest defined. There we could work together fetching the required data? -- 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
