Users

Download

users@lists.libvirt.org

May 2016

39 participants
42 discussions

[libvirt-users] Ubuntu 14.04 virsh 1.2.2 blockcommit hangs at 100% / command 'blockcommit' doesn't support option --pivot
by Liam Curtis 03 May '16

03 May '16

Hello All, I think I have seen this in previous bugs. Trying to live backup qcow2 images. I am able to virsh snapshot-create-as and virsh domblklist shows correct new source, but I am unable to commit back changes to qcow base. I get the above error. Libvirt at 1.2.2-0ubuntu13.1.17 Qemu is (2.0.0+dfsg-2ubuntu1.22) I tried compiling latest libvirt, but cannot get it to connect to socket on installed binaries Anyone get this working on Ubuntu 14.04?

2 2

[libvirt-users] Making remote access to qemu://session easier?
by Lars Kellogg-Stedman 03 May '16

03 May '16

This is frustrating: $ export LIBVIRT_DEFAULT_URI=qemu+ssh://remotehost/session $ virsh list error: failed to connect to the hypervisor error: no valid connection error: Operation not supported: Connecting to session instance without socket path is not supported by the ssh connection driver Has there been any thought given to making this easier? It seems that having a simple helper script on the remote host that could make the same "use $XDG_RUNTIME_DIR or use $HOME/.confg" decision as libvirtd would be able determine the socket path automatically. Would that be a reasonable solution? I see that right now, even support for qemu://remotehost/system requires that "virsh" knows that path to the remote socket, so having a remote helper that can read the libvirt configuration might simplify things in general. That is, I am envisioning that for .../session connections, virsh would do something like: ssh remotehost libvirt-socket-helper --user And for .../system connections, virsh would do something like: ssh remotehost libvirt-socket-helper --system Rather than: ssh remotehost sh -c 'if nc -q 2>&1 | grep \"requires an argument\" >/dev/null 2>&1; then ARG=-q0;else ARG=;fi;nc $ARG -U /var/run/libvirt/libvirt-sock' And in either of the above cases, "libvirt-socket-helper" would parse the environment and the libvirtd configuration as necessary and ultimately act like "nc -U /path/to/some/socket". -- Lars Kellogg-Stedman <lars(a)redhat.com> | larsks @ {freenode,twitter,github} Cloud Engineering / OpenStack | http://blog.oddbit.com/

3 3