[Support] SpaceinvaderOne - Macinabox


1864 posts in this topic Last Reply

Recommended Posts

Many thanks SpaceInvaderOne for the tutorial and container :) 

I'm up and running, but I have a couple of weird issues related to graphics (no actual GPU in system) when I access the system remotely:

VNC - (Via browser) -  I get disappearing text or blocked-out screen elements

ARD - Same
Splashtop - Same

--See attached image for example in the address bar of chrome.  Other than this, things seem to work really well.  Didn't have this issue in other Older KVM installs (SpaceInvaderOne instructions).


Any ideas as to what's up? 

 

TIA!

(xml here:)

http://ecklund.us/paste/?9d8d1ceed586f3e3#kauMS0SvxZFzg3DNUpYgTSltmK2daPMdSo8T38Nxm6g=

Screen Shot 2020-02-06 at 8.10.19 PM.png

Link to post
  • Replies 1.9k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

PLEASE - PLEASE - PLEASE EVERYONE POSTING IN THIS THREAD IF YOU POST YOUR XML FOR THE VM HERE PLEASE REMOVE/OBSCURE THE OSK KEY AT THE BOTTOM. IT IS AGAINST THE RULES OF THE FORUM FOR OSK K

09 Dec 2020   Basic usage instructions.   Macinabox needs the following other apps to be installed. CA User Scripts (macinabox will inject a user script. This is what fixes th

Do you like this for an icon? I think its appropriate.

Posted Images

Hi everyone,

 

@SpaceInvaderOne thanks for making an amazing docker!

 

I recently migrated my Intel i5 server to a new Ryzen board and CPU and it hasn't been as a simple to get my Mac OS VM working.

 

I have finally gotten my MSI Radeon RX 570 to passthrough, however I seem to get stuck on the Apple logo on boot for Catalina and cannot seem to figure out how to get passed it. It doesn't even show the progress bar. There is nothing I can see in my logs that hint at what the issue is. I have tried a clean install and get the same issue.

 

My hardware is the ASRock X570 Taichi with Ryzen 9950X 

 

Below is my XML and attached is my server diagnosis file:

 

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  <name>MacinaboxCatalina</name>
  <uuid>483b033b-dafb-4ded-aac1-86fae9be9316</uuid>
  <description>MacOS Catalina</description>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="default.png" os="Catalina"/>
  </metadata>
  <memory unit='KiB'>33554432</memory>
  <currentMemory unit='KiB'>33554432</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>12</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='10'/>
    <vcpupin vcpu='1' cpuset='26'/>
    <vcpupin vcpu='2' cpuset='11'/>
    <vcpupin vcpu='3' cpuset='27'/>
    <vcpupin vcpu='4' cpuset='12'/>
    <vcpupin vcpu='5' cpuset='28'/>
    <vcpupin vcpu='6' cpuset='13'/>
    <vcpupin vcpu='7' cpuset='29'/>
    <vcpupin vcpu='8' cpuset='14'/>
    <vcpupin vcpu='9' cpuset='30'/>
    <vcpupin vcpu='10' cpuset='15'/>
    <vcpupin vcpu='11' cpuset='31'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-q35-3.1'>hvm</type>
    <loader readonly='yes' type='pflash'>/mnt/disks/Samsung_SSD_960_PRO_512GB_S3EWNX0JA08097W/MacinaboxCatalina/ovmf/OVMF_CODE.fd</loader>
    <nvram>/mnt/disks/Samsung_SSD_960_PRO_512GB_S3EWNX0JA08097W/MacinaboxCatalina/ovmf/OVMF_VARS.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='12' threads='1'/>
  </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/disks/Samsung_SSD_960_PRO_512GB_S3EWNX0JA08097W/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/disks/Samsung_SSD_960_PRO_512GB_S3EWNX0JA08097W/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/disks/Samsung_SSD_960_PRO_512GB_S3EWNX0JA08097W/MacinaboxCatalina/macos_disk.img'/>
      <target dev='hde' bus='sata'/>
      <address type='drive' controller='0' bus='0' target='0' unit='4'/>
    </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='0xa'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
    </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:2e:de:16'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <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='0x0e' slot='0x00' function='0x0'/>
      </source>
      <rom file='/mnt/disks/Samsung_SSD_960_PRO_512GB_S3EWNX0JA08097W/MacinaboxCatalina/MSI.RX570.8192.180304.rom'/>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x0e' slot='0x00' function='0x1'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x05ac'/>
        <product id='0x024f'/>
      </source>
      <address type='usb' bus='0' port='2'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x1532'/>
        <product id='0x0043'/>
      </source>
      <address type='usb' bus='0' port='3'/>
    </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=DELETED
    <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,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check'/>
  </qemu:commandline>
</domain>


Any thoughts on what could be causing this?

fosterserver-diagnostics-20200207-2259.zip

Link to post

I have tried and failed to get Macinabox to work for me on either Mojave or Catalina.  The Macinabox docker is configured like this:

 

1300144540_MacinaboxDockerconfig.thumb.png.e112cdef5df7a876de342f5c82a90833.png

 

I get a (supposedly) successful install of macinabox VM:

 

Macinabox Catalina install Log.rtf

 

using a VM config of:

 

Macinabox Catalina VM XML.rtf

 

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:

 

342025675_MacinaboxServerspecs.thumb.png.b5816ae5fc435ab8bb41492721bcd1dd.png

 

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

 

 

 

Link to post
13 hours ago, rctneil said:

I have this set up and working but how can i access the files stored on my Unraid?  How can i map locations on the server to locations in MacOS?

I'm successfully using unassigned devices + shares to access unraid files and other disks on mac os.

Link to post

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!

Link to post

Installed HighSiera by following your video which works fine until I make any change via the vm template (yes I edited the xml afterwords and added the xml at the bottom from line 136 on. Also added the icon location back correct in xml. Then on reboot it just goes to clover install again, not boot the installed HighSiera. So I added back the correct loader & nvram info in xml which fixes the boot issue. But at this point any changes in vm template breaks the vm even after adding the custom lines from 136 on back in xml. So I added everything in template I want including Nvidia RTX 2060 gpu passthrough and compare the new created xml with the previuous working xml. I then replace in the new created xml from the vm template lines 136 and so on back to the bottom, the icon location, the correct type of nic, the correct loader info, the correct nvram info and it boots all the way up but with 4 little screens side by side at top of the screen. Any idea what is causing this or what I may be doing wrong?

 

Unraid Nvidia 6.8.2

 

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

Edited by jpowell8672
Link to post
2 hours ago, jpowell8672 said:

Installed HighSiera by following your video which works fine until I make any change via the vm template (yes I edited the xml afterwords and added the xml at the bottom from line 136 on. Also added the icon location back correct in xml. Then on reboot it just goes to clover install again, not boot the installed HighSiera. So I added back the correct loader & nvram info in xml which fixes the boot issue. But at this point any changes in vm template breaks the vm even after adding the custom lines from 136 on back in xml. So I added everything in template I want including Nvidia RTX 2060 gpu passthrough and compare the new created xml with the previuous working xml. I then replace in the new created xml from the vm template lines 136 and so on back to the bottom, the icon location, the correct type of nic, the correct loader info, the correct nvram info and it boots all the way up but with 4 little screens side by side at top of the screen. Any idea what is causing this or what I may be doing wrong?

 

Unraid Nvidia 6.8.2

 

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

 

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.

Edited by jpowell8672
Link to post
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

Link to post
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. :(

 

Link to post
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 :)

 

Link to post

@SpaceInvaderOne Thanks for all of your hard work with unraid/virtualization -- Have you experienced the VNC / Splashtop graphics issues that I mentioned here:  https://forums.unraid.net/topic/84601-support-spaceinvaderone-macinabox/?do=findComment&comment=820154

 

Sorry to bump/ask again.  I'm just curious to know if you have a thought about why this is. 

 

Thanks!

Link to post

Hi Guys,

 

Have been running Mojave VM for a while now with VMX features enabled. After upgrading from 6.8.0 to either 6.8.1 or 6.8.2, I am getting the following in VM log and virtualization stopped working inside the Mac VM.

 

2020-02-11T14:42:00.754322Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48FH).vmx-exit-load-perf-global-ctrl [bit 12]
2020-02-11T14:42:00.754328Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48FH).vmx-exit-ack-intr [bit 15]
2020-02-11T14:42:00.754332Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(490H).vmx-entry-ia32e-mode [bit 9]
2020-02-11T14:42:00.754337Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(490H).vmx-entry-load-perf-global-ctrl [bit 13]
2020-02-11T14:42:00.754341Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(485H).vmx-activity-hlt [bit 6]
2020-02-11T14:42:00.754345Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(480H).vmx-ins-outs [bit 54]
2020-02-11T14:42:00.756593Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
2020-02-11T14:42:00.756615Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48EH).vmx-vintr-pending [bit 2]
2020-02-11T14:42:00.756621Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48EH).vmx-tsc-offset [bit 3]
2020-02-11T14:42:00.756626Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48EH).vmx-hlt-exit [bit 7]
2020-02-11T14:42:00.756631Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48EH).vmx-invlpg-exit [bit 9]
2020-02-11T14:42:00.756636Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48EH).vmx-mwait-exit [bit 10]
2020-02-11T14:42:00.756641Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48EH).vmx-rdpmc-exit [bit 11]
2020-02-11T14:42:00.756646Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48EH).vmx-rdtsc-exit [bit 12]
2020-02-11T14:42:00.756651Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48EH).vmx-cr8-load-exit [bit 19]
2020-02-11T14:42:00.756656Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48EH).vmx-cr8-store-exit [bit 20]
2020-02-11T14:42:00.756661Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48EH).vmx-flexpriority [bit 21]
2020-02-11T14:42:00.756666Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48EH).vmx-vnmi-pending [bit 22]
2020-02-11T14:42:00.756671Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48EH).vmx-movdr-exit [bit 23]
2020-02-11T14:42:00.756676Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48EH).vmx-io-exit [bit 24]
2020-02-11T14:42:00.756681Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48EH).vmx-io-bitmap [bit 25]
2020-02-11T14:42:00.756686Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48EH).vmx-msr-bitmap [bit 28]
2020-02-11T14:42:00.756691Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48EH).vmx-monitor-exit [bit 29]
2020-02-11T14:42:00.756696Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48EH).vmx-pause-exit [bit 30]
2020-02-11T14:42:00.756700Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48EH).vmx-secondary-ctls [bit 31]
2020-02-11T14:42:00.756705Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48BH).vmx-apicv-xapic [bit 0]
2020-02-11T14:42:00.756711Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48BH).vmx-wbinvd-exit [bit 6]
2020-02-11T14:42:00.756716Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48DH).vmx-intr-exit [bit 0]
2020-02-11T14:42:00.756721Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48DH).vmx-nmi-exit [bit 3]
2020-02-11T14:42:00.756726Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48DH).vmx-vnmi [bit 5]
2020-02-11T14:42:00.756731Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48FH).vmx-exit-load-perf-global-ctrl [bit 12]
2020-02-11T14:42:00.756752Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48FH).vmx-exit-ack-intr [bit 15]
2020-02-11T14:42:00.756757Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(490H).vmx-entry-ia32e-mode [bit 9]
2020-02-11T14:42:00.756780Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(490H).vmx-entry-load-perf-global-ctrl [bit 13]
2020-02-11T14:42:00.756785Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(485H).vmx-activity-hlt [bit 6]
2020-02-11T14:42:00.756789Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(480H).vmx-ins-outs [bit 54]

