[libvirt] xen driver & events

Ben Guthro bguthro at virtualiron.com
Tue Oct 28 18:00:48 UTC 2008

I'm looking into implementing emitting events from the xen driver, and I've run into a bit of a snag that I would like to discuss

I've attached an old version of my patch for reference.

However - from past discussions, I know that there was a desire to keep the xen driver stateless. However, given the semantics of xenstore watches, and events, I'm not sure I can see a way to preserve this.

Lets take the case of creating a new domain:
XenStore gives us the functionaliity to put a watch on the special xenstore key @introduceDomain.
However, when the watch fires - I see no mechanism of determining which domain has been introduced. 

The only mechanism I can find is to maintain a list of domains, and keep this up to date with events.

So I'm wondering if anyone has any ideas, or if this will introduce unwanted, but necessary state into the driver?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: events-xen.patch
Type: text/x-patch
Size: 9900 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20081028/eb6e5cf9/attachment-0001.bin>

More information about the libvir-list mailing list