Closed lstocchi closed 5 months ago
This issue has been automatically marked as stale because it has not had activity in the last 6 months. It will be closed in 30 days if no further activity occurs. Please feel free to leave a comment if you believe the issue is still relevant. Thank you for your contributions!
This issue has been automatically closed because it has not had any further activity in the last 30 days. Thank you for your contributions!
Bug description
This is not really a bug of Desktop but more of Windows. Maybe we can add some message when creating a new podman machine or it can be added in the troubleshooting section (cc @themr0c) or just leave it as a closed issue so if someone makes a search they can find a sort of guidance.
When testing the onboarding i was trying to simulate an environment with WSL1 to see which were the errors the user could face. For some unknown reason, after having uninstalled everything and reinstalled wsl + virtual machine platform (vmp) the system was not able to create a podman machine. I saw these 2 errors based on how i installed/enabled wsl.
1 use case) the machine is clean (no wsl and vmp), i enabled wsl and vmp by using the
Turn Windows features on or off
section and rebooted the machine. I was able to install podman but then i was not able to create a podman machine. The error was2 use case) the machine was clean (no wsl and vmp), i installed wsl using
wsl --install
. I can see wsl app + vmp installed/enabled but when trying to create a podman machine i facedDifferent errors but related to the same issue. Even though the solution was explained in one of them (enabling virtualization in the BIOS) i was a bit puzzled because i saw it enabled in my features list.
Maybe we should add an additional message in the log view??
BTW the solution was to enable virtualization in the BIOS.
After enabling it i could see it in the task manager
Operating system
Windows 11
Installation Method
Installer from website/GitHub releases
Version
1.4.0
Steps to reproduce
No response
Relevant log output
No response
Additional context
No response