Jim van der Harst

Till 30 march only $31.42. http://store.wdc.com/store/wdus/en_US/DisplayAccesoryProductDetailsPage/ThemeID.21986300/Accessories/WD_314GB_PiDrive/productID.335173200/categoryId.70262300 This drive is for the Raspberry!

I have the same problem to. Something to do with the boot order?

We got it working steady now. I posted my solution in an other threat. http://lime-technology.com/forum/index.php?topic=45530.msg440853#msg440853 Thank you al for your support. I'm still looking for the best way to select my processors and HT cores, cpu scheduling esxi wise.

Goodday KidCastro, it's two ways: CPU should support vt-x and vt-d and the motherboards as well. THere is a site that's lists the intel chipsets that support VT-d as VT-x is supported almost every motherboard. I'l show you the link: http://www.intel.com/content/www/us/en/support/boards-and-kits/desktop-boards/000005758.html?wapkw=vt-d+support The following Intel® Desktop Boards support Intel VT with Directed I/O: Chipset Desktop Board H87, Q87, Z87 DH87MC, DH87RL, DQ87PG B85 DB85FL X79 DX79SI, DX79SR, DX79TO H77, Q77, Z77 DH77DF, DH77EB, DH77KC, DQ77CP, DQ77KB, DQ77MK, DZ77BH-55K, DZ77GA-70K, DZ77RE-75K, DZ77SL-50K B75, Z75 DB75EN, DZ75ML-45K Q67 DQ67EP, DQ67OW, DQ67SW H61 DH61AGL Q57 DQ57TM, DQ57TML Q45 DQ45CB, DQ45EK Q35 DQ35JO, DQ35MP I dont see Z170 on that..... It's possible that the above list is outdated. Drop a question at ASRock support for the correct answer. If the manual says VT-d it probably will

In my case it was a syslinux.cfg problem.... and fixed with what Saarg said: vfio_iommu_type1.allow_unsafe_interrupts=1 default /syslinux/menu.c32 menu title Lime Technology prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append vfio_iommu_type1.allow_unsafe_interrupts=1 initrd=/bzroot

Agree on Saarg. I posted a solution about a similar problem: http://lime-technology.com/forum/index.php?topic=45530.0

MMmm first I thought I had the same problem but as you already addressed your cache is online but your data disk is not and the array is not started. Have you tried "Spin down and spin up " Also you can click the disks HTML link to get advanced settings. Hope this helps a bit . Jim

