GitXplorerGitXplorer
b

fusion-m1-514-repro

public
0 stars
0 forks
0 issues

Commits

List of commits on branch main.
Verified
c53ea46e073b095ba76b45ce1106e99ffd7e52e9

Update README.md

mmitchellh committed 3 years ago
Verified
be328b48c7994123a217054b85dbcac2c1946f3c

Update README.md

mmitchellh committed 3 years ago
Verified
6c64f1f5ddb888df61175d152fb15891116feb4d

update Makefile

mmitchellh committed 3 years ago
Verified
5e7a24291585d526172121169afbdffb84ff737d

Update README.md

mmitchellh committed 3 years ago
Verified
72a1481d9c96a89f40a0da9c2bc9cf48163cdcda

update README

mmitchellh committed 3 years ago
Verified
0c8e06f951e46cafff47a456ee0a5f9a56542479

Commit

mmitchellh committed 3 years ago

README

The README file for this repository.

Fusion M1 NixOS w/ Kernel 5.14 Issue

This repository reproduces an issue I'm seeing: when installing NixOS with Linux Kernel 5.14, the VM spins to 100% CPU on boot (but never makes it past what looks like the EFI screen perhaps). This only happens on Fusion Public Tech Preview on Apple M1, and does NOT happen on Fusion 12 on Intel.

This matters because open-vm-tools requires at least kernel 5.14 for GUI support and that matters for my use case.

Requirements

Steps to Reproduce

All of these steps must be run on an M1 Mac computer. If you run it on an Intel machine there is no bug.

  1. make nixos.iso - This will create the NixOS ISO. If you want to recreate the ISO you must delete the old one. This will place the ISO in the current directory as nixos.iso.

  2. Create a VM in Fusion (manually). Settings I used:

  • From nixos.iso
  • 4 CPUs, 8192 RAM.
  • 150 GB disk, SATA important: switch NVMe to SATA! The Makefile assumes SATA device paths.
  • Full resolution display
  1. Boot it up. You'll log in automatically as the nixos user. Go to the root user and set the password to "root":
$ sudo su
$ passwd
  1. Get the IP address, should be 192.168.something from ifconfig.

  2. Optional: Take a snapshot here if you want to try this multiple times.

  3. Set NIXADDR=<ip address of VM> and run make vm/bootstrap-broken. This will reproduce the bug and automatically reboot the VM. Your CPU should spin to 100% (or 100% times the number of vCPUs). This process takes maybe 10 minutes until the reboot.

  4. Optional: You can restore from the snapshot and run make vm/bootstrap-good which uses a 5.10 kernel which works and does not bug out.