Bug 787734
Summary: | virt-v2v does not remove VMware guest tools RPMs | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Marko Myllynen <myllynen> | |
Component: | virt-v2v | Assignee: | Matthew Booth <mbooth> | |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 6.2 | CC: | rjones, rwu, tzheng, yupzhang | |
Target Milestone: | rc | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | virt-v2v-0.8.7-1.el6 | Doc Type: | Bug Fix | |
Doc Text: |
Cause
The customer is converting a VMware guest which has installed the newer style of VMware tools which are split into multiple packages.
Consequence
VMware tools are not removed during the conversion process. They may cause warnings to be displayed in the converted guest, or cause it to function incorrectly.
Fix
The conversion process was updated to recognise the new VMware tools packages and remove them.
Result
VMware tools packages are correctly removed during conversion.
|
Story Points: | --- | |
Clone Of: | ||||
: | 837167 (view as bug list) | Environment: | ||
Last Closed: | 2012-06-20 12:42:02 UTC | Type: | --- | |
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: | ||||
Bug Blocks: | 837167 |
Description
Marko Myllynen
2012-02-06 16:02:26 UTC
Looks like the rpms have been renamed. They're now called vmware-tools-* and kmod-vmware-tools-*. We've already previously decided not to remove kmods, but we ought to remove anything called vmware-tools-*. Fixed in upstream commit 15dc5512ad49419df5d921ab76df55ff93ca35c9. When convert a VMware guest with vmware tools installed,it will install some replacement dependencies for some packages,due to Bug 800353,virt-v2v failed to install packages using yum during conversion,so the bug is blocked by Bug 800353. As the Bug 800353 has been fixed,so tested the bug with: virt-v2v-0.8.7-4.el6.x86_64 libvirt-0.9.10-4.el6.x86_64 libguestfs-1.16.8-1.el6.x86_64 Steps: 1.Configure a esx rhel6 guest with vmware repo and install vmware-tools-* and kmod-vmware-tools-* 2.Use virt-v2v to convert the guest. # virt-v2v -ic esx://10.66.72.149/?no_verify=1 -os default -b breth0 rhel6.2-x64-vmware-tools rhel6.2-x64-vmware-tools_rhel6.2-x64-vmware-tools: 100% [==============================================]D 0h10m06s virt-v2v: rhel6.2-x64-vmware-tools configured with virtio drivers. 3.After conversion,check the guests 1).check the vmware repo It has been disabled. 2)check whether the vmware tools packages have been removed. #rpm -qa|grep vmware-tools #rpm -qa|grep kmod The vmware-tools-* and kmod-vmware-tools-* are all removed. As comment 2 said:"We've already previously decided not to remove kmods, but we ought to remove anything called vmware-tools-*." matthew,it removed all kmod packages,does it have problem or have you decided to design that way? Removing these kmods didn't cause any problems in my testing, and as they're VMware-specific I think they're unlikely to. This is deliberate in this case. Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause The customer is converting a VMware guest which has installed the newer style of VMware tools which are split into multiple packages. Consequence VMware tools are not removed during the conversion process. They may cause warnings to be displayed in the converted guest, or cause it to function incorrectly. Fix The conversion process was updated to recognise the new VMware tools packages and remove them. Result VMware tools packages are correctly removed during conversion. 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. http://rhn.redhat.com/errata/RHBA-2012-0788.html |