Search results

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

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

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.

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

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

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

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

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.

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

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

According to my information (net) this is not the case. linux has a timeout of 300s as aging timeout, but the garbage collection that really removes the entries can be delayed for another 30s or even more. So all docs say you may end up between 5-10 minutes at worst. And that's about my...

Well that's hard to tell now. I already had to set all the corresponding bridges by hand to 300. Nevertheless I checked the other bridges in the boxes (there are 5). And they all show the same "30000").So I guess the major issue is the different arp timeouts of the guest producing the fake tcp...

Hello, well, you are right with the arp explanation. In the meantime I found a workaround that does work. I made a cronjob on a guest on host 2 that sends arping -fc1 to every guest that falsely reaches the guest on host3. This leads to the corresponding macs being re-added to the bridges on...

Hello all, hm, I had to find out that this above "workaround" does not work. After some hour runtime the thing is exactly the same with the new "auto" macs. The setup consists of 3 proxmox hosts with a trunk port connected over 2 switches. Host 1 has the guest, host 2 shows the mac in the...

Hello all, regarding this problem I found something that may be helpful to others or for tracking down the problem. It seems that some (all?) of the duplicated packets have a destination mac that is preconfigured in the corresponding guest network setup. In my case they start with "52:54" or...

Hello all, I have a pretty standard setup for several linux guests on Proxmox. Lately I found out by monitoring the guest interfaces with snmp that there is traffic I cannot explain. So I tried to find the cause for it and found out that every guest connected to the same bridge and subnet gets...

Sure, here: https://pve.proxmox.com/wiki/VNC_Client_Access and last sentence reads: "Note: Using this method it not possible to set a VNC password. " (which means vnc access config via config file)

I just had to read in the wiki that when configuring vnc for a guest it is not possible to use a password. This is really unusable for customer access. How do you think one should enable customers to access their corresponding guests?

Can you please elaborate what that means. "containers" like "LXC containers" ? We have none in the setup. We are talking about the vm list on the left of the web gui... (as an example)

So there are no coders in your staff? Alphabetical sorting of a given list is "not so easy to implement" ?!? (sorry, couldn't resist)