Il 01/05/2012 22:56, Eric Blake ha scritto: > What sort > of timing restrictions are there? For example, the proposed > 'drive-reopen' command (probably now delegated to qemu 1.2) would mean > that qemu would be calling back into libvirt in order to do the reopen. > If libvirt takes its time in passing back an open fd, is it going to > starve qemu from answering unrelated monitor commands in the meantime? > I definitely want to make sure we avoid deadlock where libvirt is > waiting on a monitor command, but the monitor command is waiting on > libvirt to pass an fd. FWIW I'm going to kill drive-reopen in favor of something like block-job-complete that will not require reopening (it will require opening the backing files though, and that can also take time). Paolo -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list