Apparantly, agent smith was connecting to xenstored instead of directly to the xen store socket. We don't run xenstored, so this failed.. Due to to piss poor error handling in our Xen interface, this just caused a segfault. This should be fixed now in trunk. Enjoy.
Apparantly, agent smith was connecting to xenstored instead of directly to the xen store socket. We don't run xenstored, so this failed.. Due to to piss poor error handling in our Xen interface, this just caused a segfault. This should be fixed now in trunk. Enjoy.