We currently have a set of domain lifecycle events
VIR_DOMAIN_EVENT_ADDED = 0,
VIR_DOMAIN_EVENT_REMOVED = 1,
VIR_DOMAIN_EVENT_STARTED = 2,
VIR_DOMAIN_EVENT_SUSPENDED = 3,
VIR_DOMAIN_EVENT_RESUMED = 4,
VIR_DOMAIN_EVENT_STOPPED = 5,
VIR_DOMAIN_EVENT_SAVED =
of filtering mechanism?
-Original Message-
From: [EMAIL PROTECTED] on behalf of Daniel P. Berrange
Sent: Fri 11/14/2008 6:18 AM
To: libvir-list@redhat.com
Subject: [libvirt] RFC: Add a 'reason' argument for domain events ?
We currently have a set of domain lifecycle events
On Fri, Nov 14, 2008 at 11:18:48AM +, Daniel P. Berrange wrote:
[...]
One option is to add alot more events
VIR_DOMAIN_MIGRATED_IN (migrated to another node)
VIR_DOMAIN_MIGRATED_OUT (migrated from another node)
VIR_DOMAIN_SHUTDOWN (graceful shutdown by host admin)
On Fri, Nov 14, 2008 at 07:28:09AM -0500, Ben Guthro wrote:
To revisit the DEFINED, UNDEFINED topic - I have been giving this some
thought,
and it seems like it is redundant information to me.
Doesn't the existence of a config file define the difference between a
transient
and a
