[Support] SpaceinvaderOne - Macinabox


1940 posts in this topic Last Reply

Recommended Posts

14 hours ago, derpuma said:

As I was not able to manage it, to resize the apfs partition of may macOS after I have installed it (it does not work for me with disk utility and neither with diskutil apfs resizeContainer /dev/diskXsX 0 via terminal), I would like to get rid of some unclarity in regards of booting into the macOS VM.

 

I tried to clone my small 64G partition via Carbon Copy Cloner into a new 500G VM disk of a fresh macOS Catalina install (mounted via Diskimagemounter in macOS). This worked fine so far, I also mounted the EFI partition of the new cloned and larger VDISK and replaced the EFI Folder with the one of my 64G Disk where I have made some changes in the config.plist and updated some kexts. I also copied the Clover.qcow2 image and the ovmf folder of my smaller working macOS Vdisk over to the new bigger VDsik.
Unfortunately the system was not able to boot afterwards. Clover was empty and I was not able to select the boot devices.
What am I missing?
It would be nice, if someone could explain me how booting is done step by step.

What is where, what's the rule of the Clover.qcow2 image? I thought all booting information is in the EFI Folder of the corresponding VM OS VDISK Drive.

Cause I failed, I did another fresh install of macOS into a 500G fresh VDisk and migrated the system via Apples Migration Assistant, which worked flawless.

Anyhow, I would like to understand how booting works to get manual access to some operations via CCC f.ex.
Thanks in advance for some explanation!

 

Thats what I did as well.

Spent hours trying to resize the partition, couldnt get it working.

In the end, it was just easier to fresh install and use migration assistant.
 

 

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

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

6 minutes ago, Vash12 said:


Do you experience any lag using nomachine? I usually remote into the VM.

no point passing through a GPU.

 

 

Not really. I dont know what specifically ‘remote into the VM’ means as it could be interpreted many ways. 

Link to post
Not really. I dont know what specifically ‘remote into the VM’ means as it could be interpreted many ways. 

Thanks, I normally would remote into the mac vm using splastop or vnc.
Want to avoid passingthrough a gpu.


Sent from my iPhone using Tapatalk
Link to post
6 hours ago, Vash12 said:

Thats what I did as well.

Spent hours trying to resize the partition, couldnt get it working.

In the end, it was just easier to fresh install and use migration assistant.
 

 

 

I saw others successfully using Carbon Copy Cloner too.
I guess the main Clover Partition is in the Clover.qcow2 file.

What I would like to do is boot from my older OS X installations from SSD.
I have a couple of disks with Mojave and High Sierra and it would be nice to boot from Unraid via SSD.
I tried that with the /dev/disk/by-id/ata-Crucial_CT500MX200SSD1_15040E7D6DF8 but it did not boot up and get stuck while the loading bar under the

Apple logo appeared.


So my question is: Does the Clover.qcow2 take any information from the EFI Folder of the linked new SSD Boot device?
Or would it be necessary to edit something in the Clover.qcow2 File too?
When I tried to boot up, I saw clover boot options from my VDISK installation, so I guess Clover.qcow2 linked to that image?
 

Would it be generally possible to modifiy the files manually and boot like I'd like to?
I just need to know how everything connects...

Thx!

Edited by derpuma
Link to post
4 hours ago, cawighy said:

How can I rename a VM once it has been created? Editing the template doesn’t allow me to change it. 

It should be possible if you do it right! Be carefull, that you create a new, non existing name and that the <uuid> is unique.

What error message shows up? Are you able to update and only the name does not show up?
Look if you do not mess up with  <name>MacinaboxCatalina</name> and  <description>MacOS Catalina</description>...

Link to post

Does anyone know if it is possible to extend the disk? I made a 100GB disk and now want it to be 200GB. Changing it in Unraid was fine and in osx it sees the disk is larger but disk utility is unable to extend the volume no matter what I try. Has anyone ever actually done this?

Link to post
1 hour ago, PeteAsking said:

