eschultz

Those are pretty interesting results, @bastl! I'll need to confirm those thread pairings on my Threadripper -- It's possible Linux is confused on the actual thread parings for threadripper.

Probably in a week. QEMU 3.0 was just released so we'll get that in to the public unRAID 6.6-rc release too.

Your CPU (Intel Celeron G1610T) doesn't support VT-d even though the motherboard does: https://ark.intel.com/products/71074/Intel-Celeron-Processor-G1610T-2M-Cache-2_30-GHz

These keyboard issues are solved in the upcoming unRAID 6.6 -- it includes an updated version of QEMU that has the keyboard mappings fixed.

Yup, that's basically the steps. @Bob1215 Which Linux distro are you using? The 'make_bootable_linux' I built and tested from Ubuntu and should be generic enough to run in many other distros.

We plan on adding API rest endpoints for everything in the gui some point down the road. I think that'll make your job much easier!

@TechMed Did you ever try unRAID 6.5+ on one of your H8DME-2 with the IPMI card installed? Just wondering if it made it to the console and didn't hang somewhere in the process of booting up.

@jfeeser How's the new build working out for you?

You have the user.scripts plugin installed... is there something custom running there that might be causing this? You could reboot and select 'safe mode' to boot and that would prevent all installed plugins from loading. Edit: Yes, it looks like it's hung up on this user script: /tmp/user.scripts/tmpScripts/Deluge_Collector/script

virtio should give you the best performance since it's not emulated like the other virtual network card options. The Supermicro board you have only has 1Gpbs ports, did you have a 10Gbps NIC addon? If so, what brand and model?

Seems like one of the sticks of ram is going bad too.

Your saying 6.5.2 was completely stable for you, just become unstable at 6.5.3?

and Chrome from Windows 10 looks a bit different: So these aren't "images" but rather the browser/OS is rendering these emoji (like a system font). Each one of these are essentially just a single unicode character.

