I've added a Drive to a VM using
qm set 101 -sata1 /dev/disk/by-partuuid/11fc2c64-5311-45da-8224-75dc9624c46
The VM is running FreeNAS, which shows
ada1 at ahcich1 bus 0 scbus3 target 0 lun 0
ada1: <QEMU HARDDISK 2.5+> ATA-7 SATA device
ada1: Serial Number QM00007
ada1: 150.000MB/s transfers (SATA 1.x, UDMA5, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 2861587MB (5860530176 512 byte sectors)
ada1: Previously was known as ad6
Is it really emulating SATA 1, at 150MB/s?
Can I change the command (add a parameter?) to emulate SATA III?
I can see an advantage in adding via by-partuuid, but are there any disadvantages?
If it's OK to use by-partuuid, then which is best for a partition table, GPT or MBR?
qm set 101 -sata1 /dev/disk/by-partuuid/11fc2c64-5311-45da-8224-75dc9624c46
The VM is running FreeNAS, which shows
ada1 at ahcich1 bus 0 scbus3 target 0 lun 0
ada1: <QEMU HARDDISK 2.5+> ATA-7 SATA device
ada1: Serial Number QM00007
ada1: 150.000MB/s transfers (SATA 1.x, UDMA5, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 2861587MB (5860530176 512 byte sectors)
ada1: Previously was known as ad6
Is it really emulating SATA 1, at 150MB/s?
Can I change the command (add a parameter?) to emulate SATA III?
I can see an advantage in adding via by-partuuid, but are there any disadvantages?
If it's OK to use by-partuuid, then which is best for a partition table, GPT or MBR?