[Support] SpaceinvaderOne - Macinabox


Recommended Posts

2 hours ago, Mattyfaz said:

 

Any ideas what I could've done wrong? It's sort of working as I can see the small mouse moving on all those little screens.
Any tips would be much appreciated!

<OS> segment is wrong. You need to copy it from original XML too and everything will start.

I created empty VM for this purpose. Then I want to add or change something I change this VM and then copy XML parts I need to Macinabox XML.

Edited by AlexSolo
Link to comment

I have a Clover boot problem that's just started somewhat out of the blue. For the past few days, when I boot my MacinaboxCataloina VM, I just get a blank screen with a solid cursor (it's been working perfectly for several months);

 

DSC_0503.thumb.JPG.0a27ef738ae666c46c5a0d06a7cf612d.JPG

 

System hangs there and no Clover menu loads. I 3x disks defined, my clover QCow, a System disk and a Scratch disk;

 

    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2' cache='writeback'/>
      <source file='/mnt/user/domains/MacinaboxCatalina/Clover.qcow2' index='3'/>
      <backingStore/>
      <target dev='hdc' bus='sata'/>
      <boot order='1'/>
      <alias name='sata0-0-2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='2'/>
    </disk>
    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source dev='/dev/disk/by-id/ata-Crucial_CT120M500SSD1_14340D03A1FD' index='2'/>
      <backingStore/>
      <target dev='hdd' bus='sata'/>
      <alias name='sata0-0-3'/>
      <address type='drive' controller='0' bus='0' target='0' unit='3'/>
    </disk>
    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source dev='/dev/disk/by-id/ata-TS64GSSD340_20140731B61710144112' index='1'/>
      <backingStore/>
      <target dev='hde' bus='sata'/>
      <alias name='sata0-0-4'/>
      <address type='drive' controller='0' bus='0' target='0' unit='4'/>
    </disk>

 

If I remove both system and scratch disk (the second 2x entries), the VM will load up the Clover boot menu, but obviously cannot go any further due to there being no volumes available. Adding back either of the disks will revert to the black screen and no Clover menu.

 

I've maxed out my Google-Fu and found that this screen can appear if the Clover timeout is set to zero. The solution in this case is to hold down any key at boot to force the clover menu to load. This kind of works for me. I can hold down, say, the space bar and after 3 or 4 attempts, it will load up Clover and I can progress. It seems somewhat sensitive to when the key is first pressed though, holding from VM launch in unRAID UI won't cut the mustard, I've got to find some indeterminate time in the first 5/6 seconds.

 

Now, I checked my clover config, and my timeout is set to 5 seconds. So while the problem manifests and the solution (mostly) works as per my research, the cause is not as described.

 

I've tried replacing the clover qcow image file from a different VM, thinking there might be corruption, I had the same problem (the clover qcpw works fine on the other VM).

 

I'm a bit stumped by this. Not a show stopper, but a major PITA. Any insights or suggestions appreciated.

 

Thanks for reading. Please forgive the horrid state of my monitor - I think my wife was 'cleaning' at the weekend 😞

 

 

 

 

 

 

Link to comment
On 4/16/2020 at 7:30 PM, frodr said:

Hi,

 

Is there a way to install another MacOS vm?

 

I tried this several times with changed appdata and basesystem folders on the second MacOS vm. It seems that it is not made a new vdisk for the second vm, but refers to the first vm vdisk. 

 

What is the correct way for a second vm?

 

Happy for any help.

 

 

/frode

 

 

Anyone, please.

Link to comment
1 hour ago, frodr said:

Anyone, please.

I've used the MacinaBox docker container to create multiple MacOS VMs and currently have it working for High Sierra, Mojave and Catalina. The only changes made were to the paths required by the docker container and of course selecting the correct OS version. I used the full install method for all 3. Here's a screenshot of my Mojave setup (last one I created). All it required was the 3 changes.

 

MacinaBoxConfig.thumb.jpg.4eb3eec2d47b2cbea2c910973ccd3fb6.jpg

Edited by AgentXXL
spelling
Link to comment

hey guys,

 

