mikeyosm

What's up with SAMBA shares in this beta? I am using two VMs (win2012 - Win10) and have a downloads folder located on a SSD shared using 'unassigned devices' plugin. If I download and save a file to the downloads folder I have to refresh explorer or close it/reopen it to see the file. I also have a very large (120GB) VHD file located on the same share that cannot be opened/mounted unless I first copy it to my C drive on my windows guest. What's going on?

Please add your diagnostics zip, and if possible a recent diagnostics zip from v6.1.9 for comparison. Please see attached. I noticed some more sata related errors this morning. thank you. I replaced my SATA cables and the SATA errors seems to have gone (for now). Still getting the kernel: usb 3-7: device descriptor read/all, error -71 error though.

Please add your diagnostics zip, and if possible a recent diagnostics zip from v6.1.9 for comparison. Please see attached. I noticed some more sata related errors this morning. thank you. mounraid01-syslog-20160322-0934.zip mounraid01-diagnostics-20160322-0941.zip

Upgraded to b19 and noticed the following in logs.... Is there anything there I should be concerned about? Since the upgrade my SSD which has the shares, docker img etc mysteriously disappears from UNRAID and I have to power cycle the computer to get it re-recognised in the BIOS again. It was not doing this in in 6.1.9. Mar 21 20:35:17 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen Mar 21 20:35:17 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error Mar 21 20:36:02 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen Mar 21 20:36:02 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error Mar 21 20:36:19 MOUNRAID01 kernel: usb 3-7: device descriptor read/all, error -71 Mar 21 20:37:42 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen Mar 21 20:37:42 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error Mar 21 20:59:03 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen Mar 21 20:59:03 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error Mar 21 21:04:38 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen Mar 21 21:04:38 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error Mar 21 22:48:21 MOUNRAID01 kernel: usb 3-7: device descriptor read/all, error -71 Mar 21 22:48:21 MOUNRAID01 kernel: usb 3-7: device descriptor read/all, error -71 Mar 21 22:48:22 MOUNRAID01 kernel: usb 3-7: device descriptor read/all, error -71 Mar 21 22:48:22 MOUNRAID01 kernel: usb 3-7: device descriptor read/all, error -71 Mar 21 22:49:16 MOUNRAID01 kernel: usb 3-7: device descriptor read/all, error -71 Mar 21 22:49:16 MOUNRAID01 kernel: usb 3-7: device descriptor read/all, error -71 Mar 21 22:49:17 MOUNRAID01 kernel: usb 3-7: device descriptor read/8, error -71 Mar 21 22:49:17 MOUNRAID01 kernel: usb 3-7: device descriptor read/all, error -71 Mar 21 22:49:18 MOUNRAID01 kernel: usb 3-7: device descriptor read/all, error -71 Mar 21 22:51:53 MOUNRAID01 kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen Mar 21 22:51:53 MOUNRAID01 kernel: ata5.00: irq_stat 0x08000000, interface fatal error

Has anyone had success with 6.2 beta 18 or 19 booting their OSX VM? It was working fine for me on 6.1.9 with GPU passthrough but now I'm on 6.2b19, the VM refuses to start with the GPU assigned 'device initialization failure'. Without GPU (nvidia 750ti) passthrough the VM boots as far as the moving progress bar under the apple logo and stays like that for ages. It simply won't get to the login screen.

well i tried it and it does seem to resolve the problem. However, I tried this on an osx VM that booted past the SEABIOS before and now it doesnt, grrr.

It's already in the new beta. Or do you have even more groups than in this hotfix? I have 37 groups. Any harm in trying the file anyhow to see if it resolves the issue?

Did the vfio fix as described here https://lime-technology.com/forum/index.php?topic=44010.0 make it in to the beta release? I am having the same issue still but want to be sure the fix won't break anything else in the beta.

I just came across this error in 6.2b19. Is it safe to use the qemu.conf file in this post overwriting the beta version file?

HT enabled, hyper-v enabled 4 cores assigned so far. No ISOLCPU or pinning required. I will be trying 8 cores later to see if performance scales as expected. EDIT: 8 cores assigned, no performance issues cpu or gpu. Fantastic!

So an update on my issue since trying 6.2b 19 I am pleased to say that the hyper-v enlightenment has resolved my crappy 2d/desktop performance issue with my 980ti. Very happy with the performance overall thus far.

yes, all fixed, thanks!

Hi So, I took the plunge and installed beta19 over my 6.1.9 install. Install went fine but now after I rebooted I don't see the VM or Docker TAB yet they are both enabled in settings. I check the VM Manager settings and libvirt is pointing to a location that does not exist /mnt/user/system/libvirt/libvirt.img I then created the directory /system/libvirt but this has made no difference. I also noted that when starting the array, libvirt service and docker etc are not showing as starting like they did before in the status bar at the bottom. Is there some maintenance/migration tasks I need to perform? Please help. thanks.

Not stopping me as long as I don't exceed 4 cores on a VM, even with HT enabled. I will be trying 6.2 soon. I am curious though whether some issues people are having with poor cpu and GPU performance is linked to Xeon processors.

Yeah, thought as much, shame really. I have my wired razer wildcat gamepad set to allow wake up from sleep but when I click a button on the controller it does not wake the VM.

Hello I just noticed that devices in device manager such as my Logitech G19 keyboard and G400 mouse have 'allow this device to wake the computer' grayed out and I'm unable to select it. What do I need to do in unraid and/or Windows to enable this feature? My BIOS has all sleep states and USB device wake enabled. The USB hub that my keyboard/mouse are connected to is passed through to the VM. Thank you.

anywhere between 50 and 60'c with my 950 pro 512GB. I also added heatsinks on the ram chips to drop the temps a few degrees since the m.2 slot is directly under my passive 750ti.

Don't expect max rated speeds with overheads of unraid hypervisor. I get around 1800 and 900 in passthrough, maybe a tad more with AV off and no other disk activity.

How many cores are you allocating to your VM? I found that anything more than 4 cores lead to stutter and generally poor desktop and gaming performance regardless of HT enabled or not. I'm stable as long as I don't use more than 4 cores per VM

I'm using a xfx 750 nvidia card for El Capitan. No problems when using the nvidia web package. Had to use nv_disable before installing the driver though.

It might help people if you mention the unraid version when posting problems. Has anyone seen an improvement with 6.2 beta in terms of choppiness etc?

You need to determine your own settings, unless you have exactly the same setup as I do. I'm using 2 of the the $65 8-core 16-thread Xeon E5-2670s Brit, do you mind performing a test for me involving the dolphin emulator? On my e5 2660v3 with the emulator running a rom in in the background, if I lose focus of the emulator window and move the mouse around the desktop, the sound in the emulator starts to stutter quit badly. I'm convinced it's to do with cpu but want to be sure. This sound/performance issue is not repeatable on a bare metal install. Cheers.

6.2 beta is out. Hopefully this will fix some of the issues with stutter etc.

It worked! ty! Off to trying out gpu passtrough and cpu benchmarks. Good luck with that. I am holding out for 6.2. Whilst I dont have any GPU performance issues, I am unable to get my Xeon 2660V3 above 4 cores in a VM. Anything above 4 and I get lag and stutter all over the place.

The path to the OVMF file can be your share. I just used /boot/config as an example.