archedraft

If I remember correctly you said that this is the first VM you have attempted, correct? If so please try getting a Windows 7,8, or 10 VM working with GPU and USB passthrough. More people can help and it's a lot more clear if your system is capable of even doing USB passthrough. With OSX there could be a multitude of reasons. Let's start eliminating some of the easy ones.

If I select the low option but nothing else of mine is running, will I still get the results of the normal option?

I suppose I should give that a try. I figured with an i7 and only 2 disks that I was OK but maybe with the 3 VMs and multiple dockers it is just too much. I'll report back (probably in a few days) when I have a chance to do this.

I was running a check all disk and the following happened and the same thing happened last night as well with the scheduled check. The files are still getting checked but I wonder if I should be concerned? Jan 16 10:58:15 Pithos kernel: ------------[ cut here ]------------ Jan 16 10:58:15 Pithos kernel: WARNING: CPU: 7 PID: 23760 at arch/x86/kernel/cpu/perf_event_intel_ds.c:315 reserve_ds_buffers+0x10e/0x347() Jan 16 10:58:15 Pithos kernel: alloc_bts_buffer: BTS buffer allocation failure Jan 16 10:58:15 Pithos kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables kvm_intel kvm vhost_net vhost macvtap macvlan tun xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod ahci i2c_i801 libahci r8169 mii acpi_cpufreq Jan 16 10:58:15 Pithos kernel: CPU: 7 PID: 23760 Comm: qemu-system-x86 Not tainted 4.1.15-unRAID #1 Jan 16 10:58:15 Pithos kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H77 Pro4-M, BIOS P2.00 08/06/2013 Jan 16 10:58:15 Pithos kernel: 0000000000000009 ffff88040f60f9a8 ffffffff815f1ad0 0000000000000000 Jan 16 10:58:15 Pithos kernel: ffff88040f60f9f8 ffff88040f60f9e8 ffffffff8104775b ffff88044f255ec0 Jan 16 10:58:15 Pithos kernel: ffffffff8101fd97 0000000000000000 0000000000000000 0000000000010e10 Jan 16 10:58:15 Pithos kernel: Call Trace: Jan 16 10:58:15 Pithos kernel: [<ffffffff815f1ad0>] dump_stack+0x4c/0x6e Jan 16 10:58:15 Pithos kernel: [<ffffffff8104775b>] warn_slowpath_common+0x97/0xb1 Jan 16 10:58:15 Pithos kernel: [<ffffffff8101fd97>] ? reserve_ds_buffers+0x10e/0x347 Jan 16 10:58:15 Pithos kernel: [<ffffffff810477b6>] warn_slowpath_fmt+0x41/0x43 Jan 16 10:58:15 Pithos kernel: [<ffffffff8101fd97>] reserve_ds_buffers+0x10e/0x347 Jan 16 10:58:15 Pithos kernel: [<ffffffff8101ab58>] x86_reserve_hardware+0x141/0x153 Jan 16 10:58:15 Pithos kernel: [<ffffffff8101abae>] x86_pmu_event_init+0x44/0x240 Jan 16 10:58:15 Pithos kernel: [<ffffffff810a7b77>] perf_try_init_event+0x42/0x74 Jan 16 10:58:15 Pithos kernel: [<ffffffff810ad260>] perf_init_event+0x9d/0xd4 Jan 16 10:58:15 Pithos kernel: [<ffffffff810ad61c>] perf_event_alloc+0x385/0x4f7 Jan 16 10:58:15 Pithos kernel: [<ffffffffa015755b>] ? stop_counter+0x2f/0x2f [kvm] Jan 16 10:58:15 Pithos kernel: [<ffffffff810ad7bc>] perf_event_create_kernel_counter+0x2e/0x12c Jan 16 10:58:15 Pithos kernel: [<ffffffffa0157676>] reprogram_counter+0xc0/0x109 [kvm] Jan 16 10:58:15 Pithos kernel: [<ffffffffa0157741>] reprogram_fixed_counter+0x82/0x8d [kvm] Jan 16 10:58:15 Pithos kernel: [<ffffffffa0157929>] reprogram_idx+0x4a/0x4f [kvm] Jan 16 10:58:15 Pithos kernel: [<ffffffffa015818b>] kvm_handle_pmu_event+0x66/0x87 [kvm] Jan 16 10:58:15 Pithos kernel: [<ffffffffa01842dc>] ? vmx_invpcid_supported+0x1b/0x1b [kvm_intel] Jan 16 10:58:15 Pithos kernel: [<ffffffffa01412dc>] kvm_arch_vcpu_ioctl_run+0x4f9/0xeb0 [kvm] Jan 16 10:58:15 Pithos kernel: [<ffffffff815f7d59>] ? retint_kernel+0x1b/0x1d Jan 16 10:58:15 Pithos kernel: [<ffffffffa014c49f>] ? em_cli+0x2d/0x2d [kvm] Jan 16 10:58:15 Pithos kernel: [<ffffffffa0186773>] ? __vmx_load_host_state.part.53+0x125/0x12c [kvm_intel] Jan 16 10:58:15 Pithos kernel: [<ffffffffa013c65b>] ? kvm_arch_vcpu_load+0x139/0x143 [kvm] Jan 16 10:58:15 Pithos kernel: [<ffffffffa0133ff1>] kvm_vcpu_ioctl+0x169/0x48f [kvm] Jan 16 10:58:15 Pithos kernel: [<ffffffff810a5b3e>] ? perf_ctx_unlock+0x20/0x24 Jan 16 10:58:15 Pithos kernel: [<ffffffffa014c49f>] ? em_cli+0x2d/0x2d [kvm] Jan 16 10:58:15 Pithos kernel: [<ffffffff8110c316>] do_vfs_ioctl+0x367/0x421 Jan 16 10:58:15 Pithos kernel: [<ffffffff81114033>] ? __fget+0x6c/0x78 Jan 16 10:58:15 Pithos kernel: [<ffffffff8110c409>] SyS_ioctl+0x39/0x64 Jan 16 10:58:15 Pithos kernel: [<ffffffff815f71ee>] system_call_fastpath+0x12/0x71 Jan 16 10:58:15 Pithos kernel: ---[ end trace 3d8a9b1ae359c9a2 ]---

