Bytales

I have managed to make the text scroll on the tv, which is connected to the onboard VGA. I used Bios Version F06, which is the last bios that has the ability to allow onboard VGA as enabled. I also made the Unraid Memory stick by downloading the ISO, extracting it, and with the "make bootable bat" i made it bootable. I also enabled, boot mode Legacy in the Motherboard. Previously, i had made the Unraid Memory stick with the Executable launcher that downloaded the iso, and i had always checked Bios UEFI. The Motherboard bios booting mode had also been set to UEFI. However, i still couldnt get both machines to start. Only one i could get it to boot the Windows ISO, the other one had no Image on the Monitor. After that i played with ProxMox, and while attemtping to manually enable IOMMU and add a PCI device, i had notied the following: Both my GPUs have the same device ID. Could this be the reason why i cant get two different VMs to run, each getting one of These two VGA ? I could get two VMs to boot, one with a VEGA Card, and one with the Geforce Titanium 750, and i assumed it was a matter of PCI express Placement. Which is why i got a PCI express extender, and tested with that as well. with the upper VEGA connected to the 4th PCI Slot instead of the 5th. Because i noticed in the original LinusTechTips Video, he had two different GPUs, and mentioned different brands of mice and Keyboards.

I see. Recently the unraid gui option dissapeared from my boot menu, and i remade the memory stick.

So if i can browse the Internet with Sound in 4k@60fps with the AMD Drivers installed within the unraid GUI, and while not doining it, leave the Card to mine, it would probably be worth it to spend 150 eur. Otherwise not. So please let me know if such a Scenario is possible.

Due to how my Motherboard is consturcted, i Need to populate the Motherboard 5th Slot with a low end GPU Card. Regardless of bios Settings, the gpu sitted here is what Unraid will use for itself. So im in the market for a new GPU, that must be single Slot; this will allow me to use the Motherboard 6th pci Slot as well. Im going to be connecting a 4k TV to this Single Slot Graphic Card, and i have some questions i couldnt find answer for anywhere. 1)If i will boot Unraid Gui, (will then UNRAID use the GPU to Display ist gui?), ive seen the unraid gui basically has a Mozilla browser built in. Would i be able to use the UNRAID GUI in 4k@60 fps, and use all the Features one would expect from a normal browser, like YouTube, Videos, Music? etc, as if i were using a browser in a normal Windows/Linux enviroment ? The GPU supposedly has also a Sound Card built in. And Sound would be transmited through HDMI to TV 2)Would i be able from this Unraid GUI to install Radeon pro Drivers for the Video Card, and use it to mine crypto ? from within the unraid GUI console ? Provided all the mining programs are on the boot Memory stick ? And i would acces them with the console. If all this would be true, i would then get an AMD WX 3100 Card, which has 4k60fps Support through its DP ports (i would Need a HDMI Adapter), and i could use the unraid gui to browse web, and the Card set to mine Crypto. If None of this would be possible, i would get a dummy Card. But i would at least want to have proper 4k Support in the gui, for at least browsing in moziila text based Websites, at least.... I want to know because the Card is aprox 150EUR, i dont want to throw 150EUR just for something i wont use, i would be better off spending only 30 only a less speced single Slot Card.

I even tried the VBios Trick, still no results. I am all left out of ideeas. I have mailed SpaceInvaderOne, perhaps he can figure something out. Also im putting a bounty of 25000 MUTEX up, payed in full to whoever figures out hte working solution More on MutexCurrency here https://mutexcurrency.io/ Here is the announcement i made on our Discord Chanell.

According to the Manual My Vega Cards are in slot PCIE_3(No.37) and PCIE_1(No.35). Geforce Titanium is in slot PCIE_5(No.39) So chosing "Legacy VGA" in Bios with external and Slot Number 3, would have chosen the Frontier Card. But i have tried again with slot number 5. Same thing. Unraid is hell bent on Using the Cadin PCIE_3 as its own. I dont think there can be a fix for this. Its probably the way the Motherboard is created internaly, could that be it ?

Only way i can trick Unraid not to use the card and have its boot text appear scrolling on the big tv (connected to either the geforce titanium or the onboard VGA) is by disconnecting the cable from the upper frontier card. But if i connect the cable afterwards, and create a VM with the Frontier card, im not getting any image afterwards. So it seems a cable must be connected to the Frontier card from the get go, which, if it happens prompts unraid to take the card for itself, then i cant use it for the VM. What an utter shit !

