PVE 5.1: KVM broken on old CPUs

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 !
 
neiion said:
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 :)
Click to expand...

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.
 
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?
 
superbit said:
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?
Click to expand...

the regular kernels in the PVE repo don't contain the test commit (yet)..
 
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
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
 
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!
 
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?
 
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
 
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
 
cybermcm said:
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
Click to expand...
https://git.proxmox.com/?p=pve-kernel.git;a=summary


25 hours ago Fabian Grünbichler bump version to 4.13-28, bump ABI to 4.13.8-2-pve master commit | commitdiff | tree | snapshot
25 hours ago Fabian Grünbichler revert mmu changes causing bluescreens commit | commitdiff | tree | snapshot

so it's in 4.13.8-2-pve

the patch is here:
https://git.proxmox.com/?p=pve-kern...a;hb=777ee9fe67b12c9ee6918e40930f7f641474d364
 
the blue screen fix is part of 4.13.8-2-pve, the fix regarding the issue in this thread is not.
 
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
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
 
  • Like
Reactions: superbit and cybermcm
Just tested the new kernel -> works; great work guys! and thank you again for your efforts
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back