Search results

  1. P

    not able to restore backup anymore

    When restoring a LXC container I got the this error: Parameter verification failed. (400) bwlimit: type check ('number') failed - got '' The same on my second Proxmox (not clustered). What can be wrong? first server version: proxmox-ve: 6.1-2 (running kernel: 5.3.13-1-pve) pve-manager: 6.1-4...
  2. P

    zfs as root file system booting extremely slow

    For a test with zfs as root file system I installed proxmox 3.4 on two different servers, with two hdd's in zfs raid-0. Once booted both machines are very fast for their age. But booting takes 45 minutes to more than an hour. As I have two Proxmox 3.3 servers now, that I will replace with new...
  3. P

    Article on Proxmox in Linux Magazine

    Last Linux Magazine (issue#150) has an article on Proxmox. Virtualization with the Proxmox Virtual Environment 2.2Virtualization Control RoomAuthor(s): Thomas Drilling The Proxmox Virtual Environment has developed from an insider’s tip to a free VMware ESXi/ vSphere clone. We show you how to...
  4. P

    qmrestore error message

    I got the following error message using qmrestore: dos not lock like a QemuServer vzdump backup I guess this should be: does not look like a QuemuServer vzdump backup. Peter
  5. P

    Turnkey brings Openvz containers with easy install on Proxmox

    Turnkey (http://www.turnkeylinux.org/) offers more than 30 ready made linux servers. I use them to install them on Proxmox under KVM. Now they bring them also as Openvz containers. On their website you find in the forum a howto to install them as easy as the Openvz containers offered by Proxmox...
  6. P

    Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead

    My syslog is full of the WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead What does this mean? I have some strange issues, like a backup not being able to restore. proxmox1:~# pveversion -v pve-manager: 1.7-12 (pve-manager/1.7/5490) running kernel...
  7. P

    small bug in dutch translation

    When removing a VM I get the message: Weet u zeker dat u VM %? wilt verwijderen? Dit zal de opgeslagen data permanent verwijderen The number of the VM is not presented. This is not a new bug. Maybe only in the dutch translation. pveversion: pve-manager: 1.7-12 (pve-manager/1.7/5490) running...
  8. P

    kvm change hdd from ide to virtio

    Since virtio is a better choice on kvm for the hdd interface I want to change that for my vm's. It works without a problem for the nic. But it is unclear to me whether it is possible for de hdd interface. So: is it possible en howto? I'm very happy with my proxmox servers. Great work. seen...
  9. P

    second hdd problem

    Hello, I have two proxmox in a cluster. On proxmox1 I added a second hdd (LVM) to a kvm vm with Freenas. Works perfect. But on proxmox2 I get the following error when opening the tab hardware on every kvm vm: [4513]ERR: 24: Error in Perl code: command '/sbin/vgchange -aly hdd101-c' failed...
  10. P

    cannot migrate kvm vms

    When I migrate a running kvm vm I get the error: volume 'local:103/vm-103-disk.qcow2' does not exist When I migrate it not running, the vm will be migrated, but will not start. openvz containers will be migrated without a problem. proxmox2:~# pveversion -v pve-manager: 1.4-10...
  11. P

    pve-kvm not correctly installed

    hi, I have a cluster of two proxmosses. After updating tot 1.4 i get this output on both of them by pveversion -v: pve-manager: 1.4-6 (pve-manager/1.4/4340) qemu-server: 1.1-4 pve-kernel...