Updates. There is an option in the bios, called, Legacy VGA, but its empty. THis is on the latest Bio F10. Lucky i can update the bios through the IPMI, so i went to F06 i had before unraid. With F06, the Option of "Legacy VGA" is not empty any more, and i can change to auto, onboard, external, and when external, i need to input slot. I tried with onboard. Text still scrolls on the monitor connected to the Upper Frontier on the 5th PCI Slot. I tried with External, and set it to slot 3, where the Geforce 750 titanium sits. Text still scrolls on the Upper Frontier Card. As long as text scrolls on this card, i cant use it for the VM. Making a VM with the other card, or evne with the geforce 750titanium card, works. But so long as the Upper Frontier card is selected for the VM, it just doesnt work. Bios F09 and F10, the "Legacy VGA Option is empty". F06 is not empty. I can still try other Bioses. But it looks like Unraid is hell bent on taking this Frontier card for himself, no matter what. ANd the problem is Slots 5 and 7 are the only slots where i can install the said cards. Unless i could somehow connect the frontier card to the upper PCI slots, through some sort of external enclosure. I still need to see how Unraid reacts to having in the sistem, those usb graphic adapters. Is there no way to force unraid by commad to use a certain Graphics Adapter ?

I noticed they are listed in this order because of how they are grouped in the IOMMU groups, and here lies the key to my situation. Group 61 ASPEED Group 64 Upper Frontier Group 82 Geforce Titanium Group 85 Lower Frontier I need to somehow reshuffle them !

Installing a Geforce 750 titanium make the First Frontier Card, still sit at the second place, and when botting up unraid, i still get text scrolling on the Monitor connected to this card. It seems unraid is hell bent in using it for himself. Ill try ACS ovveride perhaps theyere going to be arranged differently.

Im planing to get something like this and insert something like this This has a HDMI and 2 USB slots, so i could conenct a mouse and keyboard, that i could thus use exclusivly for managing UNRAID. Will this be seen as a graphics adapter ? I have a spare 750ti since like forever, going to install it, and see how the system behaves. I would rather have the above components, since they will be located on the outside, and will allow me through the ports to controll the unraid consolle, without needing to use the mouse and keyboards assigned to the VM. Curious, how the system doesnt take the onboard video as it should. If there was a way to bind Unraid to use the onboard graphics, by specifing exactly to use the onboard card, it would be much easier. I think you should create this option for future versions.

i need to hardcode somehow to make unraid use the onboard vga. You can clearly see there are 3 cards in the system when assigning the cards to the windows VM. I m asking, if the Onboard card is used by Unraid, isnt then suppose NOT to appear on the list of selecteble graphics cards for the VM ? The card has its own IOMMU group And the Vegas are also in different groups themselves.

It is a VGA port, and i have a VGA to HDMI adapter to connect to the TV. When the TV is thus connected, when booting, text appears rolling on both the TV and on the monitor connected to the first AMD Vega card. BUt the text is different. THere is no setting in motherboard bios to enable by default. I could replicate the above photo, only when the TV is disconnected though, which seems strange. Wide monitor boots iso, the other one cant.

Isnt there a way to edit the Syslinux configuration to make Unraid use specifically the onboard graphics ? Or to deny it the Vega Frontier Cards ? Ill take a look in bios see if i can find anything

Yeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees this was it. Unraid uses the upper frontier edition for itself it seems, when trying to create a vm passing through this card it wont work, i created a vm using the second card, and it from within the uefi bios i booted the win iso and it loaded it. SO it seems unraid is using one the upper frontier edition for itself, even if im accesing it through a gui ui. Now the next problem is to figure out, how to give unraid the onboard video, if it can use it at all, and if not i need to put a gpu in the first slot. It seems Unraid uses what ever gpu is inserted first, or how is it exactly functioning ? I thought Unraid was suppose to use my onboard GPU ! Is there any way to force Unraid to use it somehow, writing a line somewhere ? If i can figure this out, everything checks out finally, Holy damn !, it took me a while of fussin around. 1 Week to be more precise. Notice how the left monitor has the text on it, that is connected to first card, and it seems it is being used by unraid. Creating the VM with the second card connected to the wide monitor, worked, and i managed to start the windows iso.

