Recommended Posts

28 minutes ago, dodo-dk said:

 

This works:

 

 

I tried your file but it did not change anything. Shutdown of VM fails with the following error message:

"TASK ERROR: VM quit/powerdown failed"

 

Im using DSM 6.2.2-24922 Update 4.

Link to post
Share on other sites
  • 2 weeks later...

Hey, has anyone managed to get virtio nic working on DSM 6.2.2-24922 Update 4?

 

Using a custom extra.lzma with virtio, virtio_ring and virtio_net modules, all modules load fine but virtio nics do not show up

Edited by x1fr
Link to post
Share on other sites
On 1/16/2020 at 5:43 PM, x1fr said:

Hey, has anyone managed to getvirtionic working on DSM 6.2.2-24922 Update 4?

 

Using a custom extra.lzma with virtio, virtio_ring and virtio_net modules, all modules load fine but virtionics do not show up

Hi, 

 

Would you mind sharing this custom extra.lzma for DSM 6.2.2-24922 and to show the processes of customizing and loading those virtio_net modules?

 

Thanks

Link to post
Share on other sites
1 hour ago, will_xia said:

Hi, 

 

Would you mind sharing this custom extra.lzma for DSM 6.2.2-24922 and to show the processes of customizing and loading those virtio_net modules?

 

Thanks

 

All I did was follow this guide :

 

 

 

While using modules from this topic :

 

 

 

I did not compile modules myself

Link to post
Share on other sites
2 hours ago, will_xia said:

Would you mind sharing this custom extra.lzma for DSM 6.2.2-24922 and to show the processes of customizing and loading those virtio_net modules?

 

the modules are already inside the extra.lzma (at least for 3615/17)

but will not be loaded automatically (not in rc.modules) as i'm not sure of interference when loaded an a non-kvm system

my initial plan was to release the new driver package for 918+ (included virtio drivers as with the new 3615/17 package, still not released because if the i915 problems) and then look if we can test the virtio drivers (if no one else did it until then)

to unpack ans repack the extra.lzma (to mod the rc.modules to load the virtio drivers) any linux can be used, no fance build eviroment or chroot needed

 

Link to post
Share on other sites
9 hours ago, IG-88 said:

 

the modules are already inside the extra.lzma (at least for 3615/17)

but will not be loaded automatically (not in rc.modules) as i'm not sure of interference when loaded an a non-kvm system

my initial plan was to release the new driver package for 918+ (included virtio drivers as with the new 3615/17 package, still not released because if the i915 problems) and then look if we can test the virtio drivers (if no one else did it until then)

to unpack ans repack the extra.lzma (to mod the rc.modules to load the virtio drivers) any linux can be used, no fance build eviroment or chroot needed

 

 

 

Thank you for your answer. In my case, the extra.lzma for loader 1.03b_mod ds3617 DSM 6.2.2 v0.5_test is not work for virtio ethernet nic. 

 

$ cat /etc/rc.modules
EXTRA_MODULES="crc-itu-t crc-ccitt dca mii mdio libphy atl1 atl1e atl1c alx uio ipg jme skge sky2 ptp_pch pch_gbe qla3xxx qlcnic qlge netxen_nic sfc e1000 pcnet32 vmxnet3 bnx2 libcrc32c bnx2x e1000e igb igbvf ixgbe ixgbevf r8101 r8125 r8169 r8168 tg3 usbnet ax88179_178a button evdev ohci-hcd ehci-hcd ehci-pci atl2 e100 igbvf ixgb forcedeth tn40xx be2net cxgb cxgb3 cxgb4 atlantic bna vxge aqc111 asix cx82310_eth et131x i40e i40evf mcs7830 pegasus plusb r8152 rtl8150 s2io xgmac virtio virtio_pci virtio_ring virtio_net virtio_blk"

 

$ ls /usr/lib/modules/update/virtio*
/usr/lib/modules/update/virtio_balloon.ko  /usr/lib/modules/update/virtio_console.ko  /usr/lib/modules/update/virtio_mmio.ko  /usr/lib/modules/update/virtio_pci.ko   /usr/lib/modules/update/virtio_scsi.ko
/usr/lib/modules/update/virtio_blk.ko      /usr/lib/modules/update/virtio.ko          /usr/lib/modules/update/virtio_net.ko   /usr/lib/modules/update/virtio_ring.ko

 

