marian

I did recompile whole kernel including modules from the latest sources that were on the sourceforge. I used .config file that came with the source. Change just the few bits in menuconfig to enable virtio drivers and attach "+" at the end of the version so it matches with the one running on the xpenology box. Got it loaded onto the box and virtio_net injects but it doesn't create the interface. Guess i must be doing something wrong. Nothing useful in kernel logs, it's like nothing happened on modprobe. Didn't have the time to investigate further. Also if the kernel in the sourceforge is not exactly same version it may not work correctly and hence the issues. Does synology release source as per the GPL or they violate it by keeping it too long?

I can build the drivers and package them. However the virtio drivers I built don't seem to work. The network interface does not come up after modprobing the driver. virtio_blk throws up some errors. I would like to either check my process against some one else's or get access to the workflow i.e. scripts to build them using proven steps. I followed the guide it makes sense but I must be making mistake somewhere. I imagine you guys must have been building extra.lzma files for some time now, you probably have some helper scripts right? BTW: 6.2 is based on the latest kernel that on sourceforge.

Can you please publish the scripts for your workflow that produces extra.lzma files @IG-88? I wanted to build virtio drivers for 1.04b loader the other day by hand and I didn't get the result i wanted. I would like to compare the process. Thanks.

Can somebody please tell me how to make virtio working with Jun Loader 1.04b? I compiled virtio modules from Synology sources for ApolloLake (DS 918+): https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/22259branch/apollolake-source/linux-4.4.x.txz/download Placed them in /lib/modules inside rd.gz Edited /etc/rc inside rd.gz to load virtio_net with dependencies and repackaged rd.gz with cpio and lzma I then ran vm inside Bhyve (FreeBSD 11.2), vm config on the host: uefi="yes" cpu=2 memory=1G network0_type="virtio-net" network0_device="tap1" disk0_type="ahci-hd" disk0_name="synoboot-1.04b-virtio-jun.img" grub_run_dir="/grub" network0_mac="58:9c:fc:0b:e8:aa" uuid="b75f312f-e2d8-11e8-9f90-90e2ba471364" They do insert correctly on the guest (it seems): DiskStation> lsmod | grep virtio virtio_net 20035 0 virtio_ring 6787 1 virtio_net virtio 5273 1 virtio_net but the eth0 interface does not come up, i get lo only DiskStation> ifconfig 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:1 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) tap1 host interface seems to have no problem bringing up eth0 on the guest with e1000 driver. Here is the modified loader: https://mega.nz/#!nGYXCQDC!heCIsfbHpFP1FBnKSO2uJtMHDygMLoFqJa7_67Lrrqs Root password: jun Hope somebody gives me a hand, I would like to make virtio_net working as a priority - looking at virtio_blk for the disk next (already in the updated loader).