Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About phyzical

  • Rank
  1. hey all, ive got a catalina vm running but having trouble passing through a usb controller, i understand i need to rename EHC1->EH01 and EHC2->EH02, which i have done via clover configuration ACHI patches and i have copied injectallusb.kext and applied the patches following this guide https://hackintosher.com/forums/thread/list-of-hackintosh-usb-port-limit-patches-10-15-updated.467/ But when i reboot i get no usb ability? checking the system report on the mac i see no change when plugging in devices either. i have a Gigabyte X79-UP4 if that helps. i can passthrough individual devices fine, but thats a pain haha Do you have any suggestions on anything i may be missing or doing wrong? Thanks in advance!
  2. Thanks to all that provided input @glennv Thanks for all that, was able to play around with clover, tried stubbing the gt 620, tried providing custom kexts and core display ect from what i could find online alas nothing seemed to help haha.. But there is a silver lining in a sense, i canabilised my main server's GPU GTX 760 which works with catalina OOB hazzah! so got it working by cheating still counts @juan11perez Thanks for all the suggestions, alas again the gt620 refused to work with anything other than mint. But again once i started using the gtx 760 as the secondary card i was able to atleast get kubuntu booting. for some reason though ubuntu still refused to play ball, ahwell kubuntu will do now my main server is just running 4k off dodgy IGPU until i upgrade my secondary pc some time near the new year. itll do! Marking this as solved even though i feel whatever issues i was running into i never truly solved.. haha ohwell wins a win right...? Thanks again all! time for my docker adventure to begin, and then my main server will be ready to come to unraid
  3. @glennv as a note. I have the primary card (GTX 770 primary passing through fine with the vbios ) the card im trying to use is the secondary card so unraid doesnt boot up on it, do i still need to "stub" it? i will search a bit harder on how to stub it and try it anyway juust incase. i will also have a crack at the clover configurator i almost downloaded it but thought it was about editing the clover BEFORE getting it all up and running. i haven't watched his older videos in regards to osx as i assumed they were not applicable given his latest docker (as in its a total different path) but i will have a watch of those too thanks. i might need to try doing an osx from scratch instead of his ezpz mode solution also haha you are correct i am a tooootal noob in regards to Hackintosh. if only IOS didnt have such a large market share haha... as is the way with anything learn by fucking up thanks again!
  4. i understand there would be times were things should get lost to avoid issues in the template configuration or maybe when one changes to a new unraid version and options are redundant. i will make a report will the things im seeing get lost to a save as a solution going forward. itimpi's idea does sound like a nice middle ground. and should help with custom qemu settings (referencing spaceinvaders new container) i.e but would not help with things like metadata, os and network override before i give up on the suggestion at the very least would diff on save not be possible to return the things that have been/will be dropped? or a more complicated approach version control of xmls allowing for a diff in the same sense as say pull requests, taking this as a thought i guess choosing what to keep as i originally suggested isnt as easy as i thought as you end up with "conflicts" haha. at the very least keeping a copy of say the last X xmls for a vm in a tab maybe? (im sure people do this manually anyway in cause of breaking things on change/testing anyway) thanks for listening!
  5. @glennv thanks for all that, 2 quick questions * "stubbing" this is just assigning the gpu for passthrough correct? * i tried adding the boot flag in clover via the boot menu but after a restart it seemed it was gone do you have any resources on the correct way to "edit the clover settings". most of the stuff ive been finding over the past few days suggests it should just be visible as a mounted folder? i tried checking all the /dev/disksXX and /Volumes but i could not find it if i can figure out how to edit the clover then i should be able to test skipping the boot loader to rule out the reboot bug Thanks!
  6. @juan11perez Thanks for that, sounds like i was trying to do it right though i didnt try changing the proprietary settings. i will try with kubuntu just for the sake of it, worse case ive got the mint install. my ubuntu installs are defiantly doing something weird and getting a a reboot bug a soon as i passthrough the GPU @glennv by the sounds of it cyber was just giving his 2 cents on what hes been experiencing in regards to linux not macosx, In regards to OSX i agree i shouldn't have had an output using catlina and the nvidia card (maybe the macinabox didnt install catlina but high seirra the first time?). so i will try high sierra again. Should i only need to install the webdrivers? or do i have to make clover config changes also i.e. nvda_enable=1. I am currently trying to use the macinabox docker so i am forced to a prebuilt clover image and i haven't been able to find a way to easily modify this cqow2 image. Im just trying to rule out that im running into the reboot bug with my gfx when the clover bootscreen pops up and thats why im not getting a signal on OSX Thanks
  7. Hey there loving unraid so far, While ive been making changes to vms that are not in the list of supported options, i.e switching between gui and xml, it can be a bit annoying to have to re add said custom options, so i had a thought what if we could notify the user on save on an xml template to display the options being lost (at the very least) and maybe give the choice to keep such options that will be lost? or maybe let them choose what to keep and what to ditch? If i wanted to try to make such a feature where would i go about starting (repo/development infra wise)? I dont feel it would be too difficult just an extra modal/form step and submission server side with a diff of before and after template to determine what to show. or is this part of unraid not opensource? if not ill leave it as a feature request Thanks!
  8. hey @samtrois thanks for the suggestion tried another cable but doesn't make a difference sadly
  9. Hey all, on my first install i was able to get GPU passthrough via my GT 620 as a secondary card. but the next day i could not get video signal anymore. So i tried reinstalling the OS a few times infact.. (also tried high sierra and mojave) this had no effect. I also think i was served with weird boot screen at one point which allowed me to skip the clover boot loader (i think this is the important part as the GT 620 suffers from the reboot bug) Does anyone know how to adjust the Clover image to allow for me to try and skip the boot loader to rule this out as an issue or any tips for GPU passthrough and these macos images. i know the 620 shouldn't work with catalina but i swear it was working, persisted vm sleep too. i dont know how i got lucky the first time haha.. thanks!
  10. holy crap.... i was about to post another massssive speel about it not working.... and as i was rerunning all the vms to get logs the mint OS passed through the blood GPU OFC only thir time lucky apparently.... Thanks Juan for the suggestion. atleast i have something to dev on . But would appreicate answers in regards to how you "update" the drivers correctly on ubuntu incase im doing something wrong with that. Now for me to try and get a mac box passing through again. PROGRESSSS! edit: spoke too soon.. so i spun down the vm and when i went to spin it back up. no bootable device again, changed to sata like i had todo with the ubutnu box and then i couldnt passthrough the GPU anymore.. but i could ssh onto the box so it was spinning up correctly. just noticed i can do the whole install via the GPU passthrough with mint so ill try again like that instead okay looks like this might be hitting the reboot bug on the gt 620. unfortanly google suggests the 560 suffers from this too ahwell. atleast i have something working as annoying as it will be for now
  11. Hey @juan11perez, Thanks for the input! to confirm in installing the correct apt. i tried nvidia-driver-435. but same issue. (the nvdia server-x thing from store was also installed with the install install) The weird thing this its getting stuck in a reboot loop i think... as i cant ssh onto the box any more and when i hook up an rgb keyboard the keys flicker (as they do on first boot) every few seconds having a look in the syslog i see the usb keyboard is over and over until i kill the box. chaging back to vnc restores the box and ssh works again. it does this no matter the gpu primary with bios or secondary gpus. I will try mint tonight just so i can try something linux based that "should work"... another question incase its a factor do you use VirtIO for the vdisk. i am always forced to change it to SATA after removing the iso or it complains no bootable media.
  12. Hey there all, So im having issues passing through gpu to anything that is not windows? This was my first post where i was having issues with passing through the gpu as the primary card, that has since been working great. Also if i pass through any of my 3 cards through to windows all loads up as expected. i could never get any gpu output on any linux based os, i tried ubuntu and deepin so i sidelined it and focused on the windows vm. When i first tested two Vms after getting primary gpu through on the 770 working i had catlina (i think... from spaceinvaders new docker container ) running on my gt 620 with output and the primary passthrough via 770 to the windows vm i cheered... but after i booted the pc the next day i had no gpu signal to the mac vm anymore. i tried reinstalling it about 6 times trying various combinations, with and without vbios on the GT 620, gtx 560 and the gtx 770 to the mac with no luck. i eventually gave up on the osx vm as technically the cards probably shouldn't work and the first time i must have just got lucky?... i even tried mojave and high sierra (as this is meant to support nvida more) no luck there either So now ive decided to focus on atleast getting an ubuntu box going as that should work with my other two nvidia cards (gt 620 or gtx 560), and work for my development needs, below is my current ubuntu xml. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Ubuntu</name> <uuid>6b4c1fc5-3957-abff-23ed-085e92516c27</uuid> <metadata> <vmtemplate xmlns="unraid" name="Ubuntu" icon="ubuntu.png" os="ubuntu"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='3'/> <vcpupin vcpu='1' cpuset='7'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='1' threads='2'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <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/domains/Ubuntu/vdisk1.img'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <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'/> <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='0xb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xa'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='7' model='pcie-to-pci-bridge'> <model name='pcie-pci-bridge'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <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'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:c4:2a:8c'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> </domain> i have tried the 620, 560 and even the 770 nothing no signal output. no errors logged in diagnostics as far as i can see. the libvrt says so i think its trying... ive spent a few hours each night trying to get various os's that are not windows to give me an output, hair pulling stuff haha.. especially since i had output the the mac vm just the way i wanted once before... i just want a non vnc output for a dev machine ;( Does anyone have ANY suggestions.. Thanks in advance!!
  13. So i had another few hours of researching other threads, rereading the ones i had. i found a few people mentioning they had to choose the audio driver also when providing the bios and i realized i dont think i was providing it during my testing of the various combinations. so i gave it all another go but unfornatly this made no difference buuuut, since i had been switching the cards so much i decided to give the 770 a crack, had something in slot 1 and the gtx in slot 2 dumped the bios and bam the 770 let me passthrough as the primary card when in slot 1.. omfg i guess the gt 620 and gtx 560 just don't allow for it to be the primary and passthrough? is there somewhere i should add these cards to add to the list of no goes? i.e a wiki? the gt 620 doesn't seem to suffer from the reboot bug btw, i am able to boot it on a windows vm multiple times without reboot. Now i have a new issue (which may have been compounding to my testing to begin with) i cant seem to get video output to a vm that isnt windows i.e deepin or ubuntu. ive tried the 560 and 620 as secondary cards. i even tried the 770 as the primary card providing the vbios no dice. I will setup a majove vm tommrow and see if that makes any difference also. Guess its time to start investigating again. Just tested space invaders new container for making mac os vms and got an output on the gt 620 while having an output on the 770 as primary to the windows vm guess theres some sort of driver issue im facing with the ubuntu and deepin vms thanks for the hand holding @testdasi, ill mark this one as solved
  14. Hey @testdasi, * So i tried switching to legacy boot via bios, no change * the only thing i could see in regards to gpu "switching" was choosing the primary pcie which seemed to have no effect on unraid unfortunately * now the fun one.. so i tried switching the gpus around (gtx 770 in slot 1 and gtx 560 in slot 2), this moved the unraid boot over to the gtx 770, i tried launching a windows vm this time on the gtx 560. i got picture (to be expected as its no longer primary) proceeded to dump the vbios same as every other time i could unbind could not not rebind (i wonder if this is a symptom at all? had the same issue with the gt 620). When i tried to test a boot on the windows vm with this bios i got nothing, so i rebooted and confirmed the windows vm rebooted with the bvios rom i dumped. I then proceeded to switch the cards back to the original order (gtx 770 in slot 2 and gtx 550 in slot 1) but unfortunately i got the same issue... * To confirm if i switch the slots i shouldn't have to re dump the bios? its just in the space invader video there was mention of (be sure to make sure the video location has not changed which ofc it does if i have switch the gfx card back) i did have one weird thing happen though the first time i launched it up after switching back to the original order i had the boot screen on the 770 still even though it was in slot 2, so after it didnt work i had a thought maybe i could replicate this to re dump the bios (but ofc if switching the slots doesn't affect the bios then this is a moot point). i also could not replicate this again anyways (tried relaunching with cords only in 770, also tried a boot with only 770 shutdown then boot again with both cards) * one other thing i could replicate (not that i think it indicates anything) was that if i launched a vm with the primary card and then proceeded to unbind the call would never return, as in it just hung indefinably (this is got my hopes up as maybe i had been doing it all wrong) but unfortunately it did not seem to make a difference in the long run Is it possible i just have some hardware that refuses to play ball? Or to Anyone else is lurking have you happened to have run into a similar issue? Thanks again!!
  15. Thanks again, So i found an gtx 560 SE and switched that out for the gt 620. did another bios dump, i did have a weird issue where the terminal would lockup on unbind while dumping the bios.. (no known weird issues with this new card is there maybe?). buut same thing no output on vm spinup with the 560 as passthrough with bios.. * i will try switching via the bios tomorow (its getting late) and see if i get the same issue with 770 as primary and 560 as secondary. * Oh one thing i am noticing is that when im using the passthrough im forced to force stop the vm, as opposed to when vncing which i just stop. This would mean the VM isnt loading up the OS properly right and thus cant sned the kill signal? Looking at the "logs" of the vm from the vm tab doesn't seem to have anything useful... buut just incase This is the VNC when passthrough i just feel like im screwing something up at this point if its happening on two completely different generations of cards right? Thanks!