After Proxmox VE 5.2-10 Update Windows VM doesnt start

Discussion in 'Proxmox VE: Installation and configuration' started by elyday, Nov 10, 2018.

Tags:
  1. elyday

    elyday New Member

    Joined:
    Nov 10, 2018
    Messages:
    3
    Likes Received:
    0
    Hello,

    my Windows VM does not want to start after the update from 4.x to 5.2-10. As an error I get

    Hyper-V SynIC is not supported by kernel
    kvm: kvm_init_vcpu failed: Function not implemented

    back.

    This is what I can offer you:
    root@root590:/etc# pveversion -v
    proxmox-ve: 5.2-2 (running kernel: 4.4.13-2-pve)
    pve-manager: 5.2-10 (running version: 5.2-10/6f892b40)
    pve-kernel-4.15: 5.2-11
    pve-kernel-4.15.18-8-pve: 4.15.18-28
    pve-kernel-4.4.134-1-pve: 4.4.134-112
    pve-kernel-4.4.95-1-pve: 4.4.95-99
    pve-kernel-4.4.40-1-pve: 4.4.40-82
    pve-kernel-4.4.13-2-pve: 4.4.13-58
    corosync: 2.4.2-pve5
    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.0-8
    libpve-apiclient-pearl: 2.0-5
    libpve-common-perl: 5.0-41
    libpve-guest-common-perl: 2.0-18
    libpve-http-server-perl: 2.0-11
    libpve-storage-perl: 5.0-30
    libqb0: 1.0.1-1
    <font color=#38B0DE>-==- Proudly Presents
    lxc-pve: 3.0.2+pve1-3
    lxcfs: 3.0.2-2
    novnc-pve: 1.0.0-2
    proxmox widget toolkit: 1.0-20
    pve-cluster: 5.0-30
    pve-container: 2.0-29
    pve-docs: 5.2-9
    pve-firewall: 3.0-14
    pve firmware: 2.0-6
    pve-ha-manager: 2.0-5
    pve-i18n: 1.0-6
    pve-libspice-server1: 0.14.1-1
    pve-qemu-kvm: 2.12.1-1
    pve-xtermjs: 1.0-5
    qemu-server: 5.0-38
    smartmontools: 6.5+svn4324-1
    spiceterm: 3.0-5
    vncterm: 1.5-3
    root@root590:/etc# sqm config 118
    bootdisk: ide0
    cores: 8
    ide0: SSD:118/vm-118-disk-1.qcow2,size=20G
    ide2: local:iso/WindowsServer2012x64_EN.iso,media=cdrom
    memory: 7168
    name: MC
    net0: e1000=1E:B7:E3:D1:99:3D,bridge=vmbr0
    numa: 0
    ostype: win8
    scsihw: virtio-scsi-pci
    smbios1: uuid=3cf62827-5352-4c47-a42b-c9df4be5ddd2
    sockets: 1
     
  2. tom

    tom Proxmox Staff Member
    Staff Member

    Joined:
    Aug 29, 2006
    Messages:
    13,082
    Likes Received:
    342
    Why do you run still this very old kernel? You installed already latest 4.15, but it looks like you missed to reboot your host.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. elyday

    elyday New Member

    Joined:
    Nov 10, 2018
    Messages:
    3
    Likes Received:
    0
    I have rebooted the machine several times since the update
     
  4. dcsapak

    dcsapak Proxmox Staff Member
    Staff Member

    Joined:
    Feb 1, 2016
    Messages:
    2,775
    Likes Received:
    251
    then you have configured your system to run from the 4.4 kernel, please boot your machine with the newer kernel, otherwise this will not work
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. elyday

    elyday New Member

    Joined:
    Nov 10, 2018
    Messages:
    3
    Likes Received:
    0
    And how can i configure that the system will boot with the newer kernel?
     
  6. dcsapak

    dcsapak Proxmox Staff Member
    Staff Member

    Joined:
    Feb 1, 2016
    Messages:
    2,775
    Likes Received:
    251
    normally this is done automatically, the person which configured this would have to know
    but i would check /etc/default/grub for example
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  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