Hi Everyone,
I am currently exploring on bringing up XenGT for an Intel embedded board.
I came across this document relating to bringing up XenGT for the Sandy Bridge/Ivy Bridge/Haswell platform
https://www.intel.com/content/dam/www/public/us/en/documents/guides/xgengt-for-ivi-solutions-dev-kit-getting-started-guide.pdf
Our current Intel embedded board is up with an Yocto image integrated with the Intel BSP for the board. The board uses ABL boot loader.
I saw in the XenGT document for the Sandy Bridge/Ivy Bridge/Haswell platform, that there is mention of Qemu alone and no mention of any Intel BSPs. Don’t we require Intel BSP for dom0 kernel
to work in the XenGT hypervisor? Or is a generic version of Intel BSP integrated with the kernel image link
https://github.com/01org/XenGT-Preview-kernel.git.
Also, as we have an Yocto image in the Intel board, we might have to cross compile the Kernel, Xen and Qemu builds as mentioned in the link above for our Intel embedded board using a Linaro
toolchain. If not, is there a way, we can link this particular version of XenGT directly with our Yocto image for the Intel board by including the meta-virtualization layer as mentioned in the link
http://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/about/ and doing ‘bitbake xen image minimal’?
Please advise which is the correct route to take in this regard.
Thanks
M
__________________________________________________________________ CONFIDENTIALITY NOTE: This electronic message (including any attachments) may contain information that is privileged, confidential, and proprietary. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is strictly prohibited. If you received this electronic message in error, please immediately reply to the sender that
you have received this communication and destroy the material in its entirety, whether in electronic or hard copy format. Although Rivian Automotive Inc. has taken reasonable precautions to ensure no viruses are present in this email, Rivian accepts no responsibility
for any loss or damage arising from the use of this email or attachments.
