Recent content by spirit

if you backup storage is slow (or if you are limited with network bandwidth), it can slow down vm write during the backup, if a block is not yet saved. (it's not related to ceph, this is the same for any kind of storage) You can try to enable fleecing option in the backup scheduling advanced...

Was talking with a Guy at fosdem working for the europeean commission. They seem to have migrated recently from vmware......to nutanix.......

Hi, sorry to bump this old thread, but it's finally coming ! https://github.com/corosync/corosync/wiki/Corosync-3.1.10-Release-Notes

I had trid ocfs2 10year ago during 1~2 year, and I had a lot of lock problem if 1node of the cluster was going down. (like full cluster lock during 1~2min, the time that the lock was released). I have done benchmark test last year, and write performance was not super great with new block...

can you send your corosync logs ? journalctl -u corosync do you only 1 corosync link ? or dedicated nic ? shared with other network ?

what is the mtu of your physical interfaces && main bridge ?

seem than freebsd have fixed the checksum bug with virtio-net recently (september 2015 / freebsd15) https://cgit.freebsd.org/src/commit/?id=5a8f33f52ae38bbf12f8f45b8e0f75166805c386 I don't known if it's already available in pfsense/opensense It's related to this bug...

Hi dominik, I'm going to test with a H200 soon. have asked to nvidia support for ai enterprise support (and also about MIG mode not working with windows vms)

I have build the 6.17 kernel with openzfs 2.4 , no more error. If somebody want it, I can share it. (it's unsigned, so not working with secure boot)

seem to be fixed here : https://github.com/openzfs/zfs/pull/17943 I don't known if it's already fixed in current proxmox kernel

a difference with snapshot mode is that the qemu agent is doing a fs-freeze/fs-thawt before the backup, so maybe you can try to disable this ? (they are an vm config option in vm guest agent config). also, not sure that it could help, if you using the agent agent , they are also an extra...

move the file (delete the vm config on source node) to be sure to not restart it again on old01 by mistake, when it's running on NEW01, or you'll break your vm filesystem

you can edit manually /etc/network/interfaces and add: iface <vnetname> address X.X.X.X/X I'll be merged with the sdn config on reload

the vm traffic is goinf through the vxlan (vxlan_remoteip ...), so it's use peers ip address. if you want to split management && vm traffic on 2 nic, you need to setup 2 differents ip address on each host on different subnet. (1 for management, 1 for peers). Also, don't need vmbr0 or vmbr1...

systemd v256 -> not on debian13, so not on proxmox