From the topic where someone had trouble passing in a 750 titanium Jonp said Quote: You need to make sure that graphics are output using the on-board graphics for the unRAID console. If you are seeing the console on the NVIDIA GPU, that's your problem. End of Quote My unraid starts using the first option on its menu, and i acces is from the web console from another computer on the network ! Now i realize when i start Unraid, allthough i get image on the tv connected to the onboard card, the monitor connected to the GPU im trying to pass through, also has some text on it, does this mean unraid is using this GPU im trying to pas through to the vm, to itself (the amd vega card) ? If that indeed is the case it explains why perhaps the vm doesnt function proprly ! THe question is, when is the vm starting to use the passed through GPU ? when the windows iso boots and loads ?, or it starts using it even with displaying the bios ? ?

Here is what i learned Starting the VM with VNC works, and starts by bringing me in the uefi bios, presumably because the key is not pressed to resume booting from "CD". Once in uefi bios i type exit, i get in some sort of bios, there, i choose the first quemu CDrom, and that is the iso upon which it boots. Starting the VM with the video card has mixed results, but i managed with the video card to get me into uefi shell. I type exit, get into the bios, and choosing that same CDrom (where the iso is mounted), cannot lunch the boot sequence. As if the drive where the windows 10 iso is cant lunch. I disconnected one GPU, and with a single gpu, i get the same results, so the cloned gpus arent it. My bios is OVMF and machine type is i440fx-3.0. TRying SeaBios, gets me a black screen. So i tried doing the mount drives as sata, SCSI or USB, same thing. Opening the logs for the VM gets me this 2018-09-28T19:37:05.553176Z qemu-system-x86_64: vfio_region_write(0000:46:00.0:region0+0x526d8, 0x0,8) failed: Device or resource busy 2018-09-28T19:37:05.553191Z qemu-system-x86_64: vfio_region_write(0000:46:00.0:region0+0x526c0, 0x0,8) failed: Device or resource busy 2018-09-28T19:37:05.553203Z qemu-system-x86_64: vfio_region_write(0000:46:00.0:region0+0x526c8, 0x0,8) failed: Device or resource busy 2018-09-28T19:37:05.553218Z qemu-system-x86_64: vfio_region_write(0000:46:00.0:region0+0x526b0, 0x0,8) failed: Device or resource busy 2018-09-28T19:37:05.553231Z qemu-system-x86_64: vfio_region_write(0000:46:00.0:region0+0x526b8, 0x0,8) failed: Device or resource busy 2018-09-28T19:37:05.553267Z qemu-system-x86_64: vfio_region_write(0000:46:00.0:region0+0x526a0, 0x0,8) failed: Device or resource busy 2018-09-28T19:37:05.553284Z qemu-system-x86_64: vfio_region_write(0000:46:00.0:region0+0x526a8, 0x0,8) failed: Device or resource busy 2018-09-28T19:37:05.553325Z qemu-system-x86_64: vfio_region_write(0000:46:00.0:region0+0x52690, 0x0,8) failed: Device or resource busy 2018-09-28T19:37:05.553341Z qemu-system-x86_64: vfio_region_write(0000:46:00.0:region0+0x52698, 0x0,8) failed: Device or resource busy 2018-09-28T19:37:05.553362Z qemu-system-x86_64: vfio_region_write(0000:46:00.0:region0+0x52680, 0x0,8) failed: Device or resource busy 2018-09-28T19:37:05.553380Z qemu-system-x86_64: vfio_region_write(0000:46:00.0:region0+0x52688, 0x0,8) failed: Device or resource busy 2018-09-28T19:37:05.553396Z qemu-system-x86_64: vfio_region_write(0000:46:00.0:region0+0x52670, 0x0,8) failed: Device or resource busy 2018-09-28T19:37:05.553408Z qemu-system-x86_64: vfio_region_write(0000:46:00.0:region0+0x52678, 0x0,8) failed: Device or resource busy 2018-09-28T19:37:05.553424Z qemu-system-x86_64: vfio_region_write(0000:46:00.0:region0+0x52660, 0x0,8) failed: Device or resource busy 2018-09-28T19:37:05.553437Z qemu-system-x86_64: vfio_region_write(0000:46:00.0:region0+0x52668, 0x0,8) failed: Device or resource busy 2018-09-28T19:37:05.553452Z qemu-system-x86_64: vfio_region_write(0000:46:00.0:region0+0x52650, 0x0,8) failed: Device or resource busy 2018-09-28T19:37:05.553465Z qemu-system-x86_64: vfio_region_write(0000:46:00.0:region0+0x52658, 0x0,8) failed: Device or resource busy 2018-09-28T19:37:05.553487Z qemu-system-x86_64: vfio_region_write(0000:46:00.0:region0+0x52640, 0x0,8) failed: Device or resource busy 2018-09-28T19:37:05.553501Z qemu-system-x86_64: vfio_region_write(0000:46:00.0:region0+0x52648, 0x0,8) failed: Device or resource busy 2018-09-28T19:37:05.553517Z qemu-system-x86_64: vfio_region_write(0000:46:00.0:region0+0x52630, 0x0,8) failed: Device or resource busy Only pasted the last lines Is this the fail message why i cant load the windows 10 iso when making the VM with the video card ? Is there any other way to make the boot medium mount in the vm ? Somehow using the VideoCard interferes with the system ability to properly boot the WIndows ISO. Perhaps i can mount or passthrough the physical DVD rom, and make a bootable cdrom that could boot from the cdrom, that could work. The way i see it, the ISO cannot load when i make the VM using the video card. Perhaps i can mount the GPU in another way, by modifying the XML file, <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='4'> <name>Windows 10</name> <uuid>d122b979-98f6-286c-bb73-bac9e5375f21</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>17</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='8'/> <vcpupin vcpu='2' cpuset='40'/> <vcpupin vcpu='3' cpuset='9'/> <vcpupin vcpu='4' cpuset='41'/> <vcpupin vcpu='5' cpuset='10'/> <vcpupin vcpu='6' cpuset='42'/> <vcpupin vcpu='7' cpuset='11'/> <vcpupin vcpu='8' cpuset='43'/> <vcpupin vcpu='9' cpuset='12'/> <vcpupin vcpu='10' cpuset='44'/> <vcpupin vcpu='11' cpuset='13'/> <vcpupin vcpu='12' cpuset='45'/> <vcpupin vcpu='13' cpuset='14'/> <vcpupin vcpu='14' cpuset='46'/> <vcpupin vcpu='15' cpuset='15'/> <vcpupin vcpu='16' cpuset='47'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-3.0'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/d122b979-98f6-286c-bb73-bac9e5375f21_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='17' threads='1'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/VIDisks/Windows 10/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISOs/Windows10.iso'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <alias name='sata0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISOs/virtio-win-0.1.160-1.iso'/> <backingStore/> <target dev='hdb' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xd'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:3f:58:e6'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-4-Windows 10/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x46' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0b05'/> <product id='0x1857'/> <address bus='5' device='5'/> </source> <alias name='hostdev1'/> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1e7d'/> <product id='0x2e7d'/> <address bus='5' device='4'/> </source> <alias name='hostdev2'/> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>

