Posts by mbgroen

  • KVM Plugin cannot load UEFI firmware (OVMF_CODE_4M.fd)

    I've removed the symbolic links from OVMF_CODE_4M.fd and OVMF_CODE.fd to /usr/share/ovmf/OVMF.fd and renamed OVMF_CODE_4M.fd.org back to OVMF_CODE_4M.fd and installed your version of openmediavault-kvm (8.0.2) and tested a couple of settings.


    Just UEFI:


    <os firmware='efi'>

    <type arch='x86_64' machine='pc-q35-10.0'>hvm</type>

    <firmware>

    <feature enabled='no' name='enrolled-keys'/>

    <feature enabled='no' name='secure-boot'/>

    </firmware>

    <loader readonly='yes' type='pflash' format='raw'>/usr/share/OVMF/OVMF_CODE_4M.fd</loader>

    <nvram template='/usr/share/OVMF/OVMF_VARS_4M.fd' templateFormat='raw' format='raw'>/var/lib/libvirt/qemu/nvram/UEFI-Test_VARS.fd</nvram>


    Tested and works!


    UEFI and Secure Boot:

    <os firmware='efi'>

    <type arch='x86_64' machine='pc-q35-10.0'>hvm</type>

    <firmware>

    <feature enabled='yes' name='enrolled-keys'/>

    <feature enabled='yes' name='secure-boot'/>

    </firmware>

    <loader readonly='yes' secure='yes' type='pflash' format='raw'>/usr/share/OVMF/OVMF_CODE_4M.ms.fd</loader>

    <nvram template='/usr/share/OVMF/OVMF_VARS_4M.ms.fd' templateFormat='raw' format='raw'>/var/lib/libvirt/qemu/nvram/UEFI_SecureBoot_Test_VARS.fd</nvram>


    Tested and works!


    I've also tested a VM with UEFI, Secure Boot and a vTPM, although the vTPM option is probably unrelated, this also works fine :)

    Many thanks!

  • KVM Plugin cannot load UEFI firmware (OVMF_CODE_4M.fd)

    After using omv-release-upgrade to upgrade from OMV 7.7.24 to OMV 8 my existing VM's that use UEFI didn't start anymore. I got an error saying that /usr/share/OVMF/OVMF_CODE.fd didn't exist.

    When creating a new UEFI VM in the KVM plugin of OMV-Extras 8.x, I got a slightly different error related to an issue loading /usr/share/OVMF/OVMF_CODE_4M.fd. This new firmware apparently can't be loaded with the "rom=" option, but should be loaded with "loader readonly='yes' type='pflash'" To temporary resolve both issues I renamed /usr/share/OVMF/OVMF_CODE_4M.fd to /usr/share/OVMF/OVMF_CODE_4M.fd.org and created 2 symbolic links /usr/share/OVMF/OVMF_CODE.fd and /usr/share/OVMF/OVMF_CODE_4M.fd both pointing to /usr/share/ovmf/OVMF.fd (note the lowercase ovfm directory name, that directory also still exists and has an older UEFI firmware file that can be loaded with the "rom=" option. Anyone else experiencing the same issue?

  • No login to GUI possible

    Same here. After updating the K8S plugin, I couldn't login to the WebUI anymore (Same error as OP). After removing the K8S plugin via CLI the WebUI is working again. Tried reinstalling the K8S plugin, but then the issues comes back.

  • K8S plugin settings "Copy Token" button does not work

    Hi Volker, thanks for your response. I was using Safari 17.3.1 on macOS Sonoma 14.3.1 . When I use Chromium it indeed does function normally and the token gets copied.

  • Netatalk

    Quote from mbgroen

    I'm a Mac user too and really would like to stay using the AFP plugin.
    It allows me to set a nice icon (using the advanced settings) in the finder and only shows just one icon in the finder instead of a blue screen computer icon next to all the separate shares (see screenshots). Somehow Apple managed to change this behavior if you share via SMB on a Mac (SMB shares look the same as when using AFP and no extra computer icon), does somebody know how to mimic this behavior? That would only leave the nice icons to be desired.



    I've got the icon part sorted by adding an extra service section to /usr/share/openmediavault/mkconf/avahiservices.d/smb (to make it stick after config updates):


    <service>
    <type>_device-info._tcp</type>
    <port>0</port>
    <txt-record>model=Xserve</txt-record>
    </service>


    And then modifying the SMB/CIFS service discovery item in the OMV 4 webUI under Network -> Service Discovery to reflect the same name as the AFP name (Home Server in my case).


    I disabled "Browsable" under the SMB/CIFS Home Directory settings and added the following to the Advanced Settings text field part (in bold):

    min receivefile size = 16384
    write cache size = 524288
    getwd cache = yes
    socket options = TCP_NODELAY IPTOS_LOWDELAY
    min protocol = SMB2
    vfs objects = catia fruit streams_xattr
    fruit:metadata = stream
    fruit:posix_rename = yes
    fruit:veto_appledouble = no
    fruit:wipe_intentionally_left_blank_rfork = yes
    fruit:delete_empty_adfiles = yes
    disable netbios = yes


    I also stopped and disabled nmbd just to be sure, since I'm not sure if disable netbios = yes is accepted:
    sudo systemctl stop nmbd.service
    sudo systemctl disable nmbd.service


    Works like I wanted now... I left AFP enabled for my Time Machine share, but that won't be necessary anymore after upgrading to OMV 5 as I understood.

  • Netatalk

    Those Mac mini's are actually real Mac mini's btw ;) OMV server is a HP Microserver Gen8, love this cheap little server with 4 drive bay's (pus an extra SSD as boot drive), iLO, 16GB memory and Xeon support.... Combined with OMV it's the perfect NAS server!

  • Netatalk

    I'm a Mac user too and really would like to stay using the AFP plugin.
    It allows me to set a nice icon (using the advanced settings) in the finder and only shows just one icon in the finder instead of a blue screen computer icon next to all the separate shares (see screenshots). Somehow Apple managed to change this behavior if you share via SMB on a Mac (SMB shares look the same as when using AFP and no extra computer icon), does somebody know how to mimic this behavior? That would only leave the nice icons to be desired.


  • Will upgrade from OMV 4 to OMV 5 require reinstallation?

    I really hope the Docker plugin will be ported to OMV 5 too, this makes setting up containers a lot more user friendly and gives a more "integrated" NAS feeling than opening a separate tool like Portainer in a new window. People who need the extra options Portainer offers can always install a Portainer container.