admin
Immortal
Immortal

Can you please post/attach the VM's vmx file.

Regards,

Randhir

Reply
0 Kudos
NewGuyInVMs
Contributor
Contributor

This is the VM's vmx file.

Thanks for reminding me!

Reply
0 Kudos
admin
Immortal
Immortal

Can you see below link about BSOD 7B....

P2v and 0x0000007B BSOD

While you are editing the vmx file, you may also want to replace

guestOS = "longhorn"

by

guestOS = "winvista"

or - even better - edit the guest OS in the VM's settings.

Regards,

Randhir

Reply
0 Kudos
NewGuyInVMs
Contributor
Contributor

I did change the guestOS, but it made no difference.

BSOD appears again (this time appeared without a code, but with the same message). I did run a chkdsk on the VM, but nothing changed.

Reply
0 Kudos
admin
Immortal
Immortal

can you confirm if you change

change

scsi0.virtualDev = "lsilogic"

to

scsi0.virtualDev = "lsisas1068"

It only applies if the virtual disk is configured like this

scsi0.virtualDev = "lsisas1068"

On the target platform boot the newly created VM into the Windows 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 ILIAS_NB_FIFTH.

Then find the key

 

HKLM\ILIAS_NB_FIFTH\ControlSet001\services\LSI_SAS

 

and set the start type to REG_DWORD 0

Then select HKLM\ILIAS_NB_FIFTH and click Menu > File > Unload Hive.

You can close regedit now and restart.

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

Regards,

Randhir

View solution in original post

POCEH
VMware Employee
VMware Employee

If VM booted this is step ahead Smiley Happy

From the screenshots I've see that probably "ahci" controller is not present in Vista, so try to change it to "lsisas1068", "lsilogic" and "buslogic" (in this order) and boot VM. You can change the string in VMX file directly with text editor.

Please share the result.

Reply
0 Kudos
NewGuyInVMs
Contributor
Contributor

I guess you are referring to the

sata0.virtualDev = "ahci"

line in the .vmx file. I tried to boot the VM after I changed it to both 3 values, but on every one of them similar message to the below appeared:

Screenshot_22.png

I tried also the suggestion of ranchuab to change

scsi0.virtualDev = "lsilogic"

to

scsi0.virtualDev = "lsisas1068"

But that didn't make any difference as well.

I will try to do the rest he suggests once I get to open a CMD through the installation disc - I have to select the repair option and wait for it to complete the try before it shows up the options to open the cmd.

Reply
0 Kudos
NewGuyInVMs
Contributor
Contributor

Oh, wow! That actually did make it work! VM booted with no problem and I logged into the admin account! Smiley Happy

Thanks ranchuab and POCEH for all your help!

Reply
0 Kudos
admin
Immortal
Immortal

you are welcome NewGuyInVMs Smiley Happy

Regards,

Randhir

Reply
0 Kudos
NewGuyInVMs
Contributor
Contributor

I've got only one last problem - not sure if I should make a new question on the Workstation forum about this so I'll ask here first.

I am trying to install VMware Tools on this VM, but it fails giving me the below error message:

Screenshot_24.png

I can successfully visit the webpage from the browser of the VM and also on the browser of the pc running the VM:
Screenshot_25.png

Any idea what to do in this case?

Reply
0 Kudos
POCEH
VMware Employee
VMware Employee

First check if VM Player 12 is supported yet. If not should upgrade to latest one and then try to install tools.

Just wild guess. HTH

Also check if Vista is supported.