Your uncolored emoji looks colored to me: (I'm on a Mac)

Even my poor normal-user test account, with 0 posts, has the skin tone option and color.

Which browser are you using? Firefox and Chrome for me show the same ones in color:

Can anyone here confirm the 20-25% cpu usage for an idle Windows 10 VM, without HPET, that's just using VNC graphics (no GPU passthrough)?

The current web interface only lets 'root' login.

Certainly is enough for storage and light Docker use.

Also this: Jun 17 10:07:18 MediaCentre kernel: BTRFS info (device loop2): space_info 4 has 934412288 free, is not full Jun 17 10:07:18 MediaCentre kernel: BTRFS info (device loop2): space_info total=1073741824, used=139247616, pinned=0, reserved=16384, may_use=0, readonly=65536 Jun 17 10:07:18 MediaCentre kernel: BTRFS warning (device loop2): page private not zero on page 153567232 Jun 17 10:07:18 MediaCentre kernel: BTRFS warning (device loop2): page private not zero on page 153571328 Jun 17 10:07:18 MediaCentre kernel: BTRFS warning (device loop2): page private not zero on page 153575424 Jun 17 10:07:18 MediaCentre kernel: BTRFS warning (device loop2): page private not zero on page 153579520 loop2 is probably your docker image file (20GB).

Just so it's easier to see, here's the call trace: Jun 17 10:07:18 MediaCentre kernel: WARNING: CPU: 10 PID: 19572 at fs/btrfs/extent-tree.c:9968 btrfs_free_block_groups+0x245/0x2da Jun 17 10:07:18 MediaCentre kernel: Modules linked in: xt_nat veth xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat arc4 ecb md4 cifs ccm xfs md_mod bonding e1000e igb ptp pps_core i2c_algo_bit x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_uncore intel_rapl_perf ahci i2c_i801 mxm_wmi i2c_core libahci video wmi backlight button acpi_pad [last unloaded: tun] Jun 17 10:07:18 MediaCentre kernel: CPU: 10 PID: 19572 Comm: umount Tainted: G W 4.14.40-unRAID #1 Jun 17 10:07:18 MediaCentre kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z370M-ITX/ac, BIOS P1.60 11/30/2017 Jun 17 10:07:18 MediaCentre kernel: task: ffff88045ba62ac0 task.stack: ffffc90001ea0000 Jun 17 10:07:18 MediaCentre kernel: RIP: 0010:btrfs_free_block_groups+0x245/0x2da Jun 17 10:07:18 MediaCentre kernel: RSP: 0018:ffffc90001ea3e18 EFLAGS: 00010206 Jun 17 10:07:18 MediaCentre kernel: RAX: ffff880448b0d288 RBX: ffff8804576e2000 RCX: 000000018020000e Jun 17 10:07:18 MediaCentre kernel: RDX: ffff8804576e2e28 RSI: ffff880448b0f200 RDI: ffffffff81b5325d Jun 17 10:07:18 MediaCentre kernel: RBP: ffff880448b0d288 R08: 0000000000000001 R09: ffffffff815c7000 Jun 17 10:07:18 MediaCentre kernel: R10: ffffea001122c300 R11: 0000000000000001 R12: 0000000000000038 Jun 17 10:07:18 MediaCentre kernel: R13: 0000000000000000 R14: dead000000000100 R15: ffff8804576e20a0 Jun 17 10:07:18 MediaCentre kernel: FS: 000014dd6b89f780(0000) GS:ffff88045e880000(0000) knlGS:0000000000000000 Jun 17 10:07:18 MediaCentre kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 17 10:07:18 MediaCentre kernel: CR2: 000014e4922e19d8 CR3: 000000010dc18001 CR4: 00000000003606e0 Jun 17 10:07:18 MediaCentre kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jun 17 10:07:18 MediaCentre kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Jun 17 10:07:18 MediaCentre kernel: Call Trace: Jun 17 10:07:18 MediaCentre kernel: close_ctree+0x1b7/0x27d Jun 17 10:07:18 MediaCentre kernel: generic_shutdown_super+0x6b/0x10a Jun 17 10:07:18 MediaCentre kernel: kill_anon_super+0x9/0xe Jun 17 10:07:18 MediaCentre kernel: btrfs_kill_super+0xd/0x8e Jun 17 10:07:18 MediaCentre kernel: deactivate_locked_super+0x2f/0x61 Jun 17 10:07:18 MediaCentre kernel: cleanup_mnt+0x40/0x5c Jun 17 10:07:18 MediaCentre kernel: task_work_run+0x73/0x86 Jun 17 10:07:18 MediaCentre kernel: exit_to_usermode_loop+0x46/0x75 Jun 17 10:07:18 MediaCentre kernel: do_syscall_64+0xf7/0xfe Jun 17 10:07:18 MediaCentre kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jun 17 10:07:18 MediaCentre kernel: RIP: 0033:0x14dd6ab11ec7 Jun 17 10:07:18 MediaCentre kernel: RSP: 002b:00007ffef21e65d8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6 Jun 17 10:07:18 MediaCentre kernel: RAX: 0000000000000000 RBX: 00000000006072b0 RCX: 000014dd6ab11ec7 Jun 17 10:07:18 MediaCentre kernel: RDX: 0000000000000001 RSI: 0000000000000000 RDI: 000000000060b1a0 Jun 17 10:07:18 MediaCentre kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 Jun 17 10:07:18 MediaCentre kernel: R10: 0000000000000008 R11: 0000000000000246 R12: 000000000060b1a0 Jun 17 10:07:18 MediaCentre kernel: R13: 000014dd6b68aed0 R14: 0000000000607490 R15: 0000000000000000 Jun 17 10:07:18 MediaCentre kernel: Code: 8d 93 28 0e 00 00 48 39 c2 0f 84 a4 00 00 00 48 8b ab 28 0e 00 00 48 83 7d 90 00 75 0e 48 83 7d 98 00 75 07 48 83 7d a0 00 74 15 <0f> 0b 31 c9 31 d2 48 89 df 48 8d b5 78 ff ff ff e8 4e 7a ff ff

The call traces are related to your USB controllers. Most likely you won't be able to passthrough any USB controllers to a VM (but USB device assignment would probably work fine). Here's one of the call traces: Jun 15 11:52:46 Tower kernel: WARNING: CPU: 2 PID: 1 at drivers/iommu/intel-iommu.c:2689 domain_prepare_identity_map+0xa2/0x13a Jun 15 11:52:46 Tower kernel: Modules linked in: Jun 15 11:52:46 Tower kernel: CPU: 2 PID: 1 Comm: swapper/0 Tainted: G I 4.14.49-unRAID #1 Jun 15 11:52:46 Tower kernel: Hardware name: System manufacturer System Product Name/P6T SE, BIOS 0908 09/21/2010 Jun 15 11:52:46 Tower kernel: task: ffff88013a730000 task.stack: ffffc90000644000 Jun 15 11:52:46 Tower kernel: RIP: 0010:domain_prepare_identity_map+0xa2/0x13a Jun 15 11:52:46 Tower kernel: RSP: 0000:ffffc90000647b38 EFLAGS: 00010292 Jun 15 11:52:46 Tower kernel: RAX: 0000000000000085 RBX: ffffffff8203a01c RCX: 0000000000000251 Jun 15 11:52:46 Tower kernel: RDX: 0000000000000001 RSI: 0000000000000002 RDI: 0000000000000246 Jun 15 11:52:46 Tower kernel: RBP: ffffffff8203a058 R08: 0000000000000007 R09: ffff8800000bc000 Jun 15 11:52:46 Tower kernel: R10: 0000000000000000 R11: 000000000000bf48 R12: 00000000bf7dc000 Jun 15 11:52:46 Tower kernel: R13: 0000000000000003 R14: ffffffff81b64797 R15: ffff880139957000 Jun 15 11:52:46 Tower kernel: FS: 0000000000000000(0000) GS:ffff88013b280000(0000) knlGS:0000000000000000 Jun 15 11:52:46 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 15 11:52:46 Tower kernel: CR2: 0000000000000000 CR3: 0000000001c0a000 CR4: 00000000000006e0 Jun 15 11:52:46 Tower kernel: Call Trace: Jun 15 11:52:46 Tower kernel: get_valid_domain_for_dev+0x89/0xf8 Jun 15 11:52:46 Tower kernel: __intel_map_single+0x3a/0x150 Jun 15 11:52:46 Tower kernel: intel_alloc_coherent+0xc3/0xe7 Jun 15 11:52:46 Tower kernel: dma_pool_alloc+0x100/0x1c0 Jun 15 11:52:46 Tower kernel: ehci_qh_alloc+0x36/0xab Jun 15 11:52:46 Tower kernel: ehci_setup+0x1c2/0x4b9 Jun 15 11:52:46 Tower kernel: ehci_pci_setup+0x333/0x47d Jun 15 11:52:46 Tower kernel: usb_add_hcd+0x266/0x772 Jun 15 11:52:46 Tower kernel: usb_hcd_pci_probe+0x222/0x37a Jun 15 11:52:46 Tower kernel: local_pci_probe+0x3c/0x7a Jun 15 11:52:46 Tower kernel: pci_device_probe+0x11b/0x154 Jun 15 11:52:46 Tower kernel: driver_probe_device+0x142/0x2a6 Jun 15 11:52:46 Tower kernel: ? set_debug_rodata+0xc/0xc Jun 15 11:52:46 Tower kernel: __driver_attach+0x68/0x88 Jun 15 11:52:46 Tower kernel: ? driver_probe_device+0x2a6/0x2a6 Jun 15 11:52:46 Tower kernel: bus_for_each_dev+0x63/0x7a Jun 15 11:52:46 Tower kernel: bus_add_driver+0xe1/0x1c6 Jun 15 11:52:46 Tower kernel: driver_register+0x7d/0xaf Jun 15 11:52:46 Tower kernel: ? ehci_hcd_init+0x52/0x52 Jun 15 11:52:46 Tower kernel: do_one_initcall+0x89/0x11e Jun 15 11:52:46 Tower kernel: kernel_init_freeable+0x171/0x1f4 Jun 15 11:52:46 Tower kernel: ? rest_init+0xa5/0xa5 Jun 15 11:52:46 Tower kernel: kernel_init+0x5/0xeb Jun 15 11:52:46 Tower kernel: ret_from_fork+0x35/0x40 Jun 15 11:52:46 Tower kernel: Code: 00 48 89 c5 e8 73 20 0d 00 bf 01 00 00 00 48 89 c3 e8 66 20 0d 00 48 89 e9 48 89 da 48 c7 c7 45 40 b6 81 48 89 c6 e8 60 47 cd ff <0f> 0b eb 70 6b 8d 44 0a 00 00 09 41 bd 40 00 00 00 48 89 d8 83 Jun 15 11:52:46 Tower kernel: ---[ end trace 4d522f905ad2e847 ]--- Jun 15 11:52:46 Tower kernel: ehci-pci 0000:00:1a.7: Mapping reserved region failed Jun 15 11:52:46 Tower kernel: DMAR: Setting identity map for device 0000:00:1a.7 [0xec000 - 0xeffff] Jun 15 11:52:46 Tower kernel: ehci-pci 0000:00:1a.7: cache line size of 256 is not supported Jun 15 11:52:46 Tower kernel: ehci-pci 0000:00:1a.7: irq 18, io mem 0xfbcff000 Jun 15 11:52:46 Tower kernel: ehci-pci 0000:00:1a.7: USB 2.0 started, EHCI 1.00 Jun 15 11:52:46 Tower kernel: hub 1-0:1.0: USB hub found Jun 15 11:52:46 Tower kernel: hub 1-0:1.0: 6 ports detected Jun 15 11:52:46 Tower kernel: ehci-pci 0000:00:1d.7: EHCI Host Controller Jun 15 11:52:46 Tower kernel: ehci-pci 0000:00:1d.7: new USB bus registered, assigned bus number 2 Jun 15 11:52:46 Tower kernel: ehci-pci 0000:00:1d.7: debug port 1 Jun 15 11:52:46 Tower kernel: DMAR: 32bit 0000:00:1d.7 uses non-identity mapping Jun 15 11:52:46 Tower kernel: DMAR: Setting identity map for device 0000:00:1d.7 [0xbf7dc000 - 0xbf7dbfff] Jun 15 11:52:46 Tower kernel: Your BIOS is broken; RMRR ends before it starts! Jun 15 11:52:46 Tower kernel: BIOS vendor: American Megatrends Inc.; Ver: 0908 ; Product Version: System Version This most likely is a BIOS bug. You're already running the latest BIOS but that motherboard is dated and Asus won't be providing any more updates for it.

I got in touch with the developer and he was able to make it work with OpenSSL 1.1.x... so I will add this in to unRAID 6.6. Please share some benchmarks if you're able to compare unRAID 6.5 to unRAID 6.6 in SSH network transfer speeds.

Try using OVMF instead of Seabios for your VMs -- unfortunately you can't change this setting once your VM OS is installed so you'll have to create a pair of new VMs. At least you can create a new VM with OVMF and just see if starting that VM causes the screen to go blank on your console.

Does your cache pool devices consist of SSDs or HDDs? Are you using Dynamix S3 Sleep plugin or some other way to make your machine sleep?