Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Who is the customer behind the request?
Account name: 540054
Customer segment: 2
TAM/SRM customer yes/no
: Cynthia Baldwin, SRM
VHT score: 2
What is the nature and description of the request?
Ability to use virt-filesystems with remote systems when it is connected using virt-filesystems -c <remote URI> -d domainname. Even though we are able to connect with remote libvirt systems, virt-v2v looks for VM images in the local system instead of remote system to the filesystem details
Why does the customer need this? (List the business requirements here)
Customer is looking for this feature because he do not want copy the image files to local systems before executing virt-filesystems -c <remote URI>.
How would the customer like to achieve this? (List the functional requirements here)
virt-filesystems -c <remote URI> -d domname should fetch the information from the image file the the VM uses on the remote system.
For each functional requirement listed in question 4, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
The virt-filesystems will list information of remote VM filesystem details when connected using a remote URI. Currently it fails with the error message, "no such file or directory" as it is looking for the image file in the local system
Is there already an existing RFE upstream or in Red Hat bugzilla?
Not able to find one.
How quickly does this need resolved? (desired target release)
RHEL 6.3?
Does this request meet the RHEL Bug and Feature Inclusion Criteria
yes
List the affected packages
libguestfs
Would the customer be able to assist in testing this functionality if implemented?
yes
Comment 6Richard W.M. Jones
2011-10-17 15:40:30 UTC
Reassigning this to libguestfs.
Comment 10Richard W.M. Jones
2013-07-30 10:05:08 UTC
This bug had the wrong product (because of my mistake) so it didn't
appear on my scope.
This is fixed in RHEL 7.0. You can access remote systems using
the nbd protocol, ie:
virt-filesystems -a nbd://remote.example.com
For RHEL 6 it's not likely we will add this extra functionality
since it's significantly complicated.
Comment 12Richard W.M. Jones
2013-09-27 09:00:27 UTC
Closing - see comment 10. Remote functionality using NBD and some
other transports will be available in RHEL 7.
Who is the customer behind the request? Account name: 540054 Customer segment: 2 TAM/SRM customer yes/no : Cynthia Baldwin, SRM VHT score: 2 What is the nature and description of the request? Ability to use virt-filesystems with remote systems when it is connected using virt-filesystems -c <remote URI> -d domainname. Even though we are able to connect with remote libvirt systems, virt-v2v looks for VM images in the local system instead of remote system to the filesystem details Why does the customer need this? (List the business requirements here) Customer is looking for this feature because he do not want copy the image files to local systems before executing virt-filesystems -c <remote URI>. How would the customer like to achieve this? (List the functional requirements here) virt-filesystems -c <remote URI> -d domname should fetch the information from the image file the the VM uses on the remote system. For each functional requirement listed in question 4, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. The virt-filesystems will list information of remote VM filesystem details when connected using a remote URI. Currently it fails with the error message, "no such file or directory" as it is looking for the image file in the local system Is there already an existing RFE upstream or in Red Hat bugzilla? Not able to find one. How quickly does this need resolved? (desired target release) RHEL 6.3? Does this request meet the RHEL Bug and Feature Inclusion Criteria yes List the affected packages libguestfs Would the customer be able to assist in testing this functionality if implemented? yes