Search results

also have a look at https://forum.proxmox.com/threads/proxmox-server-via-wifi-list-of-wifi-bridge-adapters-which-work-with-proxmox.161124/ , which provides an alternative/easier way to hook up proxmox to wifi

hello. is anybody using proxmox behind a wifi repeater in "wifi client mode" and likes to share his experience here ? many repeaters provide that "wifi client mode" features and my experience with this is more and more promising, the more adapters i'm testing (currently i ordered some...

so, if there apparently is an issue with ksm here - where is the corresponding bugticket at https://bugzilla.proxmox.com ?

you won't need to configure anything - just include the proxmox host via checkmk so that it's being accessed by the api and then it simply works. in our environment, configured vm names match their dns host names. maybe this is why it just works for me. have a look how to otherwise match VM...

https://github.com/openzfs/zfs/issues/13925

hello, does anybody monitor proxmox with checkmk and has an idea how to avoid memory warnings? i'm constantly getting "memroy warn/critical" and it's flapping all the time, because checkmk does not take arc usage into consideration. even proxmox itself, still does not handle that properly...

it's typically not a problem that zfs proxmox hosts show high memory load. it's not zfs arc's fault, the problem is that arc is a special case for reclaimable memory and many monitoring tools or even proxmox itself does not take into consideration that arc cache is special regarding memory...

yes, exactly that

it depends what's your definition of "compute cluster". you can cluster pve hosts without a problem without shared storage. live migration of VMs between hosts in that cluster is also possible without shared storage, though it puts much more effort to migrate vm's, as virtual disks need to...

shared storage is overrated very often - and often introduces more problems then it's solving ;)

https://pve.proxmox.com/wiki/Performance_Tweaks#Disk_Cache

FYI https://bugzilla.proxmox.com/show_bug.cgi?id=6268

you can detach the disk from the vm and attach to another one, but you can't use that at the same time with 2 vms

does proxmox team add tests like these to their regression testing , which would help avoiding such issues proactively in the future?

maybe this is related ? https://bugzilla.proxmox.com/show_bug.cgi?id=3873

>is that the device can disappear, and ZFS doesn't really handle this well. it's worst for single-device pools, where you often need a reboot to get out of the mess - yes , zfs cannot handle this for now. it's difficult to resolve, see https://github.com/openzfs/zfs/issues/5242

danke für die ausführung. die argumentation kann ich nachvollziehen. wenn geschachtelte containerization bei dir aber bislang ohne probleme gelaufen ist über mehrere proxmox releases wäre es angesichts der popularität ja dann vielleicht doch mal an der zeit , daß es von proxmox da ein paar...

there is a patch in the making which adresses gc speed and may drastically speed things up. < give it a try and report your results when it has been megered and made available via update: https://bugzilla.proxmox.com/show_bug.cgi?id=5331

do you have snapshots in that dataset ? you should try cd into the last snapshot and have a look what's listed there