Bug 1988279
| Summary: | Virt-v2v can't remove vmware-tools 11.0.5 successfully from win2019 and win10 guest after conversion | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | mxie <mxie> | ||||
| Component: | virt-v2v | Assignee: | Richard W.M. Jones <rjones> | ||||
| Status: | ASSIGNED --- | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 9.0 | CC: | chhu, juzhou, lersek, mzhan, rjones, tyan, tzheng, vwu, xiaodwan | ||||
| Target Milestone: | beta | Keywords: | Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 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
2021-07-30 09:15:48 UTC
I'm fairly sure this must happen because the fix for bug 1917760 is incomplete. In that bug we replaced the wrong /i option with /x. I can see from the log file that we are doing that here. But somehow we're getting the 1603 error which indicates that msiexec is still trying to install VMware Tools. While researching this I found this interesting VMware KBase article about how to nuke VMware from the system. We could try this as an alternative to using msiexec since that tool seems to be broken. https://kb.vmware.com/s/article/1001354 The error from the log is: CustomAction VM_LogStart returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) It appears that VMware Tools often doesn't uninstall, see someone having the same problem here: https://superuser.com/questions/1538084/uninstall-of-vmware-tools-fails-does-nothing I think the KB based approach above may be better. Downgrading sev/prio based on the availability of workarounds (I also fail to see a critical functional issue here). Should we make this bug a KB / documentation permanent restriction article? > Should we make this bug a KB / documentation permanent restriction article? Not sure what that means, but this does need some development and testing work to see if the approach of modifying the registry directly (comment 3) would work better. (In reply to Richard W.M. Jones from comment #6) > > Should we make this bug a KB / documentation permanent restriction article? > > Not sure what that means, but this does need some development and > testing work to see if the approach of modifying the registry directly > (comment 3) would work better. It would mean in practice that we won't try to solve a VMWare-tools bug from our end, but document the workaround for customers to do that themselves... If there's a reliable way we can avoid that, though, I agree we should pursue that. Just hope we don't 'invalidate' any Windows-related support / guarantees (I guess we really don't care about VMWare here, do we?) by editing the registry directly. But I take it we do that elsewhere as well.. *** Bug 1988442 has been marked as a duplicate of this bug. *** |