Search results

  1. G

    KVM virtualisation configured, but not available.

    Sorry for delay in coming back I'm not sure how to update the Proxmox server or the kernel more specifically. The current version of Proxmox I have is just based on the latest .iso available which I downloaded from here (7.1-2) I then made this into a bootable usb to install. Is there a...
  2. G

    KVM virtualisation configured, but not available.

    Yeah it's an odd one! so output of pvevefsion is pve-manager/7.1-7/df5740ad (running kernel: 5.13.19-1-pve) Output of cat /proc/cpuinfo is: (prints out the below 8 times with minimal differences, assuming this is because it's per processor core or threads or something..) processor : 0...
  3. G

    KVM virtualisation configured, but not available.

    No, I'm not running Proxmox on any VMware or existing virtualisation method. This is installed directly on hardware with nothing else - for what it's worth, I've got it running on a HP Proliant MicroServer Gen 8, with an intel 1265L v2 CPU and 16gb RAM. Using an SSD as the disk where Proxmox is...
  4. G

    KVM virtualisation configured, but not available.

    The output from that command is: root@proxmoxgc:~# grep flags /proc/cpuinfo | tail -n 1 vmx flags : vnmi preemption_timer invvpid ept_x_only flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest I have already tried disabling the KVM hardware in VM options but that just...
  5. G

    KVM virtualisation configured, but not available.

    Thanks for your reply. Yes the cpu supports both VT-d and virtualisation and my bios is up to date, it’s so strange I’ve had a proxmox server running before on the same hardware.. so not sure what else to do? Are there any additional configurations I need to check or add? Or specific commands...
  6. G

    KVM virtualisation configured, but not available.

    Hi! So I'm new to using Proxmox and apologies if this question has been asked many times before but i'm really struggling to resolve an issue that i currently getting on my server that i've recently set up. After creating a new VM (with no matter what config) I am getting this message when...