Jump to content
XPEnology Community

Esxi DSM 6 ovf deploy - Jun's loader


koroziv

Recommended Posts

Not that I know of. Try importing in ws12 jun's loader directly ( the alpha for 6.1). After importing do not start the vm, edit the settings to your preferences. Add a drive (on the scsi controller) for install save the settings and export. You might need to convert it before export, make it hw 10 or 9.

As a general note, I use my router admin ui to determine what ip is allocated to the vm. If I get on the pc today I'll try to make one for hw version 9.

We can setup a team viewer session if you want, pm me and I'll try to help.

 

Sent from my SM-G930F using Tapatalk

Link to comment
Share on other sites

The hw 10 vm should work in esxi 5.5. I can't test but that's why I chose hw version 10 and not 11 or 12, many use the old 5.5.

In ws12 I can import and run hw10 version with no issues, didn't try the hw13 one.

What hardware are you using?

 

Sent from my SM-G930F using Tapatalk

 

I'm using the following :

 

HP Proliat DL380 G7

ESXi 5.5

(standard/built in network and controller)

 

I have a lot of other VM's running on this host and they work fine.

I have only 1 LAN interface active on the ESX and all other VM's are using it fine.

DHCP works to other VM's.

Is there a way to what the console says?

 

In WS12 I get:

"The import failed because C:\Users\XXXX\Desktop\6.1hw10\6.1.ovf did not pass OVF specification conformance or virtual hardware compliance checks.

 

Click Retry to relax OVF specification and virtual hardware compliance checks and try the import again, or click Cancel to cancel the import. If you retry the import, you might not be able to use the virtual machine in VMware Workstation."

 

I press retry and the ovf gets deployed in WS12 but when I fire it up the console says:

 

EFI VMware Virtual SCSI Hard Drive (0.0) : Unsuccessfull

EFI VMware Virtual SATA Hard Drive (0.0) : Unsuccessfull

 

WS12 is my second option, I want to get it to work in ESX. I'm thinking that I can convet it to ESX if I get it to work in WS12.

Link to comment
Share on other sites

I didn't really helped :sad: nothing worked; and the lag from ws12 in teamviewer was legendary :smile:

I tried to use jun's loader directly, to eliminate all possible issues generated from my created vm, but that also didn't get an ip address.

Try and create another xpeno 5.2 for test, see if that works; since you already have one going the new one should also work; if not there is a problem with the current esxi network setup.

Not sure if the esxi version is the problem, but I hope you find a solution (and share it with us)

Link to comment
Share on other sites

I'm having the same problem as zagor.

Deployed ovf fine, but can't find synology in network.

It isn't requesting ip via dhcp, so network doesn't seem to work (tried E1000 and E1000E) and tried Different MAC's also.

Also tried the 4 boot options and isn't working for me either.

I'm on ESXi 6.5 with Loader 2.0.9 installed to also run MacOS, gonna try to install on another host without that loader, maybe the loader is the problem.

Link to comment
Share on other sites

I've got problem with importing ovf then i choosed simplest possible solution. Create new VM as usual, linux - other 64 bit, etc. Then add 1st hdd from jun's package and add other hhd's tocreate volumes. Thats all. DSM 6.1 works with no problem.

 

Im having ESXI 6.

Link to comment
Share on other sites

That is the simplest and easiest way to do it.

I made this vm's for the lazy and for those that have issues with jun's images, like I had the first time with the loader for dsm 6.0. Unfortunately some setups are to diferent from mine, hardware or software gremlins can cause problems.

 

Sent from my SM-G930F using Tapatalk

Link to comment
Share on other sites

I've got problem with importing ovf then i choosed simplest possible solution. Create new VM as usual, linux - other 64 bit, etc. Then add 1st hdd from jun's package and add other hhd's tocreate volumes. Thats all. DSM 6.1 works with no problem.

 

Im having ESXI 6.

Wow I feel like a Super Noob now. Wish I've known this a long time ago. Thanks brother!

 

Sent from my XT1565 using Tapatalk

