On Tue, Nov 29, 2011 at 03:36:04PM -0600, Adam Litke wrote:
> Hopefully monitorCommand will not be too bad, since vdsm should be asking
> libvirt for the VM details when they are needed.  Of course we'll need to be
> testing to make sure we aren't keeping state around.  Also, I would expect
> monitorCommand to 'taint' the VM in the eyes of the vdsm API (as it does for
> libvirt).

That's besides the main point of this thread, but I should probably mention that
monitorCommand was never a public API. Its sole purpose was testing and
debugging. RHEV-M never used it, and it was obsoleted in vdsm-4.9 (RHEV-3.0) in
favor of `virsh qemu-monitor-command`.
vdsm-devel mailing list

Reply via email to