Evgenii
-
Posts
5 -
Joined
-
Last visited
Posts posted by Evgenii
-
-
Can use my configuration!
Work configuration:
MAC: AA:A8:62:84:F9:86 must be assign to network interface.
Change path: file=/mnt/StorageVM/Images/images/118/synoboot.img
root@vm-proxmox:/tmp/synology# cat /etc/pve/nodes/vm-proxmox/qemu-server/118.conf
args: -device 'ich9-usb-ehci1,id=usb-ctl-synoboot,addr=0x18' -drive 'id=usb-drv-synoboot,file=/mnt/StorageVM/Images/images/118/synoboot.img,if=none,format=raw' -device 'usb-storage,id=usb-stor-synoboot,bootindex=1,removable=off,drive=usb-drv-synoboot' bootdisk: sata0 cores: 4 memory: 4096 name: xynology.dev net0: vmxnet3=AA:A8:62:84:F9:86,bridge=vmbr0,tag=100 numa: 0 ostype: l26 serial0: socket smbios1: uuid=190c7a46-fac8-4036-99f6-a333a74f31b6 sockets: 1 vmgenid: 1ef70d37-0e17-4d65-9cbb-71c9e1238f39Synoboot loader 1.03b:
https://nextcloud.almatey.kiev.ua/nextcloud/index.php/s/yweqp9Q3JLBpgtL
DiskStation DSM 6.2-23739 & DSM_DS3615xs_2373
After start the xynology server, you must run 'qm term ID' on the
Proxmox server and too look in the dhcp log file, maybe after start server, IP was received
---- log after apply ---
: Loading module mpt3sas ... [ OK ] Insert net driver(Mindspeed only)... Starting /usr/syno/bin/synocfgen... /usr/syno/bin/synocfgen returns 0 All disk ready or timeout execeed Exit on error [1] DISK NOT INSTALLED... Mon May 25 07:59:05 UTC 2020 none /sys/kernel/debug debugfs rw,relatime 0 0 sys /sys sysfs rw,relatime 0 0 none /dev devtmpfs rw,relatime,size=2013368k,nr_inodes=503342,mode=755 0 0 proc /proc proc rw,relatime 0 0 linuxrc.syno failed on 1 starting pid 3892, tty '': '/etc/rc' :: Starting /etc/rc :: Mounting procfs ... [ OK ] :: Mounting tmpfs ... [ OK ] :: Mounting devtmpfs ... [ OK ] :: Mounting devpts ... [ OK ] :: Mounting sysfs ... [ OK ] udhcpc (v1.16.1) started eth0 Link encap:Ethernet HWaddr AA:A8:62:84:F9:86 inet addr:10.200.0.2 Bcast:10.200.255.255 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6 errors:0 dropped:0 overruns:0 frame:0 TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:985 (985.0 B) TX bytes:1620 (1.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: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-aaa86284f986::upnp:rootdevice (55): Synology/synology_broadwell_3617xs/6.2-23739/10.200.0.2 (43): http://10.200.0.2:5000/description-eth0.xml Connected. done. /usr/syno/bin/reg_ssdp_service 10.200.0.2 aaa86284f986 6.2-23739 synology_broadwell_3617xs 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 ============ Mon May 25 08:01:34 UTC 2020 ============================== starting pid 5867, tty '': '/sbin/getty 115200 console' Mon May 25 08:01:35 2020 DiskStation login: -
And yes! I can successfully install virtio* modules and create an eth0 device with these modules, but after running ifconfig eth0 or eth0 up, I get a kernel panic
I think it depends on the original Synology modules that are already loaded, and virtio* modules will not work while the modules from Synology are loaded.
-
Hello @speedyrazor
Yes!
1. You must use two interfaces if you are doing a test:
1. E1000 (no change)
2. vmxnet3 (for test)3. You should use -> 'Serial Port (serial0) socket' in the xynology server configuration on proxmox
4. You can connect to the terminal using the command -> 'qm terminal ID (your machine ID)' after turning on the server.
----
I am using:
Loadrer 1.03b
DiskStation DSM 6.2-23739 & DSM_DS3615xs_2373I can test your configuration.
What do you use ? -
You can use VMware -> vmxnet3 network driver - the paravirtualization driver instead of the virtio_net driver for change e1000 network emulation driver.
Basic configuration with vmxnet3 driver and full support for 10Gb network speed.
args: -device 'ich9-usb-ehci1,id=usb-ctl-synoboot,addr=0x18' -drive 'id=usb-drv-synoboot,file=/mnt/StorageVM/Images/images/103/synoboot.img,if=none,format=raw' -device 'usb-storage,id=usb-stor-synoboot,bootindex=1,removable=off,drive=usb-drv-synoboot' balloon: 0 boot: c bootdisk: sata0 cores: 4 bostpci0: 04:00 memory: 4096 name: xynology.ds.network net0: vmxnet3=00:11:32:03:FC:31,bridge=vmbr0,tag=255 net1: vmxnet3=D6:0A:3C:58:34:FF,bridge=vmbr0,tag=255 net2: e1000=52:BF:F9:11:69:0C,bridge=vmbr0,tag=100 numa: 0 onboot: 1 ostype: l26 scsihw: megasas serial0: socket smbios1: uuid=5251abfb-8118-4dd6-9dea-586dde8b4ebf sockets: 1 startup: order=0,up=1,down=180 vmgenid: 7f3ddc78-6314-45c1-86b0-90cb9bf9c63eExample:
root@xynology:~# /tmp/iperf -c 192.168.253.1
------------------------------------------------------------ Client connecting to 192.168.253.1, TCP port 5001 TCP window size: 22.5 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.253.254 port 33321 connected with 192.168.253.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 6.60 GBytes 5.67 Gbits/sec
KVM - Virtio Network - Driver extension
in DSM 6.x
Posted
Is it libvirt & virt-manager, etc.? I think you should look towards Proxmox as a replacement for KVM
I used it too before. But, as I met Proxmox, I forgot about KVM. Proxmox also uses KVM, but management is simpler.
Proxmox have a support LXC containers too.
Good luck in finding a solution although it is under your nose!