[yocto] [ADT] Sysroot setup issue

Wed Aug 22 17:36:46 PDT 2012

Hi Jessica,

Thanks while responding while on vacation.

No worries. I have resolved the NFS boot issue. I entirely missed that my
dev system had a firewall running blocking ports 3048 and 3049 used by the
user-space rpc.mountd and rpc.nfsd daemons that runquemu-export-rootfs sets
up. My fault. Sorry about that.

The kernel images may be an incorrect expectation from my side. I checked
the ADT installer scripts and they do not seem to do anything with the
kernel images they download. From my point of view it would make sense to
copy them into <sysroot>/boot.

The adt_installer.conf file suggests that minimal, minimal-dev, sato,
sato-dev, sato-sdk,lsb, lsb-dev, lsb-sdk are valid images
for YOCTOADT_ROOTFS_<arch>, but really only the *-dev and *-sdk images make
sense for an ADT as the others are missing the dev headers and libs.

While the ADT installer downloads all the image files specified in
YOCTOADT_ROOTFS_<arch> it really only extracts the one specified
by YOCTOADT_TARGET_SYSROOT_IMAGE_<arch> into the location specified
by YOCTOADT_TARGET_SYSROOT_LOC_<arch>. If you keep the installer files
around you can of course later install them with runqemu-extract-sdk but
that's not necessarily intuitive.

I eventually extracted all the sysroot images into separate directories and
created a link to the one I wanted to use with the name specified
by YOCTOADT_TARGET_SYSROOT_LOC_<arch>. That works well.

I don't know what the overall direction of development for the ADT
installer is but I could make some patches to address these items if that
makes sense to the community.

:rjs

On Wed, Aug 22, 2012 at 5:16 PM, Zhang, Jessica <jessica.zhang at intel.com>wrote:

>  Hi Rudi,****
>
> ** **
>
> I’m currently on vacation so have very limited access to my YP setup.
>  We’ve been using the sysroot and nfs like below to start qemu after
> adt-installation, can you give it a try to see whether there’s problem or
> not?****
>
> ** **
>
> Runqemu youradtinstallerdir/download_image/bzImage-qemux86.bin
> ${HOME}/test-yocto/x86****
>
> ** **
>
> ** **
>
> Scott,****
>
> ** **
>
> Can you help answer or look into the boot dir missing kernel file issue
> that Rudi’s reporting to see whether it’s a bug on our end?****
>
> ** **
>
> Thanks,****
>
> Jessica****
>
> ** **
>
> *From:* yocto-bounces at yoctoproject.org [mailto:
> yocto-bounces at yoctoproject.org] *On Behalf Of *Rudolf Streif
> *Sent:* Tuesday, August 21, 2012 1:17 PM
> *To:* yocto at yoctoproject.org
> *Subject:* [yocto] [ADT] Sysroot setup issue****
>
> ** **
>
> Hi, ****
>
> ** **
>
> I am trying to setup the ADT using an ADT installer. I have downloaded the
> installer from
> http://downloads.yoctoproject.org/releases/yocto/yocto-1.2.1/adt_installer/ as
> well as created my own installer using a build environment with Denzil
> 7.0.1.****
>
> ** **
>
> The adt_installer.conf contains these settings:****
>
> ** **
>
> YOCTOADT_REPO="http://adtrepo.yoctoproject.org/1.2.1"****
>
> YOCTOADT_TARGETS="arm x86"****
>
> YOCTOADT_QEMU="Y"****
>
> YOCTOADT_NFS_UTIL="Y"****
>
> ** **
>
> YOCTOADT_ROOTFS_arm="minimal"****
>
> YOCTOADT_TARGET_SYSROOT_IMAGE_arm="minimal"****
>
> YOCTOADT_TARGET_SYSROOT_LOC_arm="$HOME/test-yocto/arm"****
>
> ** **
>
> YOCTOADT_ROOTFS_x86="minimal"****
>
> YOCTOADT_TARGET_SYSROOT_IMAGE_x86="minimal"****
>
> YOCTOADT_TARGET_SYSROOT_LOC_x86="$HOME/test-yocto/x86"****
>
> ** **
>
> The installer downloads kernel and root fs images. After the installation
> has finished****
>
> ** **
>
> ${HOME}/test-yocto/arm/boot does not contain any kernel images and****
>
> ** **
>
> ${HOME}/test-yocto/x86/boot only contains a empty link bzImage ->
> bzImage-3.2.18-yocto-standard****
>
> ** **
>
> I manually copied the x86 kernel image bzImage-qemux86.bin from the
> download_image directory of the extracted installer tarball into the
> directory, initialized the ADT environment and then ran****
>
> ** **
>
>
> runqemu ${HOME}/test-yocto/x86/boot/bzImage-qemux86.bin ${HOME}/test-yocto/x86
> ****
>
> ** **
>
> The NFS user-space server initializes on the tap0 interface and the kernel
> boots. However, it panics because it cannot locate the root fs. rpcbind is
> started with the -i option on my system.****
>
> ** **
>
> I also ran QEMU directly using:****
>
> ** **
>
> /opt/poky/1.2.1/sysroots/x86_64-pokysdk-linux/usr/bin/qemu -kernel
> /home/rudi/test-yocto/x86/boot/bzImage-qemux86.bin -show-cursor -usb
> -usbdevice wacom-tablet -vga vmware -enable-gl -no-reboot -m 128 --append
> "root=/dev/nfs nfsroot=192.168.100.199://home/rudi/test-yocto/x86 rw
> ip=192.168.100.38::192.168.100.199:255.255.255.0 mem=128M
> oprofile.timer=1 "****
>
> ** **
>
> with my dev system's NFS server running and exporting the file system (I
> verified that I can mount the exported file system via NFS).****
>
> ** **
>
> Questions:****
>
>    1. Why do the sysroot boot directory not contain any kernel images? I
>    don't think that is what it is supposed to be.****
>    2. Is there anything broken with the sysroot causing the boot process
>    to fail when the kernel tries to access the root fs?****
>    3. Any hints on how to fix it?****
>
>  Thanks,****
>
> Rudi****
>
> ** **
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20120822/c30f77ec/attachment.html>