$ dmesg | grep 'virtio'
[  526.653527] virtio-pci 0000:06:03.0: setting latency timer to 64
[  528.391896] virtio_console: Unknown symbol hvc_remove (err 0)
[  528.391935] virtio_console: Unknown symbol hvc_kick (err 0)
[  528.391958] virtio_console: Unknown symbol hvc_alloc (err 0)
[  528.391979] virtio_console: Unknown symbol hvc_poll (err 0)
[  528.392089] virtio_console: Unknown symbol hvc_instantiate (err 0)
[  528.392117] virtio_console: Unknown symbol __hvc_resize (err 0)
[  571.290649] virtio_console: Unknown symbol hvc_remove (err 0)
[  571.290698] virtio_console: Unknown symbol hvc_kick (err 0)
[  571.290722] virtio_console: Unknown symbol hvc_alloc (err 0)
[  571.290744] virtio_console: Unknown symbol hvc_poll (err 0)
[  571.290770] virtio_console: Unknown symbol hvc_instantiate (err 0)
[  571.290794] virtio_console: Unknown symbol __hvc_resize (err 0)

 

Maybe some steps of mine were wrong. Could you tell me about more detail of operation procedure?

Link to post
Share on other sites
22 hours ago, will_xia said:

virtio virtio_pci virtio_ring virtio_net virtio_blk"

 

you did not load virtio_console in rc.modules but its in demesg

beside this, i guess virtio_console would not be needed for storage or network?

virtio_net would be loaded later, so its more interesting to know whats after the virtio_console error

 

its not clear at all that virtio will work, synology does have its own dsm version (with its own kernel config when compiling) when using virtual dsm with kvm (VMM)

(hvc = hypervisor virtual console, part of /drivers/tty/hvc in kernel source)

so i'd guess that ar least virtio_consoles is not possible as the kernel option "hvc_driver" ist not part of the synology kernel for 3617

 

Link to post
Share on other sites
11 hours ago, IG-88 said:

 

you did not load virtio_console in rc.modules but its in demesg

beside this, i guess virtio_console would not be needed for storage or network?

virtio_net would be loaded later, so its more interesting to know whats after the virtio_console error

 

its not clear at all that virtio will work, synologydoes have its own dsm version (with its own kernel config when compiling) when using virtual dsm with kvm (VMM)

(hvc = hypervisor virtual console, part of /drivers/tty/hvc in kernel source)

so i'd guess that ar least virtio_consoles is not possible as the kernel option "hvc_driver" ist not part of the synology kernel for 3617

 

 

Thank you for your quick reply.  The virtio_console may be loaded by default. I will remove it from the update folder and see what happens. 

 

I am not sure it is correct that I added those extra modules in the rc.modules file. It will be great If there is a clear loading guide or a driver package that already contains virtio net driver. Expect it to be implemented in the next version.

Edited by will_xia
Link to post
Share on other sites

linuxrc.syno in root von kvm64 rd.gz

so this is how its loaded in the official virtual dsm

insmod /lib/modules/virtio.ko
insmod /lib/modules/virtio_ring.ko
insmod /lib/modules/virtio_pci.ko
insmod /lib/modules/virtio_blk.ko
insmod /lib/modules/virtio_net.ko
insmod /lib/modules/virtio_scsi.ko
insmod /lib/modules/virtio_console.ko


 

Link to post
Share on other sites
  • 1 month later...

Yes!!!🥳  It took me 3 days of torment and attempts to install it in all possible ways and finally today I was able to install  DSM 6.2 for DS3615xs with Jun's loader 1.03b in Proxmox ( for me virtualization is something new compared to baremetal instalation of Xpenology 5.1 so I even mad my own tutorial for dummies 🙃).

Now... is it possible to access ( created by Proxmox )ZFS pool or I have to create some new BTFRS storage pool in Xpenology?

