Bug 678232
Summary: | virtv2v convert windows guest with vmware-tools from esx,it will show the vmware-tools error msg | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Huang Wenlong <whuang> | ||||||||||
Component: | virt-v2v | Assignee: | Matthew Booth <mbooth> | ||||||||||
Status: | CLOSED DEFERRED | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||||||
Severity: | medium | Docs Contact: | |||||||||||
Priority: | high | ||||||||||||
Version: | 6.1 | CC: | cwei, dpal, mprpic, mshao, mzhan, pkennedy, rjones, syeghiay | ||||||||||
Target Milestone: | rc | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | Unspecified | ||||||||||||
OS: | Unspecified | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
Doc Text: |
VMware Tools on Microsoft Windows is unable to disable itself when it detects that it is no longer running on a VMware platform. Consequently, converting a Microsoft Windows guest from VMware ESX which has VMware Tools installed will result in errors. These errors usually manifest as error messages on startup, and a "Stop Error" (also known as a BSOD) when shuting down the guest. To work around this issue, uninstall VMware Tools on Microsoft Windows guests prior to conversion.
|
Story Points: | --- | ||||||||||
Clone Of: | |||||||||||||
: | 711972 (view as bug list) | Environment: | |||||||||||
Last Closed: | 2014-11-18 11:17:19 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: | 702988, 711972 | ||||||||||||
Attachments: |
|
Description
Huang Wenlong
2011-02-17 08:56:57 UTC
Created attachment 479283 [details]
libgestfs_trace
Created attachment 479284 [details]
win2k3-vmware-tools-error-msg
most guest in the ESX will be installed vmware-tools so change the priority to high This is a known issue, and unfortunately we don't have capacity to fix this right now. The workaround is to uninstall vmware tools after conversion. the guest with vmware-tools will BSOD when shutdown after conversion , but if uninstall vmware-tool from the guest before conversion then converting it and it will shutdown without BSOD after conversion . please check attachment about BSOD Created attachment 479297 [details]
BSOD-vmware-tools
(In reply to comment #5) > This is a known issue, and unfortunately we don't have capacity to fix this > right now. The workaround is to uninstall vmware tools after conversion. thanks , I got it . Created attachment 480496 [details]
Patch to uninstall vmware tools from firstboot.bat
This patch looks for vmware tools in the software hive, and adds a line to firstboot.bat to uninstall it if it's detected.
I haven't pushed this yet because I haven't actually replicated the reported behaviour. I'm just getting 0x7B BSODs for converted Windows guests at the moment. Hopefully this is an unrelated quirk of my development system.
The approach in the above patch doesn't work. VMware Tools cannot be uninstalled using its own installer unless it is still running on VMware virtual hardware. The error message is: "Setup failed to determine which VMware product this virtual machine is running on. Click OK to cancel the installation." There is no option to continue. A web search doesn't suggest any simple workarounds. I saw a suggestion that vmware tools can be forcibly removed using the original VMware Tools installation media and running setup.exe /c. This doesn't work, as it only forcibly removes the installation registry entries. It doesn't unconfigure any services, or remove anything from disk. 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 Converting a Microsoft Windows guest from VMware ESX which has VMware Tools installed. Note that this does not affect Linux guests. What actions or circumstances cause the bug to present (if known). VMware Tools on Microsoft Windows is not able to disable itself when it detects that it is no longer running on a VMware platform. It also prevents uninstallation when not running on a VMware platform. Consequence After conversion, VMware Tools will display several error messages on startup, and the guest will always BSOD on shutdown. It is not possible to uninstall or disable VMware Tools. Workaround The only currently known workaround is to uninstall VMware Tools on Microsoft Windows guests prior to conversion. Result Uninstalling VMware Tools causes the conversion to work normally as intended. It is not ideal, as it requires modification of the original guest. The modification is, however, reversible. VMware Tools can be reinstalled on the original guest to restore its full functionality. Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as an exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,14 +1 @@ -Cause +VMware Tools on Microsoft Windows is unable to disable itself when it detects that it is no longer running on a VMware platform. Consequently, converting a Microsoft Windows guest from VMware ESX which has VMware Tools installed will result in errors. These errors usually manifest as error messages on startup, and a "Stop Error" (also known as a BSOD) when shuting down the guest. To work around this issue, uninstall VMware Tools on Microsoft Windows guests prior to conversion.-Converting a Microsoft Windows guest from VMware ESX which has VMware Tools installed. Note that this does not affect Linux guests. - -What actions or circumstances cause the bug to present (if known). -VMware Tools on Microsoft Windows is not able to disable itself when it detects that it is no longer running on a VMware platform. It also prevents uninstallation when not running on a VMware platform. - -Consequence -After conversion, VMware Tools will display several error messages on startup, and the guest will always BSOD on shutdown. It is not possible to uninstall or disable VMware Tools. - -Workaround -The only currently known workaround is to uninstall VMware Tools on Microsoft Windows guests prior to conversion. - -Result -Uninstalling VMware Tools causes the conversion to work normally as intended. It is not ideal, as it requires modification of the original guest. The modification is, however, reversible. VMware Tools can be reinstalled on the original guest to restore its full functionality. This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4. This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. Virt-v2v needs to run on the latest Red Hat Enterprise Linux release to ensure it can correctly read and modify new guest filesystem features. A new version of virt-v2v is now available for RHEL 7.1. Before RHEL 7.1 is released, follow the instructions here to install unsupported preview packages on top of RHEL 7.0: https://www.redhat.com/archives/libguestfs/2014-May/msg00090.html After RHEL 7.1 is released, virt-v2v will be available in Technical Preview. You can run virt-v2v in a single virtual machine. Other requirements are covered here: http://libguestfs.org/virt-v2v.1.html#resource-requirements If you find a missing feature or bug in the new version of virt-v2v please file a bug using the following link: https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%20Linux%207&component=libguestfs |