The recnfiguration is done when final synch. is set.
So still after deselecting the "reconfig" it still fails with: "Unable to find system volume, reconfiguration is not possible"
As I wrote, I can boot up the converted VM fine, but cannot use the Synch, in the Converter job, which is needed.
Once there are successful conversions you try to figure out what the differences between machines are.
The MBR/GPT partitions scheme, presence or not of LDM, versions of Windows, etc.
When incremental conversion is performed, the reconfigurations are done to test intermediate conversions.
The most important reconfig is final one. Of course the case without reconfig is still valid if target VM boots properly.
HTH
The issue is I don't know what to look at. All P2V is windows 2016 servers. 3 worked fine and another 3 came with the reconfiguration failed. All 3 failed servers could be booted in VMware fine after the error. Problem is that the option to Synch. again is gone when the job fails.
I found no solution to debug this at VMware Converter or source machine
Yes, I understand you that debugging and troubleshooting such issues is not trivial task.
The easiest way is to produce different log files with single conversions for successful and not successful ones.
The restart of worker service will switch the log file but you need to be sure that there are no pending task, including scheduled, while restarting!
The similar result could be retrieved with different Converters installations (on different machines).
HTH
With online Linux conversion, VMware Converter Standalone seems to drop acls that have been set with setfacl.
Unfortunately you are right - the extended ACLs are not preserved with tar command.
The bug is filed for future release.
Perhaps a workaround for now would be to do manually in the source before conversion:
getfacl -R / | gzip > fs.acl.gz
And after conversion in the resulted machine:
zcat fs.acl.gz | setfacl --restore=- && rm fs.acl.gz
Hello
I am doing some testing to convert some KVM machines ( Debian 9 ) and I receive the following error when the final stages are reached.
FAILED: An error occurred during the conversion: 'GrubInstaller::InstallGrub: /usr/lib/vmware-converter/installGrub.sh failed with return code: 127, and message: FATAL: kernel too old Error running vmware-updateGrub.sh through chroot into /mnt/p2v-src-root Command:
chroot "/mnt/p2v-src-root" /vmware-updateGrub.sh
It is surprising that the error related to 'kernel too old' as it is a latest kernel on Debian 9.
I am running the latest VMware Convert 6.2.0 on Windows.
Destination machine - vSphere 6.7 U1
I note from research that older versions of VMware Converter uses GRUB1 and GRUB2 is needed however this seems only applicable to older version of VMware Converter.
The source machine is NOT using LVM and has one partition located in /
Any advice would be appreciated.
I managed to find this which may be the solution.
VMware P2V Conversion: GrubInstaller Error During Conversion of Debian Linux Host | Mantraaz
Ill test out and report back.
Consider trying Disk2vhd to P2V and then StarWind V2V Converter to make VMDK.
Hello
Debian 9 is not supported by Converter, so it is expected to fail.
A few notes on the article mentioned:
- it describes a way to do manual reconfig, which is basically correct.
- it omits to mention that you should also call mkinitramfs after grub2-install. You should ensure that the new inirtd image supports disk and network controllers suitable for VMware virtual hardware.
- it recommends altering fstab by replacing with the new volume UUID. This is also fine, though Converter uses block device mounts.
- it blames grub version. In that case Converter recognizes the correct grub version but fails to install grub due to the source machine having kernel 4.19 (Converter helper has a kernel that is too old for that).
In addition you may also use these posts as reference for manual reconfig:
Re: Conversion fails with the error:FAILED: An error occurred during the conversion:'root is not found'
HTH,
Plamen
Hello
Thank you for the advice and guides. Still working through it and now you have provided more details which were excluded in the guide it may finally work. Ill let you know once I try your tips.
A more thorough workaround for now:
Before conversion in source machine:
find / -maxdepth 1 -type d | egrep -v '^/(dev|proc|sys|tmp|run|)$' | xargs getcap -r | gzip > fs.cap.gz
After conversion in resulted machine:
zcat fs.cap.gz | awk -F= '{print $2 " " $1}' | xargs -n 2 setcap -v
completely misses h drive that is 735Gb?
Please upload log bundle to check.
logs attached, thanks
The error is:
2019-04-14T16:21:21.305+01:00 info vmware-converter-agent[06900] [Originator@6876 sub=Default] [GetDriveLetterOrMountPoint] Mount point for volume \\?\Volume{976dbe7b-b29f-4125-9583-d3fc9584a4cd}\ is H:
2019-04-14T16:21:21.305+01:00 warning vmware-converter-agent[06900] [Originator@6876 sub=Default] [GetVolumeProperties] Cannot get single extent for volume \\?\Volume{976dbe7b-b29f-4125-9583-d3fc9584a4cd}\(#3)
2019-04-14T16:21:21.305+01:00 info vmware-converter-agent[06900] [Originator@6876 sub=Default] [PopulateVolumeProperties] Unable to get the list of partitions for volume \\?\Volume{976dbe7b-b29f-4125-9583-d3fc9584a4cd}\
2019-04-14T16:21:21.305+01:00 warning vmware-converter-agent[06900] [Originator@6876 sub=Default] [PopulateVolumeProperties] PopulateVolumeProperties indicated that volume \\?\Volume{976dbe7b-b29f-4125-9583-d3fc9584a4cd}\ does not have a recognized file system. Skipping volume ...
What kind of volume is this? Keep in mind that RAID volumes are not supported: Supported Source Disk Types
HTH
Hello,
We have a VM on HYPER-V Server (Windows 2012 R2 Datacenter Edition).
VMware VCenter Converter Standalone Version:6.2.0.8466193 is installed on VM to convert to VMware.
Getting error “unable to obtain hardware for the selected machine”, when we try to convert VM.
Are you sure the VM is powered off?
Please upload the client log. It can be found in "%LOCALAPPDATA%\VMware\VMware vCenter Converter Standalone Client\Logs"
