Proxmox Kernel

  • Anybody who would like to enlighten me as to the use of "installing the proxmox kernel" in the OMV3 WebUI?

    I also dont see any purpose of virtualising OMV except for development purpose. Where is the sense of virtualising the NAS that already offers virtualization?


    For sure there is no performance gain by having two layers of virtualization above each other. And all thos hasszles handing through hdds to the VM. I do remember my odysee with my HP ProLiant Gen8 and P410 raid controler, finding after many hours of research, that HP uses some addressrange required for pass through for theyre intenal server iLO communication...


    Well I do see some gains in getting independend of hardware, yes, but then, having an ISO backup from the OS disc, setting up OMV is almost as fast and easy as moving a VM from one server to an other server, setting up the passthrough and transfering all the data to the new machine.... vs plugin in the old data drives into a new server, plug in a new OS drive and setup OMV, pulling all the settings out of the OS-disc-backup. So I just dont see the benefit of virtualization of the OMV machine.



    But you guys for sure could explain to me the errors of my ways... :-D


    Thanks
    Cheers, Manne

  • I don't use the proxmox kernel. I think they decided to use that when there were issues with zfs. Proxmox uses a newer ubuntu (/) kernel. It is newer than the backport kernel so should should support newer hardware and software if you need that.


    I do have omv3 running on proxmox. It is a nice way to share some of the hard drive space and use some of the plugins. Works well. I also test omv that way.

  • I was the initiator for the proxmox kernel because of missing headers. Here is the post:


    [HOWTO] Instal ZFS-Plugin & use ZFS on OMV


    @ryecoaaron coded the button to make it more easy to install the Proxmox kernel and the headers.


    I like the situation that host and guest use the same kernel!


    Greetings Hoppel

    ---------------------------------------------------------------------------------------------------------------
    frontend software - tvos | android tv | libreelec | win10 | kodi krypton
    frontend hardware - appletv 4k | nvidia shield tv | odroid c2 | yamaha rx-a1020 | quadral chromium style 5.1 | samsung le40-a789r2
    -------------------------------------------
    backend software - debian | openmediavault | latest backport kernel | zfs raid-z2 | docker | emby | unifi | vdr | tvheadend | fhem
    backend hardware - supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x10tb wd red | digital devices max s8
    ---------------------------------------------------------------------------------------------------------------------------------------

    Edited once, last by hoppel118 ().

  • Proxmox uses a newer ubuntu (/) kernel. It is newer than the backport kernel so should should support newer hardware and software if you need that.


    At the moment proxmox uses kernel 4.13 while you get 4.14 from the backports. ;)

    ---------------------------------------------------------------------------------------------------------------
    frontend software - tvos | android tv | libreelec | win10 | kodi krypton
    frontend hardware - appletv 4k | nvidia shield tv | odroid c2 | yamaha rx-a1020 | quadral chromium style 5.1 | samsung le40-a789r2
    -------------------------------------------
    backend software - debian | openmediavault | latest backport kernel | zfs raid-z2 | docker | emby | unifi | vdr | tvheadend | fhem
    backend hardware - supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x10tb wd red | digital devices max s8
    ---------------------------------------------------------------------------------------------------------------------------------------

  • I just ran across this thread. I just moved my OMV4 to my Proxmox server. What benefit comes with moving the current kernel to the proxmox kernel? I am not a developer type, just a user that is trying to get a grip on using virtualization.

  • Need to look into this more. As of this morning proxmox is switching to.


    Code
    zfs-linux (0.7.13-pve1~bpo1) unstable; urgency=medium
    * update ZFS to 0.7.13
    * base zfs-linux on upstream ZOL instead of debian --
    Proxmox Support Team <support@proxmox.com> Fri, 08 Mar 2019 06:53:00 +0100

    Not sure if this might be a problem on OMV? Or if you could move OMV to the zfs-linux instead of debian? Kind of defeats the goal of simplicity.

  • Code
    pve-kernel (4.15.18-35) unstable; urgency=medium
    * update sources to Ubuntu-4.15.0-47.50
    * update ZFS to 0.7.13
    * bump ABI to 4.15.18-12
    -- Proxmox Support Team <support@proxmox.com> Wed, 13 Mar 2019 08:24:42 +0100
  • Not sure if this might be a problem on OMV? Or if you could move OMV to the zfs-linux instead of debian? Kind of defeats the goal of simplicity.

    The only way to move the plugin to zfs-linux instead of debian would be to enable the proxmox repo all the time. That would update some packages that people may not want to do.

    omv 5.5.9 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.6
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • Have you noticed, about how often the Proxmox kernel is updated? Does it at least "loosely" follow Debian kernel updates?

    Every couple of weeks. Basically whenever Ubuntu 18.04 updates the kernel.

    omv 5.5.9 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.6
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • I am using OMV in as a proxmox vm. I just wanted others to notice the change.

    The only way to move the plugin to zfs-linux instead of debian would be to enable the proxmox repo all the time. That would update some packages that people may not want to do.

    Proxmox uses the debian repo. Same as OMV?


    Code
    deb http://ftp.us.debian.org/debian stretch main contrib non-free
    # security updates
    deb http://security.debian.org stretch/updates main contrib non-free


    and

    Code
    #deb https://enterprise.proxmox.com/debian/pve stretch pve-enterprise
    deb http://download.proxmox.com/debian/pve stretch pve-no-subscription

    So unless something is in both it wont get updated from proxmox's repo. It could get messy if they overlap now or in the future. There are ways to manage that.

  • Proxmox means two different things:

    • A virtualization solution based on Debian userland but adding own packages via an own repo: http://download.proxmox.com/de…ubscription/binary-amd64/ (this repo also contains the pve-kernel package which is more or less based on latest Ubuntu Bionic kernel at this time)
    • Their kernel to be used with OMV and as such providing the ability to benefit from Ubuntu's great ZFS support

    If you as an OMV user add the Proxmox repo and install the pve-kernel your only benefit is ZFS support. This is totally unrelated to the fact OMV can run inside Proxmox as virtual machine. Especially there's no real benefit from running the same kernel the hypervisor uses inside a VM (if you want to run the same kernel, then containerization is the way to go, virtualization is the variant where you want to be able to run a different kernel or even a different OS)

  • install the pve-kernel your only benefit is ZFS support

    That isn't the only benefit. You are basically using the Ubuntu 18.04 LTS kernel which is better supported/more stable than a backports kernel especially when the backports kernel is from an unreleased version (such is the case with the backports kernel currently from unreleased Debian 10).

    omv 5.5.9 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.6
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    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!