Search the Community

Showing results for tags 'passthrough'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Information
    • Readers News & Rumours
    • Information and Feedback
    • The Noob Lounge
  • XPEnology Project
    • F.A.Q - START HERE
    • Loader Releases & Extras
    • DSM Updates Reporting
    • Developer Discussion Room
    • Tutorials and Guides
    • DSM Installation
    • DSM Post-Installation
    • Packages & DSM Features
    • General Questions
    • Hardware Modding
    • Software Modding
    • Miscellaneous
  • International
    • РУССКИЙ
    • FRANÇAIS
    • GERMAN
    • SPANISH
    • ITALIAN
    • KOREAN
    • CHINESE
    • HUNGARIAN

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 5 results

  1. Hi all, Hope you are all well at this very strage moment in history. So, the topic... I am running: VMware ESXi-6.7.0-20191204001-standard-customized (VMware, Inc.) DSM 6.2.2-24922 Update 6, 3617xs HP Microserver Gen8/E3-1220 V2, Latest firmware and iLO HP P420 PCIe RAID w/ 4x HDD, RDM - ready to attach to VM (tested an working) HP Cougar Point AHCI w/ 2x SSD - passthrough, connected to VM Install and update was flawless, I set the following in grub.cfg: set sn=xxxxxxxxxxxxx set mac1=xxxxxxxxxxx DiskIdxMap=0C0
  2. Hello Guys, I've recently installed DS918+ on ESXi 6.7, but i have problems with passthrough. I have Asrock J3455-ITX board which have builed in second sata controller (Asmedia). For storage I'm using two 8TB WD drives that were took out of MyBook external drives. I set Asmedia controller to be passthrough to VM with DSM, but once I create Volume on RAID1 pool, I start getting write errors on drives. I tried also external PCIE-X sata controller on Marvell chipset and got the same issue. Errors starts to appear once I'm writing to drives. Issue does not appear once
  3. Hi, As you now when using a virtual environment to run the XPEnoloy the SMART is missing. The only change to run it is pass the Disk Controller to the VM using I/O passthrough. However, using the VMware ESXi with the Physical RDM, all SMART commands work inside a Linux VM. So, the conclusion is that the tools inside the DSM refuses to enable SMART when a non-conformant controller is detected. Then, to enable the SMART inside a VM the kernel needs to hack the identification of the Virtual Controller. As I feel this can be done inside the Jun's Loader. So, fro
  4. Hi, I've just got an XPEnology install up and running with Jun's loader under a Proxmox hypervisor. Everything seems to be working fine, persisting across reboots etc, but I'm just wondering where the DSM configuration data is stored? I have 4 SATA disks configured for direct passthrough and a RAID5 volume placed on them, and I boot the system using the synoboot.img from the loader. But where is all the DSM data stored? I can't see the synoboot.img changing and I don't know where else it would go.
  5. I have Proxmox 5.1. Xpenology 1.02b loader; DSM6.1.4 Update 5. Intel onbard (AHCI) SATA controller passthrough. I have 3 SSD in RAID0 mode. What I notice is, the write performance on SSD is terrible. I've try to tweak Proxmox, and the Xpeno VM, but nothing seems to help. My VM config: args: -device 'piix3-usb-uhci,addr=0x18' -drive 'id=synoboot,file=/var/lib/vz/images/100/synoboot_jun2b_virtIO.img,if=none,format=raw' -device 'usb-storage,id=synoboot,drive=synoboot' bios: ovmf boot: 4 cores: 4 hostpci0: 00:17.0,pcie=1 machine: q35 memory: 6144 name: DSM6.x net0: virtio