Transition Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About DemoGeek

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yes I tried every option out there , including E1000, E1000e, VXMNet3 ... but no luck... I figured out after some searching that my CPU is old one Xeon - SandyBridge on this particular test. Same server , no issues with the 3615 or 3617 install. I believe that might be the issue.
  2. Not able to get DS918+ running on ESXi6.7 SU3 Can run DS3617 and DS3615 by following the the instructions but tried everything for DS918+ to work but no luck? Can anyone share their synoboot.img or ova file for DS918+ Thanks
  3. I am having this strange issue where Jun Loader 1.04(b) with DS918+ is not working with ESXi 6.7SU2. In order to troubleshoot, i turned on the serial interface as per instructions above and got the serial connection successfull but it does not show anything other than the initial screen of GNU Grub version 2.02 ==================================================================== GNU GRUB version 2.02 +----------------------------------------------------------------------------+ | DS918+ 6.2.1/6.2 Baremetal with Jun's Mod v1.04b | | DS918+ 6.2.1/6.2 Baremetal with Jun's Mod v1.04b Reinstall | |*DS918+ 6.2.1/6.2 VMWare/ESXI with Jun's Mod v1.04b | | | +----------------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands . before booting or `c' for a command-line. ==================================================================== THIS IS THE ONLY SCREEN I SEE on the SERIAL CONSOLE What am I missing?
  4. I found this issue consistent with following flavors of nested installation 1. VMWorkStation(Win10) ==> Syn(A1) ==>Syn(B).Nested VM. 2. ESXi==> Vmworkstation (Win2016)==>Syn(A2). Nested VM but no ip in both cases. Tried everything like changing Mac from grub.cnf but no ip taken by nested VM Interestingly if I do nested VM inside actual physical synology, same boot loaders etc, it WORKS.... What am I missing in Case#1/2 here? Any help is greatly appreciated....
  5. SYN-A Mac address is already updated on boot. By same .img file, I meant same drivers etc.b. I have also changed SYN-B Mac just on case but no luck!!!!
  6. Thanks for the reply. what you just suggested is a plan b. For now the main reason for this approach is manageability. Vmworkstation is behind the CGNAT and it is much easier to control one VM machine with remote access than multiple machines. For some reason SYN-B not getting an IP even though same .img file is running as basis of SYN-A. I tried following but no luck 1. Turn off promiscuous mode for Ethernet 2. Update the drivers (latest) for 1.04(b) loader. 3. Change NIC to e1000 in vmx for Syn-A. Strange thing is that the issue happening only on nested Xpenolgy and not on WinLite or Linux machine.
  7. Following is my setup Core i5-4250u running windows and then VMWorkstation 15.5 Pro. Inside VMWorkstation, running 1.04(b) loader DS918+ - Lets say SYN-A Now inside SYN-A running two virtual machines (Windows 10 Lite and another Synology SYN-B) SYN A has two NICs, One is bridged to local LAN and other is Natted (VMWorkstation NAT) Issue is that Windows Lite is getting the IP on both NICs but SYN-B is booting but not getting an IP on boot I have already checked Virtualiz Intel VT-x/EPT or AMD-V/RVI inside the SYN-A properties of CPU for SYN-A in VMWorkstation. Does anyone know why I am not able to get the IP for the SYN-B (Nested virtualization - SYN B is nested inside SYN A)? Read some posts that it is Ubuntu issue with NIC not enabled for promiscuous mode in nested situation. Any other clues or thoughts?
  8. Looking for same!!!! Anyone.... This is a great idea!!!!