Hi Guys,
SInce our upgrade to Proxmox V5 our 2 hosted 2008R2 server(s) bluescreen a few time(s) per week.
Bluescreen error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
Always at night, so customer (luckilly) do not have downtime.
It are original VMWare machines. We took them out of a vcenter datacenter with Acronis Cloud backup, recovered them on our proxmox.
config:
balloon: 0
boot: cdn
bootdisk: sata0
cores: 2
ide2: none,media=cdrom
memory: 8192
name: K0242BEDCRVSR01
net0: e1000=BE:71
7:92:EE:53,bridge=vmbr2,tag=5
numa: 0
ostype: win7
sata0: local-lvm:vm-402-disk-1,size=200G
sata1: local-lvm:vm-402-disk-3,size=65G
scsihw: virtio-scsi-pci
smbios1: uuid=329004e4-d941-4bde-9421-7023c50367db
sockets: 1
I know we should have used virtio for drive(s). But it won't boot because it misses drivers. No idea how we preload them.
pveversion -v:
proxmox-ve: 5.1-25 (running kernel: 4.13.4-1-pve)
pve-manager: 5.1-35 (running version: 5.1-35/722cc488)
pve-kernel-4.13.4-1-pve: 4.13.4-25
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-15
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-2
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.0-2
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.2-pve1~bpo90
Any thoughts?
SInce our upgrade to Proxmox V5 our 2 hosted 2008R2 server(s) bluescreen a few time(s) per week.
Bluescreen error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
Always at night, so customer (luckilly) do not have downtime.
It are original VMWare machines. We took them out of a vcenter datacenter with Acronis Cloud backup, recovered them on our proxmox.
config:
balloon: 0
boot: cdn
bootdisk: sata0
cores: 2
ide2: none,media=cdrom
memory: 8192
name: K0242BEDCRVSR01
net0: e1000=BE:71
7:92:EE:53,bridge=vmbr2,tag=5numa: 0
ostype: win7
sata0: local-lvm:vm-402-disk-1,size=200G
sata1: local-lvm:vm-402-disk-3,size=65G
scsihw: virtio-scsi-pci
smbios1: uuid=329004e4-d941-4bde-9421-7023c50367db
sockets: 1
I know we should have used virtio for drive(s). But it won't boot because it misses drivers. No idea how we preload them.
pveversion -v:
proxmox-ve: 5.1-25 (running kernel: 4.13.4-1-pve)
pve-manager: 5.1-35 (running version: 5.1-35/722cc488)
pve-kernel-4.13.4-1-pve: 4.13.4-25
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-15
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-2
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.0-2
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.2-pve1~bpo90
Any thoughts?
