winklevos

My upgrade from 6.9.2 went well, much better than RC1. Only issue i've got of note now is onboard bluetooth passthough is not working in windows 10 VM. https://forums.unraid.net/topic/117082-bluetooth-passthru-to-vm-not-working-on-6100-rc2/?tab=comments#comment-1079352

I also have this issue, unable to get onboard BT working in VM. Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) is the onboard PCI device, which is completely passed through and the WIFI component works. PCI Devices and IOMMU Groups IOMMU group 0: [8086:9b33] 00:00.0 Host bridge: Intel Corporation Device 9b33 (rev 05) IOMMU group 1: [8086:1901] 00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 05) IOMMU group 2: [8086:1905] 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x8) (rev 05) IOMMU group 3: [8086:9bc5] 00:02.0 VGA compatible controller: Intel Corporation CometLake-S GT2 [UHD Graphics 630] (rev 05) IOMMU group 4: [8086:43ed] 00:14.0 USB controller: Intel Corporation Tiger Lake-H USB 3.2 Gen 2x1 xHCI Host Controller (rev 11) This controller is bound to vfio, connected USB devices are not visible. [8086:43ef] 00:14.2 RAM memory: Intel Corporation Tiger Lake-H Shared SRAM (rev 11) IOMMU group 5: [8086:43e8] 00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-H Serial IO I2C Controller #0 (rev 11) [8086:43e9] 00:15.1 Serial bus controller [0c80]: Intel Corporation Device 43e9 (rev 11) IOMMU group 6: [8086:43e0] 00:16.0 Communication controller: Intel Corporation Tiger Lake-H Management Engine Interface (rev 11) IOMMU group 7: [8086:43d2] 00:17.0 SATA controller: Intel Corporation Device 43d2 (rev 11) [2:0:0:0] disk ATA ST8000VN004-2M21 SC60 /dev/sdb 8.00TB [4:0:0:0] disk ATA Samsung SSD 870 1B6Q /dev/sdc 1.00TB [5:0:0:0] disk ATA Samsung SSD 860 4B6Q /dev/sdd 1.00TB IOMMU group 8: [8086:43c0] 00:1b.0 PCI bridge: Intel Corporation Device 43c0 (rev 11) IOMMU group 9: [8086:43b8] 00:1c.0 PCI bridge: Intel Corporation Device 43b8 (rev 11) IOMMU group 10: [8086:43bd] 00:1c.5 PCI bridge: Intel Corporation Device 43bd (rev 11) IOMMU group 11: [8086:43be] 00:1c.6 PCI bridge: Intel Corporation Device 43be (rev 11) IOMMU group 12: [8086:43bf] 00:1c.7 PCI bridge: Intel Corporation Device 43bf (rev 11) IOMMU group 13: [8086:43b0] 00:1d.0 PCI bridge: Intel Corporation Tiger Lake-H PCI Express Root Port #9 (rev 11) IOMMU group 14: [8086:4385] 00:1f.0 ISA bridge: Intel Corporation Device 4385 (rev 11) [8086:f0c8] 00:1f.3 Audio device: Intel Corporation Device f0c8 (rev 11) [8086:43a3] 00:1f.4 SMBus: Intel Corporation Tiger Lake-H SMBus Controller (rev 11) [8086:43a4] 00:1f.5 Serial bus controller [0c80]: Intel Corporation Tiger Lake-H SPI Controller (rev 11) IOMMU group 15: [10de:1e81] 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) IOMMU group 16: [10de:10f8] 01:00.1 Audio device: NVIDIA Corporation TU104 HD Audio Controller (rev a1) IOMMU group 17: [10de:1ad8] 01:00.2 USB controller: NVIDIA Corporation TU104 USB 3.1 Host Controller (rev a1) This controller is bound to vfio, connected USB devices are not visible. IOMMU group 18: [10de:1ad9] 01:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU104 USB Type-C UCSI Controller (rev a1) IOMMU group 19: [1b73:1100] 02:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10) Bus 005 Device 001 Port 5-0 ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002 Port 5-4 ID 1d5c:5011 Fresco Logic USB2.0 Hub Bus 006 Device 001 Port 6-0 ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 006 Device 002 Port 6-2 ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive Bus 006 Device 003 Port 6-4 ID 1d5c:5001 Fresco Logic USB3.0 Hub IOMMU group 20: [1000:0072] 03:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) [1:0:0:0] disk ATA Samsung SSD 870 1B6Q /dev/sde 1.00TB [1:0:1:0] disk ATA ST16000NM001G-2K SN02 /dev/sdf 16.0TB [1:0:2:0] disk ATA ST16000NM001G-2K SN02 /dev/sdg 16.0TB [1:0:3:0] disk ATA ST8000VN0022-2EL SC61 /dev/sdh 8.00TB IOMMU group 21: [8086:15f3] 05:00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-V (rev 03) IOMMU group 22: [8086:15f3] 06:00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-V (rev 03) IOMMU group 23: [8086:2725] 07:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) IOMMU group 24: [144d:a808] 08:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 This controller is bound to vfio, connected drives are not visible. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='1'> <name>Windows 10</name> <uuid>30254974-facb-777e-7ee4-19438c9b00d4</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>33554432</memory> <currentMemory unit='KiB'>33554432</currentMemory> <memoryBacking> <hugepages/> <nosharepages/> </memoryBacking> <vcpu placement='static'>14</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='11'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='12'/> <vcpupin vcpu='4' cpuset='3'/> <vcpupin vcpu='5' cpuset='13'/> <vcpupin vcpu='6' cpuset='4'/> <vcpupin vcpu='7' cpuset='14'/> <vcpupin vcpu='8' cpuset='5'/> <vcpupin vcpu='9' cpuset='15'/> <vcpupin vcpu='10' cpuset='6'/> <vcpupin vcpu='11' cpuset='16'/> <vcpupin vcpu='12' cpuset='7'/> <vcpupin vcpu='13' cpuset='17'/> <emulatorpin cpuset='9,19'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-6.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/30254974-facb-777e-7ee4-19438c9b00d4_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vpindex state='on'/> <synic state='on'/> <stimer state='on'/> <reset state='on'/> <vendor_id state='on' value='1234567890ab'/> <frequencies state='on'/> </hyperv> <kvm> <hidden state='on'/> </kvm> <vmport state='off'/> <ioapic driver='kvm'/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='7' threads='2'/> <cache mode='passthrough'/> </cpu> <clock offset='utc'> <timer name='rtc' present='no' tickpolicy='catchup'/> <timer name='pit' present='no' tickpolicy='delay'/> <timer name='hpet' present='no'/> <timer name='hypervclock' present='yes'/> <timer name='tsc' present='yes' mode='native'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10/vdisk1.img' index='2'/> <backingStore/> <target dev='hdc' bus='virtio'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.208-1.iso' index='1'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <interface type='bridge'> <mac address='52:54:00:db:92:c6'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-1-Windows 10/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/isos/2080s_trimmed.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x14' function='0x0'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x2'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x2'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x3'/> </source> <alias name='hostdev4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x3'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </source> <alias name='hostdev5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x10' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </source> <boot order='1'/> <alias name='hostdev6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0c' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>

