Crikey! The 1st time I try to use the converter standalone and I get this error when it trys to install the agent on the remote source! I've followed the instructions to the letter: Converter installed on XPSP3 in the same workgroup as the source XPSP3 PC. Admin a/c and password correct ( I can net use a share when sharing is switched on). Firewalls on both PCs switched off. File sharing on the source disabled (not quite sure why I have to do this, but it's in the instructions).

I get these entries in the converter-worker-1.log:

Install Agent on 192.168.2.5

Connecting to ADMIN$ on 192.168.2.5 as 192.168.2.5\administrator

SMB manager: Host could not be reached over the network to map share http://\\192.168.2.5\ADMIN$.

And that's it. I tried re-enabling file sharing on the source, but that made no difference.

What am I doing wrong? Is there a workaround? Please help!

Regards, Peter

I have been told that I can not use vCenter Converter or the Standalone Converter to convert a VHD file to vmdk.  file to use to create a VM on vCenter ESXi host.  Is that correct?   I thought that this was possible or is it only possible directly from a running hyper-V virtual machine?

I have a Windows 2003 server that I am trying to convert from a physial server to a VM guest using vCenter Converter Standalone.  The original drive letters for this server are f: and g: where F: drive is my system boot drive.  As I go through the process, the target says F: and G: drive but when it is done it gives me an error that no operating sytem found.  I start the machine up and choose Windows Recovery mode and now see that the drive letters are changed to c: and d: drives which is why it will not start. I tried using diskpart from recovery mode but it will not allow me to change these drive letters.  How do I get it to change or remain at F: and G: when using the vcenter converter?

Thanks.

As the subject notes, I'm trying to test out converting some physical systems to VMWare using Converter 5.5 Standalone. Running it on a Windows 7 system, and I'm attempting to convert a Linux system that's running CentOS6. The wizard goes through smooth, and the source information is pulls down all looks correct. The conversion starts, connects to the helper, and starts formatting the destination. Then, at 3%, the conversion fails with this error:

FAILED: A general system error occurred: connect (`192.168.8.232'): Network is unreachable connect (`192.168.8.232'): Network is unreachable connect (`192.168.8.232'):

Network is unreachable Network error. Host 192.168.8.232 key can't be retrieved. (return code 2)

192.168.8.232 in this case is the source system. It's up and running just fine, and I maintain a SSH connection the entire time, but for some reason this error keeps coming up and I'm not sure why.

The conversion prompts for the key initially when the process starts, so I'm not sure if the "key can't be retrieved" error is as result of the "network unrechable" error, or if the key error comes first before the network error. Either way, network connectivity is fine, and I'm stumped as to why it keeps failing at this point. Any thoughts?

Hello,

I'm working on a customer to convert his physical servers to vSphere 5.5 infrastructure.

I'm using converter 5.5 and have problems P2Ving one windows 2003 server with system disk with 2 partitions (C and E).

Physical Server

Disk 2: system disk with 2 partitions (C:, E: )

Vmware Converter

I have converted in following way:

Partition C:, G:, F: together

Partition E: standalone (converter 5.5 doesn’t support conversion of multiple partitions on the same disk).

Result is I have one virtual machine with 3 vmdk (disks C, G, F) and another “fake” virtual machine with only one vmdk (disk E).

I have moved the disk E vmdk to the folder of the “real” vm and added it to the virtual machine.

Boot.ini file is as following:

timeout=30

default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Standard" /fastdetect

When I boot the virtual machine, I see the boot.ini menu, but the system doesn’t start and loop forever to boot menu.

Can anyone help me ?

thanks in advance

Best regards

Davide

Hi,

I get the following error:

FAILED: The VSS snapshots cannot be stored because there is not enough space on the source volumes or because the source machine does not have any NTFS volumes. Error code: 2147754783 (0x8004231F).

I have windows 7 Pro with SSD.

Used space: 16 GB

Free space: 39.7GB

any idea how to solve this issue?

Thanks!!

Dotan.

Hopefully just a quick question but can I use a newer version of the converter to convert a server to a ESXI 5.5.3 server? Server is 2008R2 and if I try an download the 5.5 converter it brings me to a page that I can only download 6.0 or newer. Thanks in advance

