wenlez

Members
  • Content count

    152
  • Joined

  • Last visited

Community Reputation

0 Neutral

About wenlez

  • Rank
    Advanced Member
  1. it does seem the p9 pid is created. But , where is the error??
  2. Not if you use the DS3617x image. the DS3617 works well with my 8 core / 16 threads CPU.
  3. 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.
  4. I'm scare to play with the MTU setting. What if the network stops working and I can't connect to my NAS?
  5. 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.
  6. 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.
  7. 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?
  8. I'm going to try to use my PM961 SSD as a main drive. no one has gotten NVMe SSD to work yet?
  9. 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.
  10. I wonder about this as well.
  11. 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.."
  12. 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]
  13. 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.
  14. if you SSH to the server, you'll see more cores being recognized. DS3617xs itself uses a Xeon D1528 CPU, which has four cores. So, it's just reporting what it think DS3617 has. I think this is hard coded somewhere.
  15. Assuming you have both NIC's mac address correct, and they are both(mac1 & mac2 ) defined in the grub.cfg file, you can SSH to the server and check via command ifconfig | grep eth[0-4] . if the mac addresses match exactly on your ethernet ports on the motherboard, then try to use other ethernet cable.