9/23/2023 0 Comments Qemu m1![]() This disk image is currently unformatted, so we get the messages about formatting it with fdisk first before continuing:įrom the fdisk menu select option 1 to create a DOS Primary partition:Īfter rebooting, the VM attempts to boot from c: but it’s still blank at this point, this was the same issue during the Windows 95 install too. Now booting up we get the install menu from the boot floppy: ![]() We’ll add a floppy for the boot disk, a cdrom iso, and then we can correctly boot: On the next page you can again configure the boot iso, but since the Windows 98 iso I have is not bootable and we need to use a boot floppy, check the ‘Skip ISO boot’ option instead. What I found did work was to avoid using the Windows option on the first page of dialogs, and use the Custom/Other option instead. After testing different options, I found that the default option in the VM setup menus to add a boot iso apparently assumes that iso is actually bootable, and then if it’s not it doesn’t even seem to try booting from the floppy, and strangely reports the error “Boot failed: could not read the boot disk” A quick search on the UTM project’s github site didn’t find any similar issues. Next I tried 4.0.0 beta and had the same issue. img floppy images, and none of them would boot. I’m not sure if this is an issue with this 4.0.1 beta, but I tried multiple. up, not matter what option I use, it wouldn’t boot from the floppy disk image: Next I added a removable disk, type floppy, and attached a Windows 98 floppy disk boot image:īooting. Next I configured the VM with i386 emulation, 256MB, and a 1GB disk:: On the next page I configured the Windows 98 iso and disabled the UEFI boot option: Using UTM 4.01 beta, from the first menu I selected the Windows option: I previously played around with the UTM frontend for QEMU on my M1 MacBook Pro, and thought I’d give installing Windows 98 a go. The following config steps maybe useful if you’re running into the same issues, but if you’ve managed to get a Windows 98 working under UTM leave a comment and let me know! Most importantly, even if I ever managed to fully boot the macOS kernel, emulating macOS is useless anyways.This will never boot anything close to graphical macOS UI.Userspace is instead borrowed from iOS 14 b3.Absolutely nothing is supported: literally only the kernel and the serial port works, not even the userspace since there’s no disk driver.And the macOS kernel will boot into launchd.Tldr I couldn’t get the boot floppies to recognize the cdrom iso when using QEMU was configured with UTM, but runing QEMU from the shell with the same floppy and cdrom iso imaged worked completely fine. Emulating iOS is useful for security research when jailbreak is not available.This approach will help with none of these: There are only three reasons I can think of for emulating macOS: security research, software development without a real Apple Silicon machine, and Hackintoshing. as for Hackintosh: macOS uses CPU instructions that aren’t available yet on non-Apple ARM CPUs, so you can’t have hardware accelerated virtualization, only very slow emulation.Not useful for software dev: QEMU’s CPU emulation doesn’t support Apple Silicon-specific features, such as Rosetta’s memory ordering or the APRR JIT.Apple Silicon Macs already support kernel debugging. I researched this this not because it’ll be practical, but only to understand how an Apple Silicon Mac works.īesides, Hackintoshes are often built when Apple’s own hardware isn’t fast enough in this case, Apple’s ARM processors are already some of the fastest in the industry. This will never be a Time Train: only a science experiment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |