Cannot access Virtual Machine BIOS

G

gin

New Member
Mar 23, 2017
6
0
1
75
How do I access virtual machine windows 10 bios?
either boot is too fast for F2 or DEL or BIOS does not exist in VM
 
i have a dedicated proxmox server running opnsense however i need to disable pxe boot it takes to much time to boot the system, i have disabled it on the real bios but how do you do this in proxmox machine? thanks
 
I do have some sort of the same issue... I passthrough a HBA with 8 drives for my TrueNas vm runnning on Proxmox.
I did the TrueNas installation, then I passthrough the HBA card with my 8 disks attached (since it is a passthrough this controller / disk don't show up in (VM -> Options -> Boot Order) but now when I boot, the vm try to boot from the HBA disk instead of the VM os disk... any idea on how to change that permanently ? Pressing esc does not seems to work for me. the system try to boot from the hba and then detect probably the zfs data partition because I get : "This is a FreeNAS data disk and can not boot system. System halted."

If I press Esc at boot I can get the Boot device menu but I can't the Virtio-scsi Drive as default
 
Last edited:
tlex said:
I do have some sort of the same issue... I passthrough a HBA with 8 drives for my TrueNas vm runnning on Proxmox.
I did the TrueNas installation, then I passthrough the HBA card with my 8 disks attached (since it is a passthrough this controller / disk don't show up in (VM -> Options -> Boot Order) but now when I boot, the vm try to boot from the HBA disk instead of the VM os disk... any idea on how to change that permanently ? Pressing esc does not seems to work for me. the system try to boot from the hba and then detect probably the zfs data partition because I get : "This is a FreeNAS data disk and can not boot system. System halted."

If I press Esc at boot I can get the Boot device menu but I can't the Virtio-scsi Drive as default
Click to expand...
reinstalling truenas with OVMF bios worked for me ;)
 
  • Like
Reactions: Jake_3h
Esc at boot I can get the Boot device menu.
And.... You might want to get into the BIOS of a VM to boot from the ISO if you wanted to install from the OS and not have to recreate the VM... LnxBil :P
 
LnxBil said:
I'd like to know what do you want to do in the "BIOS" of a VM?
Click to expand...
In my case, I needed to disable secure boot to load my custom "unsigned" Linux kernel.

Hitting ESC after a VM reset worked fine, thanks forum members for the info.
I would have guessed eventually after trying all the F2, F8, F10, F12, DEL options repeatedly from my Mac keyboard.
 
Is there a way to increase the time window for pressing ESC?

Between reset, switch to the noVNC console and pressing ESC I'm just too slow. And I don't feel like doing video game exercise just to get the sequence right in so many millisecsonds.
 
pklausner said:
Is there a way to increase the time window for pressing ESC?

Between reset, switch to the noVNC console and pressing ESC I'm just too slow. And I don't feel like doing video game exercise just to get the sequence right in so many millisecsonds.
Click to expand...
I don’t know of a way to increase it but I just used the Proxmox web console rather than VNC (didn’t even know VNC was an option)

Power the VM off, then go to the web console for the VM. It has a start button in the middle so you can click it and immediately hit ESC. You should have plenty of time.

Hope this helps as I know not everyone has access to the web console.
 
fba said:
Edit the config file of the vm and add the line
args: -boot menu=on,splash-time=20000
This will increase the wait time to 20 seconds.
Click to expand...

Thanks to fba for the information. I’d like to add a few details:



The configuration file for each VM is usually located under /etc/pve/qemu-server/. For example, if the VMID is 103, the path would be /etc/pve/qemu-server/103.conf.

You can edit the file with vi:

vi /etc/pve/qemu-server/103.conf

Add the following line inside the file:

args: -boot menu=on,splash-time=20000

This enables the boot menu and sets the boot delay to 20,000 milliseconds (20 seconds), giving you enough time to press <ESC> for entering boot-menu when starting the VM.

After saving the configuration file, you need to shut down and restart the VM for the change to take effect.



Note: For a basic guide on using vi, you can check: https://cets.seas.upenn.edu/answers/vi.html
 
Thanks @trickyearlobe - I now get a glimpse of the start screen. Still to short though. Applied @fba 's configuration, but it seems to make no difference:
Can't see what's wrong with it:
Code: 
# head  200.conf
args: -boot menu=on,splash-time=20000 -vnc 0.0.0.0:15
boot: order=scsi0;ide2;net0
cores: 2
cpu: x86-64-v2-AES
ide2: none,media=cdrom
memory: 3072
meta: creation-qemu=10.0.2,ctime=1760457121
name: enzian
net0: e1000=BC:24:11:D7:85:FA,bridge=vmbr0
numa: 0
(The vnc part _does_ work, removing it doesn't help.)

What I didn't mention: I don't get the BIOS menu, but I _do_ get the BIOS boot menu. So maybe (my version of...) the BIOS simply has different key mappings?
 
You must log in or register to reply here.
Top Bottom