Recent content by TomFreudenberg

Could you explain your question, please. I do not understand what you mean by that.

When using BTRFS you can't create a Container from within the Webgui on the BTRFS storage. #!/usr/bin/env bash # save some values APP=$(basename "$0") # check given action CT_ID=$1 && shift CT_TEMPL=$1 && shift CT_HOSTNAME=$1 && shift CT_CORES=$1 && shift CT_MEMORY=$1 && shift CT_IPV4=$1...

While currently not supported I have patched the perl module for LXC. /usr/share/perl5/PVE/LXC.vm You may apply the patch via patch /usr/share/perl5/PVE/LXC.pm LXC.pm.patch This is the content of LXC.pm.patch: --- /usr/share/perl5/PVE/LXC.pm 2023-06-24 15:08:37.000000000 +0200 +++...

In case that Proxmox is a debian based environment, just try to install a standard debian kernel for your system. You may check then if your system has some trouble to run debian or if Proxmox kernel causes the issue on your side. I am encoutering a similar issue on our side, when running...

We have installed a number of PROXMOX Hosts on our VSPHERE Center. On one System we encountered following problem: 1. VSPHERE on Bare Metal Intel(R) Xeon(R) Gold 6342 CPU (48 Cores) 2. PROXMOX 7.3-3 (Linux 5.15.74-1-pve #1 SMP PVE 5.15.74-1) on Debian 11 3. Open-vmware-tools installed Debian /...

Anothoer option is innodb_flush_method which was changed starting with release 10.5 of MariaDB to O_DIRECT instead fsync. Using innodb_flush_method = fsync or innodb_flush_method = O_DSYNS will also work.

One last statement to that error, it depends also on system ressources. On a LXC with 8G Mem, the buffer needs to be 2G On a LXC with 2G Mem, a 1G buffer is also fine

In case that they changed different tuning values for innodb in the later builds as default, for our use case the default (128M) for `innodb_buffer_pool_size` was too small. We created a overlay conf with innodb_buffer_pool_size = 2G and that solved our issue. So, nothing wrong with PVE or...

Hi, we have encountered a strange situation: Running: 1. PVE 7.4.3 2. Partition /dev/sdb1formatted with BTRFS 3. Partition /dev/sdb1 mounted at /vol/data on host 4. Storage added: `pvesm add btrfs data --path /vol/data ; pvesm set data --format raw` 5. Unpriviledged LXC container created with...

Ich weiß nicht wie weit das fortgeschritten ist bisher. Ich habe jetzt mittlerweile sehr erfolgreich eine Konfiguration um auf einem Hetzner Bare-Metal (Server Börse) mit nur EINER externen IPv4 und IPv6 und nur EINER Netzwerkkarte einen Proxmox Node "hinter" einer OpnSense zu betreiben wobei...

Hi, thanks for any help and comments in advance. I am using InfluxDB and Grafana to visualize server metrics. While using a standardized type of installation, the Proxmox host has different FQDN pve.x1.domain.local and pve.x2.domain.local etc. but the short name is always only "pve". While I...

Thanks for your feedback, so I take this option.

Hi, On our system there are two ifaces vmbr0 and vmbr1 While vmbr0 send traffic to the outside, vmbr1 is the card to bound containers to. When creating a new CT from web interface, the vmbr0 is preselected in network card. If some does not give attention, the selected interface is wrong and...

Taken a hint from that post: https://forum.proxmox.com/threads/no-ping-from-non-root-user-in-debian-buster-lxc.72366/post-387633 ... on my containers I just reinstall all packages containing setcap command and be already installed by the image. cd /var/lib/dpkg/info/ && apt install...

Hi on my containers I just reinstall all packages containing setcap command and be already installed by the image. That works in any way - hope useful for others too. Here is a command which look at all installed packages and reinstall those ... cd /var/lib/dpkg/info/ && apt install...