Search results

It's a company that now none of us is considering because of the spam the advertisers are using to promote it. Get lost and take your services with you!

Same problem here. Did you restart the Host AND/OR the VM after update?

In my case i trashed the Asrockrack-Board and went with a Supermicro H13SAE-MF. No further problems so far!

Found a workaround: 1) set local storage (not local-zfs!) so that it can accept qcow2 images. (f.e. edit /etc/pve/storage.cfg and add ",images" to content) 2) migrate and be happy! ;-)

You can work around this by using Debian 13 (Testing/Trixie) and run Proxmox in a Debian 12 LXC. Doing this myself for my workstation. Works like a charm, see my last post how i did this!

I'm currently running my own frankenstein-proxmox-workstation. I had to use Debian 13 because of my new 9070XT. Proxmox is running as a regular LXC container inside on a containerized debian 12. No issues, working great, even clustered with my main pve machine. Step 1: create a debian 12...

thanks for clarification. I'll monitor the forum. I'll be happy to try out prerelease software, as this is a special case as follows: Yes, but in my case, it's something special i am trying. Because it's highly experimental and unsupported, i didn't mention it at all. Short form: I'm using a...

Are there already any plans on supporting Debian 13 / Trixie?

The "vlan102" seems to be unnecessary here, we have a reference to this bridge in the vlan102-definition already (ovs_bridge). In my case it works fine without it.

No CX3: Jun 12 07:04:51 pve kernel: Linux version 6.8.4-2-pve (build@proxmox) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC PMX 6.8.4-2 (2024-04-10T17:36Z) () Jun 12 07:04:51 pve kernel: DMI: To Be Filled By O.E.M. X570D4U-2L2T/X570D4U-2L2T, BIOS...

I installed the CX3 Pro on Juli, 6th. Reboots occured on August, 26. So i don't see a direct relation there.

Interesting. I'm using the same (40G) with the system. No problem with X570, only with B650

After my second board started randomly rebooting after several weeks, i had enough. Also other people mention that even H5 REV 4.01 has the Post-Code-00-Problem... I dont know

You are also using the B650D4U? The board seems to be the problem. Many people switched to the H13SAE-MF from supermicro and the problem with sudden reboots (mine) has been solved. Really disappointed by asrock and the seller seems to not want to take the board back. Having the third exchange...

Same issue here. Any solutions or updates so far?

On my AMD-cpu? seems like a good idea! ;-)

Doesn't fit to my cases. I'm using a mellanox nic in the system. Seems to be a widely known problem: https://forum.proxmox.com/threads/proxmox-mystery-random-reboots.125001/page-2

Damn it. Turns out the reason on my customers epyc system was the RAM and not the kernel. Had to downclock the ram to 1866MHz to get it stable until i have time to change the defective stick :-( Horay for mce eventlog!

I'm having the same problem. It first appeared on my new 7950x homelab-server with an AsrockRack Board. Board was swapped by the distributor, problem persisted. Yesterday i had to move an entire rack at a customer site and updated the proxmox-server at this point. This morning the system had...

Hallo, leider finde ich in den Docs keine Infos darüber, welche Rechte ein User benötigt, um per API auf Cluster/Firewall zugreifen zu können. Auch im Proxmox unter roles/permissions/paths finde ich nichts dergleichen. Kann mir jemand auf die Sprünge helfen? Mfg Stephan