Thank you for this video. I was looking for this, so I will definitly give it a try, but I was wondering why you are saying that this is just for testing.
I'll take a stab at answering this, but it may not be entirely correct since I am also here trying to recover a lost pool from this kind of testing setup. When you deploy in production across multiple vmware hosts in a cluster (or other hypervisor that supports clustering) one of the things you get from this is failover - if a host has a VM running on it and the host fails, the VM is migrated over and the most recent saved state is booted on the remaining hosts. The problem with this is the hardware passthrough. Last time I checked (before VMware was slurped up by Broadcom) clustering does not support hardware passthrough. I wanted to pass through a GPU instead of storage, but the problem is largely the same. You loose the ability to cluster, so you have a single point of failure. In this case, in production the best option is to have storage physically separate and to do your redundancy on the SAN and not in Vmware (or whatever hypervisor you are using). Again, this may not be correct but this is the main reason I can think of.
This methods are not suitable for if you have HA, as during migration to another Host, the passthrough are not migrated. As said by strykenine7902 is correct.
@@StrykenineThank you for your response. I am actually a small "home user". I have a separate TrueNas core system running independently. I also have Blue Iris running on another windows machine. My idea is to run only the Windows machine 24/7 with VMWear and TrueNAS Scale in a VM (this is where I need to passthrough the SATA Controller). I understand the risk of doing this and to lose my data if something goes wrong and therefore my plan is then to use the existing TrueNas Core machine to backup for my data up let’s say once a week.
@Lepelot, myself also run a home lab too. Since you understand the risk & have a backup plan in place, then the data lost is minimized significantly. We as home lab & tech enthusiast sometimes don't mind the tinkering & the risks, as long as we can afford the down time. LOL.
Thank you for this video. I was looking for this, so I will definitly give it a try, but I was wondering why you are saying that this is just for testing.
I'll take a stab at answering this, but it may not be entirely correct since I am also here trying to recover a lost pool from this kind of testing setup.
When you deploy in production across multiple vmware hosts in a cluster (or other hypervisor that supports clustering) one of the things you get from this is failover - if a host has a VM running on it and the host fails, the VM is migrated over and the most recent saved state is booted on the remaining hosts. The problem with this is the hardware passthrough. Last time I checked (before VMware was slurped up by Broadcom) clustering does not support hardware passthrough. I wanted to pass through a GPU instead of storage, but the problem is largely the same. You loose the ability to cluster, so you have a single point of failure.
In this case, in production the best option is to have storage physically separate and to do your redundancy on the SAN and not in Vmware (or whatever hypervisor you are using).
Again, this may not be correct but this is the main reason I can think of.
This methods are not suitable for if you have HA, as during migration to another Host, the passthrough are not migrated. As said by strykenine7902 is correct.
Yes, you are correct.
@@StrykenineThank you for your response. I am actually a small "home user". I have a separate TrueNas core system running independently. I also have Blue Iris running on another windows machine. My idea is to run only the Windows machine 24/7 with VMWear and TrueNAS Scale in a VM (this is where I need to passthrough the SATA Controller). I understand the risk of doing this and to lose my data if something goes wrong and therefore my plan is then to use the existing TrueNas Core machine to backup for my data up let’s say once a week.
@Lepelot, myself also run a home lab too. Since you understand the risk & have a backup plan in place, then the data lost is minimized significantly. We as home lab & tech enthusiast sometimes don't mind the tinkering & the risks, as long as we can afford the down time. LOL.
Thank you