Windows 2008 R2 + HOST CPU = BSOD

longhair

Member
Jun 27, 2014
113
0
16
When ever I try to use the host cpu Intel Xeon X5770 with Windows Server 2008 R2, I get a BSOD. The problem is with Proxmox because I am able to install Windows 2008 R2 on bare metal and have no issues at all.

Code:
[FONT=monospace]proxmox-ve-2.6.32: 3.3-147 (running kernel: 2.6.32-37-pve) 
pve-manager: 3.4-1 (running version: 3.4-1/3f2d890e) 
pve-kernel-2.6.32-37-pve: 2.6.32-147 
lvm2: 2.02.98-pve4 
clvm: 2.02.98-pve4 
corosync-pve: 1.4.7-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.10-2 
pve-cluster: 3.0-16 
qemu-server: 3.3-20 
pve-firmware: 1.1-3 
libpve-common-perl: 3.0-24 
libpve-access-control: 3.0-16 
libpve-storage-perl: 3.0-31 
pve-libspice-server1: 0.12.4-3 
vncterm: 1.1-8 
vzctl: 4.0-1pve6 
vzprocps: 2.0.11-2 
vzquota: 3.1-2 
pve-qemu-kvm: 2.1-12 
ksm-control-daemon: 1.1-1 
glusterfs-client: 3.5.2-1[/FONT]
 
Also what other configuration did you use for the VM such as allocated memory, fixed or dynamic? Are you trying to fresh install Windows 2008 in the VM?
 
BSOD error is a 0x00000001E

The only CPU that works is the Default (kvm64) - everything else blue screens.

12 to 24 GB dynamic memory / 24 GB fixed, clean install with a new VM using setup disc - not cloned or template.

I can set up a VM using the default, change the CPU to host (or anything else for that mater), start it up only to see it blue screen. Shutdown, change back to default and it works like nothing was wrong.
 
Hi,

you should try to choose a vcpu model which match your physical cpu host (ivybridge, sandybridge,....).

You should have same performance than HOST, but the working cpu flags are tested and validated in this case.


(From my opinion, HOST should never be used)
 
Hi,

you should try to choose a vcpu model which match your physical cpu host (ivybridge, sandybridge,....).

You should have same performance than HOST, but the working cpu flags are tested and validated in this case.


(From my opinion, HOST should never be used)

I've tried that (Nehalem) and it BSOD with the same 0x00000001E error.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!