ghost82

Thank you for your time MaLd0n, unfortunatly it doesn't boot, same "still waiting for root device". I'll take as it is, this sata controller doesn't like an entry name in DSDT and I'll inject the whole fixed DSDT or the SSDT to hide S00, which both are tested to work ok. Very strange...

Full dump: https://filetransfer.io/data-package/eWWO9LDW#link Ioreg: https://filetransfer.io/data-package/z2EwPhSj#link See SSDT-0-SATA.aml I'm using to mask S00 of the SATA controller, without this pci1b4b,9230 is named S00 and the system doesn't boot.

Hi Mald0n, thanks for your reply. I inject nothing, the default is to inject the ahci 3rd party kext, but even without it I'm able to boot with that marvell sata controller (the disk is detected as external but no issue), when DSDT doesn't give the S00 name. So the only thing that changes is the rename of pci1b4b,9230 to S00 (I even try SATA name instead of S00); if it's renamed it doesn't boot.

Hello community, Short story: I'm running a mac os vm in a qemu virtual machine for years now without any issue; after upgrading qemu to latest v. 8.0.0 version my vm didn't boot anymore. The vm is configured with a sata controller passthrough, and after some tests I found the issue in the DSDT; I'm able to run again the vm now, but I don't understand why it doesn't boot with the defective DSDT. Here is a picture of the ioreg tree when I'm able to boot: This DSDT (part of it..) works: Scope (\_SB) { Scope (PCI0) { Device (S08) { Name (_ADR, 0x00010000) // _ADR: Address } ... ... This DSDT (part of it...) doesn't work: apple complaining "still waiting for root device" with prohibition symbol: Scope (\_SB) { Scope (PCI0) { Device (S08) { Name (_ADR, 0x00010000) // _ADR: Address Device (S00) { Name (_ADR, Zero) // _ADR: Address } } ... ... ------- So it works if DSDT defines S08, without defining S00 (rename of pci1b4b,9230). Question is simple: anyone knows why this is happening? Thank you!

Thank you Mald0n, if this is a preinstalled image I'm going to try it tomorrow after finishing the download, in a qemu vm with sandy bridge cpus to see if I can boot it with some workarounds. Update: not sure if it's a preinstalled system or only the installation iso, since it was uploaded first on 7th june and it's "only" 15 Gb, it seems it's the installation iso I know I'm asking a lot, but would it be possible to share a preinstalled ventura disk image, vmdk, img doesn't matter (it can be also a 1:1 disk clone). It seems the only option for me to try with my sandy bridge (I don't have any other more recent cpu to finish/perform/swap the installation)