These are GUI logs. Click on the task and choose 'export logs'
↧
Re: Migration of SUSE Linux VMs from HyperV to ESXi
↧
Re: Migration of SUSE Linux VMs from HyperV to ESXi
PFA'd
↧
↧
Re: Migration of SUSE Linux VMs from HyperV to ESXi
Let me repeat the warning, seems you may have missed it
Offline Linux migrations do not reconfigure the destination, there is a chance the VM won't boot. It is recommended to to a powered on conversion.
Power on the VM in hyper-v and convert it as powered on machine. Otherwise - no reconfig, no boot.
HTH
Plamen
↧
Re: Migration of SUSE Linux VMs from HyperV to ESXi
the problem with powered on VM conversion is, it a prepares a separate hard-disk for /boot/efi alone, unlike in the source where /boot/efi is a part of root disk ( it is partitioned there for /boot/efi...)
↧
Re: Migration of SUSE Linux VMs from HyperV to ESXi
could you point me to document where the below info is documented...
Offline Linux migrations do not reconfigure the destination, there is a chance the VM won't boot. It is recommended to to a powered on conversion.
↧
↧
Re: Migration of SUSE Linux VMs from HyperV to ESXi
btw, the moment the vmdk is updated to use "ide" adapterType,(instead of bus/lsi) the vm boots up...
↧
Re: Migration of SUSE Linux VMs from HyperV to ESXi
Hello
I am getting below error during the conversion...there is a firemwall between the ESXi and source VM, however any <-> any is opened bi-directional between the ESXi/VM/Converter tool..
2016-10-01T12:24:07.124+04:00 error vmware-converter-server[06400] [Originator@6876 sub=Default] [task,350] [LRO] Unexpected Exception: vmodl.fault.HostNotReachable
2016-10-01T12:24:07.126+04:00 info vmware-converter-server[06400] [Originator@6876 sub=Default] [task,379] [task-7] -- ERROR -- Convert: vmodl.fault.HostNotReachable
--> (vmodl.fault.HostNotReachable) {
--> faultCause = (vmodl.MethodFault) null,
--> msg = ""
--> }
2016-10-01T12:24:07.126+04:00 info vmware-converter-server[06400] [Originator@6876 sub=Default] [diagnosticManager,260] Retrieved taskInfo for "converter.task.Task:task-7" mapping it to "converter.task.Task:task-7".
2016-10-01T12:24:07.126+04:00 info vmware-converter-server[06400] [Originator@6876 sub=Default] [diagnosticManager,300] The task with id = "task-7" was found to be a "recent" task.
↧
Re: Migration of SUSE Linux VMs from HyperV to ESXi
User Guide, p.32, section "Conversion Limitations for VMware Virtual Machines"
↧
Re: Migration of SUSE Linux VMs from HyperV to ESXi
You have been lucky. Most probably SUSE has been able to reconfigure itself (like Windows). Do not rely on that for Linux in general.
↧
↧
Re: Migration of SUSE Linux VMs from HyperV to ESXi
Context please. Is this Linux P2V again? At what stage did the error occur?
↧
Re: Migration of SUSE Linux VMs from HyperV to ESXi
It is supported. The issue is with the boot loader. SLES 11 used to install GRUB on BIOS and ELILO on UEFI. Converter doesn't support (E)LILO. However SLES 12 switched to GRUB2 which is now used for both firmwares.
↧
Re: Linux P2V issue
Can you please spend some time in analyzing the client and server side logs , below are the location ,.
It must be the first step to start troubleshooting
VMware vCenter Converter Standalone 5.x and 6.0
To collect the client and agent logs from the Job view click Job > Export logs...
To collect the client and agent logs from the Task view click Task > Export logs...
To collect client logs from the file system of the computer that is running Converter:
C:\ProgramData\VMware\VMware vCenter Converter Standalone\logs
To collect agent logs from the computer that is being converted:
C:\ProgramData\VMware\VMware vCenter Converter Standalone Agent\logs
%ALLUSERSPROFILE%\Application Data\VMware\VMware vCenter Converter Standalone Client\logs
Note: For Linux, there are no client side logs on the source machine because they are stored on the server side.
↧
Re: Solaris 10 VM Converted goes into a Boot Loop
StarWind's V2V Converter could prove helpful here: https://www.starwindsoftware.com/converter
It's completely free and is very simple to use.
↧
↧
Re: Linux P2V issue
Hello
Converter does change configuration files as part of the reconfiguration. These include fstab, GRUB configuration, modules configuration, SELINUX, network interfaces. initrd image is being rebuilt. However Apache configuration should not be affected.
Can you post which files have been changed and attach the log bundle?
Regards,
Plamen
↧
Re: Migration of SUSE Linux VMs from HyperV to ESXi
here is the update:
both p2v and v2v works
V2V is better since it updates all UUID for root, usr file-systems. It also updates /etc/fstab for uuid entries for /boot/efi. P2V doesnt update any of these values and you have to do all of it manually.
You have to boot into rescue mode and perform dracut to get the vm booted.
↧
Re: Solaris 10 VM Converted goes into a Boot Loop
Thanks we tried the StarWinds converter but had no luck at this point
↧
Re: Solaris 10 VM Converted goes into a Boot Loop
I am not a linux / solaris expert, so I hope you can explain in more detail.
- Try to boot the VM that resulted from the conversion (the one that goes in infinite loop at boot) from CD
What type of CD should I boot from ?
If this is the Solaris Live CD Iso image, where can I obtain one?
- Reinstall the boot loader
What is the process to re-install the boot loader?
- Recreate the initial ramdisk. Have in mind that the virtual hardware is expected to be different from the source machine. The most popular virtual hardware is LSI Logic and LSI Logis SAS for disk controllers (IDE and AHCI are also options), E1000 and E1000E for network. You might need to adjust some config files before recreating the initial ramdisk (check the appropriate info how to this the Solaris way)
Where and how is the initial ram disk created?
thanks
↧
↧
Re: Solaris 10 VM Converted goes into a Boot Loop
What type of CD should I boot from ?
A Solaris live CD
If this is the Solaris Live CD Iso image, where can I obtain one?
I have no idea. Perhaps the one from which the machine has been installed. Or check in some Solaris forum.
What is the process to re-install the boot loader?
Again - no idea. That was a suggestion based on a supposed similarity between Linux and Solaris. Check in some Solaris forum
Where and how is the initial ram disk created?
ditto
↧
FAILED: A general system error occurred, Network is unreachable connect, (return code 2)
Good afternoon, I have been trying to convert 2 servers for about a week now. They are running Redhat 5.5. I have been running into all sort of issues. In the beginning the servers would not query and i got passed that but now i have been stuck with this message since yesterday. I have looked at the Forums and I still have not moved anywhere. All I am trying to do is convert 2 old servers to my new esxi server. Please help!! The converter gets to about 3 percent and then Fails.
FAILED: A general system error occurred: connect (`129.166.9.205'): Network is unreachable connect (`129.166.9.205'): Network is unreachable connect (`129.166.9.205'):
Network is unreachable Network error. Host 129.166.9.205 key can't be retrieved. (return code 2)
I will attach my log if that will help.
↧
issue P2V IBM x3650 M2
got error GetVimConnection has error while trying to connect (3), Error: SSL Exception: error:140000DB:SSL routines:SSL routines:short read
OS: Windows 2008R2 SP1
Vmware converter standalone 6
esxi 5.5 update 2
converter standalone usessl already changed to false, still encounter the same issue.
strangely, this is consistenly only happen with IBM x3650 M2 as the source.
↧