Search results

We use ceph as FS on a cluster with 7 nodes. This cluster is used for testing, development and more. Today one of the nodes died. Since all the LXC and KVM are stored on ceph storage, they are completely there, but the configuration of the guests is not available since it's stored on the node...

Ah, yes, I just checked and it does happen although it's quick.

I'm not sure what you mean. I use ceph as FS and both LXC and KVM machines are migrated to other nodes easily. I have never noticed any problem with LXC's in this regard?

Yes, indeed, I'm doing that at the moment. I prefer to use LXC's whenever possible, which it why I gave it a shot...

I actually did install it, and all seems to be installable (using the installation instructions for Proxmox on Debian Bulleye), but corosync doesn't run despite using separate VLAN for the lxc's... I was hoping to that there is a way around whatever the problem is. * corosync.service -...

Hi all, Is it possible to create a virtual proxmox cluster in lxc instances? I'm planning to create a test cluster to experiment with Terraform, so if I can do that in 3 linux containers (create a node in each), it would be the lowest resource usage. Of course I can use full Qemu KVM guests...

I changed the weight of the OSD to be 30% less and that rebalanced the data nicely, so a little manual tuning had the desired effect.

I'm afraid the drive tech of these machines is substantial different. The S1 is a Sunfire X4150 with 2.5" SAS drives, whereas the HP is a ProLiant DL320s G1 with 5.25" SATA drives :-) I'm going to try to adjust the weight of the OSD that's too full to see if I can bring it down that way...

Note: This is more of an effort to understand the system works, than to get support. I know PVE 5 is not supported anymore... I have a 7 node cluster which is complaining that: root@s1:~# ceph -s cluster: id: a6092407-216f-41ff-bccb-9bed78587ac3 health: HEALTH_WARN 1...

Would a restart not clear the arp tables anyway? I restarted everything multiple times, and it seemed to make no difference.

I share your sentiment and think PVE should be made "cloud native" as you call it. A great additional, which I have only recently started playing with, is SDN integration into the GUI. To have formal kubernetes support would be really great! As far as auto-creation of clusters is concerned...

As with the other issue I could not resolve once I cleaned up the old bridges (how can that be??) and restarted the node, everything came up daisies. For the life of me, I cannot explain it, and I hope I don't have to plough through weeks like this again! o_O:cool:

This is weird. I removed the bridge VLAN11 from the SDN and recreate it, then assigned the bridge to the applicable devices and it works. 100% the same as what I had before. This was driving me mad and now it has just numbed me... At least it's working now. Some more feedback: I think this...

I have a few vlans set up manually as can be seen from my config here: I have now established that VLAN 35 is actually working 100%, one I set up manually as being eth2.35 but not VLAN aware. Now for the SDN config... I'll compare the generated config with the manual one.

After a debug session with NVidia on the Mellanox switch, we have found that the switch is not the culprit and it actually registering the proxmox nic mac addresses and passing the traffic. So it's back to the config of proxmox is seems.

I have four nodes with LAN addresses 192.168.131.1, .2, .3 and .4 . These are all configured identically except for the difference of the last octet of an ip address. So NodeA has .1, B has .2, C has .4 and so on. NodeB for example: vmbr0 is the LAN and it's is also the LAN on a pfSense...

They can only ping each other when they're on the same node. I corrected myself after posting that in the first message, so apologies if that was not clear. I have since found that there are messages on the switch that say the VLAN is being filtered, so I've taken it up with their tech support.

If that was the case, then I would be able to ping at least the host node's address from the windows guest, but I can't. I have now configured an Ubuntu LXC, so test that. The address is 192.168.142.91. If I have the LXC running on the node where the pfSense guest is running, then I can ping...

Thanks for that clarification! So I should really just set up a non-VLAN aware Vnet and work with that for now. So maybe I should rephrase my problem then: If I have set up a Vnet and Zone, it creates a bridge tagged with the VLAN. Then, when I add that bridge to a KVM guest machine, the...

CORRECTION: On checking this again, here is what I actually get: I can ping the first pfSense VLAN 11 address from any node. (192.168.142.252) I cannot ping the backup pfSense VLAN 11 address from any node, nor from the first pfSense (192.168.142.253) I can ping the CARP virtual IP from any...