Link to comment
Share on other sites

That's the point, it can't find the DSM 6.1 using find.synology.com or the synology assistant program.

I have 2 other DSM's running on the same ESXi host that are working fine, that's the DSM 5.2 from Xenoboot and DSM 6.0.1 from oktisme.

Also tried to migrate the DSM 6.1 to another ESXi host (without loader), same problem, it can't find the synology and isn't requesting ip from dhcp server.

Link to comment
Share on other sites

Here you have a video with the vm creation process

 

No time to put it on youtube, and I'm not sure that it won't be taken down for various legal reasons.

You will see there that I get an ip, if find.synology.com is not working try using other means to see all the clients in your lan.

 

Edit - video removed, to little info for a 400 mb file :smile: maybe i'll make a better one someday.

Edited by Guest
Link to comment
Share on other sites

That's the point, it can't find the DSM 6.1 using find.synology.com or the synology assistant program.

I have 2 other DSM's running on the same ESXi host that are working fine, that's the DSM 5.2 from Xenoboot and DSM 6.0.1 from oktisme.

Also tried to migrate the DSM 6.1 to another ESXi host (without loader), same problem, it can't find the synology and isn't requesting ip from dhcp server.

 

Its possible that other DSM VM you have running has the same MAC as the new one you try to run with DSM 6.1. That way one VM wont be found by find.synology.com.

Try this:

- VM settings: in options set boot time to few seconds,

- when you start new VM, with DSM 6.1, in grub options click 'e',

- edit command by adding: set mac1=

- F10 to start VM.

Link to comment
Share on other sites

I didn't really helped :sad: nothing worked; and the lag from ws12 in teamviewer was legendary :smile:

I tried to use jun's loader directly, to eliminate all possible issues generated from my created vm, but that also didn't get an ip address.

Try and create another xpeno 5.2 for test, see if that works; since you already have one going the new one should also work; if not there is a problem with the current esxi network setup.

Not sure if the esxi version is the problem, but I hope you find a solution (and share it with us)

 

Feedback:

 

ESXi 6.5 did not work same problem.

 

Some progress:

It seems that there is some problem with DHCP, the DSM 6 is not requesting/getting ip correctly.

I tried force set ip dirict to MAC:

 

arp -s 192.168.1.236 00-0C-29-BB-AF-89

 

THIS WORKED...not as expected, but it seems that it "fired up" the DHCP client in the DSM and now it got an IP.

Not the ip I tried to set, but another ip from the DHCP server. I can now see it with Synology Assistant.

 

I will investigate more when I have time, but for now I can access the DSM.

Link to comment
Share on other sites

That's the point, it can't find the DSM 6.1 using find.synology.com or the synology assistant program.

I have 2 other DSM's running on the same ESXi host that are working fine, that's the DSM 5.2 from Xenoboot and DSM 6.0.1 from oktisme.

Also tried to migrate the DSM 6.1 to another ESXi host (without loader), same problem, it can't find the synology and isn't requesting ip from dhcp server.

 

Its possible that other DSM VM you have running has the same MAC as the new one you try to run with DSM 6.1. That way one VM wont be found by find.synology.com.

Try this:

- VM settings: in options set boot time to few seconds,

- when you start new VM, with DSM 6.1, in grub options click 'e',

- edit command by adding: set mac1=

- F10 to start VM.

 

No, I am using different mac's for all of my VM's.

 

I connected a serial console using named pipe from the DSM 6.1 to my Ubuntu VM on the same host, as you you see the nic is not requesting an ip from the dhcp server (checked the logs in pfsense dhcp client list also).

 

