Bug 1596963
Summary: | virt-sysprep: error: libguestfs error: No such file or directory | ||
---|---|---|---|
Product: | [Community] Virtualization Tools | Reporter: | john |
Component: | libguestfs | Assignee: | Richard W.M. Jones <rjones> |
Status: | CLOSED CANTFIX | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | ptoscano, rbalakri |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-07-01 09:33:40 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
john
2018-06-30 23:58:43 UTC
Unfortunately libvirt doesn't provide a way for us to access disks remotely, so if you connect to a remote libvirt it still tries to load the disk as if it was a local file. This is basically a design problem with libvirt, try for example simply doing: virsh -c qemu+ssh://user@ipaddress/system dumpxml REMOTEVM and look at the disk paths returned. (It's actually a bit worse than that because there's no way for us to detect if the libvirt connection is local or remote, so eg. @localhost would work). I'm afraid if you want to sysprep a remote disk you're going to have to find a way to mount the filesystem with the disk locally (eg. share /var/lib/libvirt/images over NFS) or find another way to export the filesystem (eg. NBD) or just run virt-sysprep on the remote box instead. |