summaryrefslogtreecommitdiffstats
path: root/scripts/runqemu-gen-tapdevs
diff options
context:
space:
mode:
authorJason Wessel <jason.wessel@windriver.com>2020-06-25 10:17:10 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2020-06-28 08:36:00 +0100
commit157e44bdbaa3d5c87fc2a1dcf65d7745216b76f4 (patch)
tree62c56e1edf879530f7bbcb262e9d4462ff394b75 /scripts/runqemu-gen-tapdevs
parent34db68c8353f74edc61565a0c63aab788635cf55 (diff)
downloadpoky-157e44bdbaa3d5c87fc2a1dcf65d7745216b76f4.tar.gz
runqemu: If using a vmtype image do not add the -no-reboot flag
There is no way to use runqemu and turn off the no-reboot flag with a command line argument. If someone really wants it back it can be added with the qemuparams="" argument. Also if you use the "halt -p" from user space, the qemu will exit when it is complete. It is impossible to test self deploying image with runqemu if you cannot reboot the device. One might argue that you can run runqemu in a loop, but that defeats the purpose of having a wrapper around a tool that already does what is needed in the first place. For the vmtype images, the -no-reboot flag should not be added. (From OE-Core rev: 6d07a72356f9a8ea76b6cda9159d3ca4743028d9) Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/runqemu-gen-tapdevs')
0 files changed, 0 insertions, 0 deletions