ich denke auch dass man das pauschal überhaupt nicht beantworten kann.
es hängt total vom use case ab.
wichtigkeit datenkonsistenz vs. wichtigkeit dienste-verfügbarkeit und und und.
>Are there any negative implications of such an approach?
complexity in backup code and chances that this accidentaly remains changed from the initial value on backup errors or other problems !?
it's seems a little bit uncommon to me, that...
Fair point on the blast radius. Any tool touching hypervisor networking needs respect.
The module is not just doing a blind apply though. A lot of the work went into making re-apply/reconcile safe:
SDN reload waits for the expected `vnet*`...
Sind halt 9 Arbeitsplätze auf einem von drei Hosts im produktiven Firmeneinsatz.
Abhaken tue ich das auch. Ich hätte es ohne deinen Beitrag noch nicht mal bemerkt;)
Meinen inneren Monk stört es aber schon.
For node 2 (the working node) - this has an Intel e1000e NIC and I had to disable NIC offloading (I implemented this fix https://gist.github.com/crypt0rr/60aaabd4a5c29a256b4f276122765237)
root@proxmox2:~# cat /etc/network/interfaces
# network...
For node 1 (the malfunctioning node)
root@proxmox1:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback
iface enp0s31f6 inet manual
auto vmbr0
iface vmbr0 inet static
address 192.168.1.131/24
gateway 192.168.1.1...
Hi,
thank you for the manual, but I see possible pitfalls.
With such design the Proxmox host seems like a single point of failure when it running the ZFS + LIO iSCSI storage layer.
It holds the actual data and exports it to both Windows cluster...
mind , that you should avoid default cache settings (= O_DIRECT) with qemu/kvm VMs on top of mdraid (containers are fine), otherwise you will risk inconsistencies in the raid, as mirror can silently break with directio writes going wrong.
this...
OK, so I came up with this brief patch against PVE/QemuServer/Cloudinit.pm:
diff --git a/src/PVE/QemuServer/Cloudinit.pm b/src/PVE/QemuServer/Cloudinit.pm
index c1311da8..b3d2e9e2 100644
--- a/src/PVE/QemuServer/Cloudinit.pm
+++...
This is the cause that also prevents systemd-resolved from working with cloud-init on Debian 13, at least when assuming ifupdown being used for VM network configuration (the default, and also used on our own images).
In the helper ifupdown...
Hope you’re all well.
I have a question that’s been wrecking my head for months now.
I have a 3 node cluster (Dell PowerEdge R7525) with the following drive configuration:
Node 1: 10x 2TB NVMe KINGSTON SKC2500M82000G in raidz2
Node 2: 10x 2TB...
Small update, there are old references in the auth list here is just one for reference:
{
"entity": "osd.8",
"key": "[REDACTED]"
"caps": {
"mon": "allow profile osd"...
If anyone knows how to cover all my bases for this; what I would like to try:
purge all references to pve5 from the cluster
remove ceph and any configurations from pve5 only
reinstall ceph from scratch on pve5
2 and 3 I can handle on my own...
Ciao a tutti ho bisogno di far funzionare usb port su windows 7 sp1 x64 . Ho provato scaricando vecchi driver virtio ma niente da fare , qualcuno puo darmi il link di un driver funzionante ? DEvo fa funzionare un ble mercurysys per applicazione...
I feel like there has to be an orphaned configuration somewhere. It keeps telling me there are references to pve5 when I both don't see any in the WebUI or from where I know to look in the terminal given my current knowledge.