Edited by ruffpl
Link to post
Share on other sites
  • 2 weeks later...
On 2/26/2020 at 4:09 PM, ruffpl said:

Yes!!!🥳  It took me 3 days of torment and attempts to install it in all possible ways and finally today I was able to install  DSM 6.2 for DS3615xs with Jun's loader 1.03b in Proxmox ( for me virtualization is something new compared to baremetal instalation of Xpenology 5.1 so I even mad my own tutorial for dummies 🙃).

Now... is it possible to access ( created by Proxmox )ZFS pool or I have to create some new BTFRS storage pool in Xpenology?

 

Hi!

 

I'm struggling for 3 days, following every and each tutorial I found, but no success. I'm able to "install" the DSM on a Proxmox VM, but after the 10 minutes countdown that follows the installation, nothing happens.

 

Where is your tutorial?

 

Thanks.

Regards.

Link to post
Share on other sites
3 hours ago, Zamana said:

 

Hi!

 

I'm struggling for 3 days, following every and each tutorial I found, but no success. I'm able to "install" the DSM on a Proxmox VM, but after the 10 minutes countdown that follows the installation, nothing happens.

 

Where is your tutorial?

 

Thanks.

Regards.

 

Did you try adding a serial console to the VM to see what's happening?

Link to post
Share on other sites
3 hours ago, x1fr said:

 

Did you try adding a serial console to the VM to see what's happening?

 

Hi!

 

Yes. And after messing a bit, I'm stuck at this:

 

xterm.thumb.png.c0b4bf6273babdb678b579d928059632.png

 

 

That's my VM configuration:

 

vm.png.84bc1e0cb2aaf45ea58cf45259fba886.png

 

And that's my vm conf file:

 

conf.png.1dab595996de69158ae0fa407ef998e9.png

 

 

Any help is welcome.

 

Thanks.

Regards.

Link to post
Share on other sites

Just after post the reply above, I made some progress.

 

That's the entire serial log session BEFORE the install:

 

starting serial terminal on interface serial0
[    7.293093] ata7: Read current link speed fail, retry 1
[    7.300034] ata7: Read current link speed fail, retry 2
[    7.307094] ata7: Read current link speed fail, retry 3
[    7.308395] ata7: Issued IDENTIFY to non-existent device ?!
[    9.465095] ata7: Read current link speed fail, retry 1
[    9.472030] ata7: Read current link speed fail, retry 2
[    9.479093] ata7: Read current link speed fail, retry 3
 ... [  OK  ]
