Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

When trying to use guestfish with a remote filesystem image over ssh, I get an error:

$ echo -e "run\nlist-filesystems"| LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1 guestfish --ro -a ssh://localhost/home/alex/temp/filesystem
libguestfs: trace: set_verbose true
...
libguestfs: command: run: \ ./ssh://localhost/home/alex/temp/filesystem
qemu-img: Could not open './ssh://localhost/home/alex/temp/filesystem': Could not open './ssh://localhost/home/alex/temp/filesystem': No such file or directory
libguestfs: error: qemu-img info: ssh://localhost/home/alex/temp/filesystem: qemu-img info exited with error status 1, see debug messages above
...

If I run it instead on a local filesytem, I get the following:

$ echo -e "run\nlist-filesystems"| guestfish --ro -a filesystem
/dev/sda: ext4

(filesystem was created with:
truncate -s 10M filesystem
/usr/sbin/mke2fs -t ext4 -Elazy_itable_init=0,lazy_journal_init=0 filesystem)

The manpage documents ssh support (under ADDING REMOTE STORAGE).

Why does ssh support not work?

Thanks,
Alex King

P.S. this machine still has some packages from bullseye, but the packages in
question are from bookworm.  I have the same problem on a pure-bookworm
system.

*** End of the template - remove these template lines ***