I am trying to convert a Windows 2000 SP4 (SCSI attached 12GB c:\ drive, 1024MB memory) running on Microsoft Virtual Server over to VMware(Version 3.5.0 Build 123630) using VMware converter 3.0.3-89816.  The conversion process completes successfully, but when I try to start the server in VMware I receive a page fault in non paged area win32k.sys BSOD.  Any ideas?  Thanks.

I am trying to convert an Acronis .TIB archive to a Workstation VM.  I installed vCenter Converter 5.0, but when I tried to initiate a conversion I get an 'invalid parameters' message when I select the .TIB archive. 

Any ideas on how to get Acronis True Image 2013 and vmware to play nice, since Converter says it supports TIB files?

Thanks!

Hello,

I need to P2V our Windows 2003 Server Enterprise. Ran the converter, it finished fine with 100% completed. When trying to boot server i got 0x7B error.

Specifically STOP 0x0000007B (0xF78AAA94, 0xc0000034, 0x00000000, 0x00000000)

Converter version 4.3.0 Standalone

During conversion left disk drivers as Source.

Environment:

VMware vCenter Standalone Converter v6.1.1 installed in local-only mode on

Windows Server 2016 with the converter installed on a physical server (ip 10.160.0.69/24)

Unbuntu Desktop 12.05 Test VM in a Hyper-V Cluster (ip 10.160.0.65/24)

VMware ESXi 6.0.0 (trial) on a physical server (ip 10.160.0.66/24)

Same switch, default gateway (10.160.0.1), dns servers

Hello!

I am testing a proof of concept for my company where we can capture any physical machine on our network and bring it into our Hyper-V cluster. The best way I have found to do this is with VMware ESXi and converter. I have setup a test Ubuntu VM that to capture to ESXi. I installed openssh-server on the VM and can ssh into it from the .69 Windows Server using Putty. When I go to convert the VM with VMware, Isetup the job and start it. It starts with 1% about 1 hr then 2% 3hrs 15min, then 3% 1hr, then 3% 1min, then failed at 3%. Here is the status the job ends with:

FAILED: A general system error occurred: connect (`10.160.0.65'): Network is unreachable connect (`10.160.0.65'): Network is unreachable connect (`10.160.0.65'):
Network is unreachable Network error. Host 10.160.0.65 key can't be retrieved. (return code 2)

I don't understand why this is happening. All your help is appreciated. I'll be at my desk to answer any questions or post any more needed info.

Thanks in Advance!

Hi all,

I'm having an issue using the standalone converter to p2v a linux (CentOS) box.  It gets to 1% then fails with the following error:

FAILED: A general system error occurred:

Network error. Host 10.0.2.19 key can't be retrieved. (return code 2)

(Note: 10.0.2.19 is the IP of the CentOS box.)

Running 5.01 build 1087880 of the converter (latest as of today), and ESXi 5.1.

Anyone ever come across this error before or know what it means?  Google isn't very helpful...

Thanks in advance,

Colin

There have been many complaints about transfer rate degradation in Converter 5.0.

Converter uses NFC (a proprietary VMware protocol) for cloning to managed destination. Security has been enhanced in Converter 5.0 by encrypting the data transfer. Unfortunately this has caused a more severe performance degradation than expected.
Switching off SSL encryption is a way to work around this issue. Here is how it is done:

1. Open the converter-worker.xml configuration file. It is located in "%ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone" folder for Windows Vista or newer or in "%ALLUSERSPROFILE%\Application Data\VMware\VMware vCenter Converter Standalone" for older Windows versions.
2. Set the key Config/nfc/useSsl to false and save the configuration file.
3. Restart "VMware vCenter Converter Standalone Worker" service.

I.e. it should look like:

    ...    <nfc>       <readTimeoutMs>120000</readTimeoutMs>       <useSsl>false</useSsl>    ...

How can I create as a VMWare Converter Boot CD ISO image. I need convert P2V my exchange server 2003.

Thank.

Verify that the converter server and the running source machines have a network access to the source and destination esx hosts.

Source is 3.0.2, dest is Dell preinstall 6.5 7388607. (single host on each side)

Have tried both remote and local converter installs on virtual servers. Both fail with the same error. Tried host to host (no vCenter,) then installed a vCenter to try the thumbprint fix, no change. Installed an esx5 host (vm) running on the 6.5 box and it works fine. Tried to v2v using 5.5, 6, and 6.2, with and without ssl (worker and server), from 5 to 6.5 with the same error.

