darianf

thanks for the good explanation dmacias. i think now it really makes sense to buy the ultra cheap small ssd, like 120 GB, and pass them entirely

If full disk is to be used by the VM, which is the preferred method? or what are the advantages of one method against the other? (performance, stability, etc..) Does it matter if it's ssd or standard HDD? Thanks -d

thanks now that you say it, i'm not confident if i already tried to dump while VM up, without unbind.. Will update quickly, once i try it out (hopefully today evening) Why the need? i have matx with x99, like you. So no IGP, and only 2 PCIe slots (actually 3, but last one is not usable to fit a GPU, since the matx case would not allow). I'm planning to run 2 VM's with both the GPU's passthrough. And, i want to put the 550ti in my first slot, because i plan to work it less (will have less airflow). Putting 1060 on second slot will give it access to fresh aiflow & will run cooler. -d

hi, this is a very good tutorial, thanks gridrunner for all the steps I was able to extract the rom for my zotac 1060 mini 3g card, no issues with it. But now i'm facing an issue with my evga 550ti 1gb, placed in second PCIe slot (with 1060 in first slot). If i just start the unraid box, without any VM auto running, and try the steps for rom creation (so lspci -v does not show that line with driver in use for vfio-pcie for 550 ti - device 02:00.0), i get: cat: rom: Input/output error Same happens if i start and stop the VM. If i keep the VM started (550ti in second slot passed through) - btw, only OVMF bios works - then lspci -v shows me that line with the driver in use. I try to unbind, but no luck (command hangs). Only if i stop the VM, then the command returns the prompt. I continue with the steps for rom dumping, but again i get cat: rom: Input/output error Somehting to note, after a start/stop attempt, the VM does not start anymore, due to some GPU invalid rom error - it asks to check dmesg for more info and i get "Invalid ROM" or somehting similar. Therefore I have to reboot the whole unraid box to make it start again. In short, I'm out of options for getting the rom for this 550ti, as i tried various options: 1) immidiately after box restart, VM never started since restart of box - input/output error 2) fresh box restart, VM started and then stopped - input/output error 3) fresh box start, while VM is online - unbind hangs. Then i stop the VM, unbind runs (actually not really sure if it runs, because no message is shown as output, iut just returns to the prompt) but the cat rom fails again with input/output error. All these after fresh restarts of the physical box... What to do next, what suggestion should i try? i see some ACS suggestion, but not sure if relevant or what exactly should i change (not familiar with the concept). Or should i buy another card instead of my old 550ti? any success with the low cost 710/720 cards? thanks -d

hi do you have any options in bios to control the mode of the pcie? (16x, 8x) i would play with that maybe something comes up. 550ti is pcie 2.0 16x (which is equivalent with pcie 3.0 8x) - maybe gpu too old for this motherboard? also read this info: https://lime-technology.com/wiki/index.php/UnRAID_Manual_6#Warning:_Passing_through_a_GPU_to_a_SeaBIOS-based_VM_will_disable_console_VGA_access So you might need to play with some settings, as you see in the wiki recommendations. One thing to note: i personally could not switch from ovmf to seabios once the VM was created (so this option to switch was enabled only up to machine creation, when defining it. Once it was created, i could not switch it, so i had to recreate again). i was not passingthrough any GPU though...

ok, i tried once again to create the VM, and this time i chose SeaBios. and... magic It worked without any issue... Problem with my previous troubleshooting attempts was that once the VM was created with default bios OVMF (and failed to start with the error in the original post) the option to change the bios was disabled. Now it's sorted out. hope this helps some other noobs

Without having the experience, i would say the GPU card is always powered, as long as the unRaid box is ON, regardless of the VM state. So fan should also be always on - of course, this assumes that you don't have one of those cards that are only kicking the GPU fans when temperature exceeds certain threshold. But maybe somebody confirms based on their real experience.

dear community I'm new to unRaid (i have latest version, 6.2) so please have patience with me. I have an old PC (dual core e8400 3GHz, asus x48 Rampage Formula with 8GB of ddr2) The CPU supports both vt-x and vt-d however the motherboard does not seem to support vt-d, but only vt-x (by enabling the vanderpool support option in bios). so far so good with unraid (enless options), and i was successfully able to create a VM machine with Ubuntu, access it via vnc, play a bit with the Ubuntu settings, but i haven't done yet something like a thorough testing to gain confidence that all is ok. But, when i'm trying to create a kali linux VM (v 2016.2), it fails to start with error: KVM internal error. Suberror: 1 emulation failure RAX=0000000000000016 RBX=0000000000000000 RCX=000000007e1ecff8 RDX=000000000000003f RSI=000000007e1ec838 RDI=000000007dfa9600 RBP=000000007dfa9600 RSP=000000007ff59af0 R8 =000000000001f800 R9 =000000007e1ec818 R10=00000000000000d4 R11=0000000000000200 R12=000000007dfa7180 R13=0000000000000000 R14=0000000000000000 R15=0000000000000000 RIP=00000000000b0000 RFL=00010217 [----APC] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =0030 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] CS =0038 0000000000000000 ffffffff 00a09b00 DPL=0 CS64 [-RA] SS =0030 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] DS =0030 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] FS =0030 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] GS =0030 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] LDT=0000 0000000000000000 0000ffff 00008200 DPL=0 LDT TR =0000 0000000000000000 0000ffff 00008b00 DPL=0 TSS64-busy GDT= 000000007fee67d8 00000047 IDT= 000000007f695018 00000fff CR0=80000033 CR2=0000000000000000 CR3=000000007fef8000 CR4=00000668 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400 EFER=0000000000000500 Code=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <ff> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff This is the startup command: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Tower LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'Kali Linux' -S -machine pc-q35-2.5,accel=kvm,usb=off,mem-merge=off -cpu host -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/15f44a5e-5947-4fc8-230c-3fb70bfcd4b5_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 3072 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 15f44a5e-5947-4fc8-230c-3fb70bfcd4b5 -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-Kali Linux/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device i82801b11-bridge,id=pci.1,bus=pcie.0,addr=0x1e -device pci-bridge,chassis_nr=2,id=pci.2,bus=pci.1,addr=0x1 -device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 -device ich9-usb-uhci1,mastet,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0 -vnc 0.0.0.0:0,websocket=5700 -k en-gb -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16,bus=pcie.0,addr=0x1 -device virtio-balloon-pci,id=balloon0,bus=pci.2,addr=0x4 -msg timestamp=on Domain id=18 is tainted: high-privileges Domain id=18 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) I tried playing with params like type of machine (i440fx vs q35) and cpu mode (host passthrough e8400 vs qemu64) but it does not change a thing. Also, when creating the VM, i tried with different templates - Debian, Linux, and Ubuntu - but it did not help. What i am doing wrong? thank you