search for: libxl_device_model_version

...ut; + } + if (pthread_mutex_init(lock, &attr) != 0) { + LIBXL__LOG_ERRNO(ctx, LIBXL__LOG_ERROR, + "Failed to init mutex\n"); + rc = ERROR_FAIL; + goto out; + } +out: + pthread_mutexattr_destroy(&attr); + return rc; +} + libxl_device_model_version libxl__device_model_version_running(libxl__gc *gc, uint32_t domid) { diff -r f581bb82fecd -r 259112aee618 tools/libxl/libxl_internal.h --- a/tools/libxl/libxl_internal.h Sat Jan 14 19:04:48 2012 +0100 +++ b/tools/libxl/libxl_internal....

...leave the path as the default in the normal case. You may also want to provide an extra emulator-path-override tag/attribute/XML for advanced users, but that''s up to you. If you need to support upgrade from xend then you could perhaps treat <emulator> values not in the set of valid LIBXL_DEVICE_MODEL_VERSION string (currently "qemu-xen" and "qemu-xen-traditional") as a path to a qemu-xen-traditional device model -- no xend user can possibly have been using the new device model with xend. Or you could take the approach that xl does and just warn. Ian.