+++ This bug was initially created as a clone of Bug #1139659 +++ Description of problem: Note this requires that you have fixed bug 1134592 in libvirt first. If you create a backing file that references an ssh server, libvirt doesn't pass the required SSH_* variables through to qemu so it cannot access the ssh agent. $ qemu-img create -f qcow2 \ -b 'json: { "file.driver":"ssh", "file.path":"/mnt/scratch/test1.img", "file.user":"rjones", "file.host":"onuma.home.annexia.org", "file.host_key_check":"no" }' test2.img $ ~/d/libvirt/run guestfish -a test2.img run [...] Original error from libvirt: internal error: early end of file from monitor: possible problem: 2014-09-09T11:36:32.304954Z qemu-system-x86_64: -drive file=/tmp/test2.img,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=writeback: could not open disk image /tmp/test2.img: Could not open backing file: failed to connect to ssh-agent: no auth sock variable (libssh2 error code: -39) [code=1 domain=10] Version-Release number of selected component (if applicable): libvirt from git (2014-09-09) + patches to fix bug 1134592. How reproducible: 100% Steps to Reproduce: 1. See above. Related: bug 856619 --- Additional comment from Richard W.M. Jones on 2014-09-10 08:02:00 EDT --- Dan suggests that I make this bug into a more general feature request.
*** Bug 1139659 has been marked as a duplicate of this bug. ***
*** Bug 1434841 has been marked as a duplicate of this bug. ***
*** Bug 1434651 has been marked as a duplicate of this bug. ***
These proposed commits would mean we no longer need this in libvirt: https://www.redhat.com/archives/libguestfs/2019-April/msg00058.html https://www.redhat.com/archives/libguestfs/2019-April/msg00060.html
This bug is going to be addressed in next major release.
This no longer affects virt-v2v upstream, still affects RHEL AV 8.2, but we will rebase in AV 8.3 at which point it won't affect downstream. Still be a nice to fix for other users of course.
This bug was closed deferred as a result of bug triage. Please reopen if you disagree and provide justification why this bug should get enough priority. Most important would be information about impact on customer or layered product. Please indicate requested target release.