Cole Robinson wrote:
Daniel P. Berrange wrote:
On Mon, Feb 16, 2009 at 06:42:11PM -0500, Cole Robinson wrote:
For some reason there are two VMDef members being used to keep track of
monitor event handles: monitor_watch and monitorWatch. Remove the latter.
Can you remove the 'monitor_watch'
On Fri, Feb 27, 2009 at 10:38:45AM -0500, Cole Robinson wrote:
Daniel P. Berrange wrote:
On Mon, Feb 16, 2009 at 06:42:11PM -0500, Cole Robinson wrote:
For some reason there are two VMDef members being used to keep track of
monitor event handles: monitor_watch and monitorWatch. Remove the
Cole Robinson wrote:
Daniel P. Berrange wrote:
On Mon, Feb 16, 2009 at 06:42:11PM -0500, Cole Robinson wrote:
For some reason there are two VMDef members being used to keep track of
monitor event handles: monitor_watch and monitorWatch. Remove the latter.
Can you remove the 'monitor_watch'
Daniel P. Berrange wrote:
On Mon, Feb 16, 2009 at 06:42:11PM -0500, Cole Robinson wrote:
For some reason there are two VMDef members being used to keep track of
monitor event handles: monitor_watch and monitorWatch. Remove the latter.
Can you remove the 'monitor_watch' instead - all the
On Mon, Feb 16, 2009 at 06:42:11PM -0500, Cole Robinson wrote:
For some reason there are two VMDef members being used to keep track of
monitor event handles: monitor_watch and monitorWatch. Remove the latter.
Can you remove the 'monitor_watch' instead - all the other variables
in the
