-
Posts
1,747 -
Joined
-
Days Won
30
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by SpaceInvaderOne
-
Interview with Spaceinvader One
SpaceInvaderOne replied to SpencerJ's topic in Unraid Blog and Uncast Show Discussion
thanks glad you like the vids -
Interview with Spaceinvader One
SpaceInvaderOne replied to SpencerJ's topic in Unraid Blog and Uncast Show Discussion
Ha glad you like it ๐ -
Interview with Spaceinvader One
SpaceInvaderOne replied to SpencerJ's topic in Unraid Blog and Uncast Show Discussion
@Rhynri Hi @ Very late reply but it is called a lametric smart clock. -
[Support] SpaceinvaderOne - Macinabox
SpaceInvaderOne replied to SpaceInvaderOne's topic in Docker Containers
Hi. Splashtop works better with e1000-82545 nic type than vmxnet Please try changing the nic type to that by changing this line <model type='vmxnet3'/> to <model type='e1000-82545em'/> For sound you should be able to get it working through splashtop by adding a virtual sound card. (also i think splashtop supports clipboard sharing..) Please add this to the xml <sound model='ich9'> </sound> -
[Support] SpaceinvaderOne - Macinabox
SpaceInvaderOne replied to SpaceInvaderOne's topic in Docker Containers
Yep enable bridging and you will have br0 -
[Support] SpaceinvaderOne - Macinabox
SpaceInvaderOne replied to SpaceInvaderOne's topic in Docker Containers
Ok so I didnt realise that you are having the issue when the vm is using the GPU. What the problem is is that I you are using a Nvidia gpu.I thought you had gone back to vnc. An nvidia GPU this needs web drivers to make work. So 3 things you will need to do. 1. Boot back into the vm without passthrough using vnc. Install splashtop desktop personal streamer (free) https://www.splashtop.com/streamer on the vm. And the Spalashtop desktop on your computer. 2. Open the clover configurator and goto system parameters and check nvidia web then on smbios make sure you have product imac 14,1 (see pics) 3. Stop then vm. passthrough the graphics card again, then boot. (you will still see the garbled screen) Use splashtop to connect to the screen. It will be very small screen but don't worry. Open terminal and run this bash <(curl -s https://raw.githubusercontent.com/Benjamin-Dobell/nvidia-update/master/nvidia-update.sh) That will install the webdrivers for the gpu easily. After that reboot and you should have a workable vm !! ....hopefully ๐ -
[Support] SpaceinvaderOne - Macinabox
SpaceInvaderOne replied to SpaceInvaderOne's topic in Docker Containers
The macinabox template uses custom ovmf files. If you change <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/e930dfa3-ce5f-4a14-a642-d140ed8035bd_VARS-pure-efi.fd</nvram> </os> to be as below you will be back without the screen corruption. <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> hope that helps ๐ -
[Support] SpaceinvaderOne - Macinabox
SpaceInvaderOne replied to SpaceInvaderOne's topic in Docker Containers
Yes this is the problem here. The clover image is a qcow2 image not a raw image <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/VDisks/MacinaboxCatalina/Clover.qcow2'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> Please change the xml to be as follows <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/user/VDisks/MacinaboxCatalina/Clover.qcow2'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> -
[SOLVED] Non-working IGD pass-through with i3-8100 for VM
SpaceInvaderOne replied to T0a's topic in VM Engine (KVM)
Passing through an igpu has always been more problematic than a regular gpu. I guess you havent had sucess with igpu passthough with any vms as yet. Using a regular gpu will be much easier. I beleive the gt730 supports metal so should be okay in macOS. The gpu that i use for macOS is a sapphire rx570 pulse itx which works also natively. -
[SOLVED] Non-working IGD pass-through with i3-8100 for VM
SpaceInvaderOne replied to T0a's topic in VM Engine (KVM)
If you can get the passthrough to work with other vms it should work. Please try this xml in place of what you have. This xml has your gpu passed through in it. However when you start the vm you will have no keyboard or mouse as I couldnt put that in for you but that should be easy to do. Just use this as is to see if it boots with the gpu and gets to the desktop. Remember to put both your uuid and osk key back into the xml <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>MacinaboxCatalina2</name> <uuid>a-uuid-here</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'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/mnt/user/domains/MacinaboxCatalina/ovmf/OVMF_CODE.fd</loader> <nvram>/mnt/user/domains/MacinaboxCatalina/ovmf/OVMF_VARS.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='2' 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/user/domains/MacinaboxCatalina/Clover.qcow2'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/MacinaboxCatalina/Catalina-install.img'/> <target dev='hdd' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/MacinaboxCatalina/macos_disk.img'/> <target dev='hde' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='4'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <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'/> <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'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:2c:45:1e'/> <source bridge='br0'/> <model type='vmxnet3'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x03' 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=clean'/> <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> -
[Support] SpaceinvaderOne - Macinabox
SpaceInvaderOne replied to SpaceInvaderOne's topic in Docker Containers
I passthough a controller that i known is compatible with macOS. You may have to use a kext if the usb controller that you are passing through isn't native to osx. -
**VIDEO GUIDE** How to Install MacOS Mojave or High Sierra as a VM
SpaceInvaderOne replied to SpaceInvaderOne's topic in VMs
-
[Support] SpaceinvaderOne - Macinabox
SpaceInvaderOne replied to SpaceInvaderOne's topic in Docker Containers
I like splashtop desktop. Works well is easy to setup and has sound. -
[Support] SpaceinvaderOne - Macinabox
SpaceInvaderOne replied to SpaceInvaderOne's topic in Docker Containers
Ah I was hoping people wouldn't post the osk key here in the forum. Yes i should have put that in the first post. Post is now updated. -
[Support] SpaceinvaderOne - Macinabox
SpaceInvaderOne replied to SpaceInvaderOne's topic in Docker Containers
@hernandito wow love the icon. It is now the official icon for the container. Many thanks ๐ -
[Support] SpaceinvaderOne - Macinabox
SpaceInvaderOne replied to SpaceInvaderOne's topic in Docker Containers
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> -
opps pressed post by mistake . Anyway carrying on from above. Change it to <model type='e1000-82545em'/> This is an emulated intel nic. That then may work in the nas vm
-
A couple of things. i see in the vm template you are using br1 as the brigde try br0 If that doesnt work then i am wondering if the vm you have created doent recognise the virtio nic type that is used in a vm by defualt. try editing the vm xml. goto the template and toggle to xml view in the top right and change the follwing. You will see in the xml something that looks like this <interface type='bridge'> <mac address='00:00:00:00:00:00'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> this line here is the nic type (virtio here) <model type='virtio'/>
-
[Support] SpaceinvaderOne - Macinabox
SpaceInvaderOne replied to SpaceInvaderOne's topic in Docker Containers
@1812 I found that you must use vmxnet3 for the initial download and install. It didnt work at all for me without that. However after install of Catalina I shutdown and swapped back to e1000-82545em (only a single nic - will try dual later) This worked fine for me and i was able to access the apple store and update a few programmes that were not supported in Catalina. -
[Support] SpaceinvaderOne - Macinabox
SpaceInvaderOne replied to SpaceInvaderOne's topic in Docker Containers
I dont use vnc at all for my macos just gpu and usb controller passed through. So havent really looked until just now. I did notice the bad performance of the vnc mouse generally though. I noticed while playing around with the xml the mouse performance in the webui is greatly improved by doing the following. In the xml change remove the mouse part from below (must leave the keyboard part) <qemu:commandline> <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-mouse,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=??????????????????????????????????'/> <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> So to like this <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=?????????????????????????APPLE OSK goes here????????????????????'/> <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 will change this in the default templates that the container uses to reflect this. But everyone who has already downloaded and installed i would suggest making this change. -
[Support] SpaceinvaderOne - Macinabox
SpaceInvaderOne replied to SpaceInvaderOne's topic in Docker Containers
I dont use auto backup script myself. I manually backup my vdisks when needed which is probably not often as i should as i accidentally formatted an unassigned drive whilst tired that had a few vms i hadnt backed up for a while! ๐ช -
[Support] SpaceinvaderOne - Macinabox
SpaceInvaderOne replied to SpaceInvaderOne's topic in Docker Containers
Hey there @1812 great glad to hear its working. Did it take a long time to download the image during install? Also what disk type did you use. Raw or qcow2 and what file system format did you use, apfs or macos extended? Just interested as some people have an issue on first reboot. -
[Support] SpaceinvaderOne - Macinabox
SpaceInvaderOne replied to SpaceInvaderOne's topic in Docker Containers
Other than just force stopping the vm and rebooting please try this. open terminal from the webui on Unraid rm -r /mnt/user/domains/MacinaboxMojave/ then delete the vm template. Unraid will say it cant delete the template due to the OVMF_VARS. So remove this line from the xml (on line 25) update then the template can be removed <nvram>/mnt/user/domains/MacinaboxMojave/ovmf/OVMF_VARS.fd</nvram> Then retry the installation but in the docker template select disk type to raw. This helped someone else here, it shouldnt make a difference really but worth trying. -
[Support] SpaceinvaderOne - Macinabox
SpaceInvaderOne replied to SpaceInvaderOne's topic in Docker Containers
Should work fine on Ryzen 2700x i am using similar. So you are getting through the install and set everything up (country -timezone etc) and you reach the macOS desktop then you get the question mark on the screen after reboot? Or is this after the first reboot after the installer has downloaded the install -
[Support] SpaceinvaderOne - Macinabox
SpaceInvaderOne replied to SpaceInvaderOne's topic in Docker Containers
Hey @rorton to be honest not sure. It should work ok. If it works on a hackintosh will work for the vm. Best practice is beforehand just copy the vdisk in case anything goes wrong then you are safe. Glad to hear its all working. Just one thing to note. Dont run the container again now its intalled as a bug it will re create the vdisk that its installed on and basically wipe the install. i am just changing that at the moment and will fix that in next push.