wenlez
-
Posts
191 -
Joined
-
Last visited
-
Days Won
2
Posts posted by wenlez
-
-
kazuni did say DSM 6.2-23739, so it would has to be 1.03 loader. But there is a 1.03b? where you get that?
-
I am running into the same problem as well. I'm trying to troubleshoot this.
-
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.
-
2
-
-
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.
Quotehostpci0: 00:17.0
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.
-
On 9/17/2017 at 2:36 PM, arkilee said:
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.
-
7 hours ago, DerMoeJoe said:
I also can confirm, that with 6.1.2 lacp with 2 nics on 9000mtu was working fine for more than 1 month (with couple of reboots), but with 6.1.3 lacp doesnt work for New. I also tested mtu with 4000 & 1500 without success.
Gesendet von meinem SM-T585 mit Tapatalk
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_governorThis, allow my CPU to enter lower frequency state.
Quoteash-4.3# grep MHz /proc/cpuinfo
cpu MHz : 800.000
cpu MHz : 800.000
cpu MHz : 1700.000
cpu MHz : 800.000
cpu MHz : 800.000
cpu MHz : 2201.000
cpu MHz : 800.000
cpu MHz : 2201.000 -
On 5/31/2017 at 9:19 AM, pacman44 said:
Is it just me or the script wont work in 6.1.1 ? It was fine in 6.0.1.
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.
-
I actually just ran into this problem. I upgraded ( migrated ) 3615 to 1.02b 3617. Now my couchpotatoe, headphone, and sickbeard package won't start because git and python are not available. wtf?
-
I'm going to try to use my PM961 SSD as a main drive. no one has gotten NVMe SSD to work yet?
-
well, likely not any time soon. AMD Opteron X3216 features Zen core, and itself is an APU with Radeon VEGA. Not only the current version of boot loader doesn't support AMD CPU yet, there is likely no support of the graphics portion of the APU as well.
-
I wonder about this as well.
-
if i add "boot: synoboot" to the VM's conf file, I can't get it to boot the bootloader. In the VM's option, you'll see the Boot disk is read as "s,y,Network.."
-
Running Xpenology 6.1 in Proxmox 5 Beta 2. I can't get Synology's Virtualization Manager to work. When I try to start a virtual machine, the log say the following. Had anyone got it to work?
2017-06-13T13:50:43-05:00 Portal synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[10460]: MemSize: ccc/reservation.cpp:477 Start to op(3), ba03cfbc-00ff-451a-aef5-b814a2623589: +1073741824, orig 0 2017-06-13T13:50:43-05:00 Portal synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[10460]: core/utils.cpp:895 Failed to mkdir: /dev/virtualization/libvirt/qemu, error: No such file or directory 2017-06-13T13:50:43-05:00 Portal synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[10460]: MemSize: ccc/reservation.cpp:537 Failed to mkdir 2017-06-13T13:50:43-05:00 Portal synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[10460]: MemSize: ccc/reservation.cpp:488 Failed to op(1), ba03cfbc-00ff-451a-aef5-b814a2623589: 1073741824 2017-06-13T13:50:43-05:00 Portal synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[10460]: ccc/guest.cpp:1575 Failed to edit reservation resource for [ba03cfbc-00ff-451a-aef5-b814a2623589] ret [-2], mem: 1024 / 0, cpu: 4 / 4 2017-06-13T13:50:43-05:00 Portal synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[10460]: ccc/guest.cpp:1686 Failed to prepare for guest [ba03cfbc-00ff-451a-aef5-b814a2623589] 2017-06-13T13:50:43-05:00 Portal synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[10460]: Guest/guest.cpp:3141 Failed creating guest [ba03cfbc-00ff-451a-aef5-b814a2623589] reason [-7]
-
Thanks for sharing. last time I read about VMM, it was only capable of running the virtualized DSM. Now it can install other OS? I'm sold on it.
-
1
-
DS918+ on Proxmox (qemu)
in DSM 6.x
Posted
Does the ds3615 work for you? I still have the mount failed error.