Quantcast
Channel: VMware Communities: Message List - Converter Standalone
Viewing all 8478 articles
Browse latest View live

Re: how convert physical linux server to virtual without change in file system

$
0
0

Hello

 

First a little correction - df displays the volume size, not the partition size.

There is no straightforward way to specify an exact preservation of the volume size.

Linux P2V conversion is file level and is not meant to preserve the binary layout of the disks (unlike disk based V2V conversions for example). There are many things taken into account that affect the volume size like partition alignment, creating logical volumes (IIRC LVM extent size is not preserved), volume block size is also not preserved. All these little differences and adjustments may pile up and result in slightly different volume size.

I am curious - why do you want exact volume size preservation?

 

Regards,

Plamen


Re: how convert physical linux server to virtual without change in file system

Unable to update drive letters for the destination volume layout

$
0
0

Hello Community!

 

I try to convert a local System to a virtual one using  VMware vCenter Converter Standalone.

 

Should be an easy job. But I fail.

I get:

Warning: Unable to update drive letters for the destination volume layout.

Error: An error occurred during reconfiguration.

And then FAILED: A general system error occurred:
Platform-specific error 2.

I already studied the log files – but no success.

 

Can somebody help me to fix this problem? 

 

Thanks

 

Erhard

The logs are attached for your analysis

Re: Unable to update drive letters for the destination volume layout

$
0
0

These logs are not useful because they are for GUI. Please attach worker's log found in %ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone\logs

Re: Unable to update drive letters for the destination volume layout

$
0
0

Hi There,

 

Did you unistall the unwanted driver from converted Vm and installed the VMtools?

 

Please keep posted the status.

 

Thanks

Re: Unable to update drive letters for the destination volume layout

$
0
0

Hi Poceh!

 

Hopefully I uploaded now more useful logs.

 

Best regards

 

Erhard

Re: Unable to update drive letters for the destination volume layout

$
0
0

I see two important errors:

1016 which means "An I/O operation initiated by the registry failed unrecoverably. The registry could not read in, or write out, or flush, one of the files that contain the system's image of the registry." and

1450 which means "Insufficient system resources exist to complete the requested service."

Your option is to try to 'Reconfig' only your target VM and try to boot it.

Otherwise you need to check your source system for disk errors, for example with 'chkdsk /B'.

HTH

Re: Unable to update drive letters for the destination volume layout

$
0
0

Hi PECEH!

 

 

 

Well, I have performed chckdsk and will try again

 

Can you please provide me some more details:

 

  • which of the logs exactly contain these errors
  • how can I 'Reconfig' only the target VM'

 

I'm not experienced with VW stuff.

 

Thanks

 

Erhard


Re: Unable to update drive letters for the destination volume layout

$
0
0

On Source server open registry > go to HKLM>System>MountedDevices. Export 'MountedDevices' and restore it on destination VM then reboot once.

Re: Unable to update drive letters for the destination volume layout

$
0
0

This is *not* recommended! The VM could not boot if you restore the MountedDevices!

Re: Unable to update drive letters for the destination volume layout

$
0
0

Instead of choose 'Convert machine', choose the 'Configure machine' and point your newly created VM.

HTH

Re: Unable to convert P2V source: Ubuntu 14.04, with VMWare vCenter Coverter Standalone 6.0.0

$
0
0

Hello

 

the relevant error seems to be:

fatal: no matching mac found: client hmac-sha1,hmac-sha1-96,hmac-md5 server hmac-sha2-256,hmac-sha2-512 [preauth]

Converter uses OpenSSH 5.7 which, it seems, doesn't implement sha2 MAC. You could relax a little the source machine sshd (see man page for sshd_config) and try again.

I'll log a bug to upgrade Converter's OpenSSH in a future release.

 

HTH

Plamen

Re: Unable to convert P2V source: Ubuntu 14.04, with VMWare vCenter Coverter Standalone 6.0.0

Re: Unable to update drive letters for the destination volume layout

$
0
0

you can follow belew steps

 

