1. Yocto
  2. Messages

Re: [ADT] Sysroot setup issue

Zhang, Jessica
 

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@... [mailto:yocto-bounces@...] On Behalf Of Rudolf Streif
Sent: Tuesday, August 21, 2012 1:17 PM
To: yocto@...
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_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

 

Join {yocto@lists.yoctoproject.org to automatically receive all group messages.