root@ubuntu-server:/home/donald# screen /dev/ttyS0 115200
:: Loading module cnic ... [FAILED]
:: Loading module r8169 ... [  OK  ]
:: Loading module tg3 ... [  OK  ]
:: Loading module usbnet ... [  OK  ]
:: Loading module ax88179_178a ... [  OK  ]
:: Loading module button ... [  OK  ]
mount: open failed, msg:No such file or directory
mount: mounting /dev/bus/usb on /proc/bus/usb failed: No such device
ln: /proc/bus/usb/devices: No such file or directory
:: Loading module synobios ... [  OK  ]
udhcpc (v1.16.1) started
eth0      Link encap:Ethernet  HWaddr 00:11:32:2C:A7:85
         inet addr:169.254.58.122  Bcast:169.254.255.255  Mask:255.255.0.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:0 (0.0 B)  TX bytes:890 (890.0 B)
         Interrupt:19 Memory:fe120000-fe140000

lo        Link encap:Local Loopback
         inet addr:127.0.0.1  Mask:255.0.0.0
         UP LOOPBACK RUNNING  MTU:65536  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

:: Starting syslogd ... [  OK  ]
:: Starting scemd
:: Starting services in background
Starting findhostd in flash_rd...
Starting services in flash_rd...
Running /usr/syno/etc/rc.d/J01httpd.sh...
Starting httpd:80 in flash_rd...
Starting httpd:5000 in flash_rd...
Running /usr/syno/etc/rc.d/J03ssdpd.sh...
/usr/bin/minissdpd -i eth0
(15): upnp:rootdevice
(51): uuid:upnp_SynologyNAS-0011322ca785::upnp:rootdevice
(58): Synology/synology_bromolow_3615xs/6.1-15047/169.254.58.122
(47): http://169.254.58.122:5000/description-eth0.xml
Connected.
done.
/usr/syno/bin/reg_ssdp_service 169.254.58.122 0011322ca785 6.1-15047 synology_bromolow_3615xs eth0
Running /usr/syno/etc/rc.d/J04synoagentregisterd.sh...
Starting synoagentregisterd...
Running /usr/syno/etc/rc.d/J30DisableNCQ.sh...
Running /usr/syno/etc/rc.d/J80ADTFanControl.sh...
Running /usr/syno/etc/rc.d/J98nbnsd.sh...
Starting nbnsd...
Running /usr/syno/etc/rc.d/J99avahi.sh...
Starting Avahi mDNS/DNS-SD Daemon
cname_load_conf failed:/var/tmp/nginx/avahi-aliases.conf
:: Loading module hid ... [  OK  ]
:: Loading module usbhid ... [  OK  ]
============ Date ============
Wed Mar  1 12:24:53 UTC 2017
==============================
starting pid 5897, tty '': '/sbin/getty 115200 console'
Wed Mar  1 12:24:54 2017

DiskStation login:

 

edit:

 

Nevermind, finally found the problem.

You can't change change the MAC from the VM in vmware, the mac 00:11:32:2C:A7:85 is somewhere hardcoded in the loader, so you MUST use that one.

Changed it to 00:11:32:2C:A7:85 in the .vmx file (or using vCenter or UI from host) and is requesting IP now...

 

update:

So, problem is: when the mac address in the vm for the e1000 nic is different from the one in the loader it won't work, so both must be the same.

 

Installed DSM 6.1 and all is working now.

 

Regards,

Donald.

Edited by Guest
Link to comment
Share on other sites

It seems you don't have any dhcp server in network segment or, dhcp server can't offer any IP

 

eth0      Link encap:Ethernet  HWaddr 00:11:32:2C:A7:85
         inet addr:169.254.58.122  Bcast:169.254.255.255  Mask:255.255.0.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:0 (0.0 B)  TX bytes:890 (890.0 B)
         Interrupt:19 Memory:fe120000-fe140000

Look 169.254.58.122

It's' apipa address, it's' self assigned when network card didn't found any dhcp or dhcp can't serve any address.

Link to comment
Share on other sites

If you want to change the Mac you need to edit the cfg file on the boot vmdk. I think you can also press c or e during the boot sequence and issue a command like

Mac 00xx00xx0whatever

Not sure about the key and the correct syntax for changing the Mac address but I remember reading something about that. Maybe someone can clear this up ?

I can confirm that the Mac ending in a785 is the one in the loader, all my test vm's have the same one.

 

Edit

Lol, just a few posts above:

