limetech Posted October 6, 2022 Share Posted October 6, 2022 The 6.11.1 release includes primarily bug fixes but also includes VM Manager improvements by @SimonF. Bugs: If you discover a bug or other issue in this release, please open a Stable Releases Bug Report. ALL USERS are encouraged to upgrade. As always, prior to updating, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Version 6.11.1 2022-10-06 Improvements Updated both qemu and libvirt to latest versions: Added ppc, riscv32/riscv64, and aarch64 support. Updated docker to v20.10.18 and improved networking: When DHCP is used, wait for IPv4 assignment before proceeding on system startup, this avoids a possible race-condition at boot time when host access to custom networks is enabled. Allow user defined networks to be reconnected at docker service start. Now all defined networks will be automatically reconnected. VM Manager improvements: Implemented option to use Virtiofs for mapping of Unraid host shares into a VM. Added Spice html client for Virtual Machines (experimental). Notable Bug fixes Fixed issue where opening certain pages, eg, Dashboard, needlessly causes writes to the USB Flash boot device. Fixed the issue of docker containers can reach the Internet when the WG tunnel is not autostarted at system boot up. Users are advised to regenerate the WG configs. This can be done, e.g., by clicking in a field to change a value and then change it back in order to get the Apply button to light up. Then click Apply. Fixed issue where empty popup windows gets displayed with certain browsers and devices. Restored "NTLMv1 authentication" for incoming SMB connections. Change Log vs. Unraid OS 6.11.0 Base distro: acpid: version 2.0.34 bash: version 5.2.000 bind: version 9.18.7 ca-certificates: version 20220922 dbus: version 1.14.2 dnsmasq: version 2.87 docker: version 20.10.18 (CVE-2022-27664 CVE-2022-32190 CVE-2022-36109) git: version 2.38.0 glib2: version 2.72.4 glibc-zoneinfo: version 2022d gnutls: version 3.7.8 harfbuzz: version 5.2.0 intel-microcode: version 20220809 libXtst: version 1.2.4 libXxf86vm: version 1.1.5 libffi: version 3.4.3 libvirt: version 8.7.0 libvirt-php: version 0.5.6 lsof: version 4.96.3 nghttp2: version 1.50.0 pango: version 1.50.11 qemu: version 7.1.0 (built adding ppc, riscv32/64 support, replace arm with aarch64) sqlite: version 3.39.4 xterm: version 373 xz: version 5.2.7 Linux kernel: version 5.19.14 CONFIG_DRM_MGAG200: Matrox G200 CONFIG_X86_SGX: Software Guard eXtensions (SGX) CONFIG_X86_SGX_KVM: Software Guard eXtensions (SGX) Virtualization CONFIG_CRYPTO_ZSTD: Zstd compression algorithm md/unraid: version 2.9.25 patch: silence EDID "block all zeros" and "has corrupt header" notices patch: add NVMe quirks for non-compliant devices reported by users Management: webgui: VM Manager: Update GUI Options Include 9P and Virtiofs Remove 9P option for Windows. Update XML if virtiofs and Windows in addition to Linux. Update VM Share GUI Options webgui: Fixed: wrong feedback display on VM page webgui: Dashboard: store graph data in file instead of cookie webgui: Ask user to provide diagnostics before downgrading the OS webgui: Spice html client in addition to VNC webgui: improve handling of windows-style config files webgui: WireGuard: add explicit interface name in routing webgui: SWAL: intercept "esc" button to stop nchan upon window closing webgui: nchan: delayed command execution This prevents an empty popup window in certain browsers and devices 17 4 3 Quote Link to comment
KyleS Posted October 7, 2022 Share Posted October 7, 2022 2 hours ago, limetech said: Implemented option to use Virtiofs for mapping of Unraid host shares into a VM. Likely the most impactful change for 6.11. Thanks much. 2 Quote Link to comment
jpowell8672 Posted October 7, 2022 Share Posted October 7, 2022 Upgraded to 6.11.1 from 6.11 with no issues. Thanks, very much appreciated! 1 Quote Link to comment
limetech Posted October 7, 2022 Author Share Posted October 7, 2022 2 hours ago, KyleS said: Likely the most impactful change for 6.11. Thanks much. Thanks to @SimonF! 5 Quote Link to comment
Thorsten Posted October 7, 2022 Share Posted October 7, 2022 Hi, When I want to use the option "Unraid Share Mode Virtiofs Mode" in a Windows VM I get an error message: 2022-10-07 04:53:35.186+0000: 8850: error : qemuValidateDomainDefVhostUserRequireSharedMemory:1816 : unsupported configuration: 'virtiofs' requires shared memory Quote Link to comment
SimonF Posted October 7, 2022 Share Posted October 7, 2022 3 minutes ago, Thorsten said: Hi, When I want to use the option "Unraid Share Mode Virtiofs Mode" in a Windows VM I get an error message: 2022-10-07 04:53:35.186+0000: 8850: error : qemuValidateDomainDefVhostUserRequireSharedMemory:1816 : unsupported configuration: 'virtiofs' requires shared memory You need to still add this manually to the XML, I am looking at making it automatic in the future. <memoryBacking> <source type='memfd'/> <access mode='shared'/> </memoryBacking> 4 1 Quote Link to comment
Thorsten Posted October 7, 2022 Share Posted October 7, 2022 14 minutes ago, SimonF said: You need to still add this manually to the XML, I am looking at making it automatic in the future. <memoryBacking> <source type='memfd'/> <access mode='shared'/> </memoryBacking> Thanks the VM is starting.... My settings are as follows.... I thought since I have a share under Windows that refers to Unraid /mnt/user. Or am I wrong? Quote Link to comment
SimonF Posted October 7, 2022 Share Posted October 7, 2022 3 minutes ago, Thorsten said: Thanks the VM is starting.... My settings are as follows.... I thought since I have a share under Windows that refers to Unraid /mnt/user. Or am I wrong? For windows you need to install additional parts on the guest. https://virtio-fs.gitlab.io/howto-windows.html For a linux guest you just mount the share sudo mount -t virtiofs unraidshare /mnt/unraiddata/ 1 Quote Link to comment
craigr Posted October 7, 2022 Share Posted October 7, 2022 7 hours ago, limetech said: Notable Bug fixes Restored "NTLMv1 authentication" for incoming SMB connections. How on earth did you guys pull this off? Thank you! 1 Quote Link to comment
ezhik Posted October 7, 2022 Share Posted October 7, 2022 18 minutes ago, craigr said: How on earth did you guys pull this off? Thank you! 3 Quote Link to comment
opentoe Posted October 7, 2022 Share Posted October 7, 2022 (edited) I am unable to upgrade for some reason. Oct 7 06:58:46 SUN kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start ff37525a) Oct 7 06:58:46 SUN kernel: FAT-fs (sda1): Filesystem has been set read-only Oct 7 06:58:46 SUN kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 39d1e50e) Oct 7 06:58:46 SUN kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 6c4cd5aa) Oct 7 06:58:46 SUN kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 7930364a) Oct 7 06:58:46 SUN kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 492537, start 317e5461) Oct 7 06:58:46 SUN kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 492537, start 317e5461) Oct 7 06:58:46 SUN kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 492537, start 317e5461) Oct 7 06:58:46 SUN kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 492537, start 317e5461) Oct 7 06:58:46 SUN kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 492537, start 317e5461) Oct 7 06:58:46 SUN kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 492537, start 317e5461) Oct 7 06:59:42 SUN root: plugin: creating: /tmp/unRAIDServer.sh - from INLINE content Oct 7 06:59:42 SUN root: plugin: running: /tmp/unRAIDServer.sh Oct 7 06:59:42 SUN root: plugin: creating: /tmp/unRAIDServer.zip - downloading from URL https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/stable/unRAIDServer-6.11.1-x86_64.zip Oct 7 06:59:47 SUN root: plugin: creating: /tmp/unRAIDServer.md5 - downloading from URL https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/stable/unRAIDServer-6.11.1-x86_64.md5 Oct 7 06:59:48 SUN root: plugin: creating: /tmp/unRAIDServer.sh - from INLINE content Oct 7 06:59:48 SUN root: plugin: running: /tmp/unRAIDServer.sh Oct 7 07:01:08 SUN root: plugin: creating: /tmp/unRAIDServer.sh - from INLINE content Oct 7 07:01:08 SUN root: plugin: running: /tmp/unRAIDServer.sh Oct 7 07:01:08 SUN root: plugin: creating: /tmp/unRAIDServer.zip - downloading from URL https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/stable/unRAIDServer-6.11.1-x86_64.zip Oct 7 07:01:12 SUN root: plugin: creating: /tmp/unRAIDServer.md5 - downloading from URL https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/stable/unRAIDServer-6.11.1-x86_64.md5 Oct 7 07:01:12 SUN root: plugin: creating: /tmp/unRAIDServer.sh - from INLINE content Oct 7 07:01:12 SUN root: plugin: running: /tmp/unRAIDServer.sh Edited October 7, 2022 by opentoe Quote Link to comment
JorgeB Posted October 7, 2022 Share Posted October 7, 2022 14 minutes ago, opentoe said: I am unable to upgrade for some reason. Flash drive problems, try running chkdsk or recreating it, if still issues replace it. Quote Link to comment
opentoe Posted October 7, 2022 Share Posted October 7, 2022 3 minutes ago, JorgeB said: Flash drive problems, try running chkdsk or recreating it, if still issues replace it. Damn, brand new Samsung metal bars too. See what happens. Quote Link to comment
opentoe Posted October 7, 2022 Share Posted October 7, 2022 12 minutes ago, JorgeB said: Flash drive problems, try running chkdsk or recreating it, if still issues replace it. Well, when I looked at my motherboard lights the boot device light was on, so I did a CTRL-ALT-DEL and it started to boot properly and did the upgrade. I had to do the CTRL-ALT-DEL again, so it is probably the flash drive. I'll chkdsk on it later and/or replace it. I have a few new ones somewhere. Thx. Quote Link to comment
bkingsolver Posted October 7, 2022 Share Posted October 7, 2022 One other issue after upgrading to 6.11.1: This affects both my Windows 10 and Windows 11 (both using OVFM TPM). I tried to create a new VM from scratch with OVMF TPM and it failed with the same error on first start. I saved diagnostics, reverted, and things are fine. Should I file a bug report on this? Quote Link to comment
ghost82 Posted October 7, 2022 Share Posted October 7, 2022 (edited) I'm thinking if it is a good idea to use only one kernel and in particular one of the 5.19.x series..I'm seeing lots of kernel panics on users' logs especially related to amd gpus passed through because of the kernel, for example: Oct 7 12:40:42 Tower kernel: amdgpu 0000:0e:00.0: amdgpu: AGP: 267894784M 0x0000008400000000 - 0x0000FFFFFFFFFFFF Oct 7 12:40:42 Tower kernel: [drm] Detected VRAM RAM=8176M, BAR=256M Oct 7 12:40:42 Tower kernel: [drm] RAM width 256bits GDDR6 Oct 7 12:40:42 Tower kernel: [drm] amdgpu: 8176M of VRAM memory ready Oct 7 12:40:42 Tower kernel: [drm] amdgpu: 32122M of GTT memory ready. Oct 7 12:40:42 Tower kernel: [drm] GART: num cpu pages 131072, num gpu pages 131072 Oct 7 12:40:42 Tower kernel: [drm] PCIE GART of 512M enabled (table at 0x00000080001E8000). Oct 7 12:40:42 Tower kernel: amdgpu 0000:0e:00.0: amdgpu: PSP runtime database doesn't exist Oct 7 12:40:42 Tower kernel: amdgpu 0000:0e:00.0: amdgpu: PSP runtime database doesn't exist Oct 7 12:40:42 Tower kernel: [drm] Found VCN firmware Version ENC: 1.17 DEC: 5 VEP: 0 Revision: 2 Oct 7 12:40:42 Tower kernel: amdgpu 0000:0e:00.0: amdgpu: Will use PSP to load VCN firmware Oct 7 12:40:44 Tower kernel: [drm] failed to load ucode SMC(0x2C) Oct 7 12:40:44 Tower kernel: [drm] psp gfx command LOAD_IP_FW(0x6) failed and response status is (0x0) Oct 7 12:40:44 Tower kernel: [drm:psp_load_smu_fw [amdgpu]] *ERROR* PSP load smu failed! Oct 7 12:40:44 Tower kernel: [drm:psp_v11_0_ring_destroy [amdgpu]] *ERROR* Fail to stop psp ring Oct 7 12:40:44 Tower kernel: [drm:psp_hw_init [amdgpu]] *ERROR* PSP firmware loading failed Oct 7 12:40:44 Tower kernel: [drm:amdgpu_device_fw_loading [amdgpu]] *ERROR* hw_init of IP block <psp> failed -22 Oct 7 12:40:44 Tower kernel: amdgpu 0000:0e:00.0: amdgpu: amdgpu_device_ip_init failed Oct 7 12:40:44 Tower kernel: amdgpu 0000:0e:00.0: amdgpu: Fatal error during GPU init Oct 7 12:40:44 Tower kernel: amdgpu 0000:0e:00.0: amdgpu: amdgpu: finishing device. Oct 7 12:40:44 Tower kernel: amdgpu: probe of 0000:0e:00.0 failed with error -22 Oct 7 12:40:44 Tower kernel: BUG: kernel NULL pointer dereference, address: 0000000000000090 Oct 7 12:40:44 Tower kernel: #PF: supervisor write access in kernel mode Oct 7 12:40:44 Tower kernel: #PF: error_code(0x0002) - not-present page Oct 7 12:40:44 Tower kernel: PGD 0 P4D 0 Oct 7 12:40:44 Tower kernel: Oops: 0002 [#1] PREEMPT SMP NOPTI Oct 7 12:40:44 Tower kernel: CPU: 12 PID: 7040 Comm: rpc-libvirtd Tainted: G W 5.19.14-Unraid #1 Oct 7 12:40:44 Tower kernel: Hardware name: Gigabyte Technology Co., Ltd. X570 AORUS PRO/X570 AORUS PRO, BIOS F36d 07/20/2022 Oct 7 12:40:44 Tower kernel: RIP: 0010:drm_sched_fini+0x42/0x90 [gpu_sched] Oct 7 12:40:44 Tower kernel: Code: e8 6c 74 fb e0 48 8d ab 98 00 00 00 4c 8d 63 f8 48 85 ed 74 29 48 89 ef e8 b5 f3 71 e1 48 8b 45 10 48 8d 55 10 48 39 d0 74 0c <c6> 80 90 00 00 00 01 48 8b 00 eb ef 48 89 ef e8 6d f4 71 e1 48 83 Oct 7 12:40:44 Tower kernel: RSP: 0018:ffffc90003ac3ba0 EFLAGS: 00010217 Oct 7 12:40:44 Tower kernel: RAX: 0000000000000000 RBX: ffff888f9ce29630 RCX: ffff88816dbb81c0 Oct 7 12:40:44 Tower kernel: RDX: ffff888f9ce296d8 RSI: ffff88816dbb81e8 RDI: ffff888f9ce296c8 Oct 7 12:40:44 Tower kernel: RBP: ffff888f9ce296c8 R08: ffff888f9cf5e700 R09: 0000000000400031 Oct 7 12:40:44 Tower kernel: R10: ffff888f9cf5e700 R11: ffff88816c661520 R12: ffff888f9ce29628 Oct 7 12:40:44 Tower kernel: R13: ffff888f9ce20000 R14: ffff88810145c370 R15: ffff888100f47a60 Oct 7 12:40:44 Tower kernel: FS: 0000148f4929b6c0(0000) GS:ffff88900eb00000(0000) knlGS:0000000000000000 Oct 7 12:40:44 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 7 12:40:44 Tower kernel: CR2: 0000000000000090 CR3: 000000015dfca000 CR4: 0000000000350ee0 Oct 7 12:40:44 Tower kernel: Call Trace: Oct 7 12:40:44 Tower kernel: <TASK> Oct 7 12:40:44 Tower kernel: amdgpu_fence_driver_sw_fini+0x35/0x7c [amdgpu] Oct 7 12:40:44 Tower kernel: amdgpu_device_fini_sw+0x27/0x2bf [amdgpu] Oct 7 12:40:44 Tower kernel: amdgpu_driver_release_kms+0x12/0x25 [amdgpu] Oct 7 12:40:44 Tower kernel: drm_dev_put+0x31/0x62 [drm] Oct 7 12:40:44 Tower kernel: release_nodes+0x3d/0x5c Oct 7 12:40:44 Tower kernel: devres_release_all+0x91/0xb9 Oct 7 12:40:44 Tower kernel: device_unbind_cleanup+0xe/0x61 Oct 7 12:40:44 Tower kernel: really_probe+0x268/0x273 Oct 7 12:40:44 Tower kernel: __driver_probe_device+0x8d/0xbd Oct 7 12:40:44 Tower kernel: driver_probe_device+0x1f/0x77 Oct 7 12:40:44 Tower kernel: __device_attach_driver+0x83/0x97 Oct 7 12:40:44 Tower kernel: ? driver_allows_async_probing+0x58/0x58 Oct 7 12:40:44 Tower kernel: bus_for_each_drv+0x82/0xad Oct 7 12:40:44 Tower kernel: __device_attach+0xb9/0x154 Oct 7 12:40:44 Tower kernel: bus_rescan_devices_helper+0x3a/0x69 Oct 7 12:40:44 Tower kernel: drivers_probe_store+0x34/0x50 Oct 7 12:40:44 Tower kernel: kernfs_fop_write_iter+0x134/0x17f Oct 7 12:40:44 Tower kernel: new_sync_write+0x7c/0xbb Oct 7 12:40:44 Tower kernel: vfs_write+0xda/0x129 Oct 7 12:40:44 Tower kernel: ksys_write+0x76/0xc2 Oct 7 12:40:44 Tower kernel: do_syscall_64+0x68/0x81 Oct 7 12:40:44 Tower kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd Oct 7 12:40:44 Tower kernel: RIP: 0033:0x148f4aa8542f Oct 7 12:40:44 Tower kernel: Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 19 2d f8 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 6c 2d f8 ff 48 Oct 7 12:40:44 Tower kernel: RSP: 002b:0000148f4929a670 EFLAGS: 00000293 ORIG_RAX: 0000000000000001 Oct 7 12:40:44 Tower kernel: RAX: ffffffffffffffda RBX: 000000000000001c RCX: 0000148f4aa8542f Oct 7 12:40:44 Tower kernel: RDX: 000000000000000c RSI: 0000148f3807a4e0 RDI: 000000000000001c Oct 7 12:40:44 Tower kernel: RBP: 000000000000000c R08: 0000000000000000 R09: 0000148f3c001c00 Oct 7 12:40:44 Tower kernel: R10: 0000000000000000 R11: 0000000000000293 R12: 0000148f3807a4e0 Oct 7 12:40:44 Tower kernel: R13: 000000000000001c R14: 0000000000000000 R15: 0000148f4b2275c0 Oct 7 12:40:44 Tower kernel: </TASK> Oct 7 12:40:44 Tower kernel: Modules linked in: wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha cmac cifs asn1_decoder cifs_arc4 cifs_md4 dns_resolver xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter hfsplus cdrom xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls ixgbe xfrm_algo mdio igb ipv6 gigabyte_wmi wmi_bmof mxm_wmi edac_mce_amd edac_core amdgpu kvm_amd kvm gpu_sched drm_ttm_helper ttm drm_display_helper drm_kms_helper drm crct10dif_pclmul crc32_pclmul backlight agpgart syscopyarea crc32c_intel sysfillrect ghash_clmulni_intel aesni_intel crypto_simd cryptd rapl k10temp Oct 7 12:40:44 Tower kernel: i2c_piix4 ccp sysimgblt fb_sys_fops ahci libahci i2c_algo_bit sata_sil24 nvme i2c_core nvme_core thermal wmi tpm_crb tpm_tis tpm_tis_core tpm button acpi_cpufreq unix [last unloaded: xfrm_algo] Oct 7 12:40:44 Tower kernel: CR2: 0000000000000090 Oct 7 12:40:44 Tower kernel: ---[ end trace 0000000000000000 ]--- Oct 7 12:40:44 Tower kernel: RIP: 0010:drm_sched_fini+0x42/0x90 [gpu_sched] Oct 7 12:40:44 Tower kernel: Code: e8 6c 74 fb e0 48 8d ab 98 00 00 00 4c 8d 63 f8 48 85 ed 74 29 48 89 ef e8 b5 f3 71 e1 48 8b 45 10 48 8d 55 10 48 39 d0 74 0c <c6> 80 90 00 00 00 01 48 8b 00 eb ef 48 89 ef e8 6d f4 71 e1 48 83 Oct 7 12:40:44 Tower kernel: RSP: 0018:ffffc90003ac3ba0 EFLAGS: 00010217 Oct 7 12:40:44 Tower kernel: RAX: 0000000000000000 RBX: ffff888f9ce29630 RCX: ffff88816dbb81c0 Oct 7 12:40:44 Tower kernel: RDX: ffff888f9ce296d8 RSI: ffff88816dbb81e8 RDI: ffff888f9ce296c8 Oct 7 12:40:44 Tower kernel: RBP: ffff888f9ce296c8 R08: ffff888f9cf5e700 R09: 0000000000400031 Oct 7 12:40:44 Tower kernel: R10: ffff888f9cf5e700 R11: ffff88816c661520 R12: ffff888f9ce29628 Oct 7 12:40:44 Tower kernel: R13: ffff888f9ce20000 R14: ffff88810145c370 R15: ffff888100f47a60 Oct 7 12:40:44 Tower kernel: FS: 0000148f4929b6c0(0000) GS:ffff88900eb00000(0000) knlGS:0000000000000000 Oct 7 12:40:44 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 7 12:40:44 Tower kernel: CR2: 0000000000000090 CR3: 000000015dfca000 CR4: 0000000000350ee0 I was also experiencing some minor issues on other boxes with kernels 5.18.x and 5.19.x and decided to skip these kernels. All good with 5.15.x or 5.10.x; 5.15.x will be supported till the end of 2023, 5.10.x till the end of 2026. Is it too much effort to let the users to choose between 2 kernel versions?Maybe support the latest one and the 5.10.x lts? Edited October 7, 2022 by ghost82 Quote Link to comment
Paul_Ber Posted October 7, 2022 Share Posted October 7, 2022 (edited) Not sure if this is a bug. I upgraded from 6.11.0 to 6.11.1. After it was done upgrading, the Nvidia driver said to wait while it downloaded a Nvidia driver for Unraid 6.11.1. Then shutdown, the started up. A drive was missing from one of the slots, one on the HBA card. It is missing in the boot screen for the HBA ctrl-C screen also, so not Unraid then. Edit: Solution. Just weird, the power connector came off too easy on the missing drive. Reseated power connector, no go. Tried a different power connector and Sata end, so now I do not know if it was the power connector or sata end. But working now. Edited October 7, 2022 by Paul_Ber Solution Quote Link to comment
craigr Posted October 7, 2022 Share Posted October 7, 2022 I upgraded last night from 6.10.3 and everything is working perfectly for me! I had tried 6.11.0 but had to fall back due to NTLMv1 authentication and an odd issue with binhexdelugevpn. Both are fixed in this version. Fantastic guys! Quote Link to comment
Flendor Posted October 7, 2022 Share Posted October 7, 2022 6.11 to 6.11.1 upgrade seems to go fine. It downloads the NVDIDIA driver. All done and asks for a reboot. IP address is fixed After the reboot the server comes back up again on the correct IP address, mounts drives, shows array starting... and then the GUI dies, and there is no ping on the server IP address The console shows version 6.11.1 and the original server IP address and can be logged into Reverted back to 6.11 and everyting seemed to worked, except the DelugeVPN docker. Tried again to upgrade, same result. How can i use the console to find if the IP address has changed, or to grab logs? Quote Link to comment
cz13 Posted October 7, 2022 Share Posted October 7, 2022 upgraded 3 Servers to 6.11.1, two from 6.10.3 and one from 6.11.0. Everything seams to be fine. Thanks a lot. Quote Link to comment
craigr Posted October 7, 2022 Share Posted October 7, 2022 13 hours ago, SimonF said: You need to still add this manually to the XML, I am looking at making it automatic in the future. <memoryBacking> <source type='memfd'/> <access mode='shared'/> </memoryBacking> 13 hours ago, Thorsten said: Thanks the VM is starting.... My settings are as follows.... I thought since I have a share under Windows that refers to Unraid /mnt/user. Or am I wrong? I can't get the VM to start. No errors, just sits on TianoCore. I'll have to play more when I have time. Thanks for this feature. craigr Quote Link to comment
sarf Posted October 8, 2022 Share Posted October 8, 2022 Hi Guy's I have an Issue with virtiofs as follows. ubuntu 20.04.5 server vm. Added <memoryBacking> <source type='memfd'/> <access mode='shared'/> </memoryBacking> to the xml - no problem at all. Booted vm with virtiofs and a mapped share - all worked perfectly. mounted the share in vm - no problem at all. "ip address" at terminal in vm returns no ip address from network. shutdown and edit vm and remove virtiofs shares - start up vm, run "ip address" at terminal and it connects to network with valid ip address. tried it many times and does the same thing. hope this helps. 1 Quote Link to comment
SimonF Posted October 8, 2022 Share Posted October 8, 2022 (edited) 41 minutes ago, sarf said: Hi Guy's I have an Issue with virtiofs as follows. ubuntu 20.04.5 server vm. Added <memoryBacking> <source type='memfd'/> <access mode='shared'/> </memoryBacking> to the xml - no problem at all. Booted vm with virtiofs and a mapped share - all worked perfectly. mounted the share in vm - no problem at all. "ip address" at terminal in vm returns no ip address from network. shutdown and edit vm and remove virtiofs shares - start up vm, run "ip address" at terminal and it connects to network with valid ip address. tried it many times and does the same thing. hope this helps. Can you raise a bug report with diagnostics and I will see if I can reproduce. Does 9P work ok? Looks ok on my VM. Edited October 8, 2022 by SimonF Quote Link to comment
JustOverride Posted October 8, 2022 Share Posted October 8, 2022 Upgraded to 6.11.1 from 6.11 without issues. Thanks LT team! Quote Link to comment
optiman Posted October 8, 2022 Share Posted October 8, 2022 Uninstalled nerdpack and upgraded from 10.6.3 to 6.11.1, no issues. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.