There actually is no need to debug further on my non-maas PXE setup. As identified before - your setup breaks due to [ 20.690329] Initramfs unpacking failed: junk in compressed archive Everything else is a follow on issue, with eventually: [ 22.524541] VFS: Cannot open root device "squash:http://172.16.99.2:5248/images/ubuntu/amd64/generic/bion"; or unknown-block(0,0): error -6
But since my setup as outlined in comment #31 PXE-boots the kernel+initramfs just fine I don't have to debug the rest. I already passed the point where it breaks for you. Can you use the above hints to get your breaking setup to also one-by-one remove components. I'd assume that removing libvirt makes no difference to your case. But you could maybe end up with: - PXE-served by MAAS = bad - PXE serverd by tftpd = good Or anything like it. So please follow the hints above (or get in touch if you need me to do so) and convert your setup until you can identify which component makes the decision for good/bad case. Also still I'd be open to get your kernel/initramfs/squash/pxe/.... files to implant it into my setup for a test if any of them is the trigger. -- 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: Invalid Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Invalid 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. 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
