All of the steps above will result in an error when booting DomU as there is no rootFS included in Dom0's RootFS. The Dom0 kernel image is included in the Dom0 rootFS which is why the kernel boots but then panics when no rootFS can be found.
The config files can be edited to point to a specific kernel image and rootFS to use when booting DomU. This image and configuration is up to the user to determine and select. The kernel used in the examples above is just the Dom0 kernel. If you would like a specific DomU kernel you will need to build and boot that yourselvf.
One of the options to get the rootFS into the Dom0 kernel image is to add a diff similar to this to the meta-petalinux layer. This diff has been applied onto the 2017.1 (morty) release of meta-petalinux
diff --git a/recipes-extended/xen/xen_4.8.0.bbappend b/recipes-extended/xen/xen_4.8.0.bbappend
index 96adee9..91cb5b7 100644
--- a/recipes-extended/xen/xen_4.8.0.bbappend
+++ b/recipes-extended/xen/xen_4.8.0.bbappend
@@ -17,6 +17,7 @@ FILES_${PN}-xl_append = " \
/etc/xen/example-pvnet.cfg \
/etc/xen/example-simple.cfg \
/etc/xen/passthrough-example-part.dtb \
+ /boot/Image \
"
DEPENDS += "u-boot-mkimage-native"
@@ -44,4 +45,8 @@ do_install_append() {
install -m 0644 ${WORKDIR}/example-simple.cfg ${D}/etc/xen/example-simple.cfg
install -m 0644 ${WORKDIR}/passthrough-example-part.dtb ${D}/etc/xen/passthrough-example-part.dtb
+
+ if [ -f ${DEPLOY_DIR_IMAGE}/Image ]; then
+ install -m 0644 ${DEPLOY_DIR_IMAGE}/Image ${D}/boot/Image
+ fi
}