[Unraid OS version 6.8.0-rc5 available]

I am running a VM as a Q35-4.1 machine in RC4. Do I need to do anything to the VM prior to moving to RC5?

 

What was the reason to reverting to qemu 4.01?

 

Thank you!

[[6.7.x] Very slow array concurrent performance]

I have learned that this issue only effects me when my 1GBit connection is maxed out and writing to disk for about 20 seconds after which point every VM and docker grinds to a halt. Then after about another 20 seconds things start to resume and if the network activity is not complete this process repeats. I still have $100 on the table for when this is fixed. When 6.8 is fully released (Not RC) and fixes this issue, where can I donate to unraid?

 

Thank you,

[[6.7.x] Very slow array concurrent performance]

I want to add my hat into the list of people experiencing this issue with 6.7.x. I have run down what seems like every rabbit hole trying to fix the problem thinking it was related to a CPU pinning or isolation issue. I wish I had found this post sooner. There should be a list of known ongoing problems linked to the Unraid dashboard.

 

I know Unraid runs very barebones as a company, but this seems like an urgent issue. Indeed, Unraid is not that expensive, but I have come to rely on it more and more. I think it should be priced higher and even have an ongoing monthly fee to fund a higher level of development work.

 

Therefore, also mark me down as someone willing to pay for a higher level of support and development and premium features. Unraid was born out of a group of people who wanted something better and now is going more mainstream to less technically savvy people. This issue has been extremely troublesome to me, and I have spent so much time on it that I will donate $100 to whoever proves they find the fix.

[[6.6.5] internal error: PCI host devices must use 'pci' address type]

I experienced this same error on 6.6.1. I had to recreate the VM by first creating a new Windows 10 VM and then copying over the old XML and relinking the image. The new VM with the same XML did not yield the error which I did not understand. 2 VMs with the same XML. One would start, and the other would give the error below.

 

This is a detail of my post from Sept. 29th. -->