Marek Marczykowski 03d813bbcd remote: fix dom->id after virDomainCreateWithFlags ... The same issue as (already fixed) in virDomainCreate - REMOTE_PROC_DOMAIN_CREATE_WITH_FLAGS doesn't return new domain ID, only -1 on error or 0 on success. Besides this one fix it is more general problem - local domain object ID can desynchronize with the real one, for example in case of another client creates/destroys domain in the meantime. Perhaps virDomainGetID should be called remotely (with all performance implications...)? Or some event-based notification used? Signed-off-by: Marek Marczykowski <marmarek@invisiblethingslab.com>		2013-05-23 15:07:16 +02:00
..
lxc_protocol.x	Switch to a more extensible annotation system for RPC protocols	2013-04-23 11:24:17 +01:00
qemu_protocol.x	Make naming of remote procedures match API names exactly	2013-04-24 10:33:10 +01:00
remote_driver.c	remote: fix dom->id after virDomainCreateWithFlags	2013-05-23 15:07:16 +02:00
remote_driver.h	cleanup: Don't include libvirt/virterror.h	2013-04-17 15:54:07 +08:00
remote_protocol.x	remote: fix dom->id after virDomainCreateWithFlags	2013-05-23 15:07:16 +02:00