HaWk

- Результат: Успешно встало, VMM не работает - Версия и модель загрузчика: JUN'S LOADER v1.02b - DS3615xs - Версия DSM: DSM 6.1.7-DSM_15284 - Аппаратное решение: HPE Microserv Gen10 AMD Opteron(tm) X3421 APU - Завелось без проблем, VMM не работает. Все такцы с бубном и добавление extra.izma не помогло - Результат: Успешно встало, VMM не работает - Версия и модель загрузчика: JUN'S LOADER v1.02b - DS3615xs - Версия DSM: DSM 6.1.7-DSM_15284 Update 2 - Аппаратное решение: HPE Microserv Gen10 AMD Opteron(tm) X3421 APU - Завелось без проблем, VMM не работает. Все такцы с бубном и добавление extra.izma не помогло - Результат: Не завелось - Версия и модель загрузчика: JUN'S LOADER v1.02b - DS3615xs - Версия DSM: DSM 6.2.1-DSM_23824 - Аппаратное решение: HPE Microserv Gen10 AMD Opteron(tm) X3421 APU - Не грузится и не находит сеть - Результат: Успешно встало, VMM не работает - Версия и модель загрузчика: JUN'S LOADER v1.04b - DS918+ - Версия DSM: DSM 6.2.1-DSM_23824 - Аппаратное решение: HPE Microserv Gen10 AMD Opteron(tm) X3421 APU - Завелось без проблем, VMM не работает. Все такцы с бубном и добавление extra.izma не помогло - Результат: Успешно встало, VMM не работает - Версия и модель загрузчика: JUN'S LOADER v1.04b - DS918+ - Версия DSM: DSM 6.2.1-DSM_23824 Update 2 - Аппаратное решение: HPE Microserv Gen10 AMD Opteron(tm) X3421 APU - Завелось без проблем, VMM не работает. Все такцы с бубном и добавление extra.izma не помогло Предположительная проблема в отсутствии поддержки процессора AMD

