[Support] SpaceinvaderOne - Macinabox


2070 posts in this topic Last Reply

Recommended Posts

On 4/7/2021 at 9:49 PM, mSedek said:

Never say never.. say "up until now is not available"... anyways just downloaded genymotion (virtualbox based) and is working like a charm for my android studio high end SENIOR LEVEL development..

Because virtualbox provides its own hypervisor cpu instruction set. I was talking about macOS's native hypervisor. Until someone writes a kernel extension to add AMD-V (SVM) support to the kernel and the hypervisor framework for macOS, anything that uses the native macOS hypervisor will not work.

Link to post
  • Replies 2.1k
  • 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

Sure is. When Big Sur is released officially a new Macinabox will be out. With a bunch of new features and choice between opencore and clover bootloaders.

Posted Images

8 hours ago, cat2devnull said:

Since both sound devices are not working you either have a separate issue effecting each device or one issue taking out both.

 

I probably have a very similar setup (AsRock x570 Phantom Gaming X) board. I am using HDMI audio on both my Mac and Win VMs because that way as I switch monitor input the audio source is switched at the same time. I take the audio output from my monitor and pass it to my speakers/headphones.
The only issue is when using Mac with HDMI audio you loose volume control so I paid $19 for Sound Control which gives fixes a lot of Mac audio shortcomings.
Make sure you have your video card passed through correctly (as is often discussed in this forum).
 


    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x12' slot='0x00' function='0x0'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0' multifunction='on'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x12' slot='0x00' function='0x1'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/>
    </hostdev>


Make sure you have multifunction enabled correctly and are assigning to the same bus. As per my example above;

bus='0x12' slot='0x00' function='0x0' ---> bus='0x04' slot='0x00' function='0x0' multifunction='on'

bus='0x12' slot='0x00' function='0x1' ---> bus='0x04' slot='0x00' function='0x1'

Your card looks like it is on bus 0x0b, I can't see where it is assigned too as you haven't posted your XML.

Remember the GUI will not set this up correctly, it will not use multifunction and will put them on different destination busses.

 

As for both audio devices. They should show up easily. You just need Lilu, WhateverGreen and AppleALC kexts. I have read a few posts reporting issues with the onboard Realtek chip, until adding boot-args alcid=1 or alcid=11.

Make sure you have the latest versions of the kexts as they are adding new layout-ids all the time.

 

Just something to start with. Let us know how you go. If no luck, I should be able to pass through my onboard card and take a look for you. Just might be a day or two till I have a chance.

Thank you so much! It now works sound over hdmi to my display. I updated all kext files and also tried it with alcid=1 and alcid=11 (not both at once). But still I cant get my onboard sound passthroughed xD 

Maybe I'll look into this later.

Thank you for your great help with my HDMI Sound. Appriciate it!

Link to post

Need some help with Macinabox and High Sierra. I tried Googling around and couldn't find anything.

1. What do I need to do with OpenCore Configurator in High Sierra? It seems different than the Big Sur example in the video. I also can't see the main drive to mount to copy EFI and Nvars to the main disk.

2. If I have to hit enter when it boots up, how can I pass a graphics card to use something other than VNC? With a graphics card passed through, I can't press enter for it to continue.

3. How do I pass through a DVD drive from the server in High Sierra?

4. Is there any reason to keep the macinabox docker running after the creation of the VM?

Edited by nraygun
Link to post

Wondering if someone could shed some light on my situation..  I installed Macinabox Bigsur on a unassigned device as a vdisk and everything seems to working fine except when I try to copy files from the Bigsur vdisk to and from Unraid it just fails..  I don't know what im doing wrong..  file transfers work perfectly fine when I copy to and from my windows 10 vdisk?

 

 

Link to post
1 hour ago, ryanleeis said:

Wondering if someone could shed some light on my situation..  I installed Macinabox Bigsur on a unassigned device as a vdisk and everything seems to working fine except when I try to copy files from the Bigsur vdisk to and from Unraid it just fails..  I don't know what im doing wrong..  file transfers work perfectly fine when I copy to and from my windows 10 vdisk?

 

 

Most probably it's related to the smb/e1000/big sur issue; use virtio-net for network and most probably your issue will disappear.

Link to post
On 4/11/2021 at 12:31 AM, nraygun said:

Need some help with Macinabox and High Sierra. I tried Googling around and couldn't find anything.