Does anyone know if it is possible to extend the disk? I made a 100GB disk and now want it to be 200GB. Changing it in Unraid was fine and in osx it sees the disk is larger but disk utility is unable to extend the volume no matter what I try. Has anyone ever actually done this?

I find the easiest way to move to a larger disk is not expanding the existing disk but to migrate to a new disk instead.

1.  Create new macOS vm with larger disk. (ie 200G)

2. Stop new VM

3. Add the old macOS vm's vdisk (100g disk) as an additional disk to the new vm in its template.

4. Boot into new vm

5. Run migration assistant (applications/utilities/migration assistant)

6. Now you can migrate all programmes data and settings from the old vdisk to the new larger vdisk

7. After migration complete shutdown vm.

8 Remove old vdisk from template

9. delete old vdisk or keep as backup.

 

Link to post

I was able to expand a vdisk today, i took a couple of steps but it worked for me. I had to use a gparted VM i have for doing some vdisk work.

...Expand the vdisk in the unRAID GUI

..boot the expanded vdisk in a Gparted VM

..Gparted will alert you that the gpt of the vdisk does not recognize all the free space on the disk and will fix it. Allow it to do so. Shutdown the Gparted VM.

..Boot you macOS VM with the Newly expanded vdisk.

..In the terminal do diskutil list and find the Apple_apfs Container disk. it will probably be disk1

..Run the command-- diskutil apfs resizeContainer /dev/diskx 0. It should expand you vm to use all available space.

 

Worked for me in but if its a bit scary for you use the migration assistant or disk utility in recovery partition using the restore function. And always keep backups.

Link to post
2 hours ago, david279 said:

I was able to expand a vdisk today, i took a couple of steps but it worked for me. I had to use a gparted VM i have for doing some vdisk work.

...Expand the vdisk in the unRAID GUI

..boot the expanded vdisk in a Gparted VM

..Gparted will alert you that the gpt of the vdisk does not recognize all the free space on the disk and will fix it. Allow it to do so. Shutdown the Gparted VM.

..Boot you macOS VM with the Newly expanded vdisk.

..In the terminal do diskutil list and find the Apple_apfs Container disk. it will probably be disk1

..Run the command-- diskutil apfs resizeContainer /dev/diskx 0. It should expand you vm to use all available space.

 

Worked for me in but if its a bit scary for you use the migration assistant or disk utility in recovery partition using the restore function. And always keep backups.

This sounds really good. How do I get a gparted VM? I would like to try this option. 
 

P

Link to post

Download a gparted iso, add it as the install iso on a new VM and add any other vdisk on your system as a secondary vdisk. When you boot the VM just use gparted as any other live cd and you can manipulate the vdisk you added any way you want. 

  • Like 2
  • Thanks 1
Link to post
16 hours ago, david279 said:

Download a gparted iso, add it as the install iso on a new VM and add any other vdisk on your system as a secondary vdisk. When you boot the VM just use gparted as any other live cd and you can manipulate the vdisk you added any way you want. 

So simple and yet so much better than what I have done in the past. I usually edit the xml on the VM I want to manipulate with the live ISO set to boot first, but that can have unpredictable results when the live ISO uses the existing xml.

 

MUCH better to just add a general utility VM with gparted and other recovery tools, and change the attached disks (or preferably a copy) to whatever you need to manipulate.

 

It's the software equivalent of mounting the problem disk in a known good computer, vs trying to boot the problem child computer with a live CD.

 

Thank you for making me think through this, now I've got a much better strategy to deal with a number of issues that could come up.

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. 

 

 

 

 

 

 

Thank you very much and sorry for the late reply , your XML really helped , however I am not stuck with just a black screen 😞 I can see that the VM is running in the VIRT Management docker  . Included the images but i have no idea what i should be looking for. I have a dummy hdmi dongle in the GPU HDMI socket . By the way i ended up using a 580 instead of the 5700xt . Any thoughts on what i have done wrong? Thank you !

virt 2.PNG

virt 3.PNG

virt manager.PNG

Link to post