Skimmed the whole post and saw a couple questions about this, but no answers yet.

 

I'm just trying to passthrough my unraid shares to the VM:

 

<filesystem type='mount' accessmode='passthrough'>
      <source dir='/mnt/user/'/>
      <target dir='unraid'/>
      <alias name='fs0'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
</filesystem>

 

...but in the VM I can't find the shares anywhere.  also found this post: 

 

 

But as far as I can tell this does not work in MacOS.  The tag "unraid" (as I specified in my XML file) is not available to mount in diskutil:

 

erik@iMac ~ % diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.1 GB     disk0
   1:                  Apple_HFS macOS Base System       2.0 GB     disk0s1

/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *268.4 MB   disk1
   1:                        EFI EFI                     101.4 MB   disk1s1
   2:           Linux Filesystem                         163.9 MB   disk1s2

/dev/disk2 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *68.7 GB    disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                 Apple_APFS Container disk3         68.4 GB    disk2s2

/dev/disk3 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +68.4 GB    disk3
                                 Physical Store disk2s2
   1:                APFS Volume MacOS - Data            13.0 GB    disk3s1
   2:                APFS Volume Preboot                 80.0 MB    disk3s2
   3:                APFS Volume Recovery                528.1 MB   disk3s3
   4:                APFS Volume VM                      1.1 MB     disk3s4
   5:                APFS Volume MacOS                   11.0 GB    disk3s5

 

Has anyone gotten local shares passed through successfully?

 

Thanks!

Edited by acosmichippo
Link to comment
3 hours ago, AgentXXL said:

I've used the MacinaBox docker container to create multiple MacOS VMs and currently have it working for High Sierra, Mojave and Catalina. The only changes made were to the paths required by the docker container and of course selecting the correct OS version. I used the full install method for all 3. Here's a screenshot of my Mojave setup (last one I created). All it required was the 3 changes.

 

MacinaBoxConfig.thumb.jpg.4eb3eec2d47b2cbea2c910973ccd3fb6.jpg

Thanks. I will try that.

Link to comment

Alright I kept having problems after trying to change the XML once I had already installed.
So I removed everything and started again, this process (edit XML before install) worked for me:

  • Install via Docker
  • Restart Array, then go to VM
  • Before starting the VM, select edit, switch form view and copy out all of the XML to another text editor
  • Modify XML in the text editor with the desired CPU info, and changed the model type for the interface to e1000-82545em

580953833_ScreenShot2020-04-21at10_09_33am.png.11859e552900bba0efa117685b318292.png  41348684_ScreenShot2020-04-21at10_10_23am.png.505cc2ae333b6f4d150077022dd522dc.png

  • Copy XML back into UnRaid and Update
  • Boot the VM

It installed and is now running without issues, and I haven't had to change any XML after the fact.

Link to comment
16 hours ago, acosmichippo said:

hey guys,

 

Skimmed the whole post and saw a couple questions about this, but no answers yet.

 

I'm just trying to passthrough my unraid shares to the VM:

 


<filesystem type='mount' accessmode='passthrough'>
      <source dir='/mnt/user/'/>
      <target dir='unraid'/>
      <alias name='fs0'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
</filesystem>

 

...but in the VM I can't find the shares anywhere.  also found this post: 

 

 

But as far as I can tell this does not work in MacOS.  The tag "unraid" (as I specified in my XML file) is not available to mount in diskutil:

 


erik@iMac ~ % diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.1 GB     disk0
   1:                  Apple_HFS macOS Base System       2.0 GB     disk0s1

/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *268.4 MB   disk1
   1:                        EFI EFI                     101.4 MB   disk1s1
   2:           Linux Filesystem                         163.9 MB   disk1s2

/dev/disk2 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *68.7 GB    disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                 Apple_APFS Container disk3         68.4 GB    disk2s2

/dev/disk3 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +68.4 GB    disk3
                                 Physical Store disk2s2
   1:                APFS Volume MacOS - Data            13.0 GB    disk3s1
   2:                APFS Volume Preboot                 80.0 MB    disk3s2
   3:                APFS Volume Recovery                528.1 MB   disk3s3
   4:                APFS Volume VM                      1.1 MB     disk3s4
   5:                APFS Volume MacOS                   11.0 GB    disk3s5

 

