qemu + haxm does not work to boot and run Mac OS X High Sierra

[Marietto2008]

Hello,

I tried to boot Mac Os X High Sierra with Qemu (3.1.0) and HAXM,but it did not work. Maybe someone can help me to fix it in some way ? Would be nice to make it work,since HAXM does not support nested virtualization...

C:\Programmi\qemu\qemu-system-x86_64 -m 3072 -cpu Penryn,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on -machine pc-q35-2.9 -smp 4,cores=2 -usb -device usb-kbd -device usb-tablet -device isa-applesmc,osk="ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" -drive if=pflash,format=raw,readonly,file=C:\Programmi\qemu\OVMF_CODE.fd -drive if=pflash,format=raw,file=C:\Programmi\qemu\OVMF_VARS-1024x768.fd -smbios type=2 -device ich9-intel-hda -device hda-duplex -device ide-drive,bus=ide.2,drive=Clover -drive id=Clover,if=none,snapshot=on,format=qcow2,file=C:\Programmi\qemu\Clover.qcow2 -device ide-drive,bus=ide.1,drive=LinuxHDD -drive id=LinuxHDD,if=none,file=I:\OS\Images\mac_hdd.img,format=qcow2 -device ide-drive,bus=ide.0,drive=LinuxDVD -drive id=LinuxDVD,if=none,snapshot=on,media=cdrom,file=I:\OS\Images\HighSierra.iso -accel hax

HAX is working and emulator runs in fast virt mode.
C:\Programmi\qemu\qemu-system-x86_64: warning: Ignoring ROMD region 0x00000000ffc84000->0x0000000100000000
C:\Programmi\qemu\qemu-system-x86_64: warning: Ignoring ROMD region 0x00000000ffc00000->0x00000000ffc84000
VCPU shutdown request
VCPU shutdown request
VCPU shutdown request
VCPU shutdown request
VCPU shutdown request
VCPU shutdown request
VCPU shutdown request
VCPU shutdown request

[raphaelning]

We don't plan to provide official support for running macOS guests, but we're open to pull requests for this feature.

"VCPU shutdown request" indicates a panic in the HAXM driver. Could you post the HAXM driver log?

[HaHoYou]

The HAXM driver log can be got from Windbg. Also, would you help to provide the MacOS iso file and other files you used, as well as the method how you made them.

[Marietto2008]

Thanks. You can find everything below (the mac os x high sierra iso file and the log file). PS : About how I have obtained the mac os x iso file : I got it following this tutorial : https://github.com/kholia/OSX-KVM/tree/master/HighSierra

https://drive.google.com/open?id=1sYLvF8tgd3baCD-IVoAJ1kpx8SggyqOq

[Marietto2008]

Anyway,I have attached the log file below..

High_Sierra.LOG

[Marietto2008]

Everything is ok ? did u get everything you need ? Il giorno gio 3 gen 2019 alle ore 05:10 Huang, Jun <notifications@github.com> ha scritto:

…

The HAXM driver log can be got from Windbg. Also, would you help to provide the MacOS iso file, as well as the method how you made it. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#149 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAuGixcQ_emJumj47PyZtq_dd2QXTQdmks5u_YKhgaJpZM4ZmoLk> .

-- Mario.

[raphaelning]

did u get everything you need ?

Yes, thanks for providing all the details! It seems the error has nothing to do with the macOS guest image (mac_hdd.img or HighSierra.iso), because I was able to reproduce the same error with the following QEMU command:

qemu-system-x86_64 -machine q35 -drive if=pflash,format=raw,readonly,file=X:\path\to\OSX-KVM\OVMF_CODE.fd -accel hax

Without -accel hax, QEMU can boot to the OVMF shell. Therefore, the first step is to get OVMF working on HAXM. This is the first time we have tested booting UEFI firmware (OVMF) on HAXM, so there can be surprises.

[HaHoYou]

Yes, we got them, thanks.

[Marietto2008]

news ?

[raphaelning]

Today we received an important tip from the QEMU community (many thanks to @AlexAltea) on why OVMF doesn't yet run on HAXM:

http://lists.nongnu.org/archive/html/qemu-devel/2019-01/msg08482.html

If we implement the proposed changes, we should be a big step closer to getting OVMF booting.

[Marietto2008]

nice.

[ewoks]

any progress on this? tnx

[tibidi]

I have the same issue any progress ?

[Marietto2008]

do u remember me ? any progress ? Il giorno mar 1 ott 2019 alle ore 17:54 TIBIDI <notifications@github.com> ha scritto:

…

I have the same issue any progress ? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#149?email_source=notifications&email_token=AAFYNC5TUNO7S5ML5CZUQOLQMNXEZA5CNFSM4GM2QLSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEABYWTA#issuecomment-537103180>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAFYNC4ZK6M2KHB4LKUMD4DQMNXEZANCNFSM4GM2QLSA> .

-- Mario.