Skip to main content
Super User

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

10
  • My host is the hypervisor. I'm trying to keep the host as dumb as possible so setup of clones is as simple as possible. The shares are so big it doesn't make sense to include them in the VM drive itself. Thus, if I understand the Hyper-v File Sharing model correctly, the way I'd share from a VM is to give the VM direct access to those disks within hyper-V, but that goes against the "dumb host" thinking and makes a potential migration less than slick. The shares are on a namespace to make host swapping smoother. Am I missing an obvious nuance to FS from VM?
    – geardogg
    Commented Feb 28, 2021 at 17:12
  • 1
    I don't think you understand VMs and Hyper-V particularly well. The VMs are computers. They consist of configuration files and blob storage files on the host, running within the hypervisor. The "host" being "dumb" is not a concern at all. The host being "simple" may be. Run a second VM on that same host, attache storage to it to store the shares, and move the shares to that 2nd VM. It's really quite as simple as that.
    – music2myear
    Commented Mar 1, 2021 at 1:18
  • While this was my first thought, the point of my approach is to leave minimal entanglements between host and VMs, for portability. The host is replicating the available storage, which is a necessity, as the host is part of a virtual san. As I understand it, one has to give a VM sole rights to a partition for what you describe, and that would surely interfere with the drive replication. To play along down the path of your education, I have storage attached. How do I "move the shares to that 2nd VM" without interfering with DFSR?
    – geardogg
    Commented Mar 2, 2021 at 14:34
  • VMs don't care about partitions on the host. VMs drives are all just blob files on the host. While it is technically possible to mount a given partition on the host to a VM, it's very much NOT recommended, for many, many reasons, especially on a tight enterprise setup like yours.
    – music2myear
    Commented Mar 3, 2021 at 4:15
  • There seems to be a disconnect here. I have a blob file on a host, great. That VM wants to share files that also reside on that host, but do not reside within the VM blob. You say "just move the share to the VM" and here lies my query. If I'm going to alter my design to have a VM handle the share, how? What I read says give direct partition access to the VM.
    – geardogg
    Commented Mar 3, 2021 at 14:39