patthe Posted January 14, 2016 Share Posted January 14, 2016 Hi When I try ro activate my 3d card, and start my windows vm I have this error : internal error: early end of file from monitor: possible problem: 2016-01-14T01:23:55.994442Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to set iommu for container: Operation not permitted 2016-01-14T01:23:55.994473Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to setup container for group 15 2016-01-14T01:23:55.994482Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 15 2016-01-14T01:23:55.994499Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed 2016-01-14T01:23:55.994510Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized I DO HAVE I IOMMU activated Model: UnRaid Server M/B: ASUSTeK Computer INC. - Rampage III Extreme CPU: Intel® Core™ i7 CPU 930 @ 2.80GHz HVM: Enabled IOMMU: Enabled Cache: 256 kB, 1024 kB, 8192 kB Memory: 12288 MB (max. installable capacity 24 GB) Network: eth0: 1000Mb/s - Full Duplex Kernel: Linux 4.1.13-unRAID x86_64 OpenSSL: 1.0.1p Quote Link to comment
bungee91 Posted January 14, 2016 Share Posted January 14, 2016 Sounds like you have another device in group 15 that you're not passing to this VM. Quote Link to comment
patthe Posted January 14, 2016 Author Share Posted January 14, 2016 How can I fix this? Quote Link to comment
jonp Posted January 14, 2016 Share Posted January 14, 2016 Try moving the card to a different PCI slot and see if that works, if not, you can try enabling the pcie ACS Override under Settings > VM Manager Quote Link to comment
patthe Posted January 14, 2016 Author Share Posted January 14, 2016 Ok I try enabling ACS Overide in setting now it change the error to group 17. internal error: early end of file from monitor: possible problem: 2016-01-14T13:09:24.513367Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to set iommu for container: Operation not permitted 2016-01-14T13:09:24.513395Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to setup container for group 17 2016-01-14T13:09:24.513403Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 17 2016-01-14T13:09:24.513412Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed 2016-01-14T13:09:24.513422Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized Will try to change the card to a different port later on. Quote Link to comment
patthe Posted January 15, 2016 Author Share Posted January 15, 2016 Hi, So I cannot move my video card ( Use 3 slot ), so what other option do I have ? server-diagnostics-20160114-2006.zip Quote Link to comment
jonp Posted January 15, 2016 Share Posted January 15, 2016 Your logs tell me all I need to know: Jan 14 19:57:05 Server kernel: ------------[ cut here ]------------ Jan 14 19:57:05 Server kernel: WARNING: CPU: 0 PID: 1 at drivers/iommu/intel-iommu.c:4744 init_dmars+0x258/0x454() Jan 14 19:57:05 Server kernel: Your BIOS is broken; DMA routed to ISOCH DMAR unit but no TLB space. Jan 14 19:57:05 Server kernel: BIOS vendor: American Megatrends Inc.; Ver: 1502 ; Product Version: System Version Jan 14 19:57:05 Server kernel: Modules linked in: Jan 14 19:57:05 Server kernel: CPU: 0 PID: 1 Comm: swapper/0 Tainted: G I 4.1.13-unRAID #1 Jan 14 19:57:05 Server kernel: Hardware name: System manufacturer System Product Name/Rampage III Extreme, BIOS 1502 10/03/2011 Jan 14 19:57:05 Server kernel: 0000000000000009 ffff880331137d38 ffffffff815f12b0 0000000000001d6e Jan 14 19:57:05 Server kernel: ffff880331137d88 ffff880331137d78 ffffffff8104775b ffff880330dd0000 Jan 14 19:57:05 Server kernel: ffffffff818d6767 ffff880330f54000 0000000000000000 ffff880330f6a780 Jan 14 19:57:05 Server kernel: Call Trace: Jan 14 19:57:05 Server kernel: [<ffffffff815f12b0>] dump_stack+0x4c/0x6e Jan 14 19:57:05 Server kernel: [<ffffffff8104775b>] warn_slowpath_common+0x97/0xb1 Jan 14 19:57:05 Server kernel: [<ffffffff818d6767>] ? init_dmars+0x258/0x454 Jan 14 19:57:05 Server kernel: [<ffffffff810477b6>] warn_slowpath_fmt+0x41/0x43 Jan 14 19:57:05 Server kernel: [<ffffffff818d6767>] init_dmars+0x258/0x454 Jan 14 19:57:05 Server kernel: [<ffffffff818d6bf8>] intel_iommu_init+0x295/0x585 Jan 14 19:57:05 Server kernel: [<ffffffff818ac2a8>] pci_iommu_init+0x13/0x3e Jan 14 19:57:05 Server kernel: [<ffffffff818ac295>] ? memblock_find_dma_reserve+0x146/0x146 Jan 14 19:57:05 Server kernel: [<ffffffff81002145>] do_one_initcall+0xe9/0x178 Jan 14 19:57:05 Server kernel: [<ffffffff818a405d>] kernel_init_freeable+0x17c/0x204 Jan 14 19:57:05 Server kernel: [<ffffffff818a3807>] ? initcall_blacklist+0xa5/0xa5 Jan 14 19:57:05 Server kernel: [<ffffffff815e4585>] ? rest_init+0x89/0x89 Jan 14 19:57:05 Server kernel: [<ffffffff815e458e>] kernel_init+0x9/0xd5 Jan 14 19:57:05 Server kernel: [<ffffffff815f6d92>] ret_from_fork+0x42/0x70 Jan 14 19:57:05 Server kernel: [<ffffffff815e4585>] ? rest_init+0x89/0x89 Jan 14 19:57:05 Server kernel: ---[ end trace 577486b93363598b ]--- Jan 14 19:57:05 Server kernel: IOMMU: hardware identity mapping for device 0000:00:1b.0 Jan 14 19:57:05 Server kernel: IOMMU: Setting RMRR: Jan 14 19:57:05 Server kernel: IOMMU: Setting identity map for device 0000:00:1a.0 [0xbf7dc000 - 0xbf7dbfff] Jan 14 19:57:05 Server kernel: ------------[ cut here ]------------ Jan 14 19:57:05 Server kernel: WARNING: CPU: 0 PID: 1 at drivers/iommu/intel-iommu.c:2380 iommu_prepare_identity_map+0xd2/0x1a0() Jan 14 19:57:05 Server kernel: Your BIOS is broken; RMRR ends before it starts! Jan 14 19:57:05 Server kernel: BIOS vendor: American Megatrends Inc.; Ver: 1502 ; Product Version: System Version Jan 14 19:57:05 Server kernel: Modules linked in: Jan 14 19:57:05 Server kernel: CPU: 0 PID: 1 Comm: swapper/0 Tainted: G W I 4.1.13-unRAID #1 Jan 14 19:57:05 Server kernel: Hardware name: System manufacturer System Product Name/Rampage III Extreme, BIOS 1502 10/03/2011 Jan 14 19:57:05 Server kernel: 0000000000000009 ffff880331137cd8 ffffffff815f12b0 0000000000001ef0 Jan 14 19:57:05 Server kernel: ffff880331137d28 ffff880331137d18 ffffffff8104775b 00000000bf7dbfff Jan 14 19:57:05 Server kernel: ffffffff815f23a6 ffff880330f6a900 00000000bf7dbfff ffff880330f66098 Jan 14 19:57:05 Server kernel: Call Trace: Jan 14 19:57:05 Server kernel: [<ffffffff815f12b0>] dump_stack+0x4c/0x6e Jan 14 19:57:05 Server kernel: [<ffffffff8104775b>] warn_slowpath_common+0x97/0xb1 Jan 14 19:57:05 Server kernel: [<ffffffff815f23a6>] ? iommu_prepare_identity_map+0xd2/0x1a0 Jan 14 19:57:05 Server kernel: [<ffffffff810477b6>] warn_slowpath_fmt+0x41/0x43 Jan 14 19:57:05 Server kernel: [<ffffffff815f23a6>] iommu_prepare_identity_map+0xd2/0x1a0 Jan 14 19:57:05 Server kernel: [<ffffffff818d67fd>] init_dmars+0x2ee/0x454 Jan 14 19:57:05 Server kernel: [<ffffffff818d6bf8>] intel_iommu_init+0x295/0x585 Jan 14 19:57:05 Server kernel: [<ffffffff818ac2a8>] pci_iommu_init+0x13/0x3e Jan 14 19:57:05 Server kernel: [<ffffffff818ac295>] ? memblock_find_dma_reserve+0x146/0x146 Jan 14 19:57:05 Server kernel: [<ffffffff81002145>] do_one_initcall+0xe9/0x178 Jan 14 19:57:05 Server kernel: [<ffffffff818a405d>] kernel_init_freeable+0x17c/0x204 Jan 14 19:57:05 Server kernel: [<ffffffff818a3807>] ? initcall_blacklist+0xa5/0xa5 Jan 14 19:57:05 Server kernel: [<ffffffff815e4585>] ? rest_init+0x89/0x89 Jan 14 19:57:05 Server kernel: [<ffffffff815e458e>] kernel_init+0x9/0xd5 Jan 14 19:57:05 Server kernel: [<ffffffff815f6d92>] ret_from_fork+0x42/0x70 Jan 14 19:57:05 Server kernel: [<ffffffff815e4585>] ? rest_init+0x89/0x89 Jan 14 19:57:05 Server kernel: ---[ end trace 577486b93363598c ]--- Jan 14 19:57:05 Server kernel: IOMMU: mapping reserved region failed Jan 14 19:57:05 Server kernel: IOMMU: Setting identity map for device 0000:00:1a.1 [0xbf7dc000 - 0xbf7dbfff] this continues for a while... I would suggest procuring a higher-quality motherboard, but here's one other thing you can try to overcome this, but I make no guarantees for system stability given these errors messages on your motherboard (and this also may result in some degraded performance as compared to without this): Goto Main and click Flash to get to the Flash Device Settings Page. Locate the Syslinux Configuration Section Find and edit this section (add what I have bolded below): label unRAID OS menu default kernel /bzimage append iommu=pt pcie_acs_override=downstream initrd=/bzroot unraidsafemode Apply that change and reboot your system. Give it a whirl. You could also try looking to see if your motherboard has a BIOS update available. Quote Link to comment
patthe Posted January 15, 2016 Author Share Posted January 15, 2016 Hi, dont seem too work, still got the same error. Sucks because this is a Gaming Board, use for server now. Just wish this would work. I just wonder if I could change something else in the bios? I have a lots of option in it as it is a gaming board. I verify and I have the latest bios available for my board . Quote Link to comment
Jim van der Harst Posted January 21, 2016 Share Posted January 21, 2016 We managed to get the Asus Rampage III Extreme to work. I will post configuration files and screenshots later ones all is re-installed again. Quote Link to comment
patthe Posted January 22, 2016 Author Share Posted January 22, 2016 Ok let me know Quote Link to comment
patthe Posted January 29, 2016 Author Share Posted January 29, 2016 We managed to get the Asus Rampage III Extreme to work. I will post configuration files and screenshots later ones all is re-installed again. Any Luck ?? Quote Link to comment
Jim van der Harst Posted January 29, 2016 Share Posted January 29, 2016 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. Quote Link to comment
patthe Posted January 30, 2016 Author Share Posted January 30, 2016 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. Ok let me know With instructions on how too fix it would be awsome Quote Link to comment
Jim van der Harst Posted January 31, 2016 Share Posted January 31, 2016 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. Quote Link to comment
Jim van der Harst Posted January 31, 2016 Share Posted January 31, 2016 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. Quote Link to comment
Jim van der Harst Posted January 31, 2016 Share Posted January 31, 2016 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. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.