Loading

×Sorry to interrupt
CSS Error

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

Redhat 4 conversion fails or the virtual machine does not boot after successful conversion (1026348)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 15730Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

When converting a RHEL4 / RHAS4 operating system, you may experience these symptoms:

The conversion fails during cloning.

The conversion completes but the virtual machine fails to boot.

The Converter Agent log contains the errors:

ERROR -- Convert: converter.fault.CloneFault
(converter.fault.CloneFault) {
dynamicType = <unset>,
faultCause = (vmodl.MethodFault) null,
description = "/usr/lib/vmware-converter/copyFileSystem.sh did not finish producing output after 3600 seconds",

Upon booting the resulting virtual machine, you may see the error:

Grub Error "22"

Resolution

The conversion fails when the /var directory is cloned.

To isolate the cause of this issue:

Check these logs on the source physical machine to see if there is any indication why the tar failed:

/var/log/messages

/var/log/warn

Check the output of the dmesg command to see if there is any indication why the tar failed.

Do a test of tarring /var to another system (this is what happens in the helper virtual machine during conversion). From the other system that is simulating the actions of the helper virtual machine, run the commands:

# mkdir -p /tmp/p2v-src-root/var (assuming you have enough space in /tmp for the contents of /var from the source)

# ssh root@<IP</span>> "tar --one-file-system --sparse -C /var -cf - ." | tar -v -C /tmp/p2v-src-root/var -xf -

If Step 3 fails, try to determine which files were not cloned by doing a binary search of the/var tree on the source and /tmp/p2v-src-root on the destination. du -sh /var/foo tells you the size of each directory, so you can compare directory sizes until you find directories that differ in size.

RedHat conversions can fail due to the version of TAR installed on the source operating system. Version 1.14.XX has difficulty with sparse files (which are often found in /var) and difficulty handling long folder paths and long file names. To resolve this issue, see Enable Retention of Sparse Files During Linux Conversions (1008303).

VMware recommends that you also apply RedHat's tar bug fix update, then try to convert it to a virtual machine.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

Result 1 of 1

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 5.1.x

VMware vCenter Converter Standalone 5.0.x

VMware vCenter Converter Standalone 4.3.x

VMware vCenter Converter Standalone 4.0.x

VMware vCenter Converter 4.2.x

VMware vCenter Converter 4.1.x

VMware vCenter Converter 4.0.x

Take Our Survey

Support Assistant