search

quickemu-project / quickemu

Quickly create and run optimised Windows, macOS and Linux virtual machines
MIT License
10.73k stars 470 forks source link

Install of Big Sur repeatedly fails #153

Closed erkannt closed 3 years ago

erkannt commented 3 years ago

Expected behaviour

Able to install mac os by booting from the Base Install.

Actual behaviour

I've attached screenshots of the installer logs.

Any ideas for things to try, logs to generate etc. would be much appreciated. I'm starting to loose my mind.

Steps to reproduce the behaviour

Quickemu output

Run quickemu or quickget and paste the output here.

> quickemu --vm macos-big-sur.conf
Quickemu 2.2.6 using /usr/bin/qemu-system-x86_64 v6.0.0
 - Host:     Pop!_OS 20.04 LTS running Linux 5.13 (pop-os)
 - Guest:    Starting macos-big-sur.conf as macos-big-sur
 - CPU:      AMD Ryzen 7 1700X Eight-Core Processor
 - CPU VM:   1 Socket(s), 4 Core(s), 2 Thread(s), 12G RAM
 - BOOT:     EFI (macos)
 - Disk:     macos-big-sur/disk.qcow2 (128G)
             Looks unused, booting from macos-big-sur/RecoveryImage.img
 - Recovery: macos-big-sur/RecoveryImage.img
 - Display:  SDL, qxl, GL (on), VirGL (off)
 - ssh:      On host:  ssh user@localhost -p 22220
 - SPICE:    On host:  spicy --title "macos-big-sur" --port 5930
 - 9P:       On guest: sudo mount_9p Public-hff
 - 9P:       On host:  chmod 777 /home/hff/Public
             Required for macOS integration 👆

Linux Distribution & Kernel

> lsb_release --all
No LSB modules are available.
Distributor ID: Pop
Description:    Pop!_OS 20.04 LTS
Release:        20.04
Codename:       focal
> uname -a
Linux pop-os 5.13.0-7614-generic #14~1631647151~20.04~930e87c-Ubuntu SMP Fri Sep 17 00:26:31 UTC  x86_64 x86_64 x86_64 GNU/Linux
> qemu-system-x86_64 --version
QEMU emulator version 6.0.0 (Debian 1:6.0+dfsg-2expubuntu1~focal1.0)
Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers

big-sur-failed-to-extract-bytes big-sur-verification-failure

github-actions[bot] commented 3 years ago

Hello there 👋 Thanks for submitting your first issue to the Quickemu project 🐛 We'll try and take a look at your issue soon ⏲

In the meantime you might want to join the Wimpys World Discord 🗣 where we have a large community of Linux 🐧 enthusiasts and passionate open source developers 🧑‍💻

You might also be interested in following Wimpys World Twitch 📡 channel where Wimpy streams let's code video, including this project, several times a week. A back catalog of past live stream and other Linux related content is available on Wimpys World YouTube 📺 channel.

aredey commented 3 years ago

I had a very similar issue so ended up (successfully) installing Catalina instead, thinking I'd update to Big Sur from there. The update image seems to be successfully downloaded but the disk space on the Catalina install seems too small, the MacOS updater reports that an extra 2GB (or more) is required.

This is my first experience with MacOS or Qemu though fairly comfortable with Linux (using Ubuntu Mate 20.04 for this experiment) so tried to find something similar to gedit to expand the Qemu harddisk, ither from the Disk Utility, using the MacOS Utilities virtual disk or I'd be happy to spin up a virtual systemRescueCD or other live "CD", but nothing worked so far.

So my question is: is it possible to extend the virtual standard disk created by quickemu somehow? Any pointer would be greatly appreciated!

SneWs commented 3 years ago

A shot in the dark, make sure to have executed echo 1 | sudo tee /sys/module/kvm/parameters/ignore_msrs and try again.

SneWs commented 3 years ago

I had a very similar issue so ended up (successfully) installing Catalina instead, thinking I'd update to Big Sur from there. The update image seems to be successfully downloaded but the disk space on the Catalina install seems too small, the MacOS updater reports that an extra 2GB (or more) is required.

