Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

7 Neutral

About glennv

  • Rank
    Advanced Member


  • Gender
  • URL
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 1.Stubbing means telling unraid not to touch/see the stubbed devices so they can be used by a VM exclusively. Do a search on this forum on how to do this. 2. Install clover configurator. That allows you to mount the efi partition containing clover. Then load the clover config file and you can change anything you feel like changing Sounds like you need to first brush up on some basic hackintosh skills, otherwise you will likely get yourself into all kinds of problems. But of course trying and falling is a perfectly valid menthod to learn as well so go for it. ✌️🤪. ps recommend you watch a few SpaceInvaders videos on how to passthru a GPU and some how to in general setup an OSX VM. You will learn a lot from it and most of us have grown up with them , plus of course lots of trial and errors and frustration that comes with Hackintosh
  2. Regarding getting an nvidia to work on OSX (assuming its a suported model on the specific os) the order is typicaly 1 make sure you have a fully working vm first without any passthru. 2 backup the vm file(s) and clover partition file so you can always go back if your next steps fail. 3. boot into the vm , install the correct nvidia web drivers and set the nvidia web flag in clover. 4 shutdown the vm, stub the nvidia card and if applicable its accompanied sound card (and for newer models even an accompanied usb i believe) Reboot the unraid server . 5 backup and then modify the xml manualy (in xml mode), remove the vnc / video device and put the nvidia device(s) there instead. (if you dont know how, you could do it in gui mode and then reapply the code that the gui mode wipes away at the end as well as re-correct network device) 6 Now boot the vm with the stubbed nvidia and fingers crossed. Once it works install the cuda drivers . If it does not work , recreate/reset to your original xml and point it to your backup clover and backup os vm and boot from there without the stubbed card. There are lots of posts/threads online describing this process so check them out for details/troubleshooting etc if it does not work from the get go as there are a million way this can go wrong. Spaceinvader of course has lots of videos on this as well.
  3. What do you mean ? Myself and dozens of people here run 6.7.2 perfectly fine since day one with GpU's passed though to OSX (nvidia/high sierra or AMD/mojave/cataline). If you have issues it does not mean it does not work for anyone.
  4. np. yeah its a bit hidden under the system settings but works great
  5. install the "CA auto update" plugin. You can then select for each docker if you want to update automaticaly or not. Use it since day one to protect/exclude a few vital dockers and the rest get updated nightly if applicable
  6. Just a hunch but could it be your cache ssd that is not trimmed untill you reboot ? That will slow it down to a crawl. You can run the fstrim command manualy agianst the /mnt/cache or schedule it with the usr scripts plugin. I run it nightly against my ssds.
  7. not sure what you mean. my pihole works across all devices as dns based. Just make the dns for all your devices the pihole and you are good to go.
  8. tried it some weeks ago and also blocks lots of normal videos and lots of videos that would play ads now get stuck and just wait (likely for a signal that the add is finished , which it wont get). Also the rate at which new urls for add get generated makes it useless and more an annoiance unfortunately. Removed it. The method is not the way to go unfortunately.
  9. Tnx, yeah that second question was not specific to this docker (just played with this docker for fun to see if it behaves different to my exsiting OSX VM's). Will try and play with it by just changing the bios rez. Already had just created 2 identical VM tempates pointing to the same vdisks etc, one with VNC and one with GPU so i can play and experiment without every time having to boot the server. edit: just changed only the bios to 2560x1440p and it worked. Not sure what i did wrong the last time. Tnx
  10. @SpaceInvaderOne Not sure if i read over it somewhere , but what exactly is custom about the 2 ovmf files ? Is it just the unraid 3.1 version but with preset screen resolution or is there more modified ? Second (not specific to this docker), when i use vnc the 1920x1080 works fine and i see all boot logs ungarbled , but when i replace it with my vega 56 , its all garbled after the initial clover boot disk selection part. Tried changing the resolution on clover side and bios side to 2560x1440, but cant seem to get it to work so i can read the debug logs. Is there a limit in the bios to only be able to use 1920x1080 during boot or can it also work in a different resolution with connected monitor/gpu. (due to the reset bug its not easy to just test all combination as have to reboot the whole server everytime, but a few tries failed so before i spend 5 days trying all combos i thought i would ask how you do it) Tnx again for the cool docker.
  11. Tnx. Would have been nice if it had worked consitently accross the board but seems more llike an unreliable bandadge that in some cases kills the patient. Stability is more important for a core storage solution.
  12. I thought that was clear by now . (or maybe i should have put "the effects of the bug" ) The bug whereby a passed thru AMD card causes a VM (at least in my case my OSX VM with Vega 56) only to be able to be started once. Will run fine indefinate, everything works, but then when you restart the VM , it hangs as "apparently" the AMD card does not get properly reset. That was all before 6.8 rcx for me the case. In 6.8 rc a patch was introduced to tackle this bug according to the change logs. For me it had the side affect of not just hanging the VM but paniking and hanging the complete Unraid server (see logs /screenshots etc). Consistently and repeatable. Reverting back to 6.7.2 return it to normal buggy behavior of forementione AMD reset bug.
  13. Are there any changes made that require a retest (as i see you changed the status) as i am now running 6.7.2 but willing to retest if something changed in the code ? Did not see anything related in the rc4 change log
  14. Dont forget thats a (small) performance loss vs a huuuuuuuuge gain of flexibility and features. I host them now on ssds in a zfs pool using the great zfs plugin and make daily plus on demand snapshots plus remote send / recieve to second unraid for incremental backups from the vdisks. And clones for all kinds of test that use virtualy zero extra storage space. So with the flick of a finger i can get a broken vm back to working state. Its such a freedom to not worrie about braking your vm or clover partition with experimenting or upgrades. You loose all this when passing the whole device to your vm. So keep that in mind when planning your setup. Btw its easy oneliner to convert between physical drive and virtual using the inbuild qemu commands . I started physical passthru and migrated all to virtual eventualy.