Has anyone gotten local shares passed through successfully?

 

Thanks!

 

 

Hi @acosmichippo

 

You don't need to 'passthrough' unRAID shares via XML. like this. 

 

You simply mount them from within the OS, like you would any network volume;

 

Either find the share on your network and double-click it. It will appear on your desktop (if you have finder prefs set to display*), or at the very least will be available in finder;

 

1236297857_Screenshot2020-04-21at14_00_56.png.c2bd6276647aced13a49ec1a45bf1735.png

 

If your server is not showing up under network for some reason, you click Go->Connect To Server in the finder menu, and enter your server and share details;

 

1272470843_Screenshot2020-04-21at14_00_22.png.b04b14b121c8b1228f9a7cddc9cd3149.png

 

Once you have accessed one or more volumes, you can drag them in to login items for your account in users and groups. This will cause those volumes to mount every time you reboot your VM;

 

 1120918892_Screenshot2020-04-21at14_01_38.png.79ba8308f052ee3337ab4f832ab3eb8c.png

 

*Here's how to configure finder preferences to have everything mounted appear on your desktop;
 

1760406640_Screenshot2020-04-21at14_07_43.png.18104aefd5803cf58d1ab5270da405f7.png

 

If you have trouble, you need to search online for 'MacOS Network Volume Mounting' or some such, not unRaid, as what you're doing is the same as if you have a MAC on a LAN and you want to connect to a separate fileserver.

 

Good luck!

 

 

Edited by meep
typos
  • Like 1
Link to comment
8 hours ago, meep said:

You don't need to 'passthrough' unRAID shares via XML. like this. 

 

You simply mount them from within the OS, like you would any network volume;

 

I know I can mount SMB shares, but I WANT to passthrough.  And you don't need to put it in quotes as if I made it up, it's right there in the qemu wiki.

 

8 hours ago, ghost82 said:

Moreover, if you have any additional disks to mount you can also use the unraid unassigned devices, just mount and share and mount in mac os from network as explained in hte post above.

I want to access the files in the shares, not unassigned devices.

Edited by acosmichippo
Link to comment
1 hour ago, acosmichippo said:

 

I know I can mount SMB shares, but I WANT to passthrough.  And you don't need to put it in quotes as if I made it up, it's right there in the qemu wiki.

 

I want to access the files in the shares, not unassigned devices.

All right. Good luck with it.

Link to comment
2 hours ago, acosmichippo said:

 

I know I can mount SMB shares, but I WANT to passthrough.  And you don't need to put it in quotes as if I made it up, it's right there in the qemu wiki.

 

I want to access the files in the shares, not unassigned devices.

 

Just curious why you want to use 9p protocol for file access? I've read that 9p isn't very efficient so you might find SMB performance more suitable for your needs. There is a 9p kernel extension for OS X so I assume you've added it to your Mac VMs. If not, then that's something you need to try. Perhaps adding the kernel extension will let OS X see the 9p filesystem and then allow you to mount it or access via Finder.

 

https://github.com/benavento/mac9p

 

 

 

 

Link to comment
On 4/20/2020 at 8:59 PM, AgentXXL said:

I've used the MacinaBox docker container to create multiple MacOS VMs and currently have it working for High Sierra, Mojave and Catalina. The only changes made were to the paths required by the docker container and of course selecting the correct OS version. I used the full install method for all 3. Here's a screenshot of my Mojave setup (last one I created). All it required was the 3 changes.

 

MacinaBoxConfig.thumb.jpg.4eb3eec2d47b2cbea2c910973ccd3fb6.jpg

Adding a second MacOS vm different from what`s already setup works fine. But if already running a MacOS vm, and a second vm in the same version, that`s not working for me. The log file on the second vm clearly refering to the first vm, and not making a new app folder. Also tried with "pre-making" the app folder specified in the xml-file.

 

Anybody out there that successfully added a second MacOS vm in the same version as the first vm?

 

 

Cheers,

 

