Bug 1167302
| Summary: | virt-v2v: warning: ova hard disk has no parent controller when convert from a ova file | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | zhoujunqin <juzhou> | ||||||
| Component: | libguestfs | Assignee: | Richard W.M. Jones <rjones> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 7.1 | CC: | codong, dyuan, liye, mbooth, ptoscano, rjones, tzheng | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | V2V | ||||||||
| Fixed In Version: | libguestfs-1.28.1-1.14.el7 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2015-03-05 13:47:35 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
zhoujunqin
2014-11-24 12:27:19 UTC
The current code assumes that every <Item> element that
we read will contain a <Parent> link. However the floppy
disk in this VM does not:
<Item ovf:required="false">
<rasd:AddressOnParent>0</rasd:AddressOnParent>
<rasd:AutomaticAllocation>false</rasd:AutomaticAllocation>
<rasd:Description>Floppy Drive</rasd:Description>
<rasd:ElementName>Floppy drive 1</rasd:ElementName>
<rasd:InstanceID>10</rasd:InstanceID>
<rasd:ResourceSubType>vmware.floppy.remotedevice</rasd:ResourceSubType>
<rasd:ResourceType>14</rasd:ResourceType>
</Item>
(Note no <rasd:Parent> element)
Patch posted here:
https://www.redhat.com/archives/libguestfs/2014-November/msg00181.html
Try to verify with new build: libguestfs-1.28.1-1.14.el7.x86_64 virt-v2v-1.28.1-1.14.el7.x86_64 Steps to Reproduce: 1. Export an ova file from vcenter server: 2. Use virt-v2v to convert RHEL image to libvirt image # virt-v2v -i ova test-bug1164853-new.ova -o local -os /var/tmp -on test-bug1164853-new-test -of raw -on test-bug1164853-new-test-2 [ 0.0] Opening the source -i ova test-bug1164853-new.ova [ 101.0] Creating an overlay to protect the source from being modified [ 102.0] Opening the overlay [ 107.0] Initializing the target -o local -os /var/tmp [ 107.0] Inspecting the overlay [ 117.0] Checking for sufficient free disk space in the guest [ 117.0] Estimating space required on target for each disk [ 117.0] Converting Red Hat Enterprise Linux Server release 6.6 (Santiago) to run on KVM virt-v2v: This guest has virtio drivers installed. [ 148.0] Mapping filesystem data to avoid copying unused and blank areas [ 149.0] Closing the overlay [ 149.0] Copying disk 1/1 to /var/tmp/test-bug1164853-new-test-2-sda (raw) (100.00/100%) [ 199.0] Creating output metadata [ 199.0] Finishing off Result: There is no warning message showing during conversion, and after that, i can use virsh cmd define guest and guest can boot up correctly. # virsh define /var/tmp/test-bug1164853-new-test-2.xml Domain test-bug1164853-new-test-2 defined from /var/tmp/test-bug1164853-new-test-2.xml But i found in detail debug log, there are a lot of error message displayed, and i'm not sure whether it matters to verify this bug, please help me have a look, thanks. Created attachment 962395 [details]
detail debug info for virt-v2v
In general, if the conversion is successful and the guest boots up and works, then you can ignore the debug log. Is there anything in particular in the debug log that you are concerned about? It all looks normal to me. (In reply to Richard W.M. Jones from comment #7) > In general, if the conversion is successful and the guest boots up > and works, then you can ignore the debug log. Is there anything > in particular in the debug log that you are concerned about? It > all looks normal to me. Thanks for your quick reply, and according to above comments move this bug from ON_QA to VERIFIED. 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://rhn.redhat.com/errata/RHBA-2015-0303.html |