In that case you can read all about it here:
https://wiki.debian.org/NetworkInterfaceNames
en: Prefix for Ethernet interfaces.
wl: Prefix for Wireless (WLAN) interfaces.
enpXsY: Derived from the PCI bus location. p stands for PCI bus number and...
We are pleased to announce the release of Proxmox Datacenter Manager 1.1!
This point release focuses on expanding visibility and automation for large-scale, multi-site deployments. Our main focus for this iteration has been introducing...
Nothing.
But we are debugging the "Prune 0" shown on the dashboard. It does not feel right, correct? Perhaps it is a "display"-error in the sense that it shows the number of prunes for the Datastore but not if there is only pruning only of a...
Wenn du Hosting betreibst und keinerlei Redundanz hast/verkaufst, dann muss der Kunde jederzeit mit Ausfällen rechnen und in dem Fall reicht eine einfache Ankündigung, heute Abend gibts ein Reboot.
Wenn du was anderes mit deinen Kunden vereinbart...
In that case you can read all about it here:
https://wiki.debian.org/NetworkInterfaceNames
en: Prefix for Ethernet interfaces.
wl: Prefix for Wireless (WLAN) interfaces.
enpXsY: Derived from the PCI bus location. p stands for PCI bus number and...
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
+++...