How to access the BIOS of a VM on Proxmox or VirtualBox
ECtoZz_
Posted messages
8
Registration date
Status
Membre
Last intervention
-
avion-f16 Posted messages 19182 Registration date Status Contributeur Last intervention -
avion-f16 Posted messages 19182 Registration date Status Contributeur Last intervention -
Hello, I am looking to access the BIOS of a VM on Proxmox,
because to use WSL2, the virtualization option needs to be enabled in the BIOS.
Thank you in advance for your support.
because to use WSL2, the virtualization option needs to be enabled in the BIOS.
Thank you in advance for your support.
3 réponses
I have already activated it on the physical machine, but on the virtual machine it tells me that it is not activated, which means they are independent and therefore have a different BIOS configuration.
You are stubborn: there is no BIOS in a "physical" or virtual OS: the BIOS is by definition integrated into the motherboard and launched before the operating system.
This is related to the installation and configuration of WSL, and perhaps to the fact that if it is not a Windows 10 Pro version, the Windows hypervisor is not functional unlike what is observed for other virtual machines (e.g., VMWare).
This is related to the installation and configuration of WSL, and perhaps to the fact that if it is not a Windows 10 Pro version, the Windows hypervisor is not functional unlike what is observed for other virtual machines (e.g., VMWare).
Hello,
??
There is no BIOS in a virtual machine, WSL or not; the virtualization activation option (before installing WSL) is found, if it exists, in the BIOS...of the PC.
??
There is no BIOS in a virtual machine, WSL or not; the virtualization activation option (before installing WSL) is found, if it exists, in the BIOS...of the PC.
Hello,
The purpose of a QEMU/KVM (Proxmox) and VirtualBox virtual machine is to simulate a BIOS or UEFI type computer, with all components being reproduced, including this piece of software.
If the VM didn’t have a BIOS or UEFI, it wouldn’t be able to start a program (bootloader, OS, ...) compatible with BIOS / UEFI ;)
As for entering the menu, it depends on the implementation of that BIOS / UEFI.
On QEMU/KVM, the virtual BIOS does not have a menu, but the virtual UEFI (OVMF) does have one accessible via the F2 key.
For WSL or containers, it is of course different.
But indeed, CPU virtualization (Intel VT-x or AMD-V) is activated in the host machine's BIOS/UEFI and not in the virtual machine's :)
The purpose of a QEMU/KVM (Proxmox) and VirtualBox virtual machine is to simulate a BIOS or UEFI type computer, with all components being reproduced, including this piece of software.
If the VM didn’t have a BIOS or UEFI, it wouldn’t be able to start a program (bootloader, OS, ...) compatible with BIOS / UEFI ;)
As for entering the menu, it depends on the implementation of that BIOS / UEFI.
On QEMU/KVM, the virtual BIOS does not have a menu, but the virtual UEFI (OVMF) does have one accessible via the F2 key.
For WSL or containers, it is of course different.
But indeed, CPU virtualization (Intel VT-x or AMD-V) is activated in the host machine's BIOS/UEFI and not in the virtual machine's :)