• Content Count

  • Joined

  • Last visited

Community Reputation

4 Neutral

About Darkun1

  • Rank


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I moved off of 6.2.4 as I had similar issue and I think for a lack of a better word a memory leak with that version. I would watch UNRAID eat up every bit of available memory then shutdown my VM's because it ran out of memory. I made the jumped to 6.3.5 and currently on 6.3.6 and the issue has gone away for me and might help to move off of 6.2.4
  2. That looks correct but I am not sure if you just had a typo in your post for <emulatorpin cpuset='0-12,1-3'/> it should look like <emulatorpin cpuset='0-12,1-13'/> For the isolcpus=2,3,4,5, 6,7, 14,15,16,17,18,19 you are only telling UNRAID to ignore those CPU but it still has access to 8,9,10,11,20,21,22,23 and that's ok just an FYI
  3. Sorry for the late reply - been a busy day. Looks like the west coast fiber backbone is having issue causing sub optimal routing and I have been swamped with customers having connection problems. I did take a look at the link and it looks to have some good information and hopefully I can do some testing this weekend. Thanks for your time
  4. I was wondering if the turbo boost's on Intel CPU's works in a VM environment? I am guessing no as I have not seen my CPU boost up to 3.8GHz but constantly shows the base speed of 3.5GHz; I am feeling lazy and getting over the flu to do much research and thought I ask. I want to say my BIOS gave me an options to run my CPU at max frequency all the time but I will have to double check that feature. Any harm in running the CPU at max turbo frequency if that is an option in the BIOS? It's base speed is fine with me, just was wondering. http://ark.intel.com/products/82765/Intel-Xeon-Processo
  5. Sorry if this comes across wrong - try a different keyboard?
  6. Sorry if I confuse you but here it goes - Because you have a lot of threads but at a slower speed @ 2.2 GHz and not 100% sure what you are wanting to do with your VM or will want more than 1 VM I may try setting it up like so, see screenshot Red outline give to UNRAID - might want to give more to UNRAID if you are going to use Dockers. Yellow = VM1 and would give it 6 physical cores to access just because of the 2.2 GHz range may want to give it more Green = VM2, same idea as VM1 Orange = all to VM 1 because you have the threads to do so if you want just one VM and because of t
  7. Here is a screenshot of your motherboard layout for the PCI\PCI-E - not that its much help, I just like screenshots
  8. Can you post what hardware you are using please. Looking at how many vCPU's you have I am guessing it is a quad core with HT and just my recommendation I would use a minimum of a 6 core with HT but at 3.0 GHz or faster. Fewer but faster cores or slower but many cores You will want to try and give UNRAID CPU 0 and 4, and hide all other cores from UNRAID for VM assignment using the isolcpus=1,2,3,5,6,7 You could try different ways to assign your vCPU to your VM's 1. Give gaming VM CPU 1,5,2,6 and the work VM CPU 3,7 2. Give gaming VM CPU 1,2,3 and work VM CPU 5,6,7 Mig
  9. I just did some more testing on my system and the results I got are the following when modifying the BIOS PCI-E downstream between Gen 1,2, and 3 for the USB 3.0 card(s) I own. Gen 1 works flawlessly so far when passing the USB cards to the VM's however I believe I loose about half my speed of USB 3.0 but I am still getting in theory 250Mbs and still meets my needs currently. Gen 2 works ok, when I reboot the VM's they fail to come back online most of the time and I have to force stop them and back on and every once in awhile I have to reboot the UNRAID server to get the VM running a
  10. Try using this plugin for UNRAID, it was really nice to use from time to time to passthrough USB flash drive or external drive to the running VM when I was having issues passing through a USB controller to a VM for true plug n play http://lime-technology.com/forum/index.php?topic=47240.0
  11. I have two VAI chipset PCI-e USB 3.0 controllers that do something similar to what you are experiencing. I have been holding off on buying a new USB PCI-e card however I believe I have solved my issue and it may work for you. Inside my BOIS I have set the PCI express slots that the USB cards are in from auto to GEN 1 and I can pass-through both of my cards to each gaming VM and it works like a dream... so far. No more freeze up, lockups, or get stuck on VM reboots causing me to reboot the UNRAID server and the UNRAID server has been running for 3 days now. I am still in testing mode
  12. Sorry for the confusion - you shouldn't need to create a dword so you might be able to delete that, my "MSISupport" was already there and just needed to modify it from 0 to 1. The reason why I outlined both in orange is because I believe both are related to my one video card and one of the two is the HDMI audio part of the video card that I needed to modify. Your card might be a little different as I am running a 960. I could be wrong about the two I have outlined in orange however I know the first orange outline is the one I modify for my system. You can probably ignore the bottom orange
  13. That should fix your audio issue, you are going to want to find your Video card \ HDMI audio in your Windows registry and change the MSI from 0 to 1. You can follow the path from my screenshot but your video card \ HDMI audio might be named different.
  14. Looking at your screenshot and going off how I do my pinning but I don't have as many core's or dual CPU but I would try something like this and look at the screenshot I attached isolcpus=2,3,4,5,6,7,10,11,12,13,14,15,18,19,20,21,22,23,26,27,28,29,30,31 Red = CPU for UNRAID VM1 = Green and add this to the VM template <emulatorpin cpuset='0,1,16,17'/> VM2 = Blue and add this to the VM template <emulatorpin cpuset='0,1,16,17'/> VM3 = Orange and add this to the VM template <emulatorpin cpuset='8,9,24,25'/> VM4 = Yellow and add this to the VM template
  15. I was more suggesting remove anything pass-through, and or anything that was manually configured in the VM templet just to see if the VM boots in to Windows. If so, slowly start adding your pass-through devices and custom configuration edits for the VM templet. Might be easer creating a new but temporary VM templet and point it to the Windows 10 disk but don't pass-through or manually edit the VM, leave it as it's default and then try to VNC in to it. Sorry for the stupid suggestions but some times it helps going back to square one, might also be a Windows 10 issue, maybe something