Bug 1703405
Summary: | Virt-v2v can't convert ubuntu guest with open-vm-tools and ubuntu-server installed | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux Advanced Virtualization | Reporter: | Pino Toscano <ptoscano> |
Component: | libguestfs | Assignee: | Libvirt Maintainers <libvirt-maint> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 8.0 | CC: | juzhou, lcheng, mxie, mzhan, ptoscano, rjones, tzheng, virt-bugs, xiaodwan, zili |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | V2V | ||
Fixed In Version: | libguestfs-1.40.2-4.module+el8.0.1+3188+cd3de524 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1683888 | Environment: | |
Last Closed: | 2019-08-07 10:41: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: | |||
Bug Depends On: | 1683888 | ||
Bug Blocks: |
Description
Pino Toscano
2019-04-26 10:53:47 UTC
Verify bug with builds: virt-v2v-1.40.2-4.module+el8+3201+fd6ac632.x86_64 libvirt-5.0.0-7.module+el8+3023+072e7fc8.x86_64 libguestfs-1.40.2-4.module+el8+3201+fd6ac632.x86_64 qemu-kvm-3.1.0-25.module+el8+3153+f1590ef7.x86_64 Steps: 1. Prepare a ubuntu guest with VMware Tools service installed from Open-source VMware Tools. $ service open-vm-tools status ● open-vm-tools.service - Service for virtual machines hosted on VMware Loaded: loaded (/lib/systemd/system/open-vm-tools.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2019-05-15 07:29:03 UTC; 2min ago Docs: http://open-vm-tools.sourceforge.net/about.php 2. Convert guest from vmware to local by virt-v2v # virt-v2v -ic vpx://root.73.141/data/10.73.75.219/?no_verify=1 esx6.7-ubuntu18.04LTS-x86_64 --password-file /tmp/passwd -o rhv-upload -oc https://ibm-x3250m5-03.rhts.eng.pek2.redhat.com/ovirt-engine/api -os nfs_data -op /tmp/rhvpasswd -oo rhv-cafile=/home/ca.pem -oo rhv-direct=true -oo rhv-cluster=nfs -of raw -b ovirtmgmt [ 0.3] Opening the source -i libvirt -ic vpx://root.73.141/data/10.73.75.219/?no_verify=1 esx6.7-ubuntu18.04LTS-x86_64 [ 2.1] Creating an overlay to protect the source from being modified [ 2.7] Opening the overlay [ 19.6] Inspecting the overlay [ 34.2] Checking for sufficient free disk space in the guest [ 34.2] Estimating space required on target for each disk [ 34.2] Converting Ubuntu 18.04.2 LTS to run on KVM virt-v2v: warning: could not determine a way to update the configuration of Grub2 virt-v2v: warning: don't know how to install guest tools on ubuntu-18 virt-v2v: This guest has virtio drivers installed. [ 789.1] Mapping filesystem data to avoid copying unused and blank areas [ 789.7] Closing the overlay [ 789.9] Assigning disks to buses [ 789.9] Checking if the guest needs BIOS or UEFI to boot [ 789.9] Initializing the target -o rhv-upload -oc https://ibm-x3250m5-03.rhts.eng.pek2.redhat.com/ovirt-engine/api -op /tmp/rhvpasswd -os nfs_data [ 791.3] Copying disk 1/1 to qemu URI json:{ "file.driver": "nbd", "file.path": "/var/tmp/rhvupload.mwowFr/nbdkit0.sock", "file.export": "/" } (raw) (100.00/100%) [1676.1] Creating output metadata [1695.7] Finishing off 3. After finishing v2v conversion, power on guest in kvm and check vmware-tools service status $ service open-vm-tools status ● open-vm-tools.service - Service for virtual machines hosted on VMware Loaded: loaded (/lib/systemd/system/open-vm-tools.service; enabled; vendor preset: enabled) Active: inactive (dead) Condition:start condition failed at Wed 2019-05-16 02:59:32 UTC; 1min 27s ago └─ConditionVirtualization=vmware was not met Docs: http://open-vm-tools.sourceforge.net/about.php Result:There is no error about vmware tool during conversion and the guest can pass all checkpoints.So change 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, 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-2019:2395 |