Search results

The root cause is a faulty /etc/default/grub entry.

Hello, my initial Proxmox installation was 6.4 and I have enable PCI passthrough successfully. This is my current /etc/default/grub: # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f...

I Have switched to LXC running Ubuntu 20.04 and managed to setup a 4-node k3s cluster. However you need to modify the LXC following this instruction.

Hello, I have configured a container (LXC) and deployed k3s. However starting the relevant service fails. Checking the output of journal -xe there are different errors: Mai 01 20:45:48 k3s-master1 k3s[1910]: time="2021-05-01T20:45:48.689640997+02:00" level=info msg="Wrote kubeconfig...

Hi, I'm in the same setup / installation of k3s. Actually I can confirm the issue with kernel module br_netfilter, but module overlay is working: $ modinfo overlay filename: /lib/modules/5.4.106-1-pve/kernel/fs/overlayfs/overlay.ko alias: fs-overlay license: GPL...

Hello, I have a (working) OVS config with 1 bridge + 3 VLANs: source /etc/network/interfaces.d/* auto lo iface lo inet loopback auto enp1s0f1 iface enp1s0f1 inet manual auto eno1 iface eno1 inet manual ovs_type OVSPort ovs_bridge vmbr0 auto enp1s0f0 iface enp1s0f0 inet...

Thanks for your reply. However I'm not sure if there's an inconsistency. You say that you "[...] had to disable the VLAN-aware bridge and all traffic started working properly", but according to the config vmbr0 is vlan-aware. Or is this your management network connection? Why did you migrate...

Das verstehe ich nicht ganz. Wenn ich eine VM mit der Bridge vmbr0 verbinde, dann ist das Netzwerk dieser VM dasselbe, also 192.168.0.0/24. Die weitere Bridge für eine dediziertes VLAN 100 wäre dann: auto vmbr100 iface vmbr100 inet static address 192.168.100.21/24 gateway...

Hi, was ist denn nun die Empfehlung für multiple VLANs auf einer Bridge? In der Doku zu OVS steht: "[...] supports multiple vlans on a single bridge." Nach meinem Verständnis würde diese Konfig ohne OVS aber auch funktionieren: auto eno1 iface eno1 inet manual auto eno2 iface eno2 inet manual...

Indeed old container was privileged.

Hello, I had faced a disaster affecting the root partition of Proxmox VE. Of course I have no backup, shame on me. However, I have stored and KVM virtual disk (qcow2) and any LXC virtual disk (raw) on a seperate drive (SSD) that is not affected by the disaster. So, I managed to install Proxmox...

Initially I booted Arch Linux. I used Arch Linux (in live mode) in the past successfully to repair systems that failed with a boot issue. However, this obviously failed with Debian 9. As a matter of fact, it will also fail if you boot Debian 10 Live CD. This means there was a change /...

What exactly do you mean? More details about chroot into an existing OS? Then you can read this. Or do you need details for fixing Grub? Then you can read this. I strongly encourage you to search the internet for common scenarios in linux.

Booting Debian 9 Live CD works with chroot. Repairing grub fixed the boot issue.

Hi, after power outage I face this issue: Proxmox VE server fails to boot. I started Live-CD, mounted LVM-root and boot partition and chroot in the system. However there are many commands not available, e.g. ls mount pvs ... I can install packages like coreutils, lvm2, ... but this does not...

I see. But if several people involved and responsible for ceph-mgr tell me that the issue related to balancer will be fixed with 14.2.7, then I would trust these statements until someone proves that I'm wrong.

I have some doubts that this release only include the fixes mentioned above: CVE-2020-1699 CVE-2020-1700 However, I don't understand how I can test this new release(s) if you don't provide it in your test repo. Isn't this test repo for testing new releases?

I understand, but my point is that Ceph releases new packages fixing a couple of security issues and I have to wait some days until this has passed your internal testing leaving my system vulnerable with these issues.

Does this mean there's no roadmap available? It could make sense to release new packages in your test repo close to the official release, in particular if there are security fixes.

Hi, you should check the wiki for Proxmox VE storage model. LVM-thin is not shared (across the nodes). Regards Thomas