Connect to running qemu instance with qemu monitor
My preferred way to do this is to connect to the QEMU "monitor" via a UNIX socket. It works well, although the method is very poorly documented.
When you start QEMU, add the
-monitor parameter as follows:
$ qemu-system-i386 [..other params..] -monitor unix:qemu-monitor-socket,server,nowait
qemu-monitor-socket here is not a keyword, but a host path and filename of your choice to represent the socket on disk. You'll see this file created when QEMU starts.
server,nowait tell QEMU to listen for connections, but start the VM without waiting for a connection.
You can use the socat utility (available from all good repositories) to connect to the socket to type commands to the QEMU monitor prompt:
$ socat -,echo=0,icanon=0 unix-connect:qemu-monitor-socket QEMU 2.8.1 monitor - type 'help' for more information (qemu) _
What socat does is connect two arbitrary streams/sockets together. The first parameter
- is a synonym for
stdio, i.e., the console keyboard and output. The couple of options
echo=0,icanon=0 make keyboard interaction nicer here by preventing re-echoing of entered commands and enabling Tab completion and arrow keys for history. The final parameter says to connect to the socket file created earlier.
To send a one-shot command to QEMU, echo it thru socat to the UNIX socket:
$ echo "info status" | socat - unix-connect:qemu-monitor-socket QEMU 2.8.1 monitor - type 'help' for more information (qemu) info status VM status: running (qemu) $ _
For cleaner output in a script, I also add
| tail --lines=+2 | grep -v '^(qemu)' to filter out the first line and the
(qemu) prompt lines:
$ echo "info status" | socat - unix-connect:qemu-monitor-socket | tail --lines=+2 | grep -v '^(qemu)' VM status: running $ _
To shut down the VM as you wanted, useful monitor commands are
system_powerdown, which presses the on/off button of the imaginary machine so it can gracefully shut down, or
quit, which quits QEMU immediately.
A couple of notes:
QEMU also permits
-qmpin place of
-monitor, providing a JSON-based interface; that might be more robust for programmatic control, but I never tried it.
A socket file on disk is always empty. It doesn't store data; it's just an arbitrary handle for programs to open communications.
Someone might be able to chime in with a proper command for operating on TTYs, but I'll post a solution in the meantime involving the network.
There are a couple options for redirecting the QEMU monitor. One way is to have QEMU offer access to its monitor via telnet:
$ qemu-system-i386 -monitor telnet:127.0.0.1:55555,server,nowait;
Then, QEMU can be scripted by piping commands to
telnet. This is fine as long as the output of commands can be discarded since the telnet session will probably close too quickly for visual feedback:
$ echo system_powerdown |telnet 127.0.0.1 55555 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. Connection closed by foreign host. $ _ # qemu sends the guest an ACPI shutdown signal
If the output of the commands executed on the monitor need to be collected, a TCP session can be used instead:
$ qemu-system-i386 -monitor tcp:127.0.0.1:55555,server,nowait;
Then, commands can be sent to the listening monitor via
netcat or a similar utility:
$ echo info\ kvm |nc -N 127.0.0.1 55555 QEMU 2.11.0 monitor - type 'help' for more information (qemu) info kvm kvm support: enabled (qemu) $ echo system_powerdown |nc -N 127.0.0.1 55555 QEMU 2.11.0 monitor - type 'help' for more information (qemu) system_powerdown (qemu) $ # hit return $ _ # qemu sends the guest an ACPI shutdown signal
Here is a link to partial documentation of QEMU monitor commands: https://en.wikibooks.org/wiki/QEMU/Monitor