Thank you to everyone who helped me increase the size of my disk. In the end only 1 method worked for me. I added a second disk then booted up of the installer disk in the VM (by choosing startup disk in system preferences) and once I created a partition on the new disk with disk utility I clicked the restore option in disk utility and restored from the smaller disk which seemed to clone the original disk to the destination disk. I could then boot from the new disk and remove the old one and delete the image.

 

I also have another issue that is not a major problem but just annoying. Every time I shut down the VM and turn it back on the VNC graphics become garbled, like it is trying to display the screen many times in VNC. The way I have to fix it every time I ever turn off the VM, is to boot VM, go into the bios, choose OVMF settings and change resolution to 1920x1080 then save this and reboot. Graphics still garbled at this point. Shut down a second time and repeat the above changing the resolution to 800x600. This time when you boot the VNC graphics are normal and it is 1080p despite being set to 800x600 and I can use VNC as normal. If I ever turn off OSX I must repeat this 2 reboot process to restore the graphics. Its not a major issue as I dont reboot often and of course I avoid doing so unless I have to since its a headache to get the screen working again via vnc. I just wondered if anyone else had this issue and knew why it did it or how to fix it.

 

Kind regards

P

Link to post

HI all, I have been around Hackinstoshes before - I've build a few, but this is my first month w/ an Unraid server. That said, I have question about SIOnes excellent container. I have successfully built my High Sierra container and wanted to pass my Nvidia 1080 through for better perf.

 

I followed his video - but what's not clear is once I make the change to enable the GPU to be passed through, how do I remote into it? He says to use Splashtop- but I don't know where to point my client to once I do that? It appears that once you enable a GPU that VNC is no longer an option to login in? 

 

Also: Is there a way to take a snapshot of the container I have not that is running fine - so I can roll back to it if I mess something up while getting the GPU passed through?

 

Thanks!

 

P.S. I installed Splashtop - and it's really laggy when I use it to connect to my VM. Worse than VNC

 

Edited by Nexus
Link to post

Having a strange new issue with Macinabox. 

 

I've deleted my old OSX VM and am trying to install a new VM on an unassigned device. Whenever I try to run the Macinabox docker, it gets to the following stage:

 

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Starting process at Tue Jun 30 00:11:31 America 2020
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

I am going to download the Catalina recovery media. Please be patient!
.
.
Requirement already satisfied: requests in /root/.local/lib/python2.7/site-packages (from -r requirements.txt (line 1))
Requirement already satisfied: click in /root/.local/lib/python2.7/site-packages (from -r requirements.txt (line 2))
Requirement already satisfied: urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1 in /root/.local/lib/python2.7/site-packages (from requests->-r requirements.txt (line 1))
Requirement already satisfied: chardet<4,>=3.0.2 in /root/.local/lib/python2.7/site-packages (from requests->-r requirements.txt (line 1))
Requirement already satisfied: certifi>=2017.4.17 in /root/.local/lib/python2.7/site-packages (from requests->-r requirements.txt (line 1))
Requirement already satisfied: idna<3,>=2.5 in /usr/lib/python2.7/dist-packages (from requests->-r requirements.txt (line 1))
2020-06-30 00:11:32,400 Network Request: Fetching https://swscan.apple.com/content/catalogs/others/index-10.15-10.14-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog
2020-06-30 00:11:33,394 Selected macOS Product: 001-04366
Full install starting to unraid domain /image/MacinaboxCatalina
.
.
mkdir: created directory '/image/MacinaboxCatalina'
I have created the Macinabox directories
.
.

and then hangs there.

 

When I navigate back to the main tab of unRAID, the unassigned devices area just shows an unRAID logo animation that never resolves.  In addition, the CPU is still working overtime with on average 2/16 threads at 100% with nothing else active on the server. Netdata tells me it's iowait sucking up the CPU power. The server no longer responds to reboot or shut down commands after this happens and I've gone through two cycles of hard power off with subsequent parity drive check for 20h to make it functional again.

 

Any idea what might be happening?

 

This is on a brand new Samsung 860 Pro SSD hooked right into the mobo. I previously had a working OSX VM on this server but it was installed on my cache drive. With both of my cache drives in the TBs of read/write activity after 6 months due to the excessive read/write bug with dockers, I'm trying to move stuff off of them. 