Attached is my XML config for the VM. Any help is greatly appreciated. I need the VMX feature set to work with Docker inside my VM.

MacinaboxMojave.xml

Link to post
On 1/27/2020 at 9:06 AM, ghost82 said:

Then in clover configuration you have to be sure that InjectKexts is set to "yes".

Hi @ghost82

Is there any way to find out, if the kexts are loaded? I set this option to "yes".

The GPU is not working I tried all ports: DVI, DP, HDMI -> no signal and the display of "NoMachine" (kind of VNC-Software) remains white. I can't do anything with the VM when I put the GPU in the VM config 😕

Edited by SignorRossi
Link to post

Hi everybody, this is my very first post here.

 

I first would like to deeply thankSpaceInvaderOne for all his work: I knew nothing about VMs, and going through his videos I managed to get one working perfectly!

 

Now to my questions.

My sole purpose of using unraid is to easily setup a powerful hackintosh without too many headaches. So I would like to reserve for unraid as little resources as possible, and to passthrough ad much as possible to the hackintosh vm.

At the moment, this is my configuration: i9 7980xe, Asus X299 TUF MK2, PowerColor Vega 56.

 

With Macinabox, I installed Mojave and - thanks to SpaceInvaderOne videos and the forum - I managed to passthrough usb devices, a usb controller, onboard audio and a gpu.

 

