❌

Normale weergave

Proxmox Virtual Environment launches official Arm64 Support

5 Augustus 2026 om 09:17
  • First official Arm64 release extends Proxmox VE beyond x86-64 architectures.
  • Features day-one validation for NVIDIA Graceβ„’ and NVIDIA Veraβ„’ CPU architectures.
  • Delivers complete feature parity across KVM, LXC, ZFS, and Ceph storage stacks.

VIENNA, Austria – August 05, 2026 –Enterprise software developer Proxmox Server Solutions GmbHΒ today announced the immediate availability of the first officially supported Arm64 edition of its flagship platform, Proxmox Virtual Environment. The release extends the open-source virtualization platform to Arm-based server systems, supporting enterprise demand for high-density, energy-efficient data center architectures.

Proxmox VE for Arm64 provides a unified platform to manage Arm64 virtual machines and Linux containers (LXC). Users benefit from the established web-based management interface, software-defined networking, storage, high-availability clustering, and backup capabilities of Proxmox VE on supported Arm64 hardware.

Systems based on the NVIDIA Grace and NVIDIA Vera CPU architectures are supported from the first official Arm64 release. These platforms target demanding data center, cloud, accelerated computing, and AI training and inference environments, expanding the infrastructure options available to organizations building modern and energy-efficient data centers.

Technical validation on NVIDIA Grace Hopperβ„’ systems

Developed in technical collaboration with NVIDIA and Supermicro, Proxmox engineers performed joint validation on NVIDIA Grace Hopperβ„’ Superchip server systems. This effort enabled rapid porting and thorough testing across the platform stack, which is already operating across select enterprise production environments.

Full feature parity for ZFS and Ceph

Built on Proxmox VE’s established Linux and KVM foundation, the Arm64 edition underwent architecture-wide validation. Key enterprise storage mainstays – including ZFS and Ceph – have been fully optimized to deliver exact performance, reliability, and feature parity with existing x86 deployments.

β€œAs data centers shift toward high-density, energy-efficient architectures, our customers require the exact same mission-critical stability on Arm64 that they have relied on with x86," said Tim Marx, COO at Proxmox Server Solutions. "Through our close engineering work with NVIDIA and Supermicro, we are ensuring that enterprises can scale their next-generation AI and cloud workloads with complete confidence in their underlying hypervisor."

β€œOur goal was not simply to run Proxmox VE on a new architecture, but to deliver full feature parity: KVM, networking, clustering, ZFS, and Ceph all behaving exactly as our users expect from our x86-64 builds,” said Thomas Lamprecht, CTO at Proxmox Server Solutions. β€œDeveloping directly on NVIDIA Grace Hopper systems let us validate that on production-class hardware from day one, and NVIDIA's upstream kernel work ensures the platform evolves alongside NVIDIA Grace and NVIDIA Vera.”

Availability

Proxmox Virtual Environment for Arm64 is open-source software and immediately available for download via bare-metal ISO images or package repositories alongside existing x86-64 builds.

For enterprise environments, Proxmox Server Solutions offers comprehensive support plans that provide stable and secure updates and direct access to expert support services. These support contracts offer a cost-effective way to secure enterprise-grade stability. Enterprise support for Arm64 deployments are available upon request.

Resources:

###

About Proxmox Virtual Environment
Powering over 2 million hosts globally, Proxmox Virtual Environment is a complete open-source platform for enterprise virtualization and hyper-converged infrastructure. It natively unifies KVM virtualization, LXC containers, software-defined storage, and networking on a single platform. Alongside its dedicated Backup Server and Datacenter Manager, the Proxmox ecosystem eliminates multi-site complexity as well as dependency on proprietary stacks. Backed by a global community of over 225,000 members, the platform serves as a scalable, cost-effective foundation for modern data centers.

About Proxmox Server Solutions
Proxmox Server Solutions provides powerful, intuitive open-source server software that guarantees vendor independence and minimizes total cost of ownership. Enterprises of all sizes rely on the company’s reliable vendor support, certified training services, and a global network of 3,000 integration partners to ensure business continuity. Established in 2005 and headquartered in Vienna, Austria, tens of thousands of corporate customers worldwide trust Proxmox solutions to secure their mission-critical IT environments.

Contact:Β Daniela HΓ€sler, Proxmox Server Solutions GmbH, press@proxmox.com

  •  

v1.20.0

5 Augustus 2026 om 12:37

New major features

