[OE-core] [PATCH 1/1] qemurunner: print out the runqemu command

[Brian Avery]

true, you do, kind of.

This commit explicitly prints out what the runqemu cmd is (for instance
"runqemu snapshot -m 1024"), which is a lot easier to enter if you want to
rerun qemu the way the test did.

It's not a big deal, I just ended up adding it while i was trying to figure
out how the tests were getting started and where my params were ending up.
Your's prints out the long complete cmd line, mine prints out the shortcut
:).  The long one is definitely necessary. Mine is a convenience.

-b
an intel employee.

On Mon, Sep 12, 2016 at 1:19 AM, Joshua Lock <joshua.g.lock at linux.intel.com>
wrote:

> On Fri, 2016-09-09 at 09:38 -0700, bavery wrote:
> > This logs the launch command that was used for runqemu while running
> > -c
> > testimage.  This way, if I'd like to easily launch qemu manually in
> > order to debug a failed test, I know what commmand was run to create
> > the qemu instance.
>
> I already have this in my runqemu output:
>
> runqemu - INFO - Running
> /home/joshuagl/Projects/poky/build/tmp/sysroots/x86_64-
> linux/usr/bin/qemu-system-ppc -net
> tap,vlan=0,ifname=tap0,script=no,downscript=no -net nic,model=pcnet  -
> machine mac99 -cpu G4 -m 256 -drive file=/home/joshuagl/mess/35/core-
> image-lsb-qemuppc-20160902090100.rootfs.ext4,if=virtio,format=raw  -
> show-cursor -usb -usbdevice tablet -device virtio-rng-pci -kernel
> /home/joshuagl/mess/35/vmlinux-qemuppc.bin -append 'root=/dev/vda rw
> highres=off  mem=256M ip=192.168.7.2::192.168.7.1:255.255.255.0
> console=ttyS0 console=tty'
>
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20160912/830e6a97/attachment-0002.html>