Attached are logs. I saw the reservation message but no reservations exist.

Hi all,

This ones got me a little stumped, hoping someone has some more experience.

Source windows 2012 64bit (fresh deployment, test server for newbies in team)

Converter version 6

ESX 5.5

I start conversion and fails at 3%~ with error.

BlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning of volume \WindowsBitmapDriverVolumeId=[93-DD-5B-0B-00-00-10-00-00-00-00-00]. Error: 37409 (type: 1, code:2338)'

In worker logs all i can see is after the Worker InitialSyncFullCloneTask updates, state: 4, percentage: 3, xfer rate (Bps): 47285248 rows is as follows, no other errors - it just ends....

2015-11-08T02:16:48.945-06:00 info vmware-converter-worker[07764] [Originator@6876 sub=task-7] TargetVmManagerImpl::DeleteVM

2015-11-08T02:16:48.945-06:00 info vmware-converter-worker[07764] [Originator@6876 sub=task-7] Reusing existing VIM connection to 10.27.132.228

2015-11-08T02:16:48.976-06:00 info vmware-converter-worker[07764] [Originator@6876 sub=task-7] Destroying vim.VirtualMachine:83 on 10.27.132.228

2015-11-08T02:16:49.241-06:00 info vmware-converter-worker[07764] [Originator@6876 sub=task-7] WorkerConvertTask: Generating Agent Task bundle for task with id="task-1".

2015-11-08T02:17:26.916-06:00 info vmware-converter-worker[07764] [Originator@6876 sub=task-7] WorkerConvertTask: Retrieving agent task log bundle to "C:\Windows\TEMP\vmware-temp\vmware-SYSTEM\agentTask-task-1-vzohlwml.zip".

2015-11-08T02:17:26.931-06:00 info vmware-converter-worker[07764] [Originator@6876 sub=task-7] WorkerConvertTask: Bundle successfully retrieved to "C:\Windows\TEMP\vmware-temp\vmware-SYSTEM\agentTask-task-1-vzohlwml.zip".

2015-11-08T02:17:26.931-06:00 error vmware-converter-worker[07764] [Originator@6876 sub=Default] Task failed:

The only clue i can give thus far is that i received an ADMIN$ error when connecting initially, resolved by changing "Turn on network discovery" to on.

There are no other errors in the worker log to give any clues, so far i have tried the following

EDIT: Checked the agent log, found the following.

Will review: VMware KB: Troubleshooting issues when vCenter Converter fails during conversion

Will review 2: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2018582

2015-11-08T02:16:48.250-06:00 warning vmware-converter-agent[06348] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcNetTcpRead: bRead: -1

2015-11-08T02:16:48.250-06:00 warning vmware-converter-agent[06348] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcNet_Recv: requested 264, recevied only 0 bytes

2015-11-08T02:16:48.250-06:00 warning vmware-converter-agent[06348] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcGetMessage: recv failed:

2015-11-08T02:16:48.250-06:00 warning vmware-converter-agent[06348] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcFssrvr_IO: failed to receive io reply

2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06348] [Originator@6876 sub=Default] Sysimgbase_DiskLib_Write failed with 'NBD_ERR_NETWORK_CONNECT' (error code:2338)

2015-11-08T02:16:48.250-06:00 error vmware-converter-agent[06348] [Originator@6876 sub=task-1] TargetVolumeWriter::WriteToVolume(): Error (type: 1, code: 2338) writing 655360 bytes to the destination volume at offset 0x0000000037894000

2015-11-08T02:16:48.250-06:00 error vmware-converter-agent[06348] [Originator@6876 sub=task-1] Converter::BackgroundWriter::WriteToVolume: Write failed with error 37409.

2015-11-08T02:16:48.250-06:00 error vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::QueueItem: CircularBuffer AddItem error, destroy workItem!

2015-11-08T02:16:48.250-06:00 error vmware-converter-agent[06048] [Originator@6876 sub=task-1] BlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning of volume \WindowsBitmapDriverVolumeId=[93-DD-5B-0B-00-00-10-00-00-00-00-00]. Error: 37409 (type: 1, code: 2338)

