WS 2008R2 blue screen at sart with cache back

[tesquenure]

Hi all,

If i stop my WS 2008R2 and start it, i have bluescreen.
This is with virtio uptodate.

With no cache all is fine, but verry slow.

Do i miss some thing ?

PS :
Finaly BSOD with no cache too
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-19-pve
proxmox-ve-2.6.32: 2.3-96
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-20
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-7
vncterm: 1.0-4
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-10
ksm-control-daemon: 1.1-1

cat /etc/pve/qemu-server/100.conf
bootdisk: virtio0
cores: 4
ide2: local:iso/SW_DVD5_Windows_Svr_DC_EE_SE_Web_2008_R2_64Bit_French_w_SP1_MLF_X17-22584.ISO,media=cdrom,size=3122620K
ide3: local:iso/SW_DVD5_Office_2010w_SP1_W32_French_CORE_MLF_X17-82116.ISO,media=cdrom,size=1154384K
keyboard: fr
memory: 35840
name: MWS2008R2
net0: virtio=66:CC:75:AB:BC:7D,bridge=vmbr0
ostype: win7
sockets: 1
vga: std
virtio0: local:100/vm-100-disk-1.raw,size=200G
virtio1: backup:100/vm-100-disk-1.raw,size=5G

 

[dea]

Could be a problem of virt-io drivers. Try setting disk 1 and 2 as "sata" and verify that the system is more stable ...

Luca

 

[tesquenure]

ok i try it now

 

[tesquenure]

Same BSOD after 3 stop and start with ide driver

What i dont understand, i work on this server for 4 days with a WS 2012 with virtio and have no isu.
Now i have this with a 2008R2

 

[dea]

Same BSOD after 3 stop and start with ide driver

What i dont understand, i work on this server for 4 days with a WS 2012 with virtio and have no isu.
Now i have this with a 2008R2
View attachment 1427

Try to disable ACPI

 

[tesquenure]

I realy need it
Im not shure if problem start after the update to pve-kernel-2.6.32-19-pve: 2.6.32-96 from pve-kernel-2.6.32-18-pve: 2.6.32-88.

I just load back my WS2012 and do some tests

a nice BSOD now on my 2012 too
gona try a dowgrade pve

 

[tesquenure]

i find the way to downgrade from 2.6.32-19-pve to 2.6.32-18-pve.
but proxmox-ve-2.6.32: 2.3-96, how to change that ?

because with this conf always have BSOD

pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-18-pve
proxmox-ve-2.6.32: 2.3-96
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-20
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-7
vncterm: 1.0-4
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-10
ksm-control-daemon: 1.1-1

 

[dea]

Try to upgrade Proxmox 2.3->3.0rc2

 

[spirit]

Hi,
This doesn't seem related to a disk problem, but more a clocksource timedrift. (Which can cause bsod on windows).

(Do you a ntp server in your guest ?)

For test, can you choose linux as ostype ?

 

[spirit]

also, you can try this:

http://pve.proxmox.com/wiki/Guest_Time_drift

C:\Windows\system32>bcdedit /set {default} USEPLATFORMCLOCK on

 

[tesquenure]

Hi,

I finally install Win 2008 directly on server.
I try to update to 3.2. After the update, impossible to have the console.

Spirit, i can have the BSOD when i use discover in HDD utility and when i stop and start the VM.

I can try this on an other HDD.

I realy dont anderstand how time drift can cause that ?

 

[tesquenure]

C:\Windows\system32>bcdedit /set {default} USEPLATFORMCLOCK dont work on my server 2008 R2.
I try with linux machine type. Same BSOD.
I use the windows directly on the server ASUS TS 500

 

[spirit]

C:\Windows\system32>bcdedit /set {default} USEPLATFORMCLOCK dont work on my server 2008 R2.
I try with linux machine type. Same BSOD.
I use the windows directly on the server ASUS TS 500

ok, another ideas:

in your server bios, do you have some options like:

dynamic cpu frequency, cpu core shutdown if inactivity,C1E (enhanced halt state), Intel Speed step,...

for my dell servers, I need to : disable speedstep, disable C1E, set cpu to "max performance".

 

[tesquenure]

Juste have a new server tomorow.
I gona test bios change and let you know.

 

[tesquenure]

Bios setting change nothing. BSOD
BUt IDE drivers stop BSOD.
I think its come from VIRTIO drivers.
I have to find the way to down grade windows virtio driver.