PVE 5.1: KVM broken on old CPUs

Discussion in 'Proxmox VE: Installation and configuration' started by profpolymath, Oct 24, 2017.

  1. sevo44

    sevo44 New Member

    Joined:
    Oct 31, 2017
    Messages:
    1
    Likes Received:
    0
    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 !
     
  2. chOzcA75vE0poCY0F6XC

    Joined:
    Oct 26, 2017
    Messages:
    8
    Likes Received:
    0
    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.
     
  3. superbit

    superbit New Member

    Joined:
    Apr 17, 2012
    Messages:
    20
    Likes Received:
    0
    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?
     
  4. fabian

    fabian Proxmox Staff Member
    Staff Member

    Joined:
    Jan 7, 2016
    Messages:
    3,195
    Likes Received:
    494
    the regular kernels in the PVE repo don't contain the test commit (yet)..
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. superbit

    superbit New Member

    Joined:
    Apr 17, 2012
    Messages:
    20
    Likes Received:
    0
    It's a pity, then I and my old server will be waiting.
    Thanks a lot for your help Fabian.


     
  6. fabian

    fabian Proxmox Staff Member
    Staff Member

    Joined:
    Jan 7, 2016
    Messages:
    3,195
    Likes Received:
    494
    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 ;))
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    superbit likes this.
  7. vankooch

    vankooch New Member

    Joined:
    Nov 5, 2017
    Messages:
    12
    Likes Received:
    0
  8. nixmomo

    nixmomo Member
    Proxmox Subscriber

    Joined:
    Sep 13, 2014
    Messages:
    65
    Likes Received:
    2
    Is it fixed now in the upstream kernels?
     
  9. cybermcm

    cybermcm Member

    Joined:
    Aug 20, 2017
    Messages:
    88
    Likes Received:
    10
    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
     
  10. ktecho

    ktecho Member

    Joined:
    Jun 6, 2016
    Messages:
    47
    Likes Received:
    0
    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!
     
  11. cybermcm

    cybermcm Member

    Joined:
    Aug 20, 2017
    Messages:
    88
    Likes Received:
    10
    ktecho likes this.
  12. pacow

    pacow New Member

    Joined:
    Nov 28, 2017
    Messages:
    2
    Likes Received:
    0
    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?
     
  13. fabian

    fabian Proxmox Staff Member
    Staff Member

    Joined:
    Jan 7, 2016
    Messages:
    3,195
    Likes Received:
    494
    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
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. cybermcm

    cybermcm Member

    Joined:
    Aug 20, 2017
    Messages:
    88
    Likes Received:
    10
    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
     
  15. aderumier

    aderumier Member

    Joined:
    May 14, 2013
    Messages:
    203
    Likes Received:
    18
    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
     
  16. fabian

    fabian Proxmox Staff Member
    Staff Member

    Joined:
    Jan 7, 2016
    Messages:
    3,195
    Likes Received:
    494
    the blue screen fix is part of 4.13.8-2-pve, the fix regarding the issue in this thread is not.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. cybermcm

    cybermcm Member

    Joined:
    Aug 20, 2017
    Messages:
    88
    Likes Received:
    10
    thx @fabian for the info, waiting for the next release ;-)
     
  18. jeanlau

    jeanlau Member

    Joined:
    May 2, 2014
    Messages:
    45
    Likes Received:
    4
    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,
     
    un1x0d likes this.
  19. fabian

    fabian Proxmox Staff Member
    Staff Member

    Joined:
    Jan 7, 2016
    Messages:
    3,195
    Likes Received:
    494
    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
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    superbit and cybermcm like this.
  20. cybermcm

    cybermcm Member

    Joined:
    Aug 20, 2017
    Messages:
    88
    Likes Received:
    10
    Just tested the new kernel -> works; great work guys! and thank you again for your efforts
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice