pavo

Members
  • Posts

    14
  • Joined

  • Last visited

pavo's Achievements

Newbie

Newbie (1/14)

9

Reputation

  1. Good to know... thank you. Will have to test this out because I have 10Gb transfer rate from external NAS without any issues. Completely agree... Forgot to fix the picture Will have to test this, I use SSDTs to create ACPI devices for all my passed-through devices which makes them show as internal. Have been using these settings for both BigSur and Monterey and csrutil works perfectly fine in recovery. Having control over SIP doesn't mean you should. With using kext injection within OpenCore and the varies plugins you can use for Lilu, I haven't ran into any reason to make changes too SIP. Plus it makes it more secure operationally. Correct using `cpu=host` does mean host passthrough, but in order to make a AMD cpu have a vendor-id of `GenuineIntel` You must provide the cpu type before it, hence the reason for cpu=host. Using it this way doesn't require any AMD kernel patches and passes through ALL host CPU features that is supported by the OS, including 7leaf cpu features. As you can see I am also using a Intel CPUID in the config.plist for OpenCore to emulate an Intel CPU.
  2. Let me know what you guys think.... https://github.com/Pavo-IM/Hackinabox
  3. @ich777 First of all.... very impressive container. Does this also update Qemu versions? The latest Qemu version is 6.0.0 rc4 but I am only seeing Qemu 5.1.
  4. Good news, no more AMD reset bug with RX 6xxx XT series GPUs in macOS 11.4 beta 1 on UnRAID.
  5. Nested virtualization that uses macOS's native hypervisor will not work with AMD cpus, because macOS doesn't support the AMD-V (SVM) cpu feature that AMD cpus have. MacOS's native hypervisor only support Intel's vmx CPU feature.
  6. Because virtualbox provides its own hypervisor cpu instruction set. I was talking about macOS's native hypervisor. Until someone writes a kernel extension to add AMD-V (SVM) support to the kernel and the hypervisor framework for macOS, anything that uses the native macOS hypervisor will not work.
  7. This will never work because macOS kernel nor the hypervisor for macOS support AMD-V (SVM) cpu feature. Basically put, anything that uses macOS's hypervisor requires Intel's vmx cpu feature.
  8. Anyway to get this added to Unraid? https://github.com/gnif/vendor-reset/
  9. Disable SIP for Big Sur is FF0F0000 value and you can boot recovery if you enable JumpstartHotPlug under UEFI > APFS, but only use it to boot the Recovery, not normal boot.
  10. Why use a qcow? Why not just a USB drive like normal and either passthrough the USB Controller or pass it through as a USB device.
  11. Well anyways here is the xml I used for Unraid https://github.com/Pavo-IM/Hackinabox
  12. grrr for some reason the code block is taking out what needs to be posted.
  13. You can use the following addition to the xml and have no need for FakeSMC or VirtualSMC. <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk="************************"'/> </qemu:commandline>