Search results

  1. S

    Upgraded gone wrong

    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.
  2. S

    Upgraded gone wrong

    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...
  3. S

    Backup - move - restore

    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...
  4. S

    Fencing

    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"...
  5. S

    Could not access KVM kernel module after upgradeing to 3.4-6

    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...
  6. S

    Could not access KVM kernel module after upgradeing to 3.4-6

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

    Could not access KVM kernel module after upgradeing to 3.4-6

    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'...
  8. S

    Could not access KVM kernel module after upgradeing to 3.4-6

    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.
  9. S

    Could not access KVM kernel module after upgradeing to 3.4-6

    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)...
  10. S

    Could not access KVM kernel module after upgradeing to 3.4-6

    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:~#
  11. S

    Could not access KVM kernel module after upgradeing to 3.4-6

    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.
  12. S

    Could not access KVM kernel module after upgradeing to 3.4-6

    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...
  13. S

    Could not access KVM kernel module after upgradeing to 3.4-6

    I've just tried rebooting the machine with all of the following and the same issue appears, so I guess it must be something else that has gone wrong 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
  14. S

    Could not access KVM kernel module after upgradeing to 3.4-6

    So just did a search and found the apt logs from the update. At the bottom of the Term log are some errors would this be what has possibly caused the problem? history log: Start-Date: 2015-06-07 14:45:48 Commandline: apt-get dist-upgrade Install: pve-kernel-2.6.32-39-pve:amd64 (2.6.32-156...
  15. S

    Could not access KVM kernel module after upgradeing to 3.4-6

    I've checked a few times now and from all I can see it is enabled. It was working fine before the update and even after the update it was working ok it was only after I rebooted the system that it stopped working and I assume that was when the kernel update/patch was applied. I've installed and...
  16. S

    Could not access KVM kernel module after upgradeing to 3.4-6

    Just an update this is still an issue, but disabling KVM Hardware virtulization on the VM appears to let the VM's start up, but very slowly. Any ideas?
  17. S

    Could not access KVM kernel module after upgradeing to 3.4-6

    I did an upgrade today of Proxmox to version 3.4-6 I did not take a note of the previose version which was 3.4-something. I've done upgrades in the past and they have been fine. I was told after the update that there had been a patch to the kernal ( think that was the termenolgy might have been...
  18. S

    HA with this hardware

    Thanks for that. So I would still need a third machine for the fencing and if that is the case if I had a three node system would I then need a 4th machine to fence again or the three nodes would handle this them selves?
  19. S

    HA with this hardware

    I just wanted to get a straight answer regarding setting up Proxmox with HA. I have two physical servers HP DL360's G6 & I'm about to get some storage which will give me an NFS storage location. 2x HP DL360 G6 1x NFS Storage 1x Network Switch Will Proxmox HA work with these bits of hardware or...
  20. S

    DRBD config issues

    Thanks for the advice. I've since rebuilt again and it seems to be working now. No offense taken I'm trying to get my head around how the whole system works and how to put it together correctly so I can start to put it into testing and then into production. To be honest I'll probably go with a...