Problème Crash VM

[Philippe56]

Bonjour,

J'utilise VMware Workstation 8 sur deux postes avec une VM de Windows NT4 SP6

J'ai remarqué que sur l'un des PC, j'ai droit à un écran bleu mais sur l'autre tout fonctionne parfaitement avec la meme image vmware...

Auriez vous une idée d'ou provient le problème?

Merci à vous!

[a_p_]

Welcome to the Community,

is it ok to answer in English (my French is really bad)!?

Did you copy the VM from one host to the other while the VM was in a "Suspended" state? If this is the case you will find a .vmss file in the VM's folder that you could try to delete. If this does not solve the issue, power off the VM on the working host and copy the VM over again.

If the VM was not suspended, please post a screen shot of the BSOD and attach the VM's vmware.log files for the working as well as non-working VM.

André

[Philippe56]

Hi André and thank you for your answer!

It's ok to talk in english!

Actually, i did not copy my VM in suspended state and i copied my VM a second time and it's always the same.

There's only one computer which the vm works...so i don't understand...

Here's a screenshot of my BSOD...

Thanks for your help

Philippe

[a_p_]

"IRQL_NOT_LESS_OR_EQUAL" usually points to a hardware/driver issue. Do both hosts have the same CPU vendor (Intel or AMD) and belong to the same processor family? In case of an Intel CPU, you may want to check whether the BIOS settings for "VT-x" and "Execute Disable Bit" are the same on both hosts. This should actually not make a difference for the OS, but in case of Windows NT I'm not sure.

André

[Philippe56]

Both hosts have the same CPU vendor: Intel i3 and also the same OS: Windows 7 (x64)

the BIOS settings are exactly the same and i compare one by one the differents options, i just checked that again ans it's the same problem...

[a_p_]

The vmware.log file in the VM's folder contains a lot of information about the physical hardware's capabilities. If you attach the latest vmware.log for the working and non-working VM I could check whether they contain any hints.

André

[Philippe56]

Hi!

Sorry i had to leave last night!

So here's the log of the two virtual machine. I don't even think to take a look in there, i will examinate that right away...

Thanks!

[a_p_]

According to the log files you do have different CPUs with different BIOS settings regarding VT-x.

The one which works has an "Intel(R) Core(TM) i3-2350M CPU @ 2.30GHz". VT-x does not seem to be enabled and the VM runs in "Binary Translation" mode. The non-working PC has an "Intel(R) Core(TM) i3 CPU M 350  @ 2.27GHz". This PC has VT-x enabled and the VM is started in HWMMU mode.

What you could try to do - other than to modifying CPU/BIOS settings - is to change the VM's processor settings for the non-working VM and set "Binary Translation" as the preferred mode.

André

[Philippe56]

I changed the processor of the non working VM to "Binary Translation" as the preferred mode. And it's not working....

What is the HWMMU mode in french?

If you have any other suggestion, it would be great!thanks!

[a_p_]

I changed the processor of the non working VM to "Binary Translation" as the preferred mode. And it's not working....

Sorry, at the moment I'm out of ideas other than trying different BIOS settings. Maybe the latest vmware.log from the non-working VM has some more hints on what could be wrong after setting the preferred mode!?

What is the HWMMU mode in french?

HWMMU stands for "Hardware Memory Management Unit" virtualization. Although for vSphere, http://www.vmware.com/files/pdf/perf-vsphere-monitor_modes.pdf (page 3) explains the different execution modes.

André

[Philippe56]

Ok

Here's the latest vmware.log from the non working vm if you have any others ideas....

At the moment of the BSOD, we cans see in  the vmware.log file

2012-04-29T22:59:27.567+02:00| vcpu-0| I120: SVGA: Sync FIFO with SVGA disabled
2012-04-29T22:59:27.584+02:00| vcpu-0| I120: CPU reset: soft (mode 2)
2012-04-29T22:59:27.589+02:00| vcpu-1| I120: CPU reset: soft (mode 2)
2012-04-29T22:59:27.716+02:00| vcpu-0| I120: SVGA: Unregistering IOSpace at 0x10b0
2012-04-29T22:59:27.716+02:00| vcpu-0| I120: SVGA: Unregistering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000)
2012-04-29T22:59:27.791+02:00| vcpu-0| I120: SVGA: Registering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000)
2012-04-29T22:59:27.794+02:00| vcpu-0| I120: SVGA: Unregistering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000)
2012-04-29T22:59:27.824+02:00| vcpu-0| I120: SVGA: Registering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000)
2012-04-29T22:59:27.832+02:00| vcpu-0| I120: SVGA: Unregistering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000)
2012-04-29T22:59:27.835+02:00| vcpu-0| I120: SVGA: Registering IOSpace at 0x10b0
2012-04-29T22:59:27.835+02:00| vcpu-0| I120: SVGA: Registering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0

Is there a problem with the display driver?or you think it's a problem of cpu?

Thanks...

[Philippe56]

Hi,

I did several tests and it seems to be a video problem

In the working VM, at start up there's some messages to install video driver and finally i install it an after reboot my working vm crash with BSOD!!!

So i think it's a problem with the video driver and the VM tools...I would like to boot with the VGA driver by default, in fact i don't care of the display. I think VMware Workstation istall VM tools and the video driver...I will make some tests.