After DHCP is up it works just fine. (initramfs) wget http://192.168.122.1:80/squashfs Connecting to 192.168.122.1:80 (192.168.122.1:80) squashfs 100% |*******************************| 174M 0:00:00 ETA (initramfs) mount -t squashfs squashfs /root (initramfs) mount rootfs on / type rootfs (rw) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=1007984k,nr_inodes=251996,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=204128k,mode=755) tmpfs-root on /media/root-rw type tmpfs (rw,relatime) copymods on /root/lib/modules type tmpfs (rw,relatime) /dev/loop0 on /root type squashfs (ro,relatime)
So if anyone has a good hint how to get out of the ip/squash-root ordering issue let me know. That would - as mentioned - help to most likely exclude maas and libvirt from the suspects to be able to debug further. -- 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
