Search results

Stay serious, please. You are already the second staff member that read this thread. And none of the two found it worth the time making a feature request for it. If that is an easy process, it should likely take just as long as answering in the thread - for you. For me on the other hand - since...

Well, easy-going to tell that. But if you already happen to follow quite a lot of the important projects there is not much spare time left. And honestly I would not start at this topic, but rather with - why does a proxmox cluster node change its ssh keys on occasion (happened 3 times during the...

Lets simply end with the fact that proxmox does not have the feature (compared to libvirt/virt-manager) although it would be dead simple to implement. In our case there is no wind*ws involved.

That's really not our use case. We use read-only drives often as backups where you can examine an older setup, and you must not be able to write anything there, even if it is thrown away afterwards. Else you cannot judge if the status is as it was when this snapshot was done.

One would prefer an solution inside proxmox GUI of course. Fiddling with the file base isn't really that transparent in this case. I was pretty astonished though that libvirt/virt-manager supports this out-of-the-box (and it was often used in my environment) whereas here it isn't even something...

Believe someone with years experience with glusterfs: it is dead slow because the authors/company refuses to implement it as kernel drivers.

That's wrong. It _does_ work in every direction. A packet from vmbr5 to vmbr4 is tagged because the bridge port of vmbr5 is named vmbr4.8. So on an outgoing packet the 8 vlan id will be tagged on. The same goes one step deeper. As vmbr4 has enp5s0f0.1007 as bridge port all packets outgoing there...

Hello, I try to protect a (second) drive of some vm. With qemu/virt-manager it was easy to flag a drive read-only. But I cannot find a corresponding option in proxmox. How can I do that? The drive is an nfs-mounted raw file, btw. -- Regards Stephan

Ok, I understand your idea. But since the tagging is needed outside the proxmox cluster this is no option. But I found a solution that you already mentioned elsewhere. There is only one additional bridge needed: auto vmbr4 iface vmbr4 inet manual bridge-ports enp5s0f0.1007...

Got an idea. Maybe everything is a lot more transparent if I describe a potential setup for this whole story. Lets assume you have 5 boxes with one lan port each. Lets assume you have 2 switches. Lets assume you have a proxmox cluster. Now connect the 5 boxes to switch 1 and tag each switch...

No sorry, this was probably too bad of an explanation from my side. Of course I had to install ifupdown2 on every cluster node to be able to migrate the vm in question all over the cluster. And on every single installation the corresponding node booted right after apt-get install. In fact since...

No it is not. The guest attached to the outer vlan does of course create itself several vlans (the inner ones). And inside these vlans only those arp work that are not used in the host bridge attached to the inner vlan. Believe me that I know a thing or two about networking, and I have already...

Now we encountered other problems: 1) ARP between the external inner vlan and the newly created bridge does not work, in fact it seems indeed no arp at all works. The guest with its own vlan config (from other bridge) cannot arp to the guest on the inner vlan host bridge and both cannot arp to...

Ich versuche gerade eine Migration zwischen der fraglichen Node und einer anderen und das ist deutlich langsamer als zwischen anderen Nodes. Das bedeutet dass der Cluster tatsaechlich das 1 GBit/s Interface benutzt. Wie kann ich das aendern?

PS: I tried to install your ifupdown2 package but shot down a cluster node by doing that. I do not quite understand why it takes down the whole node and restarts just because of this installation ... PS2: After rebooting the node the dual tagged interface came up, which probably means ifupdown2...

Ok, the double vlan tagged interface definition does not work: # ifup enp5s0f0.1007.8 Error: 8021q: VLAN device already exists. ifup: ignoring unknown interface enp5s0f0.1007.8=enp5s0f0.1007.8

There are two use-cases by the guests: 1) One type of guest uses the bridged outer vlan and tags the inner vlan itself inside the guest linux 2) Another type of guest uses inner vlan host bridges as simple interfaces to communicate to type 1 guests vlan interface (defined inside the guest) The...

Hm, which means I would have to hand-configure all inner vlans needed by guests as bridges on every host of the cluster... I guess that's what "vlan-aware" was intended to replace :) Just checked: I have installed: ifupdown/stable,now 0.8.35 amd64 [installed]

Ok, I can confirm that your second code part works. I tried that. Unfortunately it does not solve the problem. It is the details that are complex: - I need one vlan-aware bridge for guests that should be attached to a single "inner" vlan, basically needing an interface like eth0.1008.25. - On...

Hallo zusammen, ich frage mich gerade warum ich in einem Cluster mit 3 Nodes fuer eine davon verschiedene IP-Adressen sehe, je nachdem wo man nachsieht. In der GUI unter "Rechenzentrum()" -> Übersicht / Knoten steht fuer eine der Nodes eine andere IP-Adresse als in der Shell erscheint per...