Search results

https://bugzilla.proxmox.com/show_bug.cgi?id=4759#c7

I added separate auth for ceph-crash with ceph auth get-or-create client.crash mon 'profile crash' mgr 'profile crash' and added it to a dedicated keyring /etc/pve/ceph.client.crash.keyring. Then I added the following to ceph.conf to make sure ceph-crash could pick it up. [client.crash]...

I see, that makes sense, thanks for clearing that up.

Hi guys, I'm experimenting with dual stack Ceph and due to missing support for dual stack in the kernel client I'm currently not using KRBD in the storage config. This works fine for VM storage except for EFI/TPM volumes. It seems as if those disks are always using KRBD, ignoring the storage...

When trying to add a USB mapping I got an error about "no such file or directory". Running this command fixed the issue: mkdir /etc/pve/mapping

I checked again and sorry for the confusion. I think some kernel packages did not autoremove since they may have been installed manually and I did not run apt-mark auto on them after. Afaict there are still no more than 4 kernels on the ESP, which fit nicely on a 512MB partition, even if there...

Sure, I mounted it first as shown in my post, just to list the contents here.

Good point, but I've completely purged all grub packages from the system and cleaned ESP, so there are just a few files on them now. root@osl101pve:~# mount /dev/sda2 /boot/efi/ root@osl101pve:~# find /boot/ -ls 2 9 drwxr-xr-x 4 root root 12 Nov 24 21:11 /boot/...

I found this portion in /usr/share/pve-kernel-helper/scripts/functions # Mark as not-for-autoremoval those kernel packages that are: # - the currently booted version, if still installed # - the kernel version we've been called for # - the latest kernel version (as determined by debian...

That's great! (I assumed someone had already thought of this, thanks for the confirmation). :) Do you also plan to add some more generic disk-rename functionality? I noticed pve only cares about the first part of the disk name [vm|base]-100-* so it could be possible to give disks more...

Hi, don't know if this is already possible or if this is the right place to suggest it. While e.g. preparing VM templates is sometimes very helpful to be able to reattach a VM disk to another VM. I would like to be able to select an unused disk and "attach it" to a different VM, giving a VM id...

Same here. Thanks a lot guys!

Yes, all nodes completely up to date as of today. (and corosync and/or node restarted). Cluster has been stable ever since the first patched 1.11 knet update from pvetest, and later upgraded to latest version 1.12. I've also applied the suggested knet timeout tweaks since we only have a single ring.

Got a segfault today. Attached coredump (recompressed with xz for size and gz for accepted filetype in forum). PID: 2200707 (corosync) UID: 0 (root) GID: 0 (root) Signal: 11 (SEGV) Timestamp: Thu 2019-10-03 16:42:21 CEST (18min ago) Command Line...

Yeah, according to the lacp specs, correct ordering is required, so since I'm on lacp+balance-tcp I'm good from that standpoint. The xor hashing both in ovs and the Cisco switch with src-dst-tcp should be 100% deterministic and make each tcp stream stay on a single interface. This is my...

Sorry, I got that mixed up. I meant balance-tcp and was referring to https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#_linux_bond which says that But during my limited testing it looks as if other bonding modes can work fine too. (Perhaps getting a bit OT here.)

If that was referring to me, not really any problems with ovs. I'm running balance-tcp lacp after patch was installed on 16 node cluster. In fact, not even a single log entry for corosync since, and I've tried to stress test it by running iperf sessions in both directions (even simultaneously...

Thanks a lot! I've reverted the kernel/driver flags and installed the new patched version and after initial tests it looks very promising. There are still retransmits while the LACP bonds are renegotiating if I play with the bonding settings and such but that is to be expected. I'm...

Unfortunately, I don't think it made a difference, I still have problems, and had to recover from a cluster meltdown yesterday. I have tried both intremap=off and disable_msi=1, both with no success -- which was expected, since all the posts suggesting those flags are for older kernel versions...

I found I had a flakey LACP bond between two switches. Rebooted the switches and that seems resolved. I've added options bnx2 disable_msi=1 to /etc/modprobe.d/bnx2.conf and rebooted all hosts (checked lspci -v for MSI-X: Enable- afterwards). So far no more corosync segfaults, but I have yet to...