Hi I am trying to enable Xen in BSP with the help of reference manual. following are the steps I tried
mkdir fsl-auto-yocto-bsp
cd fsl-auto-yocto-bsp
repo init -u https://source.codeaurora.org/external/autobsps32/auto_yocto_bsp -b release/bsp28.0
repo sync
./sources/meta-alb/scripts/host-prepare.sh - (for the first time only)
source nxp-setup-alb.sh -m s32g274ardb2 (I am using GLDBOX)
bitbake fsl-image-base
after this I used "dd" command to send binaries to sdcard
sudo dd if=./fsl-image-base-s32g274ardb2.sdcard of=${DEVSD} bs=1M && sync
upto this, all are okay and I could boot the image and login.
but after enabling xen (DISTRO_FEATURES_append += "xen" into conf file)
even though I could see xen,IMage,.dtb file in the sdcard after flashing and also two rootfs are also there (expectated), but I am facing issue when trying to use xl commands..
I used the same command (sudo dd if=./fsl-image-base-s32g274ardb2.sdcard of=${DEVSD} bs=1M && sync) to send the binaries again
I didn't change any parameter in uboot because as per the document I understood that Xen will get loaded by uboot automatically instead of kernal image
root@s32g274ardb2:~# xl info
xencall: error: Could not obtain handle on privileged command interface: No such file or directory
libxl: error: libxl.c:102:libxl_ctx_alloc: cannot open libxc handle: No such file or directory
cannot init xl context
root@s32g274ardb2:~#
Thanks in advance
Solved! Go to Solution.
Hi,
The version you are using is an old one (BSP 32 was released just last week).
However, in case you need to use BSP 28, please run the following commands in the u-boot prompt:
=> env default -a
=> saveenv
This command needs to be ran only once per deployment. In BSP32 there's no need to run these commands.
Thank you for the quick response.
It helped and worked..Kudosssssss..
Hi,
The version you are using is an old one (BSP 32 was released just last week).
However, in case you need to use BSP 28, please run the following commands in the u-boot prompt:
=> env default -a
=> saveenv
This command needs to be ran only once per deployment. In BSP32 there's no need to run these commands.