Checking my iso virtio-win-0.1.112 and I do see F:\viostor\w10 I have downloaded the Windows 10 iso now and setup the vdisk1.img to IDE then I can install Windows 10 without a problem. After the install I will add a second disk keep disk 1 on IDE and disk 2 on virtio. Install the F:\viostor\w10\amd64\viostor.inf (right mouse button --> Install. So I see two options: Change your XML for disk into IDE or get the proper iso with W10 drivers on it. Jim

I used the ISO : virtio-win-0.1.112 But that was after upgrading from Windows 8 Pro. Device Manager says: Driver date: 12/16/2015 Driver version: 62.73.104.11200 Downloading Windows 10 iso now....

I think you would have more succes to start with a Windows 8 installation and install all the virtual drivers. Then upgrade it to windows 10. Now I know this isn't what you wanted, so I am going to start and Windows 10 install my self now and see if I have the same problem. I think when you keep using IDE it will install and run the vm. I get back on this. Jim

Part 3. Getting virtio into your virtual machine You have installed Windows succesfully and want to change your IDE to VIRTIO. But when you do, you get the error "Your PC ran into a problem....... to restart". To fix this do the following: Edit the settings of your VM and add another disk to your VM. Assign not more then 1GB so you have a second disk in windows. Now remeber the warning I posted here earlier. After changing your VM through EDIT your XML is changed back to VIRTIO. This also applies to vdisk1.img. So after adding the extra disk, go into your EDIT XML and look for vdisk1.img settings again. Change the vdisk1.img back to "IDE" and delete the "address type...." line completely. Leave the VIRTIO setting and "address type..." line for vdisk2.img. Save and then start your VM. It will start and log into windows. Open your "virtio-win-0.1.112.iso" drive and install the following driver: F:\viostor\w8\amd64 Right click "viostor.inf" and select install. Normally this would be sufficient, I also did the following: Select all 5 files and copy them into C:\Windows\System32. Then copy the files "viostor.cat" and "viostor.inf" and paste them into "C:\Windows\Inf". Now reboot your VM. Go to your "Computer --> Properties" Select left column "Device Manager". Look for "Storage Controllers" and flip it open. You now should see "Red Hat Virtio SCSI controller". There is probablly just one and one "Microsoft Storage Spaces Controller". Now shutdown the virtual machine. Go into your EDIT XML and change the "vdisk1.img" to "virtio". Remove the "address type.... " line otherwise you end up unable to start your virtual machine as the device type doesn't match your disk. I hope this helps. Let me know if you need additional help. Meantime I managed to game with two games (pure because we can) and have 6 VM's now.

Part 2. VM configuration Before getting right to creating VM's and run your benchmarks... you should read this so you don't get disappointed. Installing a VM is realy going slow now. I only tried Windows 8 Pro from .iso file. There are two thing you need to know before you start your way into the "VMs" section. When you creat a VM the the .xml file of the VM will setup your harddisk controller as "virtio", like below: <source file='/mnt/user/vDisks/Desktop/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> To get normal installation speed change "virtio" to "ide". Remember when you change it to IDE, remove the address type line completly. So above example will look like: <source file='/mnt/user/vDisks/Desktop/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='ide'/> Now click "Save". You now have a VM that wants to start with the IDE driver instead of the virtio driver, which isn't there yet. IMPORTANT: WHEN YOU SAVE YOUR XML FILE AND YOU EDIT YOUR VM SETTINGS, THE XML FILE WILL SET IT BACK TO VIRTIO. That means, when you add another disk, put more CPU's or Memory or what ever change you do , even a "Cancel" will put the XML file back to VIRTIO, thus not getting the speed you want. So do your VM hardware configuration first (cpu, mem, disks, gfx, kvm) then adjust the XML from virtio to ide and ofcourse remove the whole address type line. You now can start the VM and install your Windows pretty fast.

Part 1. Syslinux.cfg configuration Ok here I am. I will put my config files here. First my hardware setup: Asus Rampage III Extreme 3 x HD 6970 (but also 2 x HD6970 and 1 boggus GFX) 12GB Mem Disk 1: 1 x 2TB Hitachi 7200RPM Cache: First started with OCZ Revo 120GB (unraid saw 2 x 60GB... there goes 1 license Cache: After getting OCZ Revo out brought back 2 x Samsung 850 Pro 256GB Boot: Data_Traveler USB 3.0 16GB Now the problem we (me and my friend) ran into was the error "Operation not permitted" after creating a VM and tried to start it. Creating the VM was not the problem, starting the VM gave "Operation not permitted". So we started looking and searching. And saw this post on the forum. Same error, same motherboard, no solution. Me and my friends are both professional in IT so we didn't accepted that and went on. I now can tell after succesfully installing, adding and customizing VM that the first error we resolved was all in the unRAID setup on the USB flash drive. I see you have VT-x and VT-d enabled in your bios just like we did. After reading different threats we tried several changes. Here is the "syslinux.cfg" file I now use: default /syslinux/menu.c32 menu title Lime Technology prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append vfio_iommu_type1.allow_unsafe_interrupts=1 initrd=/bzroot label unRAID OS Safe Mode (no plugins) kernel /bzimage append iommu=pt initrd=/bzroot append initrd=/bzroot unraidsafemode label Memtest86+ kernel /memtest The addition of "vfio_iommu_type1.allow_unsafe_interrupts=1" was getting pass our first error. The VM started but slow as hell. Took a whole night to install a Windows 8 Pro. I now manage that to do that under 6min. We first thought the marvell controller was giving us the error and added " iommu=pt" to the syslinux.cfg right behind "vfio_iommu_type1.allow_unsafe_interrupts=1". As IT professions you should know only one change at the time, we did to to "save" time and ended up waisting time We should have give it a go right after "vfio_iommu_type1.allow_unsafe_interrupts=1" and not add two parameters, but he we save you the extra time. So when the VM started we first thought.. that was the solution. After removing that but still have "vfio_iommu_type1.allow_unsafe_interrupts=1" in the syslinux.cfg it kept working. So that rendered "iommu=pt" out of the picture. Now go to the "Settings" tab and click "VM Manager". Set "PCIe ACS Override: NO" So far the syslinux.cfg explanatory. This still leaves me a very slow install of Windows 8 Pro but I'll address that in a reply here below. I want to split it up.

Yep, got it running now. It was the configuration of the unRAID server. It was an adjustment in the syslinux.cfg file. I manged to setup 3 VM's now with 3 x HD 6970 GFX's. I get back on this later.. work calling.

Well we got it working and it works pretty wel. What I notice is that when you do a GFX benchmark on two VM's the score is lower then doing the same on one VM. I thought the scores would probably end near to eachother because I thought the systems (GFX's) are working alone. So how come my GFX score is about 50% when doing a single VM GFX benchmark? I understand that there is always some lost in performance as you share the lanes on the motherboard and 1 CPU. Is this maybe a PCI-X lane issue? Or is it normal behaviour? Thank you in advanced. The config files an screenshots will follow this weekend for other users to use.