Add Windows 11 VM Docs

[kokomo123]

Per https://discussion.fedoraproject.org/t/tutorial-how-to-create-a-windows-11-vm/147506/ there were suggestions to add this to the docs of Asahi Linux, and I thought since it hasn't been added, I have sufficiently created a guide to the best of my ability using markdown and some copy/pasting from the forum thread. Feel free to edit/adjust it as the community / maintainers see fit as this seems decent enough, but i'm all ears for contributing to make it the best community windows 11 vm guide as it can possibly be. :)

[Zlendy]

I haven't tried to follow the guide yet but it looks good, nice work! 👍

I'd just like to suggest adding an option to set this up using QEMU+libvirt instead of plain old QEMU.
Many users such as myself prefer to use that front-end, if you'd like I can add this change to your PR.

[kokomo123]

That's totally fair, i'm flexible with you adding that change :)

[Zlendy]

Ok, I'll work on it in my free time and add it as a suggestion change to your PR when it's ready.

[kokomo123]

TYVM!

[Zlendy]

mkdir windows11 does not close its code tag

[Zlendy]

I feel like I almost got it, but there's some weird issue with libvirt that prevents me from running any VM, apparently.

qemu isn't the issue here because your script worked flawlessly.

[kokomo123]

That's good :) at least qemu is running for sure

[kokomo123]

Any update on libvirt problem? @Zlendy if not, i can try to replicate.

[Zlendy]

Unfortunately not, the error message is this:

BdsDxe: No bootable option or device was found.
BdsDxe: Press any key to enter the Boot Manager Menu.

This seems to indicate that the cdrom is not loaded correctly. But it's weird because I've done this so many times on x86-64 computers, this is the first time I've seen this lol.

To replicate it just create a VM with virt-install or virt-manager, any libvirt frontend should be able to replicate this.

[kokomo123]

Alright, imma create a arm64 debian vm on macOS to replicate then

[Zlendy]

macOS works fine, this only happens in Asahi Linux using libvirt

[kokomo123]

Oh, well.. lemme install asahi linux then 💀

[kokomo123]

Update: downloading a debian 13 ISO worked, and it booted successfully. I am downloading the arm64 image of windows 11 currently on Asahi.

[kokomo123]

Update: yeah it seems EDK2 firmware halts and doesn't load the image. I think we would be fine to just include the qemu instructions, and say libvirtd is unsupported at this time.

[kokomo123]

@Zlendy internal error: Child process (dmidecode -q -t 0,1,2,3,4,11,17) unexpected exit status 1: /sys/firmware/efi/systab: SMBIOS entry point missing
Sep 10 07:57:23 libvirtd[4831]: operation failed: Cannot find CPU model with PVR 0x025
This is probably why libvirtd isn't working, /sys/firmware/efi/systab doesn't have anything in it. Thus, the firmware doesn't know what to do. I hope this can be fixed, otherwise now, I am just going to push a slight edit to the docs saying "virt-manager is unsupported, please use qemu", as I have discovered through researching. https://www.reddit.com/r/AsahiLinux/comments/y7hplo/virtual_machines_on_asahi_linux/, and with default settings, toying around with the CD-rom device too. I wish libvirtd had better support on Asahi rn.

[Zlendy]

I never would've guessed that was the problem, you deserve a medal 🏅

[Zlendy]

LGTM!

[kokomo123]

@Conan-Kudo @chadmed Pinging just to make sure this is all LGTM, if there's any adjustments ya'll think is needed, feel free to let me know 👍🏻

[kokomo123]

@jannau Bump? Making sure this is all LGTM, if there's any adjustments, please let me know or if you can refer to someone that can look this over

[chadmed]

Sorry, I've been preoccupied.

Your commit history is a bit messed up. Can you please clean it up to remove the merge commits and follow the commit message format used everywhere else?

[kokomo123]

Will do my best to fix it up, thank you!

