In general, no, unless you meet one of two very specific constraints. Either:
The device needs to be exposed read-only (this MUST be at the device level, not the filesystem level) to all the VMs, and MUST NOT be written to from anywhere at runtime.
The volume must be formatted using a cluster-aware filesystem, and all VMs must be part of the cluster (...
If you don’t run cluster-aware file system inside your VMs you’ll simply destroy your shred volume immediately after first metadata update. Full clarification story is here: