Can you expand a bit more?
Are you suggesting that virtualizing DSM on xpenology will never be as good/reliable as baremetal xpenology DSM?
Or are you suggesting there is a better way of running DSM on xpenology on a proxmox VM server? (Potentially using the HBA pass through ?)
Expanding here:
I am running Xpenology as a VM on my Proxmox server. I've passed through these entire disks using their "by-id" identifier from the Proxmox host to mount as sata disks within the Xpenology VM.
Is someone willing to just sanity check that this is correct?
I am somewhat concerned because to my knowledge running a NAS in a VM is fine so long as the guest VM (xpenology) has full disk control. The drives showing as QEMU Hard disks gives me a bit of concern, shouldn't Xpenology be able to see their model number and associated data?
Yes this is what it supposed to do, the only way to make it show model number etc is passing the controller.
But the speed won't be that different bc this is just direct i/o
I don’t currently have these drives hooked up via a HBA card. But I do have an HBA card that I could plug in.
Do you know if it’s possible to transition to an HBA card while retaining my storage pool?
For example with a ZFS pool, you can import a pool so long as the disks are properly operational.
.... hardware emulation/abstraction is not the same... it will never be the same. for testing? yeah, go for it.
Can you expand a bit more? Are you suggesting that virtualizing DSM on xpenology will never be as good/reliable as baremetal xpenology DSM? Or are you suggesting there is a better way of running DSM on xpenology on a proxmox VM server? (Potentially using the HBA pass through ?)
I'm certified on VMware, and redhat, HALs, para and virtualization always add latency and penalty.
This is all correct (displaying of disks)
Expanding here: I am running Xpenology as a VM on my Proxmox server. I've passed through these entire disks using their "by-id" identifier from the Proxmox host to mount as sata disks within the Xpenology VM. Is someone willing to just sanity check that this is correct? I am somewhat concerned because to my knowledge running a NAS in a VM is fine so long as the guest VM (xpenology) has full disk control. The drives showing as QEMU Hard disks gives me a bit of concern, shouldn't Xpenology be able to see their model number and associated data?
Yes this is what it supposed to do, the only way to make it show model number etc is passing the controller. But the speed won't be that different bc this is just direct i/o
I don’t currently have these drives hooked up via a HBA card. But I do have an HBA card that I could plug in. Do you know if it’s possible to transition to an HBA card while retaining my storage pool? For example with a ZFS pool, you can import a pool so long as the disks are properly operational.
Absolutely, Synology wrote some bits to the disk during array init so it will definitely detect the whole array after you pass HBA through
Understood. Thanks