Hi Ilya, some of our Proxmox VE users also report they need to enable rxbounce to avoid their Windows VMs triggering these errors, see e.g. [1]. With rxbounce, everything seems to work smoothly, so thanks for adding this option. :) We're currently checking how our stack could handle this more gracefully. From my understanding of the rxbounce option, it seems like always passing it when mapping a volume (i.e., even if the VM disks belong to Linux VMs that aren't affected by this issue) might not be a good idea performance-wise. Another option is to only pass `rxbounce` when mapping volumes that are known to be Windows VM disks. This seems like the most sensible option, but still, I wanted to ask: I see that when rxbounce was originally introduced [2], the possibility of automatically switching over to "rxbounce mode" when needed was also discussed. Do you think this is a direction that krbd might take some time in the future? Best, Friedrich [1] https://forum.proxmox.com/threads/155741/ [2] https://lore.kernel.org/all/894a36483c241e0cc5154e09e8dd078f57a606d5.camel@xxxxxxxxxx/ _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |