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

Xen on Raspberry Pi 4


  • To: xen-users@xxxxxxxxxxxxxxxxxxxx
  • From: Paul Leiber <paul@xxxxxxxxxxxxxxxx>
  • Date: Wed, 2 Aug 2023 22:42:00 +0200
  • Arc-authentication-results: i=1; strato.com; arc=none; dkim=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; t=1691008922; s=strato-dkim-0002; d=strato.com; h=To:Subject:From:Date:Message-ID:Cc:Date:From:Subject:Sender; bh=YBV9Ei4sTmnveyzsClm1yBjVMJJrZjRtNah6fh4mZVw=; b=YxHhNCWNbI33h2W8JbQLUiXPT+NqUvbDXhGh1CbW3Hqk2fxC34AtW0VpJLb1YCActt ZrIEscxelWmitPbtwlJLdJuT4SEifsN4j5QqP1lkxlNDlTPqIF0DBb9ZsBB9TcyZ34/P aSpH6cLKX8oac6eRlpZYCKt5XuwoA/51UpxX7a0uJMLENitUtfYEjLfAXPwB5DOBi+RY /2GviqOuAn0DytpMn7C/kE3NqLzoB97fCQ1VghKkdVF1cfwAqAi1nMGvSJGDBbQ27L1W VuVFdy1qrdm5kBGlr6ANcxFX44nLfBoWCTbh32aKffrrTdZSBW7c7lGbWs8O7Svs1qy3 MSmw==
  • Arc-seal: i=1; a=rsa-sha256; t=1691008922; cv=none; d=strato.com; s=strato-dkim-0002; b=QF/kqPVZyAoBoT52at5WKLkY5/EBt+5cTpEgQSKaN67MFArzLlhgoJJ7B1bxye0IxW 6q82vbNBUPZ7TVyXm5Eg1Japvs2FEEJv4jsUfcnC8ZxbI4jhKtcxy64UBqYyNrK4tXx3 RRscX1BLyqUzLX03vIj/sduj75+yv8vHb95l1r8pty9KtgzTkMcHGPBOUXVtzw9+ogY0 djmo7Cs9muDxitRvdghMuq5LymzMKDKMAKte72BAcfez8dvyy5h92a8UJIsRS88jXKRe r/kUr9Jc/zrOeaOcz0Z3Gz8harwP9kpMT6BeUup22G4gqjQwDHr4PdOpLWY4hgbqyiFK JWhw==
  • Delivery-date: Wed, 02 Aug 2023 20:43:04 +0000
  • List-id: Xen user discussion <xen-users.lists.xenproject.org>

Hi list,

Now that the devices are available again, I got hold of a Raspberry Pi 4 (8 GB) which I am currently trying to set up Xen on for using it as a backup server.

What I did was to install a standard Debian distribution booted via EFI/GRUB2 (following https://forums.raspberrypi.com/viewtopic.php?t=282839) and then install the xen-System-arm64 package via apt. I have output on a console via UART (at least when booting Debian without Xen, see hypothesis 3 below).

Booting Debian without Xen is working fine. (Although I only see the Grub selection menu via UART when no HDMI is plugged in while booting.)

Selecting Xen in Grub leads to the following output on the console right after Grub hands over:

Loading Xen 4.17-arm64.efi ...
Loading Linux 6.1.0-10-arm64 ...
Loading initial ramdisk ...
Using modules provided by bootloader in FDT
Xen 4.17.2-pre (c/s ) EFI loader

And then the output stops.

I have four hypotheses (not mutually exclusive, and there are very probably unknown unknowns on my side):

1. Booting Xen via EFI is not working, and I need to use U-Boot as described in https://xenproject.org/2020/09/29/xen-on-raspberry-pi-4-adventures/

2. The Debian package xen-system-arm64 is not suitable for this purpose and I need to compile Xen from scratch

3. I got the console settings wrong (I currently use the settings from https://xenproject.org/2020/09/29/xen-on-raspberry-pi-4-adventures/ for Xen command line specified in Grub, but I also tried a lot of different settings), and Xen is actually doing something, but I don't see the output.

4. There is something wrong with my setup and I need to change specific EFI and/or other settings.

Has anybody got a similar setup working and can give me hints?

I am aware of https://github.com/dornerworks/xen-rpi4-builder, I might try this as one of the next steps, but I'd rather stick with Debian, if possible.

Thanks,

Paul



 


Rackspace

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