deedezz
deedezz
I encounter the same issue with the Catalina image, while we can see a larger backtrace thanks to the higher screen resolution:  I deleted the former Docker images and...
Hello, As I precised above, removing the USB forwarding line changes nothing at all. As you can see in the backtrace, this "Unknown Opcode" CPU fault seems to lay in...
Actually the code simply lays in its own kernel extension file (the `macOS Base System/System/Library/Extensions/corecrypto.kext/Contents/MacOS/corecrypto` file from the `diff/home/arch/OSX-KVM/BaseSystem.img` image from the container). Actually the code at `_gcm_init + 8e`...
Additional insight: * Here is the QEMU command run by `sosumi` (non-panicking) `/snap/sosumi/18/usr/bin/qemu-system-x86_64 -enable-kvm -m 2G -machine q35,accel=kvm -smp 4,cores=2 -cpu Penryn,vendor=GenuineIntel,kvm=on,+sse3,+sse4.2,+aes,+xsave,+avx,+xsaveopt,+xsavec,+xgetbv1,+avx2,+bmi2,+smep,+bmi1,+fma,+movbe,+invtsc -device isa-applesmc,osk=ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc -smbios type=2 -object rng-random,id=rng0,filename=/dev/urandom -device virtio-rng-pci,rng=rng0...
It looks like it may be linked to the `+ssse3` flag in the Docker-OSX configuration, which is not present in Sosumi`'s. The CoreCrypto module does a CPUID flag check on...
Hello, Regarding your last diff, is this a change that you done or a change that you are projecting to do? It seems that the mentions of [CPU configuration](https://github.com/sickcodes/Docker-OSX/search?q=ssse3) in...
> it's only occurring when qemu is unallowed to use /dev/kvm or when it's not passed in on my host Thanks for the remarks! Actually it seems that it may...