Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 3137

General discussion • How to give display to Dom0 of xen on Raspberry pi 5

$
0
0
I am trying get xen running on raspberry pi 5. I am using Linux as dom0. I ran a zephyr hello world application as DomU which worked fine. I also have a linux with GUI as DomU. I want to get display output of dom0 using hdmi ( and domU linux afterwards ). How to give hdmi access to Dom0.

My boot.scr is

Code:

fdt addr ${fdt_addr}fatload mmc 0 0x2000000 xenfdt resize 2048fatload mmc 0 0x2200000 bcm2712-raspberrypi5-xen.dtbofdt apply 0x2200000fatload mmc 0 0x1200000 Imagefdt mknod /chosen module@1200000fdt set /chosen/module@1200000 compatible "multiboot,kernel" "multiboot,module"fdt set /chosen/module@1200000 reg <0x0 0x1200000 0x0 0x${filesize}>fdt set /chosen xen,dom0-bootargs "console=hvc0 earlycon=xen earlyprintk=xen clk_ignore_unused root=/dev/mmcblk0p2 rootfstype=ext4 rw rootwait";fdt set /chosen xen,xen-bootargs "console=dtuart dtuart=/soc@107c000000/serial@7d001000 dom0_mem=256M dom0_max_vcpus=1 xsm=flask flask=permissive";fatload mmc 0 0x2300000 xenpolicyfdt set /chosen/xenpolicy reg <0x0 0x2300000 0x0 0x${filesize} >setenv fdt_high 0xffffffffffffffffbooti 0x2000000 - ${fdt_addr}


bcm2712-raspberrypi5-xen.dts

Code:

/dts-v1/;/ {        fragment@0 {                target = <0xffffffff>;                __overlay__ {                        #address-cells = <0x02>;                        #size-cells = <0x02>;                        xenpolicy {                                compatible = "xen,xsm-policy\0multiboot-module";                        };                        dom0 {                                compatible = "multiboot,kernel\0multiboot,module";                                reg = <0x8000000 0x20000000 0x00 0x2000000>;                        };                };        };        fragment@1 {                target = <0xffffffff>;                __overlay__ {                        reg = <0x7d001000 0x1000>;                };        };        fragment@4 {                target = <0xffffffff>;                __overlay__ {                        xen,passthrough;                };        };        __fixups__ {                chosen = "/fragment@0:target:0";                uart10 = "/fragment@1:target:0";                pcie2 = "/fragment@4:target:0";        };};
The current problematic boot logs is:

Code:

[   15.963957] platform cam1_reg: deferred probe pending: reg-fixed-voltage: can't get GPIO[   15.972020] platform cam0_reg: deferred probe pending: reg-fixed-voltage: can't get GPIO[   15.980605] platform 1002000000.v3d: deferred probe pending: platform: supplier soc@107c000000:firmware:clocks not ready[   15.991546] platform 107c580000.hvs: deferred probe pending: platform: supplier soc@107c000000:firmware:clocks not ready[   16.002538] platform 107c701400.hdmi: deferred probe pending: platform: supplier soc@107c000000:firmware:clocks not ready[   16.013623] platform 107c706400.hdmi: deferred probe pending: platform: supplier soc@107c000000:firmware:clocks not ready[   16.024705] platform leds: deferred probe pending: leds-gpio: Failed to get GPIO '/leds/led-pwr'[   16.033592] platform 107d004000.spi: deferred probe pending: spi-bcm2835: no tx-dma configuration found - not using dma mode

Statistics: Posted by alumulti — Fri Jan 30, 2026 4:44 am



Viewing all articles
Browse latest Browse all 3137

Trending Articles