Bug 1322512 - Libguestfs error: filesize: /var/lib/rpm/Name: No such file or directory
Summary: Libguestfs error: filesize: /var/lib/rpm/Name: No such file or directory
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libguestfs
Version: 7.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Richard W.M. Jones
QA Contact: Virtualization Bugs
URL:
Whiteboard: v2v
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-30 15:40 UTC by Josh
Modified: 2020-02-14 17:43 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-16 13:50:23 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Josh 2016-03-30 15:40:31 UTC
Description of problem: When trying to convert a .OVA file with multi-boot operating systems to the qcow2 format so I can use it with KVM (Kernel-based Virtual Machine) I receive the following error message:

virt-v2v: error: libguestfs error: filesize: /var/lib/rpm/Name: No such file or directory

If reporting bugs, run virt-v2v with debugging enabled and included the complete output:

virt-v2v -v -x [...]

Version-Release number of selected component (if applicable):

libguestfs-tools-c-1.28.1-1.55.el7.x86_64
libguestfs-1.28.1-1.55.el7.x86_64
libguestfs-xfs-1.28.1-1.55.el7.x86_64
libguestfs-winsupport-7.2-1.el7.x86_64
virt-v2v-1.28.1-1.55.el7.x86_64

How reproducible: 100%

Steps to Reproduce:
1. Run this command below:  
virt-v2v -i ova $OVA_FILE_LOCATION -o local -of qcow2 -os /var/tmp
Note: Make sure you use an OVA file with two vmdk files in it.
2. When prompted to choose the root filesystem that contains the main operating system from the list below choose 1 or 2.  Both give the same error.
3. Finally the error appears.

Actual results:
virt-v2v: error: libguestfs error: filesize: /var/lib/rpm/Name: No such file or directory

If reporting bugs, run virt-v2v with debugging enabled and included the complete output:

virt-v2v -v -x [...]

Expected results:
I expected it to complete successfully with the OVA file having been converted to qcow2 format.

Additional Information:  The /var/lib/rpm/Name does exists on my system and does appear to be accessible to a regular user.  Not sure why it still says no such file or directory exits when it is clearly there.

Comment 2 Pino Toscano 2016-03-30 16:04:21 UTC
(In reply to Josh from comment #0)
> Additional Information:  The /var/lib/rpm/Name does exists on my system and
> does appear to be accessible to a regular user.  Not sure why it still says
> no such file or directory exits when it is clearly there.

This path is within the guest.  The inspection has found that the guest is RPM-based, and thus it is trying to detect which applications are installed (virt-v2v needs to know what are the installed kernels, for example).

> Description of problem: When trying to convert a .OVA file with multi-boot
> operating systems to the qcow2 format so I can use it with KVM (Kernel-based
> Virtual Machine) I receive the following error message:
> 
> virt-v2v: error: libguestfs error: filesize: /var/lib/rpm/Name: No such file
> or directory
> 
> If reporting bugs, run virt-v2v with debugging enabled and included the
> complete output:
> 
> virt-v2v -v -x [...]

Can you please provide a full log of v2v, with the two parameters mentioned above?  Note that it might contain private data, so please check it before attaching it.

Also, would it be possible for you to provide the .OVA?

Comment 3 Richard W.M. Jones 2016-03-30 16:04:53 UTC
Please run the virt-v2v command with -v -x options and attach
the *full* output to this bugzilla.

Comment 8 Richard W.M. Jones 2017-02-16 13:50:23 UTC
Closing with insufficient data again.

If you retest this then please:

(1) Use the latest version of virt-v2v.

(2) Capture the full virt-v2v -v -x output.

(3) Capture /etc/fstab from the guest.


Note You need to log in before you can comment on or make changes to this bug.