Now it's time to start conversion again 
HTH
↧
Re: Converter 5.5.3, ESXI 6.0, P2V. "An error occurred during the conversion: 'converter.fault.FileIOFault'"
↧
Issue converting Ubuntu 8.04.4 LTS machine
I am running into an issue while trying to convert an Ubuntu Linux VM. After clicking the finish button on the summary screen I just get an error that says "Unable to create virtual machine 'iceman-test'"
I checked the worker log and found the following 2 errors:
2015-04-30T11:26:23.793-04:00 [04472 error 'Default'] VmTransformerImpl::SeparateBootDisk: Unable to find VirtualDisk for diskId=fake-disk-from-vg(system)
2015-04-30T11:26:23.794-04:00 [04472 error 'Default'] TargetVmManagerImpl::CreateVM: Vm creation failed with error Invalid argument : VmTransformerImpl::SeparateBootDisk: Unable to find VirtualDisk for an active volume
I found another article here suggesting the issue might be with swap, so, I tried to work around that by disabling it to recreate it later but that did not work.
Attached is the full worker log.
↧
↧
Converter keeps trying to install the agent
Hi
I am trying to P2V a server on a separate subnet but the the following box just keeps popping up:
HOWEVER - when I go to the server that I am trying to P2V, the Converter agent service is installed and running. Any ideas?
↧
Re: Converter keeps trying to install the agent
Could you upload log bundle?
Otherwise you can install the agent on your source machine manually and then do the conversion.
HTH
↧
Re: Converter 5.5.3, ESXI 6.0, P2V. "An error occurred during the conversion: 'converter.fault.FileIOFault'"
"The Converter failed again but this time at 21%, same error."
Second one failed earlier than the first.
-Mike
↧
↧
Re: Converter keeps trying to install the agent
Hi AndyCorbett,
Perhaps I got this wrong, but the Wizard you see there is asking to uninstall the agent after the import.
What happens when you say yes to the Automatically uninstall the Agent when Import Succeeds.
Failing that I would uninstall the agent and start at a clean state
Kind Regards
@iiToby
↧
Re: Converter keeps trying to install the agent
Right. If I click yes or no, the box disappears, and then pops up again and I never get passed it.
↧
Re: Converter 5.5.3, ESXI 6.0, P2V. "An error occurred during the conversion: 'converter.fault.FileIOFault'"
Hmmm, are you sure you check the right disk?
The other thing - is the IO error is for local disk or for remote disk? In this case the disk scan should be other...
Could you upload log bundle?
↧
Parallels PCS server to VMware vSphere
Parallels PCS server is not listed as a supported host, but I wondered if anyone had been successful in doing a V2V migration from PCS to vSphere 5.*
↧
↧
Re: Issue converting Ubuntu 8.04.4 LTS machine
Hello
It seems the source machine doesn't have a separate '/boot' volume, It is probably a directory in '/'. This is quite strange because '/' is in a logical volume. Only GRUB2 can boot from logical volumes and AFAIK Ubuntu 8 is still with GRUB1.
Converter 5.x can't convert machines with '/boot' in a logical volume. OTOH, although this functionality can be expected to be added in the next version, Ubuntu 8 can't be converted anymore since probably 5.0 (not sure about the exact version, check the release notes).
↧
Re: Converter keeps trying to install the agent
Hello
Converter server attempts to connect to agent on source machine on its port (9089 by default). It prompts you to install in case it couldn't connect to. Since you mention "a separate subnet", perhaps you have connectivity issues. Check the user guide for the ports needed in the firewall configuration.
HTH,
Plamen
↧
Re: Parallels PCS server to VMware vSphere
Hello
I have never tried that but can tell with 99% assurance this won't work. Why so? Converter supports only old versions of third party images which haven't been updated from quite a while. Even in the lucky circumstance PCS uses an understood file format, cloud environments pose additional requirements which won't be met by Converter.
As a workaround, you may try power on the machine and P2V it. Not supported either but worth a try.
HTH
Plamen
↧
Re: Parallels PCS server to VMware vSphere
Hi Shane1973,
This is from the Parallels WebSite
------------------------------------------------------------------------------------------------------------------------------------------------------------
Running Parallels Cloud Server in Virtual Machines
Starting with version 5, you can install Parallels Cloud Server in virtual machines. Doing so may prove useful if you want to evaluate the product but do not have a spare physical server.
To run virtual machines with Parallels Cloud Server 6.0, a physical server must have one of the following architectures:
- Intel with VT-x and EPT,
- AMD with AMD-V and RVI.
Recommended Virtual Machine ConfigurationA virtual machine is best optimized for use with Parallels Cloud Server 6.0 if it has the following configuration:
- CPU: 2 or more virtual CPUs
- RAM: 2 GB or more
- HDD: 40 GB or more on a plain hard disk
Installing Parallels Cloud Server in a virtual machine does not differ from installing it on a standalone server.
Restrictions and PeculiaritiesWhen using Parallels Cloud Server in a virtualized environment, keep in mind the following restrictions and specifics:
- Running Parallels Cloud Server in a virtual machine is intended for evaluation purposes only. You are not recommended to use such installations in production.
- If you change the configuration of a virtual machine where Parallels Cloud Server is installed, you may need to reactivate the product.
- When you start a virtual machine with Parallels Cloud Server, VMware Fusion may warn you that it requires full access to the network traffic. Ignore this message, and proceed with booting the virtual machine.
- To run in a virtualized Parallels Cloud Server environment, a virtual machine must have Parallels Tools installed.
- Virtual machines may run only 32-bit operating systems and have only one CPU.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you are planning on migrating the Parallels PCS I would recommend treating it like a P2V and not a V2V also before you start strip out Parallel Tools, VMware Tools and Parallel Tools have many conflicts that cause issues.
While it doesn't say supported, you can always give it a try and see how you go.
Kind Regards
@iiToby
↧
↧
Re: Parallels PCS server to VMware vSphere
Hello iToby
Sorry for nitpicking, but the text you have marked (Running Parallels Cloud Server in a virtual machine is intended for evaluation purposes only) is not applicable to the case. IIUC the case is to V2V a VM inside PCS, not virtualize the server itself.
Regards,
Plamen
↧
Re: Parallels PCS server to VMware vSphere
Thanks for the input guys.
We're going to start testing today, and try to do a P2V of a guest VM running on the PCS hypervisor.
Doesn't hurt to try and see what happens. We'll be trying to host the converted VM on vSphere 5.1
↧
Re: Parallels PCS server to VMware vSphere
Hi Palmen,
If that is case then you are correct, ignore that section.
Cheers
@iiToby
↧
Re: Converter keeps trying to install the agent
I have the following ports open both ways on the firewall. Am I missing any?
22 | TCP |
137 | UDP |
138 | UDP |
139 | TCP |
443 | TCP |
443 | TCP |
443 | TCP |
22 | TCP |
443, 902 | TCP |
445 | TCP |
9089 | TCP |
↧
↧
P2V from Debian 5.03 Lenny
Hi,
i have a physical server with OS Linux Debian 5.03 "Lenny". I'm trying to virtualize it into an Esxi 5.01 server and i have some problems.
First, i tried a "power on" p2v with vCenter Converter standalone 5.5.2 but the procedure fails at 1%.
Next, i tried a cold p2v with the old 4.1 converter and the procedure goes to 100%. Fine !
When i start the VM after conversion i have a "kernel panic" error, the server won't start.
Before kernel panic i read many errors, like:
mdadm: cannot open device /dev/sda2: No such device or address
mdadm: /dev/sda2 has wrong uuid.
After googling i found this procedure that permit to replace the wrong version of grub bootloader and update the uuid:
For resolving this issue you would need the Debian ISO. Download the latest stable version of Debian ISO and follow the below steps:
- Check the root file system from the source (physical machine) using the command fdisk -l and note the device. (eg: /dev/sda1)
ok !
- Power On the destination VM
- Boot from the Debian iso
- Select 'Rescue Mode' option from the menu
- Choose the option "Reinstall grub bootloader"
ok!
- Give the device which holds the root file system (eg: /dev/sda1)
the procedure on debian disk ask me the locazion and the keyboard type. After that an error occurs:
"The installer cannot find any partitions, so you will not be able to mount a root file system. This may be caused by the kernel failing to detect you hard disk drive or failing to read the partition table, or the disk may unpartitioned. If you wish you may investigate this from a shell in the installer environment."
....any suggestions ?
Thank you very much and best regards.
↧
Re: Converter keeps trying to install the agent
The ports look OK. I suppose you have taken into account there are actually 3 (or 4) nodes with network paths between then to care for - source machine, converter server, destination ESX server, and eventually destination vCenter Server. (e.g. port 902 is not used between source and converter)
Can you try to manually install the agent on the source? This is the easiest workaround. If that's not an option, pls upload the worker log for further examination.
Regards,
Plamen
↧
Re: P2V from Debian 5.03 Lenny
Hello
First to check - you are sure the cold clone has done its job and you have the virtual disks created, formatted, and with data on them, right?
If everything's OK so far, then it is indeed the reconfiguration that you need to do.
The advice of booting a live installation ISO is right, I would just recommend it to be the same version (i.e. 5.03) rather than the newest, at least same major version.
Another thing is to ensure the GOS can work with the new virtual hardware. Check the disk and network controller (first the disk controller). If the GOS supports any of the VMware disk controllers, use it. Otherwise you'll probably need to add some module.
HTH
Plamen
↧