VM W2K 2003 goes blue screen an keeps on rebooting

[Floye]

Community please help :smileywink:

Here is my (hopeless) scenario:

I’m using VMware vcenter Converter Standalone client 4.0.1 to P2V my Citrix member server. Converter is installed locally on Citrix server. After conversion newly created VM when powered up goes to a black screen with Windows Server 2003 than goes to grayish screen as if it were ready to get me to a login screen for like 30 sec and then our favorite Blue Screen of Death :smileywink: with a message among others “IRQL_NOT_LESS_OR_EQUAL. I did some research just to find out that it may have something to do with HD controller . After that it keeps on rebooting constantly going through the same cycle that is blue screen.

Something about physical machine that is Citrix server:

HP Proliant DL 380 G3 with 4GB RAM and SP2.

Proccessor:

3.05 gigahertz Intel Xeon (2 installed)

8 kilobyte primary memory cache

512 kilobyte secondary memory cache

Hyper-threaded (4 total)

RAID 5

Two GB NIC’s (one disabled)

Two partitions:

C: (basic volume) disc 0

D: (basic volume) disc 1

I guess that covers basics.

When starting conversion I choose Virtual Machine version 7, keep the original name (later on when booting up I uncheck power on for NIC so I would not cause any conflict)

Data copy type is default although I increase disks size (both c and d)

Now is the tricky part. This VM is going to run in ESXi 4 environment that is licensed for two processors. Since by default Converter picks up 4 processors I have to edit it and change it to either 2 or 1 processor (crashes in both cases)

Under disc controller I read somewhere that instead “preserve source” I should rather choose SCSI LSI Logic!

I have a bunch of HP insight agent services (not sure whether or not I should mark them to be stopped before conversion.)

Following options are:

Sync changes: disabled

Power on destination: no

Install VMware tools: yes

Customize guest OS: n/a

Remove Restore Checkpoints: yes

Reconfigure Destination VM: yes

Well as I stated at the beginning VM keeps on crushing and I’m getting crazy here not knowing what may possibly cause it. I would really appreciate additional questions from you guys and of course suggestions.

Cheers,

Floye

[continuum]

“IRQL_NOT_LESS_OR_EQUAL." means the Import was successful - next boot into BartPE or your favorite PE and disable old hardware related servikces and drivers that are no longer required in the VM.

Nice tool to do this is "ServicesPE"




___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay

[Floye]

Well I tryed a different approach. Using advanced option I disabled destination services and this time at least I can log in locally (don't want to log in to domain not to cause some kind of conflic) but.........after I log in server starts to discover a several new hardware including SCSI controler, CD ROM and few others. Whether I cancel or go on with install upon rebooting VM crashes and reboots. Well thank God for snapshots. I can get back to original VM in no time and play with services again and again LOL. Do you have any idea what's up with that discovery of a new hardware??? Running in circles :smileywink: help

[Floye]

Any other suggestions? Anybody?

[continuum]

the new devices probably are a bunch of PCI-bridges - you can disable them - see my site

http://sanbarrow.com/workstation-faq.html#p5




___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay

[Floye]

Continuum,

I did what you told me ( that is edited the vmx file with " pciBridgeX.present= "false") but still after boot up server starts to discover

a new hardware starting with SCSI controler, Ethernet card, LSI Logic

ultra 320 scsi adapter, VGA adapter, IDE channel etc .......:)

Could you please have a look at the vmx file right

after conversion process. That is the way vmx file looks like right after conversion and before a first boot up Maybe you will find something that causes

that nightmare

Cheers,

Floye

BTW do you know how to change a status of this post back to not answered. By mistake I changed the status to answered

[continuum]

? - that vmx-file does not look as if you had edited it ?

sure its the right one ?




___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay

[Floye]

C,

This is a vmx file right after conversion is over and before first boot up or any changes to vmx file.. Just wanted you to see an original vmx file. I did edited it once according to your website but it did not change much. Server kept on discovering new hardware.

Two questions:

1) Is everything OK with this vmx file?

2) How would you edit it? Asking so to make sure I did not make any stupid mistake.

Cheers,

Floye

[continuum]

do you still get the same BSOD number as before ?

the vmx looks as if it should work.

Is this ok ?

numvcpus = "2"

If the source machine had only one CPU try to use 1 here too




___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay

[Floye]

C,

>>>>do you still get the same BSOD number as before ?

Yes it is exactly the same

>>>>>>numvcpus = "2" If the source machine had only one CPU try to use 1 here too

Original physical machine has 1processor (4 cores) so the converter picks up 4 processors. I change it to 2.

Now here is a thought regarding that "new hardware" situation:

When I start conversion I'm logged on as a domain admin to my member citrix server. After conversion is done, since production server is still up and running I disable NIC(don't want any conflicts) on my newly created VM power it up and !!!! log on locally. Could it cause creating or rather recreating a new profile and as a consequence discovery of all the new hardware resulting in BSOD???

Like you said the vmx file seems OK so I'm trying to consider other possibilities. Please let me know of what you thing about it.

Cheers,

Floye