everwisher Posted May 1, 2022 Share #1 Posted May 1, 2022 In Proxmox, I emulated a nvme-disk and passed it through to a DSM guest using the following qemu option: -drive 'file=/dev/mapper/pve-vm--201--disk--1,if=none,id=nvm' \ -device 'nvme,serial=deadbeef,drive=nvm' After starting the DSM guest, disk /dev/nvme0n1 can be seen using this command: sudo udevadm info /dev/nvme0n1 The following information was printed: Quote Disk /dev/nvme0n1: 256 GiB, 274877906944 bytes, 536870912 sectors Disk model: QEMU NVMe Ctrl Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes P: /devices/pci0000:00/0000:00:03.0/nvme/nvme0/nvme0n1 N: nvme0n1 E: DEVNAME=/dev/nvme0n1 E: DEVPATH=/devices/pci0000:00/0000:00:03.0/nvme/nvme0/nvme0n1 E: DEVTYPE=disk E: MAJOR=259 E: MINOR=0 E: PHYSDEVBUS=pci E: PHYSDEVDRIVER=nvme E: PHYSDEVPATH=/devices/pci0000:00/0000:00:03.0 E: SUBSYSTEM=block E: SYNO_ATTR_SERIAL=deadbeef E: SYNO_DEV_DISKPORTTYPE=UNKNOWN E: SYNO_INFO_PLATFORM_NAME=apollolake E: SYNO_KERNEL_VERSION=4.4 E: SYNO_SUPPORT_XA=no E: TAGS=:systemd: E: USEC_INITIALIZED=366408 Then I modified the `/lib64/libsynonvme.so.1` file using a HEX editor in Visual Studio Code, changing the DS918+ NVME address from 0000:00:13.0 and 0000:00:13:1 to 0000:00:03.0 and 0000:00:03:1 respectively. However, when I rebooted DSM, no nvme ssd appears in the Storage Manager. Anyone with any clue about resolving this? Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.