You have two problems. In the first place you have to allow that ceph1 can act as NTP source for others. And secondly ceph1 must "fake" enough time accuracy so that it is not rejected by clients.
Hm, do you have the same workflow on the other VXLAN vnets (i.e. are you creating mass clones via ansible there as well?). If not, does the same thing happen when creating VMs via cloning on the other subnets?
Is it possible there are some...
This is not valide, im my opinion.
auto vmbr0
# ipv4 config
iface vmbr0 inet static
address 192.168.1.100/24
gateway 192.168.1.1
bridge-ports nic0 nic1 # <===
bridge-stp off
bridge-fd 0
Hello everyone, I have a weird network issue on my single-node Proxmox VE host.
In the node's System > Network page, only the bridge vmbr0 is shown; my two physical ethernet adapters nic0 and nic1 never appear in the WebUI list.
If I try to add...
A status update on this:
Two corosync parameters that are especially relevant for larger clusters are the "token timeout" and the "consensus timeout". When a node goes offline, corosync (or rather the totem protocol it implements) will need to...
Falls noch ältere Kernel-Pakete installiert sind, werden diese auf dem ESP neu installiert.
Entfernen Sie die 6.17-Initrd- und Kernel-Dateien vom ESP (wie Sie es bereits getan haben) und entfernen Sie außerdem die zugehörigen Pakete mit:
apt...
Danke! :)
Ich wundere mich gerade, dass es so funktioniert hat, ich bin mir sicher, dass ich das schon mehrfach versucht hatte, wahrscheinlich aber mit einzelenen Kernelversionen, udn er hing immer bei dem alten Kernel fest.
Egal..., das apt...
RAIDz1 is not at all like RAID5 in performance and usable space. And it's indeed not good for VMs. This had been mentioned often, see here for additional information:
https://forum.proxmox.com/threads/fabu-can-i-use-zfs-raidz-for-my-vms.159923/
Ja, das soll so sein ;-)
Manchmal hilft es, statt dem schlauen apt das einfachere dpkg zu verwenden. Also per "dpkg -P proxmox-kernel-uralt" löschen. Falls auch dies klemmt eben wie oben esp mounten, dort manuell alte Dinge löschen und dann noch...
The problem is also triggered on last kernel 7.0.12-1-pve.
[root@patchmon ~]# fio --name=stress-hdd --ioengine=libaio --iodepth=8 --rw=randwrite --bs=4k --direct=1 --fdatasync=8 --size=20G --numjobs=8
--runtime=1800 --time_based...
No, we have the NTP server on the master ceph1 already and we also use NTP client on ceph2, and ceph3 from master, but currently, we got WARNING alerts from Clock Skew on Ceph2 and 3 and we didn't know how to fix it.