:: Loading module megaraid_sas ... [  OK  ]
:: Loading module mpt2sas ... [  OK  ]
:: Loading module mpt3sas ... [  OK  ]
Insert net driver(Mindspeed only)...
Starting /usr/syno/bin/synocfgen...
/usr/syno/bin/synocfgen returns 0
Partition Version=0
Partition layout is not DiskStation style.
NOT EXECUTE /sbin/e2fsck.
Mounting /dev/md0 /tmpRoot
mount: lseek failed, msg:Invalid argument
mount: mounting /dev/md0 on /tmpRoot failed: No such device
mount /dev/md0 fail, returns 
Exit on error [3] no init exists...
Tue Mar 10 18:25:35 UTC 2020
none /sys/kernel/debug debugfs rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
none /dev devtmpfs rw,relatime,size=2021324k,nr_inodes=505331,mode=755 0 0
proc /proc proc rw,relatime 0 0
linuxrc.syno failed on 3
starting pid 4127, tty '': '/etc/rc'
:: Starting /etc/rc
:: Mounting procfs ... [  OK  ]
:: Mounting tmpfs ... [  OK  ]
:: Mounting devtmpfs ... [  OK  ]
:: Mounting devpts ... [  OK  ]
:: Mounting sysfs ... [  OK  ]
mdadm: error opening /dev/md1: No such file or directory
rc: Use all internal disk as swap.
rc: No assigned swap disk (sdg2) can be assembled, use all instead.
rc: Use all internal disk as swap.
rc: No disk (sdg2) can be assembled.
swapon: can't stat '/dev/md1': No such file or directory
:: Loading module sg ... [  OK  ]
:: Loading module mdio ... [  OK  ]
:: Loading module fat ... [  OK  ]
:: Loading module vfat ... [  OK  ]
:: Loading module dca ... [  OK  ]
:: Loading module e1000e ... [  OK  ]
:: Loading module i2c-algo-bit ... [  OK  ]
:: Loading module igb ... [  OK  ]
:: Loading module ixgbe ... [  OK  ]
:: Loading module r8168 ... [  OK  ]
:: Loading module libcrc32c ... [  OK  ]
:: Loading module mii ... [  OK  ]
:: Loading module libphy ... [  OK  ]
:: Loading module atl1 ... [  OK  ]
:: Loading module atl1e ... [  OK  ]
:: Loading module atl1c ... [  OK  ]
:: Loading module alx ... [  OK  ]
:: Loading module uio ... [  OK  ]
:: Loading module ipg ... [  OK  ]
:: Loading module jme ... [  OK  ]
:: Loading module skge ... [  OK  ]
:: Loading module sky2 ... [  OK  ]
:: Loading module ptp_pch ... [  OK  ]
:: Loading module pch_gbe ... [  OK  ]
:: Loading module qla3xxx ... [  OK  ]
:: Loading module qlcnic ... [  OK  ]
:: Loading module qlge ... [  OK  ]
:: Loading module netxen_nic ... [  OK  ]
:: Loading module sfc ... [  OK  ]
:: Loading module e1000 ... [  OK  ]
:: Loading module pcnet32 ... [  OK  ]
:: Loading module vmxnet3 ... [  OK  ]
:: Loading module bnx2 ... [  OK  ]
:: Loading module bnx2x ... [  OK  ]
:: 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  ]
:: 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:1 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:60 (60.0 B)  TX bytes:890 (890.0 B)

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
(55): Synology/synology_bromolow_3615xs/6.1-15047/192.168.0.3
(44): http://192.168.0.3:5000/description-eth0.xml
Connected.
done.
/usr/syno/bin/reg_ssdp_service 192.168.0.3 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 ============
Tue Mar 10 18:25:44 UTC 2020
==============================
starting pid 5836, tty '': '/sbin/getty 115200 console'
Tue Mar 10 18:25:45 2020

DiskStation login:

 

Then I accessed http://192.168.0.3:5000/web_index.html, did the install, and after the reboot, that's the output:

 

BdsDxe: failed to load Boot0002 "UEFI QEMU HARDDISK QM00005 " from PciRoot(0x0)/Pci(0
x7,0x0)/Sata(0x0,0xFFFF,0x0): Not Found

>>Start PXE over IPv4.

So it seems that the VM is not finding the boot disk (or the bootloader wasn't installed correctly):

 

after_install.thumb.png.c15dbdb9035605d2aed29ef54268e936.png

 

Any help is welcome.


Thanks.

Regards.

 

 

Edited by Zamana
Link to post
Share on other sites

Sorry for being late, but I spend lot of time today writing it all into one simple instruction and translating it to make it understadable. This is my own tutorial (that worked during several attempts) just for my home use. I am not IT specialist so it is written in a way that I ( and I hope other people) will understand easily. If I made or wrote something wrong please correct me.  Ps.  Sorry for my bad english and uppercase letters but in my descriptions I always use them and I don't have more strength today to rewrite it anymore. If You do it the way like it is on the list depends also of your hardware it should work. REMEMBER- YOU DO IT ON YOUR OWN RESPONSIBILITY.

 

Some extra stuff that are needed for this: Xpenology tool, Filezilla, img2kvm, ( +extra:  notepad++, osfmount, Synology mod new). It goes like this:

 

 

1. DOWNLOAD XPENOLOGY TOOL. START IT, CHOOSE DOWNLOADS  AND DOWNLOAD:

A) LOADER 1.03B FOR DS3617XS

B) DSM 6.2 FOR DS3617XS (PAT FILE)

 

2. IF YOU WANT YOU CAN MODIFY THE SERIAL NUMBER AND MAC OF NETWORK CARD, OR JUST SKIP IT AND GO DIRECTLY TO POINT 10

