| Info | ||
|---|---|---|
| ||
Copyright 2016 by Assured Information Security, Inc. Created by Ross Philipson <philipsonr@ainfosec.com>. This work is licensed under the Creative Commons Attribution 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by/4.0/. |
QMP
The basics on QMP can be found here:
...
- A chardrv implementation that is introduced into the
qemu-char.ccode. This new type of chardrv can sit below other monitors and consoles and route traffic over V4V. - A proxy process called
qmp_helperruns indom0and can talk to the V4V chardrv in QEMU in the stubdom. Theqmp_helperalso creates a UNIX socket exactly as QEMU would have above indom0. The toolstack (xl) can then connect directly to the UNIX socket and the rest is invisible to it.
The qmp_helper must be started with the stub-domain ID where the QEMU it wants to talk to lives. There is an instance of qmp_helper per stub-domain. The QEMU instance in the stub-domain must be started with this version of the QMP parameter:
-qmp v4vThe QMP helper also needs changes to SELinux and the V4V firewall before it will work properly. If those changes are not yet implemented, QMP helper can still be tested by putting SELinux in permissive mode and flushing all the V4V firewall rules:
...