should i have chosen the sound card from the GPU as well ? it is there alright !

Ive read that Unraid needs a video card itself, to load, so i have a built into the motherboard ASPEED graphics card. Shouldnt this graphics card be unasignable when creating the VM ?

I have this installed in the first PCI express Slot of the Motherboard, but it is not being detected by unraid, i cnat see it anywhere. Perhaps i should Change it from the first Slot ? https://www.gigabyte.com/Motherboard/GC-WB1733D-I-rev-10#ov

I will try making a vm passing the VNC for Video Card. But today i woke up, and i have new ideeas. I have a pci express wifi Card in the first Motherboard Slot, that doesnt appear anywhere being recognized. Ill take that out, and try without it. Also it occured to me, that i have one device that is basically a clone of itself, and that is the Video Cards. i basically have two Vega frontier Edition watercooled Version, i wonder if that is a Thing for unraid. Anyways i will try 1)No PciExpress Wifi 2)Single GPU 3)VNC only 4)a VM with Linux Mint. I really started to like unraid, and i dont want to give it up and return to a single Windows 10 machine.

nobody else has 2 vega frontier edition 1300 euro a pop in their machine, of that i am sure. I dont know what else to do.

tried them all nothing works, im trying different setting when making the VM, damn, why does it have to be so complicated ! Why the FK it just works for others where i watch YouTube videos ? And at my pc it doesnt ! Motherfucking Life ! Im on this shit for the past week trying to sort it out ! Making incremental progress every day in understanding Unraid, but this just cuts it, as everything is as it should be. It should just work !

in the uefi shell once i type exit it takes me to a bios of sorts, here i have a boot manager, and this is what i see: Nothing resembles a device that would be the ISO, i think its not even recognized that is why i enter the uefi shel. tried all of those, no windows setup starts.

what have you chosen in the boot managerm menu after typing exit ? i have nothing there that resembles a boot device from which that windows 10 should boot