Kernel pve-kernel-4.13.8-2-pve fixes this perfectly, in our case. We upgraded the kernel yesterday evening and all 7 VMs are still running perfectly this morning... 
Blue screen with 5.1
- Thread starter cybermcm
- Start date
kernel is available via pve-no-subscription now as well!
Agreed. The new kernel fixed the problemKernel pve-kernel-4.13.8-2-pve fixes this perfectly, in our case. We upgraded the kernel yesterday evening and all 7 VMs are still running perfectly this morning...
Upgraded with the new kernel 3 hosts in a cluster, no problems with Windows VMs so far, I'll try to enable again vzdump backup of Windows VMs (I noticed I had more BSD when vzdump backups were enabled) and keep watching the situation.
Next step I hope will be upgrade to CEPH Luminous 12.2.2 that should solve a memory leak from OSD daemon, that is constantly raising RAM usage in my CEPH OSDs
Next step I hope will be upgrade to CEPH Luminous 12.2.2 that should solve a memory leak from OSD daemon, that is constantly raising RAM usage in my CEPH OSDs
Since installing pve-kernel-4.13.8-2-pve from testing 'pveversion -v' reports that packages are not correctly installed. Perhaps Proxmox should consider bumping version numbers when commercial support customers are asked to install test kernels?
How do we install the official 4.13.8-2-pve kernel to clear the error?
How do we install the official 4.13.8-2-pve kernel to clear the error?
Code:
[admin@kvm5e ~]# pveversion -v
proxmox-ve: not correctly installed (running kernel: 4.13.8-2-pve)
pve-manager: 5.1-36 (running version: 5.1-36/131401db)
pve-kernel-4.13.8-2-pve: 4.13.8-28
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.3-pve1~bpo9
ceph: 12.2.1-pve3
@David Herselman
This happend because you removed the pve-kernel-4.13.8-1-pve.
You must just install proxmox-ve.
> apt install proxmox-ve
This happend because you removed the pve-kernel-4.13.8-1-pve.
You must just install proxmox-ve.
> apt install proxmox-ve
new kernel is available on pvetest (pve-kernel-4.13.8-3-pve with version 4.13.8-29):
- cherry-pick KVM fix for old CPUs
- cherry-pick / backport IB fixes
- cherry-pick vhost perf regression and mem-leak fix
- cherry-pick final Windows BSOD fix
Hi All
Yes moving back the OS to XP/2003 has worked for me also, I was at my wit's end with this one as I migrated from a damaged old server to a temp new server with Pmox 5.1. Ones crash after the other.
Unfortunately I'm not a Linux head, just sbs windows. Is it possible to update the PVE kernal without damaging my proxmox installation?
Yes moving back the OS to XP/2003 has worked for me also, I was at my wit's end with this one as I migrated from a damaged old server to a temp new server with Pmox 5.1. Ones crash after the other.
Unfortunately I'm not a Linux head, just sbs windows. Is it possible to update the PVE kernal without damaging my proxmox installation?