Bug 1834267
| Summary: | There is vddk error info when convert guest from ESXi host directly via vddk7.0 by virt-v2v | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux Advanced Virtualization | Reporter: | mxie <mxie> | ||||
| Component: | nbdkit | Assignee: | Virtualization Maintenance <virt-maint> | ||||
| Status: | CLOSED ERRATA | QA Contact: | mxie <mxie> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 8.2 | CC: | eblake, jsuchane, juzhou, mzhan, ptoscano, rjones, tyan, tzheng, virt-maint, xiaodwan, zili | ||||
| Target Milestone: | rc | Keywords: | Triaged | ||||
| Target Release: | 8.3 | Flags: | pm-rhel:
mirror+
|
||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | V2V | ||||||
| Fixed In Version: | nbdkit-1.20.6-1.module+el8.3.0+7631+c46a108a | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-11-17 17:48:34 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
mxie@redhat.com
2020-05-11 12:17:44 UTC
This seems like an harmless warning related to VMware's Customer Experience Improvement Program (CEIP), i.e. the "phone home" service: https://communities.vmware.com/thread/610375 https://github.com/vmware/powerclicore/issues/33 https://github.com/vmware/powerclicore/pull/38 In the first link somebody claims that this is fixed in (VMware) 6.7U3. What is the version of the ESXi you tested? > In the first link somebody claims that this is fixed in (VMware) 6.7U3. What
> is the version of the ESXi you tested?
Build number of our ESXi7.0 is 15843807
This is happening inside the VDDK plugin of nbdkit, so reassigning to nbdkit. Verify the bug with below builds: virt-v2v-1.42.0-5.module+el8.3.0+7152+ab3787c3.x86_64 libguestfs-1.42.0-2.module+el8.3.0+6798+ad6e66be.x86_64 libvirt-6.6.0-2.module+el8.3.0+7567+dc41c0a9.x86_64 qemu-kvm-5.1.0-2.module+el8.3.0+7652+b30e6901.x86_64 nbdkit-1.20.6-2.module+el8.3.0+7637+9ed826e0.x86_64 Steps: 1.Convert a guest from ESXi7.0 host via vddk7.0 by virt-v2v # virt-v2v -ic esx://root.199.217/?no_verify=1 -it vddk -io vddk-libdir=/home/vmware-vix-disklib-distrib -io vddk-thumbprint=C2:99:4E:B8:87:75:E8:41:71:6B:38:DA:07:C4:6B:0E:66:18:C0:75 -o rhv-upload -oo rhv-cafile=/root/ca.pem -oo rhv-direct -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -op /home/rhvpasswd -of raw -oo rhv-cluster=Default -os nfs_data -b ovirtmgmt esx7.0-rhel8.3-x86_64-efi -ip /home/esxpw [ 1.4] Opening the source -i libvirt -ic esx://root.199.217/?no_verify=1 esx7.0-rhel8.3-x86_64-efi -it vddk -io vddk-libdir=/home/vmware-vix-disklib-distrib -io vddk-thumbprint=C2:99:4E:B8:87:75:E8:41:71:6B:38:DA:07:C4:6B:0E:66:18:C0:75 [ 2.6] Creating an overlay to protect the source from being modified [ 3.3] Opening the overlay [ 10.1] Inspecting the overlay [ 31.6] Checking for sufficient free disk space in the guest [ 31.6] Estimating space required on target for each disk [ 31.6] Converting Red Hat Enterprise Linux 8.3 Beta (Ootpa) to run on KVM virt-v2v: This guest has virtio drivers installed. [ 125.8] Mapping filesystem data to avoid copying unused and blank areas virt-v2v: warning: fstrim on guest filesystem /dev/sda1 failed. Usually you can ignore this message. To find out more read "Trimming" in virt-v2v(1). Original message: fstrim: fstrim: /sysroot/: the discard operation is not supported [ 126.9] Closing the overlay [ 127.3] Assigning disks to buses [ 127.3] Checking if the guest needs BIOS or UEFI to boot virt-v2v: This guest requires UEFI on the target to boot. [ 127.3] Initializing the target -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -op /home/rhvpasswd -os nfs_data [ 128.7] Copying disk 1/1 to qemu URI json:{ "file.driver": "nbd", "file.path": "/tmp/v2vnbdkit.0bRCz4/nbdkit4.sock", "file.export": "/" } (raw) (100.00/100%) [ 586.4] Creating output metadata [ 588.6] Finishing off 2.Convert a guest from ESXi6.7 host via vddk7.0 by virt-v2v # virt-v2v -ic esx://root.75.219/?no_verify=1 -it vddk -io vddk-libdir=/home/vmware-vix-disklib-distrib -io vddk-thumbprint=DE:EA:A1:09:27:38:48:89:48:CB:95:A6:2B:5C:00:F3:53:13:25:44 -o rhv-upload -os nfs_data -of raw -b ovirtmgmt -n ovirtmgmt -oc https://ibm-x3250m5-03.rhts.eng.pek2.redhat.com/ovirt-engine/api -op /home/rhvpasswd -oo rhv-cafile=/home/ca.pem -oo rhv-direct -oo rhv-verifypeer=true -ip /home/esxpw esx6.7-rhel8.2-x86_64 [ 1.2] Opening the source -i libvirt -ic esx://root.75.219/?no_verify=1 esx6.7-rhel8.2-x86_64 -it vddk -io vddk-libdir=/home/vmware-vix-disklib-distrib -io vddk-thumbprint=DE:EA:A1:09:27:38:48:89:48:CB:95:A6:2B:5C:00:F3:53:13:25:44 [ 2.5] Creating an overlay to protect the source from being modified [ 3.3] Opening the overlay [ 10.9] Inspecting the overlay [ 36.1] Checking for sufficient free disk space in the guest [ 36.1] Estimating space required on target for each disk [ 36.1] Converting Red Hat Enterprise Linux 8.2 (Ootpa) to run on KVM virt-v2v: This guest has virtio drivers installed. [ 235.6] Mapping filesystem data to avoid copying unused and blank areas [ 236.9] Closing the overlay [ 237.2] Assigning disks to buses [ 237.2] Checking if the guest needs BIOS or UEFI to boot [ 237.2] Initializing the target -o rhv-upload -oc https://ibm-x3250m5-03.rhts.eng.pek2.redhat.com/ovirt-engine/api -op /home/rhvpasswd -os nfs_data [ 238.6] Copying disk 1/1 to qemu URI json:{ "file.driver": "nbd", "file.path": "/tmp/v2vnbdkit.j0Vu7U/nbdkit4.sock", "file.export": "/" } (raw) (100.00/100%) [ 793.7] Creating output metadata [ 795.3] Finishing off 3.Check guests on rhv after v2v conversion, the checkpoints of guest are passed Result: There is no vddk error info when convert guest from ESXi host directly via vddk7.0 by virt-v2v, so move the 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 (virt:8.3 bug fix and enhancement update), 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-2020:5137 |