VM Firmware in FreeCORE 15.1

Use UEFI for virtual machines and prepare older GRUB or UEFI-CSM guests before moving to 15.1.

FreeCORE 15.1 supports UEFI virtual machines. The VM creation and edit screens offer UEFI as the only bootloader. Existing definitions that use GRUB or UEFI-CSM remain visible, but cannot run or be edited on 15.1. The upgrade does not convert their firmware setting or guest disks.

Check Existing VMs Before Moving to 15.1

While still running FreeCORE 15.0, go to Virtual Machines and review each VM's Bootloader. Back up the guest and record its disk and device settings before changing its boot method.

Converting a guest to UEFI can require changes inside its operating system, including its partition layout and bootloader. Follow that guest operating system's procedure and verify it boots under ordinary UEFI on 15.0 before moving the storage system to 15.1. Selecting a different firmware label alone does not make legacy boot media UEFI-compatible.

If a guest cannot be migrated yet, keep the system on the 15.0 line until there is a suitable plan for it. The basic VM creation guide describes the remaining CPU, memory, disk, and network setup.

Read an Unsupported VM Record

On 15.1, the VM list labels a retained record UNSUPPORTED (GRUB) or UNSUPPORTED (UEFI-CSM). Its bootloader also carries an unsupported label. The record is kept so its identity and configuration are not silently lost.

Only Delete remains available in the record's action menu. Start and autostart changes are blocked, and opening an edit route does not enable saving. The API also rejects starting or modifying a retired-bootloader record; it cannot be converted by submitting a different bootloader through the API on 15.1.

To migrate it, use FreeCORE 15.0 to check the guest boot media and make the UEFI conversion there. Returning to an earlier boot environment is a separate system operation: review Update Security and your data and pool-feature compatibility before doing so.

Remove a Definition While Retaining Its Disks

If the definition is no longer needed, choose Delete and leave Delete Virtual Machine Data? unset to retain its zvols. Selecting that option deletes the attached zvol storage, not just the VM definition. Review the choice before confirming.

Deleting a definition also removes its device assignments. Record those settings first if the disks will be attached to a replacement VM. A retained disk still needs a compatible guest boot configuration; retaining it does not convert its contents.

Create a New VM on 15.1

Choose ADD under Virtual Machines, select UEFI, and use an installer that supports UEFI boot. Complete the CPU, memory, storage, network, and installation-media steps for the guest. VNC is available when the VM has a VNC display device and is running.

Use the normal VM list controls to start, stop, or restart a supported VM. The guest operating system must respond to a graceful stop request; a forced power-off is a separate action and can interrupt guest writes.