Was bei Datev Updates immer viel bringt, ist das deaktivieren des Virenscanners auf dem DTV und den Clients.
Hast du auf dem Host bzw. in den VMs mal die Prozesse in der Zeit beobachtet, fällt da einer auf?
Das Einzige, was ich daran eventuell ändern würde, ist die Ausstattung mit Compute und RAM - eine Anwaltskanzlei sollte sich das erfahrungsgemäß leisten können. ;-)
Für solche Setups ist ein Terminalserver i.d.r die bessere Wahl, frisst weniger Ressourcen und ist leichter zu administrieren, weil primär der TS aktualisiert werden muss und alle User dann die gleiche Instalaltion zur Verfügung hat.
The Hot-Add vs NBD results are probably the most useful clue here. If NBD keeps the VM responsive while Hot-Add drives I/O down to ~100 KB/s and causes soft lockups/RCU stalls, I’d be looking very closely at the Hot-Add path between Veeam, QEMU...
@janus57
It's for professional setup so M365 enterprise account and not personnal one
You can use OAUTH natively with proxmox to send mail ? It's what I would like but I totally ignore how to
Hi,
It's not working anymore, M365 enforced OAUTH authentication (or at least it's what we have seen with business accounts with our clients).
Since then we either use OAUTH or a SMTP relay (create with proxmox mail gateway).
Best regards,
The proxmox helper scripts don't handle multiple ceph networks. They only expect to find one in the configuration file and will throw that error when doing certain operations.
When creating OSDs, we work around it by removing all the networks...
Currently, using a CIDR that contains *all* IPs that are part of the cluster is the only way. We had some internal discussion on how to lift this restriction though. You can set the CIDR manually via pveceph, e.g.:
pveceph init --network...
please provide the configs:
- /etc/pve/storage.cfg
- VM config
as well as logs:
- any tasks logs concerning the VM since it was started on the source
- the migration and start task logs
if you can easily reproduce it with a test VM, you could...
Tested this on two Ryzen based nodes in a cluster. No issues detected so far. I did change the version manually on a Windows guest, that seemed to boot and operate ok.
I did note however that I had to install the updates on both nodes in the 2...
Hi @manu007 and @andrej_,
please share more information similar to what @davispuh did. You can try systemctl reset-failed for the scope and/or stuck unit, but it would be good to check how it's stuck first.
Currently, using a CIDR that contains *all* IPs that are part of the cluster is the only way. We had some internal discussion on how to lift this restriction though. You can set the CIDR manually via pveceph, e.g.:
pveceph init --network...
Symptom
After upgrading to Proxmox VE 9.2.20 (September 24, from 9.2.4), LXC/VM consoles in the web interface sometimes failed to start (termproxy ... failed: exit code 1, failed waiting for client: timed out), and overall interaction (console...
Honestly, it's more trouble than worth, we had zillions of times when "Configured correctly " did not pass pass the
ping -M do -s 8972 [destinationIP]test
All moderns switch ASICS can do line speed with regular frames, and most NICs have...