Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

P2V Conversion failing at 98% on Converter version 6.2 with RHEL/Cent OS 7.6 machines (67504)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 15639Language:
Chinese (Simplified)English

8 like this article

Subscribe to get an email
newsletter with new updates

8 people found this helpful Please provide article feedback:

Symptoms

Converting a powered-on Red Hat Enterprise Linux 7.6 or CentOS 7.6 machine with a kernel that was updated to 3.10.0-957.5.1 fails at 98% with the following error:
Unable to reconfigure the destination virtual machine.

In the Task Progress tab, you see the following: An error occurred during the conversion: 'SysCommandWrapper: Error encountered in SysCommand: SysCommand failed to wait /usr/lib/vmware-converter/chrootAndExec.sh to terminate.

Unable to convert CentOS or RHEL after updating the OS to 7.6
The issue does appear with a fresh install of 7.6

Run this command and validate if the kernel is 3.10.0-957.5.1 or above
rpm -qa | grep -i kernel

Cause

helper.log

2019-02-27T12:03:37.267Z verbose vmware-converter-helper[F3357B70] [Originator@6876 sub=task-1] args[6]: grub-install
2019-02-27T12:03:37.368Z verbose vmware-converter-helper[F3357B70] [Originator@6876 sub=task-1] LogResult: Command return code: 127
2019-02-27T12:03:37.368Z verbose vmware-converter-helper[F3357B70] [Originator@6876 sub=task-1] LogResult: Command stderr:
--> /vmware-updateGrub.sh: line 63: grub-install: command not found
--> /vmware-updateGrub.sh: line 71: grub-install: command not found
--> Error installing GRUB
--> Command: grub-install --force --no-floppy /dev/sda
--> Error running vmware-updateGrub.sh through chroot into /mnt/p2v-src-root
--> Command: chroot "/mnt/p2v-src-root" /vmware-updateGrub.sh "GRUB2" "(hd0)" "(hd0,1)" /vmware-device.map "grub-install"
-->
2019-02-27T12:03:37.368Z verbose vmware-converter-helper[F3357B70] [Originator@6876 sub=task-1] LogResult: Command stdout:
--> Installing GRUB2 on (hd0)...
--> Installing GRUB2 on (hd0) failed.
--> Installing GRUB2 on /dev/sda...
-->
2019-02-27T12:03:37.368Z error vmware-converter-helper[F3357B70] [Originator@6876 sub=task-1] GrubInstaller::InstallGrub: /usr/lib/vmware-converter/installGrub.sh failed with return code: 127, and message:
--> /vmware-updateGrub.sh: line 63: grub-install: command not found
--> /vmware-updateGrub.sh: line 71: grub-install: command not found
--> Error installing GRUB
--> Command: grub-install --force --no-floppy /dev/sda
--> Error running vmware-updateGrub.sh through chroot into /mnt/p2v-src-root
--> Command: chroot "/mnt/p2v-src-root" /vmware-updateGrub.sh "GRUB2" "(hd0)" "(hd0,1)" /vmware-device.map "grub-install"
-->
--> Installing GRUB2 on (hd0)...
--> Installing GRUB2 on (hd0) failed.
--> Installing GRUB2 on /dev/sda...
-->

2019-02-19T06:19:10.682Z info vmware-converter-helper[F2F49B70] [Originator@6876 sub=task-1] GRUB installer context: grubCfgFilepath:/boot/grub2/grub.cfg, oldBootDisk:0, oldBootPartition:1, newBootDiskDevice:/dev/sda, newBootPartition:1, newBootVgName:, newBootLvName:, rootPartitionDevice:/dev/rhel/root, rootPartitionPath:/mnt/p2v-src-root, bootIsSeparate:1, kernelVersion:3.10.0-957.5.1.el7.x86_64, allowFakedInitrd: 1, bootOnGpt:0, callGrubInstall: 1
2019-02-19T06:49:13.487Z error vmware-converter-helper[F2F49B70] [Originator@6876 sub=task-1] Patching initrd image failed, trying to recover old config/initrd file
2019-02-19T06:49:13.487Z warning vmware-converter-helper[F2F49B70] [Originator@6876 sub=task-1] RestoreFile: File /mnt/p2v-src-root/boot/initramfs-3.10.0-957.5.1.el7.x86_64.img does not exists

Resolution

Currently Converter Standalone 6.2.x supports the following guest operating systems: CentOS 7.0, 7.1, 7.2, 7.3, 7.4, 7.5 (64-bit)

See workaround below, Issue is documented in the release notes here

NOTE: Before attempting new version, do check the OS compatibility with ESXi & converter.

Workaround

Ensure you have valid backups:

Workaround

Before the conversion, open a command line on the source machine and run the following command:

yum downgrade lvm2-libs-2.02.180-10.el7_6.2.x86_64 lvm2-2.02.180-10.el7_6.2.x86_64 device-mapper-event-libs-1.02.149-10.el7_6.2.x86_64 device-mapper-1.02.149-10.el7_6.2.x86_64 device-mapper-libs-1.02.149-10.el7_6.2.x86_64 device-mapper-event-1.02.149-10.el7_6.2.x86_64

After the conversion, run yum update on the target machine.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
E1000/E1000E アダプタを使用する仮想マシンのあるホストを ESXi 5.1 U2 にアップグレードするとネットワーク上の問題が発生する (2072694)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Converter Standalone

VMware vCenter Converter

Related Versions:

VMware vCenter Converter Standalone 6.x

Take Our Survey

Support Assistant