Correct, you will never pass through Bus 003 but it would still be good to figure out which USB slots belong to Bus 003 for future reference.

Everything works right now so not a big deal. But I think I will take a peak in the BIOS and see what I can do. I'm not sure if that will help. My guess is that you need an add on card, unfortunately I have a silly question... Do they make USB addon cards that have multiple controllers on it? Or is the controller always going to be on the PCI bus? John Not 100% sure but I would highly suspect that it will would be limited to the PCIe slot. Even if the card had multiple controllers you probably wouldn't be able to pass through them to different VM's. I could be completely wrong though...

Hmm, I guess your options are mess around with the bios settings or get an add on card.

Like this idea! +2, or even if you hit "help" and it listed underneath.

Do you happen to have a different USB keyboard and mouse you could try? If the portable hard drive works then technically it is working, so the issue is most likely that keyboard and mouse. Does your keyboard/mouse manufacture have any additional software you can install? For example Logitech has their Setpoint software which I have found to be helpful with my devices.

But what's the fun in that?? I've always preferred the, If it ain't broke then how can we make it better, approach. Much more interesting

bts buffer is the branch trace store buffer, google indicates there was a patch last year to reduce the frequency of such logs & whether it happens or not is a function of memory fragmentation. I would think that seeing this is just a sign that this plugin is working your CPU hard. Any other problems noted or just that warn? That is the only relevant info in the log.

What format are the disks? Recently a warning was added that problems might be encountered with the plugin if Reiserfs is being used for the disks. All disks are XFS

