VM Windows 2012 R2 - random shutdown

Discussion in 'Proxmox VE: Installation and configuration' started by TomaszF, Mar 15, 2019 at 12:53.

  1. TomaszF

    TomaszF New Member

    Joined:
    Mar 14, 2019
    Messages:
    4
    Likes Received:
    0
    Hello,

    i have VM with Windows Serwer 2012 R2.

    VM is shutdown itself randomly.

    VM config:
    Code:
    root@pve:~# qm config 100
    balloon: 0
    bootdisk: virtio0
    cores: 20
    ide2: local:iso/virtio-win-0.1.164.iso,media=cdrom,size=362130K
    memory: 194560
    name: WindowsServer
    net0: virtio=F2:53:1B:69:47:BC,bridge=vmbr0
    numa: 0
    ostype: win8
    scsi1: local-lvm:vm-100-disk-0,cache=writeback,size=600G
    scsihw: virtio-scsi-pci
    smbios1: uuid=7cd84469-93c2-4e10-8c44-e69c7120a097
    sockets: 2
    vmgenid: 142e7aed-40ef-4689-baf3-603417dc1bb8


    pveversion
    Code:
    root@pve:~# pveversion -v
    proxmox-ve: 5.3-1 (running kernel: 4.15.18-10-pve)
    pve-manager: 5.3-8 (running version: 5.3-8/2929af8e)
    pve-kernel-4.15: 5.3-1
    pve-kernel-4.15.18-10-pve: 4.15.18-32
    corosync: 2.4.4-pve1
    criu: 2.11.1-1~bpo90
    glusterfs-client: 3.8.8-1
    ksm-control-daemon: 1.2-2
    libjs-extjs: 6.0.1-2
    libpve-access-control: 5.1-3
    libpve-apiclient-perl: 2.0-5
    libpve-common-perl: 5.0-44
    libpve-guest-common-perl: 2.0-19
    libpve-http-server-perl: 2.0-11
    libpve-storage-perl: 5.0-36
    libqb0: 1.0.3-1~bpo9
    lvm2: 2.02.168-pve6
    lxc-pve: 3.1.0-2
    lxcfs: 3.0.2-2
    novnc-pve: 1.0.0-2
    proxmox-widget-toolkit: 1.0-22
    pve-cluster: 5.0-33
    pve-container: 2.0-33
    pve-docs: 5.3-1
    pve-edk2-firmware: 1.20181023-1
    pve-firewall: 3.0-17
    pve-firmware: 2.0-6
    pve-ha-manager: 2.0-6
    pve-i18n: 1.0-9
    pve-libspice-server1: 0.14.1-1
    pve-qemu-kvm: 2.12.1-1
    pve-xtermjs: 3.10.1-1
    qemu-server: 5.0-45
    smartmontools: 6.5+svn4324-1
    spiceterm: 3.0-5
    vncterm: 1.5-3
    zfsutils-linux: 0.7.12-pve1~bpo1
    I'm beginner user Proxmox - i don't know which logs will by usefull in this case.

    Best regards.
     
  2. tom

    tom Proxmox Staff Member
    Staff Member

    Joined:
    Aug 29, 2006
    Messages:
    13,338
    Likes Received:
    375
    what physical hardware do you use (number and details of your physical CPUs, how much memory (RAM)?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. TomaszF

    TomaszF New Member

    Joined:
    Mar 14, 2019
    Messages:
    4
    Likes Received:
    0
    I have reduced the number of VM cores.
    The VM has been working properly for two hours.

    My actual config:
    Code:
    root@pve:~# qm config 100
    balloon: 0
    bootdisk: virtio0
    cores: 10
    ide2: local:iso/virtio-win-0.1.164.iso,media=cdrom,size=362130K
    memory: 163840
    name: WindowsServer
    net0: virtio=F2:53:1B:69:47:BC,bridge=vmbr0
    numa: 0
    ostype: win8
    scsi1: local-lvm:vm-100-disk-0,cache=writeback,size=600G
    scsihw: virtio-scsi-pci
    smbios1: uuid=7cd84469-93c2-4e10-8c44-e69c7120a097
    sockets: 2
    vmgenid: 142e7aed-40ef-4689-baf3-603417dc1bb8
    My hardware:
    • DELL PowerEdge R620
    • 2x 10Core E5-2680 V2 2,8Ghz
    • 192GB DDr3
     
  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