On Mon, Jan 14, 2019 at 1:55 PM Thiago Martins <email address hidden>
wrote:
> @Ryan,
>
> The working XML file is attached here, with 2048 MB of RAM.
>
> NOTE: This XML was created using Virt-Manager, then, MaaS took it over
> after being "refreshed".
>
Thanks!
If you drop the <os> section (which is what tells libvirt to boot via UEFI)
does your VM still work?
Note that MAAS boots UEFI images with grub2[1], not pxeboot/ipxe/seabios;
so I think we can narrow down the
error to the non-uefi case which may help find the issue.
On Mon, Jan 14, 2019 at 1:55 PM Thiago Martins <email address hidden>
wrote:
> @Ryan,
>
> The working XML file is attached here, with 2048 MB of RAM.
>
> NOTE: This XML was created using Virt-Manager, then, MaaS took it over
> after being "refreshed".
>
Thanks!
If you drop the <os> section (which is what tells libvirt to boot via UEFI)
does your VM still work?
<os> "pc-i440fx- bionic" >hvm</type> >/usr/share/ OVMF/OVMF_ CODE.fd< /loader> /var/lib/ libvirt/ qemu/nvram/ vunft-1_ VARS.fd< /nvram>
<type arch="x86_64" machine=
<loader readonly="yes" type="pflash"
<nvram>
</os>
Note that MAAS boots UEFI images with grub2[1], not pxeboot/ ipxe/seabios;
so I think we can narrow down the
error to the non-uefi case which may help find the issue.
1. images. maas.io/ ephemeral- v3/daily/ bootloaders/ uefi/amd64/ 20181123. 0/
http://
> /bugs.launchpad .net/maas/ +bug/1797581/ +attachment/ 5229030/ +files/ vunft-1. xml /bugs.launchpad .net/bugs/ 1797581 /bugs.launchpad .net/maas/ +bug/1797581/ +subscriptions
> Cheers!
> Thiago
>
> ** Attachment added: "vunft-1.xml"
>
> https:/
>
> --
> You received this bug notification because you are subscribed to qemu in
> Ubuntu.
> https:/
>
> 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:/
>