diff options
| author |   Jason Wessel <jason.wessel@windriver.com> | 2020-06-25 10:17:10 -0700 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2020-06-28 08:24:20 +0100 |
| commit | 6d07a72356f9a8ea76b6cda9159d3ca4743028d9 (patch) | |
| tree | 16559ab5b459edeee4971de84fbe2a466ce3f0df /scripts | |
| parent | e46f424748d9cc6d6160079e1a36fe43505ba2fa (diff) | |
| download | openembedded-core-contrib-6d07a72356f9a8ea76b6cda9159d3ca4743028d9.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.
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts')
| -rwxr-xr-x | scripts/runqemu | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/scripts/runqemu b/scripts/runqemu index 85f323a712..f2168c18a3 100755 --- a/scripts/runqemu +++ b/scripts/runqemu @@ -1241,7 +1241,9 @@ class BaseConfig(object): vm_drive = '-drive if=virtio,file=%s,format=%s' % (self.rootfs, rootfs_format) # All branches above set vm_drive. - self.rootfs_options = '%s -no-reboot' % vm_drive + self.rootfs_options = vm_drive + if not self.fstype in self.vmtypes: + self.rootfs_options += ' -no-reboot' self.kernel_cmdline = 'root=%s rw' % (self.get('QB_KERNEL_ROOT')) if self.fstype == 'nfs': |