kvm problem after update to omv8

  • Hello i have problem start vm after update to omv 8


    500 - Internal Server Error Unable to poweron - Path '/usr/share/OVMF/OVMF_CODE.fd' is not accessible: No such file or directory


    edit vm .xml to OVMF_CODE_4M.fd cant resolve problem


    Code
    Unable to poweron - internal error: QEMU unexpectedly closed the monitor (vm='haos'): qemu: could not load PC BIOS '/usr/share/OVMF/OVMF_CODE_4M.fd'
    
    OMV\Exception: Unable to poweron - internal error: QEMU unexpectedly closed the monitor (vm='haos'): qemu: could not load PC BIOS '/usr/share/OVMF/OVMF_CODE_4M.fd' in /usr/share/openmediavault/engined/rpc/kvm.inc:2701
    Stack trace:
    #0 [internal function]: OMVRpcServiceKvm->doCommand()
    #1 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array()
    #2 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod()
    #3 /usr/sbin/omv-engined(546): OMV\Rpc\Rpc::call()
    #4 {main}
  • lodgnewt

    Changed the title of the thread from “kvm after update to omv8” to “kvm problem after update to omv8”.
    • Official Post

    Did you read this thread about this exact problem? OMV7 > OMV8 unable to start home assistant KVM

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!