-
Announcements
-
DSM 6.2-23739 - WARNING 05/23/2018
This is a MAJOR update of DSM. DO NOT UPDATE TO DSM 6.2 with Jun's loader 1.02b or earlier. Your box will be bricked. You have been warned. https://www.synology.com/en-global/releaseNote/DS3615xs -
Email server issues - FIXED 06/14/2018
We have been experiencing email server issues. We are working on it. Bear with us. Thank you. ------------- Problem has been fixed. You might receive duplicate emails. Sorry for that.
-
wenlez
-
Content count
162 -
Joined
-
Last visited
-
Disk order with "machine: q35" enabled in Proxmox. If out that line, the disk will start from 1st box.
-
Does anyone use machine: q35 ? If I have this option enabled, all my hard drives are shifted to a higher number. Any idea on how to fix that?
-
Looks like I solved my own problem. Enabling Write Cache in DSM is the key.
- 3 replies
-
- 2
-
-
- passthrough
- sata
- (and 2 more)
-
I encounter similar issue, posted on a different topic. I have no SSD Cache, and my set up is virtualized.
-
SATA controller chipset. doesn't have to be supported by ESX. As long as your CPU(and its chipset) supports VT-d, you should be passthrough individual PCI(e) device to the VM. Also check the VM/ESX log, during the VM start. If ESX has issue passing through the PCI device, it would say something in the log. You can also do a "lspci" in the VM to validate. I have Proxmox 5.1, and the onboard Intel SATA controller is reported as: 0000:01:00.0 Class 0106: Device 8086:a282 (prog-if 01) Subsystem: Device 1458:b005 Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 45 Memory at 91600000 (32-bit, non-prefetchable) [size=8K] Memory at 91603000 (32-bit, non-prefetchable) [size=256] I/O ports at a020 [size=8] I/O ports at a028 [size=4] I/O ports at a000 [size=32] Memory at 91602000 (32-bit, non-prefetchable) [size=2K] Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [70] Power Management version 3 Capabilities: [a8] SATA HBA v1.0 Kernel driver in use: ahci
-
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=00:11:32:xxxxxxx,bridge=vmbr0 net1: virtio=00:11:32:xxxxxxx,bridge=vmbr1 numa: 1 ostype: l26 scsihw: virtio-scsi-pci serial0: socket smbios1: uuid=7fda6843-8411-473f-91a5-xxxxxxxxx sockets: 1 I've tried to passthrough the VM without q35 machine type, and without PCE=1. Write performance is the same. What's strange is, the write performance was really good back in October, when I was still on Proxmox 5.0. So I want to ask everyone, how's your SATA passthrough performance?
-
if ESXI has the option to allow you to passthrough a PCI device, then your chipset should already support VT-d. You can double check by making a new VM, and boot any LInux live CD (Ubuntu, Fedora, etc.. ), and see if you can see the attached hard drives from that SATA controller.
-
This has been working really well for me with Proxmox 5.1 ( or previously version 5.0 ). I hope someone can implement virtio-scsi driver, so I can take advantage of the "Discard" feature, to reclaim thin LVM space.
-
Strangely, when using VirtIO network, i'm limiting to 100mb/s???
-
it does seem the p9 pid is created. But , where is the error??
-
Not if you use the DS3617x image. the DS3617 works well with my 8 core / 16 threads CPU.
-
Any one got SR-IOV to work on baremetal install? I have a Xeon D1520 board. While the BIOS has it enabled, DSM doesn't seem to able to use SR-IOV.
-
I'm scare to play with the MTU setting. What if the network stops working and I can't connect to my NAS?
-
What I did was to create a cronjob ( vi /etc/crontab ), to execute a script with the following content: #!/bin/sh echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor echo ondemand > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor echo ondemand > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor echo ondemand > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor This, allow my CPU to enter lower frequency state.
-
I have 6.1.3 ( 3617x), and it works. Though, I would rather let the kernel module to set the governor at boot, instead of relying on a script to do so. Would be nice to be able to use the boost speed of the CPU. My scaling driver is acpi-cpufreq, and it can't boost my Xeon D1520 CPU.