Search results

  1. S

    Problems joining new node with 6.4 to cluster with 6.0

    The thing is we would like to consolidate the cluster with new nodes and killing old ones. So the idea was to put in one new node (which is large enough to take the whole cluster vhosts) with 6.4, which is needed for update to 7.X anyway. So put in node, migrate everything to it, kill all old...
  2. S

    Problems joining new node with 6.4 to cluster with 6.0

    Hello all, I tried to join a new node today to an existing cluster with version 6.0-4. The new node has version 6.4 (I thought it would be a good idea to use the latest minor version). First everything went well, but after completion it turns out the node is not active in the cluster. It was...
  3. S

    Problem 9 virtio-Block devices zu konfigurieren

    Es ist ein Cluster, aber leider sind mittlerweile sehr viele VMs drauf und eine Migration aller VMs einer Node ist nicht mehr so ohne weiteres drin. Daneben bin ich sehr vorsichtig mit der Idee dass nach einem Update die geupdatete Node so ohne weiteres wieder in dem Cluster funktionieren wird...
  4. S

    Problem 9 virtio-Block devices zu konfigurieren

    Hm, das bedeutet wohl ich muss die Ursache selbst suchen. Es handelt sich um produktive Systeme wo ich nicht einfach mal so updaten kann (wegen der Downtime und wegen der unbekannten Stabilitaet des neuen Systems).
  5. S

    Problem 9 virtio-Block devices zu konfigurieren

    Hallo, vielen Dank fuer die Reaktion! Ich muss dazu zwei Dinge anmerken: 1. Das ist Proxmox 6.0.-4 2. Der Gast ist Linux Kernel 3.18.43 3. Ja, der Gast laeuft bei dem Versuch, das ging bist virtio7 einwandfrei ... Beides koennte Auswirkungen haben. Ich habe im Kernel-Source allerdings keinen...
  6. S

    Problem 9 virtio-Block devices zu konfigurieren

    Hallo zusammen, hat jemand eine Erklaerung dafuer warum ich es nicht schaffe das 9. virtio-blk Device hinzuzufuegen. Da erscheint folgender Fehler: Fehler: 400 Parameter verification failed. virtio8: hotplug problem - VM XXX qmp command 'query-pci' failed - got timeout Eigentlich hatte ich...
  7. S

    command 'apt-get update' failed: exit code 100

    I can add this one to the list of possibilities why the error message shows up: # apt-get update Get:1 http://security.debian.org buster/updates InRelease [65.4 kB] Get:2 http://ftp.de.debian.org/debian buster-updates InRelease [51.9 kB] Hit:3 http://download.proxmox.com/debian/pve buster...
  8. S

    How do I disable hyperthreading?

    Sorry for hijacking this thread, but as the OP seems to use a Mikrotik CHR and solve performance problems I'd like to jump in and ask pretty much in the same direction. We tried some CHRs in our setup and they are aweful in terms of performance. Even with their P-Unlimited license they are not...
  9. S

    [SOLVED] How to use ZFS VDEV as block device for vm?

    Ok, in the meantime I found out that my question probably misled you in the storage direction. But in fact I only searched for a possibility to mount some block device (which can be a zfs vdev) inside a vm. And guess what, striking easy: qm set VMID -scsi0 /dev/someblockdevice and you have a...
  10. S

    [SOLVED] How to use ZFS VDEV as block device for vm?

    Hello, it seems the common config for vm drives in proxmox is file-based. But of course qemu can do more. So how do I tell proxmox to use a zfs vdev as block device inside a vm? -- Regards
  11. S

    How to pool some cpu cores for some vms

    I can confirm that the lack of context switching across cores (which is in fact happening when pinning) is a big gain in performance. This was the first reason why I did the pinning in libvirt/qemu. If you pin a multi-cpu vm to cores and their hts you also gain performance with the caches...
  12. S

    How to pool some cpu cores for some vms

    In fact the setup is a lot faster this way. I can prove because I did the same setup both on proxmox and on libvirt/qemu (where cpu pinning is possible). It shows that on libvirt/qemu the load on the host is about 2 lower than on proxmox. The network latencies show the same thing. proxmox is...
  13. S

    How to pool some cpu cores for some vms

    The simple reason is overcommit of the cpus. There is simply a group of vms that are not so important. So I want this group to share a small amount of cores. Whereas some vms are very important, and I want these to have some cores exclusively.
  14. S

    How to pool some cpu cores for some vms

    Lets assume we have 32 cpu cores. How can I split some of them away in a pool (lets say 8 cores) and use them from some (not all) running vms? This is trivially possible with libvirt/qemu, but I have not found a way in proxmox. Any ideas? -- Regards PS: AFAIK there is no option for cpu pinning...
  15. S

    Proxmox using swap, the everlasting thread ...

    Hello all, We are using kernels 5.0.15-1-pve and set swappiness globally to 0 by sysctl and in all processes by using this script (Taken from another thread around this topic) On a host with few kvms this works as expected, (h)top shows zero used swap. But on a host with around 20 kvms things...
  16. S

    TigerVNC Server inside vm collides with noVNC console

    PS: Here is a link to the exact same problem: https://bbs.archlinux.org/viewtopic.php?id=246256
  17. S

    TigerVNC Server inside vm collides with noVNC console

    Hello, I tried to make a VNC service work inside a vm with TigerVNC. I had to find out that there seems to be a problem related to the noVNC console of the vm. You cannot start tigervnc server by systemd in the vm (arch linux), because of this crash: (EE) (EE) Backtrace: (EE) 0: /usr/bin/Xvnc...
  18. S

    Guest gets IP packets not aimed for it

    I doubt there is asymmetry involved. The problem only touches one subnet, all the involved vms are connected there. There is no bonding. The three proxmox hosts have a switch in front each. The three switches are connected with 10G.
  19. S

    Guest gets IP packets not aimed for it

    The thing is: we are not talking about pings as payloads but heavy tcp traffic. So it is unlikely that you really get the arp request in between the ongoing tcp stream. If you think there is another explanation for the observed problem than guests having longer arp timeouts than the bridges...
  20. S

    Guest gets IP packets not aimed for it

    And this is what I know: Now the problem is that the neighbor entry will not be deleted if it's being referenced. The main thing that you're going to have problems with is the reference from the ipv4 routing table. There's a lot of complicated garbage collection stuff, but the important thing...