1195949629_Screenshot2020-04-22at19_45_05.thumb.png.7b34206a7ae6745135c3bc14b87d8331.png

 

 

 

 

Second MAcOS-vm logfile:

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Summary of what has been done

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
.
.
The reference /image below refers to where you mapped that folder in the docker template on your server
(normally to /mnt/user/doamins)
.
.
Install media was already present
.
.
Vdisk was already present
.
.
Uptodate clover image was put in /image/MacinaboxMojave
.
.
Compatible OVMF files vere put in /image/MacinaboxMojave/ovmf
.
.
An XML file was already present for MacinaboxMojave you will need to manually delete if you want me to replace this
.
.
OK process has finished at Wed Apr 22 04:28:57 Europe 2020

Link to comment

I am almost in tears right now trying to pass a NVIDIA GeForce GTX 970 to my Catalina VM.  I feel like I have done all of the edits, including making sure that the graphics and sound are on the same bus (VM bus 3) via multifunction.  Can @SpaceInvaderOne or someone please help me? I am not getting any output via HDMI.

 

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  <name>MacinaboxCatalina</name>
  <uuid>79f87c39-f419-489d-94af-868665832168</uuid>
  <description>MacOS Catalina</description>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="default.png" os="Catalina"/>
  </metadata>
  <memory unit='KiB'>8388608</memory>
  <currentMemory unit='KiB'>8388608</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>2</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='1'/>
  </cputune>
  <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>
  <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='qcow2' cache='writeback'/>
      <source file='/mnt/user/domains/MacinaboxCatalina/Clover.qcow2'/>
      <target dev='hdc' bus='sata'/>
      <boot order='1'/>
      <address type='drive' controller='0' bus='0' target='0' unit='2'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/MacinaboxCatalina/Catalina-install.img'/>
      <target dev='hdd' bus='sata'/>
      <address type='drive' controller='0' bus='0' target='0' unit='3'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/MacinaboxCatalina/macos_disk.img'/>
      <target dev='hde' bus='sata'/>
      <address type='drive' controller='0' bus='0' target='0' unit='4'/>
    </disk>
    <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' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <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='0x12'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
    </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='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>
    <interface type='bridge'>
      <mac address='52:54:00:53:41:01'/>
      <source bridge='br0'/>
      <model type='e1000-82545em'/>
      <address type='pci' domain='0x0000' bus='0x01' 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'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0' multifunction='on'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x02' slot='0x00' function='0x1'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x1'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x045e'/>
        <product id='0x07a5'/>
      </source>
      <address type='usb' bus='0' port='2'/>
    </hostdev>
    <memballoon model='none'/>
  </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='************************'/>
    <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>

 

Edited by saskwatch
Link to comment
22 minutes ago, saskwatch said:

I am almost in tears right now trying to pass a NVIDIA GeForce GTX 970 to my Catalina VM.  I feel like I have done all of the edits, including making sure that the graphics and sound are on the same bus (VM bus 3) via multifunction.  Can @SpaceInvaderOne or someone please help me? I am not getting any output via HDMI.

 

 

Hi. Well before i answer this question re the hdmi out I just want to point out that sadly Nvidia cards dont work in macOS Mojave or Catalina. You should still get a picture but no acceleration. There are no drivers since Apple no longer allow them to release them. So High Sierra would be the best OS for you to use with a gtx 970.

However this isnt why you are getting no output from the hdmi.

I would check in your clover configuration that you have under SMBIOS that product model is imac14,1. Some system definitions you will get a black screen otherwise.

Also sometimes the gpu outputs out of the 'wrong' port. You may have to try the dvi/display port out (you can use an adapter to convert it to hdmi)

hope this helps

610461759_ScreenShot2020-04-22at21_05_13.thumb.png.94e654a620417699061003a502d6cf64.png

 

  • Like 2
Link to comment

I'd want to specify that some nvidia cards are still natively supported in mojave/catalina, I have a gtx titan black working very good with the latest catalina.

Natively supported nvidia cards:

Nvidia Kepler Cards that are Natively Supported:

 

GTX Titan (GK110)

GTX Titan Black (GK110)

GTX Titan Z

GTX 780/Ti

