I didn't let me calm down - I found in the doc [1] that the switch might be on the VLAN and not the subnet (Hrm why?)
It was on the vlan http://horsea:5240/MAAS/#/vlan/5021 Not on the subnet http://horsea:5240/MAAS/#/subnet/11 There I found the "provide dhcp" entry \o/ That unlocked some understanding of what the range allocations would be like on vland/subnets. I reconfigured the range allocation and hit the "provide DHCP" switch. Looking back all is reasonable, just some stumbling on my first maas setup from scratch :-/ Must be funny for you seeing me struggle doing so :-) With that in place I created three pods with 2047/2048/2049 MB memory. ubuntu@node-horsea:~/maas$ virsh dumpxml horsea-kvm-pod-2047 | grep emor <memory unit='KiB'>2096128</memory> <currentMemory unit='KiB'>2096128</currentMemory> ubuntu@node-horsea:~/maas$ virsh dumpxml horsea-kvm-pod-2048 | grep emor <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> ubuntu@node-horsea:~/maas$ virsh dumpxml horsea-kvm-pod-2049 | grep emor <memory unit='KiB'>2098176</memory> <currentMemory unit='KiB'>2098176</currentMemory> They all went into the commissioning phase, but who would be surprised got stuck somewhere in there :-/ OTOH the bug says "composing crashes" so we might be at the right place, lets take a look at these three guests. [1]: https://docs.maas.io/devel/en/installconfig-network-dhcp#enabling-dhcp -- 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