UAD.PNG

Link to post

Hi grizzle,

 

Do you have a single GPU in your system ? I had some issues getting Uraid to release the card to my VMs i bought a very cheap card to get around this. 

Also the AMD reset bug caused me major issues, once i rebooted the VM, i had to restart the entire system to release the resource and allow it to boot again. 

Do your logs show any error when you start the VM? 

Link to post
On 12/20/2019 at 6:17 PM, maxse said:

Guys, help! strange issue . with upload

 

I have a 100/100 line. When I test on macbook at speedtest.net I get pretty much 100/100. But when I go over to the VM I get 100/0.34Mbps! I set up this VM to do backups and realized that the upload was painfully slow. I then tested the same backup software on my macbook and the speed was great.

 

So I then went over to speedtest.net on the VM and then tested it against my macbook, on the same network obviously, and got those results. What is causing the the upload to be so slow on the VM?

 

Just ran the test again:

On macbook got 98Mbps down/118Mbps Up

On the VM  it was also 98Mbps down and then upload was so slow it errored out! "Upload test error a firewal could be blocking the connection"

 

What's going on here?

 

On 12/20/2019 at 6:28 PM, 1812 said:

you are probably using vmxnet3. change to e1000-82545em


 

How can I change my nic driver between the two? I only see br0 and virbr0

Link to post
2 hours ago, Simmer said:

 


 

How can I change my nic driver between the two? I only see br0 and virbr0

That’s the network it uses. Go to advanced in the vm settings and edit the xml

Link to post

I have a macos cn running, which i had set up with this docker. Two questions:

 

1) How to update clover and is it even needed?

 

2) I’m planning to pass-through a gpu (rx 570, which i read to be best compatible for this vm. Do i need to start over or how to add it? Assume i need to be cautious not to mess up my xml file?

 

Thanks!

Link to post
3 hours ago, steve1977 said:

1) How to update clover and is it even needed?

You need to mount your efi folder in the mac os vm, download the latest release version of clover or compile by yourself and overwrite these files in the efi folder; it could be necessary to update, sometimes mac os minor updates (10.y.x1 --> 10.y.x2) may break something in the bootloader.

Some information are around in this forum, search for them.

 

3 hours ago, steve1977 said:

2) I’m planning to pass-through a gpu (rx 570, which i read to be best compatible for this vm. Do i need to start over or how to add it? Assume i need to be cautious not to mess up my xml file?

No need to start over, you just need to change the vm settings (xml).

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

You need to mount your efi folder in the mac os vm, download the latest release version of clover or compile by yourself and overwrite these files in the efi folder; it could be necessary to update, sometimes mac os minor updates (10.y.x1 --> 10.y.x2) may break something in the bootloader.

Some information are around in this forum, search for them.

 

No need to start over, you just need to change the vm settings (xml).

Thanks. It seemed from the Macinabox description that I can just run the docker again to update Clover. Is this correct?

 

I tried to change the XML file to passthrough the AMD RX580. Catalina still boots up and I can see the screen via AnyDesk. However, I don't think the passthrough GPU is being used. How can I check this? What could I have done wrong? How to best trouble-shoot?

Link to post
57 minutes ago, steve1977 said:

It seemed from the Macinabox description that I can just run the docker again to update Clover. Is this correct?

Updating clover means that the docker will download the clover image hosted on github, so if SIO doesn't update the image from the clover repo you are not updating clover.

58 minutes ago, steve1977 said:

I tried to change the XML file to passthrough the AMD RX580. Catalina still boots up and I can see the screen via AnyDesk. However, I don't think the passthrough GPU is being used. How can I check this? What could I have done wrong? How to best trouble-shoot?

Check if you have hardware acceleration (check system information and see if the gpu is seen).

If you don't attach a monitor your gpu will not be used by the os; if you can't attach a monitor you need a hdmi dongle or something that emulates an attached monitor.

Remember to use also lilu and whatevergreen kexts for the gpu to work properly.

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.