[meta-virtualization] failure to build xen minimal

McGillion, Brian brian.mcgillion at intel.com
Wed Apr 27 05:32:44 PDT 2016


Hi,

Using the master branch, I am getting the following errors when trying to
build the xen-image-minimal.

"""""""""""""""
ERROR: xen-image-minimal-1.0-r0 do_bootimg: Function failed:
build_syslinux_cfg (log file is located at
/storage/yocto/poky/build/tmp/work/intel_corei7_64-poky-linux/xen-image-minimal/1.0-r0/temp/log.do_bootimg.13471)
ERROR: Logfile of failure stored in:
/storage/yocto/poky/build/tmp/work/intel_corei7_64-poky-linux/xen-image-minimal/1.0-r0/temp/log.do_bootimg.13471
Log data follows:
| DEBUG: Executing python function do_bootimg
| DEBUG: Executing shell function build_syslinux_cfg
|
/storage/yocto/poky/build/tmp/work/intel_corei7_64-poky-linux/xen-image-minimal/1.0-r0/temp/run.build_syslinux_cfg.13471:
104:
/storage/yocto/poky/build/tmp/work/intel_corei7_64-poky-linux/xen-image-minimal/1.0-r0/temp/run.build_syslinux_cfg.13471:
cannot create : Directory nonexistent
| WARNING: exit code 2 from a shell command.
| DEBUG: Python function do_bootimg finished
| ERROR: Function failed: build_syslinux_cfg (log file is located at
/storage/yocto/poky/build/tmp/work/intel_corei7_64-poky-linux/xen-image-minimal/1.0-r0/temp/log.do_bootimg.13471)
ERROR: Task 16
(/storage/yocto/poky/meta-virtualization/recipes-extended/images/
xen-image-minimal.bb, do_bootimg) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3455 tasks of which 3454 didn't need to be
rerun and 1 failed.
No currently running tasks (3160 of 3457)

Summary: 1 task failed:
  /storage/yocto/poky/meta-virtualization/recipes-extended/images/
xen-image-minimal.bb, do_bootimg
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
""""""""""""""""""""

This is related to:

build_syslinux_cfg() {
        echo "ALLOWOPTIONS 1" > ${SYSLINUXCFG}
        echo "DEFAULT boot" >> ${SYSLINUXCFG}
        echo "TIMEOUT 10" >> ${SYSLINUXCFG}
        echo "PROMPT 1" >> ${SYSLINUXCFG}
        echo "LABEL boot" >> ${SYSLINUXCFG}
        echo "  KERNEL mboot.c32" >> ${SYSLINUXCFG}
        echo "  APPEND /xen.gz loglvl=all guest_loglvl=all console=com1,vga
com1=115200,8n1 --- /vmlinuz ramdisk_size=32768 root=/dev/ram0 rw
console=hvc0 earlyprintk=xen console=tty0 panic=10 LABEL=boot debugshell=5
--- /initrd" >> ${SYSLINUXCFG}
}

How can I trace where SYSLINUXCFG is being set and does anyone know why
this might be failing?

Thanks,
Brian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-virtualization/attachments/20160427/c8f35e98/attachment.html>


More information about the meta-virtualization mailing list