ElCoyote_

Is it possible to update DSM from within DSM (like you'd do on a regular Synology)? my virtual DSM KVM guest: 1) reports an error when going to DSM->Controle Panel->Update & restore: "Connection failed. Please check your internet connection" 2) no longer boots if I try to apply the DSM .pat file manually ("Manual DSM update").

Interestingly, I found a workaround for e1000e: - Let the KVM DSM guest boot and login on the serial port. - On the virtual serial port, login as 'root' - when logged in, type 'rmmod e1000e' (this unloads the driver) - then type insmod /lib/modules/e1000e.ko -then- things started working and I could ping my virtual NAS. I was then able to find the NAS in the Synology assistant and install it. Upon bootup, I was greeted by the same kind of e1000e messages: [ 108.413268] e1000e 0000:01:00.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 108.416259] e1000e 0000:01:00.0 eth0: NIC Link is Down [ 117.923412] e1000e 0000:01:00.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 117.926688] e1000e 0000:01:00.0 eth0: NIC Link is Down [ 119.126404] e1000e 0000:01:00.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 119.129814] e1000e 0000:01:00.0 eth0: NIC Link is Down [ 120.003781] e1000e 0000:01:00.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 120.007264] e1000e 0000:01:00.0 eth0: NIC Link is Down Again, I did the module unload/reload, had to configure the IP manually and things started working: root@SynologyNAS:~# rmmod e1000e [ 160.173250] Module [e1000e] is removed. [ 160.238040] e1000e 0000:01:00.0 eth0: NIC Link is Down root@SynologyNAS:~# insmod /lib/modules/e1000e.ko [ 173.549954] e1000e: Intel(R) PRO/1000 Network Driver - 3.4.2.4-NAPI [ 173.551544] e1000e: Copyright(c) 1999 - 2019 Intel Corporation. [ 173.555129] e1000e 0000:01:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 173.601491] e1000e 0000:01:00.0 0000:01:00.0 (uninitialized): registered PHC clock [ 173.657412] e1000e 0000:01:00.0 eth0: (PCI Express:2.5GT/s:Width x1) 52:54:00:8c:0b:bd [ 173.658556] e1000e 0000:01:00.0 eth0: Intel(R) PRO/1000 Network Connection [ 173.659545] e1000e 0000:01:00.0 eth0: MAC: 3, PHY: 8, PBA No: 000000-000 root@SynologyNAS:~# ifconfig eth0 10.0.128.227 netmask 255.255.252.0 up [ 292.929087] e1000e 0000:01:00.0 eth0: MSI interrupt test failed, using legacy interrupt. [ 292.932374] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 292.933235] 8021q: adding VLAN 0 to HW filter on device eth0 root@SynologyNAS:~# [ 293.312637] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 293.318196] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready It really seems as if the e1000e driver does not work the first time it is loaded this is what the virtual e1000e Ethernet H/w shows up like: root@SynologyNAS:~# lspci -v -s 0000:01:00.0 0000:01:00.0 Class 0200: Device 8086:10d3 Subsystem: Device 8086:0000 Flags: bus master, fast devsel, latency 0, IRQ 22 Memory at fca40000 (32-bit, non-prefetchable) [size=128K] Memory at fca60000 (32-bit, non-prefetchable) [size=128K] I/O ports at d000 [size=32] Memory at fca80000 (32-bit, non-prefetchable) [size=16K] Expansion ROM at fca00000 [disabled] [size=256K] Capabilities: [c8] Power Management version 2 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [e0] Express Endpoint, MSI 00 Capabilities: [a0] MSI-X: Enable- Count=5 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number 52-54-00-ff-ff-8c-0b-bd Kernel driver in use: e1000e It also affects the VM itself each time it boots so I just created a task on bootup that does the following: (DSM -> Task scheduler -> Triggered task -> Bootup -> user-defined script (run as roo) /sbin/rmmod e1000e /sbin/insmod /lib/modules/e1000e.ko /bin/systemctl restart synoovs-vswitch.service /sbin/ifconfig eth0 up /sbin/ifconfig eth1 up /sbin/ifconfig ovs_bond0 up

