import vmdk created from ghost? - bluescreen

[HankVonHelvete]

Hello,

We are trying to import our standard desktop machine into our ESX 4.1 environment for testing purposes.

The vmdk was created from ghost 11.5  and saved as a vmdk file. The vmdk was then copied over to our SAN.

We've tried multiple methods of creating a new VM and using and reusing the vmdk , but keep getting a bluescreen when the VM boots

.

what is the proper procedure to do this? any links or documents I can look at?

[Dave_Mishchenko]

I've moved your post to the Virtual Machine and Guest OS forum. What sort of blue screen error are you getting?  It may be that you need to inject the drivers into the VM to make it work as a VM.  VMware Converter has an option for that. http://kb.vmware.com/kb/1006556 http://kb.vmware.com/kb/1006296

[HankVonHelvete]

cant really tell, the screen doesnt stay up long enough and I cant seem to pause it. let me look at the link

[continuum]

a bluescreen is expected behaviour with a ghost vmdk.

Only if the source machine used an IDE disk with Intel-chipset you will not see this.

So you have to patch the drivers now.
It would really help to know if this is a Windows machine and if yes - which OS exactly.

For Windows 7 and 2008 R2 patching drivers is very easy  - for older versions you need Converter

[HankVonHelvete]

yes, Windows 7 64bit

if you can point me on how to patch or a step by step, it would be great

[continuum]

good - next we need to check your vmx-file. please attach it.

You need a windows7-64bit recovery CD for the next step.
If you do not have one - download one from here http://neosmart.net/blog/2009/windows-7-system-repair-discs/

[HankVonHelvete]

here` the vmx file

[HankVonHelvete]

repair disk booted

[continuum]

power it down.
use the attached vmx-file

boot to recovery cd again and do this ...
copied from my notes http://sanbarrow.com/p2v2008r2.html

On the target platform boot the newly created VM into the Windows              7 Recovery CD.
After boot is finished click on the CMD-button and run  regedit.
Select HKLM and then Menu > File > Load Hive.
Browse to the Windows-directory on the virtualdisk >  system32\config              and select the file SYSTEM.
When asked for a name enter p2v.
Then find the key

HKLM\p2v\ControlSet001\services\LSI_SAS

and set the start value to REG_DWORD 0
Then select HKLM\p2v and click Menu > File > Unload  Hive.
You can close regedit now and restart.

On next boot you can start into the win7 system. It  should find              drivers and probably needs a reboot when done.

do not select the hive in drive X: - yoou need the one from drive c: or d:

[HankVonHelvete]

.zip file seems damaged

[continuum]

just tested it again - download is ok

[HankVonHelvete]

what is the specific name of the LSI_SAS reg entry I need to set to 0?

LSI_SAS has 4 dword entries:

error control

start

tag

type

[HankVonHelvete]

no luck, even with the steps it bluescreens

[continuum]

set start = 0

did you assign the vmdk as LSI-SAS disk ?

it would help if you disable automatic reboot after a crash to find out which bluescreen you get

[HankVonHelvete]

auto reboot is off.

i honestly cant seem to find where the set the vmdk as a lsi-sas disk

[HankVonHelvete]

we've resolved this by using the p2v tool and starting from scratch