Proxmox Kernel

Proxmox has backports same as ubuntu kernel, but also add some of their own addons(i think most about 10g networks and similar).

Are there any known disadvantages to running the Proxmox kernel?
Specifically on OMV v5 ?
I assume all the normal OMV update methods/procedures will continue to work?
And does that include release updates too - i.e. going to OMV v6 whenever that might be?

Thanks, Antony

[Sorry to bump an old thread]

Awesome, thanks for the quick reply.
All I'm wanting really, is support for 10gbe card with as little other changes as possible.

Thanks, Antony

Hi,

I'm on OMV5 (Debian 10) and still using the standard kernel for now. I have ZFS up and running and I'm not having issues for the moment.

Maybe I just don't know what I am missing out.

Anyway, I now want to have KVM available on this box too, would I need this Proxmox kernel?

Or, should I just follow the Debian 10 instructions for getting KVM up and running?

Any clarification on the benefit of the Proxmox kernel in regards with KVM would be much appreciated.

Thanks,

Andrea

I have been looking for a way of installing the backports/proxmox kernel in OMV5... and I can't find it anywhere.

I am using OMV5 on a Raspberry pi4, and currently running kernel 4.19.97-v7l+

OMV Extras is installed, and I have Backports, Testing Repo and Extras Repo all enabled... just in case!

All I really would like to do is enable ZFS, but it is not installing the kernel module for it, I figured it is because the kernel headers are not installed.

If you need any other details, or if you want me to open this as a separate discussion, let me know.

Zitat von ryecoaaron

proxmox kernel is amd64 systems only.

ah... that will be why then thanks for pointing that out.

Zitat von ryecoaaron

zfs on an RPi? While you can do it, why?

mostly 'because you can' and also for snapshotting, and de-duplication... (see my other post about opendedupe)

I did consider looking at LVM... as I wanted to play with creating a caching drive too (once I find that elusive SSD that I know I have laying around here!).

I know BTRFS well... that does have de-duping... this is more for educational purposes... but if you are saying it is bad juju... I may opt with BTRFS... I think that is built-in with OMV5 isn't it?

Zitat von ryecoaaron

Every form I know of uses a substantial amount of ram increasing with the amount of storage you have and even 4GB is not enough

Just for other peoples reference... found this nice article explaining the ZFS recommendations for memory:
https://superuser.com/question…ysical-deduped-compressed

there is a way of tweaking record sizes... and I was considering, because there are many large files that may be similar, of increasing the record sizes considerably to take this into account for memory requirements.

Zitat von ryecoaaron

OMV 4 and 5 have the same btrfs support

looking at it, that is the better option, that coupled with a scheduled de-dupe overnight or something.

Again, for anyone interested:

https://btrfs.wiki.kernel.org/index.php/Deduplication

is there any particular de-duping that you recommend that you have used in the past?

ok, cool, well, I appreciate your help and advice... and I will probably go down the BTRFS route, with something like DupeRemove (http://markfasheh.github.io/duperemove/) running overnight. I will only have a 1TB drive, so if it squeezes some extra room, that will be great.

Again, thank you, and thanks for all the work you all put in to OMV

Hello everyone,

I have Proxmox 4.4 as a host and virtualized I have tested various versions of OMV since version 5.3.9, 4.1.3, 4.1.22 and 4.0.9

I configure the OMVs regardless of versions 5.3.9, 4.1.3, 4.1.22 and 4.0.9, with a vitio virtual disk for the operating system and another virtio for storage.

I direct the backup copies of the Proxmox 4.4 to this virtual OMV machines, but whenever the backup of one or more virtual machines starts, the OMV shuts down by itself without any explanation and clearly the backup is not performed and ends up blocking the Proxmox 4.4 that has the virtual machines that were doing the backups.

PROMOX 4.4. from the OMV and the other virtual machines:

• proxmox-ve: 4.4-76 (running kernel: 4.4.35-1-pve)

• pve-manager: 4.4-1 (running version: 4.4-1/eb2d6f1e)

• pve-kernel-4.4.35-1-pve: 4.4.35-76

Proxmox physical server 4.4. by OMV:

• Xeon 4 cores

• RAM 9GB

• 2 SATA 4TB hard drives

OMV virtual machine on Proxmox 4.4

• Xeon 3 cores

• 7.5GB RAM memory

• 1 Virtio 30GB hard drive, operating system.

• 1 Virtio 3500GB hard drive, storage.

I hope someone can support me in the failure.

Thanks.

And the upgrade to 5 and the to 6 is not viable?

Zitat von ness1602

And the upgrade to 5 and the to 6 is not viable?

It is a server of about 8 years or more, for old servers I always use Proxmox 4.4.

-The question is if I upload it, do you think it will work?

-Or have you tried Proxmox 5 or 6 on old servers?

Upgrade should work,i have really old servers with proxmox 6(some intel,as in server brand intel server), and they work normally.

Zitat von andrea

Hi,

[...]

Anyway, I now want to have KVM available on this box too, would I need this Proxmox kernel?

Or, should I just follow the Debian 10 instructions for getting KVM up and running?

[...]

Any clarification on the benefit of the Proxmox kernel in regards with KVM would be much appreciated.

Thanks,

Andrea

Alles anzeigen

Hi Andrea - did you ever get your answer? Also: Have you been successful in setting up KVM on OMV?