Bug 1402301
| Summary: | Improve OVA import compatibility | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | tingting zheng <tzheng> | |
| Component: | libguestfs | Assignee: | Richard W.M. Jones <rjones> | |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | |
| Severity: | medium | Docs Contact: | Yehuda Zimmerman <yzimmerm> | |
| Priority: | high | |||
| Version: | 7.4 | CC: | ahadas, akostadi, bugs, fabrice.bacchella, jsuchane, juzhou, michal.skrivanek, mkalinin, mtessun, mxie, mzhan, nsimsolo, pasik, ptoscano, rjones, shavivi, snagar, tgolembi, tzheng, xiaodwan, yzimmerm | |
| Target Milestone: | rc | Keywords: | ZStream | |
| Target Release: | 7.4 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | V2V | |||
| Fixed In Version: | libguestfs-1.36.1-1.el7 | Doc Type: | Bug Fix | |
| Doc Text: |
*virt-v2v* imports OVAs that do not have the "<ovf:Name>" attribute
Previously, the *virt-v2v* utility rejected the import of Open Virtual Appliances (OVAs) without the "<ovf:Name>" attribute. As a consequence, the *virt-v2v* utility did not import OVAs exported by Amazon Web Services (AWS). In this release, if the "<ovf:Name>" attribute is missing, *virt-v2v* uses the base name of the disk image file as the name of the virtual machine. As a result, the *virt-v2v* utility now imports OVAs exported by AWS.
|
Story Points: | --- | |
| Clone Of: | 1371843 | |||
| : | 1408124 (view as bug list) | Environment: | ||
| Last Closed: | 2017-08-01 22:11:26 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1359086, 1371843 | |||
| Bug Blocks: | 1395265, 1401077, 1401400, 1408124 | |||
|
Description
tingting zheng
2016-12-07 08:37:28 UTC
Upstream patches: 1ae4252c93c685cb8561b55c1231502b37212b5a 312379c8a61cd4a16aa7c80c1adda3081e601d43 (possibly) 98619f9c26076d034574b8822dfcc6799741ed96 Verify the bug with below builds: virt-v2v-1.36.3-2.el7.x86_64 libguestfs-1.36.3-2.el7.x86_64 libvirt-3.2.0-2.el7.x86_64 qemu-kvm-rhev-2.8.0-6.el7.x86_64 libguestfs-winsupport-7.2-2.el7.x86_64 virtio-win-1.9.0-3.el7.noarch Steps: Scenario1: 1.Download the AWS-storage-gateway.ova which is mentioned in comment0, uncompress this ova file to get the ovf file #tar -xvf AWS-storage-gateway.ova 2.Export a linux guest "rhel7.2" to ova file from vmware, uncompress rhel7.2 ova file to get the ovf file 3.Edit rhel7.2.ovf file according to aws-storage-gateway.ovf, the main changes are 3.1 Delete <Name> tag under <VirtualSystem> 3.2 Delete prefix "ovf" at <rasd:HostResource> 4.Using virt-v2v to convert the rhel7.2 ova file which was edited at step3 # virt-v2v -i ova rhel7.2-aws -o rhv -os 10.73.131.93:/home/nfs_export -of qcow2 -n ovirtmgmt -b ovirtmgmt [ 0.0] Opening the source -i ova rhel7.2-aws virt-v2v: warning: making OVA directory public readable to work around libvirt bug https://bugzilla.redhat.com/1045069 virt-v2v: warning: could not parse ovf:Name from OVF document [ 15.0] Creating an overlay to protect the source from being modified [ 15.2] Initializing the target -o rhv -os 10.73.131.93:/home/nfs_export [ 16.0] Opening the overlay [ 27.3] Inspecting the overlay [ 39.3] Checking for sufficient free disk space in the guest [ 39.3] Estimating space required on target for each disk [ 39.3] Converting Red Hat Enterprise Linux Server 7.2 (Maipo) to run on KVM virt-v2v: This guest has virtio drivers installed. [ 120.0] Mapping filesystem data to avoid copying unused and blank areas [ 120.5] Closing the overlay [ 120.8] Checking if the guest needs BIOS or UEFI to boot [ 120.8] Assigning disks to buses [ 120.8] Copying disk 1/1 to /tmp/v2v.fNsSrM/4f699f1d-7f77-4e73-a0d2-a3b73c1a0c29/images/b307cc38-0a6a-4c7d-9ba0-f8048002246d/d4652bf3-53e5-42cc-9136-b6d177694db6 (qcow2) (100.00/100%) [ 606.5] Creating output metadata [ 613.1] Finishing off 5.After finishing conversion, import the guest to data domain 6.Power on the guest and checkpoint are passed Scenario2: 1.Export a windows guest "win2008r2" to a ova file from vmware and uncompress rhel7.2 ova file to get the ovf file 2.Edit win2008r2.ovf file according to aws-storage-gateway.ovf, the main changes are 2.1 Delete <Name> tag under <VirtualSystem> 2.2 Delete prefix "ovf" at <rasd:HostResource> 3.Using virt-v2v to convert the win2008r2 ova file which was edited # virt-v2v -i ova win2008r2-aws -o rhv -os 10.73.131.93:/home/nfs_export -of raw -b ovirtmgmt -n ovirtmgmt [ 0.0] Opening the source -i ova win2008r2-aws virt-v2v: warning: making OVA directory public readable to work around libvirt bug https://bugzilla.redhat.com/1045069 virt-v2v: warning: could not parse ovf:Name from OVF document [ 42.4] Creating an overlay to protect the source from being modified [ 42.9] Initializing the target -o rhv -os 10.73.131.93:/home/nfs_export [ 43.1] Opening the overlay [ 48.7] Inspecting the overlay [ 50.3] Checking for sufficient free disk space in the guest [ 50.3] Estimating space required on target for each disk [ 50.3] Converting Windows Server 2008 R2 Standard to run on KVM virt-v2v: warning: /usr/share/virt-tools/pnp_wait.exe is missing. Firstboot scripts may conflict with PnP. virt-v2v: This guest has virtio drivers installed. [ 51.3] Mapping filesystem data to avoid copying unused and blank areas [ 51.7] Closing the overlay [ 52.2] Checking if the guest needs BIOS or UEFI to boot [ 52.2] Assigning disks to buses [ 52.2] Copying disk 1/1 to /tmp/v2v.xRDnsl/4f699f1d-7f77-4e73-a0d2-a3b73c1a0c29/images/92c3725b-f9a5-4ddc-8329-1803c856e838/c061bb90-e87b-4fe2-8d02-1272a1406808 (raw) (100.00/100%) [1197.1] Creating output metadata [1197.2] Finishing off 4.After finishing conversion, import the guest to data domain 5.Power on the guest and checkpoint are passed Scenario3: 1.Export a ova file from AWS EC2 #aws ec2 create-instance-export-task --instance-id i-0ed7a871968fb96ae --target-environment vmware --export-to-s3-task DiskImageFormat=VMDK,ContainerFormat=ova,S3Bucket=xx,S3Prefix=rhel6-ec2.ova EXPORTTASK export-i-fhdb9u4y active EXPORTTOS3TASK ova vmdk xx rhel6-ec2.ovaexport-i-fhdb9u4y.ova INSTANCEEXPORTDETAILS i-0ed7a871968fb96ae vmware 2.Using virt-v2v convert aws ova to rhv # virt-v2v -i ova rhel6-ec2.ovaexport-i-fhdb9u4y.ova -o rhv -os 10.73.131.93:/home/nfs_export -of qcow2 -n ovirtmgmt -b ovirtmgmt [ 0.0] Opening the source -i ova rhel6-ec2.ovaexport-i-fhdb9u4y.ova [ 15.6] Creating an overlay to protect the source from being modified [ 15.7] Initializing the target -o rhv -os 10.73.131.93:/home/nfs_export [ 38.3] Opening the overlay [ 42.5] Inspecting the overlay [ 47.7] Checking for sufficient free disk space in the guest [ 47.7] Estimating space required on target for each disk [ 47.7] Converting Red Hat Enterprise Linux Server release 6.2 Beta (Santiago) to run on KVM virt-v2v: warning: /files/boot/grub/device.map/hd0 references unknown device "vda". You may have to fix this entry manually after conversion. virt-v2v: warning: /files/etc/sysconfig/grub/boot references unknown device "vda". You may have to fix this entry manually after conversion. virt-v2v: This guest has virtio drivers installed. [ 77.8] Mapping filesystem data to avoid copying unused and blank areas [ 77.9] Closing the overlay [ 78.1] Checking if the guest needs BIOS or UEFI to boot [ 78.1] Assigning disks to buses [ 78.1] Copying disk 1/1 to /tmp/v2v.YO8qji/4f699f1d-7f77-4e73-a0d2-a3b73c1a0c29/images/cde3d0f0-2c26-4214-acd4-ff78aaa89d3c/6092a1c4-0796-401a-85e6-11c03ccd5591 (qcow2) (100.00/100%) [ 426.8] Creating output metadata [ 426.9] Finishing off 3.After finishing conversion, import the guest to data domain 4.Power on the guest and checkpoint are passed Scenario4: 1.Prepare a ova which was exported from Eaton Corporation and using virt-v2v convert this ova to rhv # virt-v2v -i ova IPM-1.53.158.VA_OVF10.ova -o rhv -os 10.73.131.93:/home/nfs_export -of qcow2 [ 0.0] Opening the source -i ova IPM-1.53.158.VA_OVF10.ova virt-v2v: warning: making OVA directory public readable to work around libvirt bug https://bugzilla.redhat.com/1045069 virt-v2v: warning: could not parse ovf:Name from OVF document [ 2.1] Creating an overlay to protect the source from being modified [ 2.3] Initializing the target -o rhv -os 10.73.131.93:/home/nfs_export [ 2.6] Opening the overlay [ 6.8] Inspecting the overlay [ 11.5] Checking for sufficient free disk space in the guest [ 11.5] Estimating space required on target for each disk [ 11.5] Converting CentOS release 6.8 (Final) to run on KVM virt-v2v: This guest has virtio drivers installed. [ 30.8] Mapping filesystem data to avoid copying unused and blank areas [ 32.4] Closing the overlay [ 33.6] Checking if the guest needs BIOS or UEFI to boot [ 33.6] Assigning disks to buses [ 33.6] Copying disk 1/1 to /tmp/v2v.053f3s/4f699f1d-7f77-4e73-a0d2-a3b73c1a0c29/images/d6cd9438-277b-4795-be87-b0e8bf7be8d6/fe3565d8-b60b-4250-b549-3f5bed06e3f2 (qcow2) (100.00/100%) [ 157.7] Creating output metadata [ 157.9] Finishing off 2.After finishing conversion, import the guest to data domain 4.Could power on the guest successfully Hi Pino, For scenario1,2,4. there will be virt-v2v warning : could not parse ovf:Name from OVF document, do you think it is necessary to hide this warning during v2v conversion? For scenario3, there is no warning about making OVA directory public readable to work around when v2v convert a AWS ova, but this warning will be shown when convert a vmware ova, why? Is it necessary to hide this warning when v2v converting a vmware ova conversion? (In reply to mxie from comment #6) > For scenario1,2,4. there will be virt-v2v warning : could not parse > ovf:Name from OVF document, do you think it is necessary to hide this > warning during v2v conversion? No, these warnings are not errors, but they describe anomalous conditions which virt-v2v is working around which the user may need to be aware of. > For scenario3, there is no warning about making OVA directory public > readable to work around when v2v convert a AWS ova, but this warning will be > shown when convert a vmware ova, why? Is it necessary to hide this warning > when v2v converting a vmware ova conversion? Again, the warnings aren't errors, they are there to warn the user about something which the program is doing which the user might need to be aware of. In this case when the libvirt bug (bug 1045069) is fixed we will remove the warning anyway. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2023 And how about `pnp_wait.exe`? Where should on install it from? At the moment you have to build it yourself. The source is here: https://github.com/rwmjones/rhsrvany virt-v2v will find the binary if it is called /usr/share/virt-tools/pnp_wait.exe (you can change the path part but not the binary name by setting $VIRT_TOOLS_DATA_DIR before running virt-v2v). |