[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-discuss] How to get console output after spawning new process

From: Maciej Bielski
Subject: Re: [Qemu-discuss] How to get console output after spawning new process
Date: Fri, 24 Jul 2015 17:54:01 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0

Ok, I have found a solution. The process spawned was using SIGUSR1 to
signal something to the parent process (device internals). It seems that
QEMU uses SIGUSR1 internally because when I have switched to SIGUSR2 it
works as expected.


On 07/23/2015 01:20 PM, Maciej Bielski wrote:
> I am using 'qemu-system-arm' as a Zedboard emulator (Xilinx's branch). I
> have extended it with a new device, which is described in device-tree
> and a .c file, compiled, detected and initialized when QEMU starts. But
> I need a way to talk to that device from outside of QEMU via socket.
> So, during device initialization I am spawning another process that runs
> server waiting on a socket. Then I can run a program on my host machine
> and send some data via the socket. This is working, but because of that
> process I can no longer see the output of QEMU's console (so I cannot
> log in for example).
> 1. How to set the current terminal as an output console again?
> 2. Maybe there already exists a solution to talk to QEMU internals via
> socket (-chardev option)?
> Thanks for any help or hints.
> Maciek

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]