GTX 770

GTX 760/Ti

GT 740

GT 730

GT 720

GT 710

GTX 690

GTX 680

GTX 670

GTX 660/Ti

GTX 650/Ti

GTX 645 (GT 645 is Fermi)

GT 640 (Kepler edition, GK107/208 core)

GT 630 (Kepler edition, GK208 core)

Quadro 410

Quadro K420

Quadro K600

Quadro K2000/D

Quadro K4000/D

Quadro K4200

Quadro K5000

Quadro K5200

Quadro K6000

Quadro NVS510

  • Like 1
Link to comment

@ghost82 and @SpaceInvaderOne if it was a different time in the world, I would hug you both for just replying. I thought @SpaceInvaderOne said that nvida was supported in Catalina, so I threw in my 970 hoping for the best.  I tried all the three outputs to no avail.  I will look into my clover config, but I am thinking it might be simpler and less maddening to buy a cheap AMD card. Any suggestions?

Link to comment
12 minutes ago, ghost82 said:

I'd want to specify that some nvidia cards are still natively supported in mojave/catalina, I have a gtx titan black working very good with the latest catalina.

Natively supported nvidia cards:

Nvidia Kepler Cards that are Natively Supported:

 

...

 

GTX 650/Ti

...

I just so happen to have GTX 650/Ti!!! I am going to try that! I am still interested in a good AMD card.  Who knows, if this works, maybe I might want to video edit or something - LOL!

Link to comment
4 minutes ago, saskwatch said:

Who knows, if this works, maybe I might want to video edit or something - LOL!

It should work oob, make sure to inject also lilu and whatevergreen kexts as said before.

Here a list of amd cards, just choose one with oob=yes.

Before buying one make sure it's 100% compatible.

https://www.tonymacx86.com/threads/radeon-compatibility-guide-ati-amd-graphics-cards.171291/

  • Like 1
Link to comment
6 hours ago, frodr said:

Adding a second MacOS vm different from what`s already setup works fine. But if already running a MacOS vm, and a second vm in the same version, that`s not working for me. The log file on the second vm clearly refering to the first vm, and not making a new app folder. Also tried with "pre-making" the app folder specified in the xml-file.

 

Anybody out there that successfully added a second MacOS vm in the same version as the first vm?

 

 

Cheers,

 

1195949629_Screenshot2020-04-22at19_45_05.thumb.png.7b34206a7ae6745135c3bc14b87d8331.png

 

 

 

 

Second MAcOS-vm logfile:

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Summary of what has been done

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
.
.
The reference /image below refers to where you mapped that folder in the docker template on your server
(normally to /mnt/user/doamins)
.
.
Install media was already present
.
.
Vdisk was already present
.
.
Uptodate clover image was put in /image/MacinaboxMojave
.
.
Compatible OVMF files vere put in /image/MacinaboxMojave/ovmf
.
.
An XML file was already present for MacinaboxMojave you will need to manually delete if you want me to replace this
.
.
OK process has finished at Wed Apr 22 04:28:57 Europe 2020

 

Based on what you've experienced and what's showing from the logs, it looks like you left the appdata and Basesystem paths pointing to the same folder named MacinaboxMojave.... one can be named that, but the second instance should be named something else like MacinaboxMojave2. EDIT: Sorry, thought the image in your reply was the one I posted - and your image shows that you definitely changed the path to something else: 211_mib_macos. But my findings were the same.

 

Assuming you have left the defaults as they stand, there should be a unique folder for each VM under /mnt/user/domains. The fact that it says the  install media and vdisk are present means it's definitely still pointed at the same paths as your other Mojave VM. So to verify I just tried changing the paths in my Macinabox Docker container to MacinaboxMojave2 and sure enough I got the same log response you did.

 

There's definitely an issue in the Docker container as it ignored the new paths and just referred to the existing MacinaboxMojave vdisk and install media. I note that the log says the files were put in the /image/MacinaboxMojave/* folder yet in the Docker, there doesn't seem to be a path or mountpoint called /image. I suspect part of the script that runs when the Macinabox Docker container is started is hard-coded to the /image path.

 

