Recent content by skeates

Thanks for that. The # pveversion -v returned nothing so I did the # apt-get install proxmox-ve which resolved the problem in less than 2min. Thank you for your help solved a lot of hassle.

I decided to take the plunge and upgrade my Proxmox install from 4.4 to 5 having done this in the past from 2 to 3 and 3 to 4 I never had a problem I just followed the instructions and away we went. However it seems to have gone wrong this evening. The machine boots and I can get into it, but...

I have an install of Proxmox4 that I have some VM's running on. This is on a local server. I've setup proxmox with OVH and in the process of moving my VM's across from my local server to the hosted one. Some of the VM's I just re-created from scratch as there was not much involved in them. I...

I'm just in the process of settting up fencing to test HA. I've gone through the Fencing wiki and I am going to attempt to do this with ipmi. I have modified the example config file to meet my needs, but at the bottom of the file is a section <service autostart="1" exclusive="0"...

Thank you Sir, That most certainly resolved the issue. It's wired that, that file was there if it is not installed by the system and I would not have created it manually. There is another file in that folder called fbdev-blacklist.conf not sure is that should be there either. It's contents are...

found this: root@proxmox:/etc/modprobe.d# cat kvm-intel.conf options kvm-intel nested=1 root@proxmox:/etc/modprobe.d#

md5 below root@proxmox:~# md5sum /lib/modules/2.6.32-39-pve/kernel/arch/x86/kvm/kvm-intel.ko 55e9820ca5873596885337aaff5a0eeb /lib/modules/2.6.32-39-pve/kernel/arch/x86/kvm/kvm-intel.ko root@proxmox:~# dmesg below kvm_intel: Unknown parameter `nested'kvm_intel: Unknown parameter `nested'...

I tried these versions 2.6.32-39-pve 2.6.32-37-pve 2.6.32-34-pve 2.6.32-32-pve 2.6.32-26-pve all with the same result. So my guess is something else on the system has gone wrong during the update.

Tried that it seems to error so not sure if that means something is not installed correctly or something has become corrupt root@proxmox:~# modprobe kvmroot@proxmox:~# modprobe kvm_intel ERROR: could not insert 'kvm_intel': Unknown symbol in module, or unknown parameter (see dmesg)...

Outputs nothing same as the previous command root@proxmox:~# #uname -a root@proxmox:~# Just ran root@proxmox:~# uname -a Linux proxmox 2.6.32-39-pve #1 SMP Fri May 8 11:27:35 CEST 2015 x86_64 GNU/Linux root@proxmox:~#

root@proxmox:~# #lsmod|grep kvm root@proxmox:~# So that would imply it is not enabled, but there is no reason for it not to be as it was working prior to the update.

That was probably me trying find out what was going on initially. I just ran the following root@proxmox:~# apt-get remove qemu-utils Reading package lists... Done Building dependency tree Reading state information... Done Package 'qemu-utils' is not installed, so not removed 0 upgraded...