Added to the description what we need from anyone affected.
@Maas Team see former comment for the requested guiding of users how to get
this data.
The Maas task is back from incomplete to confirmed for providing these howto's
** Changed in: maas
Status: Incomplete => Confirmed
--
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
