Skip to main content

[RTEMS] Alternative way to run QEMU on cluster like executing in background

My case is to get some stdio output from console with QEMU. Unfortunately, it is not possible to run QEMU with & command.
An alternative way is that using screen to keep ssh session running when you disconnect.
Assume I have a PC with linux shell to connect to cluster:
screen ssh yourname@clusterpc

I use the following option to set up my qemu vm and output to a file called result.txt: 
qemu-system-arm -no-reboot -nographic -M realview-pbx-a9 -m 256M -kernel \
kernel file >> result.txt
After this command, the vm is started.
Press Ctrl + A and then Ctrl + D in immediate succession.
And now it is disconnected.
To reconnect to the session
screen -r

If you have multiple sessions like my case, you need to specify the session you are going to resume:
There are several suitable screens on:
        3390.pts-13.ls12sq      (Detached)
        3646.pts-13.ls12sq      (Detached)
Type "screen [-d] -r [pid.]tty.host" to resume one of them.
In my case, I can type the following command to resume 3390.
screen -r 3390 

To kill session, Ctrl + A and than Ctrl + K, or exit the terminal.
Reference from:
http://www.howtogeek.com/howto/ubuntu/keep-your-ssh-session-running-when-you-disconnect/

------------------
The following is the Q&A for different potential errors:
  1. error opening terminal: xterm-256color
    • export TERM=xterm
  2. No command for screen
    • sudo apt-get install screen

Comments

Post a Comment

Popular posts from this blog

RSB+RTEMS 5/6 with QEMU-SMP (ARM realview_pbx_a9_qemu as example)

Since I got a request regarding this blog  written in 2016, summarizing again the complete flow with the latest version of RTEMS could be a good idea. Prepare a suitable workspace according to the adopted operating system on your host ( https://docs.rtems.org/branches/master/user/hosts/index.html ):  sudo apt-get build-dep build-essential gcc-defaults g++ gdb git unzip pax bison flex texinfo unzip python3-dev libpython-dev libncurses5-dev zlib1g-dev Checkout RSB and build: git clone git://git.rtems.org/rtems-source-builder.git rsb change directory to rsb/rtems/ and type ../source-builder/sb-set-builder --prefix=<the path you like to store the built toolchains> <the name of bsp> For example, to use QEMU, I need toolchains for ARM, so: ../source-builder/sb-set-builder --prefix=/home/kh.chen/respository/build/. 6/rtems-arm This will take a while. Please ensure your connection is reliable. Add the built folder into your PATH. For example, you can add one line in ~/.bas...
Post a Comment
Read more

[LEGO nxt] Install the Enhanced NXT firmware and Upload the OSEK excutable file with Ubuntu 64bits 14.04 in 2015

This tutorial is referred from Install the Enhanced NXT firmware on NXT . I think this is the critical part to capture the idea from the tutorial for Windows. I have tried many ways to conquer the problem of libnxt3.0, however, I still have some problems on the compilation of fwflash or something else. Though the tutorial for Windows is doable, my preference is to build up everything with Linux environment. Fortunately, I notice that NxTTool in the tutorial for Windows is really powerful. We can handle the firmware updating by using NxTTool in Linux as well! I also refer to this Japanese Blog , which inspire me a lot. As usual, install the required packages: sudo apt-get install libusb-dev:i386 libusb-0.1-4 subversion fpc Please note, here is the case for 64bits user that I change libusb-dev to libusb-dev:i386 comparing to the original tutorial. Instead of using libnxt to do the uploading, here I follow that JP Blog to get the latest version of bricxcc: (The url in blog i...
Post a Comment
Read more

Virtualenv experience or alternatives

Today I have a project which requires several packages on my python. However, due to whatever reason, I have a lot of different versions of python. Before I thought, it was fine to just install and maintain each by each. Maybe it is time to learn how to use virtualenv. (alternatively, you can use module). I first got some quick ideas from here: https://stackoverflow.com/questions/10763440/how-to-install-python3-version-of-package-via-pip-on-ubuntu The magic virtualenv does is that, it copies a series of your python binaries, include, pip, etc., into a folder. The prepared activate script does that, add the export folder into the general variable PATH at its beginning. By doing so, the targeted version of python will be the first target that will be executed. To enable virtualenv, source the position of the above folder/bin/activate To leave the virtualenv, just type deactivate, as it is defined when you load the activate script. For example, I call virtualenv in my home ...
Post a Comment
Read more