ghost82

Members
  • Content Count

    728
  • Joined

  • Last visited

  • Days Won

    2

ghost82 last won the day on April 29 2020

ghost82 had the most liked content!

Community Reputation

147 Very Good

5 Followers

About ghost82

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Tomorrow I will have some time to prepare an updated image starting from the macinabox one, debug version and with logging to file enabled so we will hopefully understand more if it fails. If your trials fail you could try that image. Please share also your full xml just to see what's your vm configuration.
  2. Provide your config.plist (delete sensible data), or better the full efi or send via pm. If you're passing through the cpu you need both patches for penryn family force, one for 11.2 and one for 11.3 (with proper min and max kernel versions) otherwise it will hang on 11.2 (if you're using the 11.3 patch) or on 11.3, after the first boot after the update (if you're using the 11.2 patch); otherwise you can use the 11.2 patch, reboot after the update (and it will hang), force shutdown the vm, edit the penryn patch for 11.3 from unraid, boot to bootpicker and complete the 11.3 update. Or
  3. You need to assign a dedicated gpu to the mac os vm, since you want "performance", to have video (hardware) acceleration, then you can access directly with a monitor attached to that gpu or with a remote software management setup in the vm (if no monitor is attached to the vm you need a hdmi or whatever your socket is, dummy plug). Without a dedicated gpu you can use the vm only for basic operations, as you won't have video acceleration. Apple never released machines with amd cpus, but you can emulate intel even if you have an amd cpu; I would go for intel as you can passthrough (no
  4. Definitely possible, and some builds can be a lot faster than a mac pro, speaking about intel mac. Qemu with kvm with gpu passthrough is not comparable with "vmware types" virtual machines. I'm using mac os in a vm from about 2 years as my daily machine and I'm very satisfied with it. Don't assume to have it working and optimized in a couple of days: depending on your experience level you can have it booted in hours (or days) and have it optimized in days or months. The main advantage of running mac os in a vm is that you can emulate the cpu(s), so you can have a ryzen/thre
  5. Hi, if I remember well you have intel with cpu passthrough? If this is the case, please take a look here:
  6. For those updating to big sur 11.3 that are using cpu passthrough and that are using the force cpu penryn patch, take into account that the patch changed from big sur 11.3 beta 1. New one is: <dict> <key>Arch</key> <string>x86_64</string> <key>Base</key> <string></string> <key>Comment</key> <string>DhinakG - cpuid_set_cpufamily - force CPUFAMILY_INTEL_PENRYN - 11.3b1</string> <key>Count</key> <integer>1</integer> <key>Enabled</key>
  7. Sorry for the delay. I never played with shiki but I think you don't need to spoof the whole vm to imac 14,2: shiki-id should spoof to imac 14,2 only for the gpu. Anyway, if it works and you are satisfied, it's ok. what boot screen are you referring?
  8. Are you following dortania instructions? https://dortania.github.io/GPU-Buyers-Guide/modern-gpus/nvidia-gpu.html#kepler-series-gtx-6xx-7xx Try to add in your config.plist, boot args: shikigva=40 shiki-id=Mac-27ADBB7B4CEE8E61 Append them if you have others, follows example: <key>NVRAM</key> <dict> <key>Add</key> <dict> ....... ....... <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key> <dict> ....... ....... <key>boot-args</key> <string>shikigva=40 sh
  9. Are you overclocking the ram?The only reference I found with that type of hang is about a different frequency for the ram
  10. Hi, not sure if it will work, but I would try to change the bus of the fenvi card, move it to bus 0 (use the 1st config with gpu passthrough). Change from: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> To: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name
  11. Here are some replies from vit9696 about usb power properties, which may be useful: Questions: 1. Does specifying the properties for the XHC device or via PciRoot - which in the end is the same thing - have any relevant impact/change on correct USB power management? 2. Are these two methods doing the same thing? 3. Is SSDT-USBX enough for handling USB port currents or maybe needs some more properties? Answers: 1. On IOUSBFamily (pre-10.11 if I remember correctly) it does and works correctly. Required to be AAPL,-prefixed properties. On IOUSBHostFamily these values are
  12. No idea..but start reading from here: It seems @giganode solved the same issue by changing the refresh rate.
  13. 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.
  14. 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