-
-
Notifications
You must be signed in to change notification settings - Fork 82
Add Windows 11 VM Docs #206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
420c954 to
bfb45f0
Compare
|
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. |
|
That's totally fair, i'm flexible with you adding that change :) |
|
Ok, I'll work on it in my free time and add it as a suggestion change to your PR when it's ready. |
|
TYVM! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mkdir windows11 does not close its code tag
a905473 to
a4fad88
Compare
|
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. |
|
That's good :) at least qemu is running for sure |
|
Any update on libvirt problem? @Zlendy if not, i can try to replicate. |
|
Unfortunately not, the error message is this: 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. |
|
Alright, imma create a arm64 debian vm on macOS to replicate then |
|
macOS works fine, this only happens in Asahi Linux using libvirt |
|
Oh, well.. lemme install asahi linux then 💀 |
|
Update: downloading a debian 13 ISO worked, and it booted successfully. I am downloading the arm64 image of windows 11 currently on Asahi. |
|
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. |
|
@Zlendy |
|
I never would've guessed that was the problem, you deserve a medal 🏅 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
|
@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 👍🏻 |
|
@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 |
|
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? |
|
Will do my best to fix it up, thank you! |
0135cbd to
74bbb6f
Compare
|
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 |
|
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. |
1b00740 to
a953a5b
Compare
5538d3e to
6efb86c
Compare
|
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. |
Signed-off-by: Kokomo123 <jyvkcxe1@duck.com>
8c77065 to
0cacfb7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This needs to be rebased
|
Will attempt to rebase, rebasing on git isn't my strong suit, thank you for being patient with me! |
57c7325 to
0cacfb7
Compare
|
💀 this is gonna be a while.. oh boy.. |
Signed-off-by: kokomo123 <70863536+kokomo123@users.noreply.github.com>
|
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. |
|
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. |
|
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. |
|
my local branch was still having the 'Merge branch 'main' into XXX' commit I am not sure how to fix that commit honestly |
|
Use If you'd like, I can fix this for you when I get out of work. |
|
Yes please if you can. I'll reopen the PR and restore the remote branch |
|
Converting this to a draft for now (i also had the allow edits by maintainers checked off this entire time, oops..) |
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. :)