Search results

That's correct, but doesn't OpenVSwitch supports IEEE_802.1ad ?

I setup OVS switch on 10 nodes which are interconnected via GRE tunnels, but I can see Proxmox is not letting us create more than 4094 vlans because tag ID larger than 4094 is not validated in Proxmox interface or API. Is there any restriction based on GRE overlay that prevent us having more vlans?

As far as I know recent versions of GuestAgent support executing any commands, therefor it should be possible to monitor guests from host, is that true?

In proxmox documents I can see it's advised to set rstp_designated_path_cost for physical ports, but as I want to create a mesh network with openvswitch containing 20 nodes which all are connected together via GRE is it necessary to set path_cost for GRE too? I've tried command below but it...

I wonder if there's any exporter that gather guest usage information from inside of them via GuestAgent and export them to prometheus? If not is it reasonable to use GuestAgent for gathering resource usage of VMs?

It fixed by using "-m physicaldev --physdev-in tap101i0" instead of -i, and it's because tap is layer 2 not layer 3

I've used a simple iptables rule to test some idea, but I can see it's not picking any packet on tap interface. Is that normal? root@node01:~# iptables -I FORWARD -i tap101i0 results: root@node01:~# iptables -L FORWARD -v -n Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target...

So as I've L2 connectivity between all nodes, how can I avoid establishing GRE between all pairs of servers?

My servers are all connected via layer2 switches, but I can't add so many vlans on them.

I've a cluster of 40 Proxmox nodes and I want to start offer private network to my clients, Each client of me may have few VMs on different nodes, and it's not static, they may add/remove VMs. My question is if I want to setup OVS based private networking it's necessary to add GRE for each two...

I've build a cloned VM using linked clone from Proxmox interface, but consider when I want to rebuild that VM, I will need to remove the primary disk of that VM and add an other one which is based on an other base image, ( for example changing the OS of that VM from Ubuntu to CentOS ) Is there...

And this also got fixed by "modprobe xprtrdma" I've add them to /etc/modules to auto load them after reboot

After running "modprobe ib_umad" on both Proxmox nodes, OpenSM detects the ports but still the link is in initialization status: service opensm status ● opensm.service - LSB: Start opensm subnet manager. Loaded: loaded (/etc/init.d/opensm; generated) Active: active (exited) since Fri...

I'm connecting two Proxmox servers with ConnectX-3 cards, they can see each other in Ethernet mode but in ib mode, the link remains in Initiating state despite physical link up status. Also in opensm logs I can see that it cant detect ib ports while there are active. and both cards are in the...

Thanks, you are right indeed. I've figured it out by "--image-shared" option when creating fio image, like code below: rbd -p rbd create --size 2048 fio_test --image-shared

I've a SSD based Ceph cluster with 3 nodes, the read IOPS is about 250K with 96 parallel fio jobs ( running from 3 different nodes ), the reasults are fine. But the Write performance is not more than 2k IOPS when more than 1 parallel jobs is running. ( with only one job I can reach 15K write...

The card was faulty, Our vendor has changed that card for us. Sorry to bother.

Hello, I'm going to use Mellanox ConnectX-3 for Proxmox 5.4 but the kernel is not detecting it, while it's being detected fine by Windows on the same server. Any help on how to make it work? lspci | grep Mellanox returns empty result pveversion -v proxmox-ve: 5.4-1 (running kernel...

I guess it's monitor connection issue, because monitor service is up and running. Any help on how to troubleshoot it would be much appreciated.

I had a two node ceph cluster, It was working fine, but after adding new node to ceph cluster and there for joining it to proxmox cluster, one of my previous monitors went into unknown status despite it's running. Also the new monitor is in unknow status too. Please check the attached picture...