General

  • support forwarding streams natively (#5558) It is now possible to define forward destinations for each path configuration. For each destination, the server will create a client that will forward the stream to the intended destination. Supported protocols are RTSP, RTMP, SRT. API and metrics have also been improved to allow monitoring the new forwarding system. Documentation: https://mediamtx.org/docs/features/forward

Media-Over-QUIC

  • support publishing and reading through native QUIC (#6039)
  • support draft-17 (#6040)
  • support draft-16 (#6045)

Fixes and improvements

General

  • docs: add missing MoQ ports (#5983)
  • Add OpenAPI definition of the Playback server (#5546)
  • fix support for regexp groups greater than 10 (#6033)

Media-Over-QUIC

  • increase max namespace field count to 32 (#6043)
  • link primitives to draft-17 sections (#6044)

RTSP

  • fix inability to read some AV1 streams with RTSP (#6001) (#6006) Since v1.16.0, temporal unit delimiters were not stripped from AV1 streams anymore. This has been restored, healing AV1 streams read with RTSP.
  • log write errors (#6023)
  • make multicast errors on single interfaces non-fatal (bluenviron/gortsplib#1115) (#5574) When writing multicast packets to several interfaces at one, a write error to a single interface was fatal and prevented writing to the other ones. Fix this.

RTMP

  • server: fix parsing URL from multitrack OBS (#6007) (bluenviron/gortmplib#93)
  • client: change mapping between URL and tcURL, app, streamKey (bluenviron/gortmplib#94) (#4676) URLs passed to clients are now mapped into RTMP-native fields (tcURL, app, streamKey) in this way: tcURL contains URL without credentials and without fragment, app contains path and query of tcURL, streamKey contains the fragment.
  • client: fix compatibility with YouTube (#5558) (bluenviron/gortmplib#95)

HLS

WebRTC

  • sort tracks in a deterministic way (#5988) (#5989) When ingesting tracks with WebRTC, track order was randomized, preventing multi-track always-available streams from working reliably, since they require tracks to be ordered in a precise way. WebRTC tracks are not ordered by MID, RID, trackID and streamID respectively.
  • fix packet corruption when reading G722 (#6000)
  • reset recomputed audio PTS if it drifts too much (#6021)
  • fix "packet lost" error when routing streams from WebRTC (#6034) Chrome sometimes sends empty packets, that are discarded by the server, but the sequence number of following packets is not recomputed, leading downstream packet loss detectors to emit errors. This is fixed.

SRT

  • improve log clarity (#5990) use message 'passphrase not provided by client' when clients do not provide passphrases.
  • show stream ID in logs (#6018)
  • close sources immediately when path is closed (#6038)

Dependencies

  • code.cloudfoundry.org/bytefmt updated from v0.82.0 to v0.83.0
  • github.com/MicahParks/jwkset updated from v0.11.0 to v0.11.3
  • github.com/MicahParks/keyfunc/v3 updated from v3.8.0 to v3.8.1
  • github.com/bluenviron/gohlslib/v2 updated from v2.4.1 to v2.4.2
  • github.com/bluenviron/gortmplib updated from v0.4.1 to v1.0.0
  • github.com/bluenviron/gortsplib/v5 updated from v5.6.2 to v5.6.3
  • github.com/go-git/go-billy/v5 updated from v5.9.0 to v5.9.1
  • github.com/go-git/go-git/v5 updated from v5.19.1 to v5.19.2
  • github.com/pion/ice/v4 updated from v4.3.0 to v4.4.0
  • github.com/pion/interceptor updated from v0.1.46 to v0.1.47
  • github.com/pion/webrtc/v4 updated from v4.2.17 to v4.2.18
  • github.com/quic-go/quic-go updated from v0.60.0 to v0.61.0
  • github.com/quic-go/webtransport-go updated from v0.11.1 to v0.12.0
  • github.com/pion/sctp updated from v1.11.0 to v1.11.1
  • golang.org/x/time updated from v0.14.0 to v0.15.0

Security

Binaries are compiled from source code by the Release workflow, which is a fully-visible process that prevents any change or external interference in produced artifacts.

Checksums of binaries are also published in a public blockchain by using GitHub Attestations, and they can be verified by running:

ls mediamtx_* | xargs -L1 gh attestation verify --repo bluenviron/mediamtx

You can verify checksums of binaries by downloading checksums.sha256 and running:

cat checksums.sha256 | grep "$(ls mediamtx_*)" | sha256sum --check

  •  
❌