MacOS fails to start, no obvious logs

[tomchiverton]

I've followed https://github.com/quickemu-project/quickemu/wiki/03-Create-macOS-virtual-machines on Ubuntu 22.04 LTS, quickemu from the PPA.

I've chmod'd my home folder, and done the ignore_msrs change, as prompted.

No obvious errors from quickget, but nothing happens at the end of quickemu

I don't see an option for more detailed logs.

tchiverton@noctua:/media/HDD-auto/quickemnu$ quickemu --vm macos-big-sur.conf
Quickemu 4.9.4 using /usr/bin/qemu-system-x86_64 v7.0.0
 - Host:     Ubuntu 22.04.4 LTS running Linux 6.5 (noctua)
 - CPU:      Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
 - CPU VM:   1 Socket(s), 2 Core(s), 2 Thread(s), 8G RAM
 - BOOT:     EFI (macOS), OVMF (OVMF_CODE.fd), SecureBoot (off).
 - Disk:     macos-big-sur/disk.qcow2 (96G)
             Looks unused, booting from macos-big-sur/RecoveryImage.img
 - Recovery: macos-big-sur/RecoveryImage.img
 - Display:  SDL, qxl-vga, GL (on), VirGL (off)
 - Sound:    intel-hda
 - ssh:      On host:  ssh user@localhost -p 22220
 - 9P:       On guest: sudo mount_9p Public-tchiverton
 - smbd:     On guest: smb://10.0.2.4/qemu
 - Network:  User (virtio-net)
 - Monitor:  On host:  nc -U "macos-big-sur/macos-big-sur-monitor.socket"
             or     :  socat -,echo=0,icanon=0 unix-connect:macos-big-sur/macos-big-sur-monitor.socket
 - Serial:   On host:  nc -U "macos-big-sur/macos-big-sur-serial.socket"
             or     :  socat -,echo=0,icanon=0 unix-connect:macos-big-sur/macos-big-sur-serial.socket
cat: macos-big-sur/macos-big-sur.pid: No such file or directory
 - Process:  Starting macos-big-sur.conf as macos-big-sur ()

[tomchiverton]

There is a single line in macos-big-sur/macos-big-sur.log

qemu-system-x86_64: Property 'Haswell-v4-x86_64-cpu.ept' not found

Similar to #1214 ?

I don't know what any of this means, but apparently was helpful last time ?

# lscpu 
Architecture:            x86_64
  CPU op-mode(s):        32-bit, 64-bit
  Address sizes:         39 bits physical, 48 bits virtual
  Byte Order:            Little Endian
CPU(s):                  8
  On-line CPU(s) list:   0-7
Vendor ID:               GenuineIntel
  Model name:            Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
    CPU family:          6
    Model:               94
    Thread(s) per core:  2
    Core(s) per socket:  4
    Socket(s):           1
    Stepping:            3
    CPU max MHz:         4000.0000
    CPU min MHz:         800.0000
    BogoMIPS:            6799.81
    Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 s
                         s ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nons
                         top_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm p
                         cid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
                          cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow flexpriority ept vpid ept_ad fsgsbase ts
                         c_adjust sgx bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv
                         1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp vnmi md_clear flush_l1d arch_capabili
                         ties
Virtualisation features: 
  Virtualisation:        VT-x
Caches (sum of all):     
  L1d:                   128 KiB (4 instances)
  L1i:                   128 KiB (4 instances)
  L2:                    1 MiB (4 instances)
  L3:                    8 MiB (1 instance)
NUMA:                    
  NUMA node(s):          1
  NUMA node0 CPU(s):     0-7
Vulnerabilities:         
  Gather data sampling:  Vulnerable: No microcode
  Itlb multihit:         KVM: Mitigation: VMX disabled
  L1tf:                  Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable
  Mds:                   Mitigation; Clear CPU buffers; SMT vulnerable
  Meltdown:              Mitigation; PTI
  Mmio stale data:       Mitigation; Clear CPU buffers; SMT vulnerable
  Retbleed:              Mitigation; IBRS
  Spec rstack overflow:  Not affected
  Spec store bypass:     Mitigation; Speculative Store Bypass disabled via prctl
  Spectre v1:            Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2:            Mitigation; IBRS; IBPB conditional; STIBP conditional; RSB filling; PBRSB-eIBRS Not affected; BHI Not affect
                         ed
  Srbds:                 Mitigation; Microcode
  Tsx async abort:       Mitigation; TSX disabled

[unicxa]

same issue here

[tomchiverton]

Maybe https://github.com/quickemu-project/quickemu/issues/1114 is useful too ?

[jonhartwell]

I am also getting this meesage along with the "Connect to SPICE" error when starting the Ventura VM.

[lj3954]

Maybe #1114 is useful too ?

The "fix" to that issue is what caused this issue.

[lj3954]

Duplicate of #1236. Fixed in #1225. You may use quickemu directly from git in the meantime until v4.9.5 is released containing the fix.

[lj3954]

@flexiondotorg I would recommend quickly releasing 4.9.5, if only for this one fix. Dozens of people have reported this single issue.

[tomchiverton]

4.9.5 isn't out yet according to https://github.com/quickemu-project/quickemu/releases and it's not in the PPA either.

[tomchiverton]

Replacing quickemu and quickget with the files from Git, then removing the existing folders and starting again from scratch with https://github.com/quickemu-project/quickemu/wiki/03-Create-macOS-virtual-machines gets at least to a booting "macOS Base System", for macos sonoma