However: I can successfully passthrough Vega 56 only installing it on the second slot, with another gpu on the first one. Specifying a rom file does not help and stubbing the device in the Syslinux configurator did not help either.

I would be ok to sacrifice a slot, but since I read it is not necessary, I would like to solve the issue.

Moreover, I get six instances of “Digital-out (HDMI)” in System Preferences - Sound. It seems weird as the card has 2 HDMIs and 2 DPs. It is only cosmetically disturbing, so I could live with it.

 

The USB controller I am passing through is a ASMedia ASM2142. It is supposed to be natively supported, but plugging in devices seem to have no effect. I need to research more into this.

 

Changing the description from Penryn to Ivy Bridge seems to give me better performances, jumping from 9211 to 9602 in Cinebench r20 (though still far from the 10153 I get in baremetal Win10).

 

The motherboard I am using has a quite poor IOMMU groups management and I am thinking about buying a different X299 motherboard.

However, the fact that to setup a working Mojave VM was quite easy after all (thanks to the informations that I found here or in youtube) makes me wonder whether I should replace my system with an AMD 3960x or 3970x instead. Most of my workflow is CPU bound and I could use all those cores.

Would there be any significant difference in the setup of a Mojave or Catalina VM switching to AMD?

 

Thank you for your help and advices!

