Recent content by Stoiko Ivanov

This site is not affiliated with Proxmox (see also the notice in the bottom): I would strongly suggest to take the ISO from our CDN (as you did): https://enterprise.proxmox.com/iso/

postscreen complaining speaks to the test with VBscript not adhering to the SMTP protocol - see https://www.postfix.org/POSTSCREEN_README.html -> test with another tool

Please share the logs from when you got the Protocol error - also consider testing with tools like swaks (or actually sending a mail) - we had a few tools that don't follow SMTP standards on the wire and got similar results, and, speaking from personal experience, sometimes I do mistype a SMTP...

Thanks for the update ! Saw that and replied there as well - let's keep the discussion there - https://bugzilla.proxmox.com/show_bug.cgi?id=8172 - as writing the same questions and answers in 2 places does not help Thanks!

could you please share: * all log messages from the journal around the time the bridge was set to promisc on * your network configuration (/etc/network/interfaces) - you can mask individual address if you need to - but try to consistently replace each IP with a separate replacement string There...

Das sollte ein temporäres Problem gewesen sein siehe: https://bugzilla.proxmox.com/show_bug.cgi?id=8158 Bitte Bescheid geben, falls der 404 fehler immer noch passiert - Danke!

Thanks for trying 7.0.14-23 again and confirming it does work!

as this thread has been going for a while and we did have at least 2 issues described here - could you please share the logs that show what's failing (and the affected components and fw versions) Thanks!

managed to reproduce the issue on a VM (instead of playing around with the naming of the block-devices and numbering, I added a second disk to a single-disk rpool (causing the device-name to change from /dev/sda3 to /dev/sda3_/dev/sdb3) - this should be a bit more deterministic/easier to...

This is most likely a different issue - discussed in: https://forum.proxmox.com/threads/proxmox-ve-9-2-21-bcm57412-bnxt_en-network-failure-after-upgrade-to-kernel-7-0-14-20-pve.186749/post-871933 the post links to a test-kernel that should contain a fix for the issue (at least other users...

I've now added the SOLVED prefix as requested. If I'm not mistaken - this is the result of new(er) users having a shorter timeframe, where they can edit their own posts and threads - and this has simply expired for @toumz in this case. I hope this helps!

A test-kernel for another regression (in bnxt_en) just got uploaded to: http://download.proxmox.com/temp/kernel-7.0.14-22_bnxt-test1/ this should contain the current fix mentioned above - if you can - please test booting that kerne (without pcie_aspm=off) - and let us know if it works see...

Thanks for the tests! much appreciated! We had a report about kernel 7.0.14-20-pve and realtek nics in our bugzilla: https://bugzilla.proxmox.com/show_bug.cgi?id=8110 @t.lamprecht reverted a few patches that seem relevant in...

sorry should have written explicit versions here - the version after 7.0.14-21-pve (as this was packaged before the reports) did anything from that boot make it to the journal, that might point to where the error is? else - upgrading pve-firmware and testing with the next kernel seems like a...

This should be fixed in the next version of proxmox-kernel - with: https://git.proxmox.com/?p=pve-kernel.git;a=commitdiff;h=9bf87de266b6edfc42703a9da80692188f6e2d46