Bug #474107 does not fix it for me since libvirt itself (virsh) is using -q anyway on new releases:
LIBVIRT_DEBUG=1 virsh -c qemu+ssh://r...@xxxx/system It seems that "nc -q" code is present on libvirt itself too: 13:55:49.688: debug : doRemoteOpen:564 : proceeding with name = qemu:///system 13:55:49.688: debug : virExecWithHook:640 : ssh -l root xxxx nc -q 0 -U /var/run/libvirt/libvirt-sock 13:55:49.701: debug : remoteIO:8431 : Do proc=66 serial=0 length=28 wait=(nil) 13:55:49.702: debug : remoteIO:8493 : We have the buck 66 0xb76f8008 0xb76f8008 13:55:50.049: debug : remoteIOEventLoop:8378 : Giving up the buck due to I/O error 66 0xb76f8008 (nil) 13:55:50.049: debug : do_open:1126 : driver 4 remote returned ERROR Putting a nc binary that supports "-q" flag under /usr/local/bin fixes it for me, see (as zigi wrote): http://bugs.centos.org/view.php?id=4188 -- remotely executed netcat (nc) uses -q option which is not universally supported https://bugs.launchpad.net/bugs/517478 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