This is my first experience with MacOS or Qemu though fairly comfortable with Linux (using Ubuntu Mate 20.04 for this experiment) so tried to find something similar to gedit to expand the Qemu harddisk, ither from the Disk Utility, using the MacOS Utilities virtual disk or I'd be happy to spin up a virtual systemRescueCD or other live "CD", but nothing worked so far.

So my question is: is it possible to extend the virtual standard disk created by quickemu somehow? Any pointer would be greatly appreciated!

This is a separate topic that does not seem to belong to this thread. However executing qemu-img resize image.qcow2 +SIZE adjusting the image.qcow2 to your path and setting the size to something like +50GB or whatever size you want should do the trick.

After that, start up the VM and run Disk Utilities and expand the OS disk with the new free space.

aredey commented 3 years ago

Thanks for the reply and suggestions. I was thinking debating whether I should "hijack" this topic or start a new one, but my goal is to install Big Sur, and I had the same/similar issue as described in the opener, so my attempted work around was to install Catalina and then use MacOs' native upgrade process - which also failed due to lack of disk size.

I have started the expansion as you described (based on https://fatmin.com/2016/12/20/how-to-resize-a-qcow2-image-and-filesystem-with-virt-resize/), and the first step seemed to work, so I have now presumably large enough virtual disk but the partition is not expanded to the disk. I tried to use the suggested command, virt-resize -expand /dev/sda1 disk.qcow2 disk.orig.qcow2 which starts to process the expansion but fails with the following error: virt-resize: error: libguestfs error: /usr/bin/supermin exited with error status 1. so was trying to an alternate way. In Linux I tend to use gparted* from a live CD but I don't know the Macos equivalent tool or process.

*sorry for the typo above, not "gedit" but "gparted".

Happy to be deleted to stay on-topic...

erkannt commented 3 years ago

A shot in the dark, make sure to have executed echo 1 | sudo tee /sys/module/kvm/parameters/ignore_msrs and try again.

I did that, made no difference, sadly. I also set the disk size to 128GB, to avoid any space issues. I've also tried installing Catalina. That install fails after the first reboot during install. "macOs could not be installed on your computer" and suggests running hardware diagnostics.

Any other ideas or tricks would be greatly appreciated.

re: resizing IIRC resizing isn't really possible as Disk Util won't let you grow the main volume past the recovery volume that it hides form you.

SneWs commented 3 years ago

re: resizing IIRC resizing isn't really possible as Disk Util won't let you grow the main volume past the recovery volume that it hides form you.

From what I've done on my native macOS machines, using disk utility to grow and shrink even the system disks works just fine (boot camp for example needs this) perhaps see https://support.apple.com/guide/disk-utility/resize-a-disk-image-dskuc033a48f/mac for suggestions and searching the web a bit might help you figure it out.

aredey commented 3 years ago

I did that, made no difference, sadly. I also set the disk size to 128GB, to avoid any space issues. I've also tried installing Catalina. That install fails after the first reboot during install. "macOs could not be installed on your computer" and suggests running hardware diagnostics.

When I first (actually, about 3 times) tried on an earlier version of Mate (18.04) I was unable to just apt get quickemu it, so started a long weekend build up the dependencies (and their own dependencies) as per list in the prerequisits section. And updating (re-compiling) qemu actually totally locked up my computer and the forced power down made it completely scuppered. So I ended up installing Mate 20.04 from scratch, thinking this must be the most compatible install. I had some teething problem even with this, but in the end somehow worked - not sure what I did, but thus am a little apprehensive tweaking it for a while.

re: resizing IIRC resizing isn't really possible as Disk Util won't let you grow the main volume past the recovery volume that it hides form you.

Looks like I'll have to redo it with a larger initial disk size, then, once I figure out how to/where to set it in the bash script. But that is for another weekend...

flexiondotorg commented 3 years ago

Looks like I'll have to redo it with a larger initial disk size, then, once I figure out how to/where to set it in the bash script.