PVE 5.1: KVM broken on old CPUs

sevo44

New Member
Oct 31, 2017
4
0
1
45
There were problems on the motherboard
====
11/09/2010
Vendor : Intel Corporation
Version : S5000.86B.15.00.0101.110920101604
-Board-
Name : S5000VSA
Vendor : Intel
====
Used test kernel and it worked
====
CPU(s)
8 x Intel(R) Xeon(R) CPU E5310 @ 1.60GHz (2 Sockets)

Kernel Version
Linux 4.13.4-1-pve #1 SMP PVE 4.13.4-26~vmxtest1 (Wed, 25 Oct 2017 10:59:18 +0200)
=====
A big thank you to c Russia !
 
Oct 26, 2017
11
0
6
25
I had a issue mounting shares also , this is how i fixed it https://forum.proxmox.com/threads/pve-5-1-cifs-share-issue-mount-error-112-host-is-down.37788/

hope it helps :)
Thanks for the hint, but I'm running an up-to-date FreeNAS system.
I've enabled SMB3_11 though, it was still om SMB3.0.
Maybe that helps.

@Thread
I've pulled the T5600 machine from the cluster, wasn't powerful enough. Can't help here without much hassle of setting things up the way they were. But it worked fine after the test kernel was installed.
 

superbit

New Member
Apr 17, 2012
20
0
1
Test kernel worked ok.
Code:
uname -a
Linux h01 4.13.4-1-pve #1 SMP PVE 4.13.4-26~vmxtest1 (Wed, 25 Oct 2017 10:59:18 +0200) x86_64 GNU/Linux
Today, I installed the same kernel number, updated from repository and I'm having problems with KVM again:
Code:
uname -a
Linux h01 4.13.4-1-pve #1 SMP PVE 4.13.4-26 (Mon, 6 Nov 2017 11:23:55 +0100) x86_64 GNU/Linux
I downgraded to test kernel and KVM returned to life again. What happened?
 

fabian

Proxmox Staff Member
Staff member
Jan 7, 2016
3,993
618
133
Test kernel worked ok.
Code:
uname -a
Linux h01 4.13.4-1-pve #1 SMP PVE 4.13.4-26~vmxtest1 (Wed, 25 Oct 2017 10:59:18 +0200) x86_64 GNU/Linux
Today, I installed the same kernel number, updated from repository and I'm having problems with KVM again:
Code:
uname -a
Linux h01 4.13.4-1-pve #1 SMP PVE 4.13.4-26 (Mon, 6 Nov 2017 11:23:55 +0100) x86_64 GNU/Linux
I downgraded to test kernel and KVM returned to life again. What happened?
the regular kernels in the PVE repo don't contain the test commit (yet)..
 

fabian

Proxmox Staff Member
Staff member
Jan 7, 2016
3,993
618
133
there is a final upstream fix which should be included in one of the next 4 .13 stable upstream releases, so either the next PVE kernel update or the one after will work out of the box again (just check the changelog, it will be mentioned ;))
 
  • Like
Reactions: superbit

cybermcm

Member
Aug 20, 2017
95
10
13
I checked pve-kernel-4.13.8-1-pve_4.13.8-27.changelog in the test repository, nothing in it about this bug for now
 

ktecho

Member
Jun 6, 2016
47
0
6
39
Can anyone share the upstream bug report to search for some info?

Is this just people that cannot start kvm machines? I'm having problems on a Win10 machine that gives me blue screens from time to time and I cannot seem to find a reason. Don't know if this could be the problem.

Thanks!
 

pacow

New Member
Nov 28, 2017
2
0
1
46
Just FYI and to confirm @cybermcm... This 4.13.8-1-pve #1 SMP PVE 4.13.8-27 kernel is now available in the stable (no-subscription) repo. It doesn't solve the KVM problem and there's no sign of it in the changelog. I assume a next kernel update would be more likely to include the fix?
 

fabian

Proxmox Staff Member
Staff member
Jan 7, 2016
3,993
618
133
the final version of the fix is slated for 4.15 (currently -rc1), given some further testing we'll cherry-pick it into our 4.13 based kernel
 

cybermcm

Member
Aug 20, 2017
95
10
13
new kernel was released yesterday, pve-kernel-4.13.8-2-pve_4.13.8-28, is this fix included (changelog doesn't mention it)? I'm currently not able to test it
 

aderumier

Member
May 14, 2013
203
18
18

fabian

Proxmox Staff Member
Staff member
Jan 7, 2016
3,993
618
133
the blue screen fix is part of 4.13.8-2-pve, the fix regarding the issue in this thread is not.
 

jeanlau

Member
May 2, 2014
45
6
8
Hello

Same issue here, with also an old Dell PowerEdge but it was working correctly before this kernel upgrade...
As Fabian says, latest released kernel ("4.13.8-2-pve") doesn't fix the KVM not loading correctly issue...
Thanks for the temporary fix : http://download.proxmox.com/temp/pve-kernel-4.13.4-1-pve_4.13.4-26~vmxtest1_amd64.deb
It allowed to be able to make my customer VMs working again (I also followed the other thread to set in grub the change as permanent in case of reboot.)
Of course, this is a temporary situation that can't last for too long so, thank you Proxmox team, to keep us informed as soon the issue will be corrected.
I think this thread concern a lot of people...

Thanks
Best Regards,
 
  • Like
Reactions: un1x0d

fabian

Proxmox Staff Member
Staff member
Jan 7, 2016
3,993
618
133
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
 

cybermcm

Member
Aug 20, 2017
95
10
13
Just tested the new kernel -> works; great work guys! and thank you again for your efforts
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE 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 your own in 60 seconds.

Buy now!