Search results

This still happens on the Debian 12 container template. I agree with the OP and found Tom's one-liner above to work to 'fix the problem'. Thanks!

Good idea.. thanks. https://bugzilla.proxmox.com/show_bug.cgi?id=4858

Hello: I have been tripped up trying to get postfix to use a relay server which requires login with username/password. I know how to make postfix do this, but the part I miss is that Proxmox VE does not have libsasl2-modules installed by default. You DO have libsasl2-2 and libsasl2-modules-db...

Yes, thanks that works. Strange that it was different as supplied by the beta iso installer. I read the page at https://pve.proxmox.com/wiki/Package_Repositories#sysadmin_package_repositories_ceph but I guess I didn't spot the difference at the start of the line. Thanks for pointing that out to me.

Hello: I have a license at the lowest cost Proxmox VE subscription level. I installed fresh Proxmox 8 in the last few days of the beta, then updated to release. I removed my license from my old box and added it to the new one -- no problem. I can get packages from the enterprise repo. But not...

I installed fresh on a new Intel Nuc Pro 13th Gen, not fully tested yet, but seems happy so far. Great work Proxmox team!

I just worked on this for way too long... The CT that I backed up and moved to another Proxmox host needed to be under: /var/lib/vz/template/cache before it was seen. Possibly it also needs to be in .zst compression format, not sure as I also tried that for my final (and only successful)...

Argh! Checking the cable was a good idea! It was not the cable I thought it was, and then I could see no activity, though there was a link to the switch. But the line through the wall to another switch was not making full contact anymore so that was the problem. I do maintain that at some point...

Thanks Jonathan... the other two bridges are working fine without that setting. I tried it just in case, but it made no difference. Maybe I'll change the cable! lol (there are activity lights on the back of the motherboard for the nic).

The only thing I noticed is that there was no MTU listed for vmbr1 / enp45s0 so I updated that. I also then did ifdown ifup in the terminal and tried changing something in the GUI and changing it back, applying... Still not working. Anything look wrong to you? auto lo iface lo inet loopback...

# ip link 2: enp42s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP mode DEFAULT group default qlen 1000 link/ether 70:85:c2:82:52:ad brd ff:ff:ff:ff:ff:ff 3: enp47s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq master vmbr2 state UP mode DEFAULT group...

Hello again.. I'm now on 5.15.39-1-pve #1 SMP PVE 5.15.39-1 (Wed, 22 Jun 2022 17:22:00 +0200) x86_64 GNU/Linux kernel and still can't ping any IPs on the same subnet (or any) through this NIC. Should it work? Can I help with getting it fixed by posting any logs? I'm about ready to throw some...

I'm now running the testing kernel 5.15.35.3 (I think!): # uname -a Linux pvea 5.15.35-1-pve #1 SMP PVE 5.15.35-3 (Wed, 11 May 2022 07:57:51 +0200) x86_64 GNU/Linux and the NIC is not magically working again. However, syslog is no longer showing array-index-out-of-bounds anymore! So, progress...

Thanks for the step-by-step! So far, no change for me. Anyone kind enough to continue helping, perhaps we should take it to the thread I started about this NIC and Proxmox 7.2 over here: https://forum.proxmox.com/threads/7-2-update-aquantia-nic-not-working-anymore.109191/ I'll check the error...

Hello Tom. Thanks, I could try this shortly. Can you give me the brief instructions of how to download and install it, and then once that kernel is released as stable, how to ensure I'm back tracking stable kernel updates?

I just updated to 5.15.35-1-pve and the Aquantia nic did not start working.

Hmm. Some developments: Perhaps for the first time ever this machine had locked up on me. Power off then reboot, I booted into the older 5.13 kernel that was offered in the boot menu, and still the aquantia NIC isn't working. I guess I'm confused if the driver is in the kernel or if now I'm...

No, but I confirm it exists in 5.15.30-2-pve!

ah, I see this has been mentioned by others, and has been patched: kernel.org Would love to see this merged into Proxmox kernel asap! Here's where to see the error: # cat syslog.1 | grep aquantia May 5 09:24:47 pvea kernel: [ 13.325232] UBSAN: array-index-out-of-bounds in...

Hello: I did this update a couple days ago, which I guess is Proxmox 7.1 to 7.2: Start-Date: 2022-05-05 09:20:50 Commandline: apt dist-upgrade Install: pve-kernel-5.15.30-2-pve:amd64 (5.15.30-3, automatic), pve-kernel-5.15:amd64 (7.2-1, automatic), libvirglrenderer1:amd64 (0.8.2-5, automatic)...