SpaceInvaderOne

Community Developer
 View Profile  See their activity

  • Posts

    1741

  • Joined

  • Days Won

    29

 Content Type 

Posts posted by SpaceInvaderOne

    [Support] SpaceinvaderOne - Macinabox

    in Docker Containers

    Posted

    11 hours ago, bastl said:

    @SpaceInvaderOne After updating to the latest release, FCP gives me the following error:

     

    Also worth to mention, there are a couple shinobi paths in the template now which i never added myself. Also I never used shinobi before.

     

     

     

    Please goto docker tab and scroll to the bottom. Then click add container.

    At the top of the page now click add template and choose macinabox

    1633544441_ScreenShot2020-04-09at20_34_11.thumb.png.5d241a9b61c0774cbe4bf7a7b5a3a215.png

     

    Then when the template is open click on the red x  (this will delete the stored template)

     

    959438689_ScreenShot2020-04-09at20_36_07.thumb.png.e6c90b1524a88795c689addb12a1b1ba.png

     

    Now just goto the apps tab and redownload the container. It will now redownload the template too as it has been deleted from above steps.

    Should be fine.

    • Like 1
    • Thanks 1

    [Support] SpaceinvaderOne - Macinabox

    in Docker Containers

    Posted

    On 4/4/2020 at 9:32 PM, RockDawg said:

    I posted about this issue a few pages back.  I have no problem getting MacOS up and running with this VM but is always slow and choppy.  Text lags behind my typing and everything seems choppy.  App windows open a bit choppy, web pages load slowly and are also a bit choppy.  It doesn't matter if I try 1, 4 or 8 cores or 4, 8 or 16 GB of RAM.  I doesn't get any better.  I've tried the SSD my Win10 VM runs on (cache drive) and another SSD via unassigned devices.  Again, no difference.

     

    Is there a tip or something on how to get it to run smooth and quickly via VNC?  I'm just looking for a simple VM.  No hardware passthrough or anything.  I have a Win10 VM setup with the same cores and RAM and it runs great.

     

    I notice a lot of people in this thread are passing through video cards.  Is that required for a good experience?  Does anybody have a quick and smooth running experience via VNC?

    You will have a better experience using splashtop desktop (personal is free on local network) with the vm rather than vnc. When logged in with vnc install the splashtop streamer for mac and the splashtop client on the computer that you want to connect from. https://www.splashtop.com/downloads

    [Support] spaceinvaderone - Shinobi Pro

    in Docker Containers

    Posted

    If having the problem with untracked working tree error then please do the following (very similar to what @Raf02suggests - thanks Raf) 

     

    (New installs wont have this problem)

     

    Goto Unraid webui and click on icon to open terminal prompt

     

    Run the following command

      

    find /var/lib/docker/btrfs/subvolumes/*/opt/shinobi/package-lock.json -delete

     

    Then in the Unraid 'Docker' tab, enable the 'Advanced view' (top right) after which you will see force update available for each container. Force update your shinobi container.

     

     

    ** VIDEO GUIDE How to Start & Stop VMs (that use passthrough) on Unraid Servers with only 1 GPU **

    in VMs

    Posted

    Swapping from one VM (with GPU passthrough) to another on a server with only 1 gpu, we normally shutdown the vm and use another computer to loginto the webUI and start up another VM.

    If you dont have another computer or just dont want to have to grab your laptop etc each time you want to jump onto another VM. We can use a script to do it all from the VM you are using.

     

    [Support] SpaceinvaderOne - Macinabox

    in Docker Containers

    Posted

    On 3/6/2020 at 10:54 PM, Zer0Nin3r said:

    Is there a way to make this change persistent? Every time I make a change using the template editor, this section of the XML is modified.

    Unfortunately at present the Unraid vm manager removes custrom xml. If you use virt-manager instead to edit your vms then the custom xml will remain the same.

    • Thanks 1

    [Support] SpaceinvaderOne - Macinabox

    in Docker Containers

    Posted

    On 3/8/2020 at 6:15 AM, AgentXXL said:

     

    But in the meantime, are there any workarounds to not having AVX2 support? All that lead-up for one simple question, but I'm expecting the answer is no. Regardless, thanks @SpaceInvaderOnefor making it so easy to create Mac VMs on unRAID!

     

    One other note caused by my OCD: in the config for the MacinaBox docker container (and VM), the paths listed for appdata and Basesystem use different case for the spelling of 'MacinaBox'. This leads to the creation of 2 folders under appdata, differing only in the case of the letters. I've changed mine so they both use the same case of 'MacinaBox' and so far everything is still working with a fresh High Sierra VM. Is there any reason why these paths use different case letters in the name of the folder? I just corrected the case of the pathname for Basesystem so it uses the same folder as appdata. Any reason why I shouldn't do this?

     

    MacinaBox.thumb.jpg.99eff3195c01647727fc7f2e5a80f580.jpg

     

    Dale

     Not sure of any workarounds I'm afraid.

     

    Thanks I meant to fix the template for the locations and forgot to. Reading your post prompted me to fix it :)

    [Support] SpaceinvaderOne - Macinabox

    in Docker Containers

    Posted

    On 2/8/2020 at 9:41 AM, adgilcan said:

     

     

    Macinabox Catalina VM XML.rtf 7.2 kB · 2 downloads

     

    However, when I start the VM it loads the clover screen but when I press Enter to install it hangs with a blank screen.  I have a 500Mb/s internet connection and have left it overnight in case it was downloading anything.  Apart from the blank (black) screen, the first thread of the CPU runs non stop at 100%, (see screenshot below) so I'm guessing something isn't right.  The current config shows me using 2 cores of the CPU and 4Gb RAM.  I have tried with 4 cores (not the first one reserved for UnRAID) and 8Gb RAM.  I have tried all sorts of machine types.  Any of the i440fx machines produce an error about pci-root but all of the Q35 variants allow the clover screen to load but hang thereafter.

     

    I'm stumped.  I'm running a new Supermicro motherboard with dual core Xeon CPUs and 128Gb RAM:

     

     

     

    Any help would be VERY much appreciated!  I've managed to get a Windows 10 VM working perfectly - thanks again to Spaceinvaderone for his great videos!

     

    Sorry for the long post!

     

    PS Try as I might I couldn't find the OSKey to obscure.  Has this been removed, or does it only come up after successful installation of the OS?

     

    Many thanks

     

     

    D

     

     

     

    Hi,

    looking at your xml all the custom lines that are needed are no longer present.

    Unfortunately when you make a change to the vm using the Unraid vm manager gui it strips out any custom xml.

    So if you make a change using the vm manager after doing so you must add back the xml that has been removed

    At the top of the xml would be 

      <os>
    <type arch='x86_64' machine='pc-q35-3.1'>hvm</type>
    <loader readonly='yes' type='pflash'>/mnt/user/domains/MacinaboxCatalina/ovmf/OVMF_CODE.fd</loader>
    <nvram>/mnt/user/domains/MacinaboxCatalina/ovmf/OVMF_VARS.fd</nvram>
  </os>

    This points to a custom ovmf file  in the domains share.

      

      <interface type='bridge'>
      <mac address='52:74:00:17:57:0f'/>
      <source bridge='br0'/>
      <model type='vmxnet3'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>

    This part here sets the network card to be vmxnet3  (as the virtio which is standard will not work)

    Vmxnet3 is necessary for the install . However after installing it is better to then change that to 

     <model type='e1000-82545em'/>

    Also at the bottom of the xml it is very important as the vm will not continue from clover without.

      

       <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x0f' slot='0x00' function='0x0'/>
    </memballoon>
  </devices>
  <qemu:commandline>
    <qemu:arg value='-usb'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='usb-kbd,bus=usb-bus.0'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='isa-applesmc,osk=the osk key has been removed from this'/>
    <qemu:arg value='-smbios'/>
    <qemu:arg value='type=2'/>
    <qemu:arg value='-cpu'/>
    <qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check'/>
  </qemu:commandline>
</domain>

     

    Also if you have set your cpu to have a large amount of cores then you will need to remove the topology line from the xml.

    for example 

      <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='16' threads='1'/>
  </cpu>

    should be changed to 

      <cpu mode='host-passthrough' check='none'>
  </cpu>

     

    Hope this helps :)

     

    [Support] SpaceinvaderOne - Macinabox

    in Docker Containers

    Posted

    2 hours ago, jpowell8672 said:

     

    Is support from @SpaceInvaderOne gone for macinabox? I see no replies for this docker from him since December 19, 2019 last year.

     

    44 minutes ago, jpowell8672 said:

     

    Just found out MacOS High Sierra does not support Nvidia RTX cards, with Apple and Nvidia in some kind of conflict dispute none of the updates to MacOS since High Sierra support any Nvidia Cards.

     

    Hey @jpowell8672  I am still here :) -- Yeah sorry  the last month has been really busy for me with work so I haven't spent a great deal of time on the forums recently.

     

    Yeah its a shame that Nvidia cards, since High Sierra, are no longer supported by Apple and especially too that support in High Sierra stops at Pascal - GTX 10 series. :(

     

    • Thanks 1

    [Support] SpaceinvaderOne - Macinabox

    in Docker Containers

    Posted

    18 hours ago, Mark Hood said:

    This is a great tool, thanks very much!

     

    It does create a very minor problem though - when I run the 'Fix Common Problems' plugin I get this error reported:

      

    
The following directories exist with similar names, only differing by the 'case' which will play havoc with Windows / SMB access.  Windows does NOT support folder names only differing by their case and strange results will happen should you attempt to manipulate the folders or files

/mnt/user/appdata/macinabox
/mnt/user/appdata/MacinaBox

    Now obviously I'm not sharing appdata over SMB - but would it be possible to update the container to only create one or other of these, so the 'Common Problems' plugin stops complaining?

     

    Thanks!

    opps yes i will fix that

    • Thanks 1