When usign P2V mode you can try to disable service/driver in "advanced options". HTH
boot into Windows 8 recovery CD and disable that driver - looks like the mass-storagedrivers are already successfully patched
You probably means Windows 2008 CD. I will give it a try and let you know. Thx...
Unfortunatly no. The issue seems to resides that the instance I am trying to import is from an old version (before EBS) and it's giving that problem.
We ended up to not need to have this instance moved afterall, so I haven't moved on with the problem.
But I would try to use Acronis Server 9, made a backup of it and have the software convert to VmWare and see how it goes as a workaround. Who knows...
Had exactly the same issue. The problem was in "Red Hat paravirtualized Xen drivers for Windows". To remove them from image on destination environment, I've booted to recovery console and made "del rhel*" in Windows\system32\drivers folder.
Hope this help in your case too.
I too am having the same issue. I have an Amazon image running Windows 2008 Standard and after following the directions using the article below I continue to run into the BSOD, specifically the storport.sys file as the gentlemen above has posted.
I am in the process now of adding a new virtual hd, will install a separate copy of Windows 2008 onto the new hd and once I get in, I will try to perform an upgrade on the problem stricken windows partition. Other than that, the only product I think may or may not work is Double Take's Move product. I do not work for Double Take but I hear this product works great since it does a bit level copy. Unfortunately you have to purchase it as there is no trial.
Lastly, trying the "del rhel*" under windows\system32\drivers only created a new BSOD with no useful information so that did not work for me.
I will keep everyone posted on what I find. I wish Amazon would allow for export to OVF (or OVA) to make this process easier.
There are 3 RHEL drivers installed by Amazon on their Windows instances that are causing the trouble. They are rhelfltr, rhelnet and rhelscsi. If you disable these services the target VM boots successfully.
Before Windows starts you can press F8 to get in advanced boot options and select "Repair" entry. After you enter your administrative password and get to the system recovery console, then do the following:
- select command prompt and type regedit
- select HKEY_LOCAL_MACHINE hive on the left
- from File menu select "Load Hive..." command and browse to C:\Windows\System32\config directory and select SYSTEM file
- enter a key name when prompted (e. g. p2v)
- find the key you specified in the previous step under HKEY_LOCAL_MACHINE and navigate to ControlSet001\services
- for each of rhelfltr, rhelnet and rhelscsi services you should select the service, locate the "Start" value on the right and change it to 4 (service disabled)
- select the key created earlier, unload the registry hive and restart the operating system
After the restart the VM should boot OK
Thank you for the post! That actually worked for me! However, I must admit, disabiling all three (rhelfltr, rhelnet, and rhelscsi) caused a new generic BSOD. I rebooted to the Windows 2008 CD, selected Repair again and changed rhelfltr and rhelnet back to 0 or enabled and left rhelscsi Start setting to 4 and rebooted. Worked like a charm! Thanks again! I only wish now that Amazon would make this process easier.
Thanks to all who chipped in here, especiallywho correctly highlighted that it's just the rhelscsi driver that was the issue, at least for him and me.
suggests to use Workstation 6.5 as the target machine type for this - does anybody know if this might be a factor here? I origianlly used Workstation 8 as the target.
Also, as I expect to be making frequent cuts of this machine, are there any bright ideas for automating the removal of the red hat scsi driver?
Incidentally, for me, I got on fine by just moving (or deleting) the scsi driver from the drivers folder. I didn't find it necessary to edit the registry.
I think the only reason Workstation 6.5 is mentioned is because at the time this KB article has been created it has been the latest Workstation available.