Try to create a new Boot.inf file and repair the OS , it should fix all the missing files
Did you try a OS repair ?
Try to create a new Boot.inf file and repair the OS , it should fix all the missing files
Did you try a OS repair ?
yes, the .vhd-file is the primary disk
When I start the VM, I get a Windows boot error :
File: \Windows\system32\winload.exe
Status: 0xc000035a
Info: Attempting to load a 64-bit application, however this CPU is not compatible with 64-bit mode.
When I boot this VM from a Windows 7 (64-bit) ISO (to try the Windows repair functionality), I get the same message - I don't have this problem when I create a new VM from scratch using this ISO-file.
The host machine has a Intel i3 2350 CPU which is running Windows 7 Ultimate 64-bit , although I think that hardware visualization support is currently disabled, but even without it all my other Windows 7 VMs run flawlessly.
Hi Sven,
Your other windows VMs work because they were built within VMware.
The VHD that you are trying to use has been built on different hardware e.g. a physical machine, then converted to a VHD and attached to a VM as the primary disk. That is a significant hardware change for Windows thus it will require the repair to take place before it will boot into the OS.
This is more of a Windows OS issue than a VMware issue., The following article explains how to get to recovery mode, from there you can run a startup repair which should resolve the issue How to start the Windows 7 Recovery Environment
Regards,
Steve
Thanks to SAraissiSAraissi for the tip! Re-installing File and Print sharing and rebooting the Windows XP Pro machine worked for me!
Hola
Please see this KB artice: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1035241
Converter agent uses a bitmap driver to track the changes on the volumes. In certain cases removing it requires restart of the machine. It is possible that's the reason you can't uninstall the agent.
HTH
Plamen
I was able to solve the problem I described by enabling hardware virtualization support within the BIOS of the host machine.
Now Windows start, but even in safe mode it crashes with a blue screen after ClassPNP.sys
... booting from an ISO, the automatic Windows repair reported that it can not solve the problem.
Hi,
We are currently running ESXi 5.5 and would like to conduct P2V.
Just would like to seek your advice that whether we can use "Standalone Convertor 6" or we should use "Standalone Converter 5.x" ?
Thanks
Gracias por la ayuda, pero ya lo había comprobado, solo tengo un proveedor.
Un saludo.
Converter 6.0. Performed a V2V on a SUSE 11 Server. Before V2V the Server partitions were not aligned, after the conversion, partitions look aligned but show the warnings below when running fdisk. The size of the volume was also increased from 30GB to 100GB. The system boots and seems to function just fine.
I looked around and the cylinder boundary warnings might be normal because the partitions were aligned and OS does not know about the alignment?
Can someone chime in if this is normal to see this?
fdisk -lu
Device Boot Start End Blocks ID System
/dev/sda1 * 128 20964991 10482432 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 20964992 23053567 1044288 83 Linux swap / Solaris
Partition 2 does not end on cylinder boundary.
/dev/sda3 23053568 232768767 104857600 83 Linux
Partition 3 does not end on cylinder boundary.
sfdisk -uS -l /dev/sda
Device Boot Start End #sectors ID System
/dev/sda1 * 128 20964991 20964864 83 Linux
end: (c,h,s) expected (1023,254,63) found (1023,2,41)
/dev/sda2 20964992 23053567 2088576 83 Linux swap / Solaris
start: (c,h,s) expected (1023,254,63) found (1023,2,42)
end: (c,h,s) expected (1023,254,63) found (1023,4,41)
/dev/sda3 23053568 232768767 209715200 83 Linux
start: (c,h,s) expected (1023,254,63) found (1023,4,42)
end: (c,h,s) expected (1023,254,63) found (1023,47,22)
/dev/sda4 0 - 0 0 Empty
Yes. Converter 6.0 is backward compatible with ESXi 5.0, 5.1 and 5.5.
Hi Vmware,
I tried three version of vmware converter ( 4.3, 5.5 & 6.0)
There is no one can work on redhat 5.3.
After i insert all the login information to the converter, the converter returns an error to me
"unable to query the live linux source machine"
Could somebody give me advice? Thanks a lot.
I have searched the problem on google and tried all the solution.
1. My source server can ssh with root.
2. echo "ALL:ALL" >> /etc/hosts.allow i added this command to hosts.allow.
3. Only one interface on the server (eth0)
Please feel free to ask if you need more information.
It still not work even i use the old version converter (4.0)
Hi,
Quick question. Need to v2v a 2008r2 server with vmware converter. The thing is that this server has a windows ISCSI Connection for one of the drives. When i try to connect to the machine i get a unable to obtain hw information... I guess this is the reason? I thought that since the machine is offline converter does not even care about that ISCSI Connection.
Martin
Hi all,
I've been suffering from what appears to be sporadic conversion performance (ranging from 800Kb to 50MB/s), I've ran two conversions side by side of windows 2003 servers (yes eol, yes no support, but this is what our business demands) both in the same source location and both going to the same destination infrastructure - One will run at around 20MB/s and the other around 4MB/s. If all my migrations ran at 4MB/s i'd wonder whether its infrastructure, but it seems to be specific to servers therefore i would like to focus on this example and see if theres anything from server level that can be done.
Actions I have taken.
Some known's
To summarise in one question: what in addition to the above can be done at server level to increase performance.
Thanks
Barry
Problem solved.
The cause is my source server is no more free space here and the df command is not working on the server.
The converter cannot determine the source server hard-drive information.
Then the error will comes out.
After i free some space on the server. It works perfectly now.
Hey Guys, i'll try to sum this up the best I can so it doesn't run long and get boring.
Recently we switched to Veeam as our backup solution and discovered that it will not backup disks larger than 2032GB.
Our main virtual file server has two disks that are about 2072GB(don't even know how that happened).
I unmounted one of them from the main virtual file server and mounted it to a new test VM that I made.
I'm trying to do a V2V convert of that test VM to a new VM with a smaller disk size with the VMware Converter Standalone, with the intention of afterwards unmounting it from the test VM and remounting back to the original main virtual file server.
The problem is the V2V just gets stuck at 98%. I've tried leaving it at 98% for about 8 hours but it still never progresses or error's out.
Any help with this or any suggestions on other ways to shrink a virtual disk would be greatly appreciated, thanks!
Hello
a few clarifications first:
"SSL set to false." - I assume this means "<useSsl>false</useSsl>" in worker config as in Increasing the cloning performance, correct?
"Ensured NIC speed set" don't know what you mean by that, hope it's ok.
Other factors that affect performance might be
cloning level - file level is slower than block level; file level will be triggered by shrinking the volume or changing the cluster size
ESX host performance. The conversion establishes a connection between the source machine and the destination host and uses the proprietary NFC protocol. I.e. the host current load, disk speed etc. will affect the performance, too.
HTH
Plamen
Hello
98% is at the reconfiguration stage. If your sole purpose is to shrink the disk, you don't need reconfiguration. It can be switched off in the wizard. To be on the safe side check that your converter version supports files that large (5.5 or 6.0 is OK, perhaps older too)
As for the running conversion - if you cancel it, that should be OK - you could use the disk. However if it has is stuck, perhaps canceling would perhaps not finish too. Stopping the converter worker service will finish the conversion of course but you can't rely on the disk integrity in that case.
HTH
Plamen
Dear louie7600louie7600,
Why don't you clone the VM?
That would be faster option than VMware conveter.
If you find this or any other answer useful please mark the answer as correct or helpful.
Regards,
RGS
How do you shrink the disk when cloning?