Dear friends, please help win Microserver Gen10 support for AMD Opteron X3421 APU. Tried: 1.02b with 6.1.7 and 6.2 starts but VMM do not load virtual machines. Tried to add Extra.Izma 4.8 to 6.1.7 - didnt help. 1.04b with 6.2.1 and 6.2.1 Updated 2 starts but VMM do not load virtual machines. Fixed errors about "TUN" in log when staring VM by: mkdir /dev/net mknod /dev/net/tun c 10 200 chmod 600 /dev/net/tun ls -l /dev/net cat /dev/net/tun insmod /lib/modules/tun.ko but this doesn't help. 2018-12-28T14:17:31+03:00 FS synoscgi_SYNO.Virtualization.Guest_1_list_SYNO.Virtualization.Guest_1_usb_list[19845]: ccc/sender.cpp:454 Failed to list host linearized from dashboard 2018-12-28T14:17:33+03:00 FS synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[20021]: ccc/guest.cpp:2403 Want Resource / Pre-allocated resource for [ca6426c7-0276-4ce0-a28c-67553329d0e9], mem: 1426063360 / 0, vcpu: 1 / 0, cpu pin: 0 / 0, cpu weight: 256 / 0 2018-12-28T14:17:33+03:00 FS synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[20021]: MemSize: ccc/reservation.cpp:900 Start to op(3), ca6426c7-0276-4ce0-a28c-67553329d0e9: [{}] -> [{"vram_size":1426063360}] 2018-12-28T14:17:33+03:00 FS synoccc_guestd[32381]: ccc/reservation.cpp:137 locked /dev/virtualization/libvirt/qemu/syno.qemu_back_mem.ca6426c7-0276-4ce0-a28c-67553329d0e9 size: 1426063360 2018-12-28T14:17:33+03:00 FS synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[20021]: CpuCore: ccc/reservation.cpp:900 Start to op(3), ca6426c7-0276-4ce0-a28c-67553329d0e9: [{}] -> [{"cpu_pin_num":0,"cpu_weight":256,"vcpu_num":1}] 2018-12-28T14:17:33+03:00 FS synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[20021]: CpuCore: ccc/reservation.cpp:1181 CPU cores utilization, total: 2 * 4, sum of vcpu used: 1, sum of cpu pin reserved: 0, want vcpu: 1, want cpu reser ved: 0 2018-12-28T14:17:34+03:00 FS kernel: [ 1537.502443] got iSCSI disk[0] 2018-12-28T14:17:35+03:00 FS kernel: [ 1538.203588] got iSCSI disk[0] 2018-12-28T14:17:35+03:00 FS synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[20021]: ccc/guest.cpp:1208 connection open failed 2018-12-28T14:17:35+03:00 FS synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[20021]: ccc/guest.cpp:2623 Failed to start guest [ca6426c7-0276-4ce0-a28c-67553329d0e9] 2018-12-28T14:17:35+03:00 FS synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[20021]: ccc/guest.cpp:199 Disks stopped in 0.201000 sec 2018-12-28T14:17:35+03:00 FS synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[20021]: ccc/vnic.cpp:1351 Destroy vnic (tap tap0211322d268e) by DetachStateDel 2018-12-28T03:17:35+03:00 FS synonetd: net_if_is_bonding_slave.c:46 Cannot get flags of network interface: No such device 2018-12-28T14:17:35+03:00 FS synoccc_guestd[32381]: ccc/reservation.cpp:105 un-locked /dev/virtualization/libvirt/qemu/syno.qemu_back_mem.ca6426c7-0276-4ce0-a28c-67553329d0e9 2018-12-28T14:17:35+03:00 FS synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[20021]: CpuCore: ccc/reservation.cpp:1181 CPU cores utilization, total: 2 * 4, sum of vcpu used: 0, sum of cpu pin reserved: 0, want vcpu: -1, want cpu rese rved: 0 2018-12-28T14:17:35+03:00 FS synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[20021]: Guest/guest.cpp:4955 Failed creating guest [ca6426c7-0276-4ce0-a28c-67553329d0e9] reason [-6] 2018-12-28T14:17:35+03:00 FS synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[20021]: guest_action.cpp:207 Bad response [{"error":{"code":908},"httpd_restart":false,"success":false}]/ request [{"api":"SYNO.CCC.Guest","guest_id":"ca642 6c7-0276-4ce0-a28c-67553329d0e9","method":"poweron","version":1}] 2018-12-28T14:19:35+03:00 FS synoscgi_SYNO.Virtualization.Guest_1_get[22553]: servicecfg_validate.c:123 [/usr/syno/etc/synoservice.d/pkgctl-Virtualization.cfg] is not a json format file. 2018-12-28T14:19:35+03:00 FS synoscgi_SYNO.Virtualization.Guest_1_get[22553]: servicecfg_root_object_get.c:137 Failed to validate service file [/usr/syno/etc/synoservice.d/pkgctl-Virtualization.cfg] 2018-12-28T14:19:35+03:00 FS synoscgi_SYNO.Virtualization.Guest_1_get[22553]: servicecfg_validate.c:123 [/usr/syno/etc/synoservice.d/pkgctl-Virtualization.cfg] is not a json format file. 2018-12-28T14:19:35+03:00 FS synoscgi_SYNO.Virtualization.Guest_1_get[22553]: servicecfg_root_object_get.c:137 Failed to validate service file [/usr/syno/etc/synoservice.d/pkgctl-Virtualization.cfg] 2018-12-28T14:19:35+03:00 FS synoscgi_SYNO.Virtualization.Guest_1_get[22553]: pkgtool.cpp:2959 Failed to get status of pkgctl-Virtualization [0x4000 servicecfg_validate.c:124] 2018-12-28T14:19:35+03:00 FS synoscgi_SYNO.Virtualization.Guest_1_get[22553]: ccc/service.cpp:1035 etcd state changed to preparing 2018-12-28T14:20:00+03:00 FS synoscgi_SYNO.Virtualization.Host_1_list[22741]: ccc/service.cpp:1014 etcd recoverd from preparing: Fri Dec 28 14:19:44 2018 - 16 seconds

