WhileDekker Posted October 21, 2018 #1 Posted October 21, 2018 (edited) Hi this is how I managed to get DSM 6.2 running on the free VMWare Workstation Player 15. I know there are other tutorials for VMWare Workstation Pro and the procedure is quite similar. Following on of these tutorials (https://xpenology.com/forum/topic/13006-tutorial-vmware-workstation-dsm-62-install-esxi-compatible) brought me very close to my goal but still I had to do some try and error, therefore I am sharing my piece of the cake here. Please note: This is how I made it work, dont blame me if this is not working for you. 1. Loader Download Jun's Loader v1.03b DS3617xs Synoboot_3617.zip | 19.5 MB | MD5 = 94d18efbc349da2bd45d6e57adabc54f 2. Convert Loader img to vmdk with Starwind V2V Image Converter (free) 3. Run the "new vm wizzard" on VMWare Workstation Player The wizzard always creates a data hd, you can use this as your first data hd or delete it later. Finish the wizard Now edit the virtual machine settings This is what I do usually - Change cpu and ram to 4/4 - remove cd, soundcard, printer - change LAN to bridged - add x more scsi hds (same settings as when using the wizard) Copy the two vmdk files from the conversion above and add as a SATA hd (select the 1k file) and select keep existing format This is how my setup looks after that Power up the vm and you will realize it doesnt boot – change bios boot order and after saving select VMWare while booting (you need to be real quick this is only showing for some secs). Find your ds via find.synology.com and run installation as usual (I downloaded latest 6.2. using the link on xpenology to be sure to use a supported version). When the HD erase notification appears it should show you all your data hds you added – I added 1 boot hd and 3 data hds so 3 hds should be shown. Takeaways: - I was using an old version of Starwind V2V converter, this converted the image but apparently sth was different and it didnt really boot up correctly (no LAN). - When configuring the synoboot as scsi I was not able to connect to my nas (didnt get an IP from DHCP) - I had to select VMWare/ESXi on boot otherwise no data hd was shown during installation and dsm installation failed - I tried the same with DS918+, but this got me into a installation loop - Tested upgrade to 6.2.1. after that ds was broken – I guess the loader is not ready for it yet – so make sure auto update is disabled Again, this is just my thoughts and how I managed it. Maybe things in this are wrong or understood wrong by me - but at least this is how I managed to get it running. Cheers Edited October 21, 2018 by WhileDekker 1 Quote
virtuaworld Posted January 3, 2019 #2 Posted January 3, 2019 Hello, I try to follow your tutorial but I don't obtain "booting kernel" and IP Adress. I have already a XPenology DSM 6.1 but I can't running a DSM with VMware Workstation Pro 15 Why is it so difficult to run DSM 6.2 ? Thank you for your help Quote
john-h Posted January 26, 2019 #3 Posted January 26, 2019 Hi WhileDekker, Great tutorial. I followed it and can very easily spin up a XPE VM in VMWare Workstation 15. All is good except 2 problems 1. XPE will not recognize more than the SATA boot drive and 1 other SCSI disk. No matter what other port I choose for the SCSI disks, they are not visible in XPE. I think I recreated this VM about 20 times trying different configurations. I tried adding up to 12 drives in the initial creation of the VM, no luck. I tried with just the boot drive and adding data drives one by one, and all at once, after booting XPE, no luck. No matter what I do, it will only see one data drive. Other than that, I can create a volume and pool with that single drive, share it to my home network, and add packages with no problems. 2. XPE will reset whenever I reboot the VM. It boots right up, but goes to the initial menu of setting up a new Synology, including reinstalling DSM. All settings, drives are gone. I checked and the VM sees the boot drive as persistent, and the data drive is also listed as persistent. I can create and revert to a snapshot no problem, but weird that I cannot reboot the VM. Have you experienced any of these issues? If not, perhaps I should create a new topic and see if the other members can shed some light. Thanks again for the simple tutorial. Quote
john-h Posted January 26, 2019 #4 Posted January 26, 2019 Well apparently now I can add/remove drives if I use SATA drives during a live VM session, so that is good. The system just will not see SCSI drives other than the first one. I still have the problem that the VM resets if rebooted. I will keep looking into it and post back. Quote
sstyle Posted January 30, 2019 #5 Posted January 30, 2019 (edited) Ok, but how to update from 6.1.7 with 1.02b loader to 6.2 with 1.03b? Edited January 30, 2019 by sstyle Quote
Olegin Posted January 30, 2019 #6 Posted January 30, 2019 1 минуту назад, sstyle сказал: Ok, but how to update from 6.17 with 1.02b loader to 6.2 with 1.03b? What dsm version do you use? Quote
sstyle Posted January 30, 2019 #7 Posted January 30, 2019 (edited) 2 minutes ago, Olegin said: What dsm version do you use? DSM 6.1.7-15284 (DS3615xs) Edited January 30, 2019 by sstyle Quote
Olegin Posted January 30, 2019 #8 Posted January 30, 2019 16 минут назад, sstyle сказал: DSM 6.1.7-15284 (DS3615xs) Stop vm. Change synoboot.img to 1.03 (before changing edit sn and mac in grub.cfg), power on and migrate to the newerest dsm version. Quote
sstyle Posted January 30, 2019 #9 Posted January 30, 2019 Just now, Olegin said: Stop vm. Change synoboot.img to 1.03 (before changing edit sn and mac in grub.cfg), power on and migrate to the newerest dsm version. Tried this, but DS does not load after "Change synoboot.img to 1.03". Quote
Olegin Posted January 30, 2019 #10 Posted January 30, 2019 13 минуты назад, sstyle сказал: Tried this, but DS does not load after "Change synoboot.img to 1.03". Change set default='2' in grub.cfg. Quote
sstyle Posted January 30, 2019 #11 Posted January 30, 2019 1 hour ago, Olegin said: Change set default='2' in grub.cfg. does not matter. I tried all 3 variants in boot menu Quote
januszmirek Posted March 11, 2020 #13 Posted March 11, 2020 Did anyone succeed with 1.04b loader and 918+ on VMWare machine? I cannot even find it on the network. 1.03b works flawlessly. Quote
januszmirek Posted March 12, 2020 #14 Posted March 12, 2020 Scratch that;) For unknown reason I was selecting SCSI as a drive type for main disk instead of SATA. Rookie's mistake. DSM 6.2.2-24922 Update 5 works great on VMWare Fusion v.11 running on MacOs 10.14. I was however using modded loader. Should also work with standard 1.04b though Quote
Krickk Posted March 18, 2020 #15 Posted March 18, 2020 Hi, Thanks for this tuto :) I've a problem, it boots normally but I cannot see it in synologgy assistant or find.synology.com Any Idea? Thx Krickk Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.