Not able to boot 2nd secondary VM

[Arun KS]

Hello,

I m trying to boot two VMs. Does Hafnium supports multiple VMs currently?.

1 secondary VM is working fine.

Logs with 2 secondary VMs,

qemu-system-aarch64 -M virt -cpu cortex-a57 -nographic -machine virtualization=true -kernel  hafnium/out/qemu_aarch64_clang/hafnium.bin -initrd initrd.img -append "rdinit=/sbin/init"

Initialising hafnium

text: 0x40001000 - 0x40008c38

rodata: 0x40009000 - 0x40009da0

data: 0x4000a000 - 0x40061c50

Supported bits in physical address: 44

Stage 2 has 4 page table levels with 1 pages at the root.

Memory range:  0x40000000 - 0x47ffffff

Ramdisk range: 0x44000000 - 0x453e5dff

Copying primary to 0000000040080000

Loading vmlinuz

Loaded with 4 vcpus, entry at 0x46800000

Loading vmlinuz

Loaded with 2 vcpus, entry at 0x45000000

FDT failed validation.

Panic: plat_update_boot_params failed

Regards,

Arun

[Arun KS]

Printing fdt address show memory overlap with 2nd VM.

Initialising hafnium

text: 0x40001000 - 0x40008c48

rodata: 0x40009000 - 0x40009db0

data: 0x4000a000 - 0x40061c50

Supported bits in physical address: 44

Stage 2 has 4 page table levels with 1 pages at the root.

Memory range:  0x40000000 - 0x47ffffff

Ramdisk range: 0x44000000 - 0x453e5dff

Copying primary to 0000000040080000

Loading vmlinuz

Available memory mem = 0x1800000 limit - next = 0x12a1a00

Loaded with 4 vcpus, entry at 0x46800000

Loading vmlinuz

Available memory mem = 0x1800000 limit - next = 0x12a1a00

Loaded with 2 vcpus, entry at 0x45000000

FDT address 0x45400000

FDT failed validation.

Panic: plat_update_boot_params failed

Regards,

Arun

[Johnson Lu]

Can you share the vms.txt on your side?

Do you ever boot up system with one VM now?

在 2019年1月4日星期五 UTC+8下午5:08:00，Arun KS写道：

[Arun Sudhilal]

On Fri, Jan 4, 2019 at 2:58 PM Johnson Lu <gf...@163.com> wrote:
>
> Can you share the vms.txt on your side?

vms.txt
25165824 4 vmlinuz
25165824 2 vmlinuz

>
> Do you ever boot up system with one VM now?

Yes. Single VM boots fine.

I have put some prints and it show that second VM image is getting
copied on top of FDT

Loaded with 2 vcpus, entry at 0x45000000
FDT address 0x45400000

vmlinuz image is around 19MB.

Regards,
Arun

> --
> You received this message because you are subscribed to the Google Groups "Hafnium" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to hafnium-discu...@googlegroups.com.
> To post to this group, send email to hafnium...@googlegroups.com.
> To view this discussion on the web, visit https://groups.google.com/d/msgid/hafnium-discuss/2f8fa751-70b2-4874-94c3-c49052e833d3%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Arun KS]

After increasing the machine memory to 512MB(using -m 512M as argument to qemu), I m able to boot second secondary VM.

/ # insmod hafnium.ko

[    9.627010] hafnium: loading out-of-tree module taints kernel.

[    9.656869] NET: Registered protocol family 19

[    9.657996] Hafnium successfully loaded with 2 VMs:

[    9.658444]  VM 1: 4 vCPUS

[    9.658699]  VM 2: 2 vCPUS

But, may be the correct fix is to keep the fdt memory carved out or reserved from hafnium memory allocator.

Regards,

Arun

> To unsubscribe from this group and stop receiving emails from it, send an email to hafnium-discuss+unsubscribe@googlegroups.com.
> To post to this group, send email to hafnium-discuss@googlegroups.com.

[Johnson Lu]

I use the same machine memory and VM memory, can also successfully load VM. But how do you know it can boot up now? Doesn't any thing more needed to boot up the VM?

在 2019年1月8日星期二 UTC+8下午3:55:38，Arun KS写道：

> To unsubscribe from this group and stop receiving emails from it, send an email to hafnium-discu...@googlegroups.com.
> To post to this group, send email to hafnium...@googlegroups.com.