3. INSTALL  PASSMARK OSF MOUNT AND NOTEPAD ++  ON YOUR COMPUTER

4. OPEN DOWNLOADED ISO BY PASSMARK, SELECT 1 PARTITION (15 MB), DESELECT  "READ ONLY" SO YOU CAN CHANGE IT AND AFTER THAT ACCEPT ALL

5. A NEW MOUNTED DRIVE WILL APPEAR IN THE WINDOWS EXPLORER, OPEN IT

6. ENTER THE FOLDER  GRUB/GRUBCFG  AND CLICK EDIT WITH NOTEPAD ++

7. NOW OPEN SYNOLOGY MOD NEW.XLSM  EXCEL FILE, CHOOSE YOUR MODEL (3615 AND 3617 ARE THE SAME) 

8. COPY THE GENERATED SERIAL AND PASTE IT IN SOME NEW TEXT DOCUMENT ON DESKTOP OR SOMEWHERE. CLICK ON SYNOLOGY MAC (ON THE BOTTOM OF EXCEL SHEED-   NEXT TO SYNOLOGY SERIAL) AND COPY GENERATED MAC ADRESS,  ALSO PASTE IT INTO TEXT DOCUMENT   
   EXAMPLE:  SYNOLOGY SERIAL: A1BBB11111   MAC: 00-11-22-2A-11-2A   
   NOW REMOVE THE    -    FROM MAC SO YOU WILL GET ONE LONG NUMBER     0011222A112A
9.  IN EDITED GRUB.CFG FIND THE LINE AND SWAP YOUR NUMBER INSTEAD OF ORIGINAL SO IT WILL LOOK LIKE :

 sn = A1BBB11111 
 mac1 = 0011222A112A 

 SAVE FILE, CLOSE FILE, DISASSEMBLY DISK (DISKMOUNT AND EXIT)

 

10. INSTALL FILEZILLA AND LOG IN TO PROXMOX F.EX:

    SERVER: sftp://192.168.1.100          USER NAME: root            PASSWORD: yourproxmoxpassword         PORT: LEAVE BLANK


11. PASTE YOUR CHANGED ( OR ORIGINAL) synoboot FILE TOGETHER WITH THE img2kvm FILE INSIDE PROXMOX TO THE FOLDER / root /    
    (INSIDE ROOT FOLDER WHERE YOU HAVE   gnupg, ssh, bash history, bashrc, forward, profile, rnd)


12. CREATE NEW VIRTUAL MACHINE IN PROXMOX ( I AM GOING TO PUT IT ON MY ZFS STORAGE POOL CALLED "VIRTUALCENTER" WITH VIRTUAL MACHINE NUMBER 100) SO:

 

GENERAL: 
                NODE:PROXMOX
                VM ID:100

OS:
                DO NOT USE ANY MEDIA
                OS: LINUX 5.X-2.6 KERNEL

SYSTEM: 
                ALL DEFAULT

HARD DISK:

                BUS/DEVICE: SATA 0
                STORAGE/SIZE: YOUR CHOICE (MY- VIRTUALCENTER)

CPU:
                YOUR CHOICE

MEMORY:  
                YOUR CHOICE

NETWORK:
                INTEL E1000

 

13. MACHINE READY / DO NOT TURN IT ON. BOOT FILE IS ALREADY IN THE FOLDER / root / READY TO CONFORM, SO WE CONTINUE...


14. ENTER PROXMOX SHELL AND COPY/PASTE THE COMMAND:


chmod + x img2kvm


THEN PASTE NEXT COMMAND ( REMEMBER - NUMBER "100" IS OUR VIRTUAL MACHINE  AND  "VIRTUALCENTER" IS A PLACE WHERE 50MB BOOT FILE WILL BE CREATED. IT IS JUST AN EXAMPLE SO IF YOUR VM ID NUMBER AND PLACE WHERE YOU WANT TO HAVE YOUR VM IS DIFERENT THAN CHANGE THEM TO YOURS. REMEMBER THAT IT  MUST OPERATE THE WM IMAGE FUNCTION AND IF NOT JUST ADD THIS IN OPTIONS IN PROXMOX/DATACENTER/STORAGE/EDIT/CONTENT-DISK IMAGE)


