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

Re: Error when converting physical Linux Error Failed to find matching disk device for VMODL Param Disk #0

April 16, 2015, 5:11 am
$
0
0

Converter 5.5 does not support RHEL 7. I suppose the following chain of events has ensued:

The parser has chosen RedHat (not enterprise) as default OS. Then it has decided to use BusLogic as SCSI controller. BusLogic OTOH is not supported anymore by RHEL 7. That at the end has caused the helper not to see the disk.

 

You may try to lure Converter believing it is RHEL 6 by editing the etc/*-release file on the source and try again. Keep in mind reconfiguration will fail(!) and XFS will not be preserved (I think the volumes will be converted to ext3 but do not guarantee).

Or wait for the next Converter.

 

Regards,

Plamen

↧
Search

Re: Getting "Invalid Fault" error when attempting to perform V2V conversion with Converter Standalone 5.5.3

April 16, 2015, 9:36 am
$
0
0

Is there a way for me to PM to you, so that I don't potentially expose any of our internal details?

↧
↧

Re: Getting "Invalid Fault" error when attempting to perform V2V conversion with Converter Standalone 5.5.3

April 16, 2015, 3:13 pm
$
0
0

The target ESXi host is registered with a vCenter server (running as a virtual machine on the target host).   Does the target ESXi host need to be disconnected from vCenter in order to use the standalone converter?

↧

Re: Getting "Invalid Fault" error when attempting to perform V2V conversion with Converter Standalone 5.5.3

April 17, 2015, 1:27 am
↧

Re: Getting "Invalid Fault" error when attempting to perform V2V conversion with Converter Standalone 5.5.3

April 17, 2015, 1:30 am
$
0
0

No, this is not needed, moreover after VC version 5.x (not sure exactly) if the ESX host is managed from the VC you can't add a VM to the ESX directly but from the VC only.

HTH

↧
↧

VM Fails to boot 0x000007b

April 17, 2015, 9:08 am
$
0
0

I had a physical Windows Server 2003 machine fail that needed to be recovered. I was able to pull the drives out and image them with Acronis. I then was able to convert the image into a VMDK and load it on a ESXi 5.5 host. I created a new VM and attached the vmdk. Now when I try to boot the VM as soon as I see the Server 2003 splash screen the machine crashes with a 0x000007b Blue Screen. I'm assuming it has something to do with SCSI drivers. I can attach the vmdk to another VM and access it. I've tried using a BartPE boot disk but I can't access the drive when I do that. I need to get the VM working since it has a lot of archived data on it. I'm hoping someone can point me in the right direction.

↧

Re: VM Fails to boot 0x000007b

April 17, 2015, 9:28 am
$
0
0

Since you suspect the SCSI drivers - did you check what SCSI controller the VM is using? LSI Logic should be default for Windows 2k3. If it is not, you may try to edit the VM and change it.

You may also try reconfiguring it again with converter.

↧

Re: VM Fails to boot 0x000007b

April 17, 2015, 9:40 am
$
0
0

I tried changing the SCSI controller type but none of them work. I didn't actually use converter to create the VMDK, I had to use another tool. Acronis was only able to convert it's image to a VHD, then I had to convert the VHD to a VMDK. Will converter take an existing VMDK and run it through the process again?

↧
Search

Re: VM Fails to boot 0x000007b

April 17, 2015, 11:07 am
$
0
0

As mentioned by Plamen you may try running "Configure Machine" against the virtual machine, to see whether this injects the required drivers. Make sure the Windows 2003 VM is configured with the default "LSI Logic Parallel" controller.

 

André

↧
↧

Re: VM Fails to boot 0x000007b

April 17, 2015, 11:42 am
$
0
0

Thank you, that seems to have resolved the issue. I did not know that converter had this ability.

↧

Re: Getting "Invalid Fault" error when attempting to perform V2V conversion with Converter Standalone 5.5.3

April 17, 2015, 12:35 pm
$
0
0

I installed the converter on a 100% clean Windows 8 workstation and attempted to run the migration and received the exact same 'Invalid Fault error'.   However, this time I noticed the following lines in the converter-worker log:

 

2015-04-17T11:55:08.779-07:00 [04088 info 'Default'] TargetVmManagerImpl::CreateVM: Creating the target VM.

2015-04-17T11:55:08.779-07:00 [04088 info 'Default'] Reusing existing VIM connection to vcenter1-sj1.quantumscape.com

2015-04-17T11:55:08.779-07:00 [04088 info 'Default'] ComputeResource for vim.HostSystem:host-43 is vim.ComputeResource:domain-s41

2015-04-17T11:55:08.779-07:00 [04088 info 'Default'] ResourcePool for vim.ComputeResource:domain-s41 is vim.ResourcePool:resgroup-42

2015-04-17T11:55:08.779-07:00 [04088 info 'Default'] Creating VM OpsCenter-sj1 in folder vim.Folder:group-v22 on host vim.HostSystem:host-43 and resource pool vim.ResourcePool:resgroup-42 (isVirtualApp = false)...

2015-04-17T11:55:11.248-07:00 [04088 error 'Default'] CreateVm task failed: The operation is not allowed in the current state.

2015-04-17T11:55:11.248-07:00 [04088 error 'Default'] TargetVmManagerImpl::CreateVM: Vm creation failed with fault vim.fault.InvalidState

2015-04-17T11:55:11.248-07:00 [04088 info 'Default'] Scheduled timer canceled, StopKeepAlive succeeds

2015-04-17T11:55:11.263-07:00 [04088 info 'vmomi.soapStub[14]'] Resetting stub adapter for server <cs p:0168a5b8, TCP:vcenter1-sj1.mycompany.com:443> : Closed

2015-04-17T11:55:11.263-07:00 [04088 error 'Ufa'] Method converter.worker.ConverterWorker.createVM threw undeclared fault of type vim.fault.InvalidState

2015-04-17T11:56:02.627-07:00 [05272 info 'Default'] [Converter.Worker.DiagnosticManagerImpl] Generating LogBundle.

 

So it almost looks like the converter isn’t able to create the new VM on the target ESXi host, but I’m not sure why.  This is a brand new target host with nothing running on it except a clean build of ESXi 5.5U2, and a single VM running the latest version of vCenter 5.5.   I’ve created a new LUN from my storage and mounted it to the iSCSi storage adapter for the target VM that I want to migrate and everything there looks like it's prepped.

↧

Re: Getting "Invalid Fault" error when attempting to perform V2V conversion with Converter Standalone 5.5.3

April 17, 2015, 1:50 pm
$
0
0

So the issue was with the vCenter server (the Linux appliance version, which is a little disconcerning) not being in a 'ready state' to allow for migrations.

 

I restarted the vCenter server and everything started working as expected, immediately.

↧

P2V conversion stop at 97 %

April 20, 2015, 3:32 am
$
0
0

I'm trying to P2V a Windows 2003 Server into my vCenter 5.5 enviroment.

 

Using Converter Standalone version 5.1.0

 

Conversion stop at 97 % and error show :

 

FAILED: A general system error occured : platform-specific error 2

 

log highlight: 6:08:10 PM : An error occurred during configuration.

 

Work diagnostic attached.

 

Appreciate anyone can help.

 

Thanks.

↧
↧

Re: P2V conversion stop at 97 %

April 20, 2015, 5:32 am
$
0
0

The converter-agent.log should be more descriptive about reason to fail....from the other hand - try to remove  /3GB switch from boot.ini and run the reconfiguration again.

HTH

↧

Re: P2V conversion stop at 97 %

April 20, 2015, 5:54 am
$
0
0

Hi Poceh,

 

I am currently back from customer site and not able to check now , will check it tomorrow morning and revert.

 

When i export the log file , there were only few files and i cant find agent file that you mention:

 

1) converter-gui-xxx.log.gz

2) vmware-converter-server-1.log

3) worker-diagnostics-task-1-hys.zip

 

Please let me know which file you would like to review so i can attach.

 

I am using local installation method for my p2v conversion.

 

Thanks.

↧
Search

Re: P2V conversion stop at 97 %

April 20, 2015, 6:39 am
$
0
0

worker-diagnostics-task-1-hys.zip should contain all diagnostic files, however if you convert 'this local machine' the agent's files are not interesting, only for remote connections, and they are placed on source computer i.e. where agent runs.

I see some strange things in log but didn't say what's wrong...

Could you repeat the conversion with latest Converter 5.5? (to convert local machine you'll need to run the Converter UI 'as administrator')


↧

Re: P2V conversion stop at 97 %

April 20, 2015, 11:43 pm
$
0
0

Hi Poceh,

 

I have refer to KB (1030145) remove /3gb switch , it require to restart the Physical Machine which i am not able to do right now , do you have any idea to disable it without impact to my Physical Server?

 

I have tried uninstall the 5.1 Vcenter converter , and reinstall 5.5 version , it show error 29142, could not start service vstor2 mntapi 2.0 driver(shared).

 

Thanks.

↧
↧

Re: P2V conversion stop at 97 %

April 21, 2015, 1:04 am
$
0
0

I've never tested but IMO the /3G switch could be removed from boot.ini just to mislead the conversion process.

About deinstallation/installation you need to restart the computer...

HTH

↧

Re: P2V conversion stop at 97 %

April 21, 2015, 8:21 am
$
0
0

Is there any un-provisioned space left on the physical disks? if yes create them as a new volume and try the P2V process.

↧

Using StandAlone Converter with SSH Tunnel and keys, no passwords

April 21, 2015, 8:59 am
$
0
0

I'm trying to convert a remote centos 6.5 box that I access via putty with ssh keys,  no password.    I created the local ssh tunnels but the converter requires a username and password.    The linux box is setup for ssh keys only,  no passwords.   Is there a work around for this?

↧
Viewing all 8478 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>