Search results

  1. S

    When you run an error Could not access KVM kernel module: No such file or directory

    I user all off pveupdate and pveupgrade first time when I started server all was ok but after update all the machines run longer
  2. S

    When you run an error Could not access KVM kernel module: No such file or directory

    $ pveversion -v proxmox-ve: 4.4-76 (running kernel: 4.4.35-1-pve) pve-manager: 4.4-1 (running version: 4.4-1/eb2d6f1e) pve-kernel-4.4.35-1-pve: 4.4.35-76 lvm2: 2.02.116-pve3 corosync-pve: 2.4.0-1 libqb0: 1.0-1 pve-cluster: 4.0-48 qemu-server: 4.0-101 pve-firmware: 1.1-10 libpve-common-perl...
  3. S

    When you run an error Could not access KVM kernel module: No such file or directory

    When you run an error Could not access KVM kernel module: No such file or directory failed to initialize KVM: No such file or directory TASK ERROR: start failed: command '/usr/bin/kvm -id 100 -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon...
  4. S

    Proxmox can not start a virtual machine

    Good day everyone, I have this problem, but I have included in the BIOS virtualisation, this error began to emerge after the apt-get update, what to do?

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!

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!