Xpenology DSM 6.1 in KVM...

[BLinux]

I was trying to post on the xpenology forum, but their account confirmation email is taking forever. So, I thought maybe some people here might have some ideas...

I'm trying to test out xpenology with dsm 6.1 in KVM virtual machine. I'm using the Jun's 1.0.2b loader for DSM 6.1 from here:

DSM 6.x.x Loader

I've set the VM to boot off USB storage that is mapped to the DS3617xs image file. And I have the NIC configured to emulate e1000 and connected to a bridge port that all my other VMs connect to get direct access to my lab network. The VM does boot the USB image fine and tries to DHCP an IP address, as can be seen in my dhcp server logs:

Aug 10 16:41:28 mumbai dhcpd: DHCPDISCOVER from 52:54:00:5d:95:65 (Diskstation) via eth0
Aug 10 16:41:28 mumbai dhcpd: DHCPOFFER on 192.168.0.115 to 52:54:00:5d:95:65 (Diskstation) via eth0

But it never really configures that IP address on it's NIC. So, I can't ping that address at all, much less pull up the DSM web gui.

So, I connected to serial console and I see this:

DiskStation login: root


BusyBox v1.16.1 (2017-02-14 03:57:39 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

DiskStation> ifconfig 
eth0      Link encap:Ethernet  HWaddr 52:54:00:5D:95:65  
          inet addr:169.254.189.70  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:763 errors:2 dropped:0 overruns:0 frame:2
          TX packets:271 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:68757 (67.1 KiB)  TX bytes:85650 (83.6 KiB)

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:7 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:784 (784.0 B)  TX bytes:784 (784.0 B)

you can see the MAC address matches the DHCP logs, but it has a totally different address.

can anyone help?

 

[Marsh]

You may be already aware of the tutorial here
Tutorial: Install/Migrate DSM 5.2 to 6.0.2 (Jun's loader)

Change vid=0x090C to vid=0x[your usb drive vid]

Change pid=0x1000 to pid=0x[your usb drive pid]

Change sn=C7LWN09761 to sn=[URL='https://xpenology.github.io/serial_generator/serial_generator_new.html']generate your sn here with DS3615xs model

Change mac1=0011322CA785 to mac1=[your NIC MAC address]. You can also add set mac2=[your NIC MAC address #2] and so on until mac4 if you have multiple NICs. However, this is not necessary.[/URL]

 

[BLinux]

You may be already aware of the tutorial here
Tutorial: Install/Migrate DSM 5.2 to 6.0.2 (Jun's loader)

Change vid=0x090C to vid=0x[your usb drive vid]

Change pid=0x1000 to pid=0x[your usb drive pid]

Change sn=C7LWN09761 to sn=generate your sn here with DS3615xs model

Change mac1=0011322CA785 to mac1=[your NIC MAC address]. You can also add set mac2=[your NIC MAC address #2] and so on until mac4 if you have multiple NICs. However, this is not necessary.

yes, i did set the SN and MAC1 to match. I wasn't sure how i would get the USB VID/PID in KVM, but either way, it seems to have booted the USB image just fine. The problem is why it won't take the DHCP address?

interestingly, if I manually set the IP address on the serial console:

DiskStation> ifconfig eth0 192.168.0.115 netmask 255.255.255.128
DiskStation> ifconfig 
eth0      Link encap:Ethernet  HWaddr 52:54:00:5D:95:65  
          inet addr:192.168.0.115  Bcast:192.168.0.127  Mask:255.255.255.128
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:365 errors:23 dropped:0 overruns:0 frame:23
          TX packets:245 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:33186 (32.4 KiB)  TX bytes:72195 (70.5 KiB)

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:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:672 (672.0 B)  TX bytes:672 (672.0 B)

It will take, and then I can browse to the DSM Web UI just fine... except that after a few minutes, it reverts the IP back to the one in the OP.

Meanwhile, when I am able to connect to the webui set page, it says "No hard disk found on DS3617xs" ... I've tried SCSI and VirtIO (didn't think this would work, but tried it anyway) and still no hard disk found...

 

[BLinux]

LOL OMG... well, i got it to work.. but the approach is dodgy as hell...

So, basically, I leave the serial console connection open, and every time it reverts to that 169.254. address I force it back to the address DHCP is giving it... this got me connected and through the setup UI.

Oh, and by the way, I had to attach the virtual disks as IDE drives for some reason... once I did that it recognized them.

uploaded the DSM pat file and it installed just fine.. except upon boot up, DHCP didn't work again, so once again, back into serial console and forced the IP. Then I logged into the DSM UI and went to control panel->network->network interface and configured a static IP to the NIC. Now that DHCP is off, the IP is stable and doesn't flip on me.

Anyway... it boots up now, but very strange way to get there....

 

[epicurean]

Be careful with this latest bootloader especially if you have more than 12 drives during updates. Whenever you update, even if you have changed the configuration to take in more drives than 12, it will revert back to default 12 again. I personally find the 3615 image more stable than the 3617.

Saying this, the 1.02b bootloader is pretty darn stable compared to the earlier versions

 

[BLinux]

Be careful with this latest bootloader especially if you have more than 12 drives during updates. Whenever you update, even if you have changed the configuration to take in more drives than 12, it will revert back to default 12 again. I personally find the 3615 image more stable than the 3617.

Saying this, the 1.02b bootloader is pretty darn stable compared to the earlier versions

thanks for pointing that out. but aren't both 3615 and 3617 the same 12-bay models?

either way, I'm actually not going to really use this for it's NAS functions. mainly looking to use it for the applications DSM 6.1 has that make certain tasks really simple. i'm mainly testing xpenology out to see if I can get rid of my real Synology as I have other systems for NAS function... my main attraction to DSM is for the applications.

 

[BLinux]

BTW, i need to verify ... but I think the DHCP problem is not an issue with Xpenology at all... I forgot I had one of my client's VPN tunnels running on this machine, and whenever I have VPN on, it totally messes up the bridge port and VM that aren't already booted. Not sure why that is, but I've seen it before and it requires me shutting down the VPN, shutting down the bridge port and restarting NetworkManager. I'm going to re-install while in a known good bridge configuration with the VPN off to verify that was the problem. Glad I had a way to work around it, but sure would be nice if I didn't have to keep forcing the IP address on the serial console.