Link to post
23 minutes ago, SignorRossi said:

 

Is there any way to find out, if the kexts are loaded? I

 

Download IORegistryExplorer and search for your extension by name. If it shows up, it's loaded. Here's me looking for WhateverGreen...

 

ioregsiteryexplorer.png.2864fbb0ae9d4406d8d3843b1a9c6376.png

Link to post
3 minutes ago, Matteo said:

Hi everybody, this is my very first post here.

 

I first would like to deeply thankSpaceInvaderOne for all his work: I knew nothing about VMs, and going through his videos I managed to get one working perfectly!

 

Now to my questions.

My sole purpose of using unraid is to easily setup a powerful hackintosh without too many headaches. So I would like to reserve for unraid as little resources as possible, and to passthrough ad much as possible to the hackintosh vm.

At the moment, this is my configuration: i9 7980xe, Asus X299 TUF MK2, PowerColor Vega 56.

 

With Macinabox, I installed Mojave and - thanks to SpaceInvaderOne videos and the forum - I managed to passthrough usb devices, a usb controller, onboard audio and a gpu.

 

However: I can successfully passthrough Vega 56 only installing it on the second slot, with another gpu on the first one. Specifying a rom file does not help and stubbing the device in the Syslinux configurator did not help either.

I would be ok to sacrifice a slot, but since I read it is not necessary, I would like to solve the issue.

Moreover, I get six instances of “Digital-out (HDMI)” in System Preferences - Sound. It seems weird as the card has 2 HDMIs and 2 DPs. It is only cosmetically disturbing, so I could live with it.

 

The USB controller I am passing through is a ASMedia ASM2142. It is supposed to be natively supported, but plugging in devices seem to have no effect. I need to research more into this.

 

Changing the description from Penryn to Ivy Bridge seems to give me better performances, jumping from 9211 to 9602 in Cinebench r20 (though still far from the 10153 I get in baremetal Win10).

 

