Jump to content
XPEnology Community

oculto

Rookie
  • Posts

    4
  • Joined

  • Last visited

Everything posted by oculto

  1. I did something unusual and it works fine. I boot ESXi 6.5 from USB, as usual but didn't use any local storage, i have been using NFS storage from Synology with VMWare plugin to snapshot. this solve my backups and replications problems. The performance is good, around 100mb/s on a gigabit lan (two lans on microserver, four on synology, using a LAG switch on the middle. because of the problems with ESXi drivers I found this setup better then using a magnetic local drive (not SSD). if the synology NFS server was running, I can reboot the ESXi fine, and it restarts with the NFS datastore mounted. I have two VMs using this NFS datastore (vmdk sitting on the NFS). one Windows 10 (i access from my mac using Microsoft Remote Desktop Beta for mac) and a macOS sierra running a server app (I use the unlock 2.0.9 to do that) with serves cache apps, netinstall files, and other stuff. I dont need to login this machine, but if I needed, I simple use the native macOS Share Screen app. For the needs I have, it works fine. and off course, there is a XPEnology VM running on this NFS (just the boot disk) and a 9211-8i HBA (M1015 card flashed) passthrough with is the main purpose of this microserver. all the four drivers and the xpenology setup runs perfectly from years.... I have a Xeon E3 1220V2 (not L) with 2 cores disable just for safe, but I can easily enable a 3rd core without any problem. a 4th core enable cause high temps and needs a better cooling solution. But 2 cores is fine for my needs, most of the times the 2 VM (windows and mac) are idling. I think I will gone a try to remove the HBA card and passtrough the B120i on AHCI mode directly to xpenology. There is no disk attached to that controller now, and I think I can move the cable from LSI to B120i without crash the xpenology setup (only adjusting the xpenology vmx file to correct PCI controller). I expected with this move to reduce around 10w of power and lower a little bit the temps inside the case without a performance penalty. these M1015 runs hots... it unusual, but it works. I didn't find anybody using ESXi 6.5 without local datastore on the web when I research about it. UPDATE: yep, I remove the 9211-8i (M1015 flashed) controller today and passthrough the cougar native controller instead, and it works fine. ahci mode, write cache enable (you need to see via terminal, the control panel didnt enable the option). no drive in the ODD bay. This is amazing, it boots esxi 6.5 on USB, no local drive for ESXI but use a NFS datastore for 2 VM (macOS and Windows 10) and boot XPEnology with passtrought controller. everything is working fine, with autostart working and no problem at all. but I notice some strange things since I move from LSI to native cougar... 1) i populate the bays 1-4 on microserver and the controller bios see all the drives (including 4TB and 6TB ones) but DSM see drives from bay 2 to 5. When I use the LSI controller, it sees the drives on bay 1 to 4 but in reverse order (drive 1 on bay 4, etc, etc) Now it sees the drive 1 on bay 2, drive 2 on bay 3, etc, etc. strange, but it seems to be cosmetic only. 2) the fan and temps overall are a little lower now, i think the LSI controller was hotter and affect the air inside the case 3) performance via network seems to be a little better, transfer flies or benchmarks are showing numbers around 2% higher than before. CPU look like a little lower too. This is a surprise for me, i thought 9211-8i will be faster than the native intel cougar chipset controller.
  2. oculto

    DSM 6.1.x Loader

    just to share: ESXi 6.5 on Microserver Gen8, pci-e passthrought LSI, etc, etc... It works better if you use VMXNET3 NIC with MANUAL MAC ADDRESS (the same you have on grub), adjust the settings on vmk file.
  3. oculto

    DSM 6.1.x Loader

    for whom who has another real synology with CMS (Central Management System), you can use this package to connect the XPENOLOGY and centralize all the notifications. The smartphone app FINDER will receive the messages if the REAL SYNOLOGY as paired and will be the MASTER on CMS. So, you dont need the PUSH SERVICE ANYMORE. But loader 1.02b has some problems for me, the CONTROL PANEL > INFO > General tab is black and the CMS is having some problems to allow all functionality (it works fine with previous loader/DSM), but notification IS WORKING. It could be great if the GENERAL BLANK PAGE was fixed, because it will fix CMS communication (they use the same method to grab the results) ps. I use regular SN/MAC from the loader, no customization. on ESXi 6.5
  4. oculto

    DSM 6.1.x Loader

    Running HP Microserver Gen8 with ESXi 6.5 and 1.02B loader and DSM 6.1.2-15132 , PCI Pass throught (LSI) with some problems with CMS (Central Management System) with I use to consolidate notifications and use mobile applications through a original synology i have. on control panel > info center > general TAB is blank, and it seems to be a problem with CMS join because on HOST it connects, confirm, but didnt get any status and disconnect after a few moments (no disconnection in fact, just a update error with some weird message about HDD hibernation, with is not true). It works on olders versions of DSM / Jun's loader... I would ask to Jun to put 5 seconds timeout on loader, because on ESXi 1 second is too short to get control on console and select the appropriate grub menu item.
×
×
  • Create New...