Installer GUI not starting (DDA/Graphics)

[LogicFan]

Here is my computer Ryzen 5950X B550I AORUS PRO AX Nvidia 1080 Ti Windows 11

Here is the error message. I've updated config.plist as suggested by one of the notes in this repo.

here is my config.plist config.plist.txt

Thanks for the help!

[Qonfused]

Looks like it gets stuck in about the same spot in GUI initialization as in https://github.com/Qonfused/OSX-Hyper-V/issues/12#issuecomment-2223117435. You do have a npci=0x3000 boot arg that appears to disable gIOPCITunnelledKey debugging and other PCI configuration behavior that'd I'd recommend disabling -- so far that's the most relevant change I can observe in your config.plist.

I figure you've seen the linked issue as you've changed the same Booter quirks that user did. They aren't necessary to change though I don't see a detrimental effect at this point in booting macOS (you've basically reached the installer but don't have any graphical output initialized).

While not directly related to this issue, I can see you've enabled DummyPowerManagement and updated the cpuid_cores_per_packages kernel patches for 16 cores, which besides from applying the AMD Vanilla kernel patches are the main changes required for 3950X/5950x/7950x AMD systems. I mostly note this for other users who may be tracking the same issue from #12.

[LogicFan]

Do you have some suggestions on what I should touch next? thank you.

[Qonfused]

As I've mentioned before, for whatever reason macOS isn't switching or initializing display output for the virtual display. launchd for example shows that we've booted into recovery but can't find the language chooser.

There are some other compounding issues -- I did notice that the NVRAM -> Delete entry was moved under the wrong spot (it should be located at the same level as NVRAM -> Add): ^ Make sure you also remove the npci=0x3000 boot arg (I don't see why this should be needed in a Hyper-V VM).

Additionally, there isn't an entry for the Monterey+ version of MacHyperVSupport package in your Kernel -> Add entries: https://github.com/Qonfused/OSX-Hyper-V/blob/b16b38a3533386bbba4c083d84344334839c05fa/src/build.yml#L18-L30

What version of macOS are you booting (is it Big Sur or earlier)?

[LogicFan]

I am trying to boot to Sonoma.

I've updated the plist as suggested. But still encounter the same issue as before. config.plist.txt

[OMGitsPipp]

i also can't boot into the installer, though it just reboots after the handoff

[Qonfused]

That sounds like a different issue than above. I'm not sure whether you mean efiboot or XNU handoff (1st or 2nd stage of boot), but in either case you may be seeing an immediate reboot after a kernel panic.

I'd verify that you've applied AMD kernel patches in the correct place in your config.plist and check whether you need to also apply the core-count patch (also from the same repository). Beyond that, there shouldn't be much work required to get VMs booting on an AMD platform.

For debugging, make sure you've using a DEBUG build of the project or are using the below config.plist properties: https://github.com/Qonfused/OSX-Hyper-V/blob/e051c1afdfeca97f97415b6ed9cd9dc0123da6f2/src/config.yml#L79-L102

This should stop and leave kernel panics on-screen and ideally save panics in a panic-YYYY-MM-DD-HHMMSS.txt file on the EFI virtual disk.

[OMGitsPipp]

I meant XNU I think, I've applied the patches correctly and I do have the debug build and the config but it just immediately reboots, here's the log and config though
opencore-2024-10-13-060944.txt config.zip

[Qonfused]

You'll want to also add this rd/wrmsr patch from https://github.com/Qonfused/OSX-Hyper-V/issues/5#issue-2217345429:

Follow the AMD section of the Dortania Install guide for your CPU family. However, in addition to the AMD kernel patches (for AMD CPU families 15h, 16h, 17h and 19h), the below kernel patch is required for High Sierra and above:

Kernel:
  Patch:
    - Arch:                 String  | "x86_64"
      Base:                 String  | "_cpu_syscall_init"
      Comment:              String  | "flagers - kill invalid wrmsr | 10.13+"
      Count:                Integer | 3
      Find:                 Data    | "0F30"
      Identifier:           String  | "kernel"
      MaxKernel:            String  | "24.99.99"
      MinKernel:            String  | "17.0.0"
      Replace:              Data    | "9090"

This isn't included in the AMD kernel patches; it's an issue unique to Hyper-V that I had forgotten to point out.

Otherwise this looks fine. I'd retry with this patch and see if the issue still persists (or if you get a kernel panic).

[OMGitsPipp]

that indeed helped