Hello I've have installed this new driver on our Test servers and have done the following in terms of multi-day testing:
Boot-volume operation on vioscsi 0.1.302
Multiple reboots and device checks
Five active VirtIO SCSI controllers
Overnight...
Thank you for your reply.
Just to clarify, its not apt upgrade on pve's that is struggling, its the apt upgrades with unattended upgrades inside the ubuntu VMs.
Yes,this is the setup we have used for many years (If the NUMA option is used, it...
According to the docs: "If the NUMA option is used, it is recommended to set the number of sockets tothe number of nodes of the host system." Have you tried that and checked how it changes your situation/problem...
https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#virtio-win_Releases
Schau hier in der nächsten Zeit ob sich die Empfehlung ändert, wenn du nicht experimentierfreudig bist.
Wir beobachten die Lage und testen selber.
--rotate-lockbox-keys worked well on our 3 node 12-OSD test cluster. The warnings are now gone. We'll be testing further with other clusters and report any issues.
Fix is up and worked well on my side: https://forum.proxmox.com/threads/ceph-cves-–-keyring-rotation-strongly-advised-probably-required-in-the-future.185863/#post-867260
Hello Thomas! @t.lamprecht
After applying the updates in the script its green again, had to use a couple of commands though:
root@training3:~# /usr/share/pve-manager/migrations/pve-cephx-rotate-service-keys
root@training3:~#...
how did it help you exactly? ;-) I personally would like to make some testing about:
* testing with 32 PGs vs 512 PGs (min/max) and how it affects performance
* testing with erasure coded pools (fastec/non-fast-ec)
* testing with krbd/non-krbd
Yeah the container has failback disabled, this seems to be the reason why the container can be moved to a different host, even though the other host has a lower priority.
This should be the same for VMs and CTs as the HA Manager handles affinity rules the same for both. In a quick test, the migration blocker with the same node affinity rule as above was shown to me for both VMs and CTs, so I couldn't move either...
Hi @dakralex
is this a known bug? If not I would create a new one. (not related to dynamic crs but we had talked about other ha improvements here in the last posts)
Bug: VMs cant be migrated to nodes with lower priority if priority is set in a...
Hello Kefu Chai (does he have a account here @aaron ?)
Nice addition of having a bulk-restart feature in ceph when using 9.2.5 :-) It worked really well on mons, mgr, osds and mds.
I also used it in a test-setup for trying a ceph 19 to 20...
Generally, these sound like good ideas! Feel free to create separate Bugzilla entries for the separate issues:
automatically add new guests as HA resources by enabling some cluster-wide check (Though new guests can be automatically added...
Hi Daniel! Some cases that do not work or might be cool adding them:
Example 1: A resource affinity rule with “Keep Separate” for VM1 and VM2, combined with an HA node affinity rule (without “Strict”) on node1 and node2 (checked), but not...
Hi, sorry for the late reply!
At least for two rooms this is already possible with non-strict node affinity rules as these will fallback to the other available cluster nodes if none of the specified nodes are available anymore. However, an HA...