Hit e during boot

Set mac1=

 

Thanks chege

Link to comment
Share on other sites

I connected a serial console using named pipe from the DSM 6.1 to my Ubuntu VM on the same host, as you you see the nic is not requesting an ip from the dhcp server (checked the logs in pfsense dhcp client list also).

 

root@ubuntu-server:/home/donald# screen /dev/ttyS0 115200
:: Loading module cnic ... [FAILED]
:: Loading module r8169 ... [  OK  ]
:: Loading module tg3 ... [  OK  ]
:: Loading module usbnet ... [  OK  ]
:: Loading module ax88179_178a ... [  OK  ]
:: Loading module button ... [  OK  ]
mount: open failed, msg:No such file or directory
mount: mounting /dev/bus/usb on /proc/bus/usb failed: No such device
ln: /proc/bus/usb/devices: No such file or directory
:: Loading module synobios ... [  OK  ]
udhcpc (v1.16.1) started
eth0      Link encap:Ethernet  HWaddr 00:11:32:2C:A7:85
         inet addr:169.254.58.122  Bcast:169.254.255.255  Mask:255.255.0.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:0 (0.0 B)  TX bytes:890 (890.0 B)
         Interrupt:19 Memory:fe120000-fe140000

lo        Link encap:Local Loopback
         inet addr:127.0.0.1  Mask:255.0.0.0
         UP LOOPBACK RUNNING  MTU:65536  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

:: Starting syslogd ... [  OK  ]
:: Starting scemd
:: Starting services in background
Starting findhostd in flash_rd...
Starting services in flash_rd...
Running /usr/syno/etc/rc.d/J01httpd.sh...
Starting httpd:80 in flash_rd...
Starting httpd:5000 in flash_rd...
Running /usr/syno/etc/rc.d/J03ssdpd.sh...
/usr/bin/minissdpd -i eth0
(15): upnp:rootdevice
(51): uuid:upnp_SynologyNAS-0011322ca785::upnp:rootdevice
(58): Synology/synology_bromolow_3615xs/6.1-15047/169.254.58.122
(47): http://169.254.58.122:5000/description-eth0.xml
Connected.
done.
/usr/syno/bin/reg_ssdp_service 169.254.58.122 0011322ca785 6.1-15047 synology_bromolow_3615xs eth0
Running /usr/syno/etc/rc.d/J04synoagentregisterd.sh...
Starting synoagentregisterd...
Running /usr/syno/etc/rc.d/J30DisableNCQ.sh...
Running /usr/syno/etc/rc.d/J80ADTFanControl.sh...
Running /usr/syno/etc/rc.d/J98nbnsd.sh...
Starting nbnsd...
Running /usr/syno/etc/rc.d/J99avahi.sh...
Starting Avahi mDNS/DNS-SD Daemon
cname_load_conf failed:/var/tmp/nginx/avahi-aliases.conf
:: Loading module hid ... [  OK  ]
:: Loading module usbhid ... [  OK  ]
============ Date ============
Wed Mar  1 12:24:53 UTC 2017
==============================
starting pid 5897, tty '': '/sbin/getty 115200 console'
Wed Mar  1 12:24:54 2017

DiskStation login:

 

edit:

 

Nevermind, finally found the problem.

You can't change change the MAC from the VM in vmware, the mac 00:11:32:2C:A7:85 is somewhere hardcoded in the loader, so you MUST use that one.

Changed it to 00:11:32:2C:A7:85 in the .vmx file (or using vCenter or UI from host) and now requesting IP now...

 

Regards,

Donald.

 

Its exactly what i told you. If you would try my solution you would know where the problem is.

 

btw. MAC is hardcoded in grub.cfg in jun's loader.

Link to comment
Share on other sites

I connected a serial console using named pipe from the DSM 6.1 to my Ubuntu VM on the same host, as you you see the nic is not requesting an ip from the dhcp server (checked the logs in pfsense dhcp client list also).

 