1. What do I need to do with OpenCore Configurator in High Sierra? It seems different than the Big Sur example in the video. I also can't see the main drive to mount to copy EFI and Nvars to the main disk.

2. If I have to hit enter when it boots up, how can I pass a graphics card to use something other than VNC? With a graphics card passed through, I can't press enter for it to continue.

3. How do I pass through a DVD drive from the server in High Sierra?

4. Is there any reason to keep the macinabox docker running after the creation of the VM?

Opencore configurator is just an app with a gui to "easily" configure opencore: I don't recommend to use it as it can mess your configuration file. Use a plist editor or the simple text edit to make modifications.

Post a picture of the efi mounter window, as it's strage you don't see the bootloader drive. By the way it's not mandatory to move the efi from the bootloader image to the main drive, I prefer to have them separated.

As far as the gpu passthrough all you need is a compatible gpu (refer to dortania website or search this forum for conpatible gpus), lilu and whatevergreen kexts injected by the bootloader (preferred) or installed in mac os (for high sierra). Opencore ahas a timeout to boot the main drive so you don't need to hit enter, if it doesn't boot your issue is with the gpu.

Never tried to passthrough a dvd drive, but also in this case you need a compatible drive with mac os and a system which in real has a dvd drive (as an example the imac pro doesn't have a dvd drive, so I don't think it's possible to pass a dvd drive).

No particular reason to keep macinabox, if you used it to install a mac os vm and you don't need it anymore, but it's your choice. Pay attention if you remove it to not remove other things needed by the vm, for example ovmf_code and vars files.

Edited by ghost82
Link to post
1 hour ago, ghost82 said:

Most probably it's related to the smb/e1000/big sur issue; use virtio-net for network and most probably your issue will disappear.

thanks.. how do I change to that?  is there something I can read about somewhere ?

Link to post
12 minutes ago, ryanleeis said:

thanks.. how do I change to that?  is there something I can read about somewhere ?

Go to vm tab, edit your vm, click on advanced edit to modify the xml code search for the network code, you will find <model type='e1000-82545em'/> or vmxnet3, try to change to:

<model type='virtio-net'/>

save, reboot and try

Edited by ghost82
Link to post
4 hours ago, ghost82 said:

Go to vm tab, edit your vm, click on advanced edit to modify the xml code search for the network code, you will find <model type='e1000-82545em'/> or vmxnet3, try to change to:


<model type='virtio-net'/>

save, reboot and try

that worked .  thanks so much !

Link to post
8 hours ago, ryanleeis said:

that worked .  thanks so much !

take into account that @bjornatic tested big sur 11.3 beta 5 and he said that the issue about "failed copying files with smb" with the e1000 driver was gone (some of us, including me, had this issue from big sur 11.0 beta 6).

virtio-net driver has the drawback of not reconnecting the network after a sleep/wake; if you don't use it (as me), you can continue to use that driver, otherwise wait for the 11.3 stable release of big sur, as maybe apple fixed the e1000 driver.

Edited by ghost82
Link to post

Hi All,

 

Well, I have been trying to make this docker do something, but I seem to not get further than this according to the docker logs:

 

Quote

******************************************************************************
Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet?

The scheme stores pixel data offscreen on the VNC viewer side for faster
retrieval. It should work with any VNC viewer. Try it by running:

x11vnc -ncache 10 ...

One can also add -ncache_cr for smooth 'copyrect' window motion.
More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching

 

 

The docker is just sits there in this state forever... tried with method 1 and 2.

Anyone has some tips? And sorry if this was brought up before...

 

Thanks!

 

Link to post

Hoping someone can help me.

 

I'm trying to install High Sierra.  I followed the guide exactly, and it downloaded the correct dmg for highsierra, but when I go to install the OS on the drive, after formatting the drive and renaming it "highsierra", it installs big sur instead.

 

Given that I have a gtx 1080ti, I have no use for big sur.  If anyone can help me figure out why this is happening, I would appreciate it.

 

Every indication tells me that I should be installing highsierra (according to whats shown in the macinabox docker container settings, and the VM template), but it always installs bigsur for some reason.

 

Thanks

Edited by huapua
Link to post
On 6/20/2020 at 12:25 PM, happythatsme said:

 

Hi Grizzle, 

 

Did you get your RX5700 working ? 

 

I managed to get it working for me, however, i had to pass the rom file and enable multifunction, I didnt have to do this in windows. 

 

I also passedthrough an NVME drive for video editing. 

 


 <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
      </source>
      <alias name='hostdev0'/>
      <rom file='/mnt/user/isos/Powercolor.RX5700XT.8176.190808.rom'/>
      <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='0x05' slot='0x00' function='0x1'/>
      </source>
      <alias name='hostdev1'/>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x1'/>
    </hostdev>

 

Full XML: 


<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' id='1' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  <name>MacinaboxCatalina</name>
  <uuid>ae14c64c-03cc-4b73-a006-85958f10c075</uuid>
  <description>MacOS Catalina</description>
  <metadata>
    <vmtemplate xmlns="unraid" name="MacOS" icon="/mnt/user/domains/MacinaboxCatalina/icon/catalina.png" os="Catalina"/>
  </metadata>
  <memory unit='KiB'>8388608</memory>
  <currentMemory unit='KiB'>8388608</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>40</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='12'/>
    <vcpupin vcpu='1' cpuset='44'/>
    <vcpupin vcpu='2' cpuset='13'/>
    <vcpupin vcpu='3' cpuset='45'/>
    <vcpupin vcpu='4' cpuset='14'/>
    <vcpupin vcpu='5' cpuset='46'/>
    <vcpupin vcpu='6' cpuset='15'/>
    <vcpupin vcpu='7' cpuset='47'/>
    <vcpupin vcpu='8' cpuset='16'/>
    <vcpupin vcpu='9' cpuset='48'/>
    <vcpupin vcpu='10' cpuset='17'/>
    <vcpupin vcpu='11' cpuset='49'/>
    <vcpupin vcpu='12' cpuset='18'/>
    <vcpupin vcpu='13' cpuset='50'/>
    <vcpupin vcpu='14' cpuset='19'/>
    <vcpupin vcpu='15' cpuset='51'/>
    <vcpupin vcpu='16' cpuset='20'/>
    <vcpupin vcpu='17' cpuset='52'/>
    <vcpupin vcpu='18' cpuset='21'/>
    <vcpupin vcpu='19' cpuset='53'/>
    <vcpupin vcpu='20' cpuset='22'/>
    <vcpupin vcpu='21' cpuset='54'/>
    <vcpupin vcpu='22' cpuset='23'/>
    <vcpupin vcpu='23' cpuset='55'/>
    <vcpupin vcpu='24' cpuset='24'/>
    <vcpupin vcpu='25' cpuset='56'/>
    <vcpupin vcpu='26' cpuset='25'/>
    <vcpupin vcpu='27' cpuset='57'/>
    <vcpupin vcpu='28' cpuset='26'/>
    <vcpupin vcpu='29' cpuset='58'/>
    <vcpupin vcpu='30' cpuset='27'/>
    <vcpupin vcpu='31' cpuset='59'/>
    <vcpupin vcpu='32' cpuset='28'/>
    <vcpupin vcpu='33' cpuset='60'/>
    <vcpupin vcpu='34' cpuset='29'/>
    <vcpupin vcpu='35' cpuset='61'/>
    <vcpupin vcpu='36' cpuset='30'/>
    <vcpupin vcpu='37' cpuset='62'/>
    <vcpupin vcpu='38' cpuset='31'/>
    <vcpupin vcpu='39' cpuset='63'/>
  </cputune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <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'>
    <cache mode='passthrough'/>
    <feature policy='require' name='topoext'/>
  </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' 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='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/MacinaboxCatalina/Catalina-install.img' 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='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/MacinaboxCatalina/macos_disk.img' 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>
    <controller type='sata' index='0'>
      <alias name='ide'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'>
      <alias name='pcie.0'/>
    </controller>
    <controller type='pci' index='1' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x10'/>
      <alias name='pci.1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='2' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='2' port='0x11'/>
      <alias name='pci.2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
    </controller>
    <controller type='pci' index='3' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='3' port='0x12'/>
      <alias name='pci.3'/>
      <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'/>
      <alias name='pci.4'/>
      <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='0x8'/>
      <alias name='pci.5'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <alias name='virtio-serial0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </controller>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <alias name='usb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <alias name='usb'/>
      <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'>
      <alias name='usb'/>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <alias name='usb'/>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <filesystem type='mount' accessmode='passthrough'>
      <source dir='/mnt/user/Media/Wedding/'/>
      <target dir='Wedding'/>
      <alias name='fs0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
    </filesystem>
    <interface type='bridge'>
      <mac address='52:54:00:74:a0:97'/>
      <source bridge='br0'/>
      <target dev='vnet0'/>
      <model type='e1000-82545em'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/0'/>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
      <alias name='serial0'/>
    </serial>
    <console type='pty' tty='/dev/pts/0'>
      <source path='/dev/pts/0'/>
      <target type='serial' port='0'/>
      <alias name='serial0'/>
    </console>
    <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-1-MacinaboxCatalina/org.qemu.guest_agent.0'/>
      <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <alias name='input0'/>
      <address type='usb' bus='0' port='1'/>
    </input>
    <input type='mouse' bus='ps2'>
      <alias name='input1'/>
    </input>
    <input type='keyboard' bus='ps2'>
      <alias name='input2'/>
    </input>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
      </source>
      <alias name='hostdev0'/>
      <rom file='/mnt/user/isos/Powercolor.RX5700XT.8176.190808.rom'/>
      <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='0x05' slot='0x00' function='0x1'/>
      </source>
      <alias name='hostdev1'/>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x1'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x046d'/>
        <product id='0xc52b'/>
        <address bus='5' device='2'/>
      </source>
      <alias name='hostdev2'/>
      <address type='usb' bus='0' port='4'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x047f'/>
        <product id='0xc053'/>
        <address bus='5' device='6'/>
      </source>
      <alias name='hostdev3'/>
      <address type='usb' bus='0' port='5'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
      </source>
      <alias name='hostdev4'/>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </hostdev>
    <memballoon model='virtio'>
      <alias name='balloon0'/>
      <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
    </memballoon>
  </devices>
  <seclabel type='dynamic' model='dac' relabel='yes'>
    <label>+0:+100</label>
    <imagelabel>+0:+100</imagelabel>
  </seclabel>
  <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>

 

I still suffer from the AMD reset bug, i need to restart if i want to switch from MAC to Windows, not ideal, but its working... Spaceinvader mentions it in this video, the script stopped working for me also. 

 

 

 

On 6/20/2020 at 12:25 PM, happythatsme said:

 

 

@happythatsme

 

Doesnt sound to me like its working if you have the FLR reset bug still... Pretty much ANY config i try works for first boot but all fail after restart of VMs

 

@grizzle what about yours? I wanna see if anyone has RX5700 working

Link to post

Hi guys, I'm getting desperate here...

I followed the YT tutorial on how to make a BigSur VM. I'm having two problems.

 

1. The noVNC doesn't pick up my mouse input at all. Keyboard works.

2. Using the keyboard I start the install as in the instruction, but it hangs on the Apple logo and there is no loading bar.

 

What am I doing wrong?

Link to post
On 4/19/2021 at 7:15 PM, hikipoklica said:

Hi guys, I'm getting desperate here...

I followed the YT tutorial on how to make a BigSur VM. I'm having two problems.

 

1. The noVNC doesn't pick up my mouse input at all. Keyboard works.

2. Using the keyboard I start the install as in the instruction, but it hangs on the Apple logo and there is no loading bar.

 

What am I doing wrong?

Maybe try restarting the VM? Because VNC always works for me, when I cracked up my xml file and need to edit it back to get a working gpu-passthrough xD

When the keyboard works normally, than maybe something is wrong within your browser settings (inside the VNC window).

 

What OS you are browsing to your unraid.

Link to post
On 4/18/2021 at 7:58 PM, huapua said:

Hoping someone can help me.

 

I'm trying to install High Sierra.  I followed the guide exactly, and it downloaded the correct dmg for highsierra, but when I go to install the OS on the drive, after formatting the drive and renaming it "highsierra", it installs big sur instead.

 

Given that I have a gtx 1080ti, I have no use for big sur.  If anyone can help me figure out why this is happening, I would appreciate it.

 

Every indication tells me that I should be installing highsierra (according to whats shown in the macinabox docker container settings, and the VM template), but it always installs bigsur for some reason.

 

Thanks

I am also encountering this issue when trying to instal mojave. I have tried both install method 1 and 2 after fully removing both the vm and docker. 

Link to post
On 4/24/2021 at 1:52 AM, supertomcat said:

I am also encountering this issue when trying to instal mojave. I have tried both install method 1 and 2 after fully removing both the vm and docker. 

same problem over here

Link to post
10 hours ago, dennisbhh said:

same problem over here

 

I got this problem a few days back ago too. I justed removed the "app" Macinabox and deleted all userscripts (macinabox) and reinstalled the app within community apps. After this I was able to get which OSX I wanted. 

Maybe this helps?

Link to post

Does anyone managed to update Big Sur 11.2* to Big Sur 11.3? For me it seems to install but after I booted back into mac os (after 15-20 Minutes update installation) it want again to update xD

Link to post

I tried to set this up. Initially I forgot to switch from Catalina to Big sur. After it finished downloading Catalina, I did that and restarted macinabox but the helper script still created the Catalina VM. I managed to delete that VM after some trouble and having to run the command virsh undefine --nvram "Macinabox Catalina" to allow me circumvent the error saying that there is nvram allocated to the domain preventing me from removing the VM in the webUI (this is probably the wrong way to do this but it was the solution that popped up on google), then remove the iso files, the custom_ovmf folder, the disk image, and the macinabox appdata folder and restart macinabox with the correct settings.

 

After doing all that, I got Big Sur loaded and booting. however after selecting MacOS base system for the initial install the apple logo shows up and then a loading bar for a few seconds and then it reboots with the message "your computer restarted because of a problem" on the following install attempt and I am completely unable to advance any farther. 

 

I repeated the reset steps listed above and went back to Catalina and had the same issue. (still currently installed and not working)

 

I have no idea if I messed up or if my server just doesn't want to work. Any assistance would be appreciated.

Edited by lmanstl
Link to post
43 minutes ago, lmanstl said:

I tried to set this up. Initially I forgot to switch from Catalina to Big sur. After it finished downloading Catalina, I did that and restarted macinabox but the helper script still created the Catalina VM. I managed to delete that VM after some trouble and having to run the command virsh undefine --nvram "Macinabox Catalina" to allow me circumvent the error saying that there is nvram allocated to the domain preventing me from removing the VM in the webUI (this is probably the wrong way to do this but it was the solution that popped up on google), then remove the iso files, the custom_ovmf folder, the disk image, and the macinabox appdata folder and restart macinabox with the correct settings.

 

After doing all that, I got Big Sur loaded and booting. however after selecting MacOS base system for the initial install the apple logo shows up and then a loading bar for a few seconds and then it reboots with the message "your computer restarted because of a problem" on the following install attempt and I am completely unable to advance any farther. 

 

I repeated the reset steps listed above and went back to Catalina and had the same issue. (still currently installed and not working)

 

I have no idea if I messed up or if my server just doesn't want to work. Any assistance would be appreciated.

Nah, you dont messed up your server. You should just enable "expert view" within editing the VM and empty your xml completely.

Than you should be able to remove your VM (without the vdisk!). The vdisk can you manually remove within the domains folder on your server.

 

I fixed my problem myself. I got a bad OpenCore Config.plist. I just redid my OpenCore and then I was able to update just fine from Big Sur 11.2.3 to 11.3.

Link to post
7 hours ago, RiDDiX said:

Nah, you dont messed up your server. You should just enable "expert view" within editing the VM and empty your xml completely.

Than you should be able to remove your VM (without the vdisk!). The vdisk can you manually remove within the domains folder on your server.

 

That is a much easier method to remove the old VM.

 

7 hours ago, RiDDiX said:

I fixed my problem myself. I got a bad OpenCore Config.plist. I just redid my OpenCore and then I was able to update just fine from Big Sur 11.2.3 to 11.3.

 

I was under the impression that this configuration was supposed to be automatic. If this is the only solution to my issue, then I will probably wait to see if an update solves my problem. I looked into this but it looks like a multi hour plist altering process and messing around in MacOS is not worth that much more of my time.

Link to post

Anyone tried to update the standard macinabox created BigSur VM to 11.3 ? Any tips.

Tried to just blind run an update (to a cloned snapshot of it on zfs) to see what happens but end in a boot loop .

 

Otherwise does a new macinabox result in 11.3 or still the old version .?

Just want to set one up fast for just some testing purposes. Whatever is the fastest (am in a lazy mood ;-)

Link to post
9 minutes ago, glennv said:

Anyone tried to update the standard macinabox created BigSur VM to 11.3 ? Any tips.

Tried to just blind run an update (to a cloned snapshot of it on zfs) to see what happens but end in a boot loop .

 

Otherwise does a new macinabox result in 11.3 or still the old version .?

Just want to set one up fast for just some testing purposes. Whatever is the fastest (am in a lazy mood ;-)

Hi,

if I remember well you have intel with cpu passthrough?

If this is the case, please take a look here:

 

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.