Serial crash when trying to boot t6000 dev kernel with hypervisor about m1n1

[marcan]

That means the guest is panicking and rebooting the machine. The hypervisor makes no attempt to stop the guest from doing that; it is a thin layer, not a security boundary. So if the guest kills the machine, the hypervisor goes along with it.

You should look at the serial log from macOS (available on the secondary USB ACM interface) to figure out why it's doing that.

Are you perhaps trying to boot macOS from a m1n1 proxy installed via the Asahi Linux installer? That won't work - to boot macOS you need to be running the OS volume macOS was installed under, which means you need to install m1n1 with kmutil/bputil on top of an existing macOS install. If you try to boot the macOS kernel under an Asahi Linux volume it'll just panic when it can't mount the root filesystem.

[rockinrobstar]

Yes, you caught me red handed, and now that you have explained it - it makes more sense. I will ask some more questions on irc about installing a 2nd macOS Volume (avoiding touching my original macOS install for now) and will attempt to update the wiki so others don't follow my folly. Thanks for your quick reply.