The motherboard I am using has a quite poor IOMMU groups management and I am thinking about buying a different X299 motherboard.

However, the fact that to setup a working Mojave VM was quite easy after all (thanks to the informations that I found here or in youtube) makes me wonder whether I should replace my system with an AMD 3960x or 3970x instead. Most of my workflow is CPU bound and I could use all those cores.

Would there be any significant difference in the setup of a Mojave or Catalina VM switching to AMD?

 

Thank you for your help and advices!

One thing you don't mention, and worth a try. Are you booting UnRaid in UEFI mode? If yes, try legacy (and vice versa).

 

I found switching from UEFI to Legacy made a lot of issues I was having with AMD graphics passthrough disappear.

 

You can find the setting under Main -> Boot device -> Flash -> Syslinux;

 

bootmode.thumb.png.b55f6c64c899a192d3e4e98c2b2e91ad.png

 

 

Link to post

I tried with open core and the qcow2 image shared in this post. I manage to boot when using VNC, but never reach the loggin page with the 5700XT passed through. If someone managed to make it work, hints would be greatly appreciated.

Edited by dboris
Link to post

Hey everyone,

 

I created a Catalina VM that is working with no issues.

 

Two quick questions that I'm hoping someone can help me with:

 

1. Can I change the name of the VM that's going to be created?

2. How can I create additional macOS VMs after creating the first one.

 

Any help is appreciated!

 

 

Link to post

  

On 2/11/2020 at 4:46 AM, SpaceInvaderOne said:

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.

 

@SpaceInvaderOne Thanks a bunch for this! I'm working on getting this up and running on my Unraid box and kept running into an issue when I'd try to add CPU cores. I didnt catch that these lines were being altered when I reset as the video did not mention them and I was not observant enough on my own. I was just about to run a diff between a copy of the original XML and its altered state after applying in form view when I found this comment. Saved the day! Or, at least, a lot of time :D

Edited by swallace
Link to post
On 2/11/2020 at 9:46 AM, SpaceInvaderOne said:

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.

 

 

Hope this helps :)

 

Ed

 

You are so right - and I knew that too.  Don't know why it slipped my mind!

 

Thanks again.  All is up and running well now.  Apart from my Nvidia GPU passthrough on Catalina :(.  Did you do a video which is relevant to this and Macinabox?

 

Cheers

 

D

Edited by adgilcan
Link to post

Just found another user commenting on @SpaceInvaderOne’s youtube channel facing the same issue as me.

 

The Photos tab within the Photos app disappeared in Catalina. This was not the case with a Mojave VM and also not with a macbook running Catalina. Then issue in Catalina VM happens both when installing Catalina directly and when installing Mojave VM first and then upgrading to Catalina.

 

Any thoughts?

Link to post

Hi guys ! And welcome to another question...

I've read all this topic and all I could find elsewhere. I watched multiple time many of Spaceinvaderone's video and in a last resort I'm turning to the community for help.

 

So. I have : Ryzen7, X570, GT710 slot1, GTX780 slot2. My W10 vm runs fine with either of the two GPU passed through (for the GT710 I load the ROM I found (and trimmed) on TechPowerUp). For both card, I use the HDMI output.

 

After installing CATALINA thanks to @SpaceInvaderOne I have a running OSX. I could even passthrough my GTX 780 without any tweaks (well I thing I changed Product Model Number to 14.2).

 

But, passing through the GT 710 (with rom) which is my primary card gives me and endless bootloop. 

 

So, is the problem coming from :

- the fact that the GT 710 is primary GPU (eventhough I load the bios and the same confi works fine in W10 vm) ?

- it can boot on the GT 710 but is CATALINA missing something that causes the boot to fail ?

- i have no idea what I'm doing and I even couldn't post my problem in the right thread...

 

I do not get it that it works with the 780 and not with the 710... I'm really thinking this is a slot1/slot2 problem... Please do not tell me to swap the GPU's...

 

 

Edited by bjornatic
Link to post

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.