Bug 7082

Summary: Support qemumips64 in runqemu
Product: [Runtime] General Runtime Reporter: Yi Zhao <yi.zhao>
Component: General RuntimeAssignee: Cristian Iorga <cristian.iorga>
Status: VERIFIED FIXED QA Contact: Lucian Musat <georgex.l.musat>
Severity: enhancement    
Priority: Medium+ CC: alexandru.c.georgescu, bluelightning, ke.zou, tom.zanussi, zhangle.yang
Version: 1.8   
Target Milestone: 1.8 M2   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: New (Never tested)
Verified: Documentation change: Don't know

Description Yi Zhao 2014-12-15 09:04:45 UTC 
When I verified bug 5314, I found the runqemu can not launch the qemumips64 image directly: 

$ runqemu qemumips64 ~/vmlinux-myqemumips64.bin ~/core-image-sato-myqemumips64-20141210092048.rootfs.ext3 

Continuing with the following parameters:
KERNEL: [/home/build/vmlinux-myqemumips64.bin]
ROOTFS: [/home/build/core-image-sato-myqemumips64-20141210092048.rootfs.ext3]
FSTYPE: [ext3]
Acquiring lockfile for tap1...
Setting up tap interface under sudo
Acquiring lockfile for tap0...
Error: No QEMU binary 'qemu-system-mips64' could be found.
Set 'tap0' nonpersistent
Releasing lockfile of preconfigured tap device 'tap0'

I need to install qemu-system package in order to get command qemu-system-mips64 in Ubuntu host.
Comment 1 Saul Wold 2014-12-15 18:22:20 UTC 
This may require some modifications to the Qemu recipe as well as the runqemu 
scripts
Comment 2 Cristian Iorga 2015-01-14 14:40:39 UTC 
Investigation started.
Comment 3 Cristian Iorga 2015-01-14 15:08:34 UTC 
Patch sent for review.
Comment 5 Lucian Musat 2015-01-22 15:57:35 UTC 
Verified on 1.8 M2 RC1 (d9d5b8b499af3ae01a1e33d0d3969c54c2d4ab1b)