I haven't had a look at the Docker container or any of it's components yet, but I suspect it's a simple pathing issue that @SpaceInvaderOne will have to fix.

Edited by AgentXXL
spelling and grammar; clarification after re-reading
Link to comment
On 4/21/2020 at 6:34 AM, Donnii said:

is there a way to passthrough the rx5700xt? I tried many times but the whole system freezes up on me :(

I was using a PowerColor 5700xt Red Dragon for a while without any issues initially but I assigned it to my Win10 VM for gaming performance. Also the MacOS drivers are not tweaked for power efficiency so I found even at idle the card was sucking 100W. It just worked OOB with up to date Clover, Lilu and WateverGreen. I can't remember if I bothered to pass a bios or not, so that is something to try. I did have an issue with the system hard locking on VM shutdown occasionally (can't remember if it ever happened on startup) and it turned out to be a problem with releasing it off the PCIe bus after Unraid had initially grabbed it on boot. (It was installed in the first PCIe slot on my x570 ASRock motherboard.) So I just added it to the BIND list using the VFIO-PCI plug-in and no issue since.

 

12 hours ago, saskwatch said:

I am thinking it might be simpler and less maddening to buy a cheap AMD card. Any suggestions?

I have been using a Yeston RX550 and it works great OOB 10.15.x. If you don't need a single slot card then the Sapphire Pulse RX550 would be a few $ cheaper and easier to get. The advantage of the 500 series is that it's a modern architecture supporting all the latest specs (Hardware H264, HEVC, OpenGL 4.5, Vulkan, DirectX 12, Displayport 1.4, HDMI 4K 60Hz) and not likely to be deprecated out of MacOS any time soon.

 

On 4/17/2020 at 1:18 AM, Spritzup said:

However I have the disk hosted on a NVMe drive and am not seeing the performance I'm expecting.  For comparison I'm seeing nearly 4 times the performance on an equivalent Windows 10 VM.  I suspect the limiting factor is having to use the SATA interface for the drive... is their anyway to change it so that it's still picked up by Catalina?

I'm running off a Samsung 970 Evo getting about 2800MB/2400MB read/write speeds. Not quite bare metal but more than acceptable.
I have carved off the drive by added it to the BIND list using the VFIO-PCI plug-in. Then set the Primary Vdisk to "None" and added it from the Other PCI Devices list. My VM XML code is included below.

    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
      </source>
      <boot order='1'/>
      <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/>
    </hostdev>

My setup is a bit different to how Macinabox does it because I have Mac/Clover boot directly off the raw drive. I don't use a boot qcow2 image. I just found it easier this way. Also means that I can boot the drive directly on the machine without Unraid if needed.

  • Thanks 1
Link to comment
12 hours ago, AgentXXL said:

 

Based on what you've experienced and what's showing from the logs, it looks like you left the appdata and Basesystem paths pointing to the same folder named MacinaboxMojave.... one can be named that, but the second instance should be named something else like MacinaboxMojave2. EDIT: Sorry, thought the image in your reply was the one I posted - and your image shows that you definitely changed the path to something else: 211_mib_macos. But my findings were the same.

 

Assuming you have left the defaults as they stand, there should be a unique folder for each VM under /mnt/user/domains. The fact that it says the  install media and vdisk are present means it's definitely still pointed at the same paths as your other Mojave VM. So to verify I just tried changing the paths in my Macinabox Docker container to MacinaboxMojave2 and sure enough I got the same log response you did.

 

There's definitely an issue in the Docker container as it ignored the new paths and just referred to the existing MacinaboxMojave vdisk and install media. I note that the log says the files were put in the /image/MacinaboxMojave/* folder yet in the Docker, there doesn't seem to be a path or mountpoint called /image. I suspect part of the script that runs when the Macinabox Docker container is started is hard-coded to the /image path.

 

I haven't had a look at the Docker container or any of it's components yet, but I suspect it's a simple pathing issue that @SpaceInvaderOne will have to fix.

Thanks for testing, and finding the same result as I did. It would be nice to have a confirmation from @SpaceInvaderOne, and maybe a fix.

Edited by frodr
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.