Bug 11803 - runqemu: use absolute path for nfs
Summary: runqemu: use absolute path for nfs
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: Scripts and Tools (show other bugs)
Version: 2.4
Hardware: x86 Multiple
: Undecided normal
Target Milestone: 2.4 M3
Assignee: Robert Yang
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-07-18 02:55 UTC by Robert Yang
Modified: 2017-07-18 03:07 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Yang 2017-07-18 02:55:23 UTC 
Reported by scott:

I have an Ubuntu 16.04 system.  I use these two commands from my poky/build directory:

These two command:

  $ runqemu-extract-sdk ~/Downloads/core-image-sato-dev-qemux86.tar.bz2 test-nfs

  $ runqemu qemux86 ./test-nfs

I never get to the interface in QEMU.  It sits and times out with a kernel panic message.  Here are my transcripts for each command both in pastebin:

https://pastebin.com/sK5E1xLp

https://pastebin.com/f92M7nGz

I could not copy any text in the QEMU window.. but did snap a photo of it that I am attaching.

This is because we must use absolute path when nfs.
Comment 1 Robert Yang 2017-07-18 03:07:47 UTC 
And I just found that I had fixed it:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=4d54ebab89595f0df38c58311b7bb012f591ec77