BSOD in VM win 2008R2 after update 3.1 to 3.2

[mario]

Hello,
I have VM win 2008R2 in PVE 3.1 everything was worked ok.
Now after I hane got subscription I decide update my PVE servers and after that VM win 2008R2 starts with BSOD.
The VMs win 7 64bit with VIRTIO drivers starts ok.
I found that when I change disk from VIRTIO to IDE I can start VM win2008R2.
My version of VIRTIO is virt-win-0.1-74.

proxmox-ve-2.6.32: 3.2-126 (running kernel: 2.6.32-29-pve)
pve-manager: 3.2-4 (running version: 3.2-4/e24a91c1)
pve-kernel-2.6.32-29-pve: 2.6.32-126
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-16
pve-firmware: 1.1-3
libpve-common-perl: 3.0-18
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve5
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1

Have You some solution for this bug?
Mariusz

 

[tom]

works here. post your VM config.

> qm config VMID

and try a new installation with virtio, does this work?

 

[mario]

balloon: 4096
boot: c
bootdisk: virtio0
cores: 4
ide2: none,media=cdrom
memory: 8192
name: SAD-01
net0: virtio=16:C0:F7:7E:769,bridge=vmbr0,tag=10
net1: virtio=BA6:38:4E:1F:E7,bridge=vmbr0,tag=20
net2: virtio=86:F8:92:15:7A:BB,bridge=vmbr10
net3: virtio=EA:09:2B:A1:64:91,bridge=vmbr11
net4: virtio=86:EC:CC:E5:7B:5D,bridge=vmbr12
net5: virtio=9E:6A:FE:47:1F:15,bridge=vmbr13
ostype: win7
scsihw: virtio-scsi-pci
sockets: 2
unused0: local:101/vm-101-disk-3.raw
unused1: local:101/vm-101-disk-2.raw
virtio0: local:101/vm-101-disk-1.raw,format=raw,size=100G

I fixit by changing in VM Options -> SCSI Controller Type from "Default (lsi)" to "VIRTIO".
Now is ok.
Thank You for quick answer.
Mariusz