Charles Duffy wrote:
$ virsh restore ramsave error: Failed to restore domain from ramsave error: Unable to read QEMU help output: Interrupted system call
This happens immediately (no delay) and only on restore; "virsh start" behaves as usual.
To be explicit (as I wasn't earlier) -- this is b167672c748bd7d16cd5f450096232266583b851 built on RHEL5 with a great many things disabled: $ ./configure \ --host=x86_64-redhat-linux-gnu \ --build=x86_64-redhat-linux-gnu \ --target=x86_64-redhat-linux \ --program-prefix= \ --prefix=/usr \ --exec-prefix=/usr \ --bindir=/usr/bin \ --sbindir=/usr/sbin \ --sysconfdir=/etc \ --datadir=/usr/share \ --includedir=/usr/include \ --libdir=/usr/lib64 \ --libexecdir=/usr/libexec \ --localstatedir=/var \ --sharedstatedir=/usr/com \ --mandir=/usr/share/man \ --infodir=/usr/share/info \ --without-xen \ --without-openvz \ --without-lxc \ --without-vbox \ --without-polkit \ --without-uml \ --without-one \ --without-phyp \ --without-esx \ --with-rhel5-api \ --without-storage-fs \ --without-storage-lvm \ --without-storage-iscsi \ --without-storage-disk \ --without-capng \ --without-netcf \ --with-qemu-user=root \ --with-qemu-group=root \ --with-init-script=redhat \ --with-remote-pid-file=/var/run/libvirtd.pid