planetwilson

Ah sorry I thought you said earlier that OSX was working okay? Your VM is no longer working following the update to 6.4? Mine are on Q35-2.10 now am on unRAID 6.4. I thought that was the version you had to be on in order to use a non-special patch clover?

I've got the smae but ignoring it as there don't appear to be any issues...

Does it matter that the CPU appears as a Core 2 Duo? Are we missing out on anything because OSX thinks it is that?

Well I have no idea why but when I downloaded it instead of doing it through the app store it worked all of a sudden.

I have a fully working 10.13.1 with gfx passthrough all there but as soon as I apply 10.13.2 it won't boot any more. Just the apple logo and a progress bar stuck at around 20%. Doesn't matter if I run my VNC or gfx passthrough version of the VM. Are you using APFS?

It doesn't require 6.3.5 it is just much easier as you don't have to use a special patched versin of Clover. FWIW I upgraded to 6.4 recently once it was past around RC16 (I was worried about stability also) or so and it has been very stable for me, no issues at all.

Does anyone have this working with OSX 10.13.2 ? When I upgrade from 10.13.1 > 10.13.2 then the VM won't boot any more....

Okay thanks will see if I can get one of the other options to work. It's a bit confusing really. I removed the disk image from the VM XML so I don't understand why I have 3 or 4 different boot options in Clover now.

Anyone had an issue running latest updates for High Sierra from the app store. Mine just sits on the update install with the Apple logo sitting with a progress bar stuck aroun a 3rd of the way alone. Hve tried a hard reset twice and same thing.

I have used this a lot and it is ace. I do however get issues at one particular place that uses DPI to try and detect VPN traffic. Is there any interest in perhaps implementing an obfsproxy in the docker container to further hide the traffic? I know the Viscosity VPN client for Mac and Windows supports adding that layer from the client side.

2 x 2.3GHz cores? or 22 x 3GHz cores? One sounds mismatched and one sounds awesome!

Yeah, thought so Sent from my iPhone using Tapatalk

is the RC fairly stable then? I only have the one unRAID server so am a bit nervous of upgrading until it is released....

80GB DDR4 ECC. Seems like an odd number but I won an extra ebay auction I wasn't expecting and rather than get rid I chucked it in on top of the 64GB I had planned for

One issue I have in my VM having followed this mechanism is crackly sound when watching videos. It is a bit strange, seems to happen whether I output the sound over HDMI to my built in monitor speakers or through my USB connected B&W desktop speakers so it seems more system based if you see what I mean. Any ideas? Actually the more I try things, it seems like it is a Safari issue as Chrome doesn't do this....can't be VM related I guess.

Anyone know of any issues upgrading to 10.12.5?

Yes I have it all working now following that guide It takes a lot of faffing through clearing everything out. Also if you get a few things in OSX trying to access your Apple ID all at once and you have 2FA enabled it all trips up over itself, Apple decides someone is trying to brute force their way in, locks the account and you end up going through a process to unlock your password. I'd turn off other devices like iPads etc and just have your iPhone handy if you have one and are using 2FA. Then sign into iCloud services one at a time slowly.

Anyone got any idea how to get iMessage working? On previous VMs I did it just worked but on my latest one done via VMWare Fusion it isn't working. I suspect I need to follow the advice in this guide possibly:- Reddit Hackintosh getting iMessage working However given it involves using Clover to generate some new IDs I am concerned I will break my existing VM as I don't *really* know what settings are unRAID/KVM sensitive....

Trying to work out the best approach having read through all this for me. I have a 14 core E5-2695 v3 and 80GB of RAM for doing various VM type scenarios. I often run a few different Windows VMs at once. cpu 0 / 14 cpu 1 / 15 cpu 2 / 16 cpu 3 / 17 cpu 4 / 18 cpu 5 / 19 cpu 6 / 20 cpu 7 / 21 cpu 8 / 22 cpu 9 / 23 cpu 10 / 24 cpu 11 / 25 cpu 12 / 26 cpu 13 / 27 I am thinking of assigning pairs 03/17 onwards in pairs to VMs. So a beefy server would get 12/26 and 13/27 for instance. Another server might get 10/24 and 11/25 assigned. That way I am not trying to put threads across VMs. Not sure it is worth pinning the emulator stuff? Should I add the isolcpu bits to syslinux so that unRAID can only use say 0/14, 1/15 and 02/16 for itself and Dockers...

Most common cause seems to be a disk filling up, I have a share set to cache disk only (my SSD) called VM which is where I store all the disk images. There is plenty of space on there. I was trying to move it across to the user share on the array the other day but couldn't simply move it like that. I wonder if I have broken something somewhere...

Yep, reboot has sorted it. Very strange though, nothing of any note in any of the libvirt logs either. Spoke too soon, started doing it again....damn.

Okay scratch that - all my VMS are doing it. Not OSX specific...

So my OSX VM that I created last week and has been working fine is suddenly behaving very strangely. I have a GTX950 based through and now during boot it will pause and refreshing the list of VMs in unraid shows it as paused or suspended. Hit play again and the progress bar goes a little further before it shows suspended again. I managed to eventually get it started but it runs for a few seconds at most before becoming suspended again. Strangely the monitor still shows the desktop at this point but frozen in time.

Aah, I didn't know you could expand them through the UI. Good to know. Expanding the partition internally I did struggle with at first. I booted into recovery thinking perhaps it was like Windows and you couldn't expand the boot partition but that had issues too. In the end I think it was the poor UX of Disk Utility. I had to click on the "free space" then click remove! then I could expand the partition into the actual free space. It was almost like Disk Utility was presenting free space as a special partition called "free space". Very odd.

One thing that tripped me up for a while that is worth noting is that when I went back to expand my drive later on using:- qemu-img resize Sierra.img +30G I found that it wouldn't boot afterwards. Only when I went back to check the output of the above line did it have a warning about not detecting the image image format correctly. WARNING: Image format was not specified for 'x86-64.img' and probing guessed raw. Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. Specify the 'raw' format explicitly to remove the restrictions. i.e. it had made the image read only. I ran the command again, expanding it by another 1GB but this time also specifying the format with -fmt raw and after that it all worked fine. I could then use disk manager inside OSX to expand to use the newly available space...