Hello,
the BSOD might be caused by some driver for the physical server for a hardware which is not present in the virtual machine. Try to uninstall all the drivers for PCI cards, Network cards, Video cards, audio cards and so on and see if the problem persist.
they have now fixed this issue with the latest version that you can download from the Acronis website and update.
Please have a look at the updated info and review here to stay updated: http://www.acronisdiscount.com/acronis-true-image-review/
Best
The issue in my previous post was due to a Parallels driver being orphaned after the Parallels tools were uninstalled. Here is a bit more info.
I believe I have figured out what works now. We have two VMware VMs that were P2V’d from VZ VMs that we are using for testing. I have verified this solution on both of those P2V’d VMs. I have also verified that this works on the original production VZ VM as well.
>
>
>
> If you notice the attachment (VM_disk_drivers_before_par_tools_removed.PNG), you will see that the Lower & Upper filters reference “prl_strg” and “partmgr” respectively in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}. Both of those drivers are shown in the driver details under Device Manager.
>
>
>
> When you remove Parallels Tools (note attachment VM_disk_drivers_after_par_tools_removed.PNG), you will notice that Device Manager shows that the prl_strg.sys file is no longer referenced. However, “prl_strg” is still associated with the LowerFilters entry in the registry. When prl_strg is removed from LowerFilters, and the system is rebooted, everything works fine.
Hi, guys,
Now I need your helps abt error of VMware vCenter Converter Standalone.
When I try to convert WinXP to virtual by this local machine, it failed the convert at 98percent and I have the next error message,
FAILED:Unable to reconfigure the destination virtual machine
I know it success the convert but appears blue screen as I turn on the machine.
Now I use,
VMware vCenter Converter Standalone6.1.1
VMware vSphere Client6.0.0
VMware ESXi6.0.0
Already I tried to use Converter5.5.3, convert by remote windows machine and to another virtual machine.
Im not sure how to solve this error.
If you have any ideas, let me know PLEASE! Thank you!
Plese upload log bundle to investigation of the problem. (It's always preferable to use latest Converter)
Also check your disks and ensure only one active volume exists (across all disks!). This is most often problem with reconfiguration.
HTH
Hi Guys/VMware Expert,
I would like to report that I have encountered an error in VMs after successfully converted from physical to virtual using P2V converter 6.0 and during booting up the VM, it hangs at "starting Udev".
Please see image below.
We have really appreciated to response and resolved this issue as well. Thank you.
Thank you in advance.
Thank you for your message.
I cannot make any change in the source server.
After powering on the VM I have no time to iuninstall anything.
I was able to successfully P2V the server from a Symantec backup using Converter 4.x, but I did not perform any thest using the live server.
Regards
marius
Try to run VM in safe mode and clean up unnecessary drivers.
HTH
What BSOD do you se? Is it "INACCESSIBLE_BOOT_DEVICE", or something else?
In case of an inaccessible boot device it may help to modify the VM's settings - i.e. change the virtual disk and controller to LSI Logic Parallel - and then run the Converter again for the converted VM using the "Configure Machine" option, which should then inject the required drivers.
André
What is the BSOD error and please provide the Model of the Physical Server
Did you tried below steps and see
1. Try log in to Server using Safe-Mode and uninstall all the Drivers
2. If Safe-Mode is not working then try to repair the OS
Thanks for your reply.
First, I upload the log bundle here.
Now its converted with running all services, but if some r stopped, could you think it might be success to convert??
Then, here I post the capture of active volume and I guess just one exists in this machine...
I also encountered such a problem。Pay attention to this：When you convert a powered-on Linux machine, Converter Standalone creates a Helper virtual machine on the destination. The Helper virtual machine needs network access to the source machine to clone the source files. Default conversion settings enforce automatic acquisition of an IPv4 address and a DNS server for the Helper virtual machine, but you can set up this network connection manually.@@
This log is not helpful, get the log bundle from Converter - select task and with right mouse button choose Export log bundle.
oh,sorry. Log bundle is Conveter Diagnostics, right?
I upload again the log bundle here.
I am trying to P2V our last physical server in the environment where 200 have so far been converted with no problems until now.
"Unable to contact the specified host. The host might not be available on the network, there might be a network configuration problem, or the management services on this host are not responding"
Suggestions?
Your ESX host do not respond, so conversion could not be started.
HTH
The error during reconfiguration phase is:
2016-06-16T05:31:52.750+09:00 error vmware-converter-worker[04204] [Originator@6876 sub=task-3] Reconfiguration failed with: vim.fault.NoPermission
Try to run GUI 'as administrator', also see that UAC is disabled.
HTH
Hi All,
I would like to redeploy a Win Server 2003 R2 Std Edition to a new physical hardware. I would like to convert the physical machine into virtual, and after which uses vSphere Hypervisor to redeploy the virtual machine in a new hardware.
A few clarification:
1) Is above strategy possible?
2) Is Win Server 2003 R2 Std Edition supported by vCenter Converter? From the documentation, it does not listed as one of the Supported OS.
3) Is it a must to have the Source and Destination both available/online at the same time to execute this? Possible to first convert to the physical to virtual. And redeploy the virtual separately?
Thanks in advance!
The physical machines as targets are not supported. In other direction you can do virtualization of your physical machine as many times as you want, in the same or different target ESX/VC. Don't worry W2K is supported but not mention because it's out of life.
HTH
Thanks POCEH,
On second note, can the vCenter Converter works with OEM license? If the Windows is an OEM license, will the P2V to ESXi works after syncing?
I come across User Guide (v4.3) that says OEM not supported. But it is not mentioned in v6.1.
Thanks.