To further this, trying to boot in safemode throws Cannot find device "bond0" After more testing, I did a completely fresh install of the new release, (no existing config). These same errors occurring. Sometimes unable to boot correctly with Cannot find device "bond0"

On another note, only thing issue so far seems to be vfio binding, vms can't work chown: cannot access '/dev/vfio/15': No such file or directory Error: unable to adjust group ownership of /dev/vfio/15 odin-diagnostics-20211028-2339.zip

There is a lot going on in the release, and a lot of good! Some mixed sentiment on the UPC and My Server stuff. Firstly the My Server stuff is fine, an optional additional service people can use to remotely monitor one or more servers. Great stuff useful for those that need or want this. The UPC stuff is a little more complex. I changed my key today, the old way, and it was super simple barely an inconvenience. I'll outline my concerns with this direction, take them as you will. UPC is linking to a forum. It could be that the forum backend is the core authentication system / CRM or the like, but it seems an odd choice to me. If a server is authenticated via UPC an open web socket is maintained. Generally not a big deal, but it's another thing to be exploited and as others have pointed out didn't work out so well for other companies. All information is useful to a hacker, no matter how little data may be captured if there is a breach it is exposing potentially vast configurations, IPs, and so on. On the configuration backups, why a private repo? This seems odd to me, are these encrypted per server? Wouldn't just end to end encrypted file blobs be more secure, regardless of saying "it doesn't include files with sensitive info". No company regardless of design or merit is immune to breaches, hacks, or acquisitions. While it's clear now that if you have a valid key you do not need to authenticate with UPC (forum), this is pretty much how all non-cloud authentications go to die. I've seen, you've seen it... And I get it, from a business perspective, it's easier for you to manage centrally, oversee, and move towards the subscription model. Confidence that a path like this isn't in the future would ease many, especially in the area of data storage where moving is not always trivial. Are you GDPR compliant, or similar data protection schemes (kind of not specific to the release, just generally) Are you ISO27001 and SOC certified such that we can be sure your development pipelines to your infrastructure won't be compromised with active connections to our servers? These are my concerns, the features and functions of Unraid in this release are great. Thanks for the work put into them

Also interested in what everyone is using, and if the 6.9 version is better with UEFI and 3.0 USBs? I had been running off SanDisk Cruzer Glide 3.0 16GB (SDCZ600-016G) for a few years but now my server doesn't want to post with it plugged in. I'm going to grab a couple of different models and see what works @Rick Sanchez not sure if you found Testing to find the best USB flash drive to boot an OS like Unraid - YouTube

Yeah shortly after they worked, got it all sorted. Unrelated note, @falconexe this dashboard is great, good work to all involved. I have some experience in the dashboard and data landscape and would enjoy helping out. After getting this setup I can see generalising the dashboard to accommodate other hardware configurations would be cool. Plus influxDB V2. Let me know, not sure if you are all collabing in a git

This would be easier if Unraid supported docker-compose, otherwise it could be rolled into one docker image. Also the links to the grafana json dashboards are dead on the first page