Hard drive passthrough - scsi, sata, or virtio?

[sasobi]

I just hooked up a 10TB SATA hard drive to an already running proxmox system. I'd like to do passthrough to a Ubuntu 18 VM. The Ubuntu VM will run docker and a bunch of containers that will access the hard drive. I'm confused by all the options for doing passthrough.

qm set 100 -scsi3 /dev/disk/by-id/_____

qm set 100 -sata3 /dev/disk/by-id/_____

qm set 100 -virtio3 /dev/disk/by-id/_____

I haven't come across any explainations that explain the 3 side-by-side. And I didn't understand individual explanations in the context of how it impacts my usage.

With any of these options, is it possible to later on remove the hard drive from the system and be able to read it on any Linux PC with a SATA-USB adapter?

 

[msg7086]

99% time you want scsi.

Use virtio if you specifically want /dev/vdX instead of /dev/sdX. (I hit a case when I needed vdX, but you shouldn't need it.)

Use sata if you want to play with the sata controller feature (like if you want to do debugging or development around sata controller.)

And, yes, you can read it from host the same way.

 

[sasobi]

99% time you want scsi.

Use virtio if you specifically want /dev/vdX instead of /dev/sdX. (I hit a case when I needed vdX, but you shouldn't need it.)

Use sata if you want to play with the sata controller feature (like if you want to do debugging or development around sata controller.)

And, yes, you can read it from host the same way.

Thanks. I've never gotten a really good feel for LVM's and I was afraid hard drive passthrough is kinda like that. So after the VM fills out the drive with files, I can physically remove the drive from the system and move it to any old linux machine and still be able to read the files? Right now, the drive's "usage" column is listed as "Partitions" rather than "LVM" or "Mounted". Is that the correct state to begin the "qm set" operation?

 

[msg7086]

I'm not sure about how it displays usage, but if you qm set the disk directly you should be good.

In my case, I only pass through a partition and not a whole disk.

By the way, I'm pretty happy with LVM, so...

 

[neail]

99% time you want scsi.

Use virtio if you specifically want /dev/vdX instead of /dev/sdX. (I hit a case when I needed vdX, but you shouldn't need it.)

Use sata if you want to play with the sata controller feature (like if you want to do debugging or development around sata controller.)

And, yes, you can read it from host the same way.

Hi,
Does passing through as SATA grants access to the SMART?
, because My SCSI mounts are not visible by SMART.
You can find my main question here-


And do you have any idea why DIRECT SYNC is not working in SCSI, (I am using it on OMV, and the Filesystem creation is crashing, though works fine with no cache)

 

[keepitsimple]

Hi,
Does passing through as SATA grants access to the SMART?
, because My SCSI mounts are not visible by SMART.
You can find my main question here-


And do you have any idea why DIRECT SYNC is not working in SCSI, (I am using it on OMV, and the Filesystem creation is crashing, though works fine with no cache)View attachment 47623

Yes, this was the only way for me to get access to smart tools. I kept getting strange errors stating zpool offline, degraded, faulted etc. Once I changed scsi to sata using qm set *** I was able to use the smart tools and all of the warnings subsided