Recent content by Oliver Polterauer

Thanks for the update. We will watch this in detail!

thanks If you need somebody to test if patch is available please contact me I can test this anytime on a test cluster! Zeha has also access to this cluster

in the newest version the kernel LPFC with 8Gbit Cards seam to work! Could not find the fix at kernel.org did you patch this yourself?

if you need any more testing, we can also do this directly on the server... can contact me with private message....

these are the errors from log file: 2020-05-12T14:40:44.780036+02:00 hostname kernel: [ 8.701385] lpfc 0000:07:00.0: 0:1303 Link Up Event x1 received Data: x1 xf7 x20 x0 x0 x0 0 2020-05-12T14:40:44.780052+02:00 hostname kernel: [ 11.177527] lpfc 0000:07:00.1: 1:1303 Link Up Event x1...

We did today on one of your test clusters an upgrade from 6.1 (running 5.3.18-3-pve) to 6.2 (5.4.34-1-pve) and after that the port_type for the lpfc drivers is not working anymore. Booting with the old kernel one gets FC Connection back online. Version 5.3.18-3-pve modinfo: description...

actually restart is not needed if you can free up the node and move the resources away (for example on other host, or mounted ISO Files). We have also changed to V3 now, because we where also running into this bug several times.

confirmed same issue. System stop here for several minutes, no hosts where running --> all migrated to a different PM Host!

I am wondering why the +pcid is not added to KVM boot. I have done some testing with updated linux kernels, without this parameter the new patched Debian 9 Kernels are much slower compared to if +pcid is added for starting kvm. -cpu...

basically the documentation is not bad, what on my opinion is missing, you need to create users in proxmox and assign them to the realm. are you using windows AD or real ldap?

is your server using Broadcom network cards? If so this might be your problem: https://forum.proxmox.com/threads/no-reboot-with-4-4-pve-kernel.27908/

We had the same problem. This seams like a kernel bug but we could solve it moving to openvswitch from "legacy bridges". Actually we wanted to switch to openvswitch some time ago, now we gave it a try and reboots work again without a problem. Maybe you might give this a try?

Nice work! Thanks for the answer! Testing it now!

Hi, is there any way to safely add static routes via the Debian interfaces file as proxmox overwrites the interfaces file on startup I have several setups where we have internal / external Interface, external gets default, internal gets all RFC1918 routes set. Of course I could do this via...

we ran into a pretty difficult to find bug with FC (would happen also with iSCSI) runing proxmox 4.3 Actually this is not a proxmox bug, but in kernel Version 3.19+ a bug in the SCSI Stack was fixed which makes using 3PAR Storage impossible. the error in dmesg looks like this: sd 0:0:0:101...