Bug 2885

Summary: [qemux86] Not able to bring up qemu sato-sdk image
Product: [Build System, Metadata & Runtime] OE-Core Reporter: veera <veerabrahmamvr>
Component: virtual machinesAssignee: Saul Wold <sgw>
Status: VERIFIED NOTABUG QA Contact:
Severity: normal    
Priority: Medium CC: jessica.zhang, laurentiu.serban, sanil.kumar, venkatarg
Version: 1.3   
Target Milestone: 1.3 M4   
Hardware: x86   
OS: arm   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---
Attachments:
Description Flags
Kernel panic screen shot is added none

Description veera 2012-08-03 07:07:37 UTC 
Created attachment 672 [details]
Kernel panic screen shot is added

build              :http://autobuilder.yoctoproject.org/pub/nightly/20120801-1/machines/qemu/qemux86/
Target platform    : qemux86
Image Profile   : sato-sdk
Procedure      : 
1.down load http://autobuilder.yoctoproject.org/pub/nightly/20120801-1/machines/qemu/qemux86/bzImage-qemux86.bin core-image-sato-sdk-qemux86-20120801001946.rootfs.ext3
2.source environment-setup-i586-poky-linux
3.runqemu  qemux86 bzImage-qemux86.bin core-image-sato-sdk-qemux86-20120801001946.rootfs.ext3

Expected Output : qemux86 sato sdk System should come up with out error 
Observation     : kernel panic.
Comment 1 Saul Wold 2012-08-13 15:01:07 UTC 
Can you re-test this and check your downloads, I was able to load this file and boot with no issues:

Here are the md5sum of the 2 files:

d2ef73aa289fd8949d2274079cdf96ea  tmp/deploy/images/core-image-sato-sdk-qemux86-20120801001946.rootfs.ext3
3124ec8578745357f1be38987911f26e  tmp/deploy/images/bzImage-qemux86.bin
Comment 2 Saul Wold 2012-08-14 07:45:35 UTC 
See previous comment
Comment 3 veera 2012-08-14 08:59:53 UTC 
Hi Saul Wold ,

      Tested with http://autobuilder.yoctoproject.org/pub/nightly/20120801-1/machines/qemu/qemux86/bzImage-qemux86.bin core-image-sato-sdk-qemux86-20120801001946.rootfs.ext3  images , but i am not able to reproduce again.

Thanks 
veera
Comment 4 Saul Wold 2012-08-14 11:02:55 UTC 
The reporter commented that it is working correctly, by guess is that there was a possible corrupt image, if the problme appears again, we can reopen this bug.
Comment 5 Laurentiu Serban 2012-09-20 21:22:21 UTC 
setting this to verified