From: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
To: "L, John Preetham (893)" <john_preetham.l@daimlertruck.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Ruslan Shymkevych <Ruslan_Shymkevych@epam.com>
Subject: Re: Request for Documentation on Bringing Up Xen on R-Car H3e (H3ULCB)
Date: Tue, 6 May 2025 11:21:42 +0000 [thread overview]
Message-ID: <87v7qec7cr.fsf@epam.com> (raw)
In-Reply-To: <FR2PPF86245AF1B97AC233A5D738AD088B4B88E2@FR2PPF86245AF1B.DEUP281.PROD.OUTLOOK.COM> (John Preetham L.'s message of "Mon, 5 May 2025 04:25:23 +0000")
Hi John,
"L, John Preetham (893)" <john_preetham.l@daimlertruck.com> writes:
> Hi Volodymyr,
>
> Thank you once again for the detailed explanation and the helpful resources.
>
> With your guidance, I was able to bring up the XEN hypervisor on the R-Car H3e board successfully. I really appreciate your support.
>
I glad that it worked.
> Now, I'm looking to move forward with bringing up a QNX guest on the
> XEN hypervisor.
If your QNX guest supports arm64 boot protocol (which is defined at [1])
and supports either Xen HVC console or SBSA (pl011-ish) UART - you can just
boot it by providing kernel= option in your domain configuration file.
This at least should give you access to guest's serial console, which is
a good starting point to further bring-up.
> Could you please share the procedure or steps you
> recommend for this?
If I'd did this, I'd done this in the following way:
1. Check that QNX kernel image is compatible with aarch64 boot
protocol. Most of projects (Linux kernel, Xen, U-boot, etc) use it and
it become de-facto standard, so probably QNX should support it too. But
if not - you'll need another loader to boot QNX. We have Xen-enabled
U-Boot, by the way.
2. Boot QNX kernel and get serial console working. As I said, - either via
HVC or SBSA. This is crucial, as you need some feedback from your guest
to understand what going on.
3. Boot rest of QNX environment. See what is working, fix things that
don't :) It would be great if QNX supports Xen PV drivers for block
and network devices, otherwise, you'll have to use virtio or
pass-through, which is somewhat more difficult to configure.
> It would also be very helpful if you could provide
> an example Device Tree Source (DTS) and
If you are not doing real device passthrough (and I recommend to
postpone this until you'll get your guest running) - you don't need any
DTS files. Xen toolstack will generate all the required DTS entries
automatically for the given configuration.
> XEN domain configuration (CFG)
> file for the QNX guest, if available.
No, we don't have any. We had experience with QNX guests, but that was
really long time ago and I don't think that any data survived. Anyways,
I recommend checking manual on xl.cfg ([2]).
Please note, that if you want to use SBSA uart, you need to enable it in
your configuration file. It should be vuart = "sbsa_uart", I
believe. Also, you'll have to run xl console with additional arguments
to make it access SBSA uart console, not default HVC one.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/arch/arm64/booting.rst?h=v6.15-rc5
[2] https://xenbits.xen.org/docs/unstable/man/xl.cfg.5.html
--
WBR, Volodymyr
prev parent reply other threads:[~2025-05-06 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 9:16 Request for Documentation on Bringing Up Xen on R-Car H3e (H3ULCB) L, John Preetham (893)
2025-01-23 0:35 ` Stefano Stabellini
2025-01-24 4:56 ` Volodymyr Babchuk
[not found] ` <8734ha2evr.fsf@epam.com>
[not found] ` <FR2PPF86245AF1B0938F55DAF4FF4E63A31B8E02@FR2PPF86245AF1B.DEUP281.PROD.OUTLOOK.COM>
2025-01-24 5:02 ` Volodymyr Babchuk
2025-05-05 4:25 ` L, John Preetham (893)
2025-05-06 11:21 ` Volodymyr Babchuk [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v7qec7cr.fsf@epam.com \
--to=volodymyr_babchuk@epam.com \
--cc=Ruslan_Shymkevych@epam.com \
--cc=john_preetham.l@daimlertruck.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.