Re: [Xen-users] How to boot domU and dom0 from a device tree

[Denis Obrezkov <denisobrezkov@xxxxxxxxx>]

I found out that I can get rid of that error if I load the same image to
another address space with -device loader. But then I get the error:
(XEN) ***************************************************
(XEN) PLEASE SPECIFY dom0_mem PARAMETER - USING 512M FOR NOW
(XEN) ***************************************************
(XEN) 3... 2... 1...
(XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
(XEN) *** LOADING DOMU cpus=1 memory=200000KB ***
(XEN) Loading Domd1 kernel from boot module @ 0000000043000000
(XEN) Loading ramdisk from boot module @ 0000000042000000
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Out of memory
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...

So, I don't understand how xen distribute the allocated memory and how
can it be allocated via a device tree.

On 6/10/19 12:09 PM, Denis Obrezkov wrote:
> Hello,
> 
> I  am trying to boot domU from a device tree. I want to use the same
> ramdisk and kernel image as for dom0. These are my u-boot commands:
> 
> fdt addr 0x44000000
> fdt resize
> fdt set /chosen \#address-cells <1>
> fdt set /chosen \#size-cells <1>
> fdt mknod /chosen module@0
> fdt set /chosen/module@0 compatible "xen,linux-zimage"
> "xen,multiboot-module"
> fdt set /chosen/module@0 reg <0x47000000 0x7cc561>
> fdt set /chosen/module@0 bootargs "rw root=/dev/ram rdinit=/sbin/init  
> earlyprintk=serial,ttyAMA0 console=hvc0 earlycon=xenboot"
> fdt mknod /chosen module@1
> fdt set /chosen/module@1 compatible "xen,linux-initrd"
> "xen,multiboot-module"
> fdt set /chosen/module@1 reg <0x42000000 0x11b680>
> 
> fdt mknod /chosen domU1
> fdt set /chosen/domU1 compatible "xen,domain"
> fdt set /chosen/domU1 \#address-cells <1>
> fdt set /chosen/domU1 \#size-cells <1>
> 
> fdt mknod /chosen/domU1 module@0
> fdt set /chosen/domU1/module@0 compatible "xen,linux-zimage"
> "xen,multiboot-module"
> fdt set /chosen/domU1/module@0 reg <0x47000000 0x7cc561>
> fdt set /chosen/domU1/module@0 bootargs "rw root=/dev/ram
> rdinit=/sbin/init console=hvc0 earlycon=xenboot"
> 
> fdt mknod /chosen/domU1 module@1
> fdt set /chosen/domU1/module@1 compatible "xen,linux-initrd"
> "xen,multiboot-module"
> fdt set /chosen/domU1/module@1 reg <0x42000000 0x11b680>
> 
> booti 0x49000000 - 0x44000000
> 
> I got: 
> 
> ....
> 
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Missing kernel boot module?
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) Could not set up DOM0 guest OS
> (XEN) ****************************************
> (XEN)
> (XEN) Reboot in five seconds...
> 
> I wasn't able to find instructions on how to run domU and dom0 images
> simultaneously.
> 

-- 
Regards, Denis Obrezkov

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-users