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

Converting a virtual machine using VMware vCenter Converter fails with the error: Unable to allocate memory error (1031065)

Last Updated: 3/20/2024Categories: Total Views: 6312Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Cannot convert a virtual machine using VMware vCenter Converter

Converting a virtual machine using Converter fails at about 50%

Converter agent service on the source server crashes

The Event Viewer reports Event ID 7034

In the vmware-converter-agent.log file located at C:\Documents and Settings\All Users\Application Data\VMware\VMware Converter Enterprise\Logs, you see a backtrace similar to:

[#2] [2010-11-02 10:16:27.774 02820 error 'App'] Unable to allocate memory: 621522448 bytes [#2] [2010-11-02 10:16:27.868 02820 info 'App'] CoreDump: Writing minidump [#2] [2010-11-02 10:16:29.743 02820 panic 'App'] [#2] [#2] Panic: Unable to allocate memory [#2] Backtrace: [#2] backtrace[00] rip 00000615 (no symbol) [#2] backtrace[01] rip 00000000 (no symbol) [#2] backtrace[02] rip 00000000 (no symbol) [#2] backtrace[03] rip 00000000 (no symbol) [#2] backtrace[04] rip 00000000 (no symbol
[#2] backtrace[59] rip 00000000 (no symbol) [#2] backtrace[60] rip 00000000 (no symbol) [#2] backtrace[61] rip 00000000 (no symbol) [#2] [#2] [2010-11-02 10:16:29.743 02820 panic 'App'] Unable to allocate memory

Resolution

This issue occurs when at least one of the source disks from the virtual machine you are trying to convert contains a large amount of small files and a file-based conversion is performed. A file-based conversion is performed when you try to shrink the disks as part of the conversion.

If the drive that has a large amount of small files is the boot drive, you cannot perform a conversion and cannot resize the drive. VMware is aware of this issue and is working to resolve this.

To workaround this issue:

Convert the source machine without shrinking the disks.

Power on the resulting virtual machine after the conversion completes.

Identify the drives has a large amount of files.

Add a .vmdk file with the required size of the disk you want and present it as another drive to the guest operating system.

Copy the data from the drive you want to shrink to the newly presented drive.

After all the data is copied and verified, remove the disk you wanted to resize.

Assign the drive (that has the size you wanted) with the drive letter that it originally had on the physical system.

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)

KB
•
VirtualCenter Converter プラグインを使用した物理サーバから仮想サーバへの変換に失敗する (1018251)

KB
•
Windows ゲストのカスタマイズで Active Directory ドメインにデプロイ済みの仮想マシンを結合できない (1012314)

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

VMware Converter

Related Versions:

VMware vCenter Converter Standalone 5.0.x

VMware vCenter Converter 4.2.x

VMware vCenter Converter 4.1.x

VMware vCenter Converter 4.0.x

VMware Converter 3.0.x

Take Our Survey

Support Assistant