[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

On 10/06/2019 22:24, Denis Obrezkov wrote:

Hi Denis,

On 6/10/19 10:30 PM, Stefano Stabellini wrote:
On Mon, 10 Jun 2019, Denis Obrezkov wrote:
Also, I found out how to pass the amount of memory for dom0. And I
passed 256M. And I can see that in a device tree there is a memory node
with 4096M allocated. So, I don't understand why I have this error:

This is easy, the answer is below.

(XEN) Loading Domd0 kernel from boot module @ 0000000047000000
(XEN) Loading ramdisk from boot module @ 0000000042000000
(XEN) Allocating 1:1 mappings totalling 256MB for dom0:
(XEN) BANK[0] 0x00000050000000-0x00000060000000 (256MB)
(XEN) Grant table range: 0x00000049000000-0x00000049040000
(XEN) Allocating PPI 16 for event channel interrupt
(XEN) Loading zImage from 0000000138000000 to
(XEN) Loading dom0 initrd from 0000000042000000 to
(XEN) Loading dom0 DTB to 0x0000000058000000-0x0000000058001da8
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Scrubbing Free RAM in background
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) ***************************************************
(XEN) Please update your firmware.
(XEN) ***************************************************
(XEN) 3... 2... 1...
(XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
(XEN) *** LOADING DOMU cpus=1 memory=140000KB ***
(XEN) Loading Domd1 kernel from boot module @ 0000000043000000
(XEN) Loading ramdisk from boot module @ 0000000048000000
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Out of memory
(XEN) ****************************************
(XEN) Reboot in five seconds...

fdt commands passed via u-boot:

setenv xen_bootargs 'dom0_mem=256M'

You just need to give more memory to dom0. Use dom0_mem=1G or something
like that for a start.
But as far as I understand domU doesn't have enough memory and fails.   I
change dom0_mem to 1G but the problem still exists.

You are right, the problem is from DomU not Dom0...

fdt addr 0x44000000
fdt resize
fdt set /chosen \#address-cells <1>
fdt set /chosen \#size-cells <1>
fdt set /chosen xen,xen-bootargs \"$xen_bootargs\"
fdt mknod /chosen module@0
fdt set /chosen/module@0 compatible "xen,linux-zimage"
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"
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 set /chosen/domU1 \cpus <1>
fdt set /chosen/domU1 \memory <0 1310720>

... this property is used to tell how much memory the guest domU1 has. I am a bit surprised that 136MB of RAM is not enough, but you could try to bump it to 512MB or even 1GB and see.


Julien Grall

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.