[kokomo123]

I have successfully completed the rebase, and squashed all the commits into one. Appropriately renamed it to sw: docs: as well as I have discovered through git commit history. I hope this is sufficient

[chadmed]

Can we please change the link to the Enterprise LTSC ISO to one that doesn't require a VLK to use? Linking to the official Windows 11 Pro ISO should suffice.

[kokomo123]

Apologies for the git spam, im really trying to squash from the merge that's necessary to avoid conflicts. Otherwise, this is the best I can do as long as there's no pending commits.

[davide125]

This needs to be rebased

[kokomo123]

Will attempt to rebase, rebasing on git isn't my strong suit, thank you for being patient with me!

[kokomo123]

💀 this is gonna be a while.. oh boy..

[chadmed]

You have completely messed up your branch.

Can you please fix this so that the only commit on your branch adds the Windows 11 guide, and fix that commit so that it does not try to mash up all the other documentation?

You should be rebasing your branch on top of main, not merging it. I can't even cherry-pick the commit because it has somehow squashed a whole bunch of changes to many files into itself.

[kokomo123]

I'm really sorry for messing this up, I was struggling with git trying to squash everything, instead I made it more damaging. I apologize again and will do better next time. I'm redoing this PR to save the headache entirely of doing it all over again, as it's already messed up.

[Zlendy]

You didn't have to delete the PR and remote branch, just redo it locally and force push your local branch to the remote one.

[kokomo123]

my local branch was still having the 'Merge branch 'main' into XXX' commit I am not sure how to fix that commit honestly

[Zlendy]

Use git reset --hard to overwrite your commit history with another, or git rebase your commits on top of main.

If you'd like, I can fix this for you when I get out of work.

[kokomo123]

Yes please if you can. I'll reopen the PR and restore the remote branch

[kokomo123]

Converting this to a draft for now (i also had the allow edits by maintainers checked off this entire time, oops..)

[Zlendy]

I guess the latest valid commit before you went straight into rebase hell is a953a5b
Could you confirm @kokomo123 ?

[kokomo123]

Can confirm, yes. that is when i changed the link

[Zlendy]

I'm done, to reset your branch with mine just run the following commands:

1. git switch add-win11-docs
2. git remote add zlendy https://github.com/zlendy/asahilinux-docs.git
3. git fetch zlendy
4. git reset --hard zlendy/fix-pr-206-commit-history
5. git push origin add-win11-docs --force

These are the steps I followed, I considered spending a little more time to explain things properly so you could learn what went wrong and why.

1. git switch main
2. git pull upstream main
3. git remote add kokomo123 https://github.com/kokomo123/asahi-docs.git
   add your repository as a remote
4. git fetch kokomo123 a953a5ba35f4d0a07a49c3f43f9f66e716c3b9be
   fetch latest valid commit from your repository
5. git switch -d a953a5ba35f4d0a07a49c3f43f9f66e716c3b9be
   switch to the latest valid commit
6. git switch -c fix-pr-206-commit-history
   switch to a new branch based on the latest valid commit
7. git rebase --interactive main
   squash commits and rebase the current branch on main
8. git push --set-upstream origin fix-pr-206-commit-history

Here's an asciinema recording of the previous commands if that makes it easier to follow for you: https://asciinema.org/a/fiM1WaazwiqrG8RoCZlnMyRyB

This decision is yours, but I'd appreciate it if you gave me credit for contributing to this PR using Co-authored-by: Zlendy <zlendy@proton.me>, just amend the commit and add that text as instructed in the link below.
https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors

[kokomo123]

Done and done, thank you so much zlendy, you were a life saver, me panicing over here and now im relieved that a kind fellow helped me fix up this branch, thank you again. You deserve another medal 🥇 sir.

[kokomo123]

@chadmed @davide125 After Zlendy helped me, this should be good to go. Thank you for your patience regarding this PR. It's been a whirlwind.