Hi, I'm trying to install DSM 7.1 on KVM (RHEL8) by using the following guide: All of the steps complete successfully but after step8 (exitcheck.sh reboot) I don't get a working network card for my guest (tried virtio and e1000e) If I use 'e1000e' as the H/W type for the NIC, the serial console shows this on bootup: Quote Mon Jan 2 22:29:25 2023 SynologyNAS login: [ 49.725380] e1000e 0000:01:00.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 49.727706] e1000e 0000:01:00.0 eth0: NIC Link is Down [ 66.301763] e1000e 0000:01:00.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 66.303984] e1000e 0000:01:00.0 eth0: NIC Link is Down [ 71.602002] e1000e 0000:01:00.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 71.614607] e1000e 0000:01:00.0 eth0: NIC Link is Down [ 74.747194] e1000e 0000:01:00.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 74.749222] e1000e 0000:01:00.0 eth0: NIC Link is Down [ 79.934335] e1000e 0000:01:00.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 79.936743] e1000e 0000:01:00.0 eth0: NIC Link is Down [ 80.564343] e1000e 0000:01:00.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx if I try to use virtio for the NIC and add the driver, no NIC is detected and an ls of /lib/modules does not show any virtio NIC driver. ./rploader.sh ext ds3622xsp-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/redpill-load/master/redpill-virtio/rpext-index.json ./rploader.sh build ds3622xsp-7.1.0-42661 SynologyNAS> ls adt7475.ko leds-atmega1608.ko syno_hddmon.ko cdc-acm.ko leds-lp3943.ko synobios.ko dca.ko lockd.ko synofsbd.ko e1000e.ko loop.ko synorbd.ko ehci-hcd.ko mpt3sas.ko udp_tunnel.ko ehci-pci.ko mv14xx.ko usb-common.ko fat.ko nfs.ko usb-storage.ko grace.ko nfsv3.ko usbcore.ko hid.ko pgdrv.ko usbhid.ko i2c-algo-bit.ko phy_alloc_0810_x64.ko vfat.ko i40e.ko r8168.ko vxlan.ko igb.ko sg.ko xhci-hcd.ko ip6_udp_tunnel.ko sha256_generic.ko xhci-pci.ko ixgbe.ko sunrpc.ko Expand The steps I am using are as follows: ./rploader.sh update ./rploader.sh fullupgrade ./rploader.sh|grep 3622 ./rploader.sh identifyusb ./rploader.sh serialgen DS3622xs+ ./rploader.sh satamap tce-load -iw nano nano user_config.json ./rploader.sh listmods ds3622xsp-7.1.0-42661 ./rploader.sh ext ds3622xsp-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/redpill-load/master/redpill-virtio/rpext-index.json (ONLY FOR VIRTIO) ./rploader.sh build ds3622xsp-7.1.0-42661 exitcheck.sh reboot Expand Any ideas? I'd like to get DSM 7.1.1 working in a VM so I can test out things without doing it on the real NAS (my only NAS). Thanks for the help, V.

Interestingly, I found a workaround with e1000e: - Let the KVM DSM guest boot and login on the serial port. - On the virtual serial port, login as 'root' - when logged in, type 'rmmod e1000e' (this unloads the driver) - then type insmod /lib/modules/e1000e.ko -then- things started working and I could ping my virtual NAS. I was then able to find the NAS in the Synology assistant and install it. Upon bootup, I was greeted by the same kind of e1000e messages: [ 108.413268] e1000e 0000:01:00.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 108.416259] e1000e 0000:01:00.0 eth0: NIC Link is Down [ 117.923412] e1000e 0000:01:00.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 117.926688] e1000e 0000:01:00.0 eth0: NIC Link is Down [ 119.126404] e1000e 0000:01:00.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 119.129814] e1000e 0000:01:00.0 eth0: NIC Link is Down [ 120.003781] e1000e 0000:01:00.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 120.007264] e1000e 0000:01:00.0 eth0: NIC Link is Down Again, I did the module unload/reload, had to configure the IP manually and things started working: root@SynologyNAS:~# rmmod e1000e [ 160.173250] Module [e1000e] is removed. [ 160.238040] e1000e 0000:01:00.0 eth0: NIC Link is Down root@SynologyNAS:~# insmod /lib/modules/e1000e.ko [ 173.549954] e1000e: Intel(R) PRO/1000 Network Driver - 3.4.2.4-NAPI [ 173.551544] e1000e: Copyright(c) 1999 - 2019 Intel Corporation. [ 173.555129] e1000e 0000:01:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 173.601491] e1000e 0000:01:00.0 0000:01:00.0 (uninitialized): registered PHC clock [ 173.657412] e1000e 0000:01:00.0 eth0: (PCI Express:2.5GT/s:Width x1) 52:54:00:8c:0b:bd [ 173.658556] e1000e 0000:01:00.0 eth0: Intel(R) PRO/1000 Network Connection [ 173.659545] e1000e 0000:01:00.0 eth0: MAC: 3, PHY: 8, PBA No: 000000-000 root@SynologyNAS:~# ifconfig eth0 10.0.128.227 netmask 255.255.252.0 up [ 292.929087] e1000e 0000:01:00.0 eth0: MSI interrupt test failed, using legacy interrupt. [ 292.932374] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 292.933235] 8021q: adding VLAN 0 to HW filter on device eth0 root@SynologyNAS:~# [ 293.312637] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 293.318196] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready It really seems as if the e1000e driver does not work the first time it is loaded this is what the virtual e1000e Ethernet H/w shows up like: root@SynologyNAS:~# lspci -v -s 0000:01:00.0 0000:01:00.0 Class 0200: Device 8086:10d3 Subsystem: Device 8086:0000 Flags: bus master, fast devsel, latency 0, IRQ 22 Memory at fca40000 (32-bit, non-prefetchable) [size=128K] Memory at fca60000 (32-bit, non-prefetchable) [size=128K] I/O ports at d000 [size=32] Memory at fca80000 (32-bit, non-prefetchable) [size=16K] Expansion ROM at fca00000 [disabled] [size=256K] Capabilities: [c8] Power Management version 2 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [e0] Express Endpoint, MSI 00 Capabilities: [a0] MSI-X: Enable- Count=5 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number 52-54-00-ff-ff-8c-0b-bd Kernel driver in use: e1000e

Hi, I'm trying to install DSM 7.1 on KVM (RHEL8) by using the following guide: All of the steps complete successfully but after step8 (exitcheck.sh reboot) I don't get a working network card for my guest (tried virtio and e1000e) If I use 'e1000e' as the H/W type for the NIC, the serial console shows this on bootup: if I try to use virtio for the NIC and add the driver, no NIC is detected and an ls of /lib/modules does not show any virtio NIC driver. The steps I am using are as follows: Any ideas? I'd like to get DSM 7.1.1 working in a VM so I can test out things without doing it on the real NAS (my only NAS). Thanks for the help, V.