To resolve this issue:

  1. Import the virtual machine to vCenter Server.
  2. Boot the virtual machine from the correct Microsoft Windows installation media (Correct architecture and version of the operating system).
  3. Select the appropriate keyboard layout and language options and click Next.
  4. Click Repair your computer.
  5. Select the operating system to be repaired and click Next.
  6. Click Start> Run, type cmd and click OK.
  7. Type bcdedit and press Enter.
  8. Under the Windows Boot Manager title with the identifier set to {bootmgr}, you may see that the device is set to boot. Similarly, under the Windows Boot Loader with the identifier set to {default}, you may see that the device and osdevice are set to boot. These items should be set properly for your environment. Usually these appear as partition=C:. In some cases the {default} identifier may have them set to partition=D:.

    Run these commands to correct the configuration:

    Note: bcdedit is located in this path: c:\windows\system32.

    bcdedit /set {bootmgr} device partition=C:

    bcdedit /set {default} device partition=C:

    bcdedit /set {default} osdevice partition=C:
  9. Type exit at the command prompt and select Shutdown.
  10. Try to reconfigure using VMware Converter. The reconfigure should now complete successfully. If it fails again, repeat Steps 1 to 7 and then run these commands to set the default device to partition=D::

    bcdedit /set {bootmgr} device partition=C:

    bcdedit /set {default} device partition=D:

    bcdedit /set {default} osdevice partition=D:

    Note: The D: partition is used as an example. You can use any available drive letter.

Note: If, after running the preceding bcdedit commands, the virtual machine boots and then fails with a blue screen, perform these steps to resolve the issue:

  1. Boot the virtual machine from the Windows 2008 ISO.
  2. Load the Recovery Console.
  3. Click Start > Run, type regedit, and click OK. The Registry Editor window opens.
  4. Click HKEY_LOCAL_MACHINE (HKLM) and then click Menu> File> Load Hive.
  5. Browse to C:\Windows\system32\config and select the file SYSTEM.
  6. When prompted for a name enter p2v.
  7. Locate the key HKLM\p2v\ControlSet001\services\LSI_SAS.
  8. Set the value of the start type to REG_DWORD 0.
  9. Select HKLM\p2v and click Menu> File> Unload Hive.
  10. Close Registry Editor and restart the virtual machine.

For more information, see Virtual machine fails to boot with a blue diagnostic screen stating: 7B Stop Code after using VMware Converter (2002106).

Note: If your problem persists even after trying the steps in this article, file a support request with VMware Support and note this Knowledge Base article ID (1037507) in the problem description. For more information, see How to Submit a Support Request.

Re: Unable to convert P2V source: Ubuntu 14.04, with VMWare vCenter Coverter Standalone 6.0.0

$
0
0

A little correction. Since you can't query the source machine, the 'culprit' is not openssh in converter helper, but plink.

Anyway - the workaround is the same.


Re: Unable to convert P2V source: Ubuntu 14.04, with VMWare vCenter Coverter Standalone 6.0.0

$
0
0

Please do not post irrelevant links, they can cause confusion and waste of time rather than be helpful.

Your link is about:

- failure to reconfig, not query source

- Debian, not Ubuntu

- earlier versions of Converter, not 6.0 (note that Converter 6.0 can deal with Debian)

 

Regards,

Plamen

Re: Unable to update drive letters for the destination volume layout

$
0
0

Hi all!

 

Thanks for all your hints.

 

I tried a lot. But no success till now.

 

Always the same ugly error messages.

Starting machine. Always Crashes bluescreen evwn in save mode etc etc. Really frustrating.

The bluescreen disappears rather quickly. I can’t catch it

 

After some days off I will try again or give anopther platform a chance to vitualize my machine.

Best regards

 

Erhard

Re: Unable to convert P2V source: Ubuntu 14.04, with VMWare vCenter Coverter Standalone 6.0.0

$
0
0

Hi Plamen!

I added required MACs to sshd_config - and converter connected!

 

Thank you for your help,

Evgenii

Re: Conversion starts, then fails at 3% with network unreachable error.

$
0
0

See if this helps you

 

P2V Percentages:

1%VSS, Remove multiple   VSS-providers from registry (Link)
1%Unable to start the   change tracking driver, User Account Control (Link)
2%Network issue, Set   speed/duplex auto/auto (Link)
2-96%Multiple,   IP/DNS/Hardware (Link   Link   Link)
3%DNS issue, set DNS   suffix (Link)
3-92%Reducing disk volume   size, Checkdisk (Link)
95-99%Fails at reconfiguration,   Missing files or drivers(Link)
96%Unable to find the   system volume, Windows Boot manager (Link   Link)
97%No Active   Partitions, Break software mirror (Link)
97-99%Inaccessible_boot_device,   Driver issue (Link   Link)
98%Unable to create,   3GB switch boot.ini (Link)
99%Unable to determine   guest OS, boot.ini (Link)
CommonLink

 

Regards

Rahul

OS Compatibility

$
0
0

Hello,

 

Can anyone advise if the following OS are compatible with the latest vCenter converter edition

 

  • Microsoft Windows Server 2008 R2 Enterprise
  • Microsoft Windows Server 2003 Enterprise
  • Microsoft Windows Server 2003 R2 Enterprise

 

Thank You

Viewing all 8478 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>