Over the last few weeks my server has been getting random kernel warnings. I have been trying to figure out why they are happening all of the sudden and I think they have something to do with this plugin. After updating to the latest plugin I started running the initial build and export on both of my disks. This kernel warning happened right after I started that process. Does any of this log mean anything too you? Jan 6 21:55:02 Pithos kernel: ------------[ cut here ]------------ Jan 6 21:55:02 Pithos kernel: WARNING: CPU: 3 PID: 24488 at arch/x86/kernel/cpu/perf_event_intel_ds.c:315 reserve_ds_buffers+0x10e/0x347() Jan 6 21:55:02 Pithos kernel: alloc_bts_buffer: BTS buffer allocation failure Jan 6 21:55:02 Pithos kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables kvm_intel kvm vhost_net vhost macvtap macvlan tun xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod ahci r8169 i2c_i801 libahci mii Jan 6 21:55:02 Pithos kernel: CPU: 3 PID: 24488 Comm: qemu-system-x86 Not tainted 4.1.13-unRAID #1 Jan 6 21:55:02 Pithos kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H77 Pro4-M, BIOS P2.00 08/06/2013 Jan 6 21:55:02 Pithos kernel: 0000000000000009 ffff880357b039a8 ffffffff815f12b0 0000000000000000 Jan 6 21:55:02 Pithos kernel: ffff880357b039f8 ffff880357b039e8 ffffffff8104775b ffff88044f395ec0 Jan 6 21:55:02 Pithos kernel: ffffffff8101fd9b 0000000000000000 0000000000000000 0000000000010e10 Jan 6 21:55:02 Pithos kernel: Call Trace: Jan 6 21:55:02 Pithos kernel: [<ffffffff815f12b0>] dump_stack+0x4c/0x6e Jan 6 21:55:02 Pithos kernel: [<ffffffff8104775b>] warn_slowpath_common+0x97/0xb1 Jan 6 21:55:02 Pithos kernel: [<ffffffff8101fd9b>] ? reserve_ds_buffers+0x10e/0x347 Jan 6 21:55:02 Pithos kernel: [<ffffffff810477b6>] warn_slowpath_fmt+0x41/0x43 Jan 6 21:55:02 Pithos kernel: [<ffffffff8101fd9b>] reserve_ds_buffers+0x10e/0x347 Jan 6 21:55:02 Pithos kernel: [<ffffffff8101ab5c>] x86_reserve_hardware+0x141/0x153 Jan 6 21:55:02 Pithos kernel: [<ffffffff8101abb2>] x86_pmu_event_init+0x44/0x240 Jan 6 21:55:02 Pithos kernel: [<ffffffff810a7b77>] perf_try_init_event+0x42/0x74 Jan 6 21:55:02 Pithos kernel: [<ffffffff810ad260>] perf_init_event+0x9d/0xd4 Jan 6 21:55:02 Pithos kernel: [<ffffffff810ad61c>] perf_event_alloc+0x385/0x4f7 Jan 6 21:55:02 Pithos kernel: [<ffffffffa01c1553>] ? stop_counter+0x2f/0x2f [kvm] Jan 6 21:55:02 Pithos kernel: [<ffffffff810ad7bc>] perf_event_create_kernel_counter+0x2e/0x12c Jan 6 21:55:02 Pithos kernel: [<ffffffffa01c166e>] reprogram_counter+0xc0/0x109 [kvm] Jan 6 21:55:02 Pithos kernel: [<ffffffffa01c1739>] reprogram_fixed_counter+0x82/0x8d [kvm] Jan 6 21:55:02 Pithos kernel: [<ffffffffa01c1921>] reprogram_idx+0x4a/0x4f [kvm] Jan 6 21:55:02 Pithos kernel: [<ffffffffa01c2183>] kvm_handle_pmu_event+0x66/0x87 [kvm] Jan 6 21:55:02 Pithos kernel: [<ffffffffa01ee2dc>] ? vmx_invpcid_supported+0x1b/0x1b [kvm_intel] Jan 6 21:55:02 Pithos kernel: [<ffffffffa01ab2dc>] kvm_arch_vcpu_ioctl_run+0x4f9/0xeb0 [kvm] Jan 6 21:55:02 Pithos kernel: [<ffffffffa01f0773>] ? __vmx_load_host_state.part.53+0x125/0x12c [kvm_intel] Jan 6 21:55:02 Pithos kernel: [<ffffffffa01a665b>] ? kvm_arch_vcpu_load+0x139/0x143 [kvm] Jan 6 21:55:02 Pithos kernel: [<ffffffffa019dff1>] kvm_vcpu_ioctl+0x169/0x48f [kvm] Jan 6 21:55:02 Pithos kernel: [<ffffffffa019de88>] ? vcpu_put+0x3b/0x3b [kvm] Jan 6 21:55:02 Pithos kernel: [<ffffffff8110c316>] do_vfs_ioctl+0x367/0x421 Jan 6 21:55:02 Pithos kernel: [<ffffffff81114033>] ? __fget+0x6c/0x78 Jan 6 21:55:02 Pithos kernel: [<ffffffff8110c409>] SyS_ioctl+0x39/0x64 Jan 6 21:55:02 Pithos kernel: [<ffffffff815f69ae>] system_call_fastpath+0x12/0x71 Jan 6 21:55:02 Pithos kernel: ---[ end trace cf2394a39c569833 ]--- Jan 6 21:57:02 Pithos bunker: added 3 files from /mnt/disk2 with mask *. Duration: 00:04:54 Average speed: 46.6 MB/s Jan 6 21:57:27 Pithos bunker: added 8 files from /mnt/disk1 with mask *. Duration: 00:05:20 Average speed: 93.0 MB/s Jan 6 21:57:59 Pithos emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Jan 6 21:58:11 Pithos emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Jan 6 21:59:41 Pithos bunker: exported 42588 files from /mnt/disk1 with mask *. Duration: 00:00:31 Jan 6 22:00:24 Pithos emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Jan 6 22:01:51 Pithos bunker: exported 34208 files from /mnt/disk2 with mask *. Duration: 00:02:41

