<ul>

<li>It is not advisable to use Greyhole pooling with drive images (instead of physical drives) due to the added overhead and I/O delay that can be introduced. It will slow down your Proxmox machine and your Amahi file server</li>

<li>The essential concept when using physical drives through the Proxmox machine is that the drive will NOT be mounted on the Proxmox machine, but routed through QEMU/KVM commands to the VM that will use it, much like a hardware pass-thru.</li>

<li>When the physical drive is added to the VM, it will show up in the Proxmox web GUI, but should <strong>NOT</strong> be tampered with from there.</li>

<li>

This step is where you finally point the physical drive to the VM, through the Proxmox console.<br />

<ul>

<li>vm101 is the ID of the virtual machine to which you want to point the drive.</li>

<li>/dev/sdb is the installed <strong>but not mounted in Proxmox</strong> drive in the hardware system.</li>

</ul>

Once booting this KVM, now add this drive by manually, permanently mounting it to the VM. This could be via editing the /etc/fstab within the VM or using any other drive mounting tool/method you wish. You should reference the Amahi drive-adding wiki article at this point to ensure the drive is added appropriately: <br />[https://wiki.amahi.org/index.php/Adding_a_second_hard_drive_to_your_HDA Adding a Second Drive to your HDA] <br />

For each physical drive you add, you can decide to pool it to Greyhole or not. It helps to understand some commands for managing drives and volumes and partitions in Linux before doing too much moving around.</li></ol>

command has run through a couple times. <br />

Do reference [https://wiki.amahi.org/index.php/Post-Install_Hardware_Changes Post Install Hardware Changes] for swapping hardware, which is similar to changing from a physical to virtual setup.</h4>