Gen 10 x3421 - 8Gb, AMD SVM in BIOS is on. installed bootloader 1.04 918+ 6.2.1 Updated 2, work fine but VMM do not work. installed bootloader 1.02b 3615xs on 6.1.7 and 6.2 (6.2.1 fails), work fine but VMM do not work. 2 NIC connected fine. VirSwitch is on. 1. Error starting VM: Failed to power on the virtual machine on the host due to insufficient RAM on the host 2. find / -name kvm* gives that No kvm-amd.ko in the system. 3. Errors Is logs: Failed to open /dev/net/tun Failed to create tap device Failed to start NI Can someone HELP to fix kernel for AMD support please? in /var/log/messages: 2018-12-28T11:52:29+03:00 FS synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[7623]: MemSize: ccc/reservation.cpp:900 Start to op(3), fd16a28d-a5f7-446f-b14a-ab188407a85e: [{}] -> [{"vram_size":1426063360}] 2018-12-28T11:52:29+03:00 FS synoccc_guestd[18266]: ccc/reservation.cpp:137 locked /dev/virtualization/libvirt/qemu/syno.qemu_back_mem.fd16a28d-a5f7-446f-b14a-ab188407a85e size: 1426063360 2018-12-28T11:52:29+03:00 FS synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[7623]: CpuCore: ccc/reservation.cpp:900 Start to op(3), fd16a28d-a5f7-446f-b14a-ab188407a85e: [{}] -> [{"cpu_pin_num":0,"cpu_weight":256,"vcpu_num":1}] 2018-12-28T11:52:29+03:00 FS synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[7623]: CpuCore: ccc/reservation.cpp:1181 CPU cores utilization, total: 2 * 4, sum of vcpu used: 1, sum of cpu pin reserved: 0, want vcpu: 1, want cpu reserv ed: 0 2018-12-28T11:52:29+03:00 FS synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[7623]: ccc/vnic.cpp:581 Failed to open /dev/net/tun 2018-12-28T11:52:29+03:00 FS synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[7623]: ccc/vnic.cpp:1190 Failed to create tap device 2018-12-28T11:52:29+03:00 FS synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[7623]: ccc/guest.cpp:70 Failed to start NIC [230572df-a2c3-4e51-a251-89ea0adea490] 2018-12-28T11:52:29+03:00 FS synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[7623]: ccc/guest.cpp:2078 Failed to start nic 2018-12-28T11:52:30+03:00 FS synoccc_guestd[18266]: ccc/reservation.cpp:105 un-locked /dev/virtualization/libvirt/qemu/syno.qemu_back_mem.fd16a28d-a5f7-446f-b14a-ab188407a85e 2018-12-28T11:52:30+03:00 FS synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[7623]: CpuCore: ccc/reservation.cpp:1181 CPU cores utilization, total: 2 * 4, sum of vcpu used: 0, sum of cpu pin reserved: 0, want vcpu: -1, want cpu reser ved: 0 2018-12-28T11:52:30+03:00 FS synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[7623]: ccc/guest.cpp:2573 Failed to prepare for guest [fd16a28d-a5f7-446f-b14a-ab188407a85e] 2018-12-28T11:52:33+03:00 FS synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[7623]: Guest/guest.cpp:4955 Failed creating guest [fd16a28d-a5f7-446f-b14a-ab188407a85e] reason [-4] 2018-12-28T11:52:33+03:00 FS synoscgi_SYNO.Virtualization.Guest.Action_1_pwr_ctl[7623]: guest_action.cpp:207 Bad response [{"error":{"code":903},"httpd_restart":false,"success":false}]/ request [{"api":"SYNO.CCC.Guest","guest_id":"fd16a2 8d-a5f7-446f-b14a-ab188407a85e","method":"poweron","version":1}] r