2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06348] [Originator@6876 sub=task-1] BackgroundWriter::ThreadFunc: Broadcasting "ThreadDone" condition.

2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06348] [Originator@6876 sub=ThreadPool] Thread delisted

2015-11-08T02:16:48.250-06:00 error vmware-converter-agent[06048] [Originator@6876 sub=task-1] BlockLevelVolumeCloneMgr::CloneVolume: failed with exception BlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning of volume \WindowsBitmapDriverVolumeId=[93-DD-5B-0B-00-00-10-00-00-00-00-00]. Error: 37409 (type: 1, code: 2338)

2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions

2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions

2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions

2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions

2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions

2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions

2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions

2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions

2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions

2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions

2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions

2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions

2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions

2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions

2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions

2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions

2015-11-08T02:16:48.250-06:00 error vmware-converter-agent[06048] [Originator@6876 sub=task-1] ScopedBackgroundWriter::~ScopedBackgroundWriter: Error in ReleaseBackgroundWriter 37409.

2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] [StreamCacheWriter] - TotalZeros : 0, TotalWrites : 1331

-->

2015-11-08T02:16:48.250-06:00 error vmware-converter-agent[06048] [Originator@6876 sub=task-1] SingleVolumeCloneTask:DoRun: Volume cloning failed with clone error BlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning of volume \WindowsBitmapDriverVolumeId=[93-DD-5B-0B-00-00-10-00-00-00-00-00]. Error: 37409 (type: 1, code: 2338)

2015-11-08T02:16:48.250-06:00 error vmware-converter-agent[06048] [Originator@6876 sub=task-1] TaskImpl has failed with MethodFault::Exception: converter.fault.CloneFault

2015-11-08T02:16:48.250-06:00 info vmware-converter-agent[06048] [Originator@6876 sub=task-1] SingleVolumeCloneTask [source computer (unknown name)]-\WindowsBitmapDriverVolumeId=[93-DD-5B-0B-00-00-10-00-00-00-00-00] --> [target VM (unknown name)]-3)=-;5;00000010000000000 updates, state: 4, percentage: 3, xfer rate (Bps): 47286047

2015-11-08T02:16:48.750-06:00 info vmware-converter-agent[04340] [Originator@6876 sub=task-1] CompositeTask canceling #2 subtasks

2015-11-08T02:16:48.750-06:00 info vmware-converter-agent[04340] [Originator@6876 sub=task-1] TaskImpl issuing Cancel command

2015-11-08T02:16:48.750-06:00 info vmware-converter-agent[04340] [Originator@6876 sub=task-1] SingleVolumeCloneTask [source computer (unknown name)]-\WindowsBitmapDriverVolumeId=[93-DD-5B-0B-00-00-10-00-00-00-00-00] --> [target VM (unknown name)]-3)=-;5;00000010000000000 updates, state: 4, percentage: 3, xfer rate (Bps): 47286047

2015-11-08T02:16:48.750-06:00 info vmware-converter-agent[04340] [Originator@6876 sub=task-1] TaskImpl issuing Cancel command

