Hello all,
I am trying to get a bit more familiar with VVol Storage:
The path that the VM files are stored follow a weird path starting with rfc4122, for example:
rfc4122.d7c0989e-9be2-41e0-a36c-2e6d593feed3/test-vm.vmx
Is there a way to find out which is VM using this "folder": rfc4122.d7c0989e-9be2-41e0-a36c-2e6d593feed3 without checking the VM files (vmx, etc)
in other words does this UUID follows any naming rules when generated / created?
Thank you
Theo
That string is a UUID that describes the protocol endpoint for a NFS-backed VVol. It's prefaced with RFC4122 because it conforms to the RFC 4122 spec governing UUID generation algorithm. The "4" as indicated below means it's v4 of that spec, which outlines random generation.
rfc4122.d7c0989e-9be2-41e0-a36c-2e6d593feed3
That UUID isn't indicative of a VM or even set of VMs but of the PE exposed by that NFS type
That string is a UUID that describes the protocol endpoint for a NFS-backed VVol. It's prefaced with RFC4122 because it conforms to the RFC 4122 spec governing UUID generation algorithm. The "4" as indicated below means it's v4 of that spec, which outlines random generation.
rfc4122.d7c0989e-9be2-41e0-a36c-2e6d593feed3
That UUID isn't indicative of a VM or even set of VMs but of the PE exposed by that NFS type