COMMAND: 


./img2kvm synoboot.img 100 vm-100-disk-1 VIRTUALCENTER

 

15. NEW DISK WILL APPEAR WITH THE NAME "UNUSED DISK 0 VIRTUALCENTER-vm-100-disk-1" IN YOUR VIRTUAL MACHINE HARDWARE


16. WHEN YOU CLICK EDIT YOU WILL SEE SOMETHING LIKE   BUS/DEVICE SATA 1  DISK IMAGE/VIRTUALCENTER: vm-100-disk-1    CLICK: ADD (REMEMBER ADD/NOT CLOSE WINDOW)
     AFTER ADDING THE DISK, INSTEAD OF "UNUSED"  IT WILL CHANGE INTO  SATA 1 DISK)


17. ENTER THE OPTIONS/ BOOT ORDER AND CHANGE THE STARTUP DEVICE 1 TO   SATA 1 DRIVE   AND

      IF YOU WANT YOU CAN CHOOSE BOOT AT STARTUP (YOUR CHOICE)


18. START YOUR VIRTUAL MACHINE


19. OPEN YOUR WEB BROWSER AND TYPE    find.synology.com  

     SEARCH FOR YOUR SYNOLOGY MACHINE AND WAIT COUPLE SECONDS


                                             ..... TADAAA ...

 

IF YOU DONE EVERYTHING RIGHT YOU GOT YOUR VIRTUAL XPENOLOGY ( READY TO INSTALL DSM6). REMEMBER YOUR XPENOLOGY  IP NUMBER (YOU CAN CHANGE IT LATER IN  DSM OPTIONS TO STATIC IP)


20. CLICK  AND INSTALL DOWNLOADED DSM_DS3617xs_23739.pat / ERASE THE DATA ON DRIVE AND CONTINUE THE INSTALLATION UNTIL XPENOLOGY WILL RESTART SO YOU CAN  CONFIGURE USER NAME, PASSWORD, ETC. ON THE END YOU CAN ALSO ADD ANOTHER VIRTUAL DISK FOR SHARED FOLDERS .SPK FILES  AND OTHER STUFF IN YOUR VM/HARDWARE/ADD HARD DISK.


DONE.
 

Edited by ruffpl
Link to post
Share on other sites

Hello ruffpl!

 

No need to apologies. I thought that your tutorial was already written...

 

I guess I'm getting closer. I followed your tutorial. After boot for the first time, I can see through the serial console (thanks x1fr!) that I have two interfaces:  lo (the default loopback) and eth0 (the first ethernet interface). This allows me to access the DSM web UI and made the installation.

 

The installation seems to go well, but after the reboot, I'm left with the default lo and another interface named "sit0", that has no MAC address and therefore has no IP address...

 

1593854903_ScreenShot2020-03-10at23_04_41.thumb.png.5944b792163b26b4ddf472149df9b3e0.png

 

What could be wrong now?

 

Link to post
Share on other sites
5 hours ago, Zamana said:

Hello ruffpl!

 

No need to apologies. I thought that your tutorial was already written...

 

I guess I'm getting closer. I followed your tutorial. After boot for the first time, I can see through the serial console (thanks x1fr!) that I have two interfaces:  lo (the default loopback) and eth0 (the first ethernet interface). This allows me to access the DSM web UI and made the installation.

 

The installation seems to go well, but after the reboot, I'm left with the default lo and another interface named "sit0", that has no MAC address and therefore has no IP address...

 

1593854903_ScreenShot2020-03-10at23_04_41.thumb.png.5944b792163b26b4ddf472149df9b3e0.png

 

What could be wrong now?

 

 

With DMS 6.2.2 ? My guess is your vm is using a e1000 nic and you did not modified your bootloader with extra.lzma drivers. You need to to that or enable e1000e driver in proxmox, see there :

(It would be even better with virtio nic, but I can't get the driver to work)

Edited by x1fr
Link to post
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.