2015-11-08T02:16:48.750-06:00 info vmware-converter-agent[04340] [Originator@6876 sub=task-1] SingleVolumeCloneTask [source computer (unknown name)]-\WindowsBitmapDriverVolumeId=[09-7B-3F-8E-00-00-10-00-00-00-00-00] --> [target VM (unknown name)]-90;7?3>(0000010000000000 updates, state: 0, percentage: 0, xfer rate (Bps): <unknown>

2015-11-08T02:16:48.750-06:00 warning vmware-converter-agent[04340] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcNetTcpWrite: bWritten: -1

2015-11-08T02:16:48.750-06:00 warning vmware-converter-agent[04340] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcSendMessage: send failed: NFC_NETWORK_ERROR

2015-11-08T02:16:48.750-06:00 warning vmware-converter-agent[04340] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcFssrvr_Close: failed to send close message

2015-11-08T02:16:48.750-06:00 warning vmware-converter-agent[04340] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcNetTcpWrite: bWritten: -1

2015-11-08T02:16:48.750-06:00 warning vmware-converter-agent[04340] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcSendMessage: send failed: NFC_NETWORK_ERROR

2015-11-08T02:16:48.750-06:00 info vmware-converter-agent[04340] [Originator@6876 sub=task-1] VolumeBasedCloneTask source computer (unknown name) --> target VM (unknown name) updates, state: 4, percentage: 3, xfer rate (Bps): 47286047

2015-11-08T02:16:48.750-06:00 info vmware-converter-agent[04340] [Originator@6876 sub=task-1] VolumeBasedCloneTask failed

2015-11-08T02:16:48.750-06:00 info vmware-converter-agent[04340] [Originator@6876 sub=task-1] CloneTask updates, state: 4, percentage: 3, xfer rate (Bps): 47286047

2015-11-08T02:16:48.750-06:00 info vmware-converter-agent[04340] [Originator@6876 sub=task-1] CloneTask failed

2015-11-08T02:16:48.750-06:00 error vmware-converter-agent[04340] [Originator@6876 sub=Default] Task failed:

Actions

• Rerun job a couple more times - failed
• Convert only C:\ - failed
• Run Check disk /R on C:\ - failed

Points to consider.

• Next step would be to install converter locally but i want to avoid this for now.
• No workarounds to be deployed, i.e. use acronis - must be able to proceed with converter alone
• Normally a checkdisk resolves this issue for me.

Question: What other things can cause the following errorBlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning of volume \WindowsBitmapDriverVolumeId=[93-DD-5B-0B-00-00-10-00-00-00-00-00]. Error: 37409 (type: 1, code:2338)'

Community, be greeted.

A short backstory. I recently converter 120+ VM's from ESXi 4.1 (running clustered with vCenter) to ESXi 6.5 standalone host (standard license).

These conversions were made with vmware converter and all went by with flying colors. Now the issue is that now I'm totally unable to convert anything from the new 6.5 host. This is a must-need-feature as our users constantly move these VM's from the host to their player/workstation infrastructure.

1) First error is with the converter. Some VM's convert okay but most of them give the "Not enough permissions" at 98%

2) Second error is with the export function in ESXi 6.5 (okay, a bit off-topic). Export goes pretty far but eventually gives network/time-out error.

3) Third error is with the newest converter 6.2. This version gives me the "cannot lock disks" error straight up. It doesn't matter, whether I'm using a NFS share or trying to convert to my local disk.

So far, it might have something to do with the ctb being enabled. Permissions should be okay as I'm having the issues with full root permissions.

Any clues to any of the issues mentioned above? All help is highly appreciated. Currently the only option for moving the VM's is through sftp and it doesn't sound like a plan for tomorrow

Cheers,

Pekka

Hello,

I am testing the converter standalone with some VMs after some changes in my configuration.

I have a two hosts cluster with HA and DRS and some simple VMs inside (all Ubuntu, 20 to 40GB disks, 1 to 4 vcpus, 2 to 4GB RAM).

I power off one of them, put it through the converter to a Workstation directory on the PC where the converter is installed.

I now want to get it back, I use the converter from Workstation to VMware infrastructure virtual machine and I get the message : "a component of the virtual machine is not accessible on the host".

All the same with other VMs.

I don't understand what is happening. Some blogs write about a CD ROM still connected to an ISO but it is not the case here.

Another gave a possible tip towards the fact it is a cluster but VMware does not confirm it when I look for some KB or official explanation. The cluster and some pool resources are the only changes made since the last time I converted a VM in the same way.

Is someone able to explain it, please ?

Hi!

SLES 11 on VMware Virtual Platform. Trying to convert it to ESX 5.1. First tried to use Converter 5.5, but … got error “FAILED: A general system error occurred: Network error.
Host ... key can't be retrieved. (return code 2)”. On SLES nothing added to hosts.allow nor hosts.deny. SSHD is running I’m able to use NX for remote connection to this server. Well, thought maybe something with RSA key and Converter 5.5 (find out via Google). Tried Converter 4.3, but … “unable to clone the volume mounted on ‘/boot’”. Here I am! Any ideas? Probably I’m doing something wrong.

More thanks, Alar.

Hi All,

i am in the midst of p-v and have some issue obtaining hw info. I belive its realted to converter version.

I am looking for version 5.1 everywhere and unable to get one.

If anyone have converter standalone 5.1 version , Kindly share. (maybe dropbox?)

Thanks.

regards,

Max