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

Re: VMware vCenter Converter fails at 1%: 'The operation experienced a network error'

August 18, 2015, 5:54 am
$
0
0

Hi theire,

 

So other question.  you did Installed the Converter as a Server and connecting to the Powered on Machine ? or you're installing the Converter directly to the Hyper-V VM as a Client?

 

as if you're not using the Converter inside the Hyper-V directly then you need additional Ports open from the Converter Server to the Hyper-V VM

 

Converter Standalone server to powered on source machine TCP - 445, 139, 9089 UDP - 137, 138    (Windows).

 

Most Problems in the Past i had with the Converter Server Config. if was most worst because of Firewalls etc,.... i installed Client on the  VM and connected to the vCenter/Esxi (but i had not much vm's to migrate last time).

 

thx

 

Max

↧
Search

Re: VMware vCenter Converter fails at 1%: 'The operation experienced a network error'

August 18, 2015, 5:55 am
$
0
0

and you need to change the host file on the Windows VM

↧
↧

Re: VMware vCenter Converter fails at 1%: 'The operation experienced a network error'

August 18, 2015, 5:57 am
↧

Re: VMware vCenter Converter fails at 1%: 'The operation experienced a network error'

August 18, 2015, 6:03 am
$
0
0

Madmax01

The Converter is running on the HyperV-Host, so im trying to convert a vm of the local hyperv to an remote esxi.

How? what do i have to put into the host files?

 

POCEH

i attached them

↧

Re: VMware vCenter Converter fails at 1%: 'The operation experienced a network error'

August 18, 2015, 6:22 am
$
0
0

Seems you want to do conversion with powered-off machine (V2V), is this correct?

In this case if a virtual disk is expandable i.e. its total capacity is times bigger that used capacity - this could be a problem.

To avoid such situation try to convert VM as powered on machine, just ensure guest os to see ESX at port 902.

HTH

↧
↧

Re: VMware vCenter Converter fails at 1%: 'The operation experienced a network error'

August 18, 2015, 6:29 am
$
0
0

hi poceh,

the used virtual disk is a static / Thick Provision disk with 50gb. Its a test vm. EDIT: The destination disk has 350GB free and i tried a second one with 1800gb free.

Yes im trying to convert a shutted down windows server 2008r2 vm to the ESXi (v2v).


I got the root credentials for the esx server, but the converter says: "The access to the host resource settings is restricted to the server 'xxx' that is managing the host. Use the management server as a destination.

 

Madmax01 wrote something about to change the hosts file. where can i find informations about this?

  • 10.15.3.201 to 195.218.58.71 have to go over the Gateway 10.15.3.206
  • reverse way is 195.218.58.65
↧

Re: VMware vCenter Converter fails at 1%: 'The operation experienced a network error'

August 18, 2015, 7:04 am
$
0
0

Hi theire,

 

So here you have the Infos .

 

VMware KB: Troubleshooting checklist for VMware Converter

 

To be honest - i didn't checked the 6.0 Converter. But with earlier versions i had the Problem that also with IP communication he blamed somewhere that Names not reachable.  So i configued the vcenter + esxi inside the local hosts file of the Source Machine

 

Best regards

 

max

↧

Re: VMware vCenter Converter fails at 1%: 'The operation experienced a network error'

August 18, 2015, 7:14 am
↧
Search

Re: VMware vCenter Converter fails at 1%: 'The operation experienced a network error'

August 18, 2015, 7:42 am
$
0
0

The probable problem could be with source disk, not with destination one... If disk is 50GB but it's not extended to max capacity but occupied something like 15GB - this is a problem - shrink the disk size, ex exend it to maximum size.

 

About "The access to the host resource is restricted..." you need to point as target the VC server which manage the ESX.

 

About hosts file - this helps when you access by name destination VC and/or ESX which are not visible in your source  machine, to avoid this use the IP addresses.

The location of the file is c:\windows\system32\drivers\etc\hosts and adding the name-to-ip resolution is very simple, just edit it with notepad (running from elevated administrator).

 

HTH

↧
↧

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

August 20, 2015, 4:23 am
$
0
0

Little late but i had the exact same problem.

Tried all other solutions with host.allow, disable firewall etc, etc

 

My solution was to disable IPv6 in converter helper and set IP address to static.

↧

RHEL DNS/DHCP server P2V conversion

August 20, 2015, 7:52 am
$
0
0


I have an HP server with RHEL 5.10 OS running VitalQIP DNS/DHCP application.  Will I need to reintall the VitalQIP and BIND applications on the VM or will the converter migrate application as well?

↧

Re: Standalone converter failed to connect to a local server

August 20, 2015, 3:14 pm
$
0
0

I ran into this as well using a domain account. While still an administrator account it was giving me the "failed to impersonate user" error. After digging around for a second i realized I had set custom DNS for testing and forgot to switch my DNS back to my DC so the application was unable to authenticate my Domain user account against the proper DC. Switched my DNS back to default and everything worked just fine.

↧

Re: RHEL DNS/DHCP server P2V conversion

August 20, 2015, 5:23 pm
$
0
0

If you do a P2V using VMware vCenter Converter you will not need reinstall the applications on destination VM, everything will be copied during the P2V process, you will need only shutdown the old physical server before start the new virtual machine and set the same IP address for the virtual machine.

↧
↧

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

August 21, 2015, 10:34 am
$
0
0

Hello,

I'm trying to convert physical Ubuntu 14.04 server into virtual machine using VMWare vCenter Coverter Standalone 6.0.0

'Convert machine' wizzard fails on setting Source with 'Unable to query the live linux machine'.

 

 

converter logs:

.....

2015-08-21T12:45:10.595-04:00 info converter-gui[03628] [Originator@6876 sub=ConverterSession] Converter::Client::Gui::Common::DiagnosticDataProvider::SetLastKnownSource - Setting last known source:

--> (converter.ComputerSpec) {

-->    location = (converter.ComputerSpec.LiveComputerLocation) {

-->       hostname = "..........",

-->       port = 2222,

-->       username = "root",

-->       password = (not shown),

-->       osType = "linuxOs",

-->       verifyPeer = <unset>,

-->       sslThumbprint = <unset>

-->    }

--> }

2015-08-21T12:45:10.627-04:00 error converter-gui[07172] [Originator@6876 sub=wizardController] Cannot query source HW info: converter.fault.SysinfoQueryLinuxFault

....

 

 

 

 

authentication logs from source Ubuntu 14.04 server :

 

...

Aug 21 17:01:23 VidyoPlatform getty[18787]: /dev/ttyS0: not a character device

Aug 21 17:01:33 VidyoPlatform sshd[18789]: fatal: no matching mac found: client hmac-sha1,hmac-sha1-96,hmac-md5 server hmac-sha2-256,hmac-sha2-512 [preauth]

Aug 21 17:01:33 VidyoPlatform getty[18791]: /dev/ttyS0: not a character device

 

...

 

vmware-sysinfo-lin64 log:

 

root@VidyoPlatform:/tmp/vmware/vmware# ./vmware-sysinfo-lin64.sh

sh: 1: /usr/sbin/grub2-install: not found

sh: 1: /usr/sbin/grub-install.unsupported: not found

<?xml version="1.0" encoding="UTF-8"?>

<sysinfo>

<storage>

  <volume mountPoint="/" blockSizeInBytes="4096" capacityInBlocks="122080257" blocksFree="49226010" blocksUsed="72854247" devicePath="/dev/sda3" fileSystemType="btrfs" isBootVolume="true" label=""/>

  <volume mountPoint="/boot/efi" blockSizeInBytes="2048" capacityInBlocks="32183" blocksFree="32023" blocksUsed="160" devicePath="/dev/sda2" fileSystemType="vfat" isBootVolume="false" label="VidyoEFI"/>

  <volume mountPoint="/var/log" blockSizeInBytes="4096" capacityInBlocks="122080257" blocksFree="49226010" blocksUsed="72854247" devicePath="/dev/sda3" fileSystemType="btrfs" isBootVolume="false" label=""/>

  <volume mountPoint="/opt/vidyo" blockSizeInBytes="4096" capacityInBlocks="122080257" blocksFree="49226010" blocksUsed="72854247" devicePath="/dev/sda3" fileSystemType="btrfs" isBootVolume="false" label=""/>

  <volume mountPoint="/opt/vidyo/static" blockSizeInBytes="4096" capacityInBlocks="122080257" blocksFree="49226010" blocksUsed="72854247" devicePath="/dev/sda3" fileSystemType="btrfs" isBootVolume="false" label=""/>

  <volume mountPoint="/opt/vidyo/app" blockSizeInBytes="4096" capacityInBlocks="122080257" blocksFree="49226010" blocksUsed="72854247" devicePath="/dev/sda3" fileSystemType="btrfs" isBootVolume="false" label=""/>

  <volume mountPoint="/opt/vidyo/conf" blockSizeInBytes="4096" capacityInBlocks="122080257" blocksFree="49226010" blocksUsed="72854247" devicePath="/dev/sda3" fileSystemType="btrfs" isBootVolume="false" label=""/>

  <volume mountPoint="/opt/vidyo/data" blockSizeInBytes="4096" capacityInBlocks="122080257" blocksFree="49226010" blocksUsed="72854247" devicePath="/dev/sda3" fileSystemType="btrfs" isBootVolume="false" label=""/>

  <volume mountPoint="/opt/vidyo/log" blockSizeInBytes="4096" capacityInBlocks="122080257" blocksFree="49226010" blocksUsed="72854247" devicePath="/dev/sda3" fileSystemType="btrfs" isBootVolume="false" label=""/>

  <disk type="gpt" controllerType="sata" bus="0" deviceId="0" capacityInSectors="976773168">

   <device path="/dev/sda" major="8" minor="0"/>

   <hwGeometry cylinders="60801" heads="255" sectors="63"/>

   <biosGeometry cylinders="60801" heads="255" sectors="63"/>

   <partition number="1" type="primary" isActive="false" fileSystemType="">

    <device path="/dev/sda1" major="8" minor="1"/>

    <lba start="34" length="2014" end="2047"/>

   </partition>

   <partition number="2" type="primary" isActive="true" fileSystemType="fat16">

    <device path="/dev/sda2" major="8" minor="2"/>

    <lba start="2048" length="129024" end="131071"/>

   </partition>

   <partition number="3" type="primary" isActive="false" fileSystemType="">

    <device path="/dev/sda3" major="8" minor="3"/>

    <lba start="131072" length="976642063" end="976773134"/>

   </partition>

  </disk>

</storage>

<network>

  <interface label="eth0" nicId="D4:AE:52:CF:59:93" status="up">

   <ip address="192.168...." mask="255.255.255.0"/>

  </interface>

  <interface label="eth1" nicId="D4:AE:52:CF:59:94" status="up"/>

</network>

<operatingSystem>

  <hostname>VidyoPlatform</hostname>

  <distribution name="ubuntu" version="14.04"/>

  <kernel release="3.13.0-36-generic" is64bit="true" SMP="false"/>

  <dracut></dracut>

</operatingSystem>

<hardwareInfo>

  <firmwareType>efi</firmwareType>

  <efiCurrentBootEntry>EFI Fixed Disk Boot Device 1     ACPI(a0341d0,0)PCI(1f,2)03120a00000000000000HD(2,800,1f800,38c22baa-d925-4f92-9d76-582ae6923cc1)</efiCurrentBootEntry>

  <cpuCount>8</cpuCount>

  <coresCount id="0">8</coresCount>

  <memoryInKb>8192000</memoryInKb>

</hardwareInfo>

<bootLoader>

  <type>grub2</type>

  <configFile>/boot/grub/grub.cfg</configFile>

  <devicemap/>

</bootLoader>

</sysinfo>

 

 

 

all items from http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1009153

checked and seem to be fine.

 

Thanks for help,

 

Eugene51

↧

While converting a vmc file VMWare Converter: (A file I/O error occurred while accesssing ". )

August 22, 2015, 7:59 am
$
0
0

I have an old vmc file that fine for years with Microsofts VirtualPC. I just converted to Windows 10 and I found out that vmc are no longer supported.

I was hoping VMware had something to convert/run vmcs, so I downloaded VMWare Converter and pointed the wizard to my vmc file and within a few seconds I get a "A file I/O error occurred while accesssing ". error.  The file is a local file and I'm running this in Windows 10 64-bit. I tried to convert some previous backup vmc files and they all give the same error at the same point. I don't think the vmc files are corrupted as they were working a few weeks ago.

↧
Search

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

August 22, 2015, 9:48 am
$
0
0

Hi

 

i have convert a physical linux machine to virtual but know i run df -h command in linux to display filesystems  my virtual machine now work with no problem but i want to know why my filesystem size has been changed ? how can i convert physical to virtual without change filesystem size? i have attached both pics (before and after) change.

 

 

Best regards

Babak

↧

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

August 22, 2015, 9:55 am
$
0
0

Based on the pictures, seems like only the device of boot partition has changed and this is the expected behavior, since on virtual machine there is no more a HP Smart Array controller present on physical machine.

↧
↧

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

August 22, 2015, 10:26 am
$
0
0

thanks

 

but most of file system size has been changed such as : u01   , u02  , u03   , /tmp and ..... 

why ?

↧

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

August 22, 2015, 8:53 pm
$
0
0

can i convert without change in partition size?

↧

Re: While converting a vmc file VMWare Converter: (A file I/O error occurred while accesssing ". )

August 23, 2015, 3:52 am
$
0
0

Have you tried this ?

 

You can import a Windows Virtual PC virtual machine and run it in Workstation. Workstation converts the virtual machine from Virtual PC (.vmc) format to VMware runtime (.vmx) format. This feature is supported only on Windows host systems.

Prerequisites

Download and install the Virtual PC virtual machine on the Windows host system.

Procedure

1

 

In Workstation, select File> Open.

If you have never imported a third-party virtual machine or virtualized a physical machine in Workstation, Workstation installs VMware vCenter Converter Standalone. After the installation is finished, you must restart the import.

2

Browse to the  .vmc file and click Open.

3

Type a name for the virtual machine, type or browse to the directory for the virtual machine files, and click Import.

After Workstation successfully imports the Virtual PC virtual machine, the virtual machine appears in the virtual machine library.

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