Well, I doubt Proxmox will implement proprietary protocols directly into their platform, but I guess you can run commercial VDI solutions as VMs on Proxmox. I'm not an expert on that, though.
As for the actual topic of this thread: I don't think...
Kleiner Tipp, wenn solche Meldungen aufpoppen, am besten auch mal lesen. Ich bekomme gern mal anfragen warum etwas nicht mehr wie gewohnt funktioniert und wenn man nachfragt hat keiner diese Notes gelesen. ;)
Hi Team,
We are currently evaluating Proxmox VE 9.2.3 for an Airport Edge use case and have a requirement for storage encryption at rest.
We understand that ZFS provides native encryption functionality, which is currently documented as an...
Hello all,
I have a Problem I definetly not understand.
I migrated a Windows 2022 server from VMWare to Proxmox.
Oracle Virtual Box runs fine on it. VMWare Workstation not.
Starting a VM in VM Workstation gives the error
"VMware Workstation and...
I hate to be that guy but installing Proxmox VE on an USB stick is not supported at all. (And never was.)
Only hard drives and/or SSDs are supported.
So it might just be that the installer does not see the USB sticks as that is not a valid...
Super, danke fürs Testen. USB ist also raus, es ist ein reines BTRFS-Thema im Kernel. Mit dem Loop-Device kann das jetzt auch jeder in einer Minute nachstellen. Soll ich den Bug eintragen und den Thread verlinken, oder machst du das selbst? Rein...
Greetings Dominik
This was the Idea first, but that doesn't solve the core issue. If the Datacenter that contains the strict node affinity goes down, the VMs on these nodes also are down and won't start on a node in the remote datacenter...
Die pmxcfs-Meldungen sind eher eine Folge als die Ursache. failed to connect to corosync heißt, dass pmxcfs in dem Moment seine Verbindung zum lokalen corosync verloren hat. Mit dem QDevice hat das erstmal nichts zu tun, corosync auf proxmox1...
I am running a single node on raid1c4 btrfs built on 4 usb flash drives. I had been using v7 because newer versions where braking pci passthrough. But because of cryptohackers I am upgrading (hopefully) to 9.2.
I already gave up running installer...
The iso images are in /var/lib/vz/template/iso/
As for the installed system, it lives in a block device, not in a qemu image file (If you chose local-zfs when installing the vm),
For example, in my system "zfs list" shows...
the proposed kernel (and checksums of the package files) are available here: http://download.proxmox.com/temp/kernel-7.0.14-22_bnxt-test1/
the proposed fix is here...
we uploaded a kernel with the changes for bnxt between 7.0.14-19-pve and 7.0.14-20-pve reverted:
http://download.proxmox.com/temp/kernel-7.0.14-22~test-bnxt-revert1/
It would be great if people experiencing the issues with bnxt_en nics could...
In our lab we were hit with this issue due to running BCM57412 bnxt_en Nics when we updated to the .14-20 kernel. We pinned to .14-19 as a workaround.
Today I updated to the .14.22 kernel and so far no issues seen.
I tested kernel-7.0.14-22_bnxt-test1, in my case, the problem is gone, there are no issues in the logs regarding the bnxt_en driver, and the network is working.
Over 2 hours in to running today's 7.0.14-22~bnxt-test1, so issues at all so far. I've even done a 5 minute iperf3 in both directions over the bnxt_en adapters, and no issues what so ever.
kernel-7.0.14-22_bnxt-test1is running about 18h now without any problems. It seems that this has resolved the issue, since with the problematic kernel 7.0.14-20, the network would always go down after 5 minutes at the latest.
Test result for 7.0.14-22~bnxt-test1 on Intel (HPE DL360 Gen11, BCM57412, NIC firmware 237.1.141.0):
No Fatal firmware reset event, no TX timeouts and no DMAR faults since boot. On -20 the first crash came 20–25 s after driver init, on every...
I can confirm that 7.0.14-22-pve kernel has resolved the issue.
iDRAC is also offering newer firmware for the Broadcom network card on my servers that have cards of that brand, new version is 38.11.70.00.