G Dog
-
Posts
4 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by G Dog
-
-
On 10/26/2019 at 9:54 AM, SpaceInvaderOne said:
yep you can change core numbers etc. Just make sure to add the custom parts at the bottom of the xml back in.
Also if passing through a large amount of cores or or a non Apple stand such as 6 cores then remove topology line in xml.
for example here
<cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='14' threads='1'/> </cpu>
would change to
<cpu mode='host-passthrough' check='none'> </cpu>
Otherwise macOS wont boot with 14 cores assigned
Also the gpu that you have makes a difference. Nvidia gpus are good in upto high sierra.
For mojave and above you will need an AMD gpu. I am using a saphire rx 570 4gb
Also to get sound working correctly from an amd card you need to put the sound part on the same bus as a multi function bit.
I will explain this in a future video that i will make. But basically heres how mine looks in case you or anyone reading this wants to see.
<hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/> </source> <rom file='/mnt/disk1/domains/vbios/Sapphire.RX570.4096.180105.rom'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0a' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x1'/> </hostdev>
This information is gold! I have tried to follow the guide from last year and could get everything to pretty much work except for sound over the HDMI. This is what was needed.
Next goal...getting 4K from iTunes to play! Any ideas?
Thank you for making the container. Worked great!
-
Not exactly sure what I did, but pretty sure that what I did should not have caused to happen what happened.
I was in the process of looking over my network settings and trying to see if I could switch my main network connection from the Ethernet port on my server to the wireless device. In looking into doing this, I noted that in order to try and make any changes to the network settings I had to shut down docker and VMs. Seemed reasonable. I have no VMs installed yet and only had the Krusader docker installed which I had used successfully. As soon as I turned off Dockers on the Settings tab for dockers I had a bunch of warning pop up about my parity drive...it was "gone" from the main or the dashboard. I thought I would restart the server to see if it would come back up. One the first start it was not showing and then I restarted again and it was there. I am in the process of rebuilding the parity and do not see any "problems".
Any ideas of what I did or what caused it? Did not loose anything, there does not seem to be anything wrong, I am really wanting to keep going down the unraid path but this had me spooked a bit. In the scheme of things, rebuilding the parity drive is not the end of the world, but concerning.
Thanks in advance for any input. I am posting my diagnostics with the hope that someone can see something.
[Support] SpaceinvaderOne - Macinabox
in Docker Containers
Posted
Earlier in this thread are some instructions on replacing the OS Section of your XML. There are several sections of the XML that get overwritten when you make changes to the VM in the template. There are certain ones that you have to go back and fix in the XML and the OS section is one of them.