Phase0_exception BSOD after 3.1 upgrade

[werdisturbed]

After upgrading to version 3.1 any Win 2008 server or Win 7 VM that was restarted, they would BSOD on Phase0_exception. Booting from the installation CD would result in the same error. I tried changing options for ACPI, SCSI controller, RTC options and KVM virtualization with no success.

I noticed that one 2008 server was booting successfully which was upgraded from 2003 to 2008 during testing. The settings for this machine was still configured as "Microsoft Windows XP/2003(wxp)". I changed the option in my other VMs that were experiencing the issue and the issue was resolved.

Has anyone else experienced this issue? What could have changed on 3.1 that would cause this? Any fix aside from the above workaround?

 

[dietmar]

What could have changed on 3.1 that would cause this?

What was your previous version?

 

[werdisturbed]

Upgraded from 3.0 to 3.1.

 

[dietmar]

Upgraded from 3.0 to 3.1.

The kvm is still the same version, only kernel is new. Maybe you can verify that booting into the old kernel and test again.

 

[spirit]

The kvm is still the same version, only kernel is new. Maybe you can verify that booting into the old kernel and test again.

Hi Dietmar,it's possible it's come from my hyper-v enlightments patches enabled for >winvista config.

I don't have problem under win2008R2 and win7.


here, Is it win2008 ? 32bit or 64bit ? and which service pack ?


(also the host need to boot on recent kernel (rhel 6.4) to have the kvm module with hyper-v support, don't remember the pve-kernel version exactly)

 

[spirit]

After upgrading to version 3.1 any Win 2008 server or Win 7 VM that was restarted, they would BSOD on Phase0_exception. Booting from the installation CD would result in the same error. I tried changing options for ACPI, SCSI controller, RTC options and KVM virtualization with no success.

I noticed that one 2008 server was booting successfully which was upgraded from 2003 to 2008 during testing. The settings for this machine was still configured as "Microsoft Windows XP/2003(wxp)". I changed the option in my other VMs that were experiencing the issue and the issue was resolved.

Has anyone else experienced this issue? What could have changed on 3.1 that would cause this? Any fix aside from the above workaround?

Do you have restarted your host with new kernel after upgrade ?

(#uname -a ) ?

 

[werdisturbed]

Do you have restarted your host with new kernel after upgrade ?

(#uname -a ) ?

I have rebooted during my troubleshooting. It doesn't look like the new kernel took.

# pveversion -v
proxmox-ve-2.6.32: 3.1-109 (running kernel: 2.6.32-20-pve)
pve-manager: 3.1-3 (running version: 3.1-3/dc0e9b0e)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-17-pve: 2.6.32-83
pve-kernel-2.6.32-18-pve: 2.6.32-88
pve-kernel-2.6.32-23-pve: 2.6.32-109
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.0-1
pve-cluster: 3.0-7
qemu-server: 3.1-1
pve-firmware: 1.0-23
libpve-common-perl: 3.0-6
libpve-access-control: 3.0-6
libpve-storage-perl: 3.0-10
pve-libspice-server1: 0.12.4-1
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.0-2

# uname -a
Linux proxmox 2.6.32-20-pve #1 SMP Wed May 15 08:23:27 CEST 2013 x86_64 GNU/Linux

I restarted one of the cluster nodes, confirmed the new kernel is in place and booted a client with the 2008/win7 definition successfully.
# uname -a
Linux proxmox3 2.6.32-23-pve #1 SMP Tue Aug 6 07:04:06 CEST 2013 x86_64 GNU/Linux

Looks like that did it. I'll schedule a reboot of the other nodes this evening and post if that doesn't resolve it.

 

[iconvergence]

any update on this got same issue

 

[werdisturbed]

any update on this got same issue

Yes the kernel was updated during the upgrade which requires a reboot to put it in place. Until you reboot the Proxmox server, the VMs will BSOD.

 

[spirit]

Yes the kernel was updated during the upgrade which requires a reboot to put it in place. Until you reboot the Proxmox server, the VMs will BSOD.

Yes, This si because proxmox 3.1 include hyper-v enlightements, which need features in kvm module of last kernel.