Just updated and saw that my disks have the orange circle. To clarify, will they always be a circle upon a refresh reboot of the server?

Have created the following, see the attached picture. For all disks it will show whether an initial build and/or an initial export was done. A green check means yes, while an orange circle means no. Useful ? Yes, I think it looks nice and adds value.

Fantastic! I wanted to build something like that eventually since our list of packages keeps growing. Nice work! Are you open to collaboration and merging your work in to the existing Nerdpack repo/plugin? I open to whatever you wanna do. Let me know what you think is best. Did you guys ever work out if this is getting incorporated directly into Nerdpack or if they are being separate?

Two more feature requests/wish list items Not sure how much trouble they would be to implement but I figure it can not hurt to ask and see what sticks. 1. It would be awesome if there was some sort of icon letting you know that all items (besides excluded folders) on disk1, 2, 3, etc. have a checksum. It would be nice for peace of mind. Maybe if not all file had a checksum then you could see a list of them? 2. Might also be nice if there was a way to check individual folders or files for valid checksums. Especially with people who have slower CPU's they might be concerned about a specific folder but a 8TB filled drive takes awhile to calculate.

Seems like a pretty interesting game. I was looking at the files on docker hub but honestly I am not good at all when it comes to creating dockers. If it was me I would end up creating a Linux VM and following this guide: http://ark.gamepedia.com/Dedicated_Server_Setup But maybe someone with a better understanding of how docker works can point out what's going on...

Once a controller gets past through unRAID no longer can see the controller. Once the VM gets shutdown, unRAID doesn't know that the controller is available so you have to restart the server in order for unRAID to see it again. There may be some sort of script you can create that will let unRAID know that the controller is free.

Yes you still have to do the steps up to and including 9. Alright, made an 11.a and 11.b step giving users the choice Just tried passthrough hostdev with a windows machine and that works fine.. But again a gfx card just gives a black screen/no output.. If I remember correctly, JonP mentioned many months ago in a forum post long forgotten, that he had much better luck with the arg format as opposed to the hostdev approach in regards to GPU... [disclaimer, I may have made all that up but I want to say I remember reading that]

Yes you still have to do the steps up to and including 9. Alright, made an 11.a and 11.b step giving users the choice

Yes you still have to do the steps up to and including 9. Slightly OT, but would hostdev work for gfx cards? Yes Might try in with OSX just for science.... Let me know what you find!

So then I suppose even with hostdev you will still have to go through the entire first process of finding out which controller you want?

I added this to the end of the guide, I know it is else where but I think it should be handy anyways. Thanks. Good choice I just read what you added and it says Oops good catch, I was editing the whole first page at a million miles a minute and sort of word vomitted that.

I added this to the end of the guide, I know it is else where but I think it should be handy anyways. Thanks.