Thanks

1. A volume cannot be shared between operating system instances. If you want to configure a pass-through disk, I don’t help with that anymore. I might have something written on it, but I didn’t keep any links. You could set up a conventional SMB share, but that potentially constitutes a licensing violation.
2. The portion that you quoted does not apply to your first sentence. The quote just means that Hyper-V’s own bits don’t benefit much from SSD, and was targeted at people that put needs-almost-zero-IOPS Hyper-V on SSD while putting much-more-I/O-bound VMs on spinning disk. I don’t have the details about your configuration, but in isolation, putting the VMs on C: isn’t a bad thing.

Using HyperV 2019 Server. Via remote Server Manager, I’ve created a storage pool (1xSSD,2xSpins) and a VD with Volume from the pool.

1. How do I go about connecting the Volume to my Guest OS as a shared disk? Link if I’ve overlooked your write-up on it.
2. I’ve installed my HyperV and Guest OSs on the same partition on the SSD (remaining space to the storage pool above). Other than the ‘Installing HyperV on SSD has no benefits other than faster boot-ups’, is this a bad practice?

Thanks. Your contents are great!

Adapters used specifically for storage do not belong to the cluster anyway. The validation wizard does not know that, though. You can safely ignore these errors.
You do need to ensure that you have excluded the storage adapters from all cluster traffic (in the networks node of Failover Cluster Manager).

Split the difference. Two or more moderately sized LUNs connected to the host. VMs use VHDX inside them. One LUN could do the trick, but multiple LUNs give you flexibility.

In your experience what is the best way to work hyper v with a san unity, create a large disk for the host and then inside the host create small volumes through disk mangement

Or create small disks from the san and show them to the host for there to save the different vhd of the vm

Thank you.

It is not supported. It would be partially functional.
What are you attempting to accomplish? There is probably a better way.

I’m struggling to find an article which explains whether or not you can use a single server with the iSCSI target server role and also Hyper-V role installed on the same Windows 2012 R2 server. Do you know if this is supported?

Thanks

Pass-through adds no value in this scenario. Connect to the management OS and use a VHDX.