Closed ANONIMNIQ closed 1 year ago
@TaylorTWBrown he doesn't have Bluetooth. That's shown for me as well. It's likely a dummy that OpenCore creates
@TaylorTWBrown he doesn't have Bluetooth. That's shown for me as well. It's likely a dummy that OpenCore creates
Interesting. For me, one motivation for macOS on Hyper-v is to passthrough Intel AX201 or CSR4.0 Bluetooth (using USBIP or something). No luck yet - I get it to turn on with the adapters connected, but I can't actually scan/find devices. Likely something to do with loading firmware at boot time, or sharing of a CNVio device (?).
@zeanzhou I tried signing in to messages, and it also crashes. You may want to open a new issue to get more visibility.
Slow but smooth install...
Damn nice
Slow but smooth install...
How much time did you spend on installing this? It has taken me an hour and the Apple loading bar is still not done.
How much time did you spend on installing this? It has taken me an hour and the Apple loading bar is still not done.
An hour and a half, I guess. VM files location in HDD though.
What is the performance? Also, can you use it for video editing and rendering without GPU acceleration?
Hi, Excuse me.I would like to know if anyone has successfully run on an AMD CPU now? I tried to modify according to the guidelines provided by OpenCore. Unfortunately, it seems different from running on a virtual machine. I am using 5700G. If someone has successfully run on an AMD CPU, could you please provide the plist file and attach your CPU/motherboard model as a reference? Thank you very much.
Hello there, I Just wanted to give help to others who may stumble upon this that I was able to get it working. Thanks to @pigworlds suggestions I was able to get it fully working. My case was interesting because I have an installed Monterey on the same hardware I run Windows on so I knew beforehand that the PC can run the OS natively so I has to work somewhat in hyper-v.
CPU: Intel i7-12700KF
Windows build: 22621.1848
The OpenCore configuration that pigworlds provided originally only needed one other addition that he mentioned in a later comment, the CPUID mod:
<key>Emulate</key>
<dict>
<key>Cpuid1Data</key>
<data>6gYJAAAAAAAAAAAAAAAAAA==</data>
<key>Cpuid1Mask</key>
<data>/////wAAAAAAAAAAAAAAAA==</data>
For me this was essential otherwise the kernel got stuck on boot. I still have weird stuck boots but restarting almost always solves it.
My target was to install Ventura and Sonoma as well as Monterey, all succeded. I was able to download the Ventura installer on Monterey and clean install Ventura from that, for Sonoma I had to mess around a little bit, I ended up moving the Sonoma installer to a separate vhdx and install from that. I made a recovery image as how the OpenCore documentation said and used a Monterey recovery to install Ventura, Monterey and a Ventura recovery to install Sonoma.
Hallo, Can I please for GOOD Instruction to do this ? Please form help and understand ? I don't understand how to create this all ? Please for Help.
Hello infortek1991. I sympathize with you struggles, however, I have managed to get this working on my Windows 10 system with an i7-6700k using this VM file here Hyper-V VM File
Has anyone managed to get GPU passthrough working?
@DovydasTEDS
Has anyone managed to get GPU passthrough working?
Yes I was able to, I don't remember the exaxt steps I followed but it only works with windows guests and only with Direct 3D. It was a somewhat complicated process, enabling on the guest then copying driver files to the guest. So it worked but for me it was not good because I wanted to have vulkan supported on the passtrough GPU and non-windows OS as well. So I tried it and just didnt bother using it because of this. I think this was the repo/guide : https://github.com/jamesstringerparsec/Easy-GPU-PV
@DrakkLord
I have used the repo before, with a Windows guest and it ran alright. It had some lag, lower performance and, like you mentioned, only D3D was passed though unfortunately. I hope Microsoft can somehow improve GPU passthrough, which might also enable us to use GPU passthrough on a macOS VM.
@DovydasTEDS
As far as I know GPU pass through is somewhat limited in hyper-v and windows in general, because it's not a real GPU pass through like the one that KVM does, this is a layer up, so it just passes over / translates the graphics API that's why only D3D works and no other OS works, so unless Microsoft decides to support real pass through there is no way this will work with anything else sadly. For me it was important because I'm working on a 3D engine and I decided that I want to support all major desktop OS-es and it would have been really nice to be able to test real 3D acceleration within hyper-v instead of booting up another OS.
Hello infortek1991. I sympathize with you struggles, however, I have managed to get this working on my Windows 10 system with an i7-6700k using this VM file here Hyper-V VM File
Thank You for Your reply and help. I will try to use what You shared. Thank You very much again for Your help. :)
Hello infortek1991. I sympathize with you struggles, however, I have managed to get this working on my Windows 10 system with an i7-6700k using this VM file here Hyper-V VM File
Thank You for Your reply and help. I will try to use what You shared. Thank You very much again for Your help. :)
You're very welcome. Hope you are successful!
Hello, I installed well-done. But Hyper-V Graphics only 3MB and resolution screen 1024x786 (default) . How can I increase Graphics more to up 128MB and to use UIScale HiDPI mode? Thank you
Hello infortek1991. I sympathize with you struggles, however, I have managed to get this working on my Windows 10 system with an i7-6700k using this VM file here Hyper-V VM File
Thank You for Your reply and help. I will try to use what You shared. Thank You very much again for Your help. :)
You're very welcome. Hope you are successful!
thank you for your video. I managed to finish installation but I m getting this error. Do you have any advice for me where to look for a solution?
Hello infortek1991. I sympathize with you struggles, however, I have managed to get this working on my Windows 10 system with an i7-6700k using this VM file here Hyper-V VM File
Thank You for Your reply and help. I will try to use what You shared. Thank You very much again for Your help. :)
You're very welcome. Hope you are successful!
thank you for your video. I managed to finish installation but I m getting this error. Do you have any advice for me where to look for a solution?
I managed to skip various errors by saving (through hyper-v) and then starting again when the apple logo with the load bar is showing. After resuming from saved state the bar seemed to load way faster for some reason
I'm using an AMD CPU(Ryzen 5 4600H). The OS doesn't seem to work with me. I use the EFI file provided by @pidimensions. That doesn't work on my PC. My VM is struck on the Apple logo
I'm using an AMD CPU(Ryzen 5 4600H). The OS doesn't seem to work with me. I use the EFI file provided by @pidimensions. That doesn't work on my PC. My VM is struck on the Apple logo
Unfortunately AMD CPUs seem to not work in hyper-v Edit: for MacOS
mine gets the the apple logo but never progresses past that (no progress bar, just black screen with apple logo)
I got the same result on 12gen intel with 8192MB RAM allocated
edit: https://github.com/acidanthera/bugtracker/issues/2179#issuecomment-1572945606
I can't use this this file ,my i use i7 and win11,who can help me solve this problem? I'm not very familiar with this.
What generation of processor are you using and how much RAM is allocated to the VM? Also are you using my VM or did you make your own?
In my case:
EFI - CPU spoof for newer CPUs.zip
(i.e. drag and drop of /EFI/EFI from e.g. WinRar)PS:
Hyper-V Disk.vhdx
is just an empty vhdx fileInstall.vhdx
directly after I move and rename to macos_boot.vhdx
or something elseOpen Issues:
MOBO: HUANANZHI X99 F8D PLUS CPU: 2x/DUAL Xeon E5 2696v4 (2016, 14 nm, Haswell like) RAM: 128 GiB (4x 32 GiB) OS Name: Microsoft Windows 10 Pro OS Version: 10.0.19045 N/A Build 19045
Great, I am very glad to hear this success! Thanks for contributing
On Sun, Aug 27, 2023 at 7:35 PM Lucas Fernando Cardoso Nunes < @.***> wrote:
In my case:
- I used @pidimensions https://github.com/pidimensions EFI - CPU spoof for newer CPUs.zip https://drive.google.com/file/d/11sfgMR5M0vU-MDdi4KNXNy5VgCEnNhEt/view and MacOS Ventura Hyper-V VM - Intel CPU.zip https://drive.google.com/file/d/1XuzQw70lhWOZ6IojCA1qZuunmV6DjJ2t/view .
- If it takes more than 2 min (gets stuck) reset/restart the VM. I didn't change anything and it worked.
- 16000 MiB RAM and 8 CPU were kept + I had to add a network with internet (Default network) because it complained that it needed internet access to continue with the installation.
- I actually:
- Mounted the original Install.vhdx
- Gave it a drive letter on Windows' Disk Management
- Deleted /EFI and add /EFI/EFI folder with EFI - CPU spoof for newer CPUs.zip content (drag and drop of /EFI/EFI from in winrar)
- Made it offline in Disk Management to be able to use in the VM
PS:
- If you get support.apple.com/mac/startup ( https://support.apple.com/en-us/101666) error, reset/restart the VM and keep the mouse in the VM screen
- Hyper-V Disk.vhdx is just an empty vhdx file
- I will use Install.vhdx directly after I move and rename to macos_boot.vhdx or something else
- https://www.youtube.com/watch?v=Ob8KW2YwXk4 is a good reference
[image: image] https://user-images.githubusercontent.com/29926675/263559121-69052e30-a3ed-469b-9971-c2426e8e8580.png
MOBO: HUANANZHI X99 F8D PLUS CPU: 2x/DUAL Xeon E5 2696v4 (2016, 14 nm, Haswell like) RAM: 128 GiB (4x 32 GiB) OS Name Microsoft Windows 10 Pro OS Version: 10.0.19045 N/A Build 19045
— Reply to this email directly, view it on GitHub https://github.com/acidanthera/bugtracker/issues/2179#issuecomment-1694792931, or unsubscribe https://github.com/notifications/unsubscribe-auth/A54FW42PIK4G26NITAQAHMLXXPKSHANCNFSM6AAAAAAS7FKS7I . You are receiving this because you were mentioned.Message ID: @.***>
Sorry for OOT, @ANONIMNIQ.
@pigworlds I've successfully installed Mountain Lion in Hyper-V, thanks to your config (which I configured a little bit for older macos). Now, how to use hvfilecopyd, hvshutdownd, and hvtimesyncd daemons? Should I put it in /Library/LaunchDaemon?
@aguys123 Now I have the same question.
My setup: https://github.com/acidanthera/bugtracker/issues/2179#issuecomment-1694792931
I used steps from @lucasfcnunes, I have the same MB, and the Xeons are different and a bit less memory, but the main difference is Windows 11 instead of Windows 10.
In my case, the install get stuck on the Apple logo.
I have tried a clean install following the README but no luck I end up stuck on boot
I am attaching my logs here to see if someone points the problem on my setup
opencore-2023-08-31-151349.txt
ok maybe is my graphics card, is a 550 RX a lexa
Damn YouTube took down my video :(
Damn YouTube took down my video :(
@pidimensions was it Apple?
In my case, the install get stuck on the Apple logo.
ok maybe is my graphics card, is a 550 RX a lexa
@nmocruz did it work for you? *Your GPU shouldn't matter as it's not used by MacOS.
Idk it just said that "our team thinks it violates the content policy" for harmful or dangerous content
Hi All, I have actually created a repo on Github to make macOS on Hyper-V a little easier for everyone. Not only do I have additional instructions but I have created the VHDX drive with all OpenCore files, kexts, and config settings needed to boot on most Intel CPU's. Currently it should support all macOS native CPU's as well as 11th and newer CPU's; AMD is explicitly not currently supported and wont have support until that is added by acidanthera. You will still need to do a few things to get up and running, but all of that is outlined in the instructions and does not require any special linux or macOS skills and can be done completely from Windows.
Of course it goes without saying that GPU passthrough is not possible, and without graphics acceleration you should expect sluggishness and weird graphics from time to time on the newer macOS versions. Within my guide I have also added some options to speed up macOS to make it far less sluggish even without graphics acceleration.
You can find my repo Here which is updated when needed to ensure I am using the latest relevant hyper-v releases from acidanthera.
Would be nice to have GPU passthrough support, I think without that the mac performance it will make it usable just for certain pontual tasks. But I will test it later. I am having issues to make it work on my dual xeon setup. I get stuck on boot even with a ready image.
On Sat 4 Nov 2023, 06:44 balopez83, @.***> wrote:
Hi All, I have actually created a repo to make macOS on Hyper-V a little easier. Not only do I have additional instructions but I have created the VHDX drive needed to boot on most Intel CPU's. Currently it should support all macOS native CPU's as well as 11th and newer CPU's.
Of course it goes without saying that GPU passthrough is not possible, and without graphics acceleration you should expect sluggishness and weird graphics from time to time on the newer macOS versions. Within my guide I have also added some options to speed up macOS to make it far less sluggish even without graphics acceleration.
You can find my repo Here https://github.com/balopez83/macOS_On_Hyper-V which is updated when needed to ensure I am using the latest relevant hyper-v releases from acidanthera.
— Reply to this email directly, view it on GitHub https://github.com/acidanthera/bugtracker/issues/2179#issuecomment-1793362097, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHGRZKAHLI4VB4K2HEXRZLYCXP5DAVCNFSM6AAAAAAS7FKS7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJTGM3DEMBZG4 . You are receiving this because you were mentioned.Message ID: @.***>
Can someone use this? I don't really understand how to create macos vm for hyper-v. I can download installer.dmg ... then I need to create VHDX image from it, but how to do this from Windows? Also, how to attach OpenCore to the VM and where exctly to use MacHyperVSupport.kext? To put it in OpenCore and crete new cofig.plist maybe?