Windows 2016 crashes whole pve 5.2 system

Discussion in 'Proxmox VE: Installation and configuration' started by djzort, Jun 14, 2018 at 11:50.

  1. djzort

    djzort New Member

    Aug 8, 2013
    Likes Received:
    Im running a single Windows 2016 server essentials VM, but every few hours (max 2 days) the whole system crashes and reboots.

    I have captured kernel dumps, but there doesnt seem to be a debug package to assist in analyzing.

    pveversion --verbose
    proxmox-ve: 5.2-2 (running kernel: 4.15.17-2-pve)
    pve-manager: 5.2-1 (running version: 5.2-1/0fcd7879)
    pve-kernel-4.15: 5.2-2
    pve-kernel-4.15.17-2-pve: 4.15.17-10
    pve-kernel-4.15.17-1-pve: 4.15.17-9
    pve-kernel-4.15.15-1-pve: 4.15.15-6
    corosync: 2.4.2-pve5
    criu: 2.11.1-1~bpo90
    glusterfs-client: 3.8.8-1
    ksm-control-daemon: not correctly installed
    libjs-extjs: 6.0.1-2
    libpve-access-control: 5.0-8
    libpve-apiclient-perl: 2.0-4
    libpve-common-perl: 5.0-32
    libpve-guest-common-perl: 2.0-16
    libpve-http-server-perl: 2.0-9
    libpve-storage-perl: 5.0-23
    libqb0: 1.0.1-1
    lvm2: 2.02.168-pve6
    lxc-pve: 3.0.0-3
    lxcfs: 3.0.0-1
    novnc-pve: 0.6-4
    proxmox-widget-toolkit: 1.0-18
    pve-cluster: 5.0-27
    pve-container: 2.0-23
    pve-docs: 5.2-4
    pve-firewall: 3.0-9
    pve-firmware: 2.0-4
    pve-ha-manager: 2.0-5
    pve-i18n: 1.0-5
    pve-libspice-server1: 0.12.8-3
    pve-qemu-kvm: 2.11.1-5
    pve-xtermjs: 1.0-5
    qemu-server: 5.0-26
    smartmontools: 6.5+svn4324-1
    spiceterm: 3.0-5
    vncterm: 1.5-3
    im just running in straight LVM thinpool storage

    Architecture:          x86_64
    CPU op-mode(s):        32-bit, 64-bit
    Byte Order:            Little Endian
    CPU(s):                24
    On-line CPU(s) list:   0-23
    Thread(s) per core:    2
    Core(s) per socket:    6
    Socket(s):             2
    NUMA node(s):          1
    Vendor ID:             GenuineIntel
    CPU family:            6
    Model:                 44
    Model name:            Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz
    Stepping:              2
    CPU MHz:               2293.475
    BogoMIPS:              5333.99
    Virtualization:        VT-x
    L1d cache:             32K
    L1i cache:             32K
    L2 cache:              256K
    L3 cache:              12288K
    NUMA node0 CPU(s):     0-23
    Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 popcnt aes lahf_lm pti tpr_shadow vnmi flexpriority ept vpid ibpb ibrs stibp dtherm arat
    cat 100.conf
    agent: 1
    bootdisk: virtio0
    cores: 4
    ide2: local:iso/virtio-win-0.1.149.iso,media=cdrom,size=310276K
    memory: 65536
    name: sdp01
    net0: virtio=00:de:ad:be:ef:00,bridge=vmbr1
    numa: 1
    onboot: 1
    ostype: win10
    scsihw: virtio-scsi-pci
    smbios1: uuid=244f5178-d35c-45ea-b336-3f209d0f2139
    sockets: 2
    virtio0: local-lvm:vm-100-disk-1,size=300G
    virtio1: local-lvm:vm-100-disk-2,size=100G
    disabling c-states didnt seem to help at all

    cat /proc/cmdline
    BOOT_IMAGE=/vmlinuz-4.15.17-2-pve root=/dev/mapper/pve-pve--root ro quiet nmi_watchdog=0 crashkernel=256M
    this didnt help at all but is in place
    cat kvm.conf
    # Win2016 bsod install workaround - see
    options kvm ignore_msrs=1

    any thoughts? im worried the cpu might be too old?
  2. Alwin

    Alwin Proxmox Staff Member
    Staff Member

    Aug 1, 2017
    Likes Received:
    Did you re-install the Win2016 after setting the ignore_msrs?
  3. djzort

    djzort New Member

    Aug 8, 2013
    Likes Received:
    Installation completed without this setting, the crash seems to happen quite infrequently (hours to days) with it on or off.

    Does reinstallation with the setting on impact the install?

    I would like to look at the vmcore but there doesnt seem to be a debug package? this would be extremely helpful - is there any reason this isnt available?

    I have adjusted the CPU from kvm64 to Westmere (to match the x5650) - 24 hours later it's still up but still too early to tell.
  4. mailinglists

    mailinglists Member

    Mar 14, 2012
    Likes Received:
    If you want to match host exactly, there is also host option (scroll down to bottom).
  5. djzort

    djzort New Member

    Aug 8, 2013
    Likes Received:
    excellent tip and much appreciated. that will be my next adjustment if this current configuration doesnt last longer than 48 hours
  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