root@ubuntu-server:/home/donald# screen /dev/ttyS0 115200
:: Loading module cnic ... [FAILED]
:: Loading module r8169 ... [  OK  ]
:: Loading module tg3 ... [  OK  ]
:: Loading module usbnet ... [  OK  ]
:: Loading module ax88179_178a ... [  OK  ]
:: Loading module button ... [  OK  ]
mount: open failed, msg:No such file or directory
mount: mounting /dev/bus/usb on /proc/bus/usb failed: No such device
ln: /proc/bus/usb/devices: No such file or directory
:: Loading module synobios ... [  OK  ]
udhcpc (v1.16.1) started
eth0      Link encap:Ethernet  HWaddr 00:11:32:2C:A7:85
         inet addr:169.254.58.122  Bcast:169.254.255.255  Mask:255.255.0.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:0 (0.0 B)  TX bytes:890 (890.0 B)
         Interrupt:19 Memory:fe120000-fe140000

lo        Link encap:Local Loopback
         inet addr:127.0.0.1  Mask:255.0.0.0
         UP LOOPBACK RUNNING  MTU:65536  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

:: Starting syslogd ... [  OK  ]
:: Starting scemd
:: Starting services in background
Starting findhostd in flash_rd...
Starting services in flash_rd...
Running /usr/syno/etc/rc.d/J01httpd.sh...
Starting httpd:80 in flash_rd...
Starting httpd:5000 in flash_rd...
Running /usr/syno/etc/rc.d/J03ssdpd.sh...
/usr/bin/minissdpd -i eth0
(15): upnp:rootdevice
(51): uuid:upnp_SynologyNAS-0011322ca785::upnp:rootdevice
(58): Synology/synology_bromolow_3615xs/6.1-15047/169.254.58.122
(47): http://169.254.58.122:5000/description-eth0.xml
Connected.
done.
/usr/syno/bin/reg_ssdp_service 169.254.58.122 0011322ca785 6.1-15047 synology_bromolow_3615xs eth0
Running /usr/syno/etc/rc.d/J04synoagentregisterd.sh...
Starting synoagentregisterd...
Running /usr/syno/etc/rc.d/J30DisableNCQ.sh...
Running /usr/syno/etc/rc.d/J80ADTFanControl.sh...
Running /usr/syno/etc/rc.d/J98nbnsd.sh...
Starting nbnsd...
Running /usr/syno/etc/rc.d/J99avahi.sh...
Starting Avahi mDNS/DNS-SD Daemon
cname_load_conf failed:/var/tmp/nginx/avahi-aliases.conf
:: Loading module hid ... [  OK  ]
:: Loading module usbhid ... [  OK  ]
============ Date ============
Wed Mar  1 12:24:53 UTC 2017
==============================
starting pid 5897, tty '': '/sbin/getty 115200 console'
Wed Mar  1 12:24:54 2017

DiskStation login:

 

edit:

 

Nevermind, finally found the problem.

You can't change change the MAC from the VM in vmware, the mac 00:11:32:2C:A7:85 is somewhere hardcoded in the loader, so you MUST use that one.

Changed it to 00:11:32:2C:A7:85 in the .vmx file (or using vCenter or UI from host) and now requesting IP now...

 

Regards,

Donald.

 

Its exactly what i told you. If you would try my solution you would know where the problem is. If you use command set MAC1= , then mac from esxi VM will be used instead.

 

btw. MAC is hardcoded in grub.cfg in jun's loader.

Link to comment
Share on other sites

When using set MAC1= command will it write it permanently to grub.cfg? or do I need to download the .vmdk to a linux client, mount it there, and edit the grub.cfg and upload it back to the datastore?

 

No, it wont write permamently. It was just to find out problem. You can try jun's xpenology tool to change grub settings.

 

viewtopic.php?f=2&t=24308

 

I've read the topic: viewtopic.php?f=2&t=24308, but I am not clear over if you can remove grub setting MAC completely?

 

I understand that you can change the MAC with Jun's Xpenology tool, but can you unset it and let it take the MAC of

the virtual VM LAN in ESXi ?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...