Quoting Jiri Denemark (2018-07-13 10:14:22)
> On Mon, Jul 09, 2018 at 22:56:53 -0500, Chris Venteicher wrote:
> > Commit makes starting a single persistent QEMU instance possible for use
> > over multiple independent QMP commands without starting and stopping
> > QEMU for each QMP command or comman
On Mon, Jul 09, 2018 at 22:56:53 -0500, Chris Venteicher wrote:
> Commit makes starting a single persistent QEMU instance possible for use
> over multiple independent QMP commands without starting and stopping
> QEMU for each QMP command or command type.
>
> Commit allows functions outside qemu_ca
Quoting Collin Walling (2018-07-11 17:48:54)
> I understand your approach, but I do not 100% agree with exposing the QEMU
> command stuff outside of qemu_capabilities.
>
> In patch 10/11, you have a function defined in qemu_caps for baselining. I'd
> spawn / kill your QEMU process within there. F
I understand your approach, but I do not 100% agree with exposing the QEMU
command stuff outside of qemu_capabilities.
In patch 10/11, you have a function defined in qemu_caps for baselining. I'd
spawn / kill your QEMU process within there. For when the features flag is set
(requiring you to cal
Commit makes starting a single persistent QEMU instance possible for use
over multiple independent QMP commands without starting and stopping
QEMU for each QMP command or command type.
Commit allows functions outside qemu_capabilities
(ex. qemuConnectBaselineHypervisorCPU in qemu_driver)
requirin
