# Table of Contents - [Developer Documentation - Proxmox VE](#developer-documentation-proxmox-ve) - [Perl Style Guide - Proxmox VE](#perl-style-guide-proxmox-ve) - [Javascript Style Guide - Proxmox VE](#javascript-style-guide-proxmox-ve) - [Technical Writing Style Guide - Proxmox VE](#technical-writing-style-guide-proxmox-ve) - [Get support - Proxmox VE](#get-support-proxmox-ve) - [Pages that link to "Developer Documentation" - Proxmox VE](#pages-that-link-to-developer-documentation-proxmox-ve) - [Developer Documentation - Proxmox VE](#developer-documentation-proxmox-ve) - [Category:Development - Proxmox VE](#category-development-proxmox-ve) - [FAQ - Proxmox VE](#faq-proxmox-ve) - [Installation - Proxmox VE](#installation-proxmox-ve) - [Downloads - Proxmox VE](#downloads-proxmox-ve) - [Categories - Proxmox VE](#categories-proxmox-ve) - [Proxmox VE](#proxmox-ve) - [Proxmox VE Documentation Index](#proxmox-ve-documentation-index) - [Proxmox VE Documentation Index](#proxmox-ve-documentation-index) - [Special pages - Proxmox VE](#special-pages-proxmox-ve) - [Category:HOWTO - Proxmox VE](#category-howto-proxmox-ve) - [Wanted categories - Proxmox VE](#wanted-categories-proxmox-ve) - [User:Thomas Lamprecht - Proxmox VE](#user-thomas-lamprecht-proxmox-ve) - [Additional ways to migrate to Proxmox VE - Proxmox VE](#additional-ways-to-migrate-to-proxmox-ve-proxmox-ve) - [Statistics - Proxmox VE](#statistics-proxmox-ve) - [Broken redirects - Proxmox VE](#broken-redirects-proxmox-ve) - [System Software Updates - Proxmox VE](#system-software-updates-proxmox-ve) - [Storage Plugin Development - Proxmox VE](#storage-plugin-development-proxmox-ve) - [User talk:Thomas Lamprecht - Proxmox VE](#user-talk-thomas-lamprecht-proxmox-ve) - [Advanced Migration Techniques to Proxmox VE - Proxmox VE](#advanced-migration-techniques-to-proxmox-ve-proxmox-ve) - [Open Source - Proxmox VE](#open-source-proxmox-ve) - [Anatomy of LXC Container Config File - Proxmox VE](#anatomy-of-lxc-container-config-file-proxmox-ve) - [Prepare Installation Media - Proxmox VE](#prepare-installation-media-proxmox-ve) - [Prepare Installation Media - Proxmox VE](#prepare-installation-media-proxmox-ve) - [Upgrade from 8 to 9 - Proxmox VE](#upgrade-from-8-to-9-proxmox-ve) - [Category:Archive - Proxmox VE](#category-archive-proxmox-ve) - [Dead-end pages - Proxmox VE](#dead-end-pages-proxmox-ve) - [Notifications](#notifications) - [pvenode(1)](#pvenode-1-) - [PVE QEMU Event Daemon](#pve-qemu-event-daemon) - [pvesubscription(1)](#pvesubscription-1-) - [Talk:Upgrade from 4.x to 5.0 - Proxmox VE](#talk-upgrade-from-4-x-to-5-0-proxmox-ve) - [Iscsi/tests - Proxmox VE](#iscsi-tests-proxmox-ve) - [ZFS: Switch Legacy-Boot to Proxmox Boot Tool - Proxmox VE](#zfs-switch-legacy-boot-to-proxmox-boot-tool-proxmox-ve) - [QEMU/KVM ACPI Guest Shutdown - Proxmox VE](#qemu-kvm-acpi-guest-shutdown-proxmox-ve) - [Qemu-guest-agent - Proxmox VE](#qemu-guest-agent-proxmox-ve) - [HTTPS Certificate Configuration (Version 4.x, 5.0 and 5.1) - Proxmox VE](#https-certificate-configuration-version-4-x-5-0-and-5-1-proxmox-ve) - [OpenVZ Console - Proxmox VE](#openvz-console-proxmox-ve) - [High Availability Cluster - Proxmox VE](#high-availability-cluster-proxmox-ve) - [Troubleshooting - Proxmox VE](#troubleshooting-proxmox-ve) - [Storage: ZFS over ISCSI - Proxmox VE](#storage-zfs-over-iscsi-proxmox-ve) - [Two-Factor Authentication - Proxmox VE](#two-factor-authentication-proxmox-ve) - [Proxmox Datacenter Manager Upgrade from Alpha to 1 - Proxmox VE](#proxmox-datacenter-manager-upgrade-from-alpha-to-1-proxmox-ve) - [MediaWiki:Restricted-displaytitle-ignored - Proxmox VE](#mediawiki-restricted-displaytitle-ignored-proxmox-ve) - [MediaWiki:Node-count-exceeded-category - Proxmox VE](#mediawiki-node-count-exceeded-category-proxmox-ve) - [Talk:Storage: LVM Thin - Proxmox VE](#talk-storage-lvm-thin-proxmox-ve) - [Talk:Storage: NFS - Proxmox VE](#talk-storage-nfs-proxmox-ve) - [Template:Langif - Proxmox VE](#template-langif-proxmox-ve) - [Category talk:Virtual Appliances - Proxmox VE](#category-talk-virtual-appliances-proxmox-ve) - [Proxmox VE Mobile Companion Data Protection - Proxmox VE](#proxmox-ve-mobile-companion-data-protection-proxmox-ve) - [Template:VZAPL - Proxmox VE](#template-vzapl-proxmox-ve) - [Talk:Backup and Restore - Proxmox VE](#talk-backup-and-restore-proxmox-ve) - [Certificate Management - Proxmox VE](#certificate-management-proxmox-ve) - [Talk:Storage: LVM - Proxmox VE](#talk-storage-lvm-proxmox-ve) - [Talk:Storage: RBD - Proxmox VE](#talk-storage-rbd-proxmox-ve) - [Subscriptions - Proxmox VE](#subscriptions-proxmox-ve) - [Talk:Debian Appliance Builder - Proxmox VE](#talk-debian-appliance-builder-proxmox-ve) - [Calendar Events - Proxmox VE](#calendar-events-proxmox-ve) - [BTRFS - Proxmox VE](#btrfs-proxmox-ve) - [Pages that link to "Template:Db" - Proxmox VE](#pages-that-link-to-template-db-proxmox-ve) - [Pages that link to "Debugging Installation" - Proxmox VE](#pages-that-link-to-debugging-installation-proxmox-ve) - [OVMF/UEFI Boot Entries - Proxmox VE](#ovmf-uefi-boot-entries-proxmox-ve) - [Pages that link to "Hotplug (qemu disk,nic,cpu,memory)" - Proxmox VE](#pages-that-link-to-hotplug-qemu-disk-nic-cpu-memory-proxmox-ve) - [Talk:Cluster Manager - Proxmox VE](#talk-cluster-manager-proxmox-ve) - [Recover From Grub Failure - Proxmox VE](#recover-from-grub-failure-proxmox-ve) - [Ports - Proxmox VE](#ports-proxmox-ve) - [Win7 Guest DHCP not working fix - Proxmox VE](#win7-guest-dhcp-not-working-fix-proxmox-ve) - [Getting Help - Proxmox VE](#getting-help-proxmox-ve) - [USB Redirector - Proxmox VE](#usb-redirector-proxmox-ve) - [SPICE - Proxmox VE](#spice-proxmox-ve) - [Install Proxmox VE on Debian Buster - Proxmox VE](#install-proxmox-ve-on-debian-buster-proxmox-ve) - [Pages that link to "QEMU/KVM Virtual Machines" - Proxmox VE](#pages-that-link-to-qemu-kvm-virtual-machines-proxmox-ve) - [Full Mesh Network for Ceph Server - Proxmox VE](#full-mesh-network-for-ceph-server-proxmox-ve) - [Pages that link to "High Availability" - Proxmox VE](#pages-that-link-to-high-availability-proxmox-ve) - [High Availability Cluster 4.x - Proxmox VE](#high-availability-cluster-4-x-proxmox-ve) - [Storage: BTRFS - Proxmox VE](#storage-btrfs-proxmox-ve) - [HTTPS Certificate Configuration (Version 3.x and earlier) - Proxmox VE](#https-certificate-configuration-version-3-x-and-earlier-proxmox-ve) - [User contributions for 2020media - Proxmox VE](#user-contributions-for-2020media-proxmox-ve) - [Talk:Ceph Server - Proxmox VE](#talk-ceph-server-proxmox-ve) - [Windows 2008 guest best practices - Proxmox VE](#windows-2008-guest-best-practices-proxmox-ve) - [File:New Text Document.txt - Proxmox VE](#file-new-text-document-txt-proxmox-ve) - [Firewall - Proxmox VE](#firewall-proxmox-ve) - [Import certificate in browser - Proxmox VE](#import-certificate-in-browser-proxmox-ve) - [NUMA - Proxmox VE](#numa-proxmox-ve) - [Proxmox VE 2.0 Cluster - Proxmox VE](#proxmox-ve-2-0-cluster-proxmox-ve) - [Paravirtualized Block Drivers for Windows - Proxmox VE](#paravirtualized-block-drivers-for-windows-proxmox-ve) - [Bibliography - Proxmox VE](#bibliography-proxmox-ve) - [Pages that link to "DRBD" - Proxmox VE](#pages-that-link-to-drbd-proxmox-ve) - [PVE2ClusterTestBed - Proxmox VE](#pve2clustertestbed-proxmox-ve) - [Template:Languages - Proxmox VE](#template-languages-proxmox-ve) - [User contributions for Hd-- - Proxmox VE](#user-contributions-for-hd-proxmox-ve) - [Proxmox VE News - Proxmox VE](#proxmox-ve-news-proxmox-ve) - [Pages that link to "Upgrade from 1.9 to 2.0" - Proxmox VE](#pages-that-link-to-upgrade-from-1-9-to-2-0-proxmox-ve) - [Pages that link to "Help:Contents" - Proxmox VE](#pages-that-link-to-help-contents-proxmox-ve) - [MediaWiki:Noindex-category - Proxmox VE](#mediawiki-noindex-category-proxmox-ve) - [Pages that link to "Template:Emptylang" - Proxmox VE](#pages-that-link-to-template-emptylang-proxmox-ve) - [Install Proxmox VE on Debian 11 Bullseye - Proxmox VE](#install-proxmox-ve-on-debian-11-bullseye-proxmox-ve) - [Passthrough Physical Disk to Virtual Machine (VM) - Proxmox VE](#passthrough-physical-disk-to-virtual-machine-vm-proxmox-ve) - [Pages that link to "Legacy: ZFS over iSCSI" - Proxmox VE](#pages-that-link-to-legacy-zfs-over-iscsi-proxmox-ve) - [Storage Replication - Proxmox VE](#storage-replication-proxmox-ve) - [Linux Container - Proxmox VE](#linux-container-proxmox-ve) - [File:New Text Document.tar.gz - Proxmox VE](#file-new-text-document-tar-gz-proxmox-ve) - [Pages that link to "Storage Model" - Proxmox VE](#pages-that-link-to-storage-model-proxmox-ve) - [Cloud-Init Support - Proxmox VE](#cloud-init-support-proxmox-ve) - [Pages that link to "Dynamic Memory Management" - Proxmox VE](#pages-that-link-to-dynamic-memory-management-proxmox-ve) - [MediaWiki:Post-expand-template-inclusion-category - Proxmox VE](#mediawiki-post-expand-template-inclusion-category-proxmox-ve) - [MediaWiki:Unstrip-size-category - Proxmox VE](#mediawiki-unstrip-size-category-proxmox-ve) - [Template:Tts - Proxmox VE](#template-tts-proxmox-ve) - [MediaWiki:Template-equals-category - Proxmox VE](#mediawiki-template-equals-category-proxmox-ve) - [Passthrough Physical Disk to Virtual Machine (VM) - Proxmox VE](#passthrough-physical-disk-to-virtual-machine-vm-proxmox-ve) - [Template:VirtIOFedoraISOFolderNames - Proxmox VE](#template-virtiofedoraisofoldernames-proxmox-ve) - [MediaWiki:Math-tracking-category-mhchem-deprecation - Proxmox VE](#mediawiki-math-tracking-category-mhchem-deprecation-proxmox-ve) - [Pages that link to "Storage: User Mode iSCSI" - Proxmox VE](#pages-that-link-to-storage-user-mode-iscsi-proxmox-ve) - [Pages that link to "Host System Administration" - Proxmox VE](#pages-that-link-to-host-system-administration-proxmox-ve) - [DRBD9 - Proxmox VE](#drbd9-proxmox-ve) - [Cisco UCS - Proxmox VE](#cisco-ucs-proxmox-ve) - [MediaWiki:Double-px-category - Proxmox VE](#mediawiki-double-px-category-proxmox-ve) - [Load - Proxmox VE](#load-proxmox-ve) - [Pages that link to "System Requirements" - Proxmox VE](#pages-that-link-to-system-requirements-proxmox-ve) - [Performance Tweaks - Proxmox VE](#performance-tweaks-proxmox-ve) - [Pages that link to "Accessing Server using different URLs" - Proxmox VE](#pages-that-link-to-accessing-server-using-different-urls-proxmox-ve) - [PBS Client CPU Benchmark - Proxmox VE](#pbs-client-cpu-benchmark-proxmox-ve) - [Pages that link to "Dell blade servers" - Proxmox VE](#pages-that-link-to-dell-blade-servers-proxmox-ve) - [Template:Warning - Proxmox VE](#template-warning-proxmox-ve) - [Template:Note - Proxmox VE](#template-note-proxmox-ve) - [MxGPU with AMD S7150 under Proxmox VE 5.x - Proxmox VE](#mxgpu-with-amd-s7150-under-proxmox-ve-5-x-proxmox-ve) - [Windows NT Guest Notes - Proxmox VE](#windows-nt-guest-notes-proxmox-ve) - [File:Svn-export.tar.gz - Proxmox VE](#file-svn-export-tar-gz-proxmox-ve) - [Command line tools - PVE 3.x - Proxmox VE](#command-line-tools-pve-3-x-proxmox-ve) - [VNC - Proxmox VE](#vnc-proxmox-ve) - [Unlock Locked OpenVZ Container - Proxmox VE](#unlock-locked-openvz-container-proxmox-ve) - [Pages that link to "MediaWiki" - Proxmox VE](#pages-that-link-to-mediawiki-proxmox-ve) - [Firmware Updates - Proxmox VE](#firmware-updates-proxmox-ve) - [User:Martin - Proxmox VE](#user-martin-proxmox-ve) - [ProxyPass Reverse - Proxmox VE](#proxypass-reverse-proxmox-ve) - [User contributions for ANeutrino - Proxmox VE](#user-contributions-for-aneutrino-proxmox-ve) - [Proxmox VE inside VirtualBox - Proxmox VE](#proxmox-ve-inside-virtualbox-proxmox-ve) - [Split lock detection - Proxmox VE](#split-lock-detection-proxmox-ve) - [Pages that link to "Debian 4.0 Standard" - Proxmox VE](#pages-that-link-to-debian-4-0-standard-proxmox-ve) - [Unattended installation of Proxmox - Proxmox VE](#unattended-installation-of-proxmox-proxmox-ve) - [Pages that link to "Ceph Server" - Proxmox VE](#pages-that-link-to-ceph-server-proxmox-ve) - [Proxmox VE Mobile - Proxmox VE](#proxmox-ve-mobile-proxmox-ve) - [Pages that link to "Deploy Hyper-Converged Ceph Cluster" - Proxmox VE](#pages-that-link-to-deploy-hyper-converged-ceph-cluster-proxmox-ve) - [Upgrade a 4.x Installation using a newer ISO image - Proxmox VE](#upgrade-a-4-x-installation-using-a-newer-iso-image-proxmox-ve) - [Root Password Reset - Proxmox VE](#root-password-reset-proxmox-ve) - [Solaris guest best practices - Proxmox VE](#solaris-guest-best-practices-proxmox-ve) - [Ceph mClock Tuning - Proxmox VE](#ceph-mclock-tuning-proxmox-ve) - [OpenVZ on ISCSI howto - Proxmox VE](#openvz-on-iscsi-howto-proxmox-ve) - [Pages that link to "Editing corosync.conf" - Proxmox VE](#pages-that-link-to-editing-corosync-conf-proxmox-ve) - [Certified Appliance: CYAN Secure Web - Proxmox VE](#certified-appliance-cyan-secure-web-proxmox-ve) - [File System level backups with LVM snapshots - Proxmox VE](#file-system-level-backups-with-lvm-snapshots-proxmox-ve) - [Certified Appliance: Proxmox Mail Gateway - Proxmox VE](#certified-appliance-proxmox-mail-gateway-proxmox-ve) - [Pages that link to "Category:Upgrade" - Proxmox VE](#pages-that-link-to-category-upgrade-proxmox-ve) - [Install Proxmox VE on Debian Wheezy - Proxmox VE](#install-proxmox-ve-on-debian-wheezy-proxmox-ve) - [Pages that link to "Upgrade from 3.x to 4.0" - Proxmox VE](#pages-that-link-to-upgrade-from-3-x-to-4-0-proxmox-ve) - [Windows XP Guest Notes - Proxmox VE](#windows-xp-guest-notes-proxmox-ve) - [Pages that link to "Upgrade from 5.x to 6.0" - Proxmox VE](#pages-that-link-to-upgrade-from-5-x-to-6-0-proxmox-ve) - [Pages that link to "User Management" - Proxmox VE](#pages-that-link-to-user-management-proxmox-ve) - [Graphical User Interface - Proxmox VE](#graphical-user-interface-proxmox-ve) - [Pages that link to "Build your first DAB Appliance Template" - Proxmox VE](#pages-that-link-to-build-your-first-dab-appliance-template-proxmox-ve) - [OpenVZ - Proxmox VE](#openvz-proxmox-ve) - [Guest Boot Problems - Proxmox VE](#guest-boot-problems-proxmox-ve) - [Kernel Samepage Merging (KSM) - Proxmox VE](#kernel-samepage-merging-ksm-proxmox-ve) - [Command Line Tools - Proxmox VE](#command-line-tools-proxmox-ve) - [Debian Etch Standard - Proxmox VE](#debian-etch-standard-proxmox-ve) - [Pages that link to "DotDEB Page" - Proxmox VE](#pages-that-link-to-dotdeb-page-proxmox-ve) - [Pages that link to "FengOffice" - Proxmox VE](#pages-that-link-to-fengoffice-proxmox-ve) - [Proxmox VE API - Proxmox VE](#proxmox-ve-api-proxmox-ve) - [Pages that link to "Quick installation" - Proxmox VE](#pages-that-link-to-quick-installation-proxmox-ve) - [IO Scheduler - Proxmox VE](#io-scheduler-proxmox-ve) - [Install Proxmox VE on Debian 13 Trixie - Proxmox VE](#install-proxmox-ve-on-debian-13-trixie-proxmox-ve) - [OpenVZ VM First Boot Setup Tips - Proxmox VE](#openvz-vm-first-boot-setup-tips-proxmox-ve) - [Pages that link to "Intel Modular Server HA" - Proxmox VE](#pages-that-link-to-intel-modular-server-ha-proxmox-ve) - [Manual: cpu-models.conf - Proxmox VE](#manual-cpu-models-conf-proxmox-ve) - [Pages that link to "Storage" - Proxmox VE](#pages-that-link-to-storage-proxmox-ve) - [Pages that link to "Windows 2003 guest best practices" - Proxmox VE](#pages-that-link-to-windows-2003-guest-best-practices-proxmox-ve) - [Pages that link to "Upgrade from 6.x to 7.0" - Proxmox VE](#pages-that-link-to-upgrade-from-6-x-to-7-0-proxmox-ve) - [Proxmox Datacenter Manager Upgrade from Alpha to 1 - Proxmox VE](#proxmox-datacenter-manager-upgrade-from-alpha-to-1-proxmox-ve) - [Cloud-Init FAQ - Proxmox VE](#cloud-init-faq-proxmox-ve) - [Template:WinX-install-steps - Proxmox VE](#template-winx-install-steps-proxmox-ve) - [PVE-zsync - Proxmox VE](#pve-zsync-proxmox-ve) - [User talk:Alejandra - Proxmox VE](#user-talk-alejandra-proxmox-ve) - [User:Alen - Proxmox VE](#user-alen-proxmox-ve) - [LVM2 - Proxmox VE](#lvm2-proxmox-ve) - [Serial Terminal - Proxmox VE](#serial-terminal-proxmox-ve) - [User contributions for M.frank - Proxmox VE](#user-contributions-for-m-frank-proxmox-ve) - [User contributions for Aasami - Proxmox VE](#user-contributions-for-aasami-proxmox-ve) - [X11 LXDE in OpenVZ - Proxmox VE](#x11-lxde-in-openvz-proxmox-ve) - [Service daemons - Proxmox VE](#service-daemons-proxmox-ve) - [Legacy: ZFS over iSCSI - Proxmox VE](#legacy-zfs-over-iscsi-proxmox-ve) - [Pages that link to "Convert OpenVZ to LXC" - Proxmox VE](#pages-that-link-to-convert-openvz-to-lxc-proxmox-ve) - [Pages that link to "Central Web-based Management" - Proxmox VE](#pages-that-link-to-central-web-based-management-proxmox-ve) - [NVIDIA vGPU on Proxmox VE - Proxmox VE](#nvidia-vgpu-on-proxmox-ve-proxmox-ve) - [Install Proxmox VE on Debian Squeeze on 32-Bit Processor - Proxmox VE](#install-proxmox-ve-on-debian-squeeze-on-32-bit-processor-proxmox-ve) - [Windows VirtIO Drivers - Proxmox VE](#windows-virtio-drivers-proxmox-ve) - [HTTPS Certificate Configuration (Version 4.x, 5.0 and 5.1) - Proxmox VE](#https-certificate-configuration-version-4-x-5-0-and-5-1-proxmox-ve) - [Introduction - Proxmox VE](#introduction-proxmox-ve) - [Install Proxmox VE on Debian Squeeze - Proxmox VE](#install-proxmox-ve-on-debian-squeeze-proxmox-ve) - [Pages that link to "Migrate to Proxmox VE" - Proxmox VE](#pages-that-link-to-migrate-to-proxmox-ve-proxmox-ve) - [Pages that link to "Cluster Manager" - Proxmox VE](#pages-that-link-to-cluster-manager-proxmox-ve) - [Windows 2012 guest best practices - Proxmox VE](#windows-2012-guest-best-practices-proxmox-ve) - [Windows 2019 guest best practices - Proxmox VE](#windows-2019-guest-best-practices-proxmox-ve) - [PCI Passthrough - Proxmox VE](#pci-passthrough-proxmox-ve) - [Dynamic Memory Management - Proxmox VE](#dynamic-memory-management-proxmox-ve) - [Windows 10 guest best practices - Proxmox VE](#windows-10-guest-best-practices-proxmox-ve) - [Windows 7 guest best practices - Proxmox VE](#windows-7-guest-best-practices-proxmox-ve) - [Windows 2016 guest best practices - Proxmox VE](#windows-2016-guest-best-practices-proxmox-ve) - [User contributions for A.zeidler - Proxmox VE](#user-contributions-for-a-zeidler-proxmox-ve) - [User contributions for S.sterz - Proxmox VE](#user-contributions-for-s-sterz-proxmox-ve) - [User contributions for L.Leahu-Vladucu - Proxmox VE](#user-contributions-for-l-leahu-vladucu-proxmox-ve) - [User contributions for A.lauterer - Proxmox VE](#user-contributions-for-a-lauterer-proxmox-ve) - [Proxmox Datacenter Manager Roadmap - Proxmox VE](#proxmox-datacenter-manager-roadmap-proxmox-ve) - [YubiKey - Proxmox VE](#yubikey-proxmox-ve) - [Pages that link to "Template:Languages" - Proxmox VE](#pages-that-link-to-template-languages-proxmox-ve) - [Related changes - Proxmox VE](#related-changes-proxmox-ve) - [Proxmox VE:Language policy - Proxmox VE](#proxmox-ve-language-policy-proxmox-ve) - [Related changes - Proxmox VE](#related-changes-proxmox-ve) - [Related changes - Proxmox VE](#related-changes-proxmox-ve) - [Related changes - Proxmox VE](#related-changes-proxmox-ve) - [Pages that link to "Category:Proxmox VE 3" - Proxmox VE](#pages-that-link-to-category-proxmox-ve-3-proxmox-ve) - [Related changes - Proxmox VE](#related-changes-proxmox-ve) - [Related changes - Proxmox VE](#related-changes-proxmox-ve) - [Related changes - Proxmox VE](#related-changes-proxmox-ve) - [Related changes - Proxmox VE](#related-changes-proxmox-ve) - [Related changes - Proxmox VE](#related-changes-proxmox-ve) - [Proxmox VE:Terms of Service - Proxmox VE](#proxmox-ve-terms-of-service-proxmox-ve) - [Pages that link to "Category:HA" - Proxmox VE](#pages-that-link-to-category-ha-proxmox-ve) - [Pages that link to "Category:High Availability" - Proxmox VE](#pages-that-link-to-category-high-availability-proxmox-ve) - [Pages that link to "Category:Proxmox VE 3.x" - Proxmox VE](#pages-that-link-to-category-proxmox-ve-3-x-proxmox-ve) - [Related changes - Proxmox VE](#related-changes-proxmox-ve) - [Related changes - Proxmox VE](#related-changes-proxmox-ve) - [Related changes - Proxmox VE](#related-changes-proxmox-ve) - [Related changes - Proxmox VE](#related-changes-proxmox-ve) - [Storage: GlusterFS - Proxmox VE](#storage-glusterfs-proxmox-ve) - [Api-viewer/index.html - Proxmox VE](#api-viewer-index-html-proxmox-ve) - [Related changes - Proxmox VE](#related-changes-proxmox-ve) - [Related changes - Proxmox VE](#related-changes-proxmox-ve) - [Related changes - Proxmox VE](#related-changes-proxmox-ve) - [Related changes - Proxmox VE](#related-changes-proxmox-ve) - [Related changes - Proxmox VE](#related-changes-proxmox-ve) - [Related changes - Proxmox VE](#related-changes-proxmox-ve) - [Related changes - Proxmox VE](#related-changes-proxmox-ve) --- # Developer Documentation - Proxmox VE Developer Documentation ======================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Developer_Documentation#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Developer_Documentation#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Developer_Documentation#Introduction) * [2 Mailing List](https://pve.proxmox.com/wiki/Developer_Documentation#Mailing_List) * [2.1 Public Inbox](https://pve.proxmox.com/wiki/Developer_Documentation#Public_Inbox) * [3 Access to Code Repository (git)](https://pve.proxmox.com/wiki/Developer_Documentation#Access_to_Code_Repository_(git)) * [4 Build instructions](https://pve.proxmox.com/wiki/Developer_Documentation#Build_instructions) * [5 Development Package Repository](https://pve.proxmox.com/wiki/Developer_Documentation#Development_Package_Repository) * [5.1 For Proxmox VE 9 based on Debian 13 Trixie](https://pve.proxmox.com/wiki/Developer_Documentation#For_Proxmox_VE_9_based_on_Debian_13_Trixie) * [5.2 For Proxmox VE 8 based on Debian 12 Bookworm](https://pve.proxmox.com/wiki/Developer_Documentation#For_Proxmox_VE_8_based_on_Debian_12_Bookworm) * [6 Checking out a git repository](https://pve.proxmox.com/wiki/Developer_Documentation#Checking_out_a_git_repository) * [7 Working on the code](https://pve.proxmox.com/wiki/Developer_Documentation#Working_on_the_code) * [7.1 Coding guidelines](https://pve.proxmox.com/wiki/Developer_Documentation#Coding_guidelines) * [7.1.1 Perl](https://pve.proxmox.com/wiki/Developer_Documentation#Perl) * [7.1.2 Rust](https://pve.proxmox.com/wiki/Developer_Documentation#Rust) * [7.1.3 JavaScript](https://pve.proxmox.com/wiki/Developer_Documentation#JavaScript) * [7.1.4 Documentation](https://pve.proxmox.com/wiki/Developer_Documentation#Documentation) * [7.2 Using git](https://pve.proxmox.com/wiki/Developer_Documentation#Using_git) * [7.2.1 Commits and Commit Messages](https://pve.proxmox.com/wiki/Developer_Documentation#Commits_and_Commit_Messages) * [8 Preparing Patches](https://pve.proxmox.com/wiki/Developer_Documentation#Preparing_Patches) * [8.1 Versioned Patches](https://pve.proxmox.com/wiki/Developer_Documentation#Versioned_Patches) * [8.2 Reviewing patches](https://pve.proxmox.com/wiki/Developer_Documentation#Reviewing_patches) * [8.3 Convenience Settings](https://pve.proxmox.com/wiki/Developer_Documentation#Convenience_Settings) * [9 Sending Patches](https://pve.proxmox.com/wiki/Developer_Documentation#Sending_Patches) * [9.1 Tutorial](https://pve.proxmox.com/wiki/Developer_Documentation#Tutorial) * [9.2 Using Authenticated SMTP Server](https://pve.proxmox.com/wiki/Developer_Documentation#Using_Authenticated_SMTP_Server) * [9.3 Example](https://pve.proxmox.com/wiki/Developer_Documentation#Example) * [10 Bugtracker (bugzilla)](https://pve.proxmox.com/wiki/Developer_Documentation#Bugtracker_(bugzilla)) * [11 Software License and Copyright](https://pve.proxmox.com/wiki/Developer_Documentation#Software_License_and_Copyright) * [12 See Also](https://pve.proxmox.com/wiki/Developer_Documentation#See_Also) Introduction ------------ This wiki describes the higher level developer documentation for all Proxmox projects, including Proxmox VE, Proxmox Backup Server and Proxmox Mail Gateway and Proxmox Offline Mirror. Please coordinate your efforts with us before starting any development. It is important to have a common view of the problem and the corresponding solution – just to avoid duplicated or unnecessary efforts. We will only include software which matches our quality criteria. The source code repository is read only. To include some code, send it as patch (git diff) to the pve-devel mailing list. We will review your code and commit after a successful review (and possible corrections/additions). Mailing List ------------ This is the primary communication channel for developers, discussing new features and implementation details. If you are a developer, and you want to develop additional features, this is the place to start. Proxmox VE Development List: [https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel](https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel) Archive: [https://lists.proxmox.com/pipermail/pve-devel/](https://lists.proxmox.com/pipermail/pve-devel/) ### Public Inbox In addition to the native mailing list archive, Proxmox runs a Public Inbox instance at [lore.proxmox.com](https://lore.proxmox.com/) that archives and indexes all messages sent to all of our public mailing lists (`pve-devel`, `pbs-devel`, `pmg-devel`, `pve-user`). Public Inbox also provides a convenient and powerful search interface, see the [public-inbox help](https://lore.proxmox.com/pve-devel/_/text/help/) for an overview and the [official Public Inbox README](https://public-inbox.org/README.html) for more features. There are also tools that build on top of Public Inbox's features, such as [b4](https://b4.docs.kernel.org/en/latest/) , which can help to pull and review patches. Access to Code Repository (git) ------------------------------- [https://git.proxmox.com](https://git.proxmox.com/) Build instructions ------------------ You could find build instructions here : [https://git.proxmox.com/?p=pve-common.git;a=blob\_plain;f=README.dev;hb=HEAD](https://git.proxmox.com/?p=pve-common.git;a=blob_plain;f=README.dev;hb=HEAD) Development Package Repository ------------------------------ Some packages required for development can only be found in the _devel_ repository. While the headlines specifically mention Proxmox VE, these repos are used for all Proxmox project based on a the mentioned Debian release. ### For Proxmox VE 9 based on Debian 13 Trixie Create a new file at `/etc/apt/sources.list.d/proxmox.sources` with the following contents: Types: deb URIs: [http://download.proxmox.com/debian/devel/](http://download.proxmox.com/debian/devel/) Suites: trixie Components: main Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg Since Debian 13 "Trixie", the [DEB822](https://manpages.debian.org/trixie/dpkg-dev/deb822.5.en.html) format is preferred. ### For Proxmox VE 8 based on Debian 12 Bookworm Add the following to the `/etc/apt/sources.list` file: deb [http://download.proxmox.com/debian/devel/](http://download.proxmox.com/debian/devel/) bookworm main Checking out a git repository ----------------------------- To clone a repository run 'git clone' with the repository name prefixed with the common URL: git://git.proxmox.com/git/ \# git clone [git://git.proxmox.com/git/pve-manager.git](git://git.proxmox.com/git/pve-manager.git) To update an already cloned project to the current version use: \# git pull Working on the code ------------------- ### Coding guidelines The codebase mostly contains Perl and rust code for the backend, JavaScript for the user interface, and C for the Proxmox Cluster Filesystem and upstream projects like the Linux kernel or QEMU. The documentation for Proxmox VE is written in AsciiDoc, using the python implementation. #### Perl For Perl, we recommend having a look at our [**perl style guide**](https://pve.proxmox.com/wiki/Perl_Style_Guide "Perl Style Guide") . #### Rust For our Rust code we use `rustfmt` (e.g., through `cargo fmt`) with default settings. Compiler warnings must be avoided. Additionally, one might check lints reported by `cargo clippy`, but we do not accept mass fixing of those all over the place, such fixes are not always productive and can introduce actual subtle (logical) errors. #### JavaScript For JavaScript, we use `eslint` as separate package to check basic code standards. New contribution must not ensure that eslint doesn't output any warning or error. Check out [Javascript Style Guide](https://pve.proxmox.com/wiki/Javascript_Style_Guide "Javascript Style Guide") We use the ExtJS framework for the web UI Components, its API documentation can be found at [https://docs.sencha.com/extjs/7.0.0/](https://docs.sencha.com/extjs/7.0.0/) . #### Documentation Avoid overly long line. Use line-length from context, which is 80 character columns most of the time, try to stay below 100 as maximum. Adhere to our [Technical Writing Style Guide](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide "Technical Writing Style Guide") . To make references explicit for already existing sections, use the auto-generated reference to avoid breaking external deep links. For example, this was done with `[[_corosync_external_vote_support]]` in [this commit](https://git.proxmox.com/?p=pve-docs.git;a=commitdiff;h=ab83397071d2e315e6aab41c19b047b494eb4d26;hp=065e6a1cd5b94b05f8de74e00a33a2ef6dc1c653) . For new sections, anchors for references should be prefixed by the chapter name, for example `[[pvecm_cluster_requirements]]` in the `pvecm - Proxmox VE Cluster Manager` chapter. ### Using git If you are not familiar with git it could be worth to take a look at this interactive tutorial: [https://try.github.io](https://try.github.io/) and read a brief introduction chapter from the official git documentation: [https://git-scm.com/docs/gittutorial](https://git-scm.com/docs/gittutorial) to gain basic knowledge on it. First, configure your _real_ name and email address for git, if not done already: $ git config --global user.name "John Doe" $ git config --global user.email john@example.com This will be used to sign off commits as your work. It is recommended to start a feature branch before working on the code locally: \# git checkout -f -b my\_branch master After this you can start working on your improvements. You'll be able to compare your changes to the current PVE master branch easily with \# git diff master..my\_branch #### Commits and Commit Messages Then, make your commit (try to make small, but self-contained, commits) and include a sign-off line (-s). In general, commit messages should be written with the following style guide in mind: * Write your commit message in the imperative: "Fix bug" and not "Fixed bug" or "Fixes bug." This convention matches up with commit messages generated by commands like git merge and git revert. * Avoid using "we", as for readers it's unclear who is meant. * Make sure the **line-length** (text-width, column count) of the commit's message is **not longer than 72 characters**. Note, HTTPS links and git trailers (e.g., `Signed-off-by:`, `Reviewed-by:` or `Fixes:`) are an exception and must **not** be split over multiple lines. * Add your `Signed-off-by: Your Name ` trailer and also track trailers from other people, like `Suggested-by`, `Co-authored-by`, `Tested-by`, `Reviewed-by` Note: Trailers should be _[causally](https://en.wikipedia.org/wiki/Causality) ordered_. For instance, a `Suggested-by` should be listed _before_ a `Signed-off-by` (the suggestion _caused_ you to create the commit), a `Tested-by` _after_ a `Signed-off-by` (a commit is created before one is able to test it). * If the commit fixes a bug **start** with that information in this form: `fix #1234: summary here` If it implements a feature tracked on Bugzilla you can also use: `close #1234: summary here` albeit `fix #1234:` is more commonly used and also fine * Try to add a tag prefix to denote the subsystem you're (mainly) changing, if an obvious choice exists. * For example, if you changed the QEMU UI component in pve-manager, a possible tag could be `ui: qemu: rest of summary here` * Don't add tags for things that are already clear from context, for example, adding a `qemu` tag for a patch in the qemu-server repository has no use. * But, do **not** just paste the affected files, including (parts of the) path and maybe even the file ending, as tag! That has no use (already contained in diff stat) and just makes it harder to read. * Commit messages are intended for human readers and should therefore focus on providing a brief summary of the core semantic changes and the rationale behind them. * Ideally, the subject is worded such, that it can be copied directly into the `debian/changelog`, which is consumed by end users. * Most of the time it's best to avoid mentioning implementations details, like for example specific function or type names in verbatim as written in the programming language. An exception can be changes, that do not have any visible (semantic) effect for users, like pure refactoring (movement of code without changing its logic) or preparations, especially if they happen in pure library repos/crates. But even there one often benefits from a higher-level human-readable overview too. * Do not put in a literal description of the code diff, especially not for simpler changes. The commit message should not focus on the detailed what's done/changed but rather answer: * Why this was done otherwise previously (or why this was missing until now). * Why the new approach is better or necessary (e.g., a bug was found, requirements changed, a prerequisite was merged that enables this). * What the resulting effect is for users or developers (if not already obvious from the subject line). If there should be no visible/semantic change then explicitly stating so can also be good for non-trivial changes. You can always edit the commit message of the most recent commit using amend: \# git commit --amend If you work on a series you can use the git rebase command to re-order, drop, squash/fixup and edit both the whole commit or just rewording its message: git rebase -i --autosquash --autostash origin/master The `autostash` is not required, but convenient if there are still pending changes, it will stash before rebase starts and apply again after rebase is done. The `autosquash` is also not required, but very convenient to auto squash fixups (`git commit --fixup=`) made for older commits in a development series The following command will take all changes of tracked files and add it to the commit: \# git commit -s -a New files won't get added automatically. To do that, or to just add some changed files to a commit, use \# git add newfile1.pl file2.pl You can always look at what will get into commit with: \# git diff --staged Preparing Patches ----------------- ℹ️ **Note**: For all repositories where Proxmox is the upstream, and where not explicitly noted otherwise, a valid [CLA](https://pve.proxmox.com/wiki/Developer_Documentation#Software_License_and_Copyright) is required to include your changes Since we have several projects in our git repository and only one development mailing list, we ask you to clarify which repository your patches are meant for by specifying it in the subject prefix. Since some names are long it's fine if you shorten them (eg. remove the 'pve-' prefix). Creating the raw patch series, for instance for the pve-container package: \# rm -rf my-patches/ # to clean left-overs # git format-patch -s -o my-patches/ --subject-prefix="PATCH container" master..my\_branch --cover-letter Explain in the cover letter the aim of your patches: edit my-patches/0000-cover-letter.patch ℹ️ **Note**: Adding a cover letter is useful every time you send more than a single patch. It makes it easier for tools like `b4` to assign additional git trailers to commits when applying them. The diffstat over all changes is also useful to gauge the impact of the patches. Sending patches: \# git send-email --to=pve-devel@lists.proxmox.com my-patches/00\*.patch # rm -rf my-patches/ # to clean left-overs If you wish to write comments for individual patches, you can do that either in the cover-letter, or in the patch's _commit summary section_ (between the line consisting of 3 consecutive dashes ending your commit message and before the list of files with their change-counts. Example: From 12345abcde Mon Sep 12 00:00:00 2001 From: Git Committer Date: Fri, 7 Oct 2016 08:30:17 +0200 Subject: \[PATCH v2 container 1/2\] Fix #1013: this and that Here is your commit message. It explains the bugfix and ends after this line. Signed-off-by: Firstname Lastname --- \*\*\*HERE\*\*\* you can write your comments. If this is a new version of an old patch, explain your changes here, for example: changes since v1: \* fixed an error in the new regex \* reworked algorithm to be O(n) src/PVE/Tools.pm | 2 +- diff --git a/src/PVE/Tools.pm b/src/PVE/Tools.pm (...) If you want to send several related patches for one feature but different repositories, you can first iterate over all involved repositories, save the patches into one directory and then do a single git send-email over all generated patches. For example, lets go to a few repos and format the most recent commit as patch to /tmp/patchq, then send it: \# cd pve-manager; git format-patch -s -o /tmp/patchq -1 # cd ../pve-guest-common; git format-patch -s -o /tmp/patchq -1 # cd ../pve-docs; git format-patch -s -o /tmp/patchq -1 # git send-email --compose --to=pve-devel@lists.proxmox.com /tmp/patchq/\* Using "start-number" and the like can improve this further, but it's a good start. ### Versioned Patches If an updated version of your patch series is called for, it should be sent as a new series rather than as reply to the old series. Always send the whole series with all patches showing the same version. Please mark your versions in your subject prefix with a small 'v' followed by the version number, git can do this for you using the `-vX` command line option. For example: \# git format-patch -s -o my-patches/ --subject-prefix="PATCH container" -v2 master..my\_branch Please **list all the changes to the previous versions** in the _commit summary_ section _as shown in the above example._ For patches with no changes to the previous version, you should mention that there were no changes in the summary section, like `no changes since last version` If your series has a cover letter, also summarize all changes in it as well. ### Reviewing patches After reviewing patches which affect a subsystem you maintain, you can notify committers that you reviewed the patch and are OK with the changes by using: Acked-by: Full Name ### Convenience Settings For convenience, you can store the pve-devel email address and the repository's default subject prefixes in your repository clones' configurations as follows: $ git config --local sendemail.to pve-devel@lists.proxmox.com $ git config --local format.subjectprefix 'PATCH container' $ git config --local format.signoff true Now the commands to create and send patches become: \# git format-patch -s -o my-patches/ master..my\_branch # git send-email --compose my-patches/00\*.patch Sending Patches --------------- Always use `git send-email` to send out patches, otherwise the indentation and formatting will get mangled, and the patch cannot be applied anymore. ### Tutorial See [https://git-send-email.io/](https://git-send-email.io/) for an interactive tutorial to setup `git send-email`. ### Using Authenticated SMTP Server `git send-email` can be instructed to use a specific SMTP server for sending, the following shows an anonymized config section example: \[sendemail\] smtpencryption=tls smtpserver=webmail.example.com smtpserverport=587 smtpuser=j.smith@example.com smtpsslcertpath= confirm = always Add this to your global user `~/.gitconfig` or to the per project `.git/config`. `git send-email` will then use these settings by default and ask you for the password on sending. ### Example To send the last two commits for a Proxmox VE project to the Proxmox VE development list you could then execute: git send-email --to="pve-devel@lists.proxmox.com" -2 If you're not used to `git send-email` it can be a good test to first send the patches to an email address of yourself, that allows to ensure all details and commands are correct. Bugtracker (bugzilla) --------------------- [https://bugzilla.proxmox.com](https://bugzilla.proxmox.com/) Software License and Copyright ------------------------------ We only include code licensed under the respective repo's license, visible under `debian/copyright`. For most of our projects, or if in doubt, this is the GNU Affero General Public License, version 3 [http://www.gnu.org/licenses/agpl-3.0.html](http://www.gnu.org/licenses/agpl-3.0.html) . Additionally, we require that contributors send us a contributor license agreement form by email to `office@proxmox.com`. This agreement establishes a relationship between us and the contributor, gives details on what it means when the contributor grants permission for their work to be included in a project, and enables us to be better stewards of these projects. With the contributor agreement chosen by Proxmox, the [Harmony CLA](http://www.harmonyagreements.org/) , the contributor gives Proxmox a license to use their contributions. The contributor continues to own the copyright in the contribution, with full rights to re-use, re-distribute, and continue modifying the contributed code, allowing them to also share that contribution with other projects. We've tried to keep the agreement as simple and comprehensible as possible. It comes in two flavors: * one for [individual contributors](https://www.proxmox.com/en/downloads/proxmox-virtual-environment/agreements/proxmox-individual-contributor-license-agreement) * and one for [entities contributors](https://www.proxmox.com/en/downloads/proxmox-virtual-environment/agreements/proxmox-entity-contributor-assignment-agreement) (companies, foundations, or other organizations). If you are making a contribution that is not your work (for example, a patch or library written by someone else), please contact office@proxmox.com for guidance on whether any additional steps are needed. See Also -------- * [Git Documentation](https://git-scm.com/documentation) * [Our Perl Style Guide](https://pve.proxmox.com/wiki/Perl_Style_Guide "Perl Style Guide") * [Our JavaScript Style Guide](https://pve.proxmox.com/wiki/Javascript_Style_Guide "Javascript Style Guide") Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Developer\_Documentation&oldid=12521](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Development](https://pve.proxmox.com/wiki/Category:Development "Category:Development") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Perl Style Guide - Proxmox VE Perl Style Guide ================ From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Perl_Style_Guide#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Perl_Style_Guide#searchInput) Contents -------- * [1 Proxmox Perl Style Guide](https://pve.proxmox.com/wiki/Perl_Style_Guide#Proxmox_Perl_Style_Guide) * [2 Module Dependencies](https://pve.proxmox.com/wiki/Perl_Style_Guide#Module_Dependencies) * [3 Modern Perl & Signatures](https://pve.proxmox.com/wiki/Perl_Style_Guide#Modern_Perl_&_Signatures) * [4 Prototypes](https://pve.proxmox.com/wiki/Perl_Style_Guide#Prototypes) * [5 Indentation & Format](https://pve.proxmox.com/wiki/Perl_Style_Guide#Indentation_&_Format) * [6 Casing](https://pve.proxmox.com/wiki/Perl_Style_Guide#Casing) * [7 Breaking long lines and strings](https://pve.proxmox.com/wiki/Perl_Style_Guide#Breaking_long_lines_and_strings) * [7.1 Wrapping Arguments](https://pve.proxmox.com/wiki/Perl_Style_Guide#Wrapping_Arguments) * [7.2 Wrapping Strings](https://pve.proxmox.com/wiki/Perl_Style_Guide#Wrapping_Strings) * [7.3 Wrapping Post-If](https://pve.proxmox.com/wiki/Perl_Style_Guide#Wrapping_Post-If) * [8 Spacing](https://pve.proxmox.com/wiki/Perl_Style_Guide#Spacing) * [9 Perl syntax choices](https://pve.proxmox.com/wiki/Perl_Style_Guide#Perl_syntax_choices) * [9.1 Blocks and multi-line statements](https://pve.proxmox.com/wiki/Perl_Style_Guide#Blocks_and_multi-line_statements) * [10 Comments](https://pve.proxmox.com/wiki/Perl_Style_Guide#Comments) * [11 Regular Expressions](https://pve.proxmox.com/wiki/Perl_Style_Guide#Regular_Expressions) * [11.1 Matching Digits Fallacy](https://pve.proxmox.com/wiki/Perl_Style_Guide#Matching_Digits_Fallacy) * [11.2 Non-Capturing Groups](https://pve.proxmox.com/wiki/Perl_Style_Guide#Non-Capturing_Groups) * [12 Basic Linting with perlcritic](https://pve.proxmox.com/wiki/Perl_Style_Guide#Basic_Linting_with_perlcritic) * [12.1 Installation](https://pve.proxmox.com/wiki/Perl_Style_Guide#Installation) * [12.2 Configuration](https://pve.proxmox.com/wiki/Perl_Style_Guide#Configuration) * [12.3 Usage](https://pve.proxmox.com/wiki/Perl_Style_Guide#Usage) Proxmox Perl Style Guide ------------------------ Since 2025 we rely on the `proxmox-perltidy` wrapper around perltidy to handle code formatting as automatically as possible to reduce bikeshedding and friction on review. This guide was written before the adoption of perltidy based code formatter. But as many of the guidelines here are not controlled by perltidy, you should strive to closely follow this guide if you're working on Perl code of Proxmox projects. Module Dependencies ------------------- We group our dependencies into the following 4 groups 1. (external) Perl modules 2. (common) modules from other PMG/PVE/Proxmox Debian packages 3. non-API modules from the same Debian package 4. API modules from the same package. Each group should be sorted alphabetically and separated by a single blank line. Modern Perl & Signatures ------------------------ For new modules we recommend you to use `use v5.36;`, which unlocks some modern Perl features and also implies `use warnings;` and `use strict;` as an added benefit. Using higher perl versions than v5.36 is not allowed, as we want to be able to backport fixes to older Proxmox releases. The most significant feature v5.36 unlocks are actual method [signatures](https://perldoc.perl.org/perlsub#Signatures) , as you might know them from other programming languages. With signatures, you can write method definitions like the following two variants: sub foo { my ($first, $second, $optional\_third) = @\_; $optional\_third = "default" if @\_ < 3; # fallback if there are less than three options passed. ... } in the following shorter way: sub foo ($first, $second, $optional\_third = "default") { ... } Note that all parameters that have no default need to be passed when calling the method, but using `undef` as default is valid for cases where there is no real fallback default value. See the perldocs for more information. We do not recommend switching existing code over to v5.36 just for the sake of it, but it can be done alongside a significant refactoring in the module, and is even recommended when splitting existing code out in new modules. The main rationale here is to avoid churn and introducing bugs due to wrong annotation caused by "busywork" while still being able to use modern features for new code. Note: With 5.36 one enables the bitwise features, which will cause breakage if you have bit-wise operations on strings (!) without using the string-specific operators. See [https://perldoc.perl.org/feature#The-'bitwise'-feature](https://perldoc.perl.org/feature#The-'bitwise'-feature) Prototypes ---------- [Prototypes](https://perldoc.perl.org/perlsub#Prototypes) are a very limited kind of compile-time argument checking. They have their place, and we strongly recommend using them when adding 1:1 wrappers for externally controlled interfaces (syscalls or other FFI) but otherwise recommend against using them if not 100% sure about the effects. Annotating existing non-private code with prototypes is almost never a good idea, doing so should be done only with a clearly stated reason and impact assessment of existing call sites. Indentation & Format -------------------- We indent by 4 spaces per indentation level. You must use the `proxmox-perltidy` tool from the package with the same name available through the Proxmox [developer package repository](https://pve.proxmox.com/wiki/Developer_Documentation#Development_Package_Repository "Developer Documentation") . `proxmox-perltidy` is a simple wrapper around `perltidy` that also ships a config to sets perltidy options to closely match our style guide as good as possible. Almost all repositories have a `tidy` make target at the top-level that will handle running `proxmox-perltidy`, but you can also simply run in manually and pass it a list of files to reformat. As most code formatters, perltidy does not touch string literals at all, you need to break them up manually to avoid overly long (>> 100 characters) lines and get some good format. See [#Breaking long lines and strings](https://pve.proxmox.com/wiki/Perl_Style_Guide#Breaking_long_lines_and_strings) . Casing ------ Use **PascalCase** for module names and **snake\_case** for variables and functions/methods. my $first\_line = PVE::SomeModule::get\_first\_line($argument\_one); Breaking long lines and strings ------------------------------- The preferred limit on the length of a single line is 100 columns. Statements longer than 80 columns may benefit readability if broken into sensible chunks, but often exceeding 80 columns avoids line-bloat or significantly increases readability while not hiding information. To show a vertical ruler directly after the maximum line width you can add `:set cc=101` to your vim configuration. For showing a additional ruler after 80 characters, use `:set cc=81,101`. See also Linus' mail on line-breaks: [https://lkml.org/lkml/2020/5/29/1038](https://lkml.org/lkml/2020/5/29/1038) ### Wrapping Arguments Once you need to wrap a function call, wrap each argument, including the first, on a separate line. Keep the trailing comma for the last argument too. An alternative inspired by rustfmt is to put all arguments and the closing parenthesis on the next line with one additional indentation. \# GOOD! Wrapped nicely, trailing commas added my $result = PVE::Some::Long::Module::Name::get\_foo\_bar\_baz( $argument\_one, $argument\_two, $argument\_three, ... $argument\_last, ); \# GOOD! Not too long, so there must not be any wrap my $result = PVE::Some::Long::Module::Name::short($a); \# GOOD! Intermediate step inspired by rustfmt PVE::Tools::foo( $bar, $baz, $very\_long\_argument\_bla\_bla); \# BAD! First argument needs to be on its own line my $result = PVE::Some::Long::Module::Name::get\_foo\_bar\_baz($argument\_one, $argument\_two, ... $argument\_last, ); \# BAD! Do not move indentation over to match opening line, but add a single level # (or 4 spaces, depending on how other code in the module handles this). my $result = PVE::Some::Long::Module::Name::get\_foo\_bar\_baz( $argument\_one, $argument\_two, ... $argument\_last); ### Wrapping Strings Continued lines for multi-line strings should be indented one level more than the first line. The dot for concatenation and the space separating words within the string should be at the beginning of each continued line. \# GOOD! Dot and space at the beginning, continuation indented once more description => "Enable backup fleecing. Cache backup data from blocks where new guest writes happen" . " on specified storage instead of copying them directly to the backup target. This can help" . " guest IO performance and even prevent hangs, at the cost of requiring more storage space.", \# BAD! Dot and space at the end description => "Enable backup fleecing. Cache backup data from blocks where new guest writes ". "happen on specified storage instead of copying them directly to the backup target. This can ". "help guest IO performance and even prevent hangs, at the cost of requiring more storage ". "space.", \# BAD! Do not move indentation over to match opening line, but add a single level description => "Enable backup fleecing. Cache backup data from blocks where new guest writes happen" . " on specified storage instead of copying them directly to the backup target. This" . " can help guest IO performance and even prevent hangs, at the cost of requiring" . " more storage space.", ### Wrapping Post-If post-if's allow concise error handling, so you can always assume that having only one line increases readability significantly. That means you can normally assume 100 columns as (preferred) text-width limit for post-if statements. If you need to wrap a line with a post-if always wrap the _whole_ `if EXPR` to a new line and indent with four (4) spaces. You must avoid using post-if if the whole post-if statement and the expression it guards spans more than two lines. \# GOOD: wrapped correctly $a\_longer\_variable\_name = $some\_hash->{value\_foo} if !defined($another\_variable\_name) && defined($some\_hash->{value\_foo}); \# GOOD: short enough, so one line it is $foo = $bar if defined($bar); \# BAD: once wrapping is required, the whole if condition needs to be ALWAYS on its own line $a\_longer\_variable\_name = $some\_hash->{value\_foo} if !defined($another\_variable\_name) && defined($some\_hash->{value\_foo}); \# BAD: wrap correctly but indentation is missing! $a\_longer\_variable\_name = $some\_hash->{value\_foo} if !defined($another\_variable\_name) && defined($some\_hash->{value\_foo}); If either side of the post-if has such a long expression where one would need to wrap that part too, strongly consider using a normal `if (EXPR) {` instead. In other words, a post-if should almost never be used if more than two lines are required to ensure the code uses not more than 100cc text-width. \# BAD: wrapping the actual post-if over multiple lines makes it very hard to read $a\_longer\_variable\_name = $some\_hash->{value\_foo} if !defined($another\_variable\_name) && defined($some\_hash->{value\_foo}) && $another\_condition && defined($yet\_another\_check); \# BAD: wrapping the guarded expression from a post-if over multiple lines makes it # very hard to read too $a\_longer\_variable\_name = "some longer text that results in overly long line: " . $some\_hash->{value\_foo} if !defined($another\_variable\_name); \# GOOD: use a "regular" if instead. Expression-wrapping is more flexible there, but # place the \`) {\` (closing \`)\` of \`if\` & start of block) on a separate line if wrapped if (!defined($another\_variable\_name) && defined($some\_hash->{value\_foo}) && $another\_condition && defined($yet\_another\_check) ) { $a\_longer\_variable\_name = $some\_hash->{value\_foo}; } \# GOOD: more fine-grained expression wrap is OK, can help readability # orient on surrounding code for what to use. Placing the logical # connectives in front is preferred. if ( !defined($another\_variable\_name) && defined($some\_hash->{value\_foo}) && $another\_condition && defined($yet\_another\_check) ) { $a\_longer\_variable\_name = $some\_hash->{value\_foo}; } Also remember that you must NOT use post if when declaring the variable for the first time with `my`! \# ERROR: declaration behind post-if is undefined and always a BUG! my $foo = $bar if defined($bar); # BAD!!! Spacing ------- Almost all spacing is correctly controlled through using the `proxmox-perltidy` tool for auto-formatting code. **Note**: This section is left over from previous times and thus collapsed by default, as not all can be done 1:1 with perltidy. Spaces around parenthesis with syntactical _words_ are inserted as you would in regular text (one before the opening parenthesis, one after the closing parenthesis). Similarly, for curly braces: * use `if (cond) {` * use `while (cond) {` * **not** `if(cond) {` * **not** `if (cond){` * **not** `if(cond){` **BUT:** no space between a _function_\`s name and its parameter list: * `func(params)` * **not** `func (params)` Use spaces around braces of lists: * use `my $list = [ 1, 2, 3 ];` * use `my $hash = { one => 1, two => 2 };` No spaces for unary operators or sigils which are directly connected to one another, or in array/hash accesses (here the contents of the brackets or curly braces represent content of the expression/variable to its left, so it makes sense to "group" them): * use `!$foo` * **not** `! $foo` * use `$foo->{text}` * use `$foo{text}` * use `$foo->[index]` * use `$foo[index]` * use `$foo->(index)` * **not** `&$foo(args)` * **not** `& $foo(args)` In general: use spaces in arithmetic expressions in a way which makes sense, eg. you can skip them on a short single binary operation, or if it helps reading the expression by grouping it so that the operator precedence is emphasized. Do not add spaces in a way which conflicts with the operators' precedences: * use `a + b` * **not** `a+b` * may use `a*3 + b*4` * **must not** use `a+3 * b+4` In if-else blocks any else or elsif should be on its own line together with its curly braces. \# Good if (expr) { code(); } else { code(); } # Bad if (expr) { code(); } else { code(); } # Bad if (expr) { code(); } else { code(); } Perl syntax choices ------------------- Most of these are chosen for semantic clarity and should make it easier to understand the code for people who don't use much Perl or simply aren't used to our code base: * use `$foo->(args)` instead of `&$foo(args)` * use `$foo->[subscript]` instead of `$$foo[subscript]` * use `$foo->{subscript}` instead of `$$foo{subscript}` When not accessing an element but simply dereferencing \*once\*, the dereferencing sigil can be put in front with braces, e.g. `${stuff}` or `@{stuff}`, provided `stuff` is easy enough to read. Otherwise, pull `stuff` out into a local variable first. * prefer `$foo = value if !defined($foo);` over `$foo //= value;` * use `if (!cond) {` over `unless (cond) {` * use `for` when looping over a list of elements over `foreach` * prefer `foo($a, $b);` over `foo $a, $b` Function calls should favor the use of parentheses. Omitting them is _only_ allowed in simple cases. foo($a, $b); # ok foo $a, $b; # okay, but discouraged print $a, $b; # okay, print is commonly used this way print($a, $b); # preferred delete $a->{b}; # okay, common my $var = delete($hash->{key}) // "default"; # ok my $var = delete $hash->{key} // "default"; # NOT ok! As a rule of thumb, when operators are involved, or when calling functions other than `print, map` or `grep`, always use parentheses for function calls. ### Blocks and multi-line statements While there certainly are way-too-long lines in our code already, please try to avoid adding more of them. Generally, when a line is long, try to split it up reasonably, and when there's a follow-up block or statement afterward (e.g. the contents of an `if` or `while`\-loop), please \*separate\* the block visually: sub foo { my ($arg1, $arg2, $arg3) = @\_; # Good: if ( defined($arg1->{foo}->{bar}) && $arg2 \* $arg1->{xzy} > $arg3->{baz} && $arg3->{more} ) { code(); } # Bad: (block not visually distinct from the code()) if ($arg1->{foo}->{bar} && $arg2 \* $arg1->{xzy} > $arg3->{baz} && $arg3->{more}) { code(); } # Good (enough): if ($arg1->{foo}->{bar} && $arg2 \* $arg1->{xzy} > $arg3->{baz} && $arg3->{more} ) { code(); } # Bad: (inconsistent '&&' placement) if ($arg1->{foo}->{bar} && $arg2 \* $arg1->{xzy} > $arg3->{baz} && $arg3->{more}) { code(); } } If a language permits leaving out braces for single statements in an `if` for example, \*do\* use braces when the condition spans multiple lines. Comments -------- Besides the fact that your comments should not explain what happens for a code hunk, but rather why it is the way it is, or why it even exists if one could question that, you should adhere to the following rules: * at least a single space after the initial comment hash symbol (#), more can be added for formatting purposes * try to stay below the 80 or 100 character per line length limit, whatever limit the surrounding codes uses * do not add newlines early, use the full width (80 to 100 cc) available * short comments can stay in the same line as the to-be-commented statement * try to keep comment and its related statement(s) together location-wise, so that it's clear what the comment target is. Regular Expressions ------------------- ### Matching Digits Fallacy For matching digits normally `\d` is used, but this has some implications which may not be expected. Namely, it matches all "Unicode Characters" (code points) from the '[Number, Decimal Digit](https://www.fileformat.info/info/unicode/category/Nd/list.htm) ' Category. If you think that this could have any implication on security or long term functionality then **do not use** `\d` but use the `[0-9]` character class. ### Non-Capturing Groups Normally you should use non-capturing groups `(?:)` as long as you do not need to use the value in parentheses. They can make the regex execution faster and simpler to understand. Basic Linting with perlcritic ----------------------------- You can use `perlcritic` to avoid some runtime errors and style issues, it's far from perfect or fixing the issues dynamic languages have in general, but it's also better than nothing by a lot. Note that when `perlcritic` outputs something like "See page 207 of PBP." it means Damian Conway's Perl Best Practice, an good reference in general. You may be able to obtain that book as PDF if you search a bit. ### Installation You can install it from the Debian package repositories: apt update apt install libperl-critic-perl libperl-critic-freenode-perl ### Configuration We target the highest severity level 5 only for now, albeit you can also try the level 4 to see if some other sensible style nits pop up, but that level may already get a bit noisy. Setup the following configuration in `~/.perlcriticrc` to fine tune the policies: severity = 5 \[TestingAndDebugging::RequireUseStrict\] severity = 5 \[TestingAndDebugging::RequireUseWarnings\] severity = 5 # we allow and use octals \[Perl::Critic::Policy::ValuesAndExpressions::ProhibitLeadingZeros\] severity = 2 # sub prototypes can be handy, even only sometimes \[Perl::Critic::Policy::Subroutines::ProhibitSubroutinePrototypes\] severity = 2 \[Perl::Critic::Policy::BuiltinFunctions::RequireGlobFunction\] severity = 2 \[Perl::Critic::Policy::Freenode::DollarAB\] severity = 2 # mostly for test, but also for very short module childs which live in the parent file \[Perl::Critic::Policy::Modules::RequireFilenameMatchesPackage\] severity = 4 # \`return undef;\` vs. \`return;\` - while the latter is tidier, it's not the highest severity! \[Perl::Critic::Policy::Subroutines::ProhibitExplicitReturnUndef\] severity = 4 \[Perl::Critic::Policy::InputOutput::ProhibitInteractiveTest\] severity = 4 \[Perl::Critic::Policy::Subroutines::RequireFinalReturn\] severity = 3 \[Perl::Critic::Policy::Variables::RequireLocalizedPunctuationVars\] severity = 3 \[Perl::Critic::Policy::ErrorHandling::RequireCheckingReturnValueOfEval\] severity = 2 \[Perl::Critic::Policy::RegularExpressions::RequireExtendedFormatting\] severity = 2 # Discouraged because "author refuses to use public bugtracking and actively breaks # interoperability". Proxmox VE uses the Debian package so the former reason is not fully relevant # and the latter means being careful about incompatible dependencies, but it's the better option # than rewriting the Proxmox VE code that depends on AnyEvent. \[Perl::Critic::Policy::Community::DiscouragedModules\] allowed\_modules = AnyEvent \[Perl::Critic::Policy::Freenode::DiscouragedModules\] allowed\_modules = AnyEvent ### Usage After installation and configuration you can use it by setting a directory or file as first argument, without that `perlcritic` waits on STDIN for code to check. perlcritic PVE/ You can also set another severity to check by passing `-X` where X is the integer level: perlcritic -4 PVE/ Note that `perlcritic` does not enforce strict linting checks, so a perl -wc PVE/File.pm would be still required for some other checks - in other words, those two tools complement each other. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Perl\_Style\_Guide&oldid=12388](https://pve.proxmox.com/mediawiki/index.php?title=Perl_Style_Guide&oldid=12388) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Development](https://pve.proxmox.com/wiki/Category:Development "Category:Development") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Javascript Style Guide - Proxmox VE Javascript Style Guide ====================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Javascript_Style_Guide#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Javascript_Style_Guide#searchInput) Contents -------- * [1 Proxmox Javascript Style Guide](https://pve.proxmox.com/wiki/Javascript_Style_Guide#Proxmox_Javascript_Style_Guide) * [2 Target Browsers](https://pve.proxmox.com/wiki/Javascript_Style_Guide#Target_Browsers) * [3 Target ECMAScript Version](https://pve.proxmox.com/wiki/Javascript_Style_Guide#Target_ECMAScript_Version) * [4 Indentation](https://pve.proxmox.com/wiki/Javascript_Style_Guide#Indentation) * [5 Variables](https://pve.proxmox.com/wiki/Javascript_Style_Guide#Variables) * [6 Spacing and Syntax Usage](https://pve.proxmox.com/wiki/Javascript_Style_Guide#Spacing_and_Syntax_Usage) * [7 Casing](https://pve.proxmox.com/wiki/Javascript_Style_Guide#Casing) * [8 Breaking long lines and strings](https://pve.proxmox.com/wiki/Javascript_Style_Guide#Breaking_long_lines_and_strings) * [9 Linting](https://pve.proxmox.com/wiki/Javascript_Style_Guide#Linting) * [9.1 Installation](https://pve.proxmox.com/wiki/Javascript_Style_Guide#Installation) * [9.2 Basic Usage](https://pve.proxmox.com/wiki/Javascript_Style_Guide#Basic_Usage) * [9.3 Buildsystem Integration](https://pve.proxmox.com/wiki/Javascript_Style_Guide#Buildsystem_Integration) * [9.4 Rule Information](https://pve.proxmox.com/wiki/Javascript_Style_Guide#Rule_Information) Proxmox Javascript Style Guide ------------------------------ Various of our files have inconsistent styles due to historical growth as well as because of the mixed styles we got from various contributors. Please try to follow this guide if you're working on code for Proxmox projects to avoid adding to the style mess. Here's a summary of our style (which is somewhat unusual at least when it comes to the mixed indentation). Target Browsers --------------- Proxmox web-interfaces try to support most widely used browsers in their current version, concretely: Chrome (Chromium), Firefox (also ESR), Safari, Edge. Browser-specific workarounds or features should be avoided, any exception will be decided on a case-by-case basis. Target ECMAScript Version ------------------------- | Debian Base Release | ECMAScript Version | | --- | --- | | <= 9 Stretch | ES5 | | 10 Buster | ES 2018 | | 11 Bullseye | ES 2020 | | 12 Bookworm | ES 2021 | | 13 Trixie | ES 2024 | See [https://compat-table.github.io/compat-table/es2016plus/](https://compat-table.github.io/compat-table/es2016plus/) for available features. Indentation ----------- We indent by 4 spaces, no tabs! In general you will not manually format the code, use the `make tidy` target or `proxmox-biome format --fix` or your editor's autoformatting if it supports calling proxmox-biome or use the biome configuration shipped by it's package under `/usr/share/proxmox-biome/biome.json`. Some example how the resulting code should look like: function foo (arg1, arg2, arg3) { if (arg1) { console.log(arg2); if (arg3) { if (arg3 !== arg2) { throw "Exceptions should avoid for dynamic stuff"; } } } } Variables --------- Code declaring new variables must **not** use `var`, but rather `let`, or if sensible `const`. If you touch old code please transform any line you change also from the old `var` declaration to the modern ones with less side effects (e.g., function scope). Avoid using `const` for everything, but rather in the sense of constants. JavaScript is too dynamic for it to provide actual benefits if used as default. An exception is copying over code from ExtJS to override a specific component, there you can keep _existing_ `var` usage so that the unmodified code stays closer to the original. Adding comments indicating boundaries between changed, and original code is recommended. Spacing and Syntax Usage ------------------------ Spaces around parenthesis with syntactical _words_ are inserted as you would in regular text (one before the opening parenthesis, one after the closing parenthesis). Similarly, for curly braces: * use `if (cond) {` * use `while (cond) {` * **not** `if(cond) {` * **not** `if (cond){` * **not** `if(cond){` Biome also insists on putting a space between a _function_\`s name and its parameter list, which we accept: * `func (params)` * **not** `func(params)` You can condense short comments on the if-statement's clause inner body line as long as text-width limits are upheld: if (cond) { // comment here that we early exit because XYZ return 42; // could be also comment here, depends on the comment reason } Casing ------ While there are quite some existing uses of snake\_case, you should **use camelCase** for (new) variable and function names. Breaking long lines and strings ------------------------------- The preferred limit on the length of a single line is 100 columns. Statements longer than 80 columns may benefit readability if broken into sensible chunks, but often exceeding 80 columns avoids line-bloat or significantly increases readability while not hiding information. The maximal line length tolerated for those exceptions is 100 columns. For vim, one can add `:set cc=101` or, to show both soft and hard limit: `:set cc=81,101` to one's configuration to show a vertical ruler that must not be "stepped on" for these boundaries. Linting ------- Instead of describing various rules and examples to follow the used coding and formatting style, it's quicker to just use `proxmox-biome`, which is a small wrapper around [biome](https://github.com/biomejs/biome) . ### Installation We provide a biome wrapper with our desired rule set backed in as default. You can install it easily after setting up the ['devel' package repository](https://pve.proxmox.com/wiki/Developer_Documentation#Development_Package_Repository "Developer Documentation") : apt update apt install proxmox-biome ### Basic Usage The `proxmox-biome` CLI tool provides various sub-commands, the most important ones are: `proxmox-biome lint`: for checking and optionally trying to fix code issues with syntax and style. `proxmox-biome format`: for checking and optionally fixing the source code format. `proxmox-biome check`: combines lint and format. Check formatting of specific file(s): proxmox-biome format src/Utils.js Reformat all JS/CSS file(s) in the current folder: `proxmox-biome format --fix .` Check linting rules including syntax and style issues of all .js files from this and child directories: proxmox-biome lint . A great deal of errors or warnings can be automatically fixed: proxmox-biome lint --fix . Combine format and linting: proxmox-biome check --fix . ### Buildsystem Integration All our JavaScript projects have a check rule that executes the linter on build automatically. But note that by default warnings are not treated as fatal, but our build system is made such that this will happen for Debian package builds, as those are intended for release. For such builds the `--error-on-warnings` option flag will be passed to biome. Most repos have a top-level `tidy` make target that can be used to reformat all relevant code files checked into git. ### Rule Information For errors and warnings biome will include a shorter rule ID in the longer human-readable error or warning message. You can use the rule ID to search the biome documentation, to get more information about a specific rule: [https://biomejs.dev/linter/javascript/rules/](https://biomejs.dev/linter/javascript/rules/) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Javascript\_Style\_Guide&oldid=12478](https://pve.proxmox.com/mediawiki/index.php?title=Javascript_Style_Guide&oldid=12478) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Development](https://pve.proxmox.com/wiki/Category:Development "Category:Development") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Technical Writing Style Guide - Proxmox VE Technical Writing Style Guide ============================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#searchInput) Consider these guidelines when writing technical documentation. This page will be in flux as requirements and situations change. Contents -------- * [1 Goals](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Goals) * [2 US or UK English?](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#US_or_UK_English?) * [3 Sentence Structure](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Sentence_Structure) * [3.1 Important information first](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Important_information_first) * [3.2 Sentence length](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Sentence_length) * [3.3 Transitions](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Transitions) * [3.4 Procedures](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Procedures) * [3.4.1 Format](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Format) * [3.4.2 Introductory sentence](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Introductory_sentence) * [3.4.3 Single-step procedure](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Single-step_procedure) * [3.4.4 Numbered procedures](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Numbered_procedures) * [3.4.5 More guidelines](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#More_guidelines) * [4 Concise Communication](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Concise_Communication) * [5 Use Active Voice](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Use_Active_Voice) * [6 Person and Mood](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Person_and_Mood) * [6.1 Third person indicative mood](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Third_person_indicative_mood) * [6.2 Second person imperative mood](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Second_person_imperative_mood) * [6.3 Avoid first person](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Avoid_first_person) * [7 Titles and Headlines](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Titles_and_Headlines) * [7.1 Title-style capitalization](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Title-style_capitalization) * [7.2 Sentence-style capitalization](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Sentence-style_capitalization) * [8 Punctuation](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Punctuation) * [8.1 Use a comma](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Use_a_comma) * [8.2 Don't use a comma](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Don't_use_a_comma) * [8.3 Slashes](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Slashes) * [8.4 Hyphens](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Hyphens) * [8.5 Em Dashes](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Em_Dashes) * [9 Lists](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Lists) * [10 Avoid Slang, Jargon, and Idioms](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Avoid_Slang,_Jargon,_and_Idioms) * [11 Consistency](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Consistency) * [12 Contractions](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Contractions) * [13 Abbreviations](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Abbreviations) * [13.1 e.g./i.e.](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#e.g./i.e.) * [14 Acronyms](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Acronyms) * [14.1 Special cases](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Special_cases) * [15 Examples](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Examples) * [16 Capitalization](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Capitalization) * [17 A/an](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#A/an) * [18 Industry Related Terms](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Industry_Related_Terms) * [19 Gender](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Gender) * [20 Data: singular or plural?](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Data:_singular_or_plural?) * [21 References](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#References) Goals ----- * Inform (educate) the user. * Write clearly, using words the audience understands. * Compose simple, active voice sentences. * Understand the audience and speak directly to the reader. * Determine if the text requires a change in grammatical person or past tense, future tense, and/or declarative mood. * Avoid unnecessary repetition, redundant jargon, and passive voice. * Evaluate your writing: write, review, and repeat. US or UK English? ----------------- We use US English. Center instead of centre. Color instead of colour. Behavior instead of behaviour. For more details and word lists you can search the web. Sentence Structure ------------------ ### Important information first Try to put the important information towards the beginning of the sentence. If possible, state the purpose of the action before stating the action, so the reader can skip the instruction if the purpose doesn't apply. Bad To enable quick and easy integration with third party tools and workflows Proxmox VE offers a RESTful API. Good Proxmox VE offers a RESTful API to enable quick and easy integration with third party tools and workflows. Bad Click Delete if you want to delete the entire document. Good To delete the entire document, click Delete. ### Sentence length Use short sentences. In general, an average of 15 to 20 words is effective for most technical communication. Long sentences tax the brain more and make it more difficult to write, read, and understand information. Sentence length affects the quality of the writing. Try to vary the length and beginnings of sentences to keep the reader focused. A sentence that list three or more items may work better as a bullet list. Test the readability of your text or highlight complex sentence structures with online tools, for example [https://www.hemingwayapp.com](https://www.hemingwayapp.com/) ### Transitions * Are words or phrases, sometimes whole paragraphs, that connect one idea together. * Use transitions to clarify the relationships between ideas. * Sometimes simply adding _for example_ or _in other words_ at the beginning of a sentence will improve the flow of ideas. | Uses | Transitions | | --- | --- | | To add to a previous point. | and, or, nor, furthermore, indeed, also, moreover, in fact, first, second, in addition | | To follow or precede an idea. | see Procedures... | | To illustrate or expand on a point | for instance, for example, for one thing, similarly, likewise | | To summarize or emphasize a point. | therefore, thus, so, and so, hence, consequently, on the whole, all in all, in other words, in short, in conclusion | | To qualify or illustrate a point | frequently, occasionally, in general, specifically, in particular, usually | | To shift to a different point of view or signal a contradiction. | but, however, yet, on the contrary, not at all, surely, no | | To make a concession. | although, though, whereas | | To connect an explanation to a statement. | because, as , since, for | | To qualify and restrict a more general idea. | if, provided, in case, unless, lest, when | ### Procedures A procedure is a sequence of numbered steps for accomplishing a task or a step-by-step instruction. #### Format * Consider a heading, so readers find instructions quickly. Choose same phrasing style for the headings. Example: "Closing the Program" * Each step specifies an action. It has to be clear and easy to follow. It should answer the question, "What should I do next?" with one meaningful action. * Use parallel structure. * Use imperative verb form (telling the reader what to do). | | Transitions for procedures | | --- | --- | | To follow or precede an idea. | first (second, third), then, next, after, before, since, as, when, while, subsequently, prior to, preceding this, previously, simultaneously, following, later, earlier, as soon as, during, until, once... | #### Introductory sentence You can introduce a procedure with an introductory sentence, providing additional context (without repeating the heading). Example: To do this with something, follow these steps: #### Single-step procedure Use a bullet if the procedure includes only one single step. Example Closing the Program * To close the program, choose Exit on the File menu. #### Numbered procedures Label sub-steps in a numbered procedure with lowercase letters, and sub-sub-steps with lowercase Roman numerals. 1\. First, do foo, as follows: a. Do the first part of foo. b. Do the second part of foo. There is no third part. i. Do the first sub-part of foo part two. ii. Do the second sub-part of foo part two. 2\. Next, do bar. #### More guidelines If the user must press _Enter_ after a step, then include that instruction as part of the step. Bad 1\. Click the search box, then type custom function. 2\. Press Enter. Good 1\. Click the search box, then type custom function and press Enter. State the purpose of the action before stating the action. Bad Click File > New > Document to start a new document. Good To start a new document, click File > New > Document. More details, see [http://www.webwritingthatworks.com/CPATTERNprocedures.htm](http://www.webwritingthatworks.com/CPATTERNprocedures.htm) or [https://developers.google.com/style/procedures](https://developers.google.com/style/procedures) Concise Communication --------------------- Technical writing is information delivery. Keep it simple and to the point. * Avoid elaborate prose. * Avoid padding. * Avoid pomp, use simple words. Most of our audience are non-native English speakers. * Avoid verbosity. Each word should contribute meaning to the sentence. Use Active Voice ---------------- Active voice clearly shows the actor in a situation. When we read active voice, we know who does what to whom. Active voice is shorter and more interesting to read. Active voice is the standard for technical writing. Active A. They speak English. Passive B. English was spoken. Passive voice obscures the _actor_—sometimes deliberately, as in, "Mistakes were made." Passive voice is ambiguous and often leaves out important information. Who made those mistakes? Passive The file is edited by the administrator. Active The administrator edits the file. You can identify the passive voice easily. Sentences that have the word "by" are almost always passive. Past-participle verbs ("was eaten", "is driven") are usually passive. You can often easily rework a passive sentence to turn it active. Just put the actor first. Passive This Wiki has been written by various authors. Mistakes were made. One must masticate thoroughly to ensure the burrito will have been eaten completely. Active Various authors wrote this Wiki. I made a mistake. Chew the burrito well. Person and Mood --------------- Depending on the kind of documentation (descriptions or instructions) it is best to use different persons/moods. * Third-person indicative mood (used in descriptions) * Second-person imperative mood (used to give instructions) * Avoid first person ### Third person indicative mood * Use this person/mood to write descriptions, to introduce a feature or a technology. * Use this mood whenever you are telling the reader about what happens, but not giving instructions. * The writer tells the reader about something but does not address the reader directly. Example A technician inserts the memory card into the card slot. Bad Don't use "one" as pronoun. This is UK English, and sounds too formal for US English. ### Second person imperative mood * Give instructions directly, if possible with imperative * Don't use modal verbs (should, could, might). * Use this person/mood to tell the reader directly to do something as if giving an order or instruction (in present tense). * It is OK to use the pronoun "you" in general description. It is by no means unprofessional. In fact, it helps you to write easier sentences. Which then simplifies comprehension for the reader. Example Insert the memory card into the card slot. To create a container... (is better than "You can create a container by...") Give instructions like: * do this * do that * use command xyz * click button ### Avoid first person * Never use first-person singular (I, me). * Try to avoid first-person plural (we) if possible. When writing about Proxmox (the company) or a project (Proxmox VE, Proxmox Backup) try to avoid the use of "we". Bad We implemented two virtualization technologies. Good Proxmox VE supports two virtualization technologies. Exception It's OK to use "we recommend" if the sentence would be too complicated otherwise. Titles and Headlines -------------------- For titles, first and second hierarchy headlines (1 & 1.1) use title-style capitalization. For all other hierarchies use sentence-style capitalization. ### Title-style capitalization * Always capitalize the first and last word. Example A Home to Go Back To * Don't capitalize a, an, or the unless it's the first word. Example Proxmox on the Issue * Don't capitalize prepositions of four or fewer letters (such as on, to, in, up, down, of, and for) unless the preposition is the first or last word. Example How to Install Proxmox VE * Don't capitalize and, but, or, nor, yet, or so unless it's the first word or the last word. Example Monitoring and Operating a Proxmox VE Cluster * Capitalize all other words, including nouns, verbs (including is and other forms of be), adverbs (including very and too), adjectives, and pronouns (including this, that, and its). Example Teaching Math Over and Over Again, in Less Time Than Before * Capitalize the second part of a hyphenated compound if it would be capitalized without the hyphen or it's the last word. Example Hyper-Converged Infrastructure * Capitalize the first word of labels and terms that appear in UI and APIs unless they're always lowercase (for example, "fdisk"). See also [https://titlecaseconverter.com/](https://titlecaseconverter.com/) ### Sentence-style capitalization Use sentence-style capitalization in most titles and headings: capitalize the first word and lowercase the rest. **Exceptions** Proper nouns, including brand, product, and service names, are always capitalized. If a title or heading includes a colon, capitalize the first word after it. Examples Watch your favorite HD movies, TV shows, and more 1 TB of cloud storage Choose the cluster size that is right for you Running a hyper-converged infrastructure with Proxmox VE Network: Setup and configuration Punctuation ----------- If a sentence contains more than a comma or two and ending punctuation, consider rewriting it to make it crisp and clear. ### Use a comma * Oxford (or serial) comma: Use Oxford commas for clarity, when separating items in a **list of three or more** items. Compare "We invited the dancers, John, and David." - In this case, John, David and the dancers were invited. "We invited the dancers, John and David." - Here, John and David are the names of the invited dancers. * Use a comma before any **coordinating conjunction** (and, but, for, or, nor, so, yet) that links two independent clauses. Example "I went running, and I saw a duck." - Two independent clauses because two times the subject "I". But "I went running and saw a duck." - Only one subject ("I") - no comma. * Following an **introductory phrase/introductory adverbs**. How to recognize an adverb: Many adverbs end in "ly" and answer the question "how?" (however, on the other hand, furthermore, meanwhile, suddenly). Example "With the app, you can call any phone." "Finally, I went running." * Use a comma after **sequence words**. Sequence words usually introduce a sentence. They are used in procedural texts to signal the order of steps. When we write sequence words like first, next, then, or last, we put a comma after those words. Example "First, pour milk into a bowl." "Then, add some freshly washed strawberries to the bowl." "After that, peel an apple and core it." * Use a comma **after a dependent clause** that starts a sentence (when, after, although, as, because, before, once, since, while). Example "When I went running, I saw a duck." * Use a comma **between two adjectives** that modify the same noun. Example "I saw the big, mean duck when I went running." ### Don't use a comma * To join independent clauses when you don't use a conjunction. (Use a semicolon instead.) Example "Select Options; then select Enable fast saves." * Between verbs in a compound predicate (when two verbs apply to a single subject). Example "The program evaluates your computer system and then copies the essential files to the target location." More details: [https://www.grammarly.com/blog/comma/](https://www.grammarly.com/blog/comma/) ### Slashes Use a forward slash to imply a combination. Capitalize the word after the slash if the word before the slash is capitalized. Example * client/server or Client/Server * TCP/IP Don't use a slash as a substitute for "or", like product/service. Use "or" to describe the action in text (product or service). ### Hyphens Hyphenate two or more words that precede and modify a noun as a unit if: * Confusion might result without the hyphen. Example read-only memory, built-in drive command-line vs. command line Two words as a noun. Hyphenate as an adjective, e.g. command-line tool, Linux command line (Source: [Microsoft style guide](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/c/command-line) ) * One of the words is a past or present participle (a verb form ending in -ed or -ing and used as an adjective or noun). Example left-aligned text, well-defined schema * The modifier is a number or single letter plus a noun or participle. Example two-sided arrow, 5-point star Hyphenate compound nouns when one of the words is abbreviated. Example e-book, e-commerce, e-bike But email ### Em Dashes Use an em dash (—) to set off a parenthetical phrase with more emphasis than parentheses provide. Don’t add spaces around an em dash. Example The information—numbers, configuration, and text—is stored in a container. Lists ----- By using bullet or numbered lists you can write in a concise and cut to the chase manner. In a list make every point essential and impactful. When to create a list: * If you find, within running text, three or more items in a row, pull them out of the paragraph and format them as a list. * Use a bullet list if the items are options, with no required order. * Use a numbered list if the user should perform or read the items in a specific order. * Keep it simple and short. * If items contain two parts, such as term and definition, boldface the first part, and plaintext the second part. * If items contain links and descriptions, put the link first, and indent the description underneath it. Do not mix and match. Keep the style within a list. Either full sentences with punctuation or phrases/fragments without punctuation. Use capitalization. Or at least keep your style consistent in a list/text. Example With punctuation: * If all bullets are full sentences - end each one with a period (full stop). * If all bullets are full sentences - end each one with a period (full stop). Without punctuation: * Bullets are phrases or fragments - no end punctuation * Bullets are phrases or fragments - no end punctuation Avoid Slang, Jargon, and Idioms ------------------------------- Don't use jargon, slang, and idioms if there is a more familiar term available. Example Symbol instead of glyph. Consistency ----------- Stick to one term if multiple are possible. Switching back and forth between multiple terms can confuse the reader. Add other possible terms the first time you use it. This helps users who search for another term. Example * USB flash drive * USB stick * USB media Use in a sentence A USB flash drive (USB stick) is the recommended way to install Proxmox VE. | | | | --- | --- |Table of used words | Instead of | Use | | mainboard, main board | motherboard | | USB/usb stick/drive, flash drive, thumb drive | USB flash drive | | Web UI, WebUI, webinterface | web interface, GUI, or web UI | Contractions ------------ Common contractions are okay to use like: * it’s * you’re * that's * don’t Do not use contractions with verbs and nouns. Bad Proxmox's the leading open-source virtualization company. Good Proxmox is the leading open-source virtualization company. Abbreviations ------------- Always avoid abbreviations out of laziness. Bad * 'approx.' for 'approximately' (better write 'about') * 'etc.' - etc. is often misused. Avoid it. Example for etc. Bad “He eats lots of fruit, such as apples, oranges, bananas, etc.” - The ‘etc.’ here is redundant because of the ‘such as’. Good If you are using ‘etc.’ then the correct way to write the above sentence would be: “He eats lots of fruit: apples, oranges, bananas, etc.” ### e.g./i.e. If possible, avoid using e.g., or i.e., in the Proxmox technical documentation. If you yourself have to look up what it means, also most other readers will not know what it means. Simply write * "for example" (e.g.,) or * "that is" (i.e.,). Or use alternative words for exemplification (illustration): as an illustration, especially, including, in detail, in other words, in particular, for example, for instance, namely, specifically, such as, to demonstrate, to explain, to illustrate Comma: If you have to use e.g./i.e, don't forget the comma at the end and use * "e.g.," as in "for example" and * "i.e.," as "in other words"/"that is". More detailed information can be found [here](https://www.grammarly.com/blog/know-your-latin-i-e-vs-e-g/) . Acronyms -------- When you use an acronym, spell it out the first time with the abbreviation in brackets. Do not use an acronym if you use it only once! Example Kernel Samepage Merging (KSM) Commonly known abbreviations can be used. For example: * USB * HTML * URL * FAQ ### Special cases Some commonly used abbreviations should be avoided. VM You can use the abbreviated VM... * if you explicitly refer to a UI item in a Proxmox solution. * if it's not mentioned in an introductory paragraph concerning VMs (for example explaining Qemu/KVM). CT You can use the abbreviated CT... * only if you explicitly refer to a UI item in a Proxmox solution. Otherwise, use "container". Guest If you're talking about both VMs and container, use "guest" or "virtual guest". PVE/PMG/PBS Should always be written as Proxmox VE/Proxmox Virtual Environment, Proxmox Mail Gateway, and Proxmox Backup Server in formal/public/marketing communication. If you're talking about one of our products, don't use 'Proxmox' alone, as it is our trademark/brand and could also just mean Proxmox, the company. It is not a product. Examples -------- Examples need to be clear, **correct** and **tested**. It is better to not have any examples than bad ones. Capitalization -------------- The basic rules of capitalization in English are quite simple: * Capitalize the first word of a sentence * Capitalize names and other proper nouns * Names are proper nouns. The names of cities, countries, companies, religions, and political parties are also proper nouns, so you should capitalize them, too. * You should also capitalize words like mom and grandpa when they are used as a form of address. * Capitalize days, months, and holidays, but not seasons * The names of days, months, and holidays are proper nouns, so you should capitalize them. * Capitalize cities, countries, nationalities, and languages * The names of cities, countries, nationalities, and languages are proper nouns, so you should capitalize them. A/an ---- Use 'an' with nouns that start with a vowel **sound** (a, e, i, o, u) and 'a' with nouns that start with a consonant sound (letters that are not vowels): * _A_ chair * _An_ apple * _A_ truck * _An_ orange * _A_ castle * _An_ opera * _A_ historical (_an_ historical is archaic and incorrect at least in the U.S.) * _A_ Media Gateway Controller * _An_ MGC (_M_ is pronounced _em_, so it is a vowel sound) NOTE _An_ before a silent _h_: an hour... _A_ before u and eu when they make a consonant _Y_ (sound like 'you') a European, a university, a unit The indefinite article: **refers to something for the first time:** An MGC is a "Media Gateway Controller." The MGC controls all activity on an IP phone network. Industry Related Terms ---------------------- Always use correct company and product names. Bad * ProxMox * Proxmox 3.4 (Which product do you mean? Proxmox is not a product) * HOWTO * html * openvz * centos * ceph * VMWARE * the Web * webUI Good * Proxmox Server Solutions GmbH * Proxmox VE * Proxmox Virtual Environment * Proxmox Mail Gateway * Proxmox Backup Server 3.1 * the web * a how-to (guide) * OpenVZ * CentOS * VMware * Ceph * Ceph Filesystem, Ceph Object Storage, Ceph Block Devices, Ceph Storage Cluster * 'web interface', web UI (space in-between), 'web-based user interface' or 'GUI' Gender ------ In technical writing, the gender-neutral pronouns, _they, them, or their,_ are preferable to the verbose _he or she/his or her/him or her_. If a sentence seems awkward, try to avoid the issue: leave out the pronoun or use second person imperative. Data: singular or plural? ------------------------- 'Data' is accepted both as a singular and a plural noun. While the plural form is more formal, we use it as a singular noun to stay consistent with existing Proxmox documentation. See [Merriam Webster](https://www.merriam-webster.com/dictionary/data) for a more in-depth explanation and examples. References ---------- This guide is loosely adapted from the following resources: * [Wikiversity - Technical writing style](https://en.wikiversity.org/wiki/Technical_writing_style) * [Microsoft Writing Style Guide](https://docs.microsoft.com/en-us/style-guide/welcome/) * [Grammarly capitalization rules](https://www.grammarly.com/blog/capitalization-rules/) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Technical\_Writing\_Style\_Guide&oldid=11882](https://pve.proxmox.com/mediawiki/index.php?title=Technical_Writing_Style_Guide&oldid=11882) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Development](https://pve.proxmox.com/wiki/Category:Development "Category:Development") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Get support - Proxmox VE Get support =========== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Get_support#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Get_support#searchInput) Proxmox VE Wiki --------------- The primary source of information is the [Proxmox VE Wiki](https://pve.proxmox.com/wiki/) . It combines the reference documentation with user contributed content. Community Support Forum ----------------------- Proxmox VE itself is fully open source, so we always encourage our users to discuss and share their knowledge using the [Proxmox VE Community Forum](https://forum.proxmox.com/) . The forum is moderated by the Proxmox support team, and has a large user base from all around the world. Needless to say, such a large forum is a great place to get information. Mailing Lists ------------- This is a fast way to communicate with the Proxmox VE community via email. * Mailing list for users: [Proxmox VE User List](http://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user) Proxmox VE is fully open source and contributions are welcome! The primary communication channel for developers is the: * Mailing list for developers: [Proxmox VE development discussion](http://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel) Commercial Support ------------------ Proxmox Server Solutions GmbH also offers enterprise support available as [Proxmox VE Subscription Service Plans](https://proxmox.com/en/proxmox-virtual-environment/pricing) . All users with a subscription get access to the Proxmox VE [Enterprise Repository](https://pve.proxmox.com/wiki/Package_Repositories#sysadmin_enterprise_repo) , and—with a Basic, Standard or Premium subscription—also to the Proxmox Customer Portal. The customer portal provides help and support with guaranteed response times from the Proxmox VE developers. For volume discounts, or more information in general, please contact [sales@proxmox.com](mailto:sales@proxmox.com) . Bug Tracker ----------- Proxmox runs a public bug tracker at [https://bugzilla.proxmox.com](https://bugzilla.proxmox.com/) . If an issue appears, file your report there. An issue can be a bug as well as a request for a new feature or enhancement. The bug tracker helps to keep track of the issue and will send a notification once it has been solved. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Get\_support&oldid=11961](https://pve.proxmox.com/mediawiki/index.php?title=Get_support&oldid=11961) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Developer Documentation" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Developer Documentation" ============================================ ← [Developer Documentation](https://pve.proxmox.com/wiki/Developer_Documentation "Developer Documentation") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Developer_Documentation#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Developer_Documentation#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Developer Documentation](https://pve.proxmox.com/wiki/Developer_Documentation "Developer Documentation") **: Displaying 7 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Developer_Documentation&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Developer_Documentation&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Developer_Documentation&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Developer_Documentation&limit=500) ) * [Main Page](https://pve.proxmox.com/wiki/Main_Page "Main Page") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Main+Page "Special:WhatLinksHere") ) * [Open Source](https://pve.proxmox.com/wiki/Open_Source "Open Source") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Open+Source "Special:WhatLinksHere") ) * [Translations](https://pve.proxmox.com/wiki/Translations "Translations") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Translations "Special:WhatLinksHere") ) * [Perl Style Guide](https://pve.proxmox.com/wiki/Perl_Style_Guide "Perl Style Guide") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Perl+Style+Guide "Special:WhatLinksHere") ) * [Javascript Style Guide](https://pve.proxmox.com/wiki/Javascript_Style_Guide "Javascript Style Guide") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Javascript+Style+Guide "Special:WhatLinksHere") ) * [Storage Plugin Development](https://pve.proxmox.com/wiki/Storage_Plugin_Development "Storage Plugin Development") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Storage+Plugin+Development "Special:WhatLinksHere") ) * [Storage Plugin Development: Writing a Storage Plugin for SSHFS](https://pve.proxmox.com/wiki/Storage_Plugin_Development:_Writing_a_Storage_Plugin_for_SSHFS "Storage Plugin Development: Writing a Storage Plugin for SSHFS") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Storage+Plugin+Development%3A+Writing+a+Storage+Plugin+for+SSHFS "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Developer_Documentation&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Developer_Documentation&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Developer_Documentation&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Developer_Documentation&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Developer\_Documentation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Developer_Documentation) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Developer Documentation - Proxmox VE Developer Documentation ======================= From Proxmox VE Revision as of 15:58, 17 March 2026 by [Thomas Lamprecht](https://pve.proxmox.com/wiki/User:Thomas_Lamprecht "User:Thomas Lamprecht") ([talk](https://pve.proxmox.com/wiki/User_talk:Thomas_Lamprecht "User talk:Thomas Lamprecht") | [contribs](https://pve.proxmox.com/wiki/Special:Contributions/Thomas_Lamprecht "Special:Contributions/Thomas Lamprecht") ) ([→Commits and Commit Messages](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Commits_and_Commit_Messages) : clarify that a literal diff2human-prose is not wanted, rather rationale and background.) ([diff](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&diff=prev&oldid=12521 "Developer Documentation") ) [← Older revision](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&direction=prev&oldid=12521 "Developer Documentation") | Latest revision (diff) | Newer revision → (diff) [Jump to navigation](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#mw-head) [Jump to search](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Introduction) * [2 Mailing List](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Mailing_List) * [2.1 Public Inbox](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Public_Inbox) * [3 Access to Code Repository (git)](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Access_to_Code_Repository_(git)) * [4 Build instructions](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Build_instructions) * [5 Development Package Repository](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Development_Package_Repository) * [5.1 For Proxmox VE 9 based on Debian 13 Trixie](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#For_Proxmox_VE_9_based_on_Debian_13_Trixie) * [5.2 For Proxmox VE 8 based on Debian 12 Bookworm](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#For_Proxmox_VE_8_based_on_Debian_12_Bookworm) * [6 Checking out a git repository](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Checking_out_a_git_repository) * [7 Working on the code](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Working_on_the_code) * [7.1 Coding guidelines](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Coding_guidelines) * [7.1.1 Perl](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Perl) * [7.1.2 Rust](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Rust) * [7.1.3 JavaScript](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#JavaScript) * [7.1.4 Documentation](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Documentation) * [7.2 Using git](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Using_git) * [7.2.1 Commits and Commit Messages](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Commits_and_Commit_Messages) * [8 Preparing Patches](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Preparing_Patches) * [8.1 Versioned Patches](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Versioned_Patches) * [8.2 Reviewing patches](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Reviewing_patches) * [8.3 Convenience Settings](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Convenience_Settings) * [9 Sending Patches](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Sending_Patches) * [9.1 Tutorial](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Tutorial) * [9.2 Using Authenticated SMTP Server](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Using_Authenticated_SMTP_Server) * [9.3 Example](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Example) * [10 Bugtracker (bugzilla)](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Bugtracker_(bugzilla)) * [11 Software License and Copyright](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Software_License_and_Copyright) * [12 See Also](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#See_Also) Introduction ------------ This wiki describes the higher level developer documentation for all Proxmox projects, including Proxmox VE, Proxmox Backup Server and Proxmox Mail Gateway and Proxmox Offline Mirror. Please coordinate your efforts with us before starting any development. It is important to have a common view of the problem and the corresponding solution – just to avoid duplicated or unnecessary efforts. We will only include software which matches our quality criteria. The source code repository is read only. To include some code, send it as patch (git diff) to the pve-devel mailing list. We will review your code and commit after a successful review (and possible corrections/additions). Mailing List ------------ This is the primary communication channel for developers, discussing new features and implementation details. If you are a developer, and you want to develop additional features, this is the place to start. Proxmox VE Development List: [https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel](https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel) Archive: [https://lists.proxmox.com/pipermail/pve-devel/](https://lists.proxmox.com/pipermail/pve-devel/) ### Public Inbox In addition to the native mailing list archive, Proxmox runs a Public Inbox instance at [lore.proxmox.com](https://lore.proxmox.com/) that archives and indexes all messages sent to all of our public mailing lists (`pve-devel`, `pbs-devel`, `pmg-devel`, `pve-user`). Public Inbox also provides a convenient and powerful search interface, see the [public-inbox help](https://lore.proxmox.com/pve-devel/_/text/help/) for an overview and the [official Public Inbox README](https://public-inbox.org/README.html) for more features. There are also tools that build on top of Public Inbox's features, such as [b4](https://b4.docs.kernel.org/en/latest/) , which can help to pull and review patches. Access to Code Repository (git) ------------------------------- [https://git.proxmox.com](https://git.proxmox.com/) Build instructions ------------------ You could find build instructions here : [https://git.proxmox.com/?p=pve-common.git;a=blob\_plain;f=README.dev;hb=HEAD](https://git.proxmox.com/?p=pve-common.git;a=blob_plain;f=README.dev;hb=HEAD) Development Package Repository ------------------------------ Some packages required for development can only be found in the _devel_ repository. While the headlines specifically mention Proxmox VE, these repos are used for all Proxmox project based on a the mentioned Debian release. ### For Proxmox VE 9 based on Debian 13 Trixie Create a new file at `/etc/apt/sources.list.d/proxmox.sources` with the following contents: Types: deb URIs: [http://download.proxmox.com/debian/devel/](http://download.proxmox.com/debian/devel/) Suites: trixie Components: main Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg Since Debian 13 "Trixie", the [DEB822](https://manpages.debian.org/trixie/dpkg-dev/deb822.5.en.html) format is preferred. ### For Proxmox VE 8 based on Debian 12 Bookworm Add the following to the `/etc/apt/sources.list` file: deb [http://download.proxmox.com/debian/devel/](http://download.proxmox.com/debian/devel/) bookworm main Checking out a git repository ----------------------------- To clone a repository run 'git clone' with the repository name prefixed with the common URL: git://git.proxmox.com/git/ \# git clone [git://git.proxmox.com/git/pve-manager.git](git://git.proxmox.com/git/pve-manager.git) To update an already cloned project to the current version use: \# git pull Working on the code ------------------- ### Coding guidelines The codebase mostly contains Perl and rust code for the backend, JavaScript for the user interface, and C for the Proxmox Cluster Filesystem and upstream projects like the Linux kernel or QEMU. The documentation for Proxmox VE is written in AsciiDoc, using the python implementation. #### Perl For Perl, we recommend having a look at our [**perl style guide**](https://pve.proxmox.com/wiki/Perl_Style_Guide "Perl Style Guide") . #### Rust For our Rust code we use `rustfmt` (e.g., through `cargo fmt`) with default settings. Compiler warnings must be avoided. Additionally, one might check lints reported by `cargo clippy`, but we do not accept mass fixing of those all over the place, such fixes are not always productive and can introduce actual subtle (logical) errors. #### JavaScript For JavaScript, we use `eslint` as separate package to check basic code standards. New contribution must not ensure that eslint doesn't output any warning or error. Check out [Javascript Style Guide](https://pve.proxmox.com/wiki/Javascript_Style_Guide "Javascript Style Guide") We use the ExtJS framework for the web UI Components, its API documentation can be found at [https://docs.sencha.com/extjs/7.0.0/](https://docs.sencha.com/extjs/7.0.0/) . #### Documentation Avoid overly long line. Use line-length from context, which is 80 character columns most of the time, try to stay below 100 as maximum. Adhere to our [Technical Writing Style Guide](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide "Technical Writing Style Guide") . To make references explicit for already existing sections, use the auto-generated reference to avoid breaking external deep links. For example, this was done with `[[_corosync_external_vote_support]]` in [this commit](https://git.proxmox.com/?p=pve-docs.git;a=commitdiff;h=ab83397071d2e315e6aab41c19b047b494eb4d26;hp=065e6a1cd5b94b05f8de74e00a33a2ef6dc1c653) . For new sections, anchors for references should be prefixed by the chapter name, for example `[[pvecm_cluster_requirements]]` in the `pvecm - Proxmox VE Cluster Manager` chapter. ### Using git If you are not familiar with git it could be worth to take a look at this interactive tutorial: [https://try.github.io](https://try.github.io/) and read a brief introduction chapter from the official git documentation: [https://git-scm.com/docs/gittutorial](https://git-scm.com/docs/gittutorial) to gain basic knowledge on it. First, configure your _real_ name and email address for git, if not done already: $ git config --global user.name "John Doe" $ git config --global user.email john@example.com This will be used to sign off commits as your work. It is recommended to start a feature branch before working on the code locally: \# git checkout -f -b my\_branch master After this you can start working on your improvements. You'll be able to compare your changes to the current PVE master branch easily with \# git diff master..my\_branch #### Commits and Commit Messages Then, make your commit (try to make small, but self-contained, commits) and include a sign-off line (-s). In general, commit messages should be written with the following style guide in mind: * Write your commit message in the imperative: "Fix bug" and not "Fixed bug" or "Fixes bug." This convention matches up with commit messages generated by commands like git merge and git revert. * Avoid using "we", as for readers it's unclear who is meant. * Make sure the **line-length** (text-width, column count) of the commit's message is **not longer than 72 characters**. Note, HTTPS links and git trailers (e.g., `Signed-off-by:`, `Reviewed-by:` or `Fixes:`) are an exception and must **not** be split over multiple lines. * Add your `Signed-off-by: Your Name ` trailer and also track trailers from other people, like `Suggested-by`, `Co-authored-by`, `Tested-by`, `Reviewed-by` Note: Trailers should be _[causally](https://en.wikipedia.org/wiki/Causality) ordered_. For instance, a `Suggested-by` should be listed _before_ a `Signed-off-by` (the suggestion _caused_ you to create the commit), a `Tested-by` _after_ a `Signed-off-by` (a commit is created before one is able to test it). * If the commit fixes a bug **start** with that information in this form: `fix #1234: summary here` If it implements a feature tracked on Bugzilla you can also use: `close #1234: summary here` albeit `fix #1234:` is more commonly used and also fine * Try to add a tag prefix to denote the subsystem you're (mainly) changing, if an obvious choice exists. * For example, if you changed the QEMU UI component in pve-manager, a possible tag could be `ui: qemu: rest of summary here` * Don't add tags for things that are already clear from context, for example, adding a `qemu` tag for a patch in the qemu-server repository has no use. * But, do **not** just paste the affected files, including (parts of the) path and maybe even the file ending, as tag! That has no use (already contained in diff stat) and just makes it harder to read. * Commit messages are intended for human readers and should therefore focus on providing a brief summary of the core semantic changes and the rationale behind them. * Ideally, the subject is worded such, that it can be copied directly into the `debian/changelog`, which is consumed by end users. * Most of the time it's best to avoid mentioning implementations details, like for example specific function or type names in verbatim as written in the programming language. An exception can be changes, that do not have any visible (semantic) effect for users, like pure refactoring (movement of code without changing its logic) or preparations, especially if they happen in pure library repos/crates. But even there one often benefits from a higher-level human-readable overview too. * Do not put in a literal description of the code diff, especially not for simpler changes. The commit message should not focus on the detailed what's done/changed but rather answer: * Why this was done otherwise previously (or why this was missing until now). * Why the new approach is better or necessary (e.g., a bug was found, requirements changed, a prerequisite was merged that enables this). * What the resulting effect is for users or developers (if not already obvious from the subject line). If there should be no visible/semantic change then explicitly stating so can also be good for non-trivial changes. You can always edit the commit message of the most recent commit using amend: \# git commit --amend If you work on a series you can use the git rebase command to re-order, drop, squash/fixup and edit both the whole commit or just rewording its message: git rebase -i --autosquash --autostash origin/master The `autostash` is not required, but convenient if there are still pending changes, it will stash before rebase starts and apply again after rebase is done. The `autosquash` is also not required, but very convenient to auto squash fixups (`git commit --fixup=`) made for older commits in a development series The following command will take all changes of tracked files and add it to the commit: \# git commit -s -a New files won't get added automatically. To do that, or to just add some changed files to a commit, use \# git add newfile1.pl file2.pl You can always look at what will get into commit with: \# git diff --staged Preparing Patches ----------------- ℹ️ **Note**: For all repositories where Proxmox is the upstream, and where not explicitly noted otherwise, a valid [CLA](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521#Software_License_and_Copyright) is required to include your changes Since we have several projects in our git repository and only one development mailing list, we ask you to clarify which repository your patches are meant for by specifying it in the subject prefix. Since some names are long it's fine if you shorten them (eg. remove the 'pve-' prefix). Creating the raw patch series, for instance for the pve-container package: \# rm -rf my-patches/ # to clean left-overs # git format-patch -s -o my-patches/ --subject-prefix="PATCH container" master..my\_branch --cover-letter Explain in the cover letter the aim of your patches: edit my-patches/0000-cover-letter.patch ℹ️ **Note**: Adding a cover letter is useful every time you send more than a single patch. It makes it easier for tools like `b4` to assign additional git trailers to commits when applying them. The diffstat over all changes is also useful to gauge the impact of the patches. Sending patches: \# git send-email --to=pve-devel@lists.proxmox.com my-patches/00\*.patch # rm -rf my-patches/ # to clean left-overs If you wish to write comments for individual patches, you can do that either in the cover-letter, or in the patch's _commit summary section_ (between the line consisting of 3 consecutive dashes ending your commit message and before the list of files with their change-counts. Example: From 12345abcde Mon Sep 12 00:00:00 2001 From: Git Committer Date: Fri, 7 Oct 2016 08:30:17 +0200 Subject: \[PATCH v2 container 1/2\] Fix #1013: this and that Here is your commit message. It explains the bugfix and ends after this line. Signed-off-by: Firstname Lastname --- \*\*\*HERE\*\*\* you can write your comments. If this is a new version of an old patch, explain your changes here, for example: changes since v1: \* fixed an error in the new regex \* reworked algorithm to be O(n) src/PVE/Tools.pm | 2 +- diff --git a/src/PVE/Tools.pm b/src/PVE/Tools.pm (...) If you want to send several related patches for one feature but different repositories, you can first iterate over all involved repositories, save the patches into one directory and then do a single git send-email over all generated patches. For example, lets go to a few repos and format the most recent commit as patch to /tmp/patchq, then send it: \# cd pve-manager; git format-patch -s -o /tmp/patchq -1 # cd ../pve-guest-common; git format-patch -s -o /tmp/patchq -1 # cd ../pve-docs; git format-patch -s -o /tmp/patchq -1 # git send-email --compose --to=pve-devel@lists.proxmox.com /tmp/patchq/\* Using "start-number" and the like can improve this further, but it's a good start. ### Versioned Patches If an updated version of your patch series is called for, it should be sent as a new series rather than as reply to the old series. Always send the whole series with all patches showing the same version. Please mark your versions in your subject prefix with a small 'v' followed by the version number, git can do this for you using the `-vX` command line option. For example: \# git format-patch -s -o my-patches/ --subject-prefix="PATCH container" -v2 master..my\_branch Please **list all the changes to the previous versions** in the _commit summary_ section _as shown in the above example._ For patches with no changes to the previous version, you should mention that there were no changes in the summary section, like `no changes since last version` If your series has a cover letter, also summarize all changes in it as well. ### Reviewing patches After reviewing patches which affect a subsystem you maintain, you can notify committers that you reviewed the patch and are OK with the changes by using: Acked-by: Full Name ### Convenience Settings For convenience, you can store the pve-devel email address and the repository's default subject prefixes in your repository clones' configurations as follows: $ git config --local sendemail.to pve-devel@lists.proxmox.com $ git config --local format.subjectprefix 'PATCH container' $ git config --local format.signoff true Now the commands to create and send patches become: \# git format-patch -s -o my-patches/ master..my\_branch # git send-email --compose my-patches/00\*.patch Sending Patches --------------- Always use `git send-email` to send out patches, otherwise the indentation and formatting will get mangled, and the patch cannot be applied anymore. ### Tutorial See [https://git-send-email.io/](https://git-send-email.io/) for an interactive tutorial to setup `git send-email`. ### Using Authenticated SMTP Server `git send-email` can be instructed to use a specific SMTP server for sending, the following shows an anonymized config section example: \[sendemail\] smtpencryption=tls smtpserver=webmail.example.com smtpserverport=587 smtpuser=j.smith@example.com smtpsslcertpath= confirm = always Add this to your global user `~/.gitconfig` or to the per project `.git/config`. `git send-email` will then use these settings by default and ask you for the password on sending. ### Example To send the last two commits for a Proxmox VE project to the Proxmox VE development list you could then execute: git send-email --to="pve-devel@lists.proxmox.com" -2 If you're not used to `git send-email` it can be a good test to first send the patches to an email address of yourself, that allows to ensure all details and commands are correct. Bugtracker (bugzilla) --------------------- [https://bugzilla.proxmox.com](https://bugzilla.proxmox.com/) Software License and Copyright ------------------------------ We only include code licensed under the respective repo's license, visible under `debian/copyright`. For most of our projects, or if in doubt, this is the GNU Affero General Public License, version 3 [http://www.gnu.org/licenses/agpl-3.0.html](http://www.gnu.org/licenses/agpl-3.0.html) . Additionally, we require that contributors send us a contributor license agreement form by email to `office@proxmox.com`. This agreement establishes a relationship between us and the contributor, gives details on what it means when the contributor grants permission for their work to be included in a project, and enables us to be better stewards of these projects. With the contributor agreement chosen by Proxmox, the [Harmony CLA](http://www.harmonyagreements.org/) , the contributor gives Proxmox a license to use their contributions. The contributor continues to own the copyright in the contribution, with full rights to re-use, re-distribute, and continue modifying the contributed code, allowing them to also share that contribution with other projects. We've tried to keep the agreement as simple and comprehensible as possible. It comes in two flavors: * one for [individual contributors](https://www.proxmox.com/en/downloads/proxmox-virtual-environment/agreements/proxmox-individual-contributor-license-agreement) * and one for [entities contributors](https://www.proxmox.com/en/downloads/proxmox-virtual-environment/agreements/proxmox-entity-contributor-assignment-agreement) (companies, foundations, or other organizations). If you are making a contribution that is not your work (for example, a patch or library written by someone else), please contact office@proxmox.com for guidance on whether any additional steps are needed. See Also -------- * [Git Documentation](https://git-scm.com/documentation) * [Our Perl Style Guide](https://pve.proxmox.com/wiki/Perl_Style_Guide "Perl Style Guide") * [Our JavaScript Style Guide](https://pve.proxmox.com/wiki/Javascript_Style_Guide "Javascript Style Guide") Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Developer\_Documentation&oldid=12521](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12521) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Development](https://pve.proxmox.com/wiki/Category:Development "Category:Development") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Category:Development - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Categories) Category:Development ==================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Category:Development#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Category:Development#searchInput) Pages in category "Development" ------------------------------- The following 7 pages are in this category, out of 7 total. ### D * [Developer Documentation](https://pve.proxmox.com/wiki/Developer_Documentation "Developer Documentation") ### J * [Javascript Style Guide](https://pve.proxmox.com/wiki/Javascript_Style_Guide "Javascript Style Guide") ### P * [Perl Style Guide](https://pve.proxmox.com/wiki/Perl_Style_Guide "Perl Style Guide") ### S * [Storage Plugin Development](https://pve.proxmox.com/wiki/Storage_Plugin_Development "Storage Plugin Development") * [Storage Plugin Development: Writing a Storage Plugin for SSHFS](https://pve.proxmox.com/wiki/Storage_Plugin_Development:_Writing_a_Storage_Plugin_for_SSHFS "Storage Plugin Development: Writing a Storage Plugin for SSHFS") ### T * [Technical Writing Style Guide](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide "Technical Writing Style Guide") * [Third Party Integration Options](https://pve.proxmox.com/wiki/Third_Party_Integration_Options "Third Party Integration Options") Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Category:Development&oldid=11561](https://pve.proxmox.com/mediawiki/index.php?title=Category:Development&oldid=11561) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # FAQ - Proxmox VE FAQ === From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/FAQ#mw-head) [Jump to search](https://pve.proxmox.com/wiki/FAQ#searchInput) | | | | --- | --- | | ![Note]() | New FAQs are appended to the bottom of this section. | 1. _What distribution is Proxmox VE based on?_ Proxmox VE is based on [Debian GNU/Linux](https://www.debian.org/) 2. _What license does the Proxmox VE project use?_ Proxmox VE code is licensed under the GNU Affero General Public License, version 3. 3. _Will Proxmox VE run on a 32bit processor?_ Proxmox VE works only on 64-bit CPUs (AMD or Intel). There is no plan for 32-bit for the platform. | | | | --- | --- | | ![Note]() | VMs and Containers can be both 32-bit and 64-bit. | 4. _Does my CPU support virtualization?_ To check if your CPU is virtualization compatible, check for the vmx or svm tag in this command output: egrep '(vmx|svm)' /proc/cpuinfo 5. _Supported Intel CPUs_ 64-bit processors with [Intel Virtualization Technology (Intel VT-x)](https://en.wikipedia.org/wiki/Virtualization_Technology#Intel_virtualization_.28VT-x.29) support. ([List of processors with Intel VT and 64-bit](https://ark.intel.com/content/www/us/en/ark/search/featurefilter.html?productType=873&2_VTX=True&2_InstructionSet=64-bit) ) 6. _Supported AMD CPUs_ 64-bit processors with [AMD Virtualization Technology (AMD-V)](https://en.wikipedia.org/wiki/Virtualization_Technology#AMD_virtualization_.28AMD-V.29) support. 7. _What is a container/virtual environment (VE)/virtual private server (VPS)?_ In the context of containers, these terms all refer to the concept of operating-system-level virtualization. Operating-system-level virtualization is a method of virtualization, in which the kernel of an operating system allows for multiple isolated instances, that all share the kernel. When referring to LXC, we call such instances containers. Because containers use the host’s kernel rather than emulating a full operating system, they require less overhead, but are limited to Linux guests. 8. _What is a QEMU/KVM guest (or VM)?_ A QEMU/KVM guest (or VM) is a guest system running virtualized under Proxmox VE using QEMU and the Linux KVM kernel module. 9. _What is QEMU?_ QEMU is a generic and open source machine emulator and virtualizer. QEMU uses the Linux KVM kernel module to achieve near native performance by executing the guest code directly on the host CPU. It is not limited to Linux guests but allows arbitrary operating systems to run. 10. _How long will my Proxmox VE version be supported?_ Proxmox VE versions are supported at least as long as the corresponding Debian version, i.e. approximately 3 years after its initial release, see [Debian lifespan](https://www.debian.org/security/faq#lifespan) . Proxmox VE uses a rolling release model and using the latest stable version is always recommended. | Proxmox VE Version | Debian Version | First Release | Debian EOL | Proxmox EOL | | --- | --- | --- | --- | --- | | Proxmox VE 9 | Debian 13 (Trixie) | 2025-08 | tba | tba | | Proxmox VE 8 | Debian 12 (Bookworm) | 2023-06 | 2026-08 | 2026-08 | | Proxmox VE 7 | Debian 11 (Bullseye) | 2021-07 | 2024-07 | 2024-07 | | Proxmox VE 6 | Debian 10 (Buster) | 2019-07 | 2022-09 | 2022-09 | | Proxmox VE 5 | Debian 9 (Stretch) | 2017-07 | 2020-07 | 2020-07 | | Proxmox VE 4 | Debian 8 (Jessie) | 2015-10 | 2018-06 | 2018-06 | | Proxmox VE 3 | Debian 7 (Wheezy) | 2013-05 | 2016-04 | 2017-02 | | Proxmox VE 2 | Debian 6 (Squeeze) | 2012-04 | 2014-05 | 2014-05 | | Proxmox VE 1 | Debian 5 (Lenny) | 2008-10 | 2012-03 | 2013-01 | 11. _How can I upgrade Proxmox VE to the next point release?_ Minor version upgrades, for example upgrading from Proxmox VE in version 8.1 to 8.2 or 8.3, can be done just like any normal update. But you should still check the [release notes](https://pve.proxmox.com/wiki/Roadmap) for any relevant notable, or breaking change. For the update itself use either the Web UI _Node → Updates_ panel or through the CLI with: apt update apt full-upgrade | | | | --- | --- | | ![Note]() | Always ensure you correctly setup the [package repositories](https://pve.proxmox.com/wiki/Package_Repositories#sysadmin_package_repositories)
and only continue with the actual upgrade if apt update did not hit any error. | 12. _How can I upgrade Proxmox VE to the next major release?_ Major version upgrades, for example going from Proxmox VE 8.4 to 9.0, are also supported. They must be carefully planned and tested and should **never** be started without having a current backup ready. Although the specific upgrade steps depend on your respective setup, we provide general instructions and advice on how an upgrade should be performed: * [Upgrade from Proxmox VE 8 to 9](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9) * [Upgrade from Proxmox VE 7 to 8](https://pve.proxmox.com/wiki/Upgrade_from_7_to_8) * [Upgrade from Proxmox VE 6 to 7](https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0) * [Upgrade from Proxmox VE 5 to 6](https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0) * [Upgrade from Proxmox VE 4 to 5](https://pve.proxmox.com/wiki/Upgrade_from_4.x_to_5.0) * [Upgrade from Proxmox VE 3 to 4](https://pve.proxmox.com/wiki/Upgrade_from_3.x_to_4.0) 13. _LXC vs LXD vs Proxmox Containers vs Docker_ LXC is a userspace interface for the Linux kernel containment features. Through a powerful API and simple tools, it lets Linux users easily create and manage system containers. LXC, as well as the former OpenVZ, aims at **system virtualization**. Thus, it allows you to run a complete OS inside a container, where you log in using ssh, add users, run apache, etc… LXD is built on top of LXC to provide a new, better user experience. Under the hood, LXD uses LXC through liblxc and its Go binding to create and manage the containers. It’s basically an alternative to LXC’s tools and distribution template system with the added features that come from being controllable over the network. Proxmox Containers are how we refer to containers that are created and managed using the Proxmox Container Toolkit (pct). They also target **system virtualization** and use LXC as the basis of the container offering. With the addition of OCI image support (technology preview), Proxmox VE can also create containers from OCI images, including full system containers but also application containers (tech preview). The Proxmox Container Toolkit (pct) is tightly coupled with Proxmox VE. This means that it is aware of cluster setups, and it can use the same network and storage resources as QEMU virtual machines (VMs). You can even use the Proxmox VE firewall, create and restore backups, or manage containers using the HA framework. Everything can be controlled over the network using the Proxmox VE API. Docker aims at running a **single** application in an isolated, self-contained environment. These are generally referred to as “Application Containers”, rather than “System Containers”. You manage a Docker instance from the host, using the Docker Engine command-line interface. It is not recommended to run docker directly on your Proxmox VE host. | | | | --- | --- | | ![Note]() | While it can be convenient to run “Application Containers” directly as Proxmox Containers, doing so is currently a tech preview. For use cases requiring container orchestration or live migration, it is still recommended to run them inside a Proxmox QEMU virtual machine. | Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=FAQ&oldid=12409](https://pve.proxmox.com/mediawiki/index.php?title=FAQ&oldid=12409) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Reference Documentation](https://pve.proxmox.com/wiki/Category:Reference_Documentation "Category:Reference Documentation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Installation - Proxmox VE Installation ============ From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Installation#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Installation#searchInput) Proxmox VE is based on Debian. This is why the install disk images (ISO files) provided by Proxmox include a complete Debian system as well as all necessary Proxmox VE packages. | | | | --- | --- | | ![Tip]() | See the [support table in the FAQ](https://pve.proxmox.com/wiki/FAQ#faq-support-table)
for the relationship between Proxmox VE releases and Debian releases. | The installer will guide you through the setup, allowing you to partition the local disk(s), apply basic system configurations (for example, timezone, language, network) and install all required packages. This process should not take more than a few minutes. Installing with the provided ISO is the recommended method for new and existing users. Alternatively, Proxmox VE can be installed on top of an existing Debian system. This option is only recommended for advanced users because detailed knowledge about Proxmox VE is required. Using the Proxmox VE Installer ------------------------------ The installer ISO image includes the following: * Complete operating system (Debian Linux, 64-bit) * The Proxmox VE installer, which partitions the local disk(s) with ext4, XFS, BTRFS (technology preview), or ZFS and installs the operating system * Proxmox VE Linux kernel with KVM and LXC support * Complete toolset for administering virtual machines, containers, the host system, clusters and all necessary resources * Web-based management interface | | | | --- | --- | | ![Note]() | All existing data on the selected drives will be removed during the installation process. The installer does not add boot menu entries for other operating systems. | Please insert the [prepared installation media](https://pve.proxmox.com/wiki/Prepare_Installation_Media#installation_prepare_media) (for example, USB flash drive or CD-ROM) and boot from it. | | | | --- | --- | | ![Tip]() | Make sure that booting from the installation medium (for example, USB) is enabled in your server’s firmware settings. Secure boot needs to be disabled when booting an installer prior to Proxmox VE version 8.1. | [![screenshot/pve-grub-menu.png](https://pve.proxmox.com/pve-docs/images/screenshot/pve-grub-menu.png)](https://pve.proxmox.com/pve-docs/images/screenshot/pve-grub-menu.png) After choosing the correct entry (for example, _Boot from USB_) the Proxmox VE menu will be displayed, and one of the following options can be selected: Install Proxmox VE (Graphical) Starts the normal installation. | | | | --- | --- | | ![Tip]() | It’s possible to use the installation wizard with a keyboard only. Buttons can be clicked by pressing the ALT key combined with the underlined character from the respective button. For example, ALT + N to press a Next button. | Install Proxmox VE (Terminal UI) Starts the terminal-mode installation wizard. It provides the same overall installation experience as the graphical installer, but has generally better compatibility with very old and very new hardware. Install Proxmox VE (Terminal UI, Serial Console) Starts the terminal-mode installation wizard, additionally setting up the Linux kernel to use the (first) serial port of the machine for in- and output. This can be used if the machine is completely headless and only has a serial console available. [![screenshot/pve-tui-installer.png](https://pve.proxmox.com/pve-docs/images/screenshot/pve-tui-installer.png)](https://pve.proxmox.com/pve-docs/images/screenshot/pve-tui-installer.png) Both modes use the same code base for the actual installation process to benefit from more than a decade of bug fixes and ensure feature parity. | | | | --- | --- | | ![Tip]() | The _Terminal UI_ option can be used in case the graphical installer does not work correctly, due to e.g. driver issues. See also [adding the nomodeset kernel parameter](https://pve.proxmox.com/wiki/Installation#nomodeset_kernel_param)
. | Advanced Options: Install Proxmox VE (Graphical, Debug Mode) Starts the installation in debug mode. A console will be opened at several installation steps. This helps to debug the situation if something goes wrong. To exit a debug console, press CTRL-D. This option can be used to boot a live system with all basic tools available. You can use it, for example, to [repair a degraded ZFS _rpool_](https://pve.proxmox.com/wiki/ZFS_on_Linux#chapter_zfs) or fix the [bootloader](https://pve.proxmox.com/wiki/Host_Bootloader#sysboot) for an existing Proxmox VE setup. Advanced Options: Install Proxmox VE (Terminal UI, Debug Mode) Same as the graphical debug mode, but preparing the system to run the terminal-based installer instead. Advanced Options: Install Proxmox VE (Serial Console Debug Mode) Same the terminal-based debug mode, but additionally sets up the Linux kernel to use the (first) serial port of the machine for in- and output. Advanced Options: Install Proxmox VE (Automated) Starts the installer in unattended mode, even if the ISO has not been appropriately prepared for an automated installation. This option can be used to gather hardware details or might be useful to debug an automated installation setup. See [Unattended Installation](https://pve.proxmox.com/wiki/Installation#installation_unattended) for more information. Advanced Options: Rescue Boot With this option you can boot an existing installation. It searches all attached hard disks. If it finds an existing installation, it boots directly into that disk using the Linux kernel from the ISO. This can be useful if there are problems with the bootloader (GRUB/systemd-boot) or the BIOS/UEFI is unable to read the boot block from the disk. Advanced Options: Test Memory (memtest86+) Runs memtest86+. This is useful to check if the memory is functional and free of errors. Secure Boot must be turned off in the UEFI firmware setup utility to run this option. You normally select **Install Proxmox VE (Graphical)** to start the installation. [![screenshot/pve-select-target-disk.png](https://pve.proxmox.com/pve-docs/images/screenshot/pve-select-target-disk.png)](https://pve.proxmox.com/pve-docs/images/screenshot/pve-select-target-disk.png) The first step is to read our EULA (End User License Agreement). Following this, you can select the target hard disk(s) for the installation. | | | | --- | --- | | ![Caution]() | By default, the whole server is used and all existing data is removed. Make sure there is no important data on the server before proceeding with the installation. | The Options button lets you select the target file system, which defaults to ext4. The installer uses LVM if you select ext4 or xfs as a file system, and offers additional options to restrict LVM space (see [below](https://pve.proxmox.com/wiki/Installation#advanced_lvm_options) ). Proxmox VE can also be installed on ZFS. As ZFS offers several software RAID levels, this is an option for systems that don’t have a hardware RAID controller. The target disks must be selected in the Options dialog. More ZFS specific settings can be changed under [Advanced Options](https://pve.proxmox.com/wiki/Installation#advanced_zfs_options) . | | | | --- | --- | | ![Warning]() | ZFS on top of any hardware RAID is not supported and can result in data loss. | [![screenshot/pve-select-location.png](https://pve.proxmox.com/pve-docs/images/screenshot/pve-select-location.png)](https://pve.proxmox.com/pve-docs/images/screenshot/pve-select-location.png) The next page asks for basic configuration options like your location, time zone, and keyboard layout. The location is used to select a nearby download server, in order to increase the speed of updates. The installer is usually able to auto-detect these settings, so you only need to change them in rare situations when auto-detection fails, or when you want to use a keyboard layout not commonly used in your country. [![screenshot/pve-set-password.png](https://pve.proxmox.com/pve-docs/images/screenshot/pve-set-password.png)](https://pve.proxmox.com/pve-docs/images/screenshot/pve-set-password.png) Next the password of the superuser (root) and an email address needs to be specified. The password must consist of at least 8 characters. It’s highly recommended to use a stronger password. Some guidelines are: * Use a minimum password length of at least 12 characters. * Include lowercase and uppercase alphabetic characters, numbers, and symbols. * Avoid character repetition, keyboard patterns, common dictionary words, letter or number sequences, usernames, relative or pet names, romantic links (current or past), and biographical information (for example ID numbers, ancestors' names or dates). The email address is used to send notifications to the system administrator. For example: * Information about available package updates. * Error messages from periodic _cron_ jobs. [![screenshot/pve-setup-network.png](https://pve.proxmox.com/pve-docs/images/screenshot/pve-setup-network.png)](https://pve.proxmox.com/pve-docs/images/screenshot/pve-setup-network.png) All those notification mails will be sent to the specified email address. The last step is the network configuration. Network interfaces that are _UP_ show a filled circle in front of their name in the drop down menu. Please note that during installation you can either specify an IPv4 or IPv6 address, but not both. To configure a dual stack node, add additional IP addresses after the installation. [![screenshot/pve-installation.png](https://pve.proxmox.com/pve-docs/images/screenshot/pve-installation.png)](https://pve.proxmox.com/pve-docs/images/screenshot/pve-installation.png) The next step shows a summary of the previously selected options. Please re-check every setting and use the Previous button if a setting needs to be changed. After clicking Install, the installer will begin to format the disks and copy packages to the target disk(s). Please wait until this step has finished; then remove the installation medium and restart your system. [![screenshot/pve-install-summary.png](https://pve.proxmox.com/pve-docs/images/screenshot/pve-install-summary.png)](https://pve.proxmox.com/pve-docs/images/screenshot/pve-install-summary.png) Copying the packages usually takes several minutes, mostly depending on the speed of the installation medium and the target disk performance. When copying and setting up the packages has finished, you can reboot the server. This will be done automatically after a few seconds by default. ##### Installation Failure If the installation failed, check out specific errors on the second TTY (_CTRL + ALT + F2_) and ensure that the systems meets the [minimum requirements](https://pve.proxmox.com/wiki/System_Requirements#install_minimal_requirements) . If the installation is still not working, look at the [how to get help chapter](https://pve.proxmox.com/wiki/Introduction#getting_help) . ### Accessing the Management Interface Post-Installation [![screenshot/gui-login-window.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-login-window.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-login-window.png) After a successful installation and reboot of the system you can use the Proxmox VE web interface for further configuration. 1. Point your browser to the IP address given during the installation and port 8006, for example: [https://youripaddress:8006](https://youripaddress:8006/) 2. Log in using the root (realm _PAM_) username and the password chosen during installation. 3. Upload your subscription key to gain access to the Enterprise repository. Otherwise, you will need to set up one of the public, less tested package repositories to get updates for security fixes, bug fixes, and new features. 4. Check the IP configuration and hostname. 5. Check the timezone. 6. Check your [Firewall settings](https://pve.proxmox.com/wiki/Firewall#chapter_pve_firewall) . ### Advanced LVM Configuration Options The installer creates a Volume Group (VG) called pve, and additional Logical Volumes (LVs) called root, data, and swap, if ext4 or xfs is used. To control the size of these volumes use: hdsize Defines the total hard disk size to be used. This way you can reserve free space on the hard disk for further partitioning (for example for an additional PV and VG on the same hard disk that can be used for LVM storage). swapsize Defines the size of the swap volume. The default is the size of the installed memory, minimum 4 GB and maximum 8 GB. The resulting value cannot be greater than one eight of the size of the hard drive (hdsize / 8). | | | | --- | --- | | ![Note]() | If set to 0, no swap volume will be created. | maxroot Defines the maximum size of the root volume, which stores the operation system. With more than 48 GiB storage available, the default is a quarter of the the size of the hard drive (hdsize / 4) with a maximum of 96 GiB. With less than 48 GiB of storage available, the root volume size is at least half the size of the hard drive (hdsize / 2). maxvz Defines the maximum size of the data volume. The actual size of the data volume is: datasize = hdsize - rootsize - swapsize - minfree Where datasize cannot be bigger than maxvz. | | | | --- | --- | | ![Note]() | In case of LVM thin, the data pool will only be created if datasize is bigger than 4GB. | | | | | --- | --- | | ![Note]() | If set to 0, no data volume will be created and the storage configuration will be adapted accordingly. | minfree Defines the amount of free space that should be left in the LVM volume group pve. With more than 128GB storage available, the default is 16GB, otherwise hdsize/8 will be used. | | | | --- | --- | | ![Note]() | LVM requires free space in the VG for snapshot creation (not required for lvmthin snapshots). | ### Advanced ZFS Configuration Options The installer creates the ZFS pool rpool, if ZFS is used. No swap space is created but you can reserve some unpartitioned space on the install disks for swap. You can also create a swap zvol after the installation, although this can lead to problems (see [ZFS swap notes](https://pve.proxmox.com/wiki/ZFS_on_Linux#zfs_swap) ). ashift Defines the ashift value for the created pool. The ashift needs to be set at least to the sector-size of the underlying disks (2 to the power of ashift is the sector-size), or any disk which might be put in the pool (for example the replacement of a defective disk). compress Defines whether compression is enabled for rpool. checksum Defines which checksumming algorithm should be used for rpool. copies Defines the copies parameter for rpool. Check the zfs(8) manpage for the semantics, and why this does not replace redundancy on disk-level. ARC max size Defines the maximum size the ARC can grow to and thus limits the amount of memory ZFS will use. See also the section on [how to limit ZFS memory usage](https://pve.proxmox.com/wiki/ZFS_on_Linux#sysadmin_zfs_limit_memory_usage) for more details. hdsize Defines the total hard disk size to be used. This is useful to save free space on the hard disk(s) for further partitioning (for example to create a swap-partition). hdsize is only honored for bootable disks, that is only the first disk or mirror for RAID0, RAID1 or RAID10, and all disks in RAID-Z\[123\]. ### Advanced BTRFS Configuration Options No swap space is created when BTRFS is used but you can reserve some unpartitioned space on the install disks for swap. You can either create a separate partition, BTRFS subvolume or a swapfile using the btrfs filesystem mkswapfile command. compress Defines whether compression is enabled for the BTRFS subvolume. Different compression algorithms are supported: _on_ (equivalent to _zlib_), _zlib_, _lzo_ and _zstd_. Defaults to _off_. hdsize Defines the total hard disk size to be used. This is useful to save free space on the hard disk(s) for further partitioning (for example, to create a swap partition). ### ZFS Performance Tips ZFS works best with a lot of memory. If you intend to use ZFS make sure to have enough RAM available for it. A good calculation is 4GB plus 1GB RAM for each TB RAW disk space. ZFS can use a dedicated drive as write cache, called the ZFS Intent Log (ZIL). Use a fast drive (SSD) for it. It can be added after installation with the following command: \# zpool add log ### Adding the nomodeset Kernel Parameter Problems may arise on very old or very new hardware due to graphics drivers. If the installation hangs during boot, you can try adding the nomodeset parameter. This prevents the Linux kernel from loading any graphics drivers and forces it to continue using the BIOS/UEFI-provided framebuffer. On the Proxmox VE bootloader menu, navigate to _Install Proxmox VE (Terminal UI)_ and press e to edit the entry. Using the arrow keys, navigate to the line starting with linux, move the cursor to the end of that line and add the parameter nomodeset, separated by a space from the pre-existing last parameter. Then press Ctrl-X or F10 to boot the configuration. Unattended Installation ----------------------- The automated installation method allows installing Proxmox VE in an unattended manner. This enables you to fully automate the setup process on bare-metal. Once the installation is complete and the host has booted up, automation tools like Ansible can be used to further configure the installation. The necessary options for the installer must be provided in an answer file. This file allows using filter rules to determine which disks and network cards should be used. To use the automated installation, it is first necessary to choose a source from which the answer file is fetched from and then prepare an installation ISO with that choice. Once the ISO is prepared, its initial boot menu will show a new boot entry named _Automated Installation_ which gets automatically selected after a 10-second timeout. [Visit our wiki](https://pve.proxmox.com/wiki/Automated_Installation) for more details and information on the unattended installation. Video Tutorials --------------- See the list of all official tutorials on our [Proxmox VE YouTube Channel](https://www.youtube.com/proxmoxve) See Also -------- * [Prepare Installation Media](https://pve.proxmox.com/wiki/Prepare_Installation_Media) * [Install Proxmox VE on Debian 12 Bookworm](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_12_Bookworm) * [System Requirements](https://pve.proxmox.com/wiki/System_Requirements) * [Package Repositories](https://pve.proxmox.com/wiki/Package_Repositories) * [Host System Administration](https://pve.proxmox.com/wiki/Host_System_Administration) * [Network Configuration](https://pve.proxmox.com/wiki/Network_Configuration) * [Installation: Tips and Tricks](https://pve.proxmox.com/wiki/Installation:_Tips_and_Tricks) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Installation&oldid=12300](https://pve.proxmox.com/mediawiki/index.php?title=Installation&oldid=12300) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Reference Documentation](https://pve.proxmox.com/wiki/Category:Reference_Documentation "Category:Reference Documentation") * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Installation](https://pve.proxmox.com/wiki/Category:Installation "Category:Installation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Downloads - Proxmox VE Downloads ========= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Downloads#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Downloads#searchInput) Contents -------- * [1 Proxmox Virtual Environment 9.1 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_9.1_(ISO_Image)) * [1.1 Update a running Proxmox Virtual Environment 9 to latest 9.1](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_9_to_latest_9.1) * [2 Proxmox Virtual Environment 9.0 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_9.0_(ISO_Image)) * [2.1 Update a running Proxmox Virtual Environment 9 to latest 9.0](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_9_to_latest_9.0) * [3 Proxmox Virtual Environment 9.0 beta1 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_9.0_beta1_(ISO_Image)) * [4 Proxmox Virtual Environment 8.4 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_8.4_(ISO_Image)) * [4.1 Update a running Proxmox Virtual Environment 8.x to latest 8.4](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_8.x_to_latest_8.4) * [5 Proxmox Virtual Environment 8.3 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_8.3_(ISO_Image)) * [5.1 Update a running Proxmox Virtual Environment 8.x to latest 8.3](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_8.x_to_latest_8.3) * [6 Proxmox Virtual Environment 8.2 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_8.2_(ISO_Image)) * [6.1 Update a running Proxmox Virtual Environment 8.x to latest 8.2](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_8.x_to_latest_8.2) * [7 Proxmox Virtual Environment 8.1 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_8.1_(ISO_Image)) * [7.1 Update a running Proxmox Virtual Environment 8.x to latest 8.1](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_8.x_to_latest_8.1) * [8 Proxmox Virtual Environment 8.0 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_8.0_(ISO_Image)) * [8.1 Update a running Proxmox Virtual Environment 8.x to latest 8.x](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_8.x_to_latest_8.x) * [8.2 Update a running Proxmox Virtual Environment 7.4 to latest 8.x](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_7.4_to_latest_8.x) * [9 Proxmox Virtual Environment 8.0 beta1 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_8.0_beta1_(ISO_Image)) * [10 Proxmox Virtual Environment 7.4 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_7.4_(ISO_Image)) * [10.1 Update a running Proxmox Virtual Environment 7.x to latest 7.4](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_7.x_to_latest_7.4) * [11 Proxmox Virtual Environment 7.3 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_7.3_(ISO_Image)) * [11.1 Update a running Proxmox Virtual Environment 7.x to latest 7.3](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_7.x_to_latest_7.3) * [12 Proxmox Virtual Environment 7.2 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_7.2_(ISO_Image)) * [12.1 Update a running Proxmox Virtual Environment 7.x to latest 7.2](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_7.x_to_latest_7.2) * [13 Proxmox Virtual Environment 7.1 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_7.1_(ISO_Image)) * [13.1 Update a running Proxmox Virtual Environment 7.x to latest 7.1](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_7.x_to_latest_7.1) * [14 Proxmox Virtual Environment 7.0 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_7.0_(ISO_Image)) * [14.1 Update a running Proxmox Virtual Environment 7.x to latest 7.0](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_7.x_to_latest_7.0) * [14.2 Update a running Proxmox Virtual Environment 6.4 to latest 7.x](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_6.4_to_latest_7.x) * [15 Proxmox Virtual Environment 7.0 beta1 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_7.0_beta1_(ISO_Image)) * [16 Proxmox Virtual Environment 6.4 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_6.4_(ISO_Image)) * [16.1 Update a running Proxmox Virtual Environment 6.x to latest 6.4](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_6.x_to_latest_6.4) * [17 Proxmox Virtual Environment 6.3 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_6.3_(ISO_Image)) * [17.1 Update a running Proxmox Virtual Environment 6.x to latest 6.3](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_6.x_to_latest_6.3) * [18 Proxmox Virtual Environment 6.2 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_6.2_(ISO_Image)) * [18.1 Update a running Proxmox Virtual Environment 6.x to latest 6.2](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_6.x_to_latest_6.2) * [19 Proxmox Virtual Environment 6.1 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_6.1_(ISO_Image)) * [19.1 Update a running Proxmox Virtual Environment 6.x to latest 6.1](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_6.x_to_latest_6.1) * [20 Proxmox Virtual Environment 6.0 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_6.0_(ISO_Image)) * [20.1 Update a running Proxmox Virtual Environment 6.x to latest 6.0](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_6.x_to_latest_6.0) * [20.2 Update a running Proxmox Virtual Environment 5.4 to latest 6.0](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_5.4_to_latest_6.0) * [21 Proxmox Virtual Environment 6.0 beta1 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_6.0_beta1_(ISO_Image)) * [22 Proxmox Virtual Environment 5.4 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_5.4_(ISO_Image)) * [22.1 Update a running Proxmox Virtual Environment 5.x to latest 5.4](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_5.x_to_latest_5.4) * [23 Proxmox Virtual Environment 5.3 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_5.3_(ISO_Image)) * [23.1 Update a running Proxmox Virtual Environment 5.x to latest 5.3](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_5.x_to_latest_5.3) * [24 Proxmox Virtual Environment 5.2 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_5.2_(ISO_Image)) * [24.1 Update a running Proxmox Virtual Environment 5.x to latest 5.2](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_5.x_to_latest_5.2) * [25 Proxmox Virtual Environment 5.1 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_5.1_(ISO_Image)) * [25.1 Update a running Proxmox Virtual Environment 5.x to latest 5.1](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_5.x_to_latest_5.1) * [26 Proxmox Virtual Environment 5.0 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_5.0_(ISO_Image)) * [26.1 Update a running Proxmox Virtual Environment 5.x to latest 5.0](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_5.x_to_latest_5.0) * [27 Proxmox Virtual Environment 5.0 beta2 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_5.0_beta2_(ISO_Image)) * [28 Proxmox Virtual Environment 5.0 beta1 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_5.0_beta1_(ISO_Image)) * [28.1 Update a running Proxmox Virtual Environment 5.x beta to latest 5.x beta](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_5.x_beta_to_latest_5.x_beta) * [29 Proxmox Virtual Environment 4.4 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_4.4_(ISO_Image)) * [29.1 Update a running Proxmox Virtual Environment 4.x to latest 4.4](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_4.x_to_latest_4.4) * [30 Proxmox Virtual Environment 4.3 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_4.3_(ISO_Image)) * [30.1 Update a running Proxmox Virtual Environment 4.x to latest 4.3](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_4.x_to_latest_4.3) * [31 Proxmox Virtual Environment 4.2 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_4.2_(ISO_Image)) * [31.1 Update a running Proxmox Virtual Environment 4.x to latest 4.2](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_4.x_to_latest_4.2) * [32 Proxmox Virtual Environment 4.1 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_4.1_(ISO_Image)) * [32.1 Update a running Proxmox Virtual Environment 4.x to latest 4.1](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_4.x_to_latest_4.1) * [33 Proxmox Virtual Environment 4.0 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_4.0_(ISO_Image)) * [33.1 Update a running Proxmox Virtual Environment 4.x to latest 4.0](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_4.x_to_latest_4.0) * [33.2 Update a running Proxmox Virtual Environment 3.x to latest 4.0](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_3.x_to_latest_4.0) * [34 Proxmox Virtual Environment 3.4 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_3.4_(ISO_Image)) * [34.1 Update a running Proxmox Virtual Environment 3.x to latest 3.4](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_3.x_to_latest_3.4) * [35 Proxmox Virtual Environment 3.3 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_3.3_(ISO_Image)) * [35.1 Update a running Proxmox Virtual Environment 3.x to latest 3.3](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_3.x_to_latest_3.3) * [36 Proxmox Virtual Environment 3.2 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_3.2_(ISO_Image)) * [36.1 Update a running Proxmox Virtual Environment 3.x to latest 3.2](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_3.x_to_latest_3.2) * [37 Proxmox Virtual Environment 3.1 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_3.1_(ISO_Image)) * [37.1 Update a running Proxmox Virtual Environment 3.x to latest 3.1](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_3.x_to_latest_3.1) * [38 Proxmox Virtual Environment 3.0 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_3.0_(ISO_Image)) * [38.1 Update a running Proxmox Virtual Environment 3.x to latest 3.0](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_3.x_to_latest_3.0) * [38.2 Update a running Proxmox Virtual Environment 2.3 to 3.0](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_2.3_to_3.0) * [39 Proxmox Virtual Environment 2.3 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_2.3_(ISO_Image)) * [39.1 Update a running Proxmox Virtual Environment 2.x to latest 2.3](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_2.x_to_latest_2.3) * [40 Proxmox Virtual Environment 2.2 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_2.2_(ISO_Image)) * [40.1 Update a running Proxmox Virtual Environment 2.x to latest 2.2](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_2.x_to_latest_2.2) * [41 Proxmox Virtual Environment 2.1 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_2.1_(ISO_Image)) * [41.1 Update a running Proxmox Virtual Environment 2.x to latest 2.1](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_2.x_to_latest_2.1) * [41.2 Update a running Proxmox Virtual Environment 1.9 to 2.x](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_1.9_to_2.x) * [42 Proxmox Virtual Environment 2.0 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_2.0_(ISO_Image)) * [42.1 Update a running Proxmox Virtual Environment to 2.0](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_to_2.0) * [43 Proxmox Virtual Environment 1.9 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_1.9_(ISO_Image)) * [43.1 Update a running Proxmox Virtual Environment to 1.9](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_to_1.9) * [44 Proxmox Virtual Environment 1.8 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_1.8_(ISO_Image)) * [44.1 Update a running Proxmox Virtual Environment to 1.8](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_to_1.8) * [45 Proxmox Virtual Environment 1.7 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_1.7_(ISO_Image)) * [45.1 Update a running Proxmox Virtual Environment to 1.7](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_to_1.7) * [46 Proxmox Virtual Environment 1.6 (ISO Image updated on 18.10.2010)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_1.6_(ISO_Image_updated_on_18.10.2010)) * [47 Proxmox VE 1.5 - New Kernel 2.6.24 and 2.6.32 (17.5.2010)](https://pve.proxmox.com/wiki/Downloads#Proxmox_VE_1.5_-_New_Kernel_2.6.24_and_2.6.32_(17.5.2010)) * [47.1 Update a running Proxmox Virtual Environment 1.5](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_1.5) * [48 Proxmox Virtual Environment 1.5 (ISO Image) - updated on 3.2.2010](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_1.5_(ISO_Image)_-_updated_on_3.2.2010) * [48.1 Update a running Proxmox Virtual Environment 1.x to 1.5](https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_1.x_to_1.5) * [49 Proxmox Virtual Environment 1.4 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_1.4_(ISO_Image)) * [50 Proxmox Virtual Environment 1.4 beta2](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_1.4_beta2) * [51 Proxmox Virtual Environment 1.4 beta1 (ISO Image updated on 17.9.2009)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_1.4_beta1_(ISO_Image_updated_on_17.9.2009)) * [52 Proxmox Virtual Environment 1.3 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_1.3_(ISO_Image)) * [53 Proxmox Virtual Environment 1.2 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_1.2_(ISO_Image)) * [54 Proxmox Virtual Environment 1.1 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_1.1_(ISO_Image)) * [55 Proxmox Virtual Environment 1.0 (ISO Image)](https://pve.proxmox.com/wiki/Downloads#Proxmox_Virtual_Environment_1.0_(ISO_Image)) Proxmox Virtual Environment 9.1 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox VE 9.1](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_9.1 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install from USB Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For a quick how-to see [Quick installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") or check out the detailed [Installation](https://pve.proxmox.com/wiki/Installation "Installation") article. * Download via [https://www.proxmox.com/downloads](https://www.proxmox.com/downloads) * Alternative download [https://enterprise.proxmox.com/iso/](https://enterprise.proxmox.com/iso/) Update a running Proxmox Virtual Environment 9 to latest 9.1 ------------------------------------------------------------ Here is the how-to for the CLI: Check your `debian.sources` file, should look like this: Types: deb URIs: http://deb.debian.org/debian/ Suites: trixie trixie-updates Components: main contrib non-free-firmware Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg Types: deb URIs: http://security.debian.org/debian-security/ Suites: trixie-security Components: main contrib non-free-firmware Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.sources Types: deb URIs: https://enterprise.proxmox.com/debian/pve Suites: trixie Components: pve-enterprise Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg The Ceph Squid enterprise repository: cat /etc/apt/sources.list.d/ceph.sources Types: deb URIs: https://enterprise.proxmox.com/debian/ceph-squid Suites: trixie Components: enterprise Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg Update your repository and packages: apt update If you get any errors, your `sources.list` (or your network or subscription key status) has a problem. Now upgrade the packages: apt dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 9.1.0 (running kernel: 6.17.2-1-pve) pve-manager: 9.1.1 (running version: 9.1.1/42db4a6cf33dac83) proxmox-kernel-helper: 9.0.4 proxmox-kernel-6.17.2-1-pve-signed: 6.17.2-1 proxmox-kernel-6.17: 6.17.2-1 amd64-microcode: 3.20250311.1 ceph-fuse: 19.2.3-pve2 corosync: 3.1.9-pve2 criu: 4.1.1-1 frr-pythontools: 10.3.1-1+pve4 ifupdown2: 3.3.0-1+pmx11 ksm-control-daemon: 1.5-1 libjs-extjs: 7.0.0-5 libproxmox-acme-perl: 1.7.0 libproxmox-backup-qemu0: 2.0.1 libproxmox-rs-perl: 0.4.1 libpve-access-control: 9.0.4 libpve-apiclient-perl: 3.4.2 libpve-cluster-api-perl: 9.0.7 libpve-cluster-perl: 9.0.7 libpve-common-perl: 9.0.15 libpve-guest-common-perl: 6.0.2 libpve-http-server-perl: 6.0.5 libpve-network-perl: 1.2.3 libpve-rs-perl: 0.11.3 libpve-storage-perl: 9.0.18 libspice-server1: 0.15.2-1+b1 lvm2: 2.03.31-2+pmx1 lxc-pve: 6.0.5-3 lxcfs: 6.0.4-pve1 novnc-pve: 1.6.0-3 proxmox-backup-client: 4.0.20-1 proxmox-backup-file-restore: 4.0.20-1 proxmox-backup-restore-image: 1.0.0 proxmox-firewall: 1.2.1 proxmox-kernel-helper: 9.0.4 proxmox-mail-forward: 1.0.2 proxmox-mini-journalreader: 1.6 proxmox-offline-mirror-helper: 0.7.3 proxmox-widget-toolkit: 5.1.2 pve-cluster: 9.0.7 pve-container: 6.0.18 pve-docs: 9.1.1 pve-edk2-firmware: 4.2025.05-2 pve-esxi-import-tools: 1.0.1 pve-firewall: 6.0.4 pve-firmware: 3.17-2 pve-ha-manager: 5.0.8 pve-i18n: 3.6.2 pve-qemu-kvm: 10.1.2-3 pve-xtermjs: 5.5.0-3 qemu-server: 9.1.0 smartmontools: 7.4-pve1 spiceterm: 3.4.1 swtpm: 0.8.0+pve3 vncterm: 1.9.1 zfsutils-linux: 2.3.4-pve1 pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repositories work out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 9.0 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox VE 9.0](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_9.0 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install from USB Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For a quick how-to see [Quick installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") or check out the detailed [Installation](https://pve.proxmox.com/wiki/Installation "Installation") article. * Download via [https://www.proxmox.com/downloads](https://www.proxmox.com/downloads) * Alternative download [https://enterprise.proxmox.com/iso/](https://enterprise.proxmox.com/iso/) Update a running Proxmox Virtual Environment 9 to latest 9.0 ------------------------------------------------------------ Here is the how-to for the CLI: Check your `debian.sources` file, should look like this: Types: deb URIs: http://deb.debian.org/debian/ Suites: trixie trixie-updates Components: main contrib non-free-firmware Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg Types: deb URIs: http://security.debian.org/debian-security/ Suites: trixie-security Components: main contrib non-free-firmware Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.sources Types: deb URIs: https://enterprise.proxmox.com/debian/pve Suites: trixie Components: pve-enterprise Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg The Ceph Squid enterprise repository: cat /etc/apt/sources.list.d/ceph.sources Types: deb URIs: https://enterprise.proxmox.com/debian/ceph-squid Suites: trixie Components: enterprise Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg Update your repository and packages: apt update If you get any errors, your `sources.list` (or your network or subscription key status) has a problem. Now upgrade the packages: apt dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 9.0.0 (running kernel: 6.14.8-2-pve) pve-manager: 9.0.3 (running version: 9.0.3/025864202ebb6109) proxmox-kernel-helper: 9.0.3 proxmox-kernel-6.14: 6.14.8-2 proxmox-kernel-6.14.8-2-pve: 6.14.8-2 ceph: 19.2.3-pve2 ceph-fuse: 19.2.3-pve2 corosync: 3.1.9-pve2 criu: 4.1.1-1 frr-pythontools: 10.3.1-1+pve4 ifupdown2: 3.3.0-1+pmx9 ksm-control-daemon: 1.5-1 libjs-extjs: 7.0.0-5 libproxmox-acme-perl: 1.7.0 libproxmox-backup-qemu0: 2.0.1 libproxmox-rs-perl: 0.4.1 libpve-access-control: 9.0.3 libpve-apiclient-perl: 3.4.0 libpve-cluster-api-perl: 9.0.6 libpve-cluster-perl: 9.0.6 libpve-common-perl: 9.0.9 libpve-guest-common-perl: 6.0.2 libpve-http-server-perl: 6.0.3 libpve-network-perl: 1.1.6 libpve-rs-perl: 0.10.7 libpve-storage-perl: 9.0.13 libqb0: 1.0.5-1 libspice-server1: 0.15.2-1+b1 lvm2: 2.03.31-2 lxc-pve: 6.0.4-2 lxcfs: 6.0.4-pve1 novnc-pve: 1.6.0-3 proxmox-backup-client: 4.0.9-1 proxmox-backup-file-restore: 4.0.9-1 proxmox-backup-restore-image: 1.0.0 proxmox-firewall: 1.1.1 proxmox-kernel-helper: 9.0.3 proxmox-mail-forward: 1.0.2 proxmox-mini-journalreader: 1.6 proxmox-offline-mirror-helper: 0.7.0 proxmox-widget-toolkit: 5.0.4 pve-cluster: 9.0.6 pve-container: 6.0.9 pve-docs: 9.0.7 pve-edk2-firmware: 4.2025.02-4 pve-esxi-import-tools: 1.0.1 pve-firewall: 6.0.3 pve-firmware: 3.16-3 pve-ha-manager: 5.0.4 pve-i18n: 3.5.2 pve-qemu-kvm: 10.0.2-4 pve-xtermjs: 5.5.0-2 qemu-server: 9.0.16 smartmontools: 7.4-pve1 spiceterm: 3.4.0 swtpm: 0.8.0+pve2 vncterm: 1.9.0 zfsutils-linux: 2.3.3-pve1 pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repositories work out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 9.0 beta1 (ISO Image) ================================================= Release notes: [Roadmap#Proxmox VE 9.0 beta1](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_9.0_beta1 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install from USB Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For a quick how-to see [Quick installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") or check out the detailed [Installation](https://pve.proxmox.com/wiki/Installation "Installation") article. * Download via [https://enterprise.proxmox.com/iso/](https://enterprise.proxmox.com/iso/) * Upgrade How-To: [Upgrade from 8 to 9](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9 "Upgrade from 8 to 9") Proxmox Virtual Environment 8.4 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox VE 8.4](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_8.4 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install from USB Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For a quick how-to see [Quick installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") or check out the detailed [Installation](https://pve.proxmox.com/wiki/Installation "Installation") article. * Download via [https://www.proxmox.com/downloads](https://www.proxmox.com/downloads) * Alternative download [https://enterprise.proxmox.com/iso/](https://enterprise.proxmox.com/iso/) Update a running Proxmox Virtual Environment 8.x to latest 8.4 -------------------------------------------------------------- Here is the how-to for the CLI: Check your `sources.list` file, should look like this: deb http://deb.debian.org/debian bookworm main contrib deb http://deb.debian.org/debian bookworm-updates main contrib # security updates deb http://security.debian.org bookworm-security main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian/pve](https://enterprise.proxmox.com/debian/pve) bookworm pve-enterprise The Ceph Reef enterprise repository: deb [https://enterprise.proxmox.com/debian/ceph-reef](https://enterprise.proxmox.com/debian/ceph-reef) bookworm enterprise Update your repository and packages: apt update If you get any errors, your `sources.list` (or your network or subscription key status) has a problem. Now upgrade the packages: apt dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 8.4.0 (running kernel: 6.8.12-9-pve) pve-manager: 8.4.0 (running version: 8.4.0/ec58e45e1bcdf2ac) proxmox-kernel-helper: 8.1.1 proxmox-kernel-6.8: 6.8.12-9 proxmox-kernel-6.8.12-9-pve-signed: 6.8.12-9 ceph: 19.2.1-pve3 ceph-fuse: 19.2.1-pve3 corosync: 3.1.9-pve1 criu: 3.17.1-2+deb12u1 dnsmasq: 2.90-4~deb12u1 glusterfs-client: 10.3-5 ifupdown: residual config ifupdown2: 3.2.0-1+pmx11 intel-microcode: 3.20250211.1~deb12u1 ksm-control-daemon: 1.5-1 libjs-extjs: 7.0.0-5 libknet1: 1.30-pve2 libproxmox-acme-perl: 1.6.0 libproxmox-backup-qemu0: 1.5.1 libproxmox-rs-perl: 0.3.5 libpve-access-control: 8.2.2 libpve-apiclient-perl: 3.3.2 libpve-cluster-api-perl: 8.1.0 libpve-cluster-perl: 8.1.0 libpve-common-perl: 8.3.1 libpve-guest-common-perl: 5.2.2 libpve-http-server-perl: 5.2.2 libpve-network-perl: 0.11.2 libpve-rs-perl: 0.9.4 libpve-storage-perl: 8.3.6 libspice-server1: 0.15.1-1 lvm2: 2.03.16-2 lxc-pve: 6.0.0-1 lxcfs: 6.0.0-pve2 novnc-pve: 1.6.0-2 proxmox-backup-client: 3.3.7-1 proxmox-backup-file-restore: 3.3.7-1 proxmox-firewall: 0.7.1 proxmox-kernel-helper: 8.1.1 proxmox-mail-forward: 0.3.2 proxmox-mini-journalreader: 1.4.0 proxmox-offline-mirror-helper: 0.6.7 proxmox-widget-toolkit: 4.3.10 pve-cluster: 8.1.0 pve-container: 5.2.6 pve-docs: 8.4.0 pve-edk2-firmware: 4.2025.02-3 pve-esxi-import-tools: 0.7.3 pve-firewall: 5.1.1 pve-firmware: 3.15-3 pve-ha-manager: 4.0.7 pve-i18n: 3.4.2 pve-qemu-kvm: 9.2.0-5 pve-xtermjs: 5.5.0-2 qemu-server: 8.3.12 smartmontools: 7.3-pve1 spiceterm: 3.3.0 swtpm: 0.8.0+pve1 vncterm: 1.8.0 zfsutils-linux: 2.2.7-pve2 pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repositories work out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 8.3 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox VE 8.3](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_8.3 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install from USB Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For a quick how-to see [Quick installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") or check out the detailed [Installation](https://pve.proxmox.com/wiki/Installation "Installation") article. * Download via [https://www.proxmox.com/downloads](https://www.proxmox.com/downloads) * Alternative download [https://enterprise.proxmox.com/iso/](https://enterprise.proxmox.com/iso/) Update a running Proxmox Virtual Environment 8.x to latest 8.3 -------------------------------------------------------------- Here is the how-to for the CLI: Check your `sources.list` file, should look like this: deb http://deb.debian.org/debian bookworm main contrib deb http://deb.debian.org/debian bookworm-updates main contrib # security updates deb http://security.debian.org bookworm-security main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian/pve](https://enterprise.proxmox.com/debian/pve) bookworm pve-enterprise The Ceph Reef enterprise repository: deb [https://enterprise.proxmox.com/debian/ceph-reef](https://enterprise.proxmox.com/debian/ceph-reef) bookworm enterprise Update your repository and packages: apt update If you get any errors, your `sources.list` (or your network or subscription key status) has a problem. Now upgrade the packages: apt dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 8.3.0 (running kernel: 6.8.12-4-pve) pve-manager: 8.3.0 (running version: 8.3.0/c1689ccb1065a83b) proxmox-kernel-helper: 8.1.0 proxmox-kernel-6.8: 6.8.12-4 proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4 ceph-fuse: 18.2.4-pve3 corosync: 3.1.7-pve3 criu: 3.17.1-2 glusterfs-client: 10.3-5 ifupdown2: 3.2.0-1+pmx11 ksm-control-daemon: 1.5-1 libjs-extjs: 7.0.0-5 libknet1: 1.28-pve1 libproxmox-acme-perl: 1.5.1 libproxmox-backup-qemu0: 1.4.1 libproxmox-rs-perl: 0.3.4 libpve-access-control: 8.2.0 libpve-apiclient-perl: 3.3.2 libpve-cluster-api-perl: 8.0.10 libpve-cluster-perl: 8.0.10 libpve-common-perl: 8.2.9 libpve-guest-common-perl: 5.1.6 libpve-http-server-perl: 5.1.2 libpve-network-perl: 0.10.0 libpve-rs-perl: 0.9.0 libpve-storage-perl: 8.2.9 libspice-server1: 0.15.1-1 lvm2: 2.03.16-2 lxc-pve: 6.0.0-1 lxcfs: 6.0.0-pve2 novnc-pve: 1.5.0-1 proxmox-backup-client: 3.2.9-1 proxmox-backup-file-restore: 3.2.9-1 proxmox-firewall: 0.6.0 proxmox-kernel-helper: 8.1.0 proxmox-mail-forward: 0.3.1 proxmox-mini-journalreader: 1.4.0 proxmox-offline-mirror-helper: 0.6.7 proxmox-widget-toolkit: 4.3.1 pve-cluster: 8.0.10 pve-container: 5.2.2 pve-docs: 8.3.1 pve-edk2-firmware: 4.2023.08-4 pve-esxi-import-tools: 0.7.2 pve-firewall: 5.1.0 pve-firmware: 3.14-1 pve-ha-manager: 4.0.6 pve-i18n: 3.3.1 pve-qemu-kvm: 9.0.2-4 pve-xtermjs: 5.3.0-3 qemu-server: 8.3.0 smartmontools: 7.3-pve1 spiceterm: 3.3.0 swtpm: 0.8.0+pve1 vncterm: 1.8.0 zfsutils-linux: 2.2.6-pve1 pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repositories work out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 8.2 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox VE 8.2](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_8.2 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install from USB Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For a quick how-to see [Quick installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") or check out the detailed [Installation](https://pve.proxmox.com/wiki/Installation "Installation") article. * Download via [https://www.proxmox.com/downloads](https://www.proxmox.com/downloads) * Alternative download [https://enterprise.proxmox.com/iso/](https://enterprise.proxmox.com/iso/) Update a running Proxmox Virtual Environment 8.x to latest 8.2 -------------------------------------------------------------- Here is the how-to for the CLI: Check your `sources.list` file, should look like this: deb http://deb.debian.org/debian bookworm main contrib deb http://deb.debian.org/debian bookworm-updates main contrib # security updates deb http://security.debian.org bookworm-security main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian/pve](https://enterprise.proxmox.com/debian/pve) bookworm pve-enterprise The Ceph Reef enterprise repository: deb [https://enterprise.proxmox.com/debian/ceph-reef](https://enterprise.proxmox.com/debian/ceph-reef) bookworm enterprise Update your repository and packages: apt update If you get any errors, your `sources.list` (or your network or subscription key status) has a problem. Now upgrade the packages: apt dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 8.2.0 (running kernel: 6.8.4-2-pve) pve-manager: 8.2.2 (running version: 8.2.2/9355359cd7afbae4) proxmox-kernel-helper: 8.1.0 proxmox-kernel-6.8: 6.8.4-2 proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2 ceph-fuse: 17.2.7-pve3 corosync: 3.1.7-pve3 criu: 3.17.1-2 glusterfs-client: 10.3-5 ifupdown2: 3.2.0-1+pmx8 ksm-control-daemon: 1.5-1 libjs-extjs: 7.0.0-4 libknet1: 1.28-pve1 libproxmox-acme-perl: 1.5.0 libproxmox-backup-qemu0: 1.4.1 libproxmox-rs-perl: 0.3.3 libpve-access-control: 8.1.4 libpve-apiclient-perl: 3.3.2 libpve-cluster-api-perl: 8.0.6 libpve-cluster-perl: 8.0.6 libpve-common-perl: 8.2.1 libpve-guest-common-perl: 5.1.1 libpve-http-server-perl: 5.1.0 libpve-network-perl: 0.9.8 libpve-rs-perl: 0.8.8 libpve-storage-perl: 8.2.1 libspice-server1: 0.15.1-1 lvm2: 2.03.16-2 lxc-pve: 6.0.0-1 lxcfs: 6.0.0-pve2 novnc-pve: 1.4.0-3 proxmox-backup-client: 3.2.0-1 proxmox-backup-file-restore: 3.2.0-1 proxmox-kernel-helper: 8.1.0 proxmox-mail-forward: 0.2.3 proxmox-mini-journalreader: 1.4.0 proxmox-offline-mirror-helper: 0.6.6 proxmox-widget-toolkit: 4.2.1 pve-cluster: 8.0.6 pve-container: 5.0.10 pve-docs: 8.2.1 pve-edk2-firmware: 4.2023.08-4 pve-esxi-import-tools: 0.7.0 pve-firewall: 5.0.5 pve-firmware: 3.11-1 pve-ha-manager: 4.0.4 pve-i18n: 3.2.2 pve-qemu-kvm: 8.1.5-5 pve-xtermjs: 5.3.0-3 qemu-server: 8.2.1 smartmontools: 7.3-pve1 spiceterm: 3.3.0 swtpm: 0.8.0+pve1 vncterm: 1.8.0 zfsutils-linux: 2.2.3-pve2 pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repositories work out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 8.1 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox VE 8.1](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_8.1 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install from USB Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For a quick how-to see [Quick installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") or check out the detailed [Installation](https://pve.proxmox.com/wiki/Installation "Installation") article. * Download via [https://www.proxmox.com/downloads](https://www.proxmox.com/downloads) * Alternative download [https://enterprise.proxmox.com/iso/](https://enterprise.proxmox.com/iso/) Update a running Proxmox Virtual Environment 8.x to latest 8.1 -------------------------------------------------------------- Here is the how-to for the CLI: Check your `sources.list` file, should look like this: deb http://deb.debian.org/debian bookworm main contrib deb http://deb.debian.org/debian bookworm-updates main contrib # security updates deb http://security.debian.org bookworm-security main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian/pve](https://enterprise.proxmox.com/debian/pve) bookworm pve-enterprise The Ceph Reef enterprise repository: deb [https://enterprise.proxmox.com/debian/ceph-reef](https://enterprise.proxmox.com/debian/ceph-reef) bookworm enterprise Update your repository and packages: apt update If you get any errors, your `sources.list` (or your network or subscription key status) has a problem. Now upgrade the packages: apt dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 8.1.0 (running kernel: 6.5.11-4-pve) pve-manager: 8.1.3 (running version: 8.1.3/b46aac3b42da5d15) proxmox-kernel-helper: 8.0.9 pve-kernel-6.2: 8.0.5 proxmox-kernel-6.5.11-4-pve-signed: 6.5.11-4 proxmox-kernel-6.5: 6.5.11-4 ceph: 17.2.7-pve1 ceph-fuse: 17.2.7-pve1 corosync: 3.1.7-pve3 criu: 3.17.1-2 glusterfs-client: 10.3-5 ifupdown2: 3.2.0-1+pmx7 ksm-control-daemon: 1.4-1 libjs-extjs: 7.0.0-4 libknet1: 1.28-pve1 libproxmox-acme-perl: 1.5.0 libproxmox-backup-qemu0: 1.4.0 libproxmox-rs-perl: 0.3.1 libpve-access-control: 8.0.7 libpve-apiclient-perl: 3.3.1 libpve-common-perl: 8.1.0 libpve-guest-common-perl: 5.0.6 libpve-http-server-perl: 5.0.5 libpve-network-perl: 0.9.4 libpve-rs-perl: 0.8.7 libpve-storage-perl: 8.0.5 libspice-server1: 0.15.1-1 lvm2: 2.03.16-2 lxc-pve: 5.0.2-4 lxcfs: 5.0.3-pve3 novnc-pve: 1.4.0-3 proxmox-backup-client: 3.0.4-1 proxmox-backup-file-restore: 3.0.4-1 proxmox-kernel-helper: 8.0.9 proxmox-mail-forward: 0.2.2 proxmox-mini-journalreader: 1.4.0 proxmox-offline-mirror-helper: 0.6.2 proxmox-widget-toolkit: 4.1.3 pve-cluster: 8.0.5 pve-container: 5.0.8 pve-docs: 8.1.3 pve-edk2-firmware: 4.2023.08-1 pve-firewall: 5.0.3 pve-firmware: 3.9-1 pve-ha-manager: 4.0.3 pve-i18n: 3.1.2 pve-qemu-kvm: 8.1.2-4 pve-xtermjs: 5.3.0-2 qemu-server: 8.0.10 smartmontools: 7.3-pve1 spiceterm: 3.3.0 swtpm: 0.8.0+pve1 vncterm: 1.8.0 zfsutils-linux: 2.2.0-pve3 pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repositories work out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 8.0 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox VE 8.0](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_8.0 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install from USB Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For a quick how-to see [Quick installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") or check out the detailed [Installation](https://pve.proxmox.com/wiki/Installation "Installation") article. * Download via [https://www.proxmox.com/downloads](https://www.proxmox.com/downloads) * Alternative download [https://enterprise.proxmox.com/iso/](https://enterprise.proxmox.com/iso/) Update a running Proxmox Virtual Environment 8.x to latest 8.x -------------------------------------------------------------- Here is the howto for the CLI: Check your sources.list file, should look like this: deb http://deb.debian.org/debian bookworm main contrib deb http://deb.debian.org/debian bookworm-updates main contrib # security updates deb http://security.debian.org bookworm-security main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian/pve](https://enterprise.proxmox.com/debian/pve) bookworm pve-enterprise The Ceph enterprise repository: deb [https://enterprise.proxmox.com/debian/ceph-quincy](https://enterprise.proxmox.com/debian/ceph-quincy) bookworm enterprise Update your repository and packages: apt update If you get any errors, your sources.list (or your network or subscription key status) has a problem. Now upgrade the packages: apt dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 8.0.2 (running kernel: 6.2.16-10-pve) pve-manager: 8.0.4 (running version: 8.0.4/d258a813cfa6b390) proxmox-kernel-helper: 8.0.3 proxmox-kernel-6.2.16-10-pve: 6.2.16-10 proxmox-kernel-6.2: 6.2.16-10 ceph-fuse: 17.2.6-pve1+3 corosync: 3.1.7-pve3 criu: 3.17.1-2 glusterfs-client: 10.3-5 ifupdown2: 3.2.0-1+pmx3 ksm-control-daemon: 1.4-1 libjs-extjs: 7.0.0-4 libknet1: 1.25-pve1 libproxmox-acme-perl: 1.4.6 libproxmox-backup-qemu0: 1.4.0 libproxmox-rs-perl: 0.3.0 libpve-access-control: 8.0.4 libpve-apiclient-perl: 3.3.1 libpve-common-perl: 8.0.7 libpve-guest-common-perl: 5.0.3 libpve-http-server-perl: 5.0.4 libpve-rs-perl: 0.8.4 libpve-storage-perl: 8.0.2 libspice-server1: 0.15.1-1 lvm2: 2.03.16-2 lxc-pve: 5.0.2-4 lxcfs: 5.0.3-pve3 novnc-pve: 1.4.0-2 proxmox-backup-client: 3.0.2-1 proxmox-backup-file-restore: 3.0.2-1 proxmox-kernel-helper: 8.0.3 proxmox-mail-forward: 0.2.0 proxmox-mini-journalreader: 1.4.0 proxmox-widget-toolkit: 4.0.6 pve-cluster: 8.0.2 pve-container: 5.0.4 pve-docs: 8.0.4 pve-edk2-firmware: 3.20230228-4 pve-firewall: 5.0.3 pve-firmware: 3.7-1 pve-ha-manager: 4.0.2 pve-i18n: 3.0.5 pve-qemu-kvm: 8.0.2-4 pve-xtermjs: 4.16.0-3 qemu-server: 8.0.6 smartmontools: 7.3-pve1 spiceterm: 3.3.0 swtpm: 0.8.0+pve1 vncterm: 1.8.0 zfsutils-linux: 2.1.12-pve1 pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repositories work out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Update a running Proxmox Virtual Environment 7.4 to latest 8.x -------------------------------------------------------------- Please follow exactly the upgrade guide: [Upgrade\_from\_7\_to\_8](https://pve.proxmox.com/wiki/Upgrade_from_7_to_8 "Upgrade from 7 to 8") Proxmox Virtual Environment 8.0 beta1 (ISO Image) ================================================= Release notes: [Roadmap#Proxmox VE 8.0 beta1](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_8.0_beta1 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install from USB Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For a quick how-to see [Quick installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") or check out the detailed [Installation](https://pve.proxmox.com/wiki/Installation "Installation") article. * Download via [https://enterprise.proxmox.com/iso/](https://enterprise.proxmox.com/iso/) * Upgrade How-To: [Upgrade from 7 to 8](https://pve.proxmox.com/wiki/Upgrade_from_7_to_8 "Upgrade from 7 to 8") Proxmox Virtual Environment 7.4 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox VE 7.4](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_7.4 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install from USB Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For a quick how-to see [Quick installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") or check out the detailed [Installation](https://pve.proxmox.com/wiki/Installation "Installation") article. * Download via [https://www.proxmox.com/downloads](https://www.proxmox.com/downloads) * Alternative download [https://enterprise.proxmox.com/iso/](https://enterprise.proxmox.com/iso/) Update a running Proxmox Virtual Environment 7.x to latest 7.4 -------------------------------------------------------------- Here is the howto for the CLI: Check your sources.list file, should look like this: deb http://deb.debian.org/debian bullseye main contrib deb http://deb.debian.org/debian bullseye-updates main contrib # security updates deb http://security.debian.org bullseye-security main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian/pve](https://enterprise.proxmox.com/debian/pve) bullseye pve-enterprise Update your repository and packages: apt update If you get any errors, your sources.list (or your network) has a problem. Now upgrade the packages: apt dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 7.4-1 (running kernel: 5.15.102-1-pve) pve-manager: 7.4-3 (running version: 7.4-3/9002ab8a) pve-kernel-5.15: 7.3-3 pve-kernel-5.15.102-1-pve: 5.15.102-1 ceph-fuse: 15.2.13-pve1 corosync: 3.1.7-pve1 criu: 3.15-1+pve-1 glusterfs-client: 9.2-1 ifupdown2: 3.1.0-1+pmx3 ksm-control-daemon: 1.4-1 libjs-extjs: 7.0.0-1 libknet1: 1.24-pve2 libproxmox-acme-perl: 1.4.4 libproxmox-backup-qemu0: 1.3.1-1 libproxmox-rs-perl: 0.2.1 libpve-access-control: 7.4-1 libpve-apiclient-perl: 3.2-1 libpve-common-perl: 7.3-3 libpve-guest-common-perl: 4.2-4 libpve-http-server-perl: 4.2-1 libpve-rs-perl: 0.7.5 libpve-storage-perl: 7.4-2 libspice-server1: 0.14.3-2.1 lvm2: 2.03.11-2.1 lxc-pve: 5.0.2-2 lxcfs: 5.0.3-pve1 novnc-pve: 1.4.0-1 proxmox-backup-client: 2.3.3-1 proxmox-backup-file-restore: 2.3.3-1 proxmox-kernel-helper: 7.4-1 proxmox-mail-forward: 0.1.1-1 proxmox-mini-journalreader: 1.3-1 proxmox-offline-mirror-helper: 0.5.1-1 proxmox-widget-toolkit: 3.6.3 pve-cluster: 7.3-3 pve-container: 4.4-3 pve-docs: 7.4-2 pve-edk2-firmware: 3.20221111-1 pve-firewall: 4.3-1 pve-firmware: 3.6-4 pve-ha-manager: 3.6.0 pve-i18n: 2.11-1 pve-qemu-kvm: 7.2.0-8 pve-xtermjs: 4.16.0-1 qemu-server: 7.4-2 smartmontools: 7.2-pve3 spiceterm: 3.2-2 swtpm: 0.8.0~bpo11+3 vncterm: 1.7-1 zfsutils-linux: 2.1.9-pve1 **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 7.3 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox VE 7.3](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_7.3 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install from USB Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For a quick how-to see [Quick installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") or check out the detailed [Installation](https://pve.proxmox.com/wiki/Installation "Installation") article. * Download via [https://www.proxmox.com/downloads](https://www.proxmox.com/downloads) * Alternative download [https://enterprise.proxmox.com/iso/](https://enterprise.proxmox.com/iso/) Update a running Proxmox Virtual Environment 7.x to latest 7.3 -------------------------------------------------------------- Here is the howto for the CLI: Check your sources.list file, should look like this: deb http://deb.debian.org/debian bullseye main contrib deb http://deb.debian.org/debian bullseye-updates main contrib # security updates deb http://security.debian.org bullseye-security main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian/pve](https://enterprise.proxmox.com/debian/pve) bullseye pve-enterprise Update your repository and packages: apt update If you get any errors, your sources.list (or your network) has a problem. Now upgrade the packages: apt dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 7.3-1 (running kernel: 5.15.74-1-pve) pve-manager: 7.3-3 (running version: 7.3-3/c3928077) pve-kernel-5.15: 7.2-14 pve-kernel-helper: 7.2-14 pve-kernel-5.15.74-1-pve: 5.15.74-1 ceph-fuse: 15.2.13-pve1 corosync: 3.1.7-pve1 criu: 3.15-1+pve-1 glusterfs-client: 9.2-1 ifupdown2: 3.1.0-1+pmx3 ksm-control-daemon: 1.4-1 libjs-extjs: 7.0.0-1 libknet1: 1.24-pve2 libproxmox-acme-perl: 1.4.2 libproxmox-backup-qemu0: 1.3.1-1 libpve-access-control: 7.2-5 libpve-apiclient-perl: 3.2-1 libpve-common-perl: 7.2-8 libpve-guest-common-perl: 4.2-3 libpve-http-server-perl: 4.1-5 libpve-storage-perl: 7.2-12 libspice-server1: 0.14.3-2.1 lvm2: 2.03.11-2.1 lxc-pve: 5.0.0-3 lxcfs: 4.0.12-pve1 novnc-pve: 1.3.0-3 proxmox-backup-client: 2.2.7-1 proxmox-backup-file-restore: 2.2.7-1 proxmox-mini-journalreader: 1.3-1 proxmox-offline-mirror-helper: 0.5.0-1 proxmox-widget-toolkit: 3.5.3 pve-cluster: 7.3-1 pve-container: 4.4-2 pve-docs: 7.3-1 pve-edk2-firmware: 3.20220526-1 pve-firewall: 4.2-7 pve-firmware: 3.5-6 pve-ha-manager: 3.5.1 pve-i18n: 2.8-1 pve-qemu-kvm: 7.1.0-4 pve-xtermjs: 4.16.0-1 qemu-server: 7.3-1 smartmontools: 7.2-pve3 spiceterm: 3.2-2 swtpm: 0.8.0~bpo11+2 vncterm: 1.7-1 zfsutils-linux: 2.1.6-pve1 pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 7.2 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox VE 7.2](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_7.2 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install from USB Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For a quick how-to see [Quick installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") or check out the detailed [Installation](https://pve.proxmox.com/wiki/Installation "Installation") article. * Download via [https://www.proxmox.com/downloads](https://www.proxmox.com/downloads) * Alternative download [https://enterprise.proxmox.com/iso/](https://enterprise.proxmox.com/iso/) Update a running Proxmox Virtual Environment 7.x to latest 7.2 -------------------------------------------------------------- Here is the howto for the CLI: Check your sources.list file, should look like this: deb http://deb.debian.org/debian bullseye main contrib deb http://deb.debian.org/debian bullseye-updates main contrib # security updates deb http://security.debian.org bullseye-security main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian/pve](https://enterprise.proxmox.com/debian/pve) bullseye pve-enterprise Update your repository and packages: apt update If you get any errors, your sources.list (or your network) has a problem. Now upgrade the packages: apt dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 7.2-1 (running kernel: 5.15.60-2-pve) pve-manager: 7.2-11 (running version: 7.2-11/b76d3178) pve-kernel-helper: 7.2-13 pve-kernel-5.15: 7.2-12 pve-kernel-5.15.60-2-pve: 5.15.60-2 ceph-fuse: 15.2.13-pve1 corosync: 3.1.5-pve2 criu: 3.15-1+pve-1 glusterfs-client: 9.2-1 ifupdown2: 3.1.0-1+pmx3 ksm-control-daemon: 1.4-1 libjs-extjs: 7.0.0-1 libknet1: 1.24-pve1 libproxmox-acme-perl: 1.4.2 libproxmox-backup-qemu0: 1.3.1-1 libpve-access-control: 7.2-4 libpve-apiclient-perl: 3.2-1 libpve-common-perl: 7.2-3 libpve-guest-common-perl: 4.1-3 libpve-http-server-perl: 4.1-4 libpve-storage-perl: 7.2-10 libspice-server1: 0.14.3-2.1 lvm2: 2.03.11-2.1 lxc-pve: 5.0.0-3 lxcfs: 4.0.12-pve1 novnc-pve: 1.3.0-3 proxmox-backup-client: 2.2.7-1 proxmox-backup-file-restore: 2.2.7-1 proxmox-mini-journalreader: 1.3-1 proxmox-widget-toolkit: 3.5.1 pve-cluster: 7.2-2 pve-container: 4.2-2 pve-docs: 7.2-2 pve-edk2-firmware: 3.20220526-1 pve-firewall: 4.2-6 pve-firmware: 3.5-4 pve-ha-manager: 3.4.0 pve-i18n: 2.7-2 pve-qemu-kvm: 7.0.0-3 pve-xtermjs: 4.16.0-1 qemu-server: 7.2-4 smartmontools: 7.2-pve3 spiceterm: 3.2-2 swtpm: 0.7.1~bpo11+1 vncterm: 1.7-1 zfsutils-linux: 2.1.6-pve1 pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 7.1 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox VE 7.1](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_7.1 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install from USB Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For a quick how-to see [Quick installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") or check out the detailed [Installation](https://pve.proxmox.com/wiki/Installation "Installation") article. * Download via [https://www.proxmox.com/downloads](https://www.proxmox.com/downloads) * Alternative download [https://enterprise.proxmox.com/iso/](https://enterprise.proxmox.com/iso/) Update a running Proxmox Virtual Environment 7.x to latest 7.1 -------------------------------------------------------------- Here is the howto for the CLI: Check your sources.list file, should look like this: deb http://deb.debian.org/debian bullseye main contrib deb http://deb.debian.org/debian bullseye-updates main contrib # security updates deb http://security.debian.org bullseye-security main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian/pve](https://enterprise.proxmox.com/debian/pve) bullseye pve-enterprise Update your repository and packages: apt update If you get any errors, your sources.list (or your network) has a problem. Now upgrade the packages: apt dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 7.1-1 (running kernel: 5.13.19-6-pve) pve-manager: 7.1-12 (running version: 7.1-12/b3c09de3) pve-kernel-helper: 7.1-14 pve-kernel-5.13: 7.1-9 pve-kernel-5.13.19-6-pve: 5.13.19-15 ceph-fuse: 15.2.13-pve1 corosync: 3.1.5-pve2 criu: 3.15-1+pve-1 glusterfs-client: 9.2-1 ifupdown2: 3.1.0-1+pmx3 ksm-control-daemon: 1.4-1 libjs-extjs: 7.0.0-1 libknet1: 1.22-pve2 libproxmox-acme-perl: 1.4.1 libproxmox-backup-qemu0: 1.2.0-1 libpve-access-control: 7.1-7 libpve-apiclient-perl: 3.2-1 libpve-common-perl: 7.1-5 libpve-guest-common-perl: 4.1-1 libpve-http-server-perl: 4.1-1 libpve-storage-perl: 7.1-1 libspice-server1: 0.14.3-2.1 lvm2: 2.03.11-2.1 lxc-pve: 4.0.11-1 lxcfs: 4.0.11-pve1 novnc-pve: 1.3.0-2 proxmox-backup-client: 2.1.5-1 proxmox-backup-file-restore: 2.1.5-1 proxmox-mini-journalreader: 1.3-1 proxmox-widget-toolkit: 3.4-7 pve-cluster: 7.1-3 pve-container: 4.1-4 pve-docs: 7.1-2 pve-edk2-firmware: 3.20210831-2 pve-firewall: 4.2-5 pve-firmware: 3.3-6 pve-ha-manager: 3.3-3 pve-i18n: 2.6-2 pve-qemu-kvm: 6.1.1-2 pve-xtermjs: 4.16.0-1 qemu-server: 7.1-4 smartmontools: 7.2-1 spiceterm: 3.2-2 swtpm: 0.7.1~bpo11+1 vncterm: 1.7-1 zfsutils-linux: 2.1.4-pve1 pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 7.0 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox VE 7.0](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_7.0 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install from USB Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For a quick how-to see [Quick installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") or check out the detailed [Installation](https://pve.proxmox.com/wiki/Installation "Installation") article. * Download via [https://www.proxmox.com/downloads](https://www.proxmox.com/downloads) * Alternative download [https://enterprise.proxmox.com/iso/](https://enterprise.proxmox.com/iso/) Update a running Proxmox Virtual Environment 7.x to latest 7.0 -------------------------------------------------------------- Here is the howto for the CLI: Check your sources.list file, should look like this: deb http://deb.debian.org/debian bullseye main contrib deb http://deb.debian.org/debian bullseye-updates main contrib # security updates deb http://security.debian.org bullseye-security main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian/pve](https://enterprise.proxmox.com/debian/pve) bullseye pve-enterprise Update your repository and packages: apt update If you get any errors, your sources.list (or your network) has a problem. Now upgrade the packages: apt dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 7.0-2 (running kernel: 5.11.22-5-pve) pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e) pve-kernel-helper: 7.1-2 pve-kernel-5.11: 7.0-8 pve-kernel-5.11.22-5-pve: 5.11.22-10 ceph-fuse: 15.2.13-pve1 corosync: 3.1.5-pve1 criu: 3.15-1+pve-1 glusterfs-client: 9.2-1 ifupdown2: 3.1.0-1+pmx3 ksm-control-daemon: 1.4-1 libjs-extjs: 7.0.0-1 libknet1: 1.22-pve1 libproxmox-acme-perl: 1.4.0 libproxmox-backup-qemu0: 1.2.0-1 libpve-access-control: 7.0-5 libpve-apiclient-perl: 3.2-1 libpve-common-perl: 7.0-10 libpve-guest-common-perl: 4.0-2 libpve-http-server-perl: 4.0-3 libpve-storage-perl: 7.0-12 libspice-server1: 0.14.3-2.1 lvm2: 2.03.11-2.1 lxc-pve: 4.0.9-4 lxcfs: 4.0.8-pve2 novnc-pve: 1.2.0-3 proxmox-backup-client: 2.0.11-1 proxmox-backup-file-restore: 2.0.11-1 proxmox-mini-journalreader: 1.2-1 proxmox-widget-toolkit: 3.3-6 pve-cluster: 7.0-3 pve-container: 4.1-1 pve-docs: 7.0-5 pve-edk2-firmware: 3.20200531-1 pve-firewall: 4.2-4 pve-firmware: 3.3-2 pve-ha-manager: 3.3-1 pve-i18n: 2.5-1 pve-qemu-kvm: 6.0.0-4 pve-xtermjs: 4.12.0-1 qemu-server: 7.0-14 smartmontools: 7.2-1 spiceterm: 3.2-2 vncterm: 1.7-1 zfsutils-linux: 2.0.5-pve1 pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Update a running Proxmox Virtual Environment 6.4 to latest 7.x -------------------------------------------------------------- Please follow exactly the upgrade guide: [Upgrade\_from\_6.x\_to\_7.0](https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0 "Upgrade from 6.x to 7.0") Proxmox Virtual Environment 7.0 beta1 (ISO Image) ================================================= Release notes: [Roadmap#Proxmox\_VE\_7.0\_beta1](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_7.0_beta1 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via [http://download.proxmox.com/iso/](http://download.proxmox.com/iso/) * [https://pve.proxmox.com/wiki/Upgrade\_from\_6.x\_to\_7.0](https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0) Proxmox Virtual Environment 6.4 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_6.4](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_6.4 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via [https://www.proxmox.com/downloads](https://www.proxmox.com/downloads) Update a running Proxmox Virtual Environment 6.x to latest 6.4 -------------------------------------------------------------- Here is the howto for the CLI: Check your sources.list file, should look like this: deb http://deb.debian.org/debian buster main contrib deb http://deb.debian.org/debian buster-updates main contrib # security updates deb http://security.debian.org buster/updates main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian/pve](https://enterprise.proxmox.com/debian/pve) buster pve-enterprise Update your repository and packages: apt update If you get any errors, your sources.list (or your network) has a problem. Now upgrade the packages: apt dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 6.4-1 (running kernel: 5.4.128-1-pve) pve-manager: 6.4-13 (running version: 6.4-13/9f411e79) pve-kernel-5.4: 6.4-5 pve-kernel-helper: 6.4-5 pve-kernel-5.4.128-1-pve: 5.4.128-2 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.1.2-pve1 criu: 3.11-3 glusterfs-client: 5.5-3 ifupdown: 0.8.35+pve1 ksm-control-daemon: 1.3-1 libjs-extjs: 6.0.1-10 libknet1: 1.20-pve1 libproxmox-acme-perl: 1.1.0 libproxmox-backup-qemu0: 1.1.0-1 libpve-access-control: 6.4-3 libpve-apiclient-perl: 3.1-3 libpve-common-perl: 6.4-3 libpve-guest-common-perl: 3.1-5 libpve-http-server-perl: 3.2-3 libpve-storage-perl: 6.4-1 libqb0: 1.0.5-1 libspice-server1: 0.14.2-4~pve6+1 lvm2: 2.03.02-pve4 lxc-pve: 4.0.6-2 lxcfs: 4.0.6-pve1 novnc-pve: 1.1.0-1 proxmox-backup-client: 1.1.13-2 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.6-1 pve-cluster: 6.4-1 pve-container: 3.3-6 pve-docs: 6.4-2 pve-edk2-firmware: 2.20200531-1 pve-firewall: 4.1-4 pve-firmware: 3.2-4 pve-ha-manager: 3.1-1 pve-i18n: 2.3-1 pve-qemu-kvm: 5.2.0-6 pve-xtermjs: 4.7.0-3 qemu-server: 6.4-2 smartmontools: 7.2-pve2 spiceterm: 3.1-1 vncterm: 1.6-2 zfsutils-linux: 2.0.5-pve1~bpo10+1 pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 6.3 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_6.3](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_6.3 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via [https://www.proxmox.com/downloads](https://www.proxmox.com/downloads) Update a running Proxmox Virtual Environment 6.x to latest 6.3 -------------------------------------------------------------- Here is the howto for the CLI: Check your sources.list file, should look like this: deb http://deb.debian.org/debian buster main contrib deb http://deb.debian.org/debian buster-updates main contrib # security updates deb http://security.debian.org buster/updates main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian/pve](https://enterprise.proxmox.com/debian/pve) buster pve-enterprise Update your repository and packages: apt update If you get any errors, your sources.list (or your network) has a problem. Now upgrade the packages: apt dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 6.3-1 (running kernel: 5.4.106-1-pve) pve-manager: 6.3-6 (running version: 6.3-6/2184247e) pve-kernel-5.4: 6.3-8 pve-kernel-helper: 6.3-8 pve-kernel-5.4.106-1-pve: 5.4.106-1 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.1.0-pve1 criu: 3.11-3 glusterfs-client: 5.5-3 ifupdown: 0.8.35+pve1 ksm-control-daemon: 1.3-1 libjs-extjs: 6.0.1-10 libknet1: 1.20-pve1 libproxmox-acme-perl: 1.0.8 libproxmox-backup-qemu0: 1.0.3-1 libpve-access-control: 6.1-3 libpve-apiclient-perl: 3.1-3 libpve-common-perl: 6.3-5 libpve-guest-common-perl: 3.1-5 libpve-http-server-perl: 3.1-1 libpve-storage-perl: 6.3-8 libqb0: 1.0.5-1 libspice-server1: 0.14.2-4~pve6+1 lvm2: 2.03.02-pve4 lxc-pve: 4.0.6-2 lxcfs: 4.0.6-pve1 novnc-pve: 1.1.0-1 proxmox-backup-client: 1.1.1-1 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.4-9 pve-cluster: 6.2-1 pve-container: 3.3-4 pve-docs: 6.3-1 pve-edk2-firmware: 2.20200531-1 pve-firewall: 4.1-3 pve-firmware: 3.2-2 pve-ha-manager: 3.1-1 pve-i18n: 2.3-1 pve-qemu-kvm: 5.2.0-5 pve-xtermjs: 4.7.0-3 qemu-server: 6.3-10 smartmontools: 7.2-pve2 spiceterm: 3.1-1 vncterm: 1.6-2 zfsutils-linux: 2.0.4-pve1 pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 6.2 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_6.2](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_6.2 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via [https://www.proxmox.com/downloads](https://www.proxmox.com/downloads) Update a running Proxmox Virtual Environment 6.x to latest 6.2 -------------------------------------------------------------- Here is the howto for the CLI: Check your sources.list file, should look like this: deb http://deb.debian.org/debian buster main contrib deb http://deb.debian.org/debian buster-updates main contrib # security updates deb http://security.debian.org buster/updates main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian/pve](https://enterprise.proxmox.com/debian/pve) buster pve-enterprise Update your repository and packages: apt update If you get any errors, your sources.list (or your network) has a problem. Now upgrade the packages: apt dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 6.2-2 (running kernel: 5.4.65-1-pve) pve-manager: 6.2-15 (running version: 6.2-15/48bd51b6) pve-kernel-5.4: 6.2-7 pve-kernel-helper: 6.2-7 pve-kernel-5.4.65-1-pve: 5.4.65-1 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.0.4-pve1 criu: 3.11-3 glusterfs-client: 5.5-3 ifupdown: 0.8.35+pve1 ksm-control-daemon: 1.3-1 libjs-extjs: 6.0.1-10 libknet1: 1.16-pve1 libproxmox-acme-perl: 1.0.5 libpve-access-control: 6.1-3 libpve-apiclient-perl: 3.0-3 libpve-common-perl: 6.2-4 libpve-guest-common-perl: 3.1-3 libpve-http-server-perl: 3.0-6 libpve-storage-perl: 6.2-9 libqb0: 1.0.5-1 libspice-server1: 0.14.2-4~pve6+1 lvm2: 2.03.02-pve4 lxc-pve: 4.0.3-1 lxcfs: 4.0.3-pve3 novnc-pve: 1.1.0-1 proxmox-backup-client: 1.0.1-1 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.3-10 pve-cluster: 6.2-1 pve-container: 3.2-2 pve-docs: 6.2-6 pve-edk2-firmware: 2.20200531-1 pve-firewall: 4.1-3 pve-firmware: 3.1-3 pve-ha-manager: 3.1-1 pve-i18n: 2.2-2 pve-qemu-kvm: 5.1.0-6 pve-xtermjs: 4.7.0-2 qemu-server: 6.2-19 smartmontools: 7.1-pve2 spiceterm: 3.1-1 vncterm: 1.6-2 zfsutils-linux: 0.8.4-pve2 pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 6.1 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_6.1](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_6.1 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via [https://www.proxmox.com/downloads](https://www.proxmox.com/downloads) Update a running Proxmox Virtual Environment 6.x to latest 6.1 -------------------------------------------------------------- Here is the howto for the CLI: Check your sources.list file, should look like this: deb http://deb.debian.org/debian buster main contrib deb http://deb.debian.org/debian buster-updates main contrib # security updates deb http://security.debian.org buster/updates main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian/pve](https://enterprise.proxmox.com/debian/pve) buster pve-enterprise Update your repository and packages: apt update If you get any errors, your sources.list (or your network) has a problem. Now upgrade the packages: apt dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 6.1-2 (running kernel: 5.3.18-3-pve) pve-manager: 6.1-8 (running version: 6.1-8/806edfe1) pve-kernel-helper: 6.1-8 pve-kernel-5.3: 6.1-6 pve-kernel-5.3.18-3-pve: 5.3.18-3 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.0.3-pve1 criu: 3.11-3 glusterfs-client: 5.5-3 ifupdown: 0.8.35+pve1 ksm-control-daemon: 1.3-1 libjs-extjs: 6.0.1-10 libknet1: 1.15-pve1 libpve-access-control: 6.0-6 libpve-apiclient-perl: 3.0-3 libpve-common-perl: 6.0-17 libpve-guest-common-perl: 3.0-5 libpve-http-server-perl: 3.0-5 libpve-storage-perl: 6.1-5 libqb0: 1.0.5-1 libspice-server1: 0.14.2-4~pve6+1 lvm2: 2.03.02-pve4 lxc-pve: 3.2.1-1 lxcfs: 3.0.3-pve60 novnc-pve: 1.1.0-1 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.1-3 pve-cluster: 6.1-4 pve-container: 3.0-23 pve-docs: 6.1-6 pve-edk2-firmware: 2.20200229-1 pve-firewall: 4.0-10 pve-firmware: 3.0-7 pve-ha-manager: 3.0-9 pve-i18n: 2.0-4 pve-qemu-kvm: 4.1.1-4 pve-xtermjs: 4.3.0-1 qemu-server: 6.1-7 smartmontools: 7.1-pve2 spiceterm: 3.1-1 vncterm: 1.6-1 zfsutils-linux: 0.8.3-pve1 pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 6.0 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_6.0](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_6.0 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via [https://www.proxmox.com/downloads](https://www.proxmox.com/downloads) Update a running Proxmox Virtual Environment 6.x to latest 6.0 -------------------------------------------------------------- Here is the howto for the CLI: Check your sources.list file, should look like this: deb http://deb.debian.org/debian buster main contrib deb http://deb.debian.org/debian buster-updates main contrib # security updates deb http://security.debian.org buster/updates main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian/pve](https://enterprise.proxmox.com/debian/pve) buster pve-enterprise Update your repository and packages: apt update If you get any errors, your sources.list (or your network) has a problem. Now upgrade the packages: apt dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 6.0-2 (running kernel: 5.0.21-5-pve) pve-manager: 6.0-12 (running version: 6.0-12/0a603350) pve-kernel-helper: 6.0-12 pve-kernel-5.0: 6.0-11 pve-kernel-5.0.21-5-pve: 5.0.21-10 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.0.2-pve4 criu: 3.11-3 glusterfs-client: 5.5-3 ksm-control-daemon: 1.3-1 libjs-extjs: 6.0.1-10 libknet1: 1.13-pve1 libpve-access-control: 6.0-3 libpve-apiclient-perl: 3.0-2 libpve-common-perl: 6.0-7 libpve-guest-common-perl: 3.0-2 libpve-http-server-perl: 3.0-3 libpve-storage-perl: 6.0-9 libqb0: 1.0.5-1 libspice-server1: 0.14.2-4~pve6+1 lvm2: 2.03.02-pve3 lxc-pve: 3.2.1-1 lxcfs: 3.0.3-pve60 novnc-pve: 1.1.0-1 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.0-9 pve-cluster: 6.0-7 pve-container: 3.0-10 pve-docs: 6.0-8 pve-edk2-firmware: 2.20190614-1 pve-firewall: 4.0-7 pve-firmware: 3.0-4 pve-ha-manager: 3.0-2 pve-i18n: 2.0-3 pve-qemu-kvm: 4.0.1-5 pve-xtermjs: 3.13.2-1 qemu-server: 6.0-13 smartmontools: 7.0-pve2 spiceterm: 3.1-1 vncterm: 1.6-1 zfsutils-linux: 0.8.2-pve2 pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Update a running Proxmox Virtual Environment 5.4 to latest 6.0 -------------------------------------------------------------- Please follow exactly the upgrade guide: [Upgrade from 5.x to 6.0](https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0 "Upgrade from 5.x to 6.0") Proxmox Virtual Environment 6.0 beta1 (ISO Image) ================================================= Release notes: [Roadmap#Proxmox\_VE\_6.0\_beta1](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_6.0_beta1 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via [http://download.proxmox.com/iso/](http://download.proxmox.com/iso/) Proxmox Virtual Environment 5.4 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_5.4](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_5.4 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via [https://www.proxmox.com/downloads](https://www.proxmox.com/downloads) Update a running Proxmox Virtual Environment 5.x to latest 5.4 -------------------------------------------------------------- Here is the howto for the CLI: Check your sources.list file, should look like this: deb http://ftp.at.debian.org/debian stretch main contrib deb http://ftp.at.debian.org/debian stretch-updates main contrib # security updates deb http://security.debian.org stretch/updates main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian/pve](https://enterprise.proxmox.com/debian/pve) stretch pve-enterprise Update your repository and packages: apt update If you get any errors, your sources.list (or your network) has a problem. Now upgrade the packages: apt dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 5.4-2 (running kernel: 4.15.18-30-pve) pve-manager: 5.4-15 (running version: 5.4-15/d0ec33c6) pve-kernel-4.15: 5.4-19 pve-kernel-4.15.18-30-pve: 4.15.18-58 corosync: 2.4.4-pve1 criu: 2.11.1-1~bpo90 glusterfs-client: 3.8.8-1 ksm-control-daemon: 1.2-2 libjs-extjs: 6.0.1-2 libpve-access-control: 5.1-12 libpve-apiclient-perl: 2.0-5 libpve-common-perl: 5.0-56 libpve-guest-common-perl: 2.0-20 libpve-http-server-perl: 2.0-14 libpve-storage-perl: 5.0-44 libqb0: 1.0.3-1~bpo9 lvm2: 2.02.168-pve6 lxc-pve: 3.1.0-7 lxcfs: 3.0.3-pve1 novnc-pve: 1.0.0-3 proxmox-widget-toolkit: 1.0-28 pve-cluster: 5.0-38 pve-container: 2.0-42 pve-docs: 5.4-2 pve-edk2-firmware: 1.20190312-1 pve-firewall: 3.0-22 pve-firmware: 2.0-7 pve-ha-manager: 2.0-9 pve-i18n: 1.1-4 pve-libspice-server1: 0.14.1-2 pve-qemu-kvm: 3.0.1-4 pve-xtermjs: 3.12.0-1 qemu-server: 5.0-56 smartmontools: 6.5+svn4324-1 spiceterm: 3.0-5 vncterm: 1.5-3 zfsutils-linux: 0.7.13-pve1~bpo2 pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 5.3 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_5.3](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_5.3 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via [https://www.proxmox.com/downloads](https://www.proxmox.com/downloads) Update a running Proxmox Virtual Environment 5.x to latest 5.3 -------------------------------------------------------------- Here is the howto for the CLI: Check your sources.list file, should look like this: deb http://ftp.at.debian.org/debian stretch main contrib deb http://ftp.at.debian.org/debian stretch-updates main contrib # security updates deb http://security.debian.org stretch/updates main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian/pve](https://enterprise.proxmox.com/debian/pve) stretch pve-enterprise Update your repository and packages: apt update If you get any errors, your sources.list (or your network) has a problem. Now upgrade the packages: apt dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 5.3-1 (running kernel: 4.15.18-12-pve) pve-manager: 5.3-11 (running version: 5.3-11/d4907f84) pve-kernel-4.15: 5.3-3 pve-kernel-4.15.18-12-pve: 4.15.18-35 corosync: 2.4.4-pve1 criu: 2.11.1-1~bpo90 glusterfs-client: 3.8.8-1 ksm-control-daemon: 1.2-2 libjs-extjs: 6.0.1-2 libpve-access-control: 5.1-3 libpve-apiclient-perl: 2.0-5 libpve-common-perl: 5.0-47 libpve-guest-common-perl: 2.0-20 libpve-http-server-perl: 2.0-12 libpve-storage-perl: 5.0-39 libqb0: 1.0.3-1~bpo9 lvm2: 2.02.168-pve6 lxc-pve: 3.1.0-3 lxcfs: 3.0.3-pve1 novnc-pve: 1.0.0-3 proxmox-widget-toolkit: 1.0-23 pve-cluster: 5.0-33 pve-container: 2.0-35 pve-docs: 5.3-3 pve-edk2-firmware: 1.20181023-1 pve-firewall: 3.0-18 pve-firmware: 2.0-6 pve-ha-manager: 2.0-8 pve-i18n: 1.0-9 pve-libspice-server1: 0.14.1-2 pve-qemu-kvm: 2.12.1-2 pve-xtermjs: 3.10.1-2 qemu-server: 5.0-47 smartmontools: 6.5+svn4324-1 spiceterm: 3.0-5 vncterm: 1.5-3 zfsutils-linux: 0.7.13-pve1~bpo2 pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 5.2 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_5.2](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_5.2 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via http [https://www.proxmox.com/downloads](https://www.proxmox.com/downloads) Update a running Proxmox Virtual Environment 5.x to latest 5.2 -------------------------------------------------------------- Here is the howto for the CLI: Check your sources.list file, should look like this: deb http://ftp.at.debian.org/debian stretch main contrib deb http://ftp.at.debian.org/debian stretch-updates main contrib # security updates deb http://security.debian.org stretch/updates main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian/pve](https://enterprise.proxmox.com/debian/pve) stretch pve-enterprise Update your repository and packages: apt update If you get any errors, your sources.list (or your network) has a problem. Now upgrade the packages: apt dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 5.2-2 (running kernel: 4.15.18-9-pve) pve-manager: 5.2-11 (running version: 5.2-11/13c2da63) pve-kernel-4.15: 5.2-12 pve-kernel-4.15.18-9-pve: 4.15.18-30 corosync: 2.4.4-pve1 criu: 2.11.1-1~bpo90 glusterfs-client: 3.8.8-1 ksm-control-daemon: 1.2-2 libjs-extjs: 6.0.1-2 libpve-access-control: 5.0-8 libpve-apiclient-perl: 2.0-5 libpve-common-perl: 5.0-41 libpve-guest-common-perl: 2.0-18 libpve-http-server-perl: 2.0-11 libpve-storage-perl: 5.0-30 libqb0: 1.0.3-1~bpo9 lvm2: 2.02.168-pve6 lxc-pve: 3.0.2+pve1-3 lxcfs: 3.0.2-2 novnc-pve: 1.0.0-2 proxmox-widget-toolkit: 1.0-20 pve-cluster: 5.0-30 pve-container: 2.0-29 pve-docs: 5.2-10 pve-edk2-firmware: 1.20181023-1 pve-firewall: 3.0-14 pve-firmware: 2.0-6 pve-ha-manager: 2.0-5 pve-i18n: 1.0-6 pve-libspice-server1: 0.14.1-1 pve-qemu-kvm: 2.12.1-1 pve-xtermjs: 1.0-5 qemu-server: 5.0-40 smartmontools: 6.5+svn4324-1 spiceterm: 3.0-5 vncterm: 1.5-3 zfsutils-linux: 0.7.12-pve1~bpo1 pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 5.1 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_5.1](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_5.1 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via http [https://www.proxmox.com/downloads](https://www.proxmox.com/downloads) Update a running Proxmox Virtual Environment 5.x to latest 5.1 -------------------------------------------------------------- Here is the howto for the CLI: Check your sources.list file, should look like this: deb http://ftp.at.debian.org/debian stretch main contrib # security updates deb http://security.debian.org stretch/updates main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian/pve](https://enterprise.proxmox.com/debian/pve) stretch pve-enterprise Update your repository and packages: apt update If you get any errors, your sources.list (or your network) has a problem. Now upgrade the packages: apt dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 5.1-42 (running kernel: 4.13.16-2-pve) pve-manager: 5.1-51 (running version: 5.1-51/96be5354) pve-kernel-4.13: 5.1-44 pve-kernel-4.13.16-2-pve: 4.13.16-47 corosync: 2.4.2-pve4 criu: 2.11.1-1~bpo90 glusterfs-client: 3.8.8-1 ksm-control-daemon: 1.2-2 libjs-extjs: 6.0.1-2 libpve-access-control: 5.0-8 libpve-apiclient-perl: 2.0-4 libpve-common-perl: 5.0-30 libpve-guest-common-perl: 2.0-14 libpve-http-server-perl: 2.0-8 libpve-storage-perl: 5.0-18 libqb0: 1.0.1-1 lvm2: 2.02.168-pve6 lxc-pve: 3.0.0-2 lxcfs: 3.0.0-1 novnc-pve: 0.6-4 proxmox-widget-toolkit: 1.0-15 pve-cluster: 5.0-25 pve-container: 2.0-21 pve-docs: 5.1-17 pve-firewall: 3.0-8 pve-firmware: 2.0-4 pve-ha-manager: 2.0-5 pve-i18n: 1.0-4 pve-libspice-server1: 0.12.8-3 pve-qemu-kvm: 2.11.1-5 pve-xtermjs: 1.0-2 qemu-server: 5.0-25 smartmontools: 6.5+svn4324-1 spiceterm: 3.0-5 vncterm: 1.5-3 zfsutils-linux: 0.7.7-pve1~bpo9 pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 5.0 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_5.0](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_5.0 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via http [https://www.proxmox.com/downloads](https://www.proxmox.com/downloads) Update a running Proxmox Virtual Environment 5.x to latest 5.0 -------------------------------------------------------------- Here is the howto for the CLI: Check your sources.list file, should look like this: deb http://ftp.at.debian.org/debian stretch main contrib # security updates deb http://security.debian.org stretch/updates main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian/pve](https://enterprise.proxmox.com/debian/pve) stretch pve-enterprise Update your repository and packages: apt update If you get any errors, your sources.list (or your network) has a problem. Now upgrade the packages: apt dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 5.0-24 (running kernel: 4.10.17-4-pve) pve-manager: 5.0-32 (running version: 5.0-32/2560e073) pve-kernel-4.10.17-4-pve: 4.10.17-24 libpve-http-server-perl: 2.0-6 lvm2: 2.02.168-pve3 corosync: 2.4.2-pve3 libqb0: 1.0.1-1 pve-cluster: 5.0-14 qemu-server: 5.0-15 pve-firmware: 2.0-2 libpve-common-perl: 5.0-18 libpve-guest-common-perl: 2.0-12 libpve-access-control: 5.0-6 libpve-storage-perl: 5.0-15 pve-libspice-server1: 0.12.8-3 vncterm: 1.5-2 pve-docs: 5.0-9 pve-qemu-kvm: 2.9.1-1 pve-container: 2.0-16 pve-firewall: 3.0-3 pve-ha-manager: 2.0-2 ksm-control-daemon: 1.2-2 glusterfs-client: 3.8.8-1 lxc-pve: 2.1.0-2 lxcfs: 2.0.7-pve4 criu: 2.11.1-1~bpo90 novnc-pve: 0.6-4 smartmontools: 6.5+svn4324-1 zfsutils-linux: 0.6.5.11-pve18~bpo90 pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 5.0 beta2 (ISO Image) ================================================= Release notes: [Roadmap#Proxmox\_VE\_5.0\_beta2](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_5.0_beta2 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via http [https://www.proxmox.com/downloads](https://www.proxmox.com/downloads) Proxmox Virtual Environment 5.0 beta1 (ISO Image) ================================================= Release notes: [Roadmap#Proxmox\_VE\_5.0\_beta1](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_5.0_beta1 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via http [https://www.proxmox.com/downloads](https://www.proxmox.com/downloads) Update a running Proxmox Virtual Environment 5.x beta to latest 5.x beta ------------------------------------------------------------------------ Here is the howto for the CLI: Check your sources.list file, should look like this: deb http://ftp.at.debian.org/debian stretch main contrib # security updates deb http://security.debian.org stretch/updates main contrib The beta repository: cat /etc/apt/sources.list.d/pve-test.list deb [http://download.proxmox.com/debian](http://download.proxmox.com/debian) stretch pvetest Update your repository and packages: apt update If you get any errors, your sources.list (or your network) has a problem. Now upgrade the packages: apt dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 5.0-9 (running kernel: 4.10.11-1-pve) pve-manager: 5.0-10 (running version: 5.0-10/0d270679) pve-kernel-4.10.11-1-pve: 4.10.11-9 libpve-http-server-perl: 2.0-4 lvm2: 2.02.168-pve2 corosync: 2.4.2-pve2 libqb0: 1.0.1-1 pve-cluster: 5.0-7 qemu-server: 5.0-4 pve-firmware: 2.0-2 libpve-common-perl: 5.0-12 libpve-guest-common-perl: 2.0-1 libpve-access-control: 5.0-4 libpve-storage-perl: 5.0-3 pve-libspice-server1: 0.12.8-3 vncterm: 1.4-1 pve-docs: 5.0-1 pve-qemu-kvm: 2.9.0-1 pve-container: 2.0-6 pve-firewall: 3.0-1 pve-ha-manager: 2.0-1 ksm-control-daemon: 1.2-2 glusterfs-client: 3.8.8-1 lxc-pve: 2.0.8-1 lxcfs: 2.0.7-pve1 criu: 2.11.1-1~bpo90 novnc-pve: 0.5-9 smartmontools: 6.5+svn4324-1 zfsutils-linux: 0.6.5.9-pve16~bpo90 pve-server:~# Proxmox Virtual Environment 4.4 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_4.4](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_4.4 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via http or bittorrent: [http://www.proxmox.com/downloads](http://www.proxmox.com/downloads) Update a running Proxmox Virtual Environment 4.x to latest 4.4 -------------------------------------------------------------- Make sure that you have uploaded a valid subscription key to your Proxmox VE host. Here is the howto for the CLI: Check your sources.list file, should look like this: deb http://ftp.at.debian.org/debian jessie main contrib # security updates deb http://security.debian.org jessie/updates main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian](https://enterprise.proxmox.com/debian) jessie pve-enterprise Update your repository and packages: apt-get update If you get any errors, your sources.list (or your network) has a problem. Before you upgrade your system, you should stop all your running VM´s and LXC containers. Now upgrade the packages: apt-get dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 4.4-112 (running kernel: 4.4.134-1-pve) pve-manager: 4.4-24 (running version: 4.4-24/08ba4d2d) pve-kernel-4.4.134-1-pve: 4.4.134-112 lvm2: 2.02.116-pve3 corosync-pve: 2.4.2-2~pve4+2 libqb0: 1.0.1-1 pve-cluster: 4.0-55 qemu-server: 4.0-115 pve-firmware: 1.1-12 libpve-common-perl: 4.0-96 libpve-access-control: 4.0-23 libpve-storage-perl: 4.0-76 pve-libspice-server1: 0.12.8-2 vncterm: 1.3-2 pve-docs: 4.4-4 pve-qemu-kvm: 2.9.1-9~pve4 pve-container: 1.0-106 pve-firewall: 2.0-33 pve-ha-manager: 1.0-41 ksm-control-daemon: 1.2-1 glusterfs-client: 3.5.2-2+deb8u3 lxc-pve: 2.0.7-4 lxcfs: 2.0.8-2~pve4 criu: 1.6.0-1 novnc-pve: 0.5-9 smartmontools: 6.5+svn4324-1~pve80 zfsutils: 0.6.5.9-pve15~bpo80 pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 4.3 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_4.3](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_4.3 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via http or bittorrent: [http://www.proxmox.com/downloads](http://www.proxmox.com/downloads) Update a running Proxmox Virtual Environment 4.x to latest 4.3 -------------------------------------------------------------- Make sure that you have uploaded a valid subscription key to your Proxmox VE host. Here is the howto for the CLI: Check your sources.list file, should look like this: deb http://ftp.at.debian.org/debian jessie main contrib # security updates deb http://security.debian.org jessie/updates main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian](https://enterprise.proxmox.com/debian) jessie pve-enterprise Update your repository and packages: apt-get update If you get any errors, your sources.list (or your network) has a problem. Before you upgrade your system, you should stop all your running VM´s and LXC containers. Now upgrade the packages: apt-get dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 4.3-72 (running kernel: 4.4.24-1-pve) pve-manager: 4.3-12 (running version: 4.3-12/6894c9d9) pve-kernel-4.4.24-1-pve: 4.4.24-72 lvm2: 2.02.116-pve3 corosync-pve: 2.4.0-1 libqb0: 1.0-1 pve-cluster: 4.0-47 qemu-server: 4.0-96 pve-firmware: 1.1-10 libpve-common-perl: 4.0-83 libpve-access-control: 4.0-19 libpve-storage-perl: 4.0-68 pve-libspice-server1: 0.12.8-1 vncterm: 1.2-1 pve-docs: 4.3-17 pve-qemu-kvm: 2.7.0-8 pve-container: 1.0-85 pve-firewall: 2.0-31 pve-ha-manager: 1.0-38 ksm-control-daemon: 1.2-1 glusterfs-client: 3.5.2-2+deb8u2 lxc-pve: 2.0.6-1 lxcfs: 2.0.5-pve1 criu: 1.6.0-1 novnc-pve: 0.5-8 smartmontools: 6.5+svn4324-1~pve80 zfsutils: 0.6.5.8-pve13~bpo80 pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 4.2 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_4.2](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_4.2 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via http or bittorrent: [http://www.proxmox.com/downloads](http://www.proxmox.com/downloads) Update a running Proxmox Virtual Environment 4.x to latest 4.2 -------------------------------------------------------------- Make sure that you have uploaded a valid subscription key to your Proxmox VE host. Here is the howto for the CLI: Check your sources.list file, should look like this: deb http://ftp.at.debian.org/debian jessie main contrib # security updates deb http://security.debian.org jessie/updates main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian](https://enterprise.proxmox.com/debian) jessie pve-enterprise Update your repository and packages: apt-get update If you get any errors, your sources.list (or your network) has a problem. Before you upgrade your system, you should stop all your running VM´s and LXC containers. Now upgrade the packages: apt-get dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 4.2-64 (running kernel: 4.4.16-1-pve) pve-manager: 4.2-18 (running version: 4.2-18/158720b9) pve-kernel-4.4.16-1-pve: 4.4.16-64 lvm2: 2.02.116-pve3 corosync-pve: 2.4.0-1 libqb0: 1.0-1 pve-cluster: 4.0-44 qemu-server: 4.0-86 pve-firmware: 1.1-9 libpve-common-perl: 4.0-72 libpve-access-control: 4.0-19 libpve-storage-perl: 4.0-57 pve-libspice-server1: 0.12.8-1 vncterm: 1.2-1 pve-qemu-kvm: 2.6.1-2 pve-container: 1.0-73 pve-firewall: 2.0-29 pve-ha-manager: 1.0-33 ksm-control-daemon: 1.2-1 glusterfs-client: 3.5.2-2+deb8u2 lxc-pve: 2.0.4-1 lxcfs: 2.0.3-pve1 cgmanager: 0.39-pve1 criu: 1.6.0-1 novnc-pve: 0.5-8 zfsutils: 0.6.5.7-pve10~bpo80 pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 4.1 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_4.1](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_4.1 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via http or bittorrent: [http://www.proxmox.com/downloads](http://www.proxmox.com/downloads) Update a running Proxmox Virtual Environment 4.x to latest 4.1 -------------------------------------------------------------- Make sure that you have uploaded a valid subscription key to your Proxmox VE host. Here is the howto for the CLI: Check your sources.list file, should look like this: deb http://ftp.at.debian.org/debian jessie main contrib # security updates deb http://security.debian.org jessie/updates main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian](https://enterprise.proxmox.com/debian) jessie pve-enterprise Update your repository and packages: apt-get update If you get any errors, your sources.list (or your network) has a problem. Before you upgrade your system, you should stop all your running VM´s and LXC containers. Now upgrade the packages: apt-get dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v proxmox-ve: 4.1-39 (running kernel: 4.2.8-1-pve) pve-manager: 4.1-22 (running version: 4.1-22/aca130cf) pve-kernel-4.2.8-1-pve: 4.2.8-39 lvm2: 2.02.116-pve2 corosync-pve: 2.3.5-2 libqb0: 1.0-1 pve-cluster: 4.0-36 qemu-server: 4.0-64 pve-firmware: 1.1-7 libpve-common-perl: 4.0-54 libpve-access-control: 4.0-13 libpve-storage-perl: 4.0-45 pve-libspice-server1: 0.12.5-2 vncterm: 1.2-1 pve-qemu-kvm: 2.5-9 pve-container: 1.0-52 pve-firewall: 2.0-22 pve-ha-manager: 1.0-25 ksm-control-daemon: 1.2-1 glusterfs-client: 3.5.2-2+deb8u1 lxc-pve: 1.1.5-7 lxcfs: 2.0.0-pve2 cgmanager: 0.39-pve1 criu: 1.6.0-1 zfsutils: 0.6.5-pve7~jessie pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 4.0 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_4.0](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_4.0 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via http or bittorrent: [http://www.proxmox.com/downloads](http://www.proxmox.com/downloads) Update a running Proxmox Virtual Environment 4.x to latest 4.0 -------------------------------------------------------------- Make sure that you have uploaded a valid subscription key to your Proxmox VE host. Here is the howto for the CLI: Check your sources.list file, should look like this: deb http://ftp.at.debian.org/debian jessie main contrib # security updates deb http://security.debian.org jessie/updates main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian](https://enterprise.proxmox.com/debian) jessie pve-enterprise Update your repository and packages: apt-get update If you get any errors, your sources.list (or your network) has a problem. Before you update your system, you should stop all your running VM´s. Now upgrade the packages: apt-get dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~#pveversion -v proxmox-ve: 4.0-21 (running kernel: 4.2.3-2-pve) pve-manager: 4.0-57 (running version: 4.0-57/cc7c2b53) pve-kernel-4.2.3-2-pve: 4.2.3-21 lvm2: 2.02.116-pve1 corosync-pve: 2.3.5-1 libqb0: 0.17.2-1 pve-cluster: 4.0-24 qemu-server: 4.0-35 pve-firmware: 1.1-7 libpve-common-perl: 4.0-36 libpve-access-control: 4.0-9 libpve-storage-perl: 4.0-29 pve-libspice-server1: 0.12.5-2 vncterm: 1.2-1 pve-qemu-kvm: 2.4-12 pve-container: 1.0-21 pve-firewall: 2.0-13 pve-ha-manager: 1.0-13 ksm-control-daemon: 1.2-1 glusterfs-client: 3.5.2-2+deb8u1 lxc-pve: 1.1.4-3 lxcfs: 0.10-pve2 cgmanager: 0.39-pve1 criu: 1.6.0-1 zfsutils: 0.6.5-pve6~jessie pve-server:~# **Important Note** If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Update a running Proxmox Virtual Environment 3.x to latest 4.0 -------------------------------------------------------------- See [Upgrade from 3.x to 4.0](https://pve.proxmox.com/wiki/Upgrade_from_3.x_to_4.0 "Upgrade from 3.x to 4.0") Proxmox Virtual Environment 3.4 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_3.4](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_3.4 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via http or bittorrent: [http://www.proxmox.com/downloads](http://www.proxmox.com/downloads) Update a running Proxmox Virtual Environment 3.x to latest 3.4 -------------------------------------------------------------- Make sure that you have uploaded a valid subscription key to your Proxmox VE host. All updates should be applied via CLI only (if you tried via GUI, please check this [forum post](http://forum.proxmox.com/threads/21045-grub2-update-problems-%28GUI-only%29-leading-to-not-correctly-installed-packages) ). here is the howto for the CLI: Check your sources.list file, should look like this: deb http://http.at.debian.org/debian wheezy main contrib # security updates deb http://security.debian.org/ wheezy/updates main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian](https://enterprise.proxmox.com/debian) wheezy pve-enterprise Update your repository and packages: apt-get update If you get any errors, your sources.list (or your network) has a problem. Before you update your system, you should stop all your running VM´s. Now upgrade the packages: apt-get dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~#pveversion -v proxmox-ve-2.6.32: 3.4-185 (running kernel: 2.6.32-48-pve) pve-manager: 3.4-16 (running version: 3.4-16/40ccc11c) pve-kernel-2.6.32-48-pve: 2.6.32-185 lvm2: 2.02.98-pve4 clvm: 2.02.98-pve4 corosync-pve: 1.4.7-1 openais-pve: 1.1.4-3 libqb0: 0.11.1-2 redhat-cluster-pve: 3.2.0-2 resource-agents-pve: 3.9.2-4 fence-agents-pve: 4.0.10-3 pve-cluster: 3.0-20 qemu-server: 3.4-9 pve-firmware: 1.1-6 libpve-common-perl: 3.0-27 libpve-access-control: 3.0-16 libpve-storage-perl: 3.0-35 pve-libspice-server1: 0.12.4-3 vncterm: 1.1-8 vzctl: 4.0-1pve6 vzprocps: 2.0.11-2 vzquota: 3.1-2 pve-qemu-kvm: 2.2-28 ksm-control-daemon: 1.1-1 glusterfs-client: 3.5.2-1 pve-server:~# **Important Note** Due to changes in our repositories in 3.1 you need to check your apt configuration. If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 3.3 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_3.3](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_3.3 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via http or bittorrent: [http://www.proxmox.com/downloads](http://www.proxmox.com/downloads) Update a running Proxmox Virtual Environment 3.x to latest 3.3 -------------------------------------------------------------- Make sure that you have uploaded a valid subscription key to your Proxmox VE host. All updates can be applied via GUI or via CLI, here is the howto for the CLI: Check your sources.list file, should look like this: deb http://http.at.debian.org/debian wheezy main contrib # security updates deb http://security.debian.org/ wheezy/updates main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian](https://enterprise.proxmox.com/debian) wheezy pve-enterprise Update your repository and packages: apt-get update If you get any errors, your sources.list (or your network) has a problem. Before you update your system, you should stop all your running VM´s. Now upgrade the packages: apt-get dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~#pveversion -v proxmox-ve-2.6.32: 3.3-139 (running kernel: 2.6.32-34-pve) pve-manager: 3.3-5 (running version: 3.3-5/bfebec03) pve-kernel-2.6.32-34-pve: 2.6.32-139 lvm2: 2.02.98-pve4 clvm: 2.02.98-pve4 corosync-pve: 1.4.7-1 openais-pve: 1.1.4-3 libqb0: 0.11.1-2 redhat-cluster-pve: 3.2.0-2 resource-agents-pve: 3.9.2-4 fence-agents-pve: 4.0.10-1 pve-cluster: 3.0-15 qemu-server: 3.3-3 pve-firmware: 1.1-3 libpve-common-perl: 3.0-19 libpve-access-control: 3.0-15 libpve-storage-perl: 3.0-25 pve-libspice-server1: 0.12.4-3 vncterm: 1.1-8 vzctl: 4.0-1pve6 vzprocps: 2.0.11-2 vzquota: 3.1-2 pve-qemu-kvm: 2.1-10 ksm-control-daemon: 1.1-1 glusterfs-client: 3.5.2-1 pve-server:~# **Important Note** Due to changes in our repositories in 3.1 you need to check your apt configuration. If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 3.2 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_3.2](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_3.2 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via http or bittorrent: [http://www.proxmox.com/downloads](http://www.proxmox.com/downloads) Update a running Proxmox Virtual Environment 3.x to latest 3.2 -------------------------------------------------------------- Make sure that you have uploaded a valid subscription key to your Proxmox VE host. All updates can be applied via GUI or via CLI, here is the howto for the CLI: Check your sources.list file, should look like this: deb http://http.at.debian.org/debian wheezy main contrib # security updates deb http://security.debian.org/ wheezy/updates main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian](https://enterprise.proxmox.com/debian) wheezy pve-enterprise Update your repository and packages: apt-get update If you get any errors, your sources.list (or your network) has a problem. Before you update your system, you should stop all your running VM´s. Now upgrade the packages: apt-get dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~#pveversion -v proxmox-ve-2.6.32: 3.2-132 (running kernel: 2.6.32-31-pve) pve-manager: 3.2-4 (running version: 3.2-4/e24a91c1) pve-kernel-2.6.32-31-pve: 2.6.32-132 lvm2: 2.02.98-pve4 clvm: 2.02.98-pve4 corosync-pve: 1.4.5-1 openais-pve: 1.1.4-3 libqb0: 0.11.1-2 redhat-cluster-pve: 3.2.0-2 resource-agents-pve: 3.9.2-4 fence-agents-pve: 4.0.5-1 pve-cluster: 3.0-12 qemu-server: 3.1-16 pve-firmware: 1.1-3 libpve-common-perl: 3.0-18 libpve-access-control: 3.0-11 libpve-storage-perl: 3.0-19 pve-libspice-server1: 0.12.4-3 vncterm: 1.1-6 vzctl: 4.0-1pve5 vzprocps: 2.0.11-2 vzquota: 3.1-2 pve-qemu-kvm: 1.7-8 ksm-control-daemon: 1.1-1 glusterfs-client: 3.4.2-1 pve-server:~# **Important Note** Due to changes in our repositories in 3.1 you need to check your apt configuration. If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 3.1 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_3.1](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_3.1 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via http or bittorrent: [http://www.proxmox.com/downloads](http://www.proxmox.com/downloads) Update a running Proxmox Virtual Environment 3.x to latest 3.1 -------------------------------------------------------------- Make sure that you have uploaded a valid subscription key to your Proxmox VE host. Check your sources.list file, should look like this: deb http://http.at.debian.org/debian wheezy main contrib # security updates deb http://security.debian.org/ wheezy/updates main contrib The enterprise repository: cat /etc/apt/sources.list.d/pve-enterprise.list deb [https://enterprise.proxmox.com/debian](https://enterprise.proxmox.com/debian) wheezy pve-enterprise Update your repository and packages: apt-get update If you get any errors, your sources.list (or your network) has a problem. Before you update your system, you should stop all your running VM´s. Now upgrade the packages: apt-get dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~#pveversion -v proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve) pve-manager: 3.1-24 (running version: 3.1-24/060bd5a6) pve-kernel-2.6.32-26-pve: 2.6.32-114 lvm2: 2.02.98-pve4 clvm: 2.02.98-pve4 corosync-pve: 1.4.5-1 openais-pve: 1.1.4-3 libqb0: 0.11.1-2 redhat-cluster-pve: 3.2.0-2 resource-agents-pve: 3.9.2-4 fence-agents-pve: 4.0.0-2 pve-cluster: 3.0-8 qemu-server: 3.1-8 pve-firmware: 1.0-23 libpve-common-perl: 3.0-9 libpve-access-control: 3.0-8 libpve-storage-perl: 3.0-18 pve-libspice-server1: 0.12.4-2 vncterm: 1.1-6 vzctl: 4.0-1pve4 vzprocps: 2.0.11-2 vzquota: 3.1-2 pve-qemu-kvm: 1.4-17 ksm-control-daemon: 1.1-1 glusterfs-client: 3.4.1-1 pve-server:~# **Important Note** Due to changes in our repositories you need to update your apt configuration. If you already use your Proxmox VE Subscription Key, access to the Enterprise repository works out of the box. For more details about the Proxmox VE repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Proxmox Virtual Environment 3.0 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_3.0](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_3.0 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via http or bittorrent: [http://www.proxmox.com/downloads](http://www.proxmox.com/downloads) Update a running Proxmox Virtual Environment 3.x to latest 3.0 -------------------------------------------------------------- Check your sources.list file, should look like this: deb http://http.at.debian.org/debian wheezy main contrib # PVE packages provided by proxmox.com deb http://download.proxmox.com/debian wheezy pve # security updates deb http://security.debian.org/ wheezy/updates main contrib Update your repository and packages: apt-get update If you get any errors, your sources.list (or your network) has a problem. Before you update your system, you should stop all your running VM´s. Now upgrade the packages: apt-get dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~#pveversion -v pve-manager: 3.0-23 (pve-manager/3.0/957f0862) running kernel: 2.6.32-22-pve proxmox-ve-2.6.32: 3.0-107 pve-kernel-2.6.32-22-pve: 2.6.32-107 lvm2: 2.02.95-pve3 clvm: 2.02.95-pve3 corosync-pve: 1.4.5-1 openais-pve: 1.1.4-3 libqb0: 0.11.1-2 redhat-cluster-pve: 3.2.0-2 resource-agents-pve: 3.9.2-4 fence-agents-pve: 4.0.0-1 pve-cluster: 3.0-4 qemu-server: 3.0-20 pve-firmware: 1.0-23 libpve-common-perl: 3.0-4 libpve-access-control: 3.0-4 libpve-storage-perl: 3.0-8 vncterm: 1.1-4 vzctl: 4.0-1pve3 vzprocps: 2.0.11-2 vzquota: 3.1-2 pve-qemu-kvm: 1.4-13 ksm-control-daemon: 1.1-1 pve-server:~# Update a running Proxmox Virtual Environment 2.3 to 3.0 ------------------------------------------------------- See [Upgrade from 2.3 to 3.0](https://pve.proxmox.com/wiki/Upgrade_from_2.3_to_3.0 "Upgrade from 2.3 to 3.0") Proxmox Virtual Environment 2.3 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_2.3](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_2.3 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via http: [Proxmox VE 2.3](http://www.proxmox.com/downloads/proxmox-ve/iso-images/136-proxmox-ve-2) * Download via bittorrent: [Proxmox VE 2.3](http://www.proxmox.com/downloads/proxmox-ve/iso-images/137-proxmox-ve-2) (MD5SUM for the ISO is e27f57028bde04b67cfb8182499124e0) Update a running Proxmox Virtual Environment 2.x to latest 2.3 -------------------------------------------------------------- Check your sources.list file, should look like this: deb http://http.at.debian.org/debian squeeze main contrib # PVE packages provided by proxmox.com deb http://download.proxmox.com/debian squeeze pve # security updates deb http://security.debian.org/ squeeze/updates main contrib Update your repository and packages: apt-get update If you get any errors, your sources.list (or your network) has a problem. Before you update your system, you should stop all your running VM´s. Now upgrade the packages: apt-get dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~#pveversion -v pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1) running kernel: 2.6.32-19-pve proxmox-ve-2.6.32: 2.3-96 pve-kernel-2.6.32-19-pve: 2.6.32-96 lvm2: 2.02.95-1pve2 clvm: 2.02.95-1pve2 corosync-pve: 1.4.4-4 openais-pve: 1.1.4-2 libqb: 0.10.1-2 redhat-cluster-pve: 3.1.93-2 resource-agents-pve: 3.9.2-3 fence-agents-pve: 3.1.9-1 pve-cluster: 1.0-36 qemu-server: 2.3-20 pve-firmware: 1.0-21 libpve-common-perl: 1.0-49 libpve-access-control: 1.0-26 libpve-storage-perl: 2.3-7 vncterm: 1.0-4 vzctl: 4.0-1pve2 vzprocps: 2.0.11-2 vzquota: 3.1-1 pve-qemu-kvm: 1.4-10 ksm-control-daemon: 1.1-1 pve-server:~# Proxmox Virtual Environment 2.2 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_2.2](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_2.2 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via http: [Proxmox VE 2.2](http://www.proxmox.com/downloads/proxmox-ve/iso-images/132-proxmox-ve-2) * Download via bittorrent: [Proxmox VE 2.2](http://www.proxmox.com/downloads/proxmox-ve/iso-images/133-proxmox-ve-2) (MD5SUM for the ISO is 6a4ba41035dc32da36a08ec421ea6fb2) Update a running Proxmox Virtual Environment 2.x to latest 2.2 -------------------------------------------------------------- Check your sources.list file, should look like this: deb http://http.at.debian.org/debian squeeze main contrib # PVE packages provided by proxmox.com deb http://download.proxmox.com/debian squeeze pve2.2 # security updates deb http://security.debian.org/ squeeze/updates main contrib Update your repository and packages: apt-get update If you get any errors, your sources.list (or your network) has a problem. Before you update your system, you should stop all your running VM´s. Now upgrade the packages: apt-get dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~#pveversion -v pve-manager: 2.2-32 (pve-manager/2.2/3089a616) running kernel: 2.6.32-17-pve proxmox-ve-2.6.32: 2.2-83 pve-kernel-2.6.32-17-pve: 2.6.32-83 lvm2: 2.02.95-1pve2 clvm: 2.02.95-1pve2 corosync-pve: 1.4.4-1 openais-pve: 1.1.4-2 libqb: 0.10.1-2 redhat-cluster-pve: 3.1.93-2 resource-agents-pve: 3.9.2-3 fence-agents-pve: 3.1.9-1 pve-cluster: 1.0-34 qemu-server: 2.0-71 pve-firmware: 1.0-21 libpve-common-perl: 1.0-40 libpve-access-control: 1.0-25 libpve-storage-perl: 2.0-36 vncterm: 1.0-3 vzctl: 4.0-1pve2 vzprocps: 2.0.11-2 vzquota: 3.1-1 pve-qemu-kvm: 1.3-10 ksm-control-daemon: 1.1-1 pve-server:~# Proxmox Virtual Environment 2.1 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_2.1](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_2.1 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via http: [Proxmox VE 2.1](http://www.proxmox.com/downloads/proxmox-ve/iso-images/114-proxmox-ve-2) * Download via bittorrent: [Proxmox VE 2.1](http://www.proxmox.com/downloads/proxmox-ve/iso-images/115-proxmox-ve-2) (MD5SUM for the ISO is 940919e832e64c29e67d89233a11b88b) Update a running Proxmox Virtual Environment 2.x to latest 2.1 -------------------------------------------------------------- Check your sources.list file, should look like this: deb http://ftp.at.debian.org/debian squeeze main contrib # PVE packages provided by proxmox.com deb http://download.proxmox.com/debian squeeze pve2.1 # security updates deb http://security.debian.org/ squeeze/updates main contrib Update your repository and packages: apt-get update If you get any errors, your sources.list (or your network) has a problem. Before you update your system, you should stop all your running VM´s. Now upgrade the packages: apt-get dist-upgrade Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~#pveversion -v pve-manager: 2.1-14 (pve-manager/2.1/f32f3f46) running kernel: 2.6.32-14-pve proxmox-ve-2.6.32: 2.1-74 pve-kernel-2.6.32-14-pve: 2.6.32-74 lvm2: 2.02.95-1pve2 clvm: 2.02.95-1pve2 corosync-pve: 1.4.3-1 openais-pve: 1.1.4-2 libqb: 0.10.1-2 redhat-cluster-pve: 3.1.92-3 resource-agents-pve: 3.9.2-3 fence-agents-pve: 3.1.8-1 pve-cluster: 1.0-27 qemu-server: 2.0-49 pve-firmware: 1.0-18 libpve-common-perl: 1.0-30 libpve-access-control: 1.0-24 libpve-storage-perl: 2.0-31 vncterm: 1.0-3 vzctl: 3.0.30-2pve5 vzprocps: 2.0.11-2 vzquota: 3.0.12-3 pve-qemu-kvm: 1.1-8 ksm-control-daemon: 1.1-1 pve-server:~# Update a running Proxmox Virtual Environment 1.9 to 2.x ------------------------------------------------------- See [Upgrade\_from\_1.9\_to\_2.0](https://pve.proxmox.com/wiki/Upgrade_from_1.9_to_2.0 "Upgrade from 1.9 to 2.0") Proxmox Virtual Environment 2.0 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_2.0](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_2.0 "Roadmap") Download the ISO image and burn it to CD-ROM or [Install\_from\_USB\_Stick](https://pve.proxmox.com/wiki/Install_from_USB_Stick "Install from USB Stick") and boot your server from CD-ROM or USB stick. For details see [Quick\_installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") * Download via http: [Proxmox VE 2.0](http://www.proxmox.com/downloads/proxmox-ve/iso-images/112-proxmox-ve-2) * Download via bittorrent: [Proxmox VE 2.0](http://www.proxmox.com/downloads/proxmox-ve/iso-images/113-proxmox-ve-2) (MD5SUM for the ISO is 5c1bf16973ee06a293be2bd2b2c648fa) Update a running Proxmox Virtual Environment to 2.0 --------------------------------------------------- See [Upgrade\_from\_1.9\_to\_2.0](https://pve.proxmox.com/wiki/Upgrade_from_1.9_to_2.0 "Upgrade from 1.9 to 2.0") Proxmox Virtual Environment 1.9 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_1.9](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_1.9 "Roadmap") Download the ISO image and burn it to CD-ROM and boot your server from CD-ROM. For details see [Installation](https://pve.proxmox.com/wiki/Installation "Installation") * Download via http: [Proxmox VE 1.9](http://www.proxmox.com/downloads/proxmox-ve/iso-images/98-proxmox-ve-1) * Download via bittorrent: [Proxmox VE 1.9](http://www.proxmox.com/downloads/proxmox-ve/iso-images/99-proxmox-ve-1) (MD5SUM for the ISO is 910f69b2ab450a304a4bae835ffa858e) Update a running Proxmox Virtual Environment to 1.9 --------------------------------------------------- Check your sources.list file, should look like this: deb http://ftp.debian.org/debian lenny main contrib # PVE packages provided by proxmox.com deb http://download.proxmox.com/debian lenny pve # security updates deb http://security.debian.org/ lenny/updates main contrib Update your repository and packages: aptitude update If you get any errors, your sources.list (or your network) has a problem. Before you update your system, you should stop all your running VM´s. Now upgrade the packages: aptitude full-upgrade Choose your preferred Proxmox VE kernel branch, see [Proxmox\_VE\_Kernel](https://pve.proxmox.com/wiki/Proxmox_VE_Kernel "Proxmox VE Kernel") If you want to switch to the 2.6.32 kernel branch just install the Proxmox VE virtual package for 2.6.32: aptitude install proxmox-ve-2.6.32 Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~#pveversion -v pve-manager: 1.9-26 (pve-manager/1.9/6567) running kernel: 2.6.32-7-pve proxmox-ve-2.6.32: 1.9-55+ovzfix-2 pve-kernel-2.6.32-7-pve: 2.6.32-55+ovzfix-2 qemu-server: 1.1-32 pve-firmware: 1.0-15 libpve-storage-perl: 1.0-19 vncterm: 0.9-2 vzctl: 3.0.29-3pve1 vzdump: 1.2-16 vzprocps: 2.0.11-2 vzquota: 3.0.11-1 pve-qemu-kvm: 0.15.0-2 ksm-control-daemon: 1.0-6 pve-server:~# Proxmox Virtual Environment 1.8 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_1.8](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_1.8 "Roadmap") Download the ISO image and burn it to CD-ROM and boot your server from CD-ROM. For details see [Installation](https://pve.proxmox.com/wiki/Installation "Installation") * Download via http: [Proxmox VE 1.8](http://www.proxmox.com/downloads/proxmox-ve/iso-images/89-proxmox-ve-1) * Download via bittorrent: [Proxmox VE 1.8](http://www.proxmox.com/downloads/proxmox-ve/iso-images/90-proxmox-ve-1) (MD5SUM for the ISO is 82f2dbab4ca5e467278e0717ed7c861f) Update a running Proxmox Virtual Environment to 1.8 --------------------------------------------------- Check your sources.list file, should look like this: deb http://ftp.debian.org/debian lenny main contrib # PVE packages provided by proxmox.com deb http://download.proxmox.com/debian lenny pve # security updates deb http://security.debian.org/ lenny/updates main contrib Update your repository and packages: aptitude update If you get any errors, your sources.list (or your network) has a problem. Before you update your system, you should stop all your running VM´s. Now upgrade the packages: aptitude safe-upgrade Choose your preferred Proxmox VE kernel branch, see [Proxmox\_VE\_Kernel](https://pve.proxmox.com/wiki/Proxmox_VE_Kernel "Proxmox VE Kernel") If you want to switch to the 2.6.32 kernel branch just install the Proxmox VE virtual package for 2.6.32: aptitude install proxmox-ve-2.6.32 Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v pve-manager: 1.8-18 (pve-manager/1.8/6070) running kernel: 2.6.32-4-pve proxmox-ve-2.6.32: 1.8-33 pve-kernel-2.6.32-4-pve: 2.6.32-33 qemu-server: 1.1-30 pve-firmware: 1.0-11 libpve-storage-perl: 1.0-17 vncterm: 0.9-2 vzctl: 3.0.27-1pve1 vzdump: 1.2-13 vzprocps: 2.0.11-2 vzquota: 3.0.11-1 pve-qemu-kvm: 0.14.1-1 ksm-control-daemon: 1.0-6 pve-server:~# Proxmox Virtual Environment 1.7 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_1.7](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_1.7 "Roadmap") Download the ISO image and burn it to CD-ROM and boot your server from CD-ROM. For details see [Installation](https://pve.proxmox.com/wiki/Installation "Installation") * Download via http: [Proxmox VE 1.7](http://www.proxmox.com/downloads/proxmox-ve/iso-images/83-proxmox-ve-1) * Download via bittorrent: [Proxmox VE 1.7](http://www.proxmox.com/downloads/proxmox-ve/iso-images/84-proxmox-ve-1) (MD5SUM for the ISO is 5d9d02499c96f89fd93e58cf010e4282) Update a running Proxmox Virtual Environment to 1.7 --------------------------------------------------- Check your sources.list file, should look like this: deb http://ftp.debian.org/debian lenny main contrib # PVE packages provided by proxmox.com deb http://download.proxmox.com/debian lenny pve # security updates deb http://security.debian.org/ lenny/updates main contrib Update your repository and packages: aptitude update If you get any errors, your sources.list (or your network) has a problem. Before you update your system, you should stop all your running VM´s. Now upgrade the packages: aptitude safe-upgrade If you want to switch to the 2.6.32 kernel branch just install the Proxmox VE virtual package for 2.6.32: aptitude install proxmox-ve-2.6.32 Reboot to activate the new Kernel, to check if you got all packages, run 'pveversion -v' and compare your output (all packages should have equal or higher version numbers): pve-server:~# pveversion -v pve-manager: 1.7-10 (pve-manager/1.7/5323) running kernel: 2.6.32-4-pve proxmox-ve-2.6.32: 1.7-30 pve-kernel-2.6.32-4-pve: 2.6.32-30 qemu-server: 1.1-28 pve-firmware: 1.0-10 libpve-storage-perl: 1.0-16 vncterm: 0.9-2 vzctl: 3.0.24-1pve4 vzdump: 1.2-10 vzprocps: 2.0.11-1dso2 vzquota: 3.0.11-1 pve-qemu-kvm: 0.13.0-3 ksm-control-daemon: 1.0-4 pve-server:~# Proxmox Virtual Environment 1.6 (ISO Image updated on 18.10.2010) ================================================================= Release notes: [Roadmap#Proxmox\_VE\_1.6\_.28updated.29\_-\_ISO\_Installer\_with\_2.6.32\_Kernel\_with\_OpenVZ\_including\_KVM\_0.12.5](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_1.6_.28updated.29_-_ISO_Installer_with_2.6.32_Kernel_with_OpenVZ_including_KVM_0.12.5 "Roadmap") Download the ISO image (Note: update to the ISO on 18.10.2010) burn it to CD-ROM and boot your server from CD-ROM. For details see [Installation](https://pve.proxmox.com/wiki/Installation "Installation") * Download via http: [Proxmox VE 1.6](http://www.proxmox.com/downloads/proxmox-ve/iso-images/81-proxmox-ve-1) * Download via bittorrent: [Proxmox VE 1.6](http://www.proxmox.com/downloads/proxmox-ve/iso-images/82-proxmox-ve-1) (MD5SUM for the ISO is 83be9d05f7bf8f2f438659f2ec891e56) **Important note** If you run windows KVM guests your operating system will recognize some hardware changes on the first boot. Under some circumstances reactivation of your windows license can be necessary. Proxmox VE 1.5 - New Kernel 2.6.24 and 2.6.32 (17.5.2010) ========================================================= Release notes: [Roadmap#Proxmox\_VE\_1.5\_-\_New\_Kernel\_2.6.24\_and\_2.6.32.2C\_including\_KVM\_0.12.4\_and\_gPXE](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_1.5_-_New_Kernel_2.6.24_and_2.6.32.2C_including_KVM_0.12.4_and_gPXE "Roadmap") Update a running Proxmox Virtual Environment 1.5 ------------------------------------------------ Update your repository and packages: aptitude update If you get any errors, your sources.list (or your network) has a problem. Before you update your system, you should stop all your running VM´s. Now you can install the new Proxmox VE virtual package: aptitude upgrade && aptitude install proxmox-ve-2.6.32 (alternative: proxmox-ve-2.6.24) Proxmox Virtual Environment 1.5 (ISO Image) - updated on 3.2.2010 ================================================================= Release notes: [Roadmap#Proxmox\_VE\_1.5](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_1.5 "Roadmap") Download the ISO image, burn it to CD-ROM and boot your server from CD-ROM. For details see [Installation](https://pve.proxmox.com/wiki/Installation "Installation") * Download via http: [Proxmox VE 1.5](http://www.proxmox.com/downloads/proxmox-ve/iso-images/37-proxmox-ve-1) * Download via bittorrent: [Proxmox VE 1.5](http://www.proxmox.com/downloads/proxmox-ve/iso-images/39-proxmox-ve-1) (MD5SUM for the ISO is 9f886782022b3408a625cb35ea34bab2) Update a running Proxmox Virtual Environment 1.x to 1.5 ------------------------------------------------------- Check your sources.list file: nano /etc/apt/sources.list **Note:** If you still run a Debian Etch based system (0.9, 1.0 or 1.1) think of a re-installation or do a dist-upgrade. deb http://ftp.debian.org/debian lenny main contrib # PVE packages provided by proxmox.com deb http://download.proxmox.com/debian lenny pve # security updates deb http://security.debian.org/ lenny/updates main contrib Update your repository and packages: aptitude update If you get any errors, your sources.list (or your network) has a problem. Before you update your system, you should stop all your running VM´s. Now you can install the new Proxmox VE virtual package: aptitude upgrade && aptitude install proxmox-ve-2.6.18 (alternative: proxmox-ve-2.6.24 or proxmox-ve-2.6.32) Now, check the bootloader grub to make sure that the system boots the right kernel. nano /boot/grub/menu.lst Finally reboot into your new kernel and check if you got the latest Proxmox VE packages with 'pveversion -v': pveversion -v pve-manager: 1.5-7 (pve-manager/1.5/4660) running kernel: 2.6.18-2-pve proxmox-ve-2.6.18: 1.5-5 pve-kernel-2.6.18-2-pve: 2.6.18-5 qemu-server: 1.1-11 pve-firmware: 1.0-3 libpve-storage-perl: 1.0-10 vncterm: 0.9-2 vzctl: 3.0.23-1pve8 vzdump: 1.2-5 vzprocps: 2.0.11-1dso2 vzquota: 3.0.11-1 pve-qemu-kvm-2.6.18: 0.9.1-5 Proxmox Virtual Environment 1.4 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_1.4](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_1.4 "Roadmap") Download the ISO image, burn it to CD-ROM and boot your server from CD-ROM. For details see [Installation](https://pve.proxmox.com/wiki/Installation "Installation") * Download via http: [Proxmox VE 1.4](http://www.proxmox.com/downloads/proxmox-ve/iso-images/36-proxmox-ve-1) (MD5SUM for the ISO is 0bef854dcca1718f73ff64e383df280a) Proxmox Virtual Environment 1.4 beta2 ===================================== Release notes: [Roadmap#Proxmox\_VE\_1.4\_beta2](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_1.4_beta2 "Roadmap") This is the second beta release and therefore not intended for production systems. Download the ISO image, burn it to CD-ROM and boot your server from CD-ROM. For details see [Installation](https://pve.proxmox.com/wiki/Installation "Installation") * no download, outdated Proxmox Virtual Environment 1.4 beta1 (ISO Image updated on 17.9.2009) ====================================================================== Release notes: [Roadmap#Proxmox\_VE\_1.4\_beta1](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_1.4_beta1 "Roadmap") This is a beta release and therefore not intended for production systems. Download the ISO image, burn it to CD-ROM and boot your server from CD-ROM. For details see [Installation](https://pve.proxmox.com/wiki/Installation "Installation") * no download, outdated Proxmox Virtual Environment 1.3 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_1.3](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_1.3 "Roadmap") Download the ISO image, burn it to CD-ROM and boot your server from CD-ROM. For details see [Installation](https://pve.proxmox.com/wiki/Installation "Installation") * Download via http: [Proxmox VE 1.3](http://www.proxmox.com/downloads/proxmox-ve/iso-images/28-proxmox-ve-1) (MD5SUM is 6ddefdba42121ea24b4e1a3b17d93355) **Important note** If you run windows KVM guests your operating system will recognize some hardware changes on the first boot and windows shows a new network card in the device manager. (e.g. you need to reassign the fixed IP setup to the new network card. if you have DHCP setup there should be no issues). Under some circumstances reactivation of your windows license can be necessary. Proxmox Virtual Environment 1.2 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_1.2](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_1.2 "Roadmap") Download the ISO image, burn it to CD-ROM and boot your server from CD-ROM. For details see [Installation](https://pve.proxmox.com/wiki/Installation "Installation") * no download, outdated Proxmox Virtual Environment 1.1 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox\_VE\_1.1](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_1.1 "Roadmap") Download the ISO image, burn it to CD-ROM and boot your server from CD-ROM. For details see [Installation](https://pve.proxmox.com/wiki/Installation "Installation") * no download, outdated Proxmox Virtual Environment 1.0 (ISO Image) =========================================== Release notes: [Roadmap#Proxmox VE 1.0 - First stable release](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_1.0_-_First_stable_release "Roadmap") Download the ISO image, burn it to CD-ROM and boot your server from CD-ROM. For details see [Installation](https://pve.proxmox.com/wiki/Installation "Installation") * no download, outdated Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Downloads&oldid=12402](https://pve.proxmox.com/mediawiki/index.php?title=Downloads&oldid=12402) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Installation](https://pve.proxmox.com/wiki/Category:Installation "Category:Installation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Categories - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Categories) Categories ========== [Jump to navigation](https://pve.proxmox.com/wiki/Special:Categories#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:Categories#searchInput) The following categories exist on the wiki, and may or may not be unused. Also see [wanted categories](https://pve.proxmox.com/wiki/Special:WantedCategories "Special:WantedCategories") . Categories Display categories starting at: Show * [Archive](https://pve.proxmox.com/wiki/Category:Archive "Category:Archive") (27 members) * [Ceph Upgrade](https://pve.proxmox.com/wiki/Category:Ceph_Upgrade "Category:Ceph Upgrade") (9 members) * [Cluster](https://pve.proxmox.com/wiki/Category:Cluster "Category:Cluster") (2 members) * [Development](https://pve.proxmox.com/wiki/Category:Development "Category:Development") (7 members) * [HA](https://pve.proxmox.com/wiki/Category:HA "Category:HA") (0 members) * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") (144 members) * [Hardware](https://pve.proxmox.com/wiki/Category:Hardware "Category:Hardware") (3 members) * [High Availability](https://pve.proxmox.com/wiki/Category:High_Availability "Category:High Availability") (1 member) * [Installation](https://pve.proxmox.com/wiki/Category:Installation "Category:Installation") (44 members) * [Pages using deprecated source tags](https://pve.proxmox.com/mediawiki/index.php?title=Category:Pages_using_deprecated_source_tags&action=edit&redlink=1 "Category:Pages using deprecated source tags (page does not exist)") (5 members) * [Pages with syntax highlighting errors](https://pve.proxmox.com/mediawiki/index.php?title=Category:Pages_with_syntax_highlighting_errors&action=edit&redlink=1 "Category:Pages with syntax highlighting errors (page does not exist)") (5 members) * [Pages with too many expensive parser function calls](https://pve.proxmox.com/mediawiki/index.php?title=Category:Pages_with_too_many_expensive_parser_function_calls&action=edit&redlink=1 "Category:Pages with too many expensive parser function calls (page does not exist)") (1 member) * [Proxmox Datacenter Manager](https://pve.proxmox.com/wiki/Category:Proxmox_Datacenter_Manager "Category:Proxmox Datacenter Manager") (3 members) * [Proxmox VE 1.x](https://pve.proxmox.com/wiki/Category:Proxmox_VE_1.x "Category:Proxmox VE 1.x") (0 members) * [Proxmox VE 3](https://pve.proxmox.com/wiki/Category:Proxmox_VE_3 "Category:Proxmox VE 3") (0 members) * [Proxmox VE 3.x](https://pve.proxmox.com/wiki/Category:Proxmox_VE_3.x "Category:Proxmox VE 3.x") (15 members) * [Proxmox VE 4.x](https://pve.proxmox.com/mediawiki/index.php?title=Category:Proxmox_VE_4.x&action=edit&redlink=1 "Category:Proxmox VE 4.x (page does not exist)") (1 member) * [Qemu/KVM](https://pve.proxmox.com/wiki/Category:Qemu/KVM "Category:Qemu/KVM") (15 members) * [Reference Documentation](https://pve.proxmox.com/wiki/Category:Reference_Documentation "Category:Reference Documentation") (61 members) * [SDN](https://pve.proxmox.com/wiki/Category:SDN "Category:SDN") (1 member) * [Staging](https://pve.proxmox.com/mediawiki/index.php?title=Category:Staging&action=edit&redlink=1 "Category:Staging (page does not exist)") (1 member) * [Storage](https://pve.proxmox.com/wiki/Category:Storage "Category:Storage") (2 members) * [System Administration](https://pve.proxmox.com/wiki/Category:System_Administration "Category:System Administration") (3 members) * [Technology](https://pve.proxmox.com/wiki/Category:Technology "Category:Technology") (0 members) * [Troubleshooting](https://pve.proxmox.com/wiki/Category:Troubleshooting "Category:Troubleshooting") (10 members) * [Upgrade](https://pve.proxmox.com/wiki/Category:Upgrade "Category:Upgrade") (10 members) * [Virtual Appliances](https://pve.proxmox.com/wiki/Category:Virtual_Appliances "Category:Virtual Appliances") (1 member) Retrieved from "[https://pve.proxmox.com/wiki/Special:Categories](https://pve.proxmox.com/wiki/Special:Categories) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Proxmox VE Main Page ========= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Main_Page#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Main_Page#searchInput) [![](https://pve.proxmox.com/mediawiki/images/thumb/a/a3/Proxmox-VE-Cluster-Summary.png/768px-Proxmox-VE-Cluster-Summary.png)](https://pve.proxmox.com/wiki/File:Proxmox-VE-Cluster-Summary.png) Three node cluster status Today, 14 April 2026, there are [256](https://pve.proxmox.com/wiki/Special:Statistics "Special:Statistics") articles available. **Proxmox Virtual Environment** is an open source server virtualization management solution based on QEMU/KVM and LXC. You can manage virtual machines, containers, highly available clusters, storage and networks with an integrated, easy-to-use web interface or via CLI. Proxmox VE code is licensed under the GNU Affero General Public License, version 3. The project is developed and maintained by [Proxmox Server Solutions GmbH](https://www.proxmox.com/) . For an overview of the Proxmox VE key features see the [Proxmox website](https://www.proxmox.com/en/proxmox-virtual-environment/features) . Downloads ========= [Download](https://pve.proxmox.com/wiki/Downloads "Downloads") our latest ISO image. Alternate download: [https://enterprise.proxmox.com/iso](https://enterprise.proxmox.com/iso) Installation ============ You can install Proxmox VE either on your hardware from USB or CD-ROM using our ISO image, or alternatively on top of an existing Debian installation. [Read more](https://pve.proxmox.com/wiki/Installation) Upgrading Proxmox VE ==================== [System Software Updates](https://pve.proxmox.com/wiki/System_Software_Updates "System Software Updates") are downloaded from the [Package Repositories](https://pve.proxmox.com/wiki/Package_Repositories "Package Repositories") and should be applied frequently to receive the most recent bug/security fixes and to obtain the newest features. You can also upgrade existing Proxmox VE installations to the next major release: * [Upgrade from Proxmox VE 8 to 9](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9 "Upgrade from 8 to 9") * [Upgrade Guides for older Releases](https://pve.proxmox.com/wiki/Category:Upgrade "Category:Upgrade") See the [supported release table](https://pve.proxmox.com/wiki/FAQ#faq-support-table "FAQ") for the current release and the end of life date of older releases. Migrate to Proxmox VE ===================== For an overview about how to migrate to Proxmox VE see [Migrate to Proxmox VE](https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE "Migrate to Proxmox VE") . Using Proxmox VE ================ This wiki includes the complete [Proxmox VE Reference Documentation](https://pve.proxmox.com/pve-docs/) If you are new to Proxmox VE the following chapters will help you to start: * [QEMU/KVM Virtual Machines](https://pve.proxmox.com/wiki/QEMU/KVM_Virtual_Machines "QEMU/KVM Virtual Machines") and [Linux Container](https://pve.proxmox.com/wiki/Linux_Container "Linux Container") are the two types of virtualization technologies supported by Proxmox VE * [Host System Administration](https://pve.proxmox.com/wiki/Host_System_Administration "Host System Administration") will detail all the tasks commonly done on the Proxmox VE host such as setting [Package Repositories](https://pve.proxmox.com/wiki/Package_Repositories "Package Repositories") , [Network Configuration](https://pve.proxmox.com/wiki/Network_Configuration "Network Configuration") , [System Software Updates](https://pve.proxmox.com/wiki/System_Software_Updates "System Software Updates") , [Host Bootloader](https://pve.proxmox.com/wiki/Host_Bootloader "Host Bootloader") , [External Metric Server](https://pve.proxmox.com/wiki/External_Metric_Server "External Metric Server") , [Disk Health Monitoring](https://pve.proxmox.com/wiki/Disk_Health_Monitoring "Disk Health Monitoring") , [Logical Volume Manager (LVM)](https://pve.proxmox.com/wiki/Logical_Volume_Manager_(LVM) "Logical Volume Manager (LVM)") , [ZFS on Linux](https://pve.proxmox.com/wiki/ZFS_on_Linux "ZFS on Linux") * [Cluster Manager](https://pve.proxmox.com/wiki/Cluster_Manager "Cluster Manager") will explain to you how to connect your Proxmox VE hosts in clusters * You can configure [High Availability](https://pve.proxmox.com/wiki/High_Availability "High Availability") for your virtual machines and containers once you have setup a cluster * [Storage](https://pve.proxmox.com/wiki/Storage "Storage") will give you an overview of all the supported storage technologies in Proxmox VE: [Ceph RBD](https://pve.proxmox.com/wiki/Storage:_RBD "Storage: RBD") , [ZFS](https://pve.proxmox.com/wiki/Storage:_ZFS "Storage: ZFS") , [User Mode iSCSI](https://pve.proxmox.com/wiki/Storage:_User_Mode_iSCSI "Storage: User Mode iSCSI") , [iSCSI](https://pve.proxmox.com/wiki/Storage:_iSCSI "Storage: iSCSI") , [ZFS over iSCSI](https://pve.proxmox.com/wiki/Storage:_ZFS_over_iSCSI "Storage: ZFS over iSCSI") , [LVM](https://pve.proxmox.com/wiki/Storage:_LVM "Storage: LVM") , [LVM thin](https://pve.proxmox.com/wiki/Storage:_LVM_Thin "Storage: LVM Thin") , [NFS](https://pve.proxmox.com/wiki/Storage:_NFS "Storage: NFS") and [Proxmox Backup Server](https://pve.proxmox.com/wiki/Storage:_Proxmox_Backup_Server "Storage: Proxmox Backup Server") * Setup a hyper-converged infrastructure deploying a [Ceph Cluster](https://pve.proxmox.com/wiki/Deploy_Hyper-Converged_Ceph_Cluster "Deploy Hyper-Converged Ceph Cluster") . * [Backup and Restore](https://pve.proxmox.com/wiki/Backup_and_Restore "Backup and Restore") will explain how to use the integrated backup manager * [Firewall](https://pve.proxmox.com/wiki/Firewall "Firewall") details how the built-in Proxmox VE Firewall works * [Software-Defined Network](https://pve.proxmox.com/wiki/Software-Defined_Network "Software-Defined Network") documents the Proxmox VE SDN capabillties * [User Management](https://pve.proxmox.com/wiki/User_Management "User Management") explains how the authentication and permissions work in Proxmox VE * finally, the [Developer Documentation](https://pve.proxmox.com/wiki/Developer_Documentation "Developer Documentation") will show you how to get access to the source code, and how to send patches, so your work will be included in the next Proxmox VE release Offline Documentation ===================== The complete **[Proxmox VE Reference Documentation](https://pve.proxmox.com/pve-docs/) ** is also available offline in different formats such as html, pdf or epub. This documentation is also included in each PVE installation, and is accessible via contextual help buttons. HOWTOs & Troubleshooting ======================== [HOWTOs](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") How to do something [Hardware](https://pve.proxmox.com/wiki/Category:Hardware "Category:Hardware") Hardware for Proxmox VE [Troubleshooting](https://pve.proxmox.com/wiki/Category:Troubleshooting "Category:Troubleshooting") What to do if something fails Release History and Roadmap =========================== Take a look on the [Roadmap](https://pve.proxmox.com/wiki/Roadmap "Roadmap") for existing and upcoming features. Videos ====== Browse videos about Proxmox Virtual Environment on our website: [https://www.proxmox.com/en/services/videos/proxmox-virtual-environment](https://www.proxmox.com/en/services/videos/proxmox-virtual-environment) . Testimonials ============ Companies regardless their size, sector, or industry, as well as universities, public institutions and non-profits use Proxmox VE in their production environment. Take a look on our [testimonials](https://www.proxmox.com/en/about/stories?f=7) page. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Main\_Page&oldid=12320](https://pve.proxmox.com/mediawiki/index.php?title=Main_Page&oldid=12320) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Proxmox VE Documentation Index ☰ Proxmox VE Administration Guide[](https://pve.proxmox.com/pve-docs/#_proxmox_ve_administration_guide "Permalink to this heading") ---------------------------------------------------------------------------------------------------------------------------------- You can browse the [administration guide as a single-page HTML document](https://pve.proxmox.com/pve-docs/pve-admin-guide.html) . You can also download the guide in the following formats: * [PDF file](https://pve.proxmox.com/pve-docs/pve-admin-guide.pdf) * [E-book (ePub)](https://pve.proxmox.com/pve-docs/pve-admin-guide.epub) Individual Chapters[](https://pve.proxmox.com/pve-docs/#_individual_chapters "Permalink to this heading") ---------------------------------------------------------------------------------------------------------- | Chapter | | --- | | [1\. Introduction](https://pve.proxmox.com/pve-docs/chapter-pve-intro.html) | | [2\. Installing Proxmox VE](https://pve.proxmox.com/pve-docs/chapter-pve-installation.html) | | [3\. Host System Administration](https://pve.proxmox.com/pve-docs/chapter-sysadmin.html) | | [4\. Graphical User Interface](https://pve.proxmox.com/pve-docs/chapter-pve-gui.html) | | [5\. Cluster Manager](https://pve.proxmox.com/pve-docs/chapter-pvecm.html) | | [6\. Proxmox Cluster File System (pmxcfs)](https://pve.proxmox.com/pve-docs/chapter-pmxcfs.html) | | [7\. Proxmox VE Storage](https://pve.proxmox.com/pve-docs/chapter-pvesm.html) | | [8\. Deploy Hyper-Converged Ceph Cluster](https://pve.proxmox.com/pve-docs/chapter-pveceph.html) | | [9\. Storage Replication](https://pve.proxmox.com/pve-docs/chapter-pvesr.html) | | [10\. QEMU/KVM Virtual Machines](https://pve.proxmox.com/pve-docs/chapter-qm.html) | | [11\. Proxmox Container Toolkit](https://pve.proxmox.com/pve-docs/chapter-pct.html) | | [12\. Software-Defined Network](https://pve.proxmox.com/pve-docs/chapter-pvesdn.html) | | [13\. Proxmox VE Firewall](https://pve.proxmox.com/pve-docs/chapter-pve-firewall.html) | | [14\. User Management](https://pve.proxmox.com/pve-docs/chapter-pveum.html) | | [15\. High Availability](https://pve.proxmox.com/pve-docs/chapter-ha-manager.html) | | [16\. Backup and Restore](https://pve.proxmox.com/pve-docs/chapter-vzdump.html) | | [17\. Notifications](https://pve.proxmox.com/pve-docs/chapter-notifications.html) | | [25\. Shell interface for the Proxmox VE API](https://pve.proxmox.com/pve-docs/chapter-pvesh.html) | | [26\. Frequently Asked Questions](https://pve.proxmox.com/pve-docs/chapter-pve-faq.html) | | [27\. Bibliography](https://pve.proxmox.com/pve-docs/chapter-pve-bibliography.html) | Proxmox VE Manual Pages[](https://pve.proxmox.com/pve-docs/#_proxmox_ve_manual_pages "Permalink to this heading") ------------------------------------------------------------------------------------------------------------------ ### Command-line Interface[](https://pve.proxmox.com/pve-docs/#_command_line_interface "Permalink to this heading") | Name | | Title | | | | --- | --- | | [ha-manager(1)](https://pve.proxmox.com/pve-docs/ha-manager.1.html) | | High Availability | | | | [pct(1)](https://pve.proxmox.com/pve-docs/pct.1.html) | | Proxmox Container Toolkit | | | | [pveam(1)](https://pve.proxmox.com/pve-docs/pveam.1.html) | | Container Images | | | | [pveceph(1)](https://pve.proxmox.com/pve-docs/pveceph.1.html) | | Deploy Hyper-Converged Ceph Cluster | | | | [pvecm(1)](https://pve.proxmox.com/pve-docs/pvecm.1.html) | | Cluster Manager | | | | [pvenode(1)](https://pve.proxmox.com/pve-docs/pvenode.1.html) | | Proxmox Node Management | | | | [pveperf(1)](https://pve.proxmox.com/pve-docs/pveperf.1.html) | | Proxmox VE Benchmark Script | | | | [pvesh(1)](https://pve.proxmox.com/pve-docs/pvesh.1.html) | | Shell interface for the Proxmox VE API | | | | [pvesm(1)](https://pve.proxmox.com/pve-docs/pvesm.1.html) | | Proxmox VE Storage | | | | [pvesr(1)](https://pve.proxmox.com/pve-docs/pvesr.1.html) | | Storage Replication | | | | [pvesubscription(1)](https://pve.proxmox.com/pve-docs/pvesubscription.1.html) | | Subscription Management | | | | [pveum(1)](https://pve.proxmox.com/pve-docs/pveum.1.html) | | User Management | | | | [qm(1)](https://pve.proxmox.com/pve-docs/qm.1.html) | | QEMU/KVM Virtual Machines | | | | [qmrestore(1)](https://pve.proxmox.com/pve-docs/qmrestore.1.html) | | Restore Virtual Machines | | | | [vzdump(1)](https://pve.proxmox.com/pve-docs/vzdump.1.html) | | Backup and Restore | | | ### Service Daemons[](https://pve.proxmox.com/pve-docs/#_service_daemons "Permalink to this heading") | Name | | Title | | | | --- | --- | | [pmxcfs(8)](https://pve.proxmox.com/pve-docs/pmxcfs.8.html) | | Proxmox Cluster File System (pmxcfs) | | | | [pve-firewall(8)](https://pve.proxmox.com/pve-docs/pve-firewall.8.html) | | Proxmox VE Firewall | | | | [pve-ha-crm(8)](https://pve.proxmox.com/pve-docs/pve-ha-crm.8.html) | | Cluster Resource Manager Daemon | | | | [pve-ha-lrm(8)](https://pve.proxmox.com/pve-docs/pve-ha-lrm.8.html) | | Local Resource Manager Daemon | | | | [pvedaemon(8)](https://pve.proxmox.com/pve-docs/pvedaemon.8.html) | | Proxmox VE API Daemon | | | | [pveproxy(8)](https://pve.proxmox.com/pve-docs/pveproxy.8.html) | | Proxmox VE API Proxy Daemon | | | | [pvescheduler(8)](https://pve.proxmox.com/pve-docs/pvescheduler.8.html) | | Proxmox VE Scheduler Daemon | | | | [pvestatd(8)](https://pve.proxmox.com/pve-docs/pvestatd.8.html) | | Proxmox VE Status Daemon | | | | [qmeventd(8)](https://pve.proxmox.com/pve-docs/qmeventd.8.html) | | PVE QEMU Event Daemon | | | | [spiceproxy(8)](https://pve.proxmox.com/pve-docs/spiceproxy.8.html) | | SPICE Proxy Service | | | ### Configuration Options[](https://pve.proxmox.com/pve-docs/#_configuration_options "Permalink to this heading") | Name | | Title | | | | --- | --- | | [cpu-models.conf(5)](https://pve.proxmox.com/pve-docs/cpu-models.conf.5.html) | | Custom CPU Model Configuration | | | | [datacenter.cfg(5)](https://pve.proxmox.com/pve-docs/datacenter.cfg.5.html) | | Datacenter Configuration | | | | [pct.conf(5)](https://pve.proxmox.com/pve-docs/pct.conf.5.html) | | Container Configuration | | | | [qm.conf(5)](https://pve.proxmox.com/pve-docs/qm.conf.5.html) | | Virtual Machine Configuration | | | ### API Viewer[](https://pve.proxmox.com/pve-docs/#_api_viewer "Permalink to this heading") The [API viewer](https://pve.proxmox.com/pve-docs/api-viewer/index.html) is a tiny web application which allows you to inspect all available API calls. * * * --- # Proxmox VE Documentation Index Proxmox VE Administration Guide[](https://pve.proxmox.com/pve-docs-8/#_proxmox_ve_administration_guide "Permalink to this heading") ------------------------------------------------------------------------------------------------------------------------------------ | Format | Link | | --- | --- | | Printable version | [pve-admin-guide.pdf](https://pve.proxmox.com/pve-docs-8/pve-admin-guide.pdf) | | Online HTML version | [pve-admin-guide.html](https://pve.proxmox.com/pve-docs-8/pve-admin-guide.html) | | E-Book version | [pve-admin-guide.epub](https://pve.proxmox.com/pve-docs-8/pve-admin-guide.epub) | Individual Chapters[](https://pve.proxmox.com/pve-docs-8/#_individual_chapters "Permalink to this heading") ------------------------------------------------------------------------------------------------------------ | Title | Link | | --- | --- | | High Availability | [chapter-ha-manager.html](https://pve.proxmox.com/pve-docs-8/chapter-ha-manager.html) | | Notifications | [chapter-notifications.html](https://pve.proxmox.com/pve-docs-8/chapter-notifications.html) | | Proxmox Container Toolkit | [chapter-pct.html](https://pve.proxmox.com/pve-docs-8/chapter-pct.html) | | Proxmox Cluster File System (pmxcfs) | [chapter-pmxcfs.html](https://pve.proxmox.com/pve-docs-8/chapter-pmxcfs.html) | | Bibliography | [chapter-pve-bibliography.html](https://pve.proxmox.com/pve-docs-8/chapter-pve-bibliography.html) | | Frequently Asked Questions | [chapter-pve-faq.html](https://pve.proxmox.com/pve-docs-8/chapter-pve-faq.html) | | Proxmox VE Firewall | [chapter-pve-firewall.html](https://pve.proxmox.com/pve-docs-8/chapter-pve-firewall.html) | | Graphical User Interface | [chapter-pve-gui.html](https://pve.proxmox.com/pve-docs-8/chapter-pve-gui.html) | | Installing Proxmox VE | [chapter-pve-installation.html](https://pve.proxmox.com/pve-docs-8/chapter-pve-installation.html) | | Deploy Hyper-Converged Ceph Cluster | [chapter-pveceph.html](https://pve.proxmox.com/pve-docs-8/chapter-pveceph.html) | | Cluster Manager | [chapter-pvecm.html](https://pve.proxmox.com/pve-docs-8/chapter-pvecm.html) | | Software-Defined Network | [chapter-pvesdn.html](https://pve.proxmox.com/pve-docs-8/chapter-pvesdn.html) | | Shell interface for the Proxmox VE API | [chapter-pvesh.html](https://pve.proxmox.com/pve-docs-8/chapter-pvesh.html) | | Proxmox VE Storage | [chapter-pvesm.html](https://pve.proxmox.com/pve-docs-8/chapter-pvesm.html) | | Storage Replication | [chapter-pvesr.html](https://pve.proxmox.com/pve-docs-8/chapter-pvesr.html) | | User Management | [chapter-pveum.html](https://pve.proxmox.com/pve-docs-8/chapter-pveum.html) | | QEMU/KVM Virtual Machines | [chapter-qm.html](https://pve.proxmox.com/pve-docs-8/chapter-qm.html) | | PVE QEMU Event Daemon | [chapter-qmeventd.html](https://pve.proxmox.com/pve-docs-8/chapter-qmeventd.html) | | Host System Administration | [chapter-sysadmin.html](https://pve.proxmox.com/pve-docs-8/chapter-sysadmin.html) | | Backup and Restore | [chapter-vzdump.html](https://pve.proxmox.com/pve-docs-8/chapter-vzdump.html) | Proxmox VE Manual Pages[](https://pve.proxmox.com/pve-docs-8/#_proxmox_ve_manual_pages "Permalink to this heading") -------------------------------------------------------------------------------------------------------------------- ### Command-line Interface[](https://pve.proxmox.com/pve-docs-8/#_command_line_interface "Permalink to this heading") | Name | Title | | | Link | | --- | --- | --- | | ha-manager(1) | High Availability | | | [ha-manager.1](https://pve.proxmox.com/pve-docs-8/ha-manager.1.html) | | pct(1) | Proxmox Container Toolkit | | | [pct.1](https://pve.proxmox.com/pve-docs-8/pct.1.html) | | pveam(1) | Container Images | | | [pveam.1](https://pve.proxmox.com/pve-docs-8/pveam.1.html) | | pveceph(1) | Deploy Hyper-Converged Ceph Cluster | | | [pveceph.1](https://pve.proxmox.com/pve-docs-8/pveceph.1.html) | | pvecm(1) | Cluster Manager | | | [pvecm.1](https://pve.proxmox.com/pve-docs-8/pvecm.1.html) | | pvenode(1) | Proxmox Node Management | | | [pvenode.1](https://pve.proxmox.com/pve-docs-8/pvenode.1.html) | | pveperf(1) | Proxmox VE Benchmark Script | | | [pveperf.1](https://pve.proxmox.com/pve-docs-8/pveperf.1.html) | | pvesh(1) | Shell interface for the Proxmox VE API | | | [pvesh.1](https://pve.proxmox.com/pve-docs-8/pvesh.1.html) | | pvesm(1) | Proxmox VE Storage | | | [pvesm.1](https://pve.proxmox.com/pve-docs-8/pvesm.1.html) | | pvesr(1) | Storage Replication | | | [pvesr.1](https://pve.proxmox.com/pve-docs-8/pvesr.1.html) | | pvesubscription(1) | Subscription Management | | | [pvesubscription.1](https://pve.proxmox.com/pve-docs-8/pvesubscription.1.html) | | pveum(1) | User Management | | | [pveum.1](https://pve.proxmox.com/pve-docs-8/pveum.1.html) | | qm(1) | QEMU/KVM Virtual Machines | | | [qm.1](https://pve.proxmox.com/pve-docs-8/qm.1.html) | | qmrestore(1) | Restore Virtual Machines | | | [qmrestore.1](https://pve.proxmox.com/pve-docs-8/qmrestore.1.html) | | vzdump(1) | Backup and Restore | | | [vzdump.1](https://pve.proxmox.com/pve-docs-8/vzdump.1.html) | ### Service Daemons[](https://pve.proxmox.com/pve-docs-8/#_service_daemons "Permalink to this heading") | Name | Title | | | Link | | --- | --- | --- | | pmxcfs(8) | Proxmox Cluster File System (pmxcfs) | | | [pmxcfs.8](https://pve.proxmox.com/pve-docs-8/pmxcfs.8.html) | | pve-firewall(8) | Proxmox VE Firewall | | | [pve-firewall.8](https://pve.proxmox.com/pve-docs-8/pve-firewall.8.html) | | pve-ha-crm(8) | Cluster Resource Manager Daemon | | | [pve-ha-crm.8](https://pve.proxmox.com/pve-docs-8/pve-ha-crm.8.html) | | pve-ha-lrm(8) | Local Resource Manager Daemon | | | [pve-ha-lrm.8](https://pve.proxmox.com/pve-docs-8/pve-ha-lrm.8.html) | | pvedaemon(8) | Proxmox VE API Daemon | | | [pvedaemon.8](https://pve.proxmox.com/pve-docs-8/pvedaemon.8.html) | | pveproxy(8) | Proxmox VE API Proxy Daemon | | | [pveproxy.8](https://pve.proxmox.com/pve-docs-8/pveproxy.8.html) | | pvescheduler(8) | Proxmox VE Scheduler Daemon | | | [pvescheduler.8](https://pve.proxmox.com/pve-docs-8/pvescheduler.8.html) | | pvestatd(8) | Proxmox VE Status Daemon | | | [pvestatd.8](https://pve.proxmox.com/pve-docs-8/pvestatd.8.html) | | qmeventd(8) | PVE QEMU Event Daemon | | | [qmeventd.8](https://pve.proxmox.com/pve-docs-8/qmeventd.8.html) | | spiceproxy(8) | SPICE Proxy Service | | | [spiceproxy.8](https://pve.proxmox.com/pve-docs-8/spiceproxy.8.html) | ### Configuration Options[](https://pve.proxmox.com/pve-docs-8/#_configuration_options "Permalink to this heading") | Name | Title | | | Link | | --- | --- | --- | | cpu-models.conf(5) | Custom CPU Model Configuration | | | [cpu-models.conf.5](https://pve.proxmox.com/pve-docs-8/cpu-models.conf.5.html) | | datacenter.cfg(5) | Datacenter Configuration | | | [datacenter.cfg.5](https://pve.proxmox.com/pve-docs-8/datacenter.cfg.5.html) | | pct.conf(5) | Container Configuration | | | [pct.conf.5](https://pve.proxmox.com/pve-docs-8/pct.conf.5.html) | | qm.conf(5) | Virtual Machine Configuration | | | [qm.conf.5](https://pve.proxmox.com/pve-docs-8/qm.conf.5.html) | ### API Viewer[](https://pve.proxmox.com/pve-docs-8/#_api_viewer "Permalink to this heading") The [API viewer](https://pve.proxmox.com/pve-docs-8/api-viewer/index.html) is a tiny web application which allows you to inspect all available API calls. * * * --- # Special pages - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Special_pages) Special pages ============= [Jump to navigation](https://pve.proxmox.com/wiki/Special:SpecialPages#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:SpecialPages#searchInput) Contents -------- * [1 Maintenance reports](https://pve.proxmox.com/wiki/Special:SpecialPages#mw-specialpagesgroup-maintenance) * [2 Lists of pages](https://pve.proxmox.com/wiki/Special:SpecialPages#mw-specialpagesgroup-pages) * [3 Account management](https://pve.proxmox.com/wiki/Special:SpecialPages#mw-specialpagesgroup-login) * [4 Users and rights](https://pve.proxmox.com/wiki/Special:SpecialPages#mw-specialpagesgroup-users) * [5 Recent changes and logs](https://pve.proxmox.com/wiki/Special:SpecialPages#mw-specialpagesgroup-changes) * [6 Media reports and uploads](https://pve.proxmox.com/wiki/Special:SpecialPages#mw-specialpagesgroup-media) * [7 Data and tools](https://pve.proxmox.com/wiki/Special:SpecialPages#mw-specialpagesgroup-wiki) * [8 Redirecting special pages](https://pve.proxmox.com/wiki/Special:SpecialPages#mw-specialpagesgroup-redirects) * [9 High use pages](https://pve.proxmox.com/wiki/Special:SpecialPages#mw-specialpagesgroup-highuse) * [10 Page tools](https://pve.proxmox.com/wiki/Special:SpecialPages#mw-specialpagesgroup-pagetools) * [11 Other special pages](https://pve.proxmox.com/wiki/Special:SpecialPages#mw-specialpagesgroup-other) Maintenance reports ------------------- * [Broken redirects](https://pve.proxmox.com/wiki/Special:BrokenRedirects "Special:BrokenRedirects") * [Dead-end pages](https://pve.proxmox.com/wiki/Special:DeadendPages "Special:DeadendPages") * [Double redirects](https://pve.proxmox.com/wiki/Special:DoubleRedirects "Special:DoubleRedirects") * [Long pages](https://pve.proxmox.com/wiki/Special:LongPages "Special:LongPages") * [Oldest pages](https://pve.proxmox.com/wiki/Special:AncientPages "Special:AncientPages") * [Orphaned pages](https://pve.proxmox.com/wiki/Special:LonelyPages "Special:LonelyPages") * [Pages with the fewest revisions](https://pve.proxmox.com/wiki/Special:FewestRevisions "Special:FewestRevisions") * [Pages without language links](https://pve.proxmox.com/wiki/Special:WithoutInterwiki "Special:WithoutInterwiki") * [Protected pages](https://pve.proxmox.com/wiki/Special:ProtectedPages "Special:ProtectedPages") * [Protected titles](https://pve.proxmox.com/wiki/Special:ProtectedTitles "Special:ProtectedTitles") * [Short pages](https://pve.proxmox.com/wiki/Special:ShortPages "Special:ShortPages") * [Uncategorized categories](https://pve.proxmox.com/wiki/Special:UncategorizedCategories "Special:UncategorizedCategories") * [Uncategorized files](https://pve.proxmox.com/wiki/Special:UncategorizedFiles "Special:UncategorizedFiles") * [Uncategorized pages](https://pve.proxmox.com/wiki/Special:UncategorizedPages "Special:UncategorizedPages") * [Uncategorized templates](https://pve.proxmox.com/wiki/Special:UncategorizedTemplates "Special:UncategorizedTemplates") * [Unused categories](https://pve.proxmox.com/wiki/Special:UnusedCategories "Special:UnusedCategories") * [Unused files](https://pve.proxmox.com/wiki/Special:UnusedFiles "Special:UnusedFiles") * [Unused templates](https://pve.proxmox.com/wiki/Special:UnusedTemplates "Special:UnusedTemplates") * [Wanted categories](https://pve.proxmox.com/wiki/Special:WantedCategories "Special:WantedCategories") * [Wanted files](https://pve.proxmox.com/wiki/Special:WantedFiles "Special:WantedFiles") * [Wanted pages](https://pve.proxmox.com/wiki/Special:WantedPages "Special:WantedPages") * [Wanted templates](https://pve.proxmox.com/wiki/Special:WantedTemplates "Special:WantedTemplates") Lists of pages -------------- * [All pages](https://pve.proxmox.com/wiki/Special:AllPages "Special:AllPages") * [All pages with prefix](https://pve.proxmox.com/wiki/Special:PrefixIndex "Special:PrefixIndex") * [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") * [Category tree](https://pve.proxmox.com/wiki/Special:CategoryTree "Special:CategoryTree") * [External links search](https://pve.proxmox.com/wiki/Special:LinkSearch "Special:LinkSearch") * [List of redirects](https://pve.proxmox.com/wiki/Special:ListRedirects "Special:ListRedirects") * [Pages with a page property](https://pve.proxmox.com/wiki/Special:PagesWithProp "Special:PagesWithProp") * [Search](https://pve.proxmox.com/wiki/Special:Search "Special:Search") * [Tracking categories](https://pve.proxmox.com/wiki/Special:TrackingCategories "Special:TrackingCategories") Account management ------------------ * [Bot passwords](https://pve.proxmox.com/wiki/Special:BotPasswords "Special:BotPasswords") * [Change credentials](https://pve.proxmox.com/wiki/Special:ChangeCredentials "Special:ChangeCredentials") * [Change or remove email address](https://pve.proxmox.com/wiki/Special:ChangeEmail "Special:ChangeEmail") * [Log in](https://pve.proxmox.com/wiki/Special:UserLogin "Special:UserLogin") * [Log out](https://pve.proxmox.com/wiki/Special:UserLogout "Special:UserLogout") * [Preferences](https://pve.proxmox.com/wiki/Special:Preferences "Special:Preferences") * [Remove credentials](https://pve.proxmox.com/wiki/Special:RemoveCredentials "Special:RemoveCredentials") * [Reset password](https://pve.proxmox.com/wiki/Special:PasswordReset "Special:PasswordReset") * [Reset tokens](https://pve.proxmox.com/wiki/Special:ResetTokens "Special:ResetTokens") Users and rights ---------------- * [Active users list](https://pve.proxmox.com/wiki/Special:ActiveUsers "Special:ActiveUsers") * [Autoblocks](https://pve.proxmox.com/wiki/Special:AutoblockList "Special:AutoblockList") * [Blocked users](https://pve.proxmox.com/wiki/Special:BlockList "Special:BlockList") * [Grants](https://pve.proxmox.com/wiki/Special:ListGrants "Special:ListGrants") * [Password policies](https://pve.proxmox.com/wiki/Special:PasswordPolicies "Special:PasswordPolicies") * [User contributions](https://pve.proxmox.com/wiki/Special:Contributions "Special:Contributions") * [User group rights](https://pve.proxmox.com/wiki/Special:ListGroupRights "Special:ListGroupRights") * [User list](https://pve.proxmox.com/wiki/Special:ListUsers "Special:ListUsers") * [User rights](https://pve.proxmox.com/wiki/Special:UserRights "Special:UserRights") Recent changes and logs ----------------------- * [Gallery of new files](https://pve.proxmox.com/wiki/Special:NewFiles "Special:NewFiles") * [Logs](https://pve.proxmox.com/wiki/Special:Log "Special:Log") * [New pages](https://pve.proxmox.com/wiki/Special:NewPages "Special:NewPages") * [Recent changes](https://pve.proxmox.com/wiki/Special:RecentChanges "Special:RecentChanges") * [Related changes](https://pve.proxmox.com/wiki/Special:RecentChangesLinked "Special:RecentChangesLinked") * [Valid change tags](https://pve.proxmox.com/wiki/Special:Tags "Special:Tags") Media reports and uploads ------------------------- * [File list](https://pve.proxmox.com/wiki/Special:ListFiles "Special:ListFiles") * [List of files with duplicates](https://pve.proxmox.com/wiki/Special:ListDuplicatedFiles "Special:ListDuplicatedFiles") * [MIME search](https://pve.proxmox.com/wiki/Special:MIMESearch "Special:MIMESearch") * [Media statistics](https://pve.proxmox.com/wiki/Special:MediaStatistics "Special:MediaStatistics") * [Search for duplicate files](https://pve.proxmox.com/wiki/Special:FileDuplicateSearch "Special:FileDuplicateSearch") Data and tools -------------- * [API sandbox](https://pve.proxmox.com/wiki/Special:ApiSandbox "Special:ApiSandbox") * [Book sources](https://pve.proxmox.com/wiki/Special:BookSources "Special:BookSources") * [Expand templates](https://pve.proxmox.com/wiki/Special:ExpandTemplates "Special:ExpandTemplates") * [Namespace information](https://pve.proxmox.com/wiki/Special:NamespaceInfo "Special:NamespaceInfo") * [Statistics](https://pve.proxmox.com/wiki/Special:Statistics "Special:Statistics") * [System messages](https://pve.proxmox.com/wiki/Special:AllMessages "Special:AllMessages") * [Version](https://pve.proxmox.com/wiki/Special:Version "Special:Version") Redirecting special pages ------------------------- * [Delete a page](https://pve.proxmox.com/wiki/Special:DeletePage "Special:DeletePage") * [Differences](https://pve.proxmox.com/wiki/Special:Diff "Special:Diff") * [Edit a page](https://pve.proxmox.com/wiki/Special:EditPage "Special:EditPage") * [New section](https://pve.proxmox.com/wiki/Special:NewSection "Special:NewSection") * [Page history](https://pve.proxmox.com/wiki/Special:PageHistory "Special:PageHistory") * [Page info](https://pve.proxmox.com/wiki/Special:PageInfo "Special:PageInfo") * [Permanent link](https://pve.proxmox.com/wiki/Special:PermanentLink "Special:PermanentLink") * [Protect a page](https://pve.proxmox.com/wiki/Special:ProtectPage "Special:ProtectPage") * [Purge](https://pve.proxmox.com/wiki/Special:Purge "Special:Purge") * [Random page](https://pve.proxmox.com/wiki/Special:Random "Special:Random") * [Random page in category](https://pve.proxmox.com/wiki/Special:RandomInCategory "Special:RandomInCategory") * [Random redirect](https://pve.proxmox.com/wiki/Special:RandomRedirect "Special:RandomRedirect") * [Random root page](https://pve.proxmox.com/wiki/Special:RandomRootpage "Special:RandomRootpage") * [Redirect by file, user, page, revision, or log ID](https://pve.proxmox.com/wiki/Special:Redirect "Special:Redirect") High use pages -------------- * [Most linked-to categories](https://pve.proxmox.com/wiki/Special:MostLinkedCategories "Special:MostLinkedCategories") * [Most linked-to files](https://pve.proxmox.com/wiki/Special:MostLinkedFiles "Special:MostLinkedFiles") * [Most linked-to pages](https://pve.proxmox.com/wiki/Special:MostLinkedPages "Special:MostLinkedPages") * [Most transcluded pages](https://pve.proxmox.com/wiki/Special:MostTranscludedPages "Special:MostTranscludedPages") * [Pages with the most categories](https://pve.proxmox.com/wiki/Special:MostCategories "Special:MostCategories") * [Pages with the most interwikis](https://pve.proxmox.com/wiki/Special:MostInterwikis "Special:MostInterwikis") * [Pages with the most revisions](https://pve.proxmox.com/wiki/Special:MostRevisions "Special:MostRevisions") Page tools ---------- * [Cite This Page](https://pve.proxmox.com/wiki/Special:CiteThisPage "Special:CiteThisPage") * [Compare pages](https://pve.proxmox.com/wiki/Special:ComparePages "Special:ComparePages") * [Export pages](https://pve.proxmox.com/wiki/Special:Export "Special:Export") * [What links here](https://pve.proxmox.com/wiki/Special:WhatLinksHere "Special:WhatLinksHere") Other special pages ------------------- * [Contribute](https://pve.proxmox.com/wiki/Special:Contribute "Special:Contribute") Retrieved from "[https://pve.proxmox.com/wiki/Special:SpecialPages](https://pve.proxmox.com/wiki/Special:SpecialPages) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Category:HOWTO - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Categories) Category:HOWTO ============== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Category:HOWTO#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Category:HOWTO#searchInput) HOWTOs Pages in category "HOWTO" ------------------------- The following 144 pages are in this category, out of 144 total. ### A * [Additional ways to migrate to Proxmox VE](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE "Additional ways to migrate to Proxmox VE") * [Advanced Migration Techniques to Proxmox VE](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE "Advanced Migration Techniques to Proxmox VE") * [Anatomy of LXC Container Config File](https://pve.proxmox.com/wiki/Anatomy_of_LXC_Container_Config_File "Anatomy of LXC Container Config File") * [Automated Installation](https://pve.proxmox.com/wiki/Automated_Installation "Automated Installation") ### B * [Backup and Restore](https://pve.proxmox.com/wiki/Backup_and_Restore "Backup and Restore") * [Benchmarking Storage](https://pve.proxmox.com/wiki/Benchmarking_Storage "Benchmarking Storage") * [Booting a ZFS root file system via UEFI](https://pve.proxmox.com/wiki/Booting_a_ZFS_root_file_system_via_UEFI "Booting a ZFS root file system via UEFI") * [Bypassing backup and restore when upgrading](https://pve.proxmox.com/wiki/Bypassing_backup_and_restore_when_upgrading "Bypassing backup and restore when upgrading") ### C * [Central Web-based Management](https://pve.proxmox.com/wiki/Central_Web-based_Management "Central Web-based Management") * [Ceph Hammer to Jewel](https://pve.proxmox.com/wiki/Ceph_Hammer_to_Jewel "Ceph Hammer to Jewel") * [Ceph Jewel to Luminous](https://pve.proxmox.com/wiki/Ceph_Jewel_to_Luminous "Ceph Jewel to Luminous") * [Ceph Luminous to Nautilus](https://pve.proxmox.com/wiki/Ceph_Luminous_to_Nautilus "Ceph Luminous to Nautilus") * [Ceph mClock Tuning](https://pve.proxmox.com/wiki/Ceph_mClock_Tuning "Ceph mClock Tuning") * [Ceph Nautilus to Octopus](https://pve.proxmox.com/wiki/Ceph_Nautilus_to_Octopus "Ceph Nautilus to Octopus") * [Ceph Octopus to Pacific](https://pve.proxmox.com/wiki/Ceph_Octopus_to_Pacific "Ceph Octopus to Pacific") * [Ceph Pacific to Quincy](https://pve.proxmox.com/wiki/Ceph_Pacific_to_Quincy "Ceph Pacific to Quincy") * [Ceph Quincy to Reef](https://pve.proxmox.com/wiki/Ceph_Quincy_to_Reef "Ceph Quincy to Reef") * [Ceph RBD Mirroring](https://pve.proxmox.com/wiki/Ceph_RBD_Mirroring "Ceph RBD Mirroring") * [Ceph Reef to Squid](https://pve.proxmox.com/wiki/Ceph_Reef_to_Squid "Ceph Reef to Squid") * [Ceph Server](https://pve.proxmox.com/wiki/Ceph_Server "Ceph Server") * [Ceph Squid to Tentacle](https://pve.proxmox.com/wiki/Ceph_Squid_to_Tentacle "Ceph Squid to Tentacle") * [Convert Debian CT to Kali](https://pve.proxmox.com/wiki/Convert_Debian_CT_to_Kali "Convert Debian CT to Kali") * [Convert OpenVZ to LXC](https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC "Convert OpenVZ to LXC") ### D * [Debian Appliance Builder](https://pve.proxmox.com/wiki/Debian_Appliance_Builder "Debian Appliance Builder") * [Debugging Installation](https://pve.proxmox.com/wiki/Debugging_Installation "Debugging Installation") * [Developer Documentation](https://pve.proxmox.com/wiki/Developer_Documentation "Developer Documentation") * [Developer Workstations with Proxmox VE and X11](https://pve.proxmox.com/wiki/Developer_Workstations_with_Proxmox_VE_and_X11 "Developer Workstations with Proxmox VE and X11") * [Disk Health Email Alerts](https://pve.proxmox.com/wiki/Disk_Health_Email_Alerts "Disk Health Email Alerts") * [Downloads](https://pve.proxmox.com/wiki/Downloads "Downloads") * [DRBD](https://pve.proxmox.com/wiki/DRBD "DRBD") * [Duplicate Virtual Machines](https://pve.proxmox.com/wiki/Duplicate_Virtual_Machines "Duplicate Virtual Machines") * [Dynamic Memory Management](https://pve.proxmox.com/wiki/Dynamic_Memory_Management "Dynamic Memory Management") ### E * [Enable Core Dump systemd](https://pve.proxmox.com/wiki/Enable_Core_Dump_systemd "Enable Core Dump systemd") ### F * [Fail2ban](https://pve.proxmox.com/wiki/Fail2ban "Fail2ban") * [FreeBSD Guest Notes](https://pve.proxmox.com/wiki/FreeBSD_Guest_Notes "FreeBSD Guest Notes") ### G * [Get support](https://pve.proxmox.com/wiki/Get_support "Get support") * [Guest Time drift](https://pve.proxmox.com/wiki/Guest_Time_drift "Guest Time drift") ### H * [Hotplug (qemu disk,nic,cpu,memory)](https://pve.proxmox.com/wiki/Hotplug_(qemu_disk,nic,cpu,memory) "Hotplug (qemu disk,nic,cpu,memory)") * [HTTPS Certificate Configuration (Version 4.x, 5.0 and 5.1)](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1) "HTTPS Certificate Configuration (Version 4.x, 5.0 and 5.1)") ### I * [Import certificate in browser](https://pve.proxmox.com/wiki/Import_certificate_in_browser "Import certificate in browser") * [Infiniband](https://pve.proxmox.com/wiki/Infiniband "Infiniband") * [Install Proxmox VE on Debian 11 Bullseye](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye "Install Proxmox VE on Debian 11 Bullseye") * [Install Proxmox VE on Debian 12 Bookworm](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_12_Bookworm "Install Proxmox VE on Debian 12 Bookworm") * [Install Proxmox VE on Debian 13 Trixie](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie "Install Proxmox VE on Debian 13 Trixie") * [Install Proxmox VE on Debian Buster](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster "Install Proxmox VE on Debian Buster") * [Install Proxmox VE on Debian Stretch](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Stretch "Install Proxmox VE on Debian Stretch") * [Installation](https://pve.proxmox.com/wiki/Installation "Installation") * [Installation: Tips and Tricks](https://pve.proxmox.com/wiki/Installation:_Tips_and_Tricks "Installation: Tips and Tricks") * [IO Scheduler](https://pve.proxmox.com/wiki/IO_Scheduler "IO Scheduler") * [ISCSI Multipath](https://pve.proxmox.com/wiki/ISCSI_Multipath "ISCSI Multipath") * [Iscsi/nappit](https://pve.proxmox.com/wiki/Iscsi/nappit "Iscsi/nappit") ### K * [Kernel Crash Trace Log](https://pve.proxmox.com/wiki/Kernel_Crash_Trace_Log "Kernel Crash Trace Log") * [KSM](https://pve.proxmox.com/wiki/KSM "KSM") ### L * [Legacy: ZFS over iSCSI](https://pve.proxmox.com/wiki/Legacy:_ZFS_over_iSCSI "Legacy: ZFS over iSCSI") * [Linux Container](https://pve.proxmox.com/wiki/Linux_Container "Linux Container") * [Live Snapshots](https://pve.proxmox.com/wiki/Live_Snapshots "Live Snapshots") * [LVM2](https://pve.proxmox.com/wiki/LVM2 "LVM2") ### M * [Mainboards](https://pve.proxmox.com/wiki/Mainboards "Mainboards") * [Manual: pct.conf](https://pve.proxmox.com/wiki/Manual:_pct.conf "Manual: pct.conf") * [Migrate to Proxmox VE](https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE "Migrate to Proxmox VE") * [Moving disk image from one KVM machine to another](https://pve.proxmox.com/wiki/Moving_disk_image_from_one_KVM_machine_to_another "Moving disk image from one KVM machine to another") * [Multipath](https://pve.proxmox.com/wiki/Multipath "Multipath") * [MxGPU with AMD S7150 under Proxmox VE 5.x](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x "MxGPU with AMD S7150 under Proxmox VE 5.x") ### N * [NVIDIA vGPU on Proxmox VE](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE "NVIDIA vGPU on Proxmox VE") ### O * [OATH(TOTP) Authentication](https://pve.proxmox.com/wiki/OATH(TOTP)_Authentication "OATH(TOTP) Authentication") * [Open vSwitch](https://pve.proxmox.com/wiki/Open_vSwitch "Open vSwitch") * [OpenVPN in LXC](https://pve.proxmox.com/wiki/OpenVPN_in_LXC "OpenVPN in LXC") * [OVH](https://pve.proxmox.com/wiki/OVH "OVH") * [OVMF/UEFI Boot Entries](https://pve.proxmox.com/wiki/OVMF/UEFI_Boot_Entries "OVMF/UEFI Boot Entries") ### P * [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") * [Paravirtualized Block Drivers for Windows](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows "Paravirtualized Block Drivers for Windows") * [Paravirtualized Drivers for Linux](https://pve.proxmox.com/wiki/Paravirtualized_Drivers_for_Linux "Paravirtualized Drivers for Linux") * [Paravirtualized Network Drivers for Windows](https://pve.proxmox.com/wiki/Paravirtualized_Network_Drivers_for_Windows "Paravirtualized Network Drivers for Windows") * [PfSense Guest Notes](https://pve.proxmox.com/wiki/PfSense_Guest_Notes "PfSense Guest Notes") * [Ports](https://pve.proxmox.com/wiki/Ports "Ports") * [Prepare Installation Media](https://pve.proxmox.com/wiki/Prepare_Installation_Media "Prepare Installation Media") * [Proxmox Cluster file system (pmxcfs)](https://pve.proxmox.com/wiki/Proxmox_Cluster_file_system_(pmxcfs) "Proxmox Cluster file system (pmxcfs)") * [Proxmox ISCSI installation](https://pve.proxmox.com/wiki/Proxmox_ISCSI_installation "Proxmox ISCSI installation") * [Proxmox VE API](https://pve.proxmox.com/wiki/Proxmox_VE_API "Proxmox VE API") * [Proxmox VE Kernel](https://pve.proxmox.com/wiki/Proxmox_VE_Kernel "Proxmox VE Kernel") * [Proxmox VE Mobile](https://pve.proxmox.com/wiki/Proxmox_VE_Mobile "Proxmox VE Mobile") * [PVE-zsync](https://pve.proxmox.com/wiki/PVE-zsync "PVE-zsync") ### Q * [QEMU Machine Version Upgrade](https://pve.proxmox.com/wiki/QEMU_Machine_Version_Upgrade "QEMU Machine Version Upgrade") * [Qemu-guest-agent](https://pve.proxmox.com/wiki/Qemu-guest-agent "Qemu-guest-agent") * [QEMU/KVM ACPI Guest Shutdown](https://pve.proxmox.com/wiki/QEMU/KVM_ACPI_Guest_Shutdown "QEMU/KVM ACPI Guest Shutdown") * [Quick installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") ### R * [Raid controller](https://pve.proxmox.com/wiki/Raid_controller "Raid controller") * [Raspberry Pi as third node](https://pve.proxmox.com/wiki/Raspberry_Pi_as_third_node "Raspberry Pi as third node") * [Renaming a PVE node](https://pve.proxmox.com/wiki/Renaming_a_PVE_node "Renaming a PVE node") * [Resize disks](https://pve.proxmox.com/wiki/Resize_disks "Resize disks") * [Root Password Reset](https://pve.proxmox.com/wiki/Root_Password_Reset "Root Password Reset") ### S * [Secure Boot Setup](https://pve.proxmox.com/wiki/Secure_Boot_Setup "Secure Boot Setup") * [Security Reporting](https://pve.proxmox.com/wiki/Security_Reporting "Security Reporting") * [Separate Cluster Network](https://pve.proxmox.com/wiki/Separate_Cluster_Network "Separate Cluster Network") * [Serial Terminal](https://pve.proxmox.com/wiki/Serial_Terminal "Serial Terminal") * [Service daemons](https://pve.proxmox.com/wiki/Service_daemons "Service daemons") * [Setup Simple Zone With SNAT and DHCP](https://pve.proxmox.com/wiki/Setup_Simple_Zone_With_SNAT_and_DHCP "Setup Simple Zone With SNAT and DHCP") * [Shrink Qcow2 Disk Files](https://pve.proxmox.com/wiki/Shrink_Qcow2_Disk_Files "Shrink Qcow2 Disk Files") * [Software RAID](https://pve.proxmox.com/wiki/Software_RAID "Software RAID") * [Solaris guest best practices](https://pve.proxmox.com/wiki/Solaris_guest_best_practices "Solaris guest best practices") * [SPICE](https://pve.proxmox.com/wiki/SPICE "SPICE") * [Storage Migration](https://pve.proxmox.com/wiki/Storage_Migration "Storage Migration") * [Stretch Cluster](https://pve.proxmox.com/wiki/Stretch_Cluster "Stretch Cluster") ### T * [Tape Drives](https://pve.proxmox.com/wiki/Tape_Drives "Tape Drives") * [Technical Writing Style Guide](https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide "Technical Writing Style Guide") * [Translations](https://pve.proxmox.com/wiki/Translations "Translations") * [Two-Factor Authentication](https://pve.proxmox.com/wiki/Two-Factor_Authentication "Two-Factor Authentication") ### U * [Upgrade a 4.x Installation using a newer ISO image](https://pve.proxmox.com/wiki/Upgrade_a_4.x_Installation_using_a_newer_ISO_image "Upgrade a 4.x Installation using a newer ISO image") * [Upgrade from 1.9 to 2.0](https://pve.proxmox.com/wiki/Upgrade_from_1.9_to_2.0 "Upgrade from 1.9 to 2.0") * [Upgrade from 2.3 to 3.0](https://pve.proxmox.com/wiki/Upgrade_from_2.3_to_3.0 "Upgrade from 2.3 to 3.0") * [Upgrade from 3.x to 4.0](https://pve.proxmox.com/wiki/Upgrade_from_3.x_to_4.0 "Upgrade from 3.x to 4.0") * [Upgrade from 4.x to 5.0](https://pve.proxmox.com/wiki/Upgrade_from_4.x_to_5.0 "Upgrade from 4.x to 5.0") * [Upgrade from 5.x to 6.0](https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0 "Upgrade from 5.x to 6.0") * [Upgrade from 6.x to 7.0](https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0 "Upgrade from 6.x to 7.0") * [Upgrade from 7 to 8](https://pve.proxmox.com/wiki/Upgrade_from_7_to_8 "Upgrade from 7 to 8") * [Upgrade from 8 to 9](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9 "Upgrade from 8 to 9") * [USB Devices in Virtual Machines](https://pve.proxmox.com/wiki/USB_Devices_in_Virtual_Machines "USB Devices in Virtual Machines") * [USB Redirector](https://pve.proxmox.com/wiki/USB_Redirector "USB Redirector") * [User Management](https://pve.proxmox.com/wiki/User_Management "User Management") ### V * [VM Backup Consistency](https://pve.proxmox.com/wiki/VM_Backup_Consistency "VM Backup Consistency") * [VM Templates and Clones](https://pve.proxmox.com/wiki/VM_Templates_and_Clones "VM Templates and Clones") * [VMA](https://pve.proxmox.com/wiki/VMA "VMA") * [VNC](https://pve.proxmox.com/wiki/VNC "VNC") * [VNC Client Access](https://pve.proxmox.com/wiki/VNC_Client_Access "VNC Client Access") ### W * [Web Interface Via Nginx Proxy](https://pve.proxmox.com/wiki/Web_Interface_Via_Nginx_Proxy "Web Interface Via Nginx Proxy") * [Windows 10 guest best practices](https://pve.proxmox.com/wiki/Windows_10_guest_best_practices "Windows 10 guest best practices") * [Windows 11 guest best practices](https://pve.proxmox.com/wiki/Windows_11_guest_best_practices "Windows 11 guest best practices") * [Windows 2003 guest best practices](https://pve.proxmox.com/wiki/Windows_2003_guest_best_practices "Windows 2003 guest best practices") * [Windows 2008 guest best practices](https://pve.proxmox.com/wiki/Windows_2008_guest_best_practices "Windows 2008 guest best practices") * [Windows 2012 guest best practices](https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices "Windows 2012 guest best practices") * [Windows 2016 guest best practices](https://pve.proxmox.com/wiki/Windows_2016_guest_best_practices "Windows 2016 guest best practices") * [Windows 2019 guest best practices](https://pve.proxmox.com/wiki/Windows_2019_guest_best_practices "Windows 2019 guest best practices") * [Windows 2022 guest best practices](https://pve.proxmox.com/wiki/Windows_2022_guest_best_practices "Windows 2022 guest best practices") * [Windows 2025 guest best practices](https://pve.proxmox.com/wiki/Windows_2025_guest_best_practices "Windows 2025 guest best practices") * [Windows 7 guest best practices](https://pve.proxmox.com/wiki/Windows_7_guest_best_practices "Windows 7 guest best practices") * [Windows 8 guest best practices](https://pve.proxmox.com/wiki/Windows_8_guest_best_practices "Windows 8 guest best practices") * [Windows guests - build ISOs including VirtIO drivers](https://pve.proxmox.com/wiki/Windows_guests_-_build_ISOs_including_VirtIO_drivers "Windows guests - build ISOs including VirtIO drivers") * [Windows NT Guest Notes](https://pve.proxmox.com/wiki/Windows_NT_Guest_Notes "Windows NT Guest Notes") * [Windows VirtIO Drivers](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers "Windows VirtIO Drivers") * [Windows XP Guest Notes](https://pve.proxmox.com/wiki/Windows_XP_Guest_Notes "Windows XP Guest Notes") * [WLAN](https://pve.proxmox.com/wiki/WLAN "WLAN") ### Y * [YubiKey](https://pve.proxmox.com/wiki/YubiKey "YubiKey") ### Z * [ZFS: Switch Legacy-Boot to Proxmox Boot Tool](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool "ZFS: Switch Legacy-Boot to Proxmox Boot Tool") * [ZFS: Tips and Tricks](https://pve.proxmox.com/wiki/ZFS:_Tips_and_Tricks "ZFS: Tips and Tricks") Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Category:HOWTO&oldid=116](https://pve.proxmox.com/mediawiki/index.php?title=Category:HOWTO&oldid=116) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Wanted categories - Proxmox VE Wanted categories ================= [Jump to navigation](https://pve.proxmox.com/wiki/Special:WantedCategories#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WantedCategories#searchInput) Showing below up to **5** results in range #**1** to #**5**. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WantedCategories&limit=20&offset=0 "Show 20 results per page") | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WantedCategories&limit=100&offset=0 "Show 100 results per page") | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WantedCategories&limit=250&offset=0 "Show 250 results per page") | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WantedCategories&limit=500&offset=0 "Show 500 results per page") ) 1. [Pages using deprecated source tags](https://pve.proxmox.com/mediawiki/index.php?title=Category:Pages_using_deprecated_source_tags&action=edit&redlink=1 "Category:Pages using deprecated source tags (page does not exist)") (5 members) 2. [Pages with syntax highlighting errors](https://pve.proxmox.com/mediawiki/index.php?title=Category:Pages_with_syntax_highlighting_errors&action=edit&redlink=1 "Category:Pages with syntax highlighting errors (page does not exist)") (5 members) 3. [Pages with too many expensive parser function calls](https://pve.proxmox.com/mediawiki/index.php?title=Category:Pages_with_too_many_expensive_parser_function_calls&action=edit&redlink=1 "Category:Pages with too many expensive parser function calls (page does not exist)") (1 member) 4. [Proxmox VE 4.x](https://pve.proxmox.com/mediawiki/index.php?title=Category:Proxmox_VE_4.x&action=edit&redlink=1 "Category:Proxmox VE 4.x (page does not exist)") (1 member) 5. [Staging](https://pve.proxmox.com/mediawiki/index.php?title=Category:Staging&action=edit&redlink=1 "Category:Staging (page does not exist)") (1 member) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WantedCategories&limit=20&offset=0 "Show 20 results per page") | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WantedCategories&limit=100&offset=0 "Show 100 results per page") | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WantedCategories&limit=250&offset=0 "Show 250 results per page") | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WantedCategories&limit=500&offset=0 "Show 500 results per page") ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WantedCategories](https://pve.proxmox.com/wiki/Special:WantedCategories) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # User:Thomas Lamprecht - Proxmox VE User:Thomas Lamprecht ===================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/User:Thomas_Lamprecht#mw-head) [Jump to search](https://pve.proxmox.com/wiki/User:Thomas_Lamprecht#searchInput) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=User:Thomas\_Lamprecht&oldid=7318](https://pve.proxmox.com/mediawiki/index.php?title=User:Thomas_Lamprecht&oldid=7318) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Additional ways to migrate to Proxmox VE - Proxmox VE Additional ways to migrate to Proxmox VE ======================================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#searchInput) **Note**: This article describes special cases kept for conservation purpose, we recommend the [Migrate to Proxmox VE](https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE "Migrate to Proxmox VE") and [Advanced Migration Techniques to Proxmox VE](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE "Advanced Migration Techniques to Proxmox VE") articles. Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#Introduction) * [2 SSH Migration of a Windows machine to a VM raw file](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#SSH_Migration_of_a_Windows_machine_to_a_VM_raw_file) * [3 Migrate a Windows machine to a VM logical volume using netcat](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#Migrate_a_Windows_machine_to_a_VM_logical_volume_using_netcat) * [4 Migration to a a smaller partition on a VM](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#Migration_to_a_a_smaller_partition_on_a_VM) * [4.1 FSArchiver](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#FSArchiver) * [4.2 mergeide](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#mergeide) * [5 Running FSArchiver from SystemRescueCd](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#Running_FSArchiver_from_SystemRescueCd) * [5.1 Backup the partition](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#Backup_the_partition) * [5.2 Restore the partition](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#Restore_the_partition) * [5.3 Successful cases](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#Successful_cases) * [6 SelfImage](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#SelfImage) * [6.1 Prepare the Windows operating system](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#Prepare_the_Windows_operating_system) * [6.2 Prepare the Proxmox VE VM](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#Prepare_the_Proxmox_VE_VM) * [6.3 Do the migration](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#Do_the_migration) * [7 Windows backup](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#Windows_backup) * [7.1 The Workflow](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#The_Workflow) * [7.2 Backup the physical machine](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#Backup_the_physical_machine) * [7.3 Cloning the virtual machine](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#Cloning_the_virtual_machine) * [7.4 Restore the backup on the virtual machine](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#Restore_the_backup_on_the_virtual_machine) * [7.5 Reboot the virtual machine](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#Reboot_the_virtual_machine) * [8 Windows systems specific issues](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#Windows_systems_specific_issues) * [8.1 inaccessible boot device](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#inaccessible_boot_device) * [8.2 Disk booting tips](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#Disk_booting_tips) * [8.3 Hidden non present devices](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#Hidden_non_present_devices) * [8.4 Other suggested pages](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#Other_suggested_pages) * [9 Fake Raid specific issues](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#Fake_Raid_specific_issues) * [10 Physical Linux server to Container](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#Physical_Linux_server_to_Container) * [11 Move OpenVZ containers to Proxmox VE](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#Move_OpenVZ_containers_to_Proxmox_VE) * [12 Convert Windows to use (VirtIO) SCSI (KVM)](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE#Convert_Windows_to_use_(VirtIO)_SCSI_(KVM)) Introduction ============ If you have not read the [main wiki article about migrating to Proxmox VE](https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE "Migrate to Proxmox VE") , or the [Advanced Migration Techniques to Proxmox VE](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE "Advanced Migration Techniques to Proxmox VE") article yet, you should do so now. They contain the most relevant options to migrate to Proxmox VE. In contrast, this article gathers years of knowledge for special cases. SSH Migration of a Windows machine to a VM raw file =================================================== Assumptions: * You have a physical machine in which you imported the [File:Mergeide.zip](https://pve.proxmox.com/wiki/File:Mergeide.zip "File:Mergeide.zip") , as shown on top of this page * The physical machine has disk device /dev/sda (read this with "fdisk -l", and look for "hda" or "sda" or similar, NOT dm- or other...) * You have already created a virtual machine with a raw type, file-based disk in stopped state. * The VM has VMID 101 (read this from the VM list in the web interface) Download [SystemRescueCD](http://www.sysresccd.org/) , burn it and reboot the physical machine with it in the CD tray. At its bash prompt, give eth0 an IP, or use DHCP: To assign IP: ifconfig eth0 192.168.1.10 netmask 255.255.255.0 up (use IP on same subnet as Proxmox VE server) To use DHCP: dhcpcd eth0 To start the image process on the physical machine: dd if=/dev/sda | ssh root@proxmox dd of=/var/lib/vz/images/vmid/diskname.raw Change the root@proxmox to root@yourproxmoxip and change the vmid/diskname to the VMID number and the name you want to call the disk. I.E. VMID 101 and disk called vm-101-disk-1.raw would be: dd if=/dev/sda | ssh root@proxmox dd of=/var/lib/vz/images/101/vm-101-disk-1.raw Once this completes you can assign this disk file to your VM on the Proxmox VE interface. Tested a 8GB physical server over gigabit network and was running in about 10 minutes. Migrate a Windows machine to a VM logical volume using netcat ============================================================= Assumptions: * You have a physical machine in which you imported the [File:Mergeide.zip](https://pve.proxmox.com/wiki/File:Mergeide.zip "File:Mergeide.zip") , as shown on top of this page * The physical machine has disk device /dev/sda (read this with "fdisk -l", and look for "hda" or "sda" or similar, NOT dm- or other...) * You have already created a virtual machine with a disk on LVM, larger in size than the physical machine one (at least 1 GB more), STOPPED, do NOT start it during this procedure! * The VM has VMID 103 (read this from the VM list in the web interface) * The LVM VG is named SHARED-VG (read this with: "vgdisplay -s") * So the LV partition is /dev/SHARED-VG/vm-103-disk-1 (read this with: "lvdisplay |grep LV|grep 103") Download [SystemRescueCD](http://www.sysresccd.org/) , burn it and reboot the physical machine with it in the CD tray. At its bash prompt, give eth0 an IP, coherent with the network of one Proxmox VE server (in the following example: 10.0.0.27): ifconfig eth0 10.0.0.17 netmask 255.255.255.0 up then assign root user a password, so you can log in via ssh: passwd Log in via SSH on both the physical machine and the Proxmox VE server. On the Proxmox VE server, give the command: date; netcat -w30 -vvnlp 3333 | gzip -dc > /dev/SHARED-VG/vm-103-disk-1; date and on the physical machine give the command: dd if=/dev/sda | gzip -c | nc -w30 -vvn 10.0.0.27 3333 You have to start the second command WITHIN 30 seconds of issuing the first one (the -w30...)! This way, the Proxmox VE machine is waiting for a stream of bytes on TCP port 3333, then gunzip it and redirects on the vm virtual disk. The physical machine outputs its ENTIRE disk as a stream of bytes, gzip it and pass it via netcat to the Proxmox VE server. The 2 date commands are useful to have a trace of when this process starts and ends. Tested migrating a 75GB disk in about 90 minutes on a 100Mbit LAN. VM started and worked as expected, after recognizing at first boot the new IDE controllers. An alternate method for Windows VMs is using **ntfsclone** with **ncat**. First, create the actual VM, and boot it with the System Rescue CD. Partition it to match the partition structure of the host machine. Once you have the partitions built out, you can copy the partitions directly from the source machine to the new VM. This will only copy used data. The commands are: On the destination system : \# nc -l -p 1234 | ntfsclone -r -O /dev/sda3 - On the source system : \# nc -s -o - /dev/sdb1 | netcat DestSrvIP 1234 Migration to a a smaller partition on a VM ========================================== While it's quite easy to "clone" a partition to another (real or virtual) of the same or bigger size, it's not so simple to do the same if the destination partition is smaller than the original one. This is possible, fortunately, and at least a proven method follows, but you have to take care of some pre-conditions: * Since you want to clone to a smaller partition, we will operate at the file system level, copying all the files from the source file system to the destination one. * So, we have to make sure that the destination partition **has** enough room to get all the files, at least, with better some free space left there. * The cloning is not possible directly, i.e disk-to-disk, but we have to "save" the source partition, and then "restore" it on the destination one. * Must be sure that the tools used are known very well as to how to copy files on the file systems involved, including symlinks, hardlinks, file system specific attributes, and so on. FSArchiver ---------- One free tool you can use for this is [FSArchiver](http://www.fsarchiver.org/) , which is a system tool that allows you to save the contents of a file-system to a compressed archive file. The file-system can be restored on a partition which has a different size and it can be restored on a different file-system. Unlike tar/dar, FSArchiver also creates the file-system when it extracts the data to partitions. Everything is check summed in the archive in order to protect the data. If the archive is corrupt, you just loose the current file, not the whole archive. FSArchiver is released under the GPL-v2 license. It's still under heavy development so it must not be used on critical data. So, you've been warned. Latest **FSArchiver** should be in the latest [SystemRescueCD](http://www.sysresccd.org/) , although you can obtain it on your favorite recent distribution. Cloning NTFS, **be sure** to use either version 0.6.10 or a patched previous version, because there was a bug that caused errors with NTFS junctions (something like Linux symlinks). If your origin physical server is configured in RAID-1 using "Fake Raid" (MB Bios raid), see the section about it in this article mergeide -------- As said above, install [File:Mergeide.zip](https://pve.proxmox.com/wiki/File:Mergeide.zip "File:Mergeide.zip") on the physical Windows machine (see [Microsoft KB article](http://support.microsoft.com/kb/314082/en-us) for details) to provide support for the natively supported IDE controllers in Windows. Without this, cloned XP booting failed for me. Running FSArchiver from SystemRescueCd ====================================== Use the latest SystemRescueCD available, that has a recent FSArchiver version: Confirm the version is right with: \# fsarchiver -V it should be at least "0.6.10", particularly if you are cloning NTFS file systems. Then run: \# fsarchiver probe simple that will report your disks/partitions current layout in a simple, understandable way, like: \[======DISK======\] \[=============NAME==============\] \[====SIZE====\] \[MAJ\] \[MIN\] \[sda \] \[WDC WD5002ABYS-5 \] \[ 15.00 GB\] \[ 8\] \[ 0\] \[=====DEVICE=====\] \[==FILESYS==\] \[======LABEL======\] \[====SIZE====\] \[MAJ\] \[MIN\] \[loop0 \] \[squashfs \] \[ \] \[ 671.85 MB\] \[ 7\] \[ 0\] \[sda1 \] \[ntfs \] \[System \] \[ 15.00 GB\] \[ 8\] \[ 1\] \[ramzswap0 \] \[swap \] \[ \] \[ 248.47 MB\] \[251\] \[ 0\] You have to provide a folder to save the partition "backup", which will be quite large (FSArchiver has several compression level, but just to be sure have enough free space there to accommodate all the uncompressed file...) if you need to reach a "tmpfolder" windows share, you have to install the **smbfs** package before (standard repositories), so that then you can \# mkdir /mnt/tmpfolder # mount -t smbfs //windows/tmpfolder /mnt/tmpfolder -o user=username giving a suitable password when asked. Backup the partition -------------------- Now you have to perform the "backup", **BE CAREFUL the first path is the backup file to save, the second the source partition, do not invert** I used: \# fsarchiver savefs -v -o /mnt/tmpfolder/physical.fsa /dev/sda1 (-v is verbose, shows each file is backing up, and if you have a lot of files and a slow video card can slow down a lot the entire process) Then (if no errors reported) run the same Live CD in a KVM VM with a 15GB virtual empty disk, better if a bit larger, (virtio), so /dev/vda. After mounting the smb share in the same way, run GParted (present in SystemRescueCd, startx to enter the graphical interface and run it) and created a empty NTFS partition there, /dev/vda1, and set the boot flag. Restore the partition --------------------- Then run **Note:** i use here **/dev/vda1** while the original was **/dev/sda1**, and **id=0** because i restore the **first** partition in the physical.fsa (yes, it may store more than one) as /dev/vda1 \# fsarchiver restfs -v /mnt/tmpfolder/physical.fsa id=0,dest=/dev/vda1 check if there are no restore errors. It was quite quick and just worked. Successful cases ---------------- * I successfully cloned an Windows XP professional machine from a physical 40GB (used 12GB) partition to a virtual (KVM) 15GB one, stored on Proxmox VE LVM. The archive file was around 7GB. (i had just 2 hard link restore errors, but in the log were reported on non critical files, although i would prefer 0 errors...) * I successfully cloned an Windows 2003 AD controller machine from a physical 250GB (used 5GB) partition to a virtual (KVM) 15GB one, stored on Proxmox VE LVM. The archive file was around 3,4GB. (i had just 0 restore errors of any kind) * Cloned a physical Ubuntu 9.04 desktop from a 32 raid5 disk to a virtual KVM 12 disk. Just had to reinstall grub to make it boot inside KVM. No errors. SelfImage ========= Warning : SelfImage does not do snapshot of physical disk. So, shutdown services and avoid writes during the copy process Prepare the Windows operating system ------------------------------------ Install [SelfImage](http://www.chip.de/downloads/SelfImage_30991577.html) on the physical Windows machine. Execute the [File:Mergeide.zip](https://pve.proxmox.com/wiki/File:Mergeide.zip "File:Mergeide.zip") (see [Microsoft KB article](http://support.microsoft.com/kb/314082/en-us) for details) to provide support for the natively supported IDE controllers in Windows. Prepare the Proxmox VE VM ------------------------- Create an new KVM container with a suitable disk size. It is recommended that you choose the size 1 GB bigger than the size of the physical disk that you want to migrate to make sure all your data fits to the virtual disk. Use VNC or SSH to connect to console on the Proxmox VE host. Export the qcow2 disk in the container directory with NBD qemu-nbd -t /var/lib/vz/images/xxx/vm-xxx-disk.qcow2 -p 1024 where xxx is the VM ID. If you use LVM as storage model, you can also export the logical volume created by Proxmox VE via the web interface qemu-nbd -t /dev/VolumeGroup/vm-xxx-disk-1 -p 1024 Do the migration ---------------- Start SelfImage on the physical machine, choose to image entire hard disk, not partition. On output file select NBD with your **PVE host IP** and **port 1024** as parameters. Click Start. When imaging is complete press CTRL+C on the PVE console to stop the export of your virtual disk file. Start the virtual machine and have fun. Windows backup ============== This may be useful if any other approach fails, or looks too complicated for you, as does not involve other software except Windows and PVE itself. It was used successfully to convert a live Windows 2000 server sp4 to PVE 1.5, and was inspired from a blog post related to a similar migration to XEN, but proved to be effective also for PVE, and probably any other VE around. Here is an [archive of the original blog post](http://replay.waybackmachine.org/20090203053232/http://blog.geekpoet.net/2008/05/manual-p2v-migration-of-windows-server.html) Here is the **[cache](https://pve.proxmox.com/mediawiki/images/8/8c/ManualP2V-with-NewSid.zip "ManualP2V-with-NewSid.zip") ** of the post along with the NewSID file. The Workflow ------------ This method is about * making a backup on your physical machine (pm) * creating a virtual machine (vm) from scratch, identical as possible to the pm * installing the same base OS of the pm on the vm, from the original supports * restoring the backup of the pm on the vm easy, uh? well, it works! Of course there are some point to take care of, and some drawbacks, too, but it is a very simple method, and you can find the drawbacks (if any) worth for the easiness you have in return! You don't need to get new software, or learn fancy Linux commands: all you got to know (and it's supposed you ALREADY know) is * how to create a vm in Proxmox VE (KVM) * how to make a backup/restore from windows (with the bundled software!) OK, follow me: Backup the physical machine --------------------------- The program you need is NTBackup, on a standard installation you can find it under the menu * Start/Program Files/Accessories/System utilities/Backup * if it has been removed, you can add it back from your windows CD Start a backup that includes * ALL the windows hard drives * the system state (this include the whole registry, IPs, hostname, and so on) Then, choose the "file" option as a destination * be sure to create this file on a network share, or a USB drive but NOT on the disks you are backing up * be sure that the network share has enough space to hold the BIG file... NOTE: Some services may "lock" some files in a way that NTBackup won't be able to copy them (while they're in use): * this is normal, and usually some of this locked files are: * files used by the open programs the logged user has (e.g. NTBackup logs...) * SQL data files, web server logs, and so on (usually running as services) * You can find "locked" files running NTBackup once, and then looking at its log for lines containing a "will be ignored" string * to find such lines in a BIG log file (mine had 250k lines) use the console FIND command ("c:\\FIND /?" is your friend) * the only workaround is, during the backup time frame: * close all the open (interactive) programs the logged user has * temporarily stop the services that are locking the files (if you can) Cloning the virtual machine --------------------------- * on PVE, you must create a vm configured just like the pm you want to migrate * same OS (you have to use a CD or a ISO for that) * same %WINDIR% folder name (e.g.: c:\\windows or c:\\winnt, etc), (the source blog post doesn't mention this but i did it...) * same SP (service pack applied) level, hotfixes, etc. * same CPU number * same page file configuration (the source blog post doesn't mention this but it turned out to matter in my conversion) * same drive layouts * number of disks and partitions, those on the vm must be at least equal in size to the pm ones * same drive letters mapping * same network card number Now, when your vm is just like your pm, except it doesn't have any of the programs and configuration the pm has: * add **one more temporary drive** to hold (temporary) files during the migration, assign it a drive letter not used in the pm * on this temporary drive, copy * the file **c:\\boot.ini** from the vm * the whole folder **c:\\windows\\repair** or **c:\\winnt\\repair**, or whatever your %WINDIR% is on your vm * the backup file you previously did with NTBackup, stored somewhere on your network Then, **before restoring**, switch the vm NIC to a non-used network in PVE, e.g.: * create a new fake bridge, not connected to any eth, * then delete the "working" vm NIC and * re-add another NIC on the vm, linked to the new fake bridge otherwise your new vm would "talk" to the real network / domain controllers, etc, and would result in a duplicate machine, duplicate IP address, and so on. This would be **BAD**. Restore the backup on the virtual machine ----------------------------------------- Log on to the vm and perform a restore of the backup file you have on the temporary disk * **note**: choose "always replace the files on my computer" (see tools>options>restore in NTBackup) **BEFORE REBOOTING** (at the end of the restore NTBackup asks you to reboot, hold down your mouse for a while...) * restore * the file **c:\\boot.ini** from the vm * the whole folder **c:\\windows\\repair** or **c:\\winnt\\repair**, or whatever your %WINDIR% is on your vm replacing those restored from the backup file. Reboot the virtual machine -------------------------- if you got any BSOD (blue screens) you may try to: * boot in safe mode * remove unrecognized components (e.g.: SCSI card) * make windows detect those components and reinstall drivers I didn't see any BSOD, so nothing to tell here. Otherwise, log on to the vm, * some component may not work, e.g. (mine) the mouse cursor may seem "out of sync" with the VNC one, be patient and wait because: * windows may recognize more virtual components and install them automatically (PCI, video, network, and so on: after a reboot they will work as expected) After that, you can * turn off the pm * on the vm add a NIC linked to the real network, assigning the real IP the pm had * reboot and log into the domain Windows systems specific issues =============================== inaccessible boot device ------------------------ Booting a virtual clone (IDE) of a physical Windows system partition may fail with a BSOD referring to the problem STOP: 0x0000007B (0xF741B84C,0xC0000034,0x00000000,0x00000000) INACCESSIBLE\_BOOT\_DEVICE this means that the source physical windows machine had no support for IDE controller, or at least the one virtually replaced by KVM (see [Microsoft KB article](http://support.microsoft.com/kb/314082/en-us) article for details): as Microsoft suggests, create a mergeide.reg file ([File:Mergeide.zip](https://pve.proxmox.com/wiki/File:Mergeide.zip "File:Mergeide.zip") ) file on the physical machine and merge that in the registry, '_before_ the P2V migration. By the way, it may not be necessary but should be no harm, anyway, and save you lots of time and headaches. Windows 2000: see [\[1\]](http://www.motherboard.windowsreinstall.com/problems.htm) Disk booting tips ----------------- * check that your disk has "boot flag" enabled (you can check this with GParted, on NTFS disks, booting the vm from a live CD ISO, see this [GParted manual page](http://gparted.sourceforge.net/docs/help-manual/C/gparted.html#gparted-fix-operating-system-boot-problems) ) maybe not so windows-specific but better remind it here. * be sure that boot.ini on your system partition is still suitable to your current disk/partition configuration (see this [kb article](http://support.microsoft.com/kb/124550) and this [kb article](http://support.microsoft.com/kb/102873) ) Hidden non present devices -------------------------- If your source physical machine had network interface controllers (NICs) with static IP assigned and then you clone the system to a vm, you will need to add a virtual Ethernet controller, provided by KVM, but Windows won't let you assign the same fixed IP to the new virtual NIC, because (it reports) there is a hidden and nonpresent devices already configured with the same IP (see [Microsoft KB article](http://support.microsoft.com/kb/241257) ). For sure it should be removed from windows "known" hardware but, you won't find it in "device management", even if you specify "show hidden peripherals", why? because Microsoft is complicated :-) To be able to see, and then remove the old physical NIC from "device management", you have to * open a console window * type: set devmgr\_show\_nonpresent\_devices = 1 and press enter * then, in the same console (do not close it) type: start devmgmt.msc and press enter * this will open the same "device management" panel you could have open from the "control panel", but now if you set the "show hidden peripherals" flag, the "nonpresent" devices will appear, although dimmed somehow, and you will be able to remove them, freeing the IP for your virtual NIC. Other suggested pages --------------------- * [Acpi setup](https://pve.proxmox.com/wiki/Acpi_kvm "Acpi kvm") * [Windows 2003 guest best practices](https://pve.proxmox.com/wiki/Windows_2003_guest_best_practices "Windows 2003 guest best practices") * [Paravirtualized Network Drivers for Windows](https://pve.proxmox.com/wiki/Paravirtualized_Network_Drivers_for_Windows "Paravirtualized Network Drivers for Windows") * [Paravirtualized Block Drivers for Windows](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows "Paravirtualized Block Drivers for Windows") Fake Raid specific issues ========================= If you have a physical PC to clone and you use a method that requires access to the file system (like with FSArchiver) from GNU/Linux, you can be in troubles if you have a so called "fake raid", that is a raid created using the motherboard bios configuration. Let's say we have a RAID1. In short GNU/Linux (i.e. SystemRescueCd) sees the device, sees that the disks have some Raid metadata, and when you try to mount them it uses the "mdadm" libraries, that can't work since that raid is totally different. To avoid this, you have to boot with the boot parameter 'nodmraid'. For example, if you boot with SystemRescueCd, at the menu where you can choose what to boot hit "tab" key You will have something like: ifcpu64.c32 rescue64 scandelay=1 -- rescue32 scandelay=1 modify it (on both sides of the "--" separator) like this: ifcpu64.c32 rescue64 scandelay=1 nodmraid -- rescue32 scandelay=1 nodmraid Physical Linux server to Container ================================== Take a look at these links if you want to migrate something that is not a Linux server to containers: * [How To Convert Physical Systems And Xen VMs Into OpenVZ Containers](http://howtoforge.com/how-to-convert-physical-systems-and-xen-vms-into-openvz-containers-debian-etch) * [Physical\_to\_container](http://wiki.openvz.org/Physical_to_container) Here we explain how to do a Physical-to-Virtual migration from a Linux installation into a Proxmox VE LXC container. Log into the machine you want to migrate into a PVE container as root and first stop any running services such as web servers or databases e.g. \`systemctl stop apache2\`, \`systemctl stop mysql\` etc. You need to be root (or run with sudo) so that tar can access and archive all files correctly using commands such as: \# cd / # tar -cvpzf backup.tar.gz --exclude=/backup.tar.gz / The tar -p switch is critical for preserving file permissions. Copy this tarball into the container templates cache directory on the PVE server which defaults to /var/lib/vz/template/cache . You may then create a new container using this tarball as a template via the web UI or using pct. If you choose to use the PVE web UI to create the new container, be sure to uncheck the 'Unprivileged Container' option (under the General options tab) else you are likely to run into file ownership issues. Creating a new privileged i386 container on ZFS storage with container ID 101 using pct would look something like this: \# pct create 101 local:vztmpl/backup.tar.gz -arch i386 -hostname your.hostname.here -onboot 1 -rootfs local-zfs:300 -memory 4096 -cores 2 Note this command doesn't configure networking. I enable networking after creating the container via the Proxmox web interface. Move OpenVZ containers to Proxmox VE ==================================== OpenVZ is depreacated and was superseeded by the Linux Container (LXC) project - which is using mainline kernel features. You can move existing OpenVZ containers (CT) with vzdump to Proxmox VE. Then check out the [Convert OpenVZ to LXC](https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC "Convert OpenVZ to LXC") article. Convert Windows to use (VirtIO) SCSI (KVM) ========================================== This procedure is required to get Windows to load and active the SCSI drivers, once active you can switch the disk and it should "Just Work". * With the VM powered off: * ensure the SCSI controller is set to VirtIO, this will work best on Windows 7 or newer. * add a new temporary SCSI virtual disk, can be small - for example, 0.1 GB big * add the VirtIO Driver ISO to a CD-ROM drive * Start the VM and make sure the drivers load for the new disk. You do not need to format it, just make sure you can see it in Device Manager * Shut down the Virtual Machine * detach the dummy disk and remove it afterwards * detach the real disk(s) and re-attach (edit) them as SCSI * Add the disks you just removed back as SCSI disks and boot the Virtual Machine. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Additional\_ways\_to\_migrate\_to\_Proxmox\_VE&oldid=11940](https://pve.proxmox.com/mediawiki/index.php?title=Additional_ways_to_migrate_to_Proxmox_VE&oldid=11940) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Statistics - Proxmox VE Statistics ========== [Jump to navigation](https://pve.proxmox.com/wiki/Special:Statistics#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:Statistics#searchInput) | Page statistics | | | --- | --- | | [Content pages](https://pve.proxmox.com/mediawiki/index.php?title=Special:AllPages&hideredirects=1 "Special:AllPages") | 256 | | [Pages](https://pve.proxmox.com/wiki/Special:AllPages "Special:AllPages")

(All pages in the wiki, including talk pages, redirects, etc.) | 1,577 | | [Uploaded files](https://pve.proxmox.com/wiki/Special:MediaStatistics "Special:MediaStatistics") | 370 | | Edit statistics | | | Page edits since Proxmox VE was set up | 12,773 | | Average edits per page | 8.10 | | User statistics | | | Registered users [(list of members)](https://pve.proxmox.com/wiki/Special:ListUsers "Special:ListUsers") | 797 | | Active users [(list of members)](https://pve.proxmox.com/wiki/Special:ActiveUsers "Special:ActiveUsers")

(Users who have performed an action in the last 30 days) | 7 | | [Bots](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_VE:Bots&action=edit&redlink=1 "Proxmox VE:Bots (page does not exist)")
[(list of members)](https://pve.proxmox.com/mediawiki/index.php?title=Special:ListUsers&group=bot "Special:ListUsers") | 0 | | [Administrators](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_VE:Administrators&action=edit&redlink=1 "Proxmox VE:Administrators (page does not exist)")
[(list of members)](https://pve.proxmox.com/mediawiki/index.php?title=Special:ListUsers&group=sysop "Special:ListUsers") | 8 | | [Interface administrators](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_VE:Interface_administrators&action=edit&redlink=1 "Proxmox VE:Interface administrators (page does not exist)")
[(list of members)](https://pve.proxmox.com/mediawiki/index.php?title=Special:ListUsers&group=interface-admin "Special:ListUsers") | 1 | | [Bureaucrats](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_VE:Bureaucrats&action=edit&redlink=1 "Proxmox VE:Bureaucrats (page does not exist)")
[(list of members)](https://pve.proxmox.com/mediawiki/index.php?title=Special:ListUsers&group=bureaucrat "Special:ListUsers") | 5 | | [Suppressors](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_VE:Suppress&action=edit&redlink=1 "Proxmox VE:Suppress (page does not exist)")
[(list of members)](https://pve.proxmox.com/mediawiki/index.php?title=Special:ListUsers&group=suppress "Special:ListUsers") | 1 | | [sysops](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_VE:Sysops&action=edit&redlink=1 "Proxmox VE:Sysops (page does not exist)")
[(list of members)](https://pve.proxmox.com/mediawiki/index.php?title=Special:ListUsers&group=sysops "Special:ListUsers") | 2 | Retrieved from "[https://pve.proxmox.com/wiki/Special:Statistics](https://pve.proxmox.com/wiki/Special:Statistics) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Broken redirects - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Redirects) Broken redirects ================ [Jump to navigation](https://pve.proxmox.com/wiki/Special:BrokenRedirects#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:BrokenRedirects#searchInput) The following redirects link to non-existent pages: Showing below up to **10** results in range #**1** to #**10**. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:BrokenRedirects&limit=20&offset=0 "Show 20 results per page") | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:BrokenRedirects&limit=100&offset=0 "Show 100 results per page") | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:BrokenRedirects&limit=250&offset=0 "Show 250 results per page") | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:BrokenRedirects&limit=500&offset=0 "Show 500 results per page") ) 1. [Certified Appliance: CYAN Secure Web](https://pve.proxmox.com/mediawiki/index.php?title=Certified_Appliance:_CYAN_Secure_Web&redirect=no "Certified Appliance: CYAN Secure Web") → [CYAN Secure Web](https://pve.proxmox.com/mediawiki/index.php?title=CYAN_Secure_Web&action=edit&redlink=1 "CYAN Secure Web (page does not exist)") 2. [Debian Etch standard (i386) Appliance](https://pve.proxmox.com/mediawiki/index.php?title=Debian_Etch_standard_(i386)_Appliance&redirect=no "Debian Etch standard (i386) Appliance") → [Debian 4.0 Standard](https://pve.proxmox.com/mediawiki/index.php?title=Debian_4.0_Standard&action=edit&redlink=1 "Debian 4.0 Standard (page does not exist)") 3. [Debian Etch Standard](https://pve.proxmox.com/mediawiki/index.php?title=Debian_Etch_Standard&redirect=no "Debian Etch Standard") → [Debian 4.0 Standard](https://pve.proxmox.com/mediawiki/index.php?title=Debian_4.0_Standard&action=edit&redlink=1 "Debian 4.0 Standard (page does not exist)") 4. [Dokumentation](https://pve.proxmox.com/mediawiki/index.php?title=Dokumentation&redirect=no "Dokumentation") → [Documentation](https://pve.proxmox.com/mediawiki/index.php?title=Documentation&action=edit&redlink=1 "Documentation (page does not exist)") 5. [Dokumentation/de](https://pve.proxmox.com/mediawiki/index.php?title=Dokumentation/de&redirect=no "Dokumentation/de") → [Documentation](https://pve.proxmox.com/mediawiki/index.php?title=Documentation&action=edit&redlink=1 "Documentation (page does not exist)") 6. [Tgt and Sheepdog](https://pve.proxmox.com/mediawiki/index.php?title=Tgt_and_Sheepdog&redirect=no "Tgt and Sheepdog") → [IScsi Target ( with tgt ) and Sheepdog](https://pve.proxmox.com/mediawiki/index.php?title=IScsi_Target_(_with_tgt_)_and_Sheepdog&action=edit&redlink=1 "IScsi Target ( with tgt ) and Sheepdog (page does not exist)") 7. [Special:Badtitle/NS100:MediaWiki](https://pve.proxmox.com/mediawiki/index.php?title=Special:Badtitle/NS100:MediaWiki&redirect=no "Special:Badtitle/NS100:MediaWiki") → [MediaWiki](https://pve.proxmox.com/mediawiki/index.php?title=MediaWiki&action=edit&redlink=1 "MediaWiki (page does not exist)") 8. [Certified Appliance: Proxmox Mail Gateway](https://pve.proxmox.com/mediawiki/index.php?title=Certified_Appliance:_Proxmox_Mail_Gateway&redirect=no "Certified Appliance: Proxmox Mail Gateway") → [Proxmox Mail Gateway](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_Mail_Gateway&action=edit&redlink=1 "Proxmox Mail Gateway (page does not exist)") 9. [User:Max Otto von Schtirliz](https://pve.proxmox.com/mediawiki/index.php?title=User:Max_Otto_von_Schtirliz&redirect=no "User:Max Otto von Schtirliz") → [Schtirliz](https://pve.proxmox.com/mediawiki/index.php?title=Schtirliz&action=edit&redlink=1 "Schtirliz (page does not exist)") 10. [Ubuntu 8.04 Minimal (Hardy)](https://pve.proxmox.com/mediawiki/index.php?title=Ubuntu_8.04_Minimal_(Hardy)&redirect=no "Ubuntu 8.04 Minimal (Hardy)") → [Ubuntu 8.04 Minimal](https://pve.proxmox.com/mediawiki/index.php?title=Ubuntu_8.04_Minimal&action=edit&redlink=1 "Ubuntu 8.04 Minimal (page does not exist)") View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:BrokenRedirects&limit=20&offset=0 "Show 20 results per page") | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:BrokenRedirects&limit=100&offset=0 "Show 100 results per page") | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:BrokenRedirects&limit=250&offset=0 "Show 250 results per page") | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:BrokenRedirects&limit=500&offset=0 "Show 500 results per page") ) Retrieved from "[https://pve.proxmox.com/wiki/Special:BrokenRedirects](https://pve.proxmox.com/wiki/Special:BrokenRedirects) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # System Software Updates - Proxmox VE System Software Updates ======================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/System_Software_Updates#mw-head) [Jump to search](https://pve.proxmox.com/wiki/System_Software_Updates#searchInput) Proxmox provides updates on a regular basis for all repositories. To install updates use the web-based GUI or the following CLI commands: \# apt-get update # apt-get dist-upgrade For occasionally upgrading Ceph to its succeeding major release, see [Ceph Repositories](https://pve.proxmox.com/wiki/Package_Repositories#sysadmin_package_repositories_ceph) . | | | | --- | --- | | ![Note]() | The APT package management system is very flexible and provides many features, see man apt-get, or [\[Hertzog13\]](https://pve.proxmox.com/wiki/Bibliography#Hertzog13)
for additional information. | | | | | --- | --- | | ![Tip]() | Regular updates are essential to get the latest patches and security related fixes. Major system upgrades are announced in the [Proxmox VE Community Forum](https://forum.proxmox.com/)
. | Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=System\_Software\_Updates&oldid=12315](https://pve.proxmox.com/mediawiki/index.php?title=System_Software_Updates&oldid=12315) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Reference Documentation](https://pve.proxmox.com/wiki/Category:Reference_Documentation "Category:Reference Documentation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Storage Plugin Development - Proxmox VE Storage Plugin Development ========================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Storage_Plugin_Development#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Storage_Plugin_Development#searchInput) Proxmox VE has a generic storage plugin system; in addition to the [natively included plugins](https://pve.proxmox.com/wiki/Storage#_storage_types "Storage") , there's also a mechanism for loading external third-party plugins. This wiki provides some basic documentation on how to develop plugins and important rules to follow when doing so. Contents -------- * [1 Licensing](https://pve.proxmox.com/wiki/Storage_Plugin_Development#Licensing) * [2 Plugin Architecture](https://pve.proxmox.com/wiki/Storage_Plugin_Development#Plugin_Architecture) * [2.1 Language Support](https://pve.proxmox.com/wiki/Storage_Plugin_Development#Language_Support) * [2.2 Loading Path](https://pve.proxmox.com/wiki/Storage_Plugin_Development#Loading_Path) * [2.3 API Versioning](https://pve.proxmox.com/wiki/Storage_Plugin_Development#API_Versioning) * [2.4 API](https://pve.proxmox.com/wiki/Storage_Plugin_Development#API) * [3 Integration Testing](https://pve.proxmox.com/wiki/Storage_Plugin_Development#Integration_Testing) * [4 Examples](https://pve.proxmox.com/wiki/Storage_Plugin_Development#Examples) * [4.1 Official Examples](https://pve.proxmox.com/wiki/Storage_Plugin_Development#Official_Examples) * [4.2 Third-Party Examples](https://pve.proxmox.com/wiki/Storage_Plugin_Development#Third-Party_Examples) * [5 Native Integration of Your Plugin](https://pve.proxmox.com/wiki/Storage_Plugin_Development#Native_Integration_of_Your_Plugin) * [6 Support and Help](https://pve.proxmox.com/wiki/Storage_Plugin_Development#Support_and_Help) Licensing --------- Your storage plugin code will be loaded by the AGPLv3+ licensed Proxmox VE system and therefore needs to be licensed to allow this. Note that this only affects the plugin code itself, not the source code of your actual storage system. To interface with proprietary code, you can, for example, run external binaries, use a (public) network API (such as over HTTP), or use a separate client library released under an AGPLv3+-compatible license. It's strongly recommended that you use one of the following three licenses for the plugin code, in order of preference: 1. [AGPL-3.0-or-later](https://spdx.org/licenses/AGPL-3.0-or-later.html) 2. [GPL-3.0-or-later](https://spdx.org/licenses/GPL-3.0-or-later.html) 3. [Apache-2.0](https://spdx.org/licenses/Apache-2.0.html) AND [MIT](https://spdx.org/licenses/MIT.html) Proxmox Server Solutions GmbH reserves the right to take legal action and/or actively break any external plugin if it is licensed under a proprietary license or one that does not comply with being combined into an AGPLv3+ project. Plugin Architecture ------------------- ### Language Support Plugins are Perl modules. Note that you can also create Perl bindings for other language, like through [Perl XS](https://perldoc.perl.org/perlxs) for C FFI/libraries or the Proxmox [perlmod](https://git.proxmox.com/?p=perlmod.git;a=blob;f=README.md;hb=HEAD) crate for rust based projects. ### Loading Path External Plugins are loaded from `/usr/share/perl5/PVE/Storage/Custom/YourCustomPlugin.pm`, and thus they must have a Perl package declaration like `package PVE::Storage::Custom::YourCustomPlugin;` We recommend that you release your storage plugin for Proxmox VE as Debian package. Doing so nicely integrates with how Proxmox VE is updated including declaring version dependencies or constraints with other packages. ### API Versioning The storage plugin system uses its own versioning for API backward compatibility, which is decoupled from the main Proxmox VE version, and the public REST API of Proxmox VE. The storage plugin's API versioning system is based consists of an `APIVER` and an `APIAGE`. * The `APIVER` is always bumped when the plugin API is changed, e.g., adding new methods, removing deprecated ones or expanding or changing the signature of an existing method. * The `APIAGE` is the number of versions we're backward compatible with, in other words, things (methods or params) got added without breaking anything unaware of it. This is often done by providing a default implementation, or value, that matches the previous behavior. For an example implementation that can handle API versioning with broad compatibility see [here](https://git.proxmox.com/?p=pve-storage-plugin-examples.git;a=blob;f=backup-provider-directory/src/PVE/Storage/Custom/BackupProviderDirExamplePlugin.pm;h=57df944c0475d914e2171c5b29744376eb057a5c;hb=HEAD#l37) . The API version changelog is tracked in the pve-storage git repository: [https://git.proxmox.com/?p=pve-storage.git;a=blob;f=ApiChangeLog](https://git.proxmox.com/?p=pve-storage.git;a=blob;f=ApiChangeLog) ### API In general, it's highly recommended to base your plugin of an included plugin, if unsure use the base plugin or the one your storage has the most similarities with. For example through: use base qw(PVE::Storage::Plugin); All (included) plugins are basing of the Proxmox [SectionConfig module](https://git.proxmox.com/?p=pve-common.git;a=blob;f=src/PVE/SectionConfig.pm) . If you decide to roll your own base for your plugin you need to ensure manually that you're compatible with the SectionConfig API. You must at least implement the following sub-methods: * `api` - return the `APIVER` version your plugin supports. * `type` - returns the storage section config string type that identifies your storage type. * `plugindata` - returns an object with metadata about what content types, formats and defaults your storage plugin supports. * `properties` - returns a schema of (additional) properties that your plugin needs or wants to support as configuration. * `option` - returns a schema of the options that your plugin understands, with specifying if they are optional or not. Note that the properties of all other plugins are available for use too. Then implement any sub-method with a `$class` as first argument from the [base-plugin](https://git.proxmox.com/?p=pve-storage.git;a=blob;f=src/PVE/Storage/Plugin.pm) for which you need a storage-specific behavior. Note: This section should be expanded, for now see the examples below and checkout the [existing included plugins](https://git.proxmox.com/?p=pve-storage.git;a=tree;f=src/PVE/Storage) and the [section config](https://git.proxmox.com/?p=pve-common.git;a=blob;f=src/PVE/SectionConfig.pm) source. Integration Testing ------------------- Currently, we recommend end-to-end testing by installing your plugin on an up-to-date Proxmox VE system and performing at least the following tasks * Add a new storage entry for your custom plugin. * Create at least one virtual machine (VM) and one container (CT) using the default configuration suggested by the guest creation wizard in the Proxmox VE management web UI. * Add a new disc volume to the Guests supported by your custom storage plugin. * Add a vTPM state drive. * Use that additional disk to run a IO benchmark tool like [fio](https://fio.readthedocs.io/en/latest/fio_doc.html) or [CrystalDiskMark](https://crystalmark.info/en/software/crystaldiskmark/) inside the virtual guest and ensure it outputs adequate performance. * For virtual machines you also should try other disk bus types than the default, e.g., VirtIO-Blk, SCSI (both VirtIO and LSI based) and potentially SATA/IDE for compatibility reasons. * Depending on the capabilities of your storage you should also try to: * Clone the disk. * Create a snapshot and rollback and/or clone the VM using that snapshot. * Create a backup (for file based or custom backup function). * Make sure that thin provisioning and discard are properly working. * Download a container template from our registry and download a ISO directly to the storage. * Purge a disk, e.g. by detaching it from a guest and then removing the unused disk entry. * Migrate both, a VM and a CT to another node. For the VM test both an online migration (VM is running) and an offline migration (VM is stopped). * Repeat the VM online live-migration with running the IO benchmark tool inside to generate IO load during migration. We're currently in the process of further improving the plugin developer experience, and as part of this we plan to create a small test suite to help ensure compliance with the API and interaction with the plugin system. However, this will never replace end-to-end testing, and we strongly recommend that you run a QA test on every major release of Proxmox VE, and ideally on every minor point release of Proxmox VE. Examples -------- ### Official Examples We currently provide a git repository hosting some examples, focusing on the backup provider API but with plans to extend for storage access in the future. See [https://git.proxmox.com/?p=pve-storage-plugin-examples.git;a=summary](https://git.proxmox.com/?p=pve-storage-plugin-examples.git;a=summary) See also the accompanying [Writing a Storage Plugin for SSHFS](https://pve.proxmox.com/wiki/Storage_Plugin_Development:_Writing_a_Storage_Plugin_for_SSHFS "Storage Plugin Development: Writing a Storage Plugin for SSHFS") wiki article. ### Third-Party Examples For some examples of real-world third party storage plugins see the following links: [https://github.com/LINBIT/linstor-proxmox/blob/master/LINSTORPlugin.pm](https://github.com/LINBIT/linstor-proxmox/blob/master/LINSTORPlugin.pm) [https://github.com/storpool/pve-storpool/blob/main/lib/PVE/Storage/Custom/StorPoolPlugin.pm](https://github.com/storpool/pve-storpool/blob/main/lib/PVE/Storage/Custom/StorPoolPlugin.pm) Native Integration of Your Plugin --------------------------------- For a storage plugin to be accepted as a native Proxmox VE plugin that is shipped by default and updated through the Proxmox VE repositories, both the plugin and the underlying storage implementation must be fully open source. The plugin must be compatible with the guidelines listed in the [#Licensing](https://pve.proxmox.com/wiki/Storage_Plugin_Development#Licensing) section. The storage implementation itself can use any open-source license. Taking a plugin into Proxmox VE's tree means we must ensure it is maintained and safe for our users, so we can provide enterprise support. For that, access to the source code is crucial. In addition to this baseline requirement, each storage technology will be evaluated on a case-by-case basis. Widespread adoption and demonstrating that you can provide continued maintenance of the backend for multiple years will significantly strengthen your case. You can distribute your plugin through your update channels. For example, a dedicated package repository provides close-to-native integration for your users. See the [Supplementary Chapters](https://pve.proxmox.com/wiki/Storage_Plugin_Development:_Writing_a_Storage_Plugin_for_SSHFS#Supplementary_Chapters "Storage Plugin Development: Writing a Storage Plugin for SSHFS") in the Storage Example How-To for more details. Support and Help ---------------- While Proxmox does not offer paid support or even development work for creating external storage plugins, you can ask any development related question on our [mailing list](https://pve.proxmox.com/wiki/Developer_Documentation#Mailing_List "Developer Documentation") . Please ask specific questions and provide your (work in progress) code, ideally as git repository. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Storage\_Plugin\_Development&oldid=12532](https://pve.proxmox.com/mediawiki/index.php?title=Storage_Plugin_Development&oldid=12532) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Development](https://pve.proxmox.com/wiki/Category:Development "Category:Development") * [Storage](https://pve.proxmox.com/wiki/Category:Storage "Category:Storage") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # User talk:Thomas Lamprecht - Proxmox VE User talk:Thomas Lamprecht ========================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/User_talk:Thomas_Lamprecht#mw-head) [Jump to search](https://pve.proxmox.com/wiki/User_talk:Thomas_Lamprecht#searchInput) **Welcome to _Proxmox VE_!** We hope you will contribute much and well. You will probably want to read the [help pages](https://pve.proxmox.com/mediawiki/index.php?title=Help:Contents&action=edit&redlink=1 "Help:Contents (page does not exist)") . Again, welcome and have fun! [Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") ([talk](https://pve.proxmox.com/wiki/User_talk:Martin "User talk:Martin") ) 11:32, 2 July 2015 (CEST) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=User\_talk:Thomas\_Lamprecht&oldid=7319](https://pve.proxmox.com/mediawiki/index.php?title=User_talk:Thomas_Lamprecht&oldid=7319) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Advanced Migration Techniques to Proxmox VE - Proxmox VE Advanced Migration Techniques to Proxmox VE =========================================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#Introduction) * [2 Physical-to-Virtual (P2V)](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#Physical-to-Virtual_(P2V)) * [2.1 Clonezilla Live CDs](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#Clonezilla_Live_CDs) * [2.2 VMware Converter](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#VMware_Converter) * [2.2.1 Prepare Windows](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#Prepare_Windows) * [2.2.2 Prepare location to save local image](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#Prepare_location_to_save_local_image) * [2.2.3 VMware vCenter Settings](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#VMware_vCenter_Settings) * [2.2.3.1 Prepare the VM on Proxmox VE](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#Prepare_the_VM_on_Proxmox_VE) * [2.2.3.2 Move the image to the Proxmox VE Server](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#Move_the_image_to_the_Proxmox_VE_Server) * [2.2.3.3 Converting to qcow2](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#Converting_to_qcow2) * [2.2.3.4 Final Steps](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#Final_Steps) * [2.2.3.5 Alternative Methods](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#Alternative_Methods) * [3 Virtual-to-Virtual (V2V)](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#Virtual-to-Virtual_(V2V)) * [3.1 VMware](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#VMware) * [3.1.1 Exporting](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#Exporting) * [3.1.1.1 GUI](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#GUI) * [3.1.1.2 CLI](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#CLI) * [3.1.2 Importing](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#Importing) * [3.1.3 Server self-migration](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#Server_self-migration) * [3.2 HyperV](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#HyperV) * [3.3 XEN](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#XEN) * [3.4 FreeNAS](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#FreeNAS) * [3.4.1 Preparation in FreeNAS](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#Preparation_in_FreeNAS) * [3.4.2 Importing to Proxmox VE](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#Importing_to_Proxmox_VE) * [3.5 RHEV](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#RHEV) * [3.6 QEMU/KVM](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#QEMU/KVM) * [4 Further information](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#Further_information) * [5 See Also](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#See_Also) * [6 References](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#References) Introduction ============ There are various ways to migrate existing servers to Proxmox VE. They can be divided into two categories: Physical-to-Virtual (P2V) Migration of physical servers to Proxmox VE Virtual-to-Virtual (V2V) Migration of virtual machines and containers from other hypervisors to Proxmox VE Physical-to-Virtual (P2V) ========================= Follow these how-to for a P2V migration, to turn a physical machine into a Proxmox VE hosted virtual machine. Clonezilla Live CDs ------------------- This method is fast, reliable and OS independent as it uses live CDs. * Get a live Linux CD like [Clonezilla](http://clonezilla.org/) . * Prepare the source host, make sure that you have standard IDE drivers enabled (for WinXP/Win2003 use the mergeide.reg ([File:Mergeide.zip](https://pve.proxmox.com/wiki/File:Mergeide.zip "File:Mergeide.zip") )), for W2k I followed this link (solution 2 worked for me): [\[1\]](http://www.motherboard.windowsreinstall.com/problems.htm) * Now, boot the physical host with Clonezilla, go for the beginner mode and select device - device and then remote, just follow the wizard * On the Proxmox VE host, prepare a KVM guest, make sure you got a big enough IDE disk assigned (add 1 GB extra to be on the safe side) and also boot this KVM guest with the Clonezilla live CD and execute a shell. * Become root and run fdisk (e.g., `fdisk /dev/sda`) to make sure that `sda` is here, exit fdisk by entering `w` and pressing enter, this is essential. * Now enter all commands that wizard on the source server instructs you too to configure the network and then start the disk copy. * After the clone operation succeeded, stop the VM, then change the boot device to the hard disk in the VM "Options" panel, and then start the VM again. Windows should install all needed drivers automatically, just the Intel NIC drivers for e1000 must be loaded from ISO VMware Converter ---------------- Physical (running) Windows server to Proxmox VE (KVM) using VMware vCenter Converter Standalone Client (V5) Tested on an HP ProLiant ML350 G5 and G6 ### Prepare Windows **VMware vCenter Converter Standalone Client** * Download [here](https://my.vmware.com/web/vmware/info/slug/infrastructure_operations_management/vmware_vcenter_converter_standalone/5_0) (version 5.x is Free Software and also free of charge but you need to create an account and login before download) **Mergeide.reg** * Execute mergeide.reg ([File:Mergeide.zip](https://pve.proxmox.com/wiki/File:Mergeide.zip "File:Mergeide.zip") ) ### Prepare location to save local image This guide is using an external USB Hard Drive. You may also save to a mapped network share. **NOTE** Although the final image will be around the same size as the actual amount of data on the server, the Proxmox VE server should have enough free space to fit the total physical disk of the server unless you plan to [shrink the windows disks.](http://pve.proxmox.com/wiki/Shrink_Qcow2_Disk_Files) once migrated to Proxmox VE. ### VMware vCenter Settings Launch VMware vCenter and use the following settings: * **Source type:** Powered-on machine * **Specify the powered-on machine:** This local machine * **Select destination type:** VMware Workstation or other VMware virtual machine * **Select VMware Product:** VMware Workstation 8.0.x * **Name:** Enter the desired name for the image * **Select a location for the virtual machine:** Browse to the USB or Network drive where the image will be saved. The next screen shows the settings for the virtual machine. Click on "Advanced options", select the Post-conversion tab and make sure ‘Install VMware Tools on the destination virtual machine’ is NOT check. We do not want to install VMware tools. Click next and then "Finish". It will now convert your physical machine to a `.vmdk` file. **NOTE:** Depending on your hardware, you may need to boot the `.vmdk` file using VMware Workstation or Player before moving the file to the Proxmox VE server. This allows windows to install additional drivers for the disk controller. If promoted to convert the disk to Workstation 9.x compatibility, say Yes. You won't know if you need this step until starting the Windows VM in the final step. If you get a blue screen during boot, you should try this step. #### Prepare the VM on Proxmox VE Create a new KVM virtual machine. You’ll want to use similar CPU and memory as the physical system. In the Hard Disk menu, leave everything as default. We won’t be using the disk created by Proxmox VE. Finish creating the VM. Make note of the VMID. For this guide, we’ll be using 100 as an example. Once the VMware converter has completed, disable all of the networks adapters on the physical server and shut down. Disabling the network adapters will avoid potential IP conflicts if you will start the physical server back into Windows after you have your new virtual server running. #### Move the image to the Proxmox VE Server Plug a USB Hard Drive into the server From the Proxmox VE command line: mkdir /mnt/usb mount /dev/sdc1 /mnt/usb/ ls /mnt/usb You should see the contents of the USB drive. In my case, the vmdk file was located in /mnt/usb/windows-server/ #### Converting to qcow2 We want to convert the .vmdk image file to qcow2. To do this, use the following command: qemu-img convert -f vmdk /mnt/usb/windows-server/windows-server.vmdk -O qcow2 /var/lib/vz/images/100/windows-server.qcow2 This can take a while depending on the size of file and speed of your system. #### Final Steps Once the conversion is complete, we need to edit the configuration file for the VM. nano /etc/pve/local/qemu-server/100.conf In the line with ide0: we want to change vm-100-disk-1.raw,size=32G to windows-server.qcow2 You may delete the empty disk created by Proxmox VE when you created the VM. rm /var/lib/vz/images/100/vm-100-disk-1.raw Start the VM and open the console. Windows should boot up normally. It’ll take a few minutes to detect the hardware changes. If the Windows system had a static IP address, you'll have to reconfigure the settings. #### Alternative Methods * [OpenVZ Template Creators](https://github.com/QuinnyPig/OpenVZ-Template-Creators) to create non Debian (we have [DAB](https://pve.proxmox.com/wiki/Debian_Appliance_Builder "Debian Appliance Builder") for it) templates. Virtual-to-Virtual (V2V) ======================== Follow these how-to for a V2V migration, to move a virtual machine (VM) from another hypervisor to VM on Proxmox VE. VMware ------ This explains the migration from a VMware ESXi 6.7 hypervisor to Proxmox VE 6.1. It is tested with guests with the following operating systems: * Debian 10 * Windows 10 Pro * Windows Server 2016 Standard ### Exporting #### GUI In VMware ESXi navigate to your virtual machine in the tree on the left. Choose Actions->Export. This will download disk images and information about your virtual machine in the .ovf format in the browser. Move those files to a storage that is accessible by your Proxmox VE host. #### CLI Install VMware's [ovftool](https://my.vmware.com/group/vmware/get-download?downloadGroup=OVFTOOL440) on your Proxmox VE host. ovftool version 4.4 has been reported to work with the following versions of ESXi: 6.5 and 6.7. Others (for example, [6.0](https://forum.proxmox.com/threads/unable-to-migrate-vm-from-esxi-6-0-0-to-proxmox-6-3-2.82301/post-362781) ) might crash with an unhelpful error message Remove any attached disk or ISO from your ESXi VM and run ovftool vi://root@/ . to export a virtual machine from ESXi directly into your current directory. You can replace the dot with any other path, for example "/mnt/pve/". This way you can export directly to a storage that you created in Proxmox VE. ℹ️ **Note**: You have to extract .ova archives With some configurations you get a single (.ova) archive file that contains all .vmdk disk images and the small XML description .ovf file. If this is the case, then you have to extract it before you continue with `qm importovf`. ### Importing Go to the command line interface of Proxmox VE. Use the command `qm importovf ` to import the virtual machine. For example: qm importovf 200 /tmp/exported-vm.ovf local-lvm This will create a new virtual machine using cores, memory and VM name as read from the OVF manifest, and import the disks. You have to configure the network manually. You can find syntax and an example on how to use this command on its [man page](https://pve.proxmox.com/pve-docs/qm.1.html) . ℹ️ **Note**: Windows guests require a few additional steps If you are migrating a Windows guest, you additionally have to execute the following commands. This example assumes that your imported virtual machine has the ID 130. * Use UEFI instead of BIOS for the virtual machine: qm set 130 --bios ovmf * Windows requires additional drivers to use SCSI. Therefore, you should temporarily use SATA instead. In the following command, 'scsi0' should be replaced with the drive that's used to boot Windows. sed -i 's/scsi0:/sata0:/' /etc/pve/qemu-server/130.conf This will give you a initial working version. You can then improve your experience and access remaining SCSI drives by installing additional drivers as explained in [Windows 10 guest best practices](https://pve.proxmox.com/wiki/Windows_10_guest_best_practices "Windows 10 guest best practices") . ### Server self-migration It is also possible to migrate without the need to export each VM separately including virtual disks. This way, you can convert a server from vSphere to Proxmox VE without the need of a second server. For this process your vSphere should use VMFS6 and you need at least one empty HDD. 1\. Export the VM information without the disks using ovftool (you still need to configure the network configuration for each VM). ovftool --noDisks vi://root@/ . 2\. Install Proxmox VE on some disk that does not contain any important data. You don't need vSphere anymore at this point. If you have an OS disk with only vSphere on it, then you can now overwrite it with Proxmox VE. **Warning**: Do not use/touch any other existing drives which are VMFS formatted 3\. Create a directory on the above mention spare HDD. 4\. Install vmfs6-tools which you need to mount (ready-only) the VMFS-formatted drives with the vSphere virtual disks. apt install vmfs6-tools -y 5\. List all available drives to identify the VMFS formatted ones fdisk -l 6\. Mount the VMFS disk partition (note it is read only) vmfs6-tool /dev/ 7\. Convert the vSphere disk to a suitable format for Proxmox VE qemu-img convert -f vmdk .vmdk -O .raw/qcow2 -p 8\. While the conversion is in progress you may create the 1st VM from ovf qm importovf 200 /tmp/exported-vm.ovf 9\. As soon as the conversion is finished you may mount the new Proxmox VE disk image to the VM. qm rescan If all VM images have been moved away from a VMFS6 disk, you can format it and use it at Proxmox VE HyperV ------ This explains the migration from a Hyper-V on Windows 10 hypervisor to Proxmox VE 6.1. It is tested with a Proxmox VE 6.1 guest. Proxmox VE uses [qemu-img](https://manpages.debian.org/testing/qemu-utils/qemu-img.1.en.html) to import disks. In my tests it supported .vhdx even though [some sources](https://linux.die.net/man/1/qemu-img) don't explicitly list .vhdx as supported format. There are additional options if this should not work anymore: * [Convert-VHD](https://docs.microsoft.com/en-us/powershell/module/hyper-v/convert-vhd?view=win10-ps) is a command line tool that is built-in in Windows and converts .vhdx to .vhd. This format is supported by qemu-img. * [StarWind V2V Converter](https://www.starwindsoftware.com/starwind-v2v-converter) is a graphical tool that can create .qcow2 disks from Hyper-V guests. In Hyper-V-Manager choose "Export..." at the right side and then a destination. While many files (for example for snapshots) will be exported, we are only interested in the .vhdx file(s). Move those files to a storage that is accessible by your Proxmox VE host. You will have to recreate the virtual machine settings yourself. Go to the GUI of Proxmox VE and create a new virtual machine. We don't need the hard disk that the virtual machine creation wizard created. Delete it in the hardware options of the virtual machine. Now go to the command line interface of Proxmox VE. Use the command "qm importdisk" to import the .vhdx virtual hard disk. You can find syntax and an example on how to use this command on its man page. XEN --- XEN also uses qemu disk format, so it should work in the same manner as described under "[VMware to Proxmox VE](https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#VMware "Migration of servers to Proxmox VE") ". You could use [xenmigrate](https://pve.proxmox.com/wiki/Xenmigrate "Xenmigrate") to do it. FreeNAS ------- Those are the necessary steps to migrate a Ubuntu Bionic VM from FreeNAS 11.2 to Proxmox VE 6.2-1. The VM in FreeNAS was created with the following parameters * Boot Loader Type: UEFI * Guest OS: Ubuntu Bionic * Disk * Disk Mode: AHCI * Zvol: test/ubuntu-1xmtpt Check the name of your zvol by going to Virtual Machines → Options of the VM ⋮→ Devices → Options of your disk ⋮ → Edit → Zvol ### Preparation in FreeNAS 1. Create a shared directory in Sharing → Unix (NFS) Shares with path `/mnt/test`. 2. Enable SSH in Services & edit the SSH service (Actions) to allow password login for root 3. Copy the zvol to the shared directory 1. Log in to FreeNAS via SSH ssh root@ip.of.your.freenas 2. Copy the zvol to the shared directory dd if=/dev/zvol/test/ubuntu-1xmtpt of=/mnt/test/ubuntu.raw bs=1m ### Importing to Proxmox VE 1. Create a virtual machine (here vmid is 103) in Proxmox VE. Make sure to set BIOS to OVMF (this is UEFI). 2. Delete the disk that was created in step 1. 3. Create a directory `mkdir /home/user/freenas` 4. Mount the shared directory from FreeNAS sudo mount -t nfs 192.168.31.241:/mnt/test /home/user/freenas 5. Import the image of the FreeNAS VM to the Proxmox VE VM as unused disk (vmid 103, storage local) qm importdisk 103 /home/user/freenas/ubuntu.raw local --format qcow2 6. In the GUI of Proxmox VE: 1. Go to the hardware view of your new virtual machine 2. Set the display to spice 3. Double click on the unused disk to attach it and choose Virtio as bus 4. Go to the options view of your new virtual machine 5. Choose your new virtio disk as bootdisk RHEV ---- The last released version of Red Hat Enterprise Virtualization (RHEV) is out of full support since August 2022[\[1\]](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#cite_note-1) and you might want migrate to a supported Proxmox VE releases earlier than it's EOL date. To move existing VMs you need to [export them as OVA](https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html/virtual_machine_management_guide/sect-exporting_and_importing_virtual_machines_and_templates#Exporting_a_virtual_machine_to_a_host) ([archived docs](https://web.archive.org/web/20221220103326/https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html/virtual_machine_management_guide/sect-exporting_and_importing_virtual_machines_and_templates#Exporting_a_virtual_machine_to_a_host) ). You should be able to do so by selecting the virtual machine, use the `More Actions` menu and there click on `Export to OVA` and use a directory or share that PVE either can directly access or easily moved later on. On the Proxmox VE side you can extract the OVA, for example with `tar xf exported-vm.ova` for the more common tar format (or `unzip` if compressed as zip archive). Then you can use `qm importovf VMID /path/to/extracted.ovf` and `qm importdisk VMID PATH/TO/DISK.img STORAGE-ID` QEMU/KVM -------- 1. Create an new VM on Proxmox VE 2. add the existing disk image to the new VM 3. add network, usb, pcie, ... devices as they where in the original VM 4. set the boot order and adapt other options 5. start the VM **Basic Example, Step-by-Step**: First a VM has to be created, for that you need to select an unused VMID (e.g., use pvecm nextid. qm create 120 In the next step the `some-image.img` refers to the disk image you want to import and the `some-storage` refers to the name of a target storage, as listed in `pvesm status`. Please adapt those to the respective values. qm disk import 120 some-image.img some-storage Please note that `qm importdisk` adds the image as unused disk to the virtual machine, you can re-attach it to the VM via the web-interface. You also need to mark it as a boot-disk, this can be done by using `qm set 120 --boot order=scsi0`. qm set 120 --scsi0 some-storage:vm-120-disk-0 **Basic Example: All-in-One**: Since Proxmox VE 7.2 you can use the `qm create` command to achieve all steps in one go: qm create VMID --scsi0 STORAGE:0,import-from=/PATH/TO/DISK.IMG --boot order=scsi0 Please replace ALL-CAPS parts with the respective value. After that you can adapt the remaining basics (memory, vCPU core count, vNICs, ...) via the web-interface. Further information =================== If your use case is not covered by this article you should check out the [additional ways to migrate to Proxmox VE](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE "Additional ways to migrate to Proxmox VE") in the wiki. It gathers years of knowledge for cases which are not as common as the ones explained here, but sometimes is also rather outdated. See Also ======== * [Migrate to Proxmox VE](https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE "Migrate to Proxmox VE") * [Reference docs for importing VMs and their disk images](https://pve.proxmox.com/pve-docs/chapter-qm.html#_importing_virtual_machines_and_disk_images) . References ========== 1. [↑](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#cite_ref-1) [https://access.redhat.com/support/policy/updates/rhev](https://access.redhat.com/support/policy/updates/rhev) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Advanced\_Migration\_Techniques\_to\_Proxmox\_VE&oldid=11942](https://pve.proxmox.com/mediawiki/index.php?title=Advanced_Migration_Techniques_to_Proxmox_VE&oldid=11942) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Open Source - Proxmox VE Open Source =========== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Open_Source#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Open_Source#searchInput) * Proxmox VE 1.x is licensed under the [Gnu General Public License version 2](http://www.gnu.org/licenses/gpl-2.0.html) * Proxmox VE 2.x and higher versions are licensed under the [GNU Affero General Public License, version 3](http://www.gnu.org/licenses/agpl-3.0.html) See Also -------- * [Developer\_Documentation](https://pve.proxmox.com/wiki/Developer_Documentation "Developer Documentation") * [GIT](https://git.proxmox.com/) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Open\_Source&oldid=10518](https://pve.proxmox.com/mediawiki/index.php?title=Open_Source&oldid=10518) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Archive](https://pve.proxmox.com/wiki/Category:Archive "Category:Archive") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Anatomy of LXC Container Config File - Proxmox VE Anatomy of LXC Container Config File ==================================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Anatomy_of_LXC_Container_Config_File#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Anatomy_of_LXC_Container_Config_File#searchInput) Contents -------- * [1 Location](https://pve.proxmox.com/wiki/Anatomy_of_LXC_Container_Config_File#Location) * [2 Mounting the rootfs](https://pve.proxmox.com/wiki/Anatomy_of_LXC_Container_Config_File#Mounting_the_rootfs) * [2.1 Anatomy](https://pve.proxmox.com/wiki/Anatomy_of_LXC_Container_Config_File#Anatomy) * [3 Other Mount Info](https://pve.proxmox.com/wiki/Anatomy_of_LXC_Container_Config_File#Other_Mount_Info) Location -------- For PVE Node: **pr64** and CT **101** the location is at /etc/pve/nodes/pr64/lxc/101.conf This configuration gets copied over **on startup** of the container to /etc/pve/lxc/101.conf Mounting the rootfs ------------------- * [local-lvm to local storage](https://tweenpath.net/proxmox-change-local-lvm-local-storage/) ### Anatomy pct mount 101 mounted CT 101 in '/var/lib/lxc/101/rootfs' ls -al /var/lib/lxc/101/rootfs total 96 drwxr-xr-x 21 100000 100000 4096 Sep 28 22:27 . drwxr-xr-x 3 root root 4096 Sep 28 23:32 .. drwxr-xr-x 2 100000 100000 4096 Sep 28 22:05 bin drwxr-xr-x 2 100000 100000 4096 Jul 14 2014 boot drwxr-xr-x 2 100000 100000 4096 Dec 10 2008 dev drwxr-xr-x 61 100000 100000 4096 Sep 28 22:27 etc drwxr-xr-x 2 100000 100000 4096 Jul 14 2014 home drwxr-xr-x 8 100000 100000 4096 Sep 28 22:05 lib drwx------ 2 root root 16384 Sep 28 22:27 lost+found drwxr-xr-x 2 100000 100000 4096 Sep 28 22:04 media drwxr-xr-x 2 100000 100000 4096 Jul 14 2014 mnt drwxr-xr-x 2 100000 100000 4096 Sep 28 22:04 opt drwxr-xr-x 2 100000 100000 4096 Jul 14 2014 proc drwx------ 2 100000 100000 4096 Sep 28 22:31 root drwxr-xr-x 2 100000 100000 4096 Sep 28 22:06 sbin drwxr-xr-x 2 100000 100000 4096 Jul 21 2010 selinux drwxr-xr-x 2 100000 100000 4096 Sep 28 22:04 srv drwxr-xr-x 2 100000 100000 4096 Mar 28 2012 sys drwxrwxrwt 4 100000 100000 4096 Sep 28 23:09 tmp drwxr-xr-x 10 100000 100000 4096 Sep 28 22:04 usr drwxr-xr-x 14 100000 100000 4096 Sep 28 22:05 var pct unmount 101 Copy a local file to the container. pct push \[OPTIONS\] Copy a file from the container to the local system. pct pull \[OPTIONS\] Other Mount Info ---------------- * [Zamba LXC Toolbox](https://github.com/bashclub/zamba-lxc-toolbox) * [Mounting into a container](https://forum.proxmox.com/threads/mount-host-directory-into-lxc-container.66555/post-299027) - [bind mount for LXC](https://www.jamescoyle.net/how-to/2019-proxmox-4-x-bind-mount-mount-storage-in-an-lxc-container) - will not remove the mount point and that has to be done manually. * [LXC on flat File System](https://forum.proxmox.com/threads/does-proxmox-support-lxc-dir-backend.98486/post-425822) * [DIY Add Disks](https://www.diytechguru.com/2020/12/12/proxmox-lvm-directory/) * [Mount existing Storage](https://forum.proxmox.com/threads/how-to-mount-existing-disk-to-storage.66559/) mkdir /mnt/bak mount /dev/sddX /mnt/bak (this is only persistent until the next reboot) You should then be able to browse the files of that storage in **/mnt/bak** Configure storage in PVE GUI or use the CLI: pvesm add dir bak --path /mnt/bak --content backup Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Anatomy\_of\_LXC\_Container\_Config\_File&oldid=11465](https://pve.proxmox.com/mediawiki/index.php?title=Anatomy_of_LXC_Container_Config_File&oldid=11465) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Prepare Installation Media - Proxmox VE Prepare Installation Media ========================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Prepare_Installation_Media#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Prepare_Installation_Media#searchInput) Download the installer ISO image from: [https://www.proxmox.com/en/downloads/proxmox-virtual-environment/iso](https://www.proxmox.com/en/downloads/proxmox-virtual-environment/iso) The Proxmox VE installation media is a hybrid ISO image. It works in two ways: * An ISO image file ready to burn to a CD or DVD. * A raw sector (IMG) image file ready to copy to a USB flash drive (USB stick). Using a USB flash drive to install Proxmox VE is the recommended way because it is the faster option. Prepare a USB Flash Drive as Installation Medium ------------------------------------------------ The flash drive needs to have at least 1 GB of storage available. | | | | --- | --- | | ![Note]() | Do not use UNetbootin. It does not work with the Proxmox VE installation image. | | | | | --- | --- | | ![Important]() | Make sure that the USB flash drive is not mounted and does not contain any important data. | Instructions for GNU/Linux -------------------------- On Unix-like operating system use the dd command to copy the ISO image to the USB flash drive. First find the correct device name of the USB flash drive (see below). Then run the dd command. \# dd bs=1M conv=fdatasync if=./proxmox-ve\_\*.iso of=/dev/XYZ | | | | --- | --- | | ![Note]() | Be sure to replace /dev/XYZ with the correct device name and adapt the input filename (_if_) path. | | | | | --- | --- | | ![Caution]() | Be very careful, and do not overwrite the wrong disk! | ### Find the Correct USB Device Name There are two ways to find out the name of the USB flash drive. The first one is to compare the last lines of the dmesg command output before and after plugging in the flash drive. The second way is to compare the output of the lsblk command. Open a terminal and run: \# lsblk Then plug in your USB flash drive and run the command again: \# lsblk A new device will appear. This is the one you want to use. To be on the extra safe side check if the reported size matches your USB flash drive. Instructions for macOS ---------------------- Open the terminal (query Terminal in Spotlight). Convert the .iso file to .dmg format using the convert option of hdiutil, for example: \# hdiutil convert proxmox-ve\_\*.iso -format UDRW -o proxmox-ve\_\*.dmg | | | | --- | --- | | ![Tip]() | macOS tends to automatically add _.dmg_ to the output file name. | To get the current list of devices run the command: \# diskutil list Now insert the USB flash drive and run this command again to determine which device node has been assigned to it. (e.g., /dev/diskX). \# diskutil list # diskutil unmountDisk /dev/diskX | | | | --- | --- | | ![Note]() | replace X with the disk number from the last command. | \# sudo dd if=proxmox-ve\_\*.dmg bs=1M of=/dev/rdiskX | | | | --- | --- | | ![Note]() | _rdiskX_, instead of _diskX_, in the last command is intended. It will increase the write speed. | Instructions for Windows ------------------------ ### Using Etcher Etcher works out of the box. Download Etcher from [https://etcher.io](https://etcher.io/) . It will guide you through the process of selecting the ISO and your USB flash drive. ### Using Rufus Rufus is a more lightweight alternative, but you need to use the **DD mode** to make it work. Download Rufus from [https://rufus.ie/](https://rufus.ie/) . Either install it or use the portable version. Select the destination drive and the Proxmox VE ISO file. | | | | --- | --- | | ![Important]() | Once you _Start_ you have to click _No_ on the dialog asking to download a different version of GRUB. In the next dialog select the _DD_ mode. | Boot your Server from the USB Flash Drive ----------------------------------------- Connect the USB flash drive to your server and make sure that booting from USB is enabled (check your servers firmware settings). Then follow the steps in the [installation wizard](https://pve.proxmox.com/wiki/Installation#chapter_installation) . Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Prepare\_Installation\_Media&oldid=11842](https://pve.proxmox.com/mediawiki/index.php?title=Prepare_Installation_Media&oldid=11842) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Reference Documentation](https://pve.proxmox.com/wiki/Category:Reference_Documentation "Category:Reference Documentation") * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Prepare Installation Media - Proxmox VE Prepare Installation Media ========================== From Proxmox VE (Redirected from [Install from USB Stick](https://pve.proxmox.com/mediawiki/index.php?title=Install_from_USB_Stick&redirect=no "Install from USB Stick") ) [Jump to navigation](https://pve.proxmox.com/wiki/Install_from_USB_Stick#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Install_from_USB_Stick#searchInput) Download the installer ISO image from: [https://www.proxmox.com/en/downloads/proxmox-virtual-environment/iso](https://www.proxmox.com/en/downloads/proxmox-virtual-environment/iso) The Proxmox VE installation media is a hybrid ISO image. It works in two ways: * An ISO image file ready to burn to a CD or DVD. * A raw sector (IMG) image file ready to copy to a USB flash drive (USB stick). Using a USB flash drive to install Proxmox VE is the recommended way because it is the faster option. Prepare a USB Flash Drive as Installation Medium ------------------------------------------------ The flash drive needs to have at least 1 GB of storage available. | | | | --- | --- | | ![Note]() | Do not use UNetbootin. It does not work with the Proxmox VE installation image. | | | | | --- | --- | | ![Important]() | Make sure that the USB flash drive is not mounted and does not contain any important data. | Instructions for GNU/Linux -------------------------- On Unix-like operating system use the dd command to copy the ISO image to the USB flash drive. First find the correct device name of the USB flash drive (see below). Then run the dd command. \# dd bs=1M conv=fdatasync if=./proxmox-ve\_\*.iso of=/dev/XYZ | | | | --- | --- | | ![Note]() | Be sure to replace /dev/XYZ with the correct device name and adapt the input filename (_if_) path. | | | | | --- | --- | | ![Caution]() | Be very careful, and do not overwrite the wrong disk! | ### Find the Correct USB Device Name There are two ways to find out the name of the USB flash drive. The first one is to compare the last lines of the dmesg command output before and after plugging in the flash drive. The second way is to compare the output of the lsblk command. Open a terminal and run: \# lsblk Then plug in your USB flash drive and run the command again: \# lsblk A new device will appear. This is the one you want to use. To be on the extra safe side check if the reported size matches your USB flash drive. Instructions for macOS ---------------------- Open the terminal (query Terminal in Spotlight). Convert the .iso file to .dmg format using the convert option of hdiutil, for example: \# hdiutil convert proxmox-ve\_\*.iso -format UDRW -o proxmox-ve\_\*.dmg | | | | --- | --- | | ![Tip]() | macOS tends to automatically add _.dmg_ to the output file name. | To get the current list of devices run the command: \# diskutil list Now insert the USB flash drive and run this command again to determine which device node has been assigned to it. (e.g., /dev/diskX). \# diskutil list # diskutil unmountDisk /dev/diskX | | | | --- | --- | | ![Note]() | replace X with the disk number from the last command. | \# sudo dd if=proxmox-ve\_\*.dmg bs=1M of=/dev/rdiskX | | | | --- | --- | | ![Note]() | _rdiskX_, instead of _diskX_, in the last command is intended. It will increase the write speed. | Instructions for Windows ------------------------ ### Using Etcher Etcher works out of the box. Download Etcher from [https://etcher.io](https://etcher.io/) . It will guide you through the process of selecting the ISO and your USB flash drive. ### Using Rufus Rufus is a more lightweight alternative, but you need to use the **DD mode** to make it work. Download Rufus from [https://rufus.ie/](https://rufus.ie/) . Either install it or use the portable version. Select the destination drive and the Proxmox VE ISO file. | | | | --- | --- | | ![Important]() | Once you _Start_ you have to click _No_ on the dialog asking to download a different version of GRUB. In the next dialog select the _DD_ mode. | Boot your Server from the USB Flash Drive ----------------------------------------- Connect the USB flash drive to your server and make sure that booting from USB is enabled (check your servers firmware settings). Then follow the steps in the [installation wizard](https://pve.proxmox.com/wiki/Installation#chapter_installation) . Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Prepare\_Installation\_Media&oldid=11842](https://pve.proxmox.com/mediawiki/index.php?title=Prepare_Installation_Media&oldid=11842) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Reference Documentation](https://pve.proxmox.com/wiki/Category:Reference_Documentation "Category:Reference Documentation") * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Upgrade from 8 to 9 - Proxmox VE Upgrade from 8 to 9 =================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Introduction) * [2 New installation](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#New_installation) * [3 Breaking Changes](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Breaking_Changes) * [4 In-place upgrade](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#In-place_upgrade) * [4.1 Prerequisites](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Prerequisites) * [4.2 Testing the Upgrade](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Testing_the_Upgrade) * [4.3 Actions step-by-step](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Actions_step-by-step) * [4.3.1 Continuously use the **pve8to9** checklist script](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Continuously_use_the_pve8to9_checklist_script) * [4.3.2 Move important Virtual Machines and Containers](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Move_important_Virtual_Machines_and_Containers) * [4.3.3 Update the configured APT repositories](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Update_the_configured_APT_repositories) * [4.3.3.1 Update Debian Base Repositories to Trixie](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Update_Debian_Base_Repositories_to_Trixie) * [4.3.3.2 Add the Proxmox VE 9 Package Repository](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Add_the_Proxmox_VE_9_Package_Repository) * [4.3.3.3 Update the Ceph Package Repository](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Update_the_Ceph_Package_Repository) * [4.3.3.4 Refresh Package Index](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Refresh_Package_Index) * [4.3.4 Upgrade the system to Debian Trixie and Proxmox VE 9.0](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Upgrade_the_system_to_Debian_Trixie_and_Proxmox_VE_9.0) * [4.3.5 Check Result & Reboot Into Updated Kernel](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Check_Result_&_Reboot_Into_Updated_Kernel) * [4.4 After the Proxmox VE upgrade](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#After_the_Proxmox_VE_upgrade) * [4.4.1 For Clusters](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#For_Clusters) * [4.4.2 Optional: Modernize apt Repository Sources](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Optional:_Modernize_apt_Repository_Sources) * [4.5 Checklist issues](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Checklist_issues) * [4.5.1 proxmox-ve package is too old](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#proxmox-ve_package_is_too_old) * [4.5.2 LVM/LVM-thin storage has guest volumes with autoactivation enabled](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#LVM/LVM-thin_storage_has_guest_volumes_with_autoactivation_enabled) * [4.6 Known Upgrade Issues](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Known_Upgrade_Issues) * [4.6.1 General](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#General) * [4.6.1.1 Upgrade wants to remove package 'proxmox-ve'](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Upgrade_wants_to_remove_package_'proxmox-ve') * [4.6.1.2 Kernel Audit Messages are Enabled During the Upgrade](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Kernel_Audit_Messages_are_Enabled_During_the_Upgrade) * [4.6.2 Third-party Storage Plugins](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Third-party_Storage_Plugins) * [4.6.3 Older Hardware and New 6.14 Kernel and Other Software](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Older_Hardware_and_New_6.14_Kernel_and_Other_Software) * [4.6.4 GRUB Might Fail To Boot From LVM in UEFI Mode](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#GRUB_Might_Fail_To_Boot_From_LVM_in_UEFI_Mode) * [4.6.5 Systemd-boot meta-package changes the bootloader configuration automatically and should be uninstalled](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Systemd-boot_meta-package_changes_the_bootloader_configuration_automatically_and_should_be_uninstalled) * [4.6.6 LVM Thin Pool needs repair](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#LVM_Thin_Pool_needs_repair) * [4.6.7 VM Live-Migration](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#VM_Live-Migration) * [4.6.7.1 VM Live-Migration with different host CPUs](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#VM_Live-Migration_with_different_host_CPUs) * [4.6.8 Network](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Network) * [4.6.8.1 Network Interface Name Change](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Network_Interface_Name_Change) * [4.6.8.2 Existing Ceph Full Mesh Setups fail to boot](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Existing_Ceph_Full_Mesh_Setups_fail_to_boot) * [4.6.8.3 Custom OpenFabric or OSPF Fabric FRR configurations broken](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Custom_OpenFabric_or_OSPF_Fabric_FRR_configurations_broken) * [4.6.9 cgroup V1 Removal](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#cgroup_V1_Removal) * [4.6.10 NVIDIA vGPU Compatibility](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#NVIDIA_vGPU_Compatibility) * [4.6.11 VM Memory Consumption Shown is Higher](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#VM_Memory_Consumption_Shown_is_Higher) * [4.6.12 Veeam Backup broken for VMs using QEMU machine version >= 10.0](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Veeam_Backup_broken_for_VMs_using_QEMU_machine_version_%3E=_10.0) * [4.6.13 Host PCI passthrough with kernel 6.14 for virtual machines sometimes broken](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Host_PCI_passthrough_with_kernel_6.14_for_virtual_machines_sometimes_broken) * [4.6.14 systemd-sysctl no longer reads /etc/sysctl.conf](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#systemd-sysctl_no_longer_reads_/etc/sysctl.conf) * [4.7 Troubleshooting](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Troubleshooting) * [4.7.1 Failing upgrade to "trixie"](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Failing_upgrade_to_%22trixie%22) * [4.7.2 Unable to boot due to grub failure](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Unable_to_boot_due_to_grub_failure) * [4.8 External links](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#External_links) Introduction ============ Proxmox VE 9.x introduces several new major features. You should plan the upgrade carefully, make and verify backups before beginning, and test extensively. Depending on the existing configuration, several manual steps—including some downtime—may be required. **Note:** A valid and tested backup is _always_ required before starting the upgrade process. Test the backup beforehand in a test lab setup. In case the system is customized and/or uses additional packages or any other third party repositories/packages, ensure those packages are also upgraded to and compatible with Debian Trixie. In general, there are two ways to upgrade a Proxmox VE 8.x system to Proxmox VE 9.x: * A new installation on new hardware (restoring VMs from the backup) * An in-place upgrade via apt (step-by-step) New installation ================ * Backup all VMs and containers to an external storage (see [Backup and Restore](https://pve.proxmox.com/wiki/Backup_and_Restore "Backup and Restore") ). * Backup all files in /etc **required:** files in /etc/pve, as well as `/etc/passwd`, `/etc/network/interfaces`, `/etc/resolv.conf`, and anything that deviates from a default installation. * Install latest Proxmox VE 9.x from the ISO (this will delete all data on the existing host). * Empty the browser cache and/or force-reload (CTRL + SHIFT + R, or for MacOS ⌘ + Alt + R) the Web UI. * Rebuild your cluster, if applicable. * Restore the file `/etc/pve/storage.cfg` (this will make the external storage used for backup available). * Restore firewall configs `/etc/pve/firewall/` and `/etc/pve/nodes//host.fw` (if applicable). * Restore all VMs from backups (see [Backup and Restore](https://pve.proxmox.com/wiki/Backup_and_Restore "Backup and Restore") ). Administrators comfortable with the command line can follow the procedure [Bypassing backup and restore when upgrading](https://pve.proxmox.com/wiki/Bypassing_backup_and_restore_when_upgrading "Bypassing backup and restore when upgrading") , if all VMs/CTs are on a single shared storage. Breaking Changes ================ See the release notes for breaking (API) changes: [https://pve.proxmox.com/wiki/Roadmap#9.0-known-issues](https://pve.proxmox.com/wiki/Roadmap#9.0-known-issues) In-place upgrade ================ In-place upgrades are carried out via apt. Familiarity with apt is required to proceed with this upgrade method. Prerequisites ------------- * Upgraded to the latest version of Proxmox VE 8.4 on all nodes. Ensure your node(s) have correct package repository configuration (web UI, Node -> Repositories) if your pve-manager version isn't at least `8.4.1`. * Hyper-converged Ceph: upgrade any Ceph Quincy or Ceph Reef cluster to Ceph 19.2 Squid **before** you start the Proxmox VE upgrade to 9.0. Follow the guide [Ceph Quincy to Reef](https://pve.proxmox.com/wiki/Ceph_Quincy_to_Reef "Ceph Quincy to Reef") and [Ceph Reef to Squid](https://pve.proxmox.com/wiki/Ceph_Reef_to_Squid "Ceph Reef to Squid") , respectively. * Co-installed Proxmox Backup Server: see [the Proxmox Backup Server 3 to 4 upgrade how-to](https://pbs.proxmox.com/wiki/index.php/Upgrade_from_3_to_4) * Reliable access to the node. It's recommended to have access over a host independent channel like IKVM/IPMI or physical access. If only SSH is available we recommend testing the upgrade on an identical, but non-production machine first. It is also highly recommended to use a terminal multiplexer (for example, tmux or screen) to ensure the upgrade can continue even if the SSH connection gets interrupted. * A healthy cluster * Valid and tested backup of all VMs and CTs (in case something goes wrong) * At least 5 GB free disk space on the root mount point, ideally more than 10 GB. * Check [known upgrade issues](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Known_Upgrade_Issues) Testing the Upgrade ------------------- An upgrade test can be easily performed using a standalone server. Install the Proxmox VE 8.4 ISO on some test hardware, then upgrade this installation to the latest minor version of Proxmox VE 8.4 (see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") ). To replicate the production setup as closely as possible, copy or create all relevant configurations to the test machine, then start the upgrade. It is also possible to install Proxmox VE 8.4 in a VM and test the upgrade in this environment. Actions step-by-step -------------------- The following actions need to be carried out from the command line of each Proxmox VE node in your cluster **Perform the actions via console or ssh; preferably via console to avoid interrupted ssh connections. Do not carry out the upgrade when connected via the virtual console offered by the GUI; as this will get interrupted during the upgrade. If only SSH is available consider using a terminal multiplexer (such as tmux or screen) to avoid issues if the SSH connection gets interrupted.** Remember to ensure that a valid backup of all VMs and CTs has been created before proceeding. ### Continuously use the **pve8to9** checklist script A small checklist program named **`pve8to9`** is included in the latest Proxmox VE 8.4 packages. The program will provide hints and warnings about potential issues before, during and after the upgrade process. You can call it by executing: pve8to9 To run it with **all** checks enabled, execute: pve8to9 --full Make sure to run the full checks at least once before the upgrade. This script only **checks** and reports things. By default, no changes to the system are made and thus, none of the issues will be automatically fixed. You should keep in mind that Proxmox VE can be heavily customized, so the script may not recognize all the possible problems with a particular setup! It is recommended to re-run the script after each attempt to fix an issue. This ensures that the actions taken actually fixed the respective warning. ### Move important Virtual Machines and Containers If any VMs and CTs need to keep running for the duration of the upgrade, migrate them away from the node that is being upgraded. Migration compatibility rules to keep in mind when planning your cluster upgrade: * A migration of a VM or CT from an older version of Proxmox VE to a newer version will always work. * A migration from a newer Proxmox VE version to an older version may work, but is generally not supported. **Note**: In a partially-upgraded cluster, minor inconsistencies may occur if you are logged into the GUI on a node that is already upgraded to Proxmox VE 9, and perform actions (such as guest migrations) on a node that is still running Proxmox VE 8. If you see any errors or warnings while migrating guests away from a node that is still running Proxmox VE 8, log into the GUI on that node and retry the migration. ### Update the configured APT repositories First, make sure that the system is using the latest Proxmox VE 8.4 packages: apt update apt dist-upgrade pveversion The last command should report at least `8.4.1` or newer. **Note:** For hyperconverged Ceph setups, ensure that you are running Ceph Squid (version 19). Check the output of `ceph --version` to be sure. If you are not running Ceph Squid, see the [upgrade guide for Ceph Reef to Squid](https://pve.proxmox.com/wiki/Ceph_Reef_to_Squid) and complete the upgrade first. Do not proceed with any of the steps below before upgrading to Ceph Squid. #### Update Debian Base Repositories to Trixie Update all Debian and Proxmox VE repository entries to Trixie. sed -i 's/bookworm/trixie/g' /etc/apt/sources.list sed -i 's/bookworm/trixie/g' /etc/apt/sources.list.d/pve-enterprise.list Ensure that there are no remaining Debian Bookworm specific repositories left, otherwise you can put a `#` symbol at the start of the respective line to comment these repositories out. Check all entries in the `/etc/apt/sources.list` and `/etc/apt/sources.list.d/pve-enterprise.list`, for the correct Proxmox VE 9 / Debian Trixie repositories see [Package Repositories](https://pve.proxmox.com/wiki/Package_Repositories "Package Repositories") . #### Add the Proxmox VE 9 Package Repository If you are using the enterprise repository, you can add the Proxmox VE 9 enterprise repository in the new deb822 style. Run the following command to create the related `pve-enterprise.sources` file: cat > /etc/apt/sources.list.d/pve-enterprise.sources << EOF Types: deb URIs: [https://enterprise.proxmox.com/debian/pve](https://enterprise.proxmox.com/debian/pve) Suites: trixie Components: pve-enterprise Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg EOF After you added the new enterprise repository as above, check that `apt` picks it up correctly. You can do so by first running `apt update` followed by `apt policy`. Make sure that no errors are shown and that `apt policy` only outputs the desired repositories. Then you can remove the old `/etc/apt/sources.list.d/pve-enterprise.list` file. Run `apt update` and `apt policy` again to be certain that the old repo has been removed. If using the no-subscription repository, see [Package Repositories](https://pve.proxmox.com/wiki/Package_Repositories "Package Repositories") . You should be able to add the Proxmox VE 9 no-subscription repository with this command: cat > /etc/apt/sources.list.d/proxmox.sources << EOF Types: deb URIs: [http://download.proxmox.com/debian/pve](http://download.proxmox.com/debian/pve) Suites: trixie Components: pve-no-subscription Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg EOF As with the enterprise repository, make sure that `apt` picks it up correctly with `apt update` followed by `apt policy`. Then remove the previous Proxmox VE 8 no-subscription repository from either the `/etc/apt/sources.list`, `/etc/apt/sources.list.d/pve-install-repo.list` or any other `.list` file you may have added it to. Run `apt update` and `apt policy` again to be certain that the old repo has been removed. #### Update the Ceph Package Repository **Note**: For hyper-converged ceph setups only, check the ceph panel and configured repositories in the Web UI of this node, if unsure. Replace any ceph.com repositories with proxmox.com ceph repositories. **Note**: At this point a hyper-converged Ceph cluster installed directly in Proxmox VE **must run Ceph 19.2 Squid**, otherwise you need to upgrade Ceph first before upgrading to Proxmox VE 9 on Debian 13 Trixie! You can check the current Ceph version in the Ceph panel of each node in the Web UI of Proxmox VE. Since Proxmox VE 8 there also exists an enterprise repository for ceph, providing the best choice for production setups. Execute the command below to add the Trixie-based Ceph enterprise repository in the new deb822 style: cat > /etc/apt/sources.list.d/ceph.sources << EOF Types: deb URIs: [https://enterprise.proxmox.com/debian/ceph-squid](https://enterprise.proxmox.com/debian/ceph-squid) Suites: trixie Components: enterprise Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg EOF Make sure that `apt` picks it up correctly by running `apt update` first and then `apt policy`. There should be no errors and the new repository should show up correctly in the output of `apt policy`. Then you can remove the old `/etc/apt/sources.list.d/ceph.list` file. You can run `apt update` and then `apt policy` again to make sure it has been properly removed. If updating fails with a 401 error, you might need to refresh the subscription first to ensure new access to ceph is granted, do this via the Web UI or `pvesubscription update --force`. If you do not have any subscription you can use the `no-subscription` repository, add it with the following command in the new deb822 style: cat > /etc/apt/sources.list.d/ceph.sources << EOF Types: deb URIs: [http://download.proxmox.com/debian/ceph-squid](http://download.proxmox.com/debian/ceph-squid) Suites: trixie Components: no-subscription Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg EOF As with the enterprise repository, make sure that `apt` picks it up correctly with `apt update` followed by `apt policy`. Then you can remove the old `/etc/apt/sources.list.d/ceph.list` file. If there is a backports line, remove it - the upgrade has not been tested with packages from the backports repository installed. #### Refresh Package Index Update the repositories' package index and verify that no error is reported: apt update ### Upgrade the system to Debian Trixie and Proxmox VE 9.0 Note that the time required for finishing this step heavily depends on the system's performance, especially the root filesystem's IOPS and bandwidth. A slow spinner can take up to 60 minutes or more, while for a high-performance server with SSD storage, the dist-upgrade can be finished in under 5 minutes. Start with this step, to get the initial set of upgraded packages: apt dist-upgrade During the above step, you will be asked to approve changes to configuration files and some service restarts, where the default config has been updated by their respective package. You may also be shown the output of apt-listchanges, you can simply exit there by pressing "q". If you get prompted for your default keyboard selection, simply use the arrow keys to navigate to the one applicable in your case and hit enter. For questions about service restarts (like Restart services during package upgrades without asking?) use the default if unsure, as the reboot after the upgrade will restart all services cleanly anyway. It's suggested to check the difference for each file in question and choose the answer accordingly to what's most appropriate for your setup. Common configuration files with changes, and the recommended choices are: * `/etc/issue` -> Proxmox VE will auto-generate this file on boot, and it has only cosmetic effects on the login console. Using the default "No" (keep your currently-installed version) is safe here. * `/etc/lvm/lvm.conf` -> Changes relevant for Proxmox VE will be updated, and a newer config version might be useful. If you did not make extra changes yourself and are unsure it's suggested to choose "Yes" (install the package maintainer's version) here. * `/etc/ssh/sshd_config` -> If you have not changed this file manually, the only differences should be a replacement of `ChallengeResponseAuthentication no` with `KbdInteractiveAuthentication no` and some irrelevant changes in comments (lines starting with `#`). If this is the case, both options are safe, though we would recommend installing the package maintainer's version in order to move away from the deprecated `ChallengeResponseAuthentication` option. If there are other changes, we suggest to inspect them closely and decide accordingly. * `/etc/default/grub` -> Here you may want to take special care, as this is normally only asked for if you changed it manually, e.g., for adding some kernel command line option. It's recommended to check the difference for any relevant change, note that changes in comments (lines starting with `#`) are not relevant. If unsure, we suggested to selected "No" (keep your currently-installed version) * `/etc/chrony/chrony.conf` -> If you made local changes you might want to move them out of the global config into the `conf.d` or, for custom time sources, the `sources.d` folder. See the `/etc/chrony/conf.d/README` and `/etc/chrony/sources.d/README` files on your system for detaily. If you did not make extra changes yourself and are unsure it's suggested to choose "Yes" (install the package maintainer's version) here. ### Check Result & Reboot Into Updated Kernel If the dist-upgrade command exits successfully, you can re-check the `pve8to9` checker script and reboot the system in order to use the new Proxmox VE kernel. Please note that you should reboot even if you already used the 6.14 kernel previously, through the opt-in package on Proxmox VE 8. This is required to guarantee the best compatibility with the rest of the system, as the updated kernel was (re-)build with the newer Proxmox VE 9 compiler and ABI versions. After the Proxmox VE upgrade ---------------------------- Empty the browser cache and/or force-reload (CTRL + SHIFT + R, or for macOS ⌘ + Alt + R) the Web UI. ### For Clusters * Check that all nodes are up and running on the latest package versions. If not, continue the upgrade on the next node, start over at [#Prerequisites](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Prerequisites) * Proxmox VE 9 deprecates HA groups in favor of HA rules. If you are using HA and HA groups, HA groups will be automatically migrated to HA rules once all cluster nodes have been upgraded to Proxmox VE 9. If you encounter any issues with HA groups or rules after having upgraded all cluster nodes, check the logs of `pve-ha-crm` on the active CRM node for errors with `journalctl -eu pve-ha-crm`. ### Optional: Modernize apt Repository Sources You can migrate existing repository sources to the recommended deb822 style format, by running: apt modernize-sources By answering the following prompt with "n" you can check the changes the command would make before applying them. To apply them simply run the command again and respond to the prompt with "Y". The command will also keep the old `.list` files around by appending `.bak` to them. So you will have the new `.sources` files and the old repository configurations in the `.list.bak` files. You can remove the leftover backup files once you verified that everything works smoothly with the new format. Checklist issues ---------------- ### proxmox-ve package is too old Check the configured package repository entries; they still need to be for Proxmox VE 8.x and Bookworm at this step (see [Package\_Repositories](https://pve.proxmox.com/wiki/Package_Repositories "Package Repositories") ). Then run apt update followed by apt dist-upgrade to get the latest Proxmox VE 8.x packages **before** upgrading to PVE 9. ### LVM/LVM-thin storage has guest volumes with autoactivation enabled On LVM or LVM-thin storages, a guest volume corresponds to an LVM Logical volume (LV). By default, LVM automatically activates an LV when it becomes visible, for example after boot or, if the LVM storage resides on an iSCSI LUN, after iSCSI login. Starting with PVE 9, new LVs will be created with autoactivation disabled. Such LVs are not automatically activated anymore, and are instead activated by Proxmox VE when needed. In clusters with shared LVM storages (for example on a shared iSCSI/FC LUN), this prevents problems that could cause guest/disk creation or guest migration to fail. See [bug #4997](https://bugzilla.proxmox.com/show_bug.cgi?id=4997) for more information. For existing LVs, we provide a migration script that disables autoactivation for all guest volumes on active and enabled LVM and LVM-thin storages. The migration script is located at `/usr/share/pve-manager/migrations/pve-lvm-disable-autoactivation`, and the `pve8to9` checklist script suggests to run this migration script if necessary. If there are guest volumes on shared LVM storages, running the migration script is strongly recommended, to prevent the issues outlined above. If guest volumes are only on local LVM or LVM-thin storages, running the migration script is optional. Known Upgrade Issues -------------------- ### General As a Debian based distribution, Proxmox VE is affected by most issues and changes affecting Debian. Thus, ensure that you read the [upgrade specific issues for Debian Trixie](https://www.debian.org/releases/trixie/release-notes/issues.en.html) . In particular, note that [`/tmp` is now a `tmpfs` file system](https://www.debian.org/releases/trixie/release-notes/issues.en.html#the-temporary-files-directory-tmp-is-now-stored-in-a-tmpfs) , using up to 50% of memory, and [files in `/tmp` and `/var/tmp` are now regularly cleaned](https://www.debian.org/releases/trixie/release-notes/issues.en.html#the-directories-tmp-and-var-tmp-are-now-regularly-cleaned) while the system is running. Please also check the known issue list from the Proxmox VE 9.0 changelog: [https://pve.proxmox.com/wiki/Roadmap#9.0-known-issues](https://pve.proxmox.com/wiki/Roadmap#9.0-known-issues) #### Upgrade wants to remove package 'proxmox-ve' If you have installed Proxmox VE on top of a plain Debian Trixie (without using the Proxmox VE ISO), you may have installed the package 'linux-image-amd64', which conflicts with current 9.x setups. To solve this, you have to remove this package with apt remove linux-image-amd64 before the dist-upgrade. #### Kernel Audit Messages are Enabled During the Upgrade Due to changes made to certain `systemd` defaults between Debian Bookworm and Debian Trixie, `journald` will begin to log kernel audit messages during the upgrade to Proxmox VE 9. In particular, audit logging was disabled by default in Debian Bookworm and earlier, while the corresponding socket `systemd-journald-audit.socket` remained enabled. In Debian Trixie, this was reversed: Audit logging is enabled by default again (thus matching upstream), while `systemd-journald-audit.socket` is now disabled by default. However, the socket remains enabled during the upgrade, which is why the audit log messages will start to appear. To prevent excessive audit messages being logged during the upgrade, you can disable and stop `systemd-journald-audit.socket` before upgrading: systemctl disable --now systemd-journald-audit.socket Otherwise, the audit messages will stop being logged once you reboot the node after the upgrade is complete. * * * ### Third-party Storage Plugins If you use any external storage plugin you need to wait until the plugin author adapted it for Proxmox VE 9.0. * * * ### Older Hardware and New 6.14 Kernel and Other Software Compatibility of old hardware (released >= 10 years ago) is not as thoroughly tested as more recent hardware. For old hardware we highly recommend testing compatibility of Proxmox VE 9 with identical (or at least similar) hardware before upgrading any production machines. Ceph has been reported to run into "illegal instruction" errors with at least AMD Opteron 2427 (released in 2009) and AMD Turion II Neo N54L (released in 2010) CPUs. We will expand this section with potential pitfalls and workarounds once they arise. * * * ### GRUB Might Fail To Boot From LVM in UEFI Mode Due to a [bug in grub](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987008) in PVE 8 and before, grub may fail to boot from LVM with an error message ``disk `lvmid/...` not found``. When booting in UEFI mode, you need to ensure that the new grub version containing the fix is indeed used for booting the system. Systems with Root on ZFS and systems booting in legacy mode are not affected. On systems booting in EFI mode with root on LVM, install the correct grub meta-package with: \[ -d /sys/firmware/efi \] && apt install grub-efi-amd64 For more details see [the relevant wiki page](https://pve.proxmox.com/wiki/Recover_From_Grub_Failure#Recovering_from_grub_.22disk_not_found.22_error_when_booting_from_LVM "Recover From Grub Failure") . ### Systemd-boot meta-package changes the bootloader configuration automatically and should be uninstalled With Debian Trixie the `systemd-boot` package got split up a bit further into `systemd-boot-efi` (containing the EFI-binary used for booting), `systemd-boot-tools` (containing `bootctl`) and the `systemd-boot` meta-package (containing hooks which run upon upgrades of itself and other packages and install systemd-boot as bootloader). As Proxmox Systems usually use `systemd-boot` for booting only in some configurations (ZFS on root and UEFI booted without secure boot), which are managed by `proxmox-boot-tool`, the meta-package `systemd-boot` should be removed. The package was automatically shipped for systems installed from the PVE 8.1 to PVE 8.4 ISOs, as it contained `bootctl` in bookworm. If the `pve8to9` checklist script suggests it, the `systemd-boot` meta-package is safe to remove unless you manually installed it and are using `systemd-boot` as a bootloader. Should `systemd-boot-efi` and `systemd-boot-tools` be required, `pve8to9` will warn you accordingly. The `pve8to9` checklist script will change its output depending on the state of the upgrade, and should be [run continuously before and after the upgrade](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Continuously_use_the_pve8to9_checklist_script) . It will print which packages should be removed or added at the appropriate time. The only situation where you should keep the meta-package `systemd-boot` installed is if you manually setup `systemd-boot` for your system. See also [the filed bug for systemd-boot](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1110177) . * * * ### LVM Thin Pool needs repair On some systems, LVM Thin Pools might need to be manually repaired after the upgrade and you will see an error message like: Check of pool pve/data failed (status:64). Manual repair required! Use the command `lvconvert --repair pve/data` to repair the pool. The cause is still being investigated. * * * ### VM Live-Migration #### VM Live-Migration with different host CPUs Live migration between nodes with different CPU models and especially different vendors can cause problems, such as VMs becoming unresponsive and causing high CPU utilization. We recommend testing live migration with a non-production VM first when upgrading. For this reason, we highly encourage using homogenous setups in clusters that use live migration. ### Network #### Network Interface Name Change Due to the new kernel recognizing more features of some hardware, like for example virtual functions, and interface naming often derives from the PCI(e) address, some NICs may change their name, in which case the network configuration needs to be adapted. In general, it's recommended to either have an independent remote connection to the Proxmox VE's host console, for example, through IPMI or IKVM, or physical access for managing the server even when its own network doesn't come up after a major upgrade or network change. With Proxmox VE 9 there is a `pve-network-interface-pinning` tool that can help you pin all network interfaces to `nicX` based names. #### Existing Ceph Full Mesh Setups fail to boot In earlier versions of the [Full Mesh Network for Ceph Server](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server "Full Mesh Network for Ceph Server") guide, the configuration contains a post-up line to restart frr: post-up /usr/bin/systemctl restart frr.service This will break with the upgrade to Proxmox VE 9, since FRR now depends on the networking.service - leading to a deadlock when restarting the node. Change the post-up to the following before a host reboot: post-up /usr/bin/systemctl is-active --quiet frr.service && /usr/bin/systemctl restart frr.service || true This way it will only restart the `frr` service if it is already running. ℹ️ **Note**: If it is too late, and the host is stuck on boot, you can boot into the **Rescue Boot** of the Proxmox VE installation ISO. It is in the **Advanced** menu of the bootloader. Once booted you can edit the `/etc/network/interfaces`. #### Custom OpenFabric or OSPF Fabric FRR configurations broken When upgrading to Proxmox VE 9, custom OpenFabric or OSPF Fabric configurations defined in `/etc/frr/frr.conf.local` will no longer work after the first request to apply the SDN config. This occurs because applying the SDN configuration automatically disables the daemons in `/etc/frr/daemons`, as these daemons are now managed by the Proxmox VE SDN stack. To restore functionality for your custom configuration, create the file `/etc/default/frr` and add `ospfd=yes` for OSPF or `fabricd=yes` for OpenFabric. This file overrides the settings in `/etc/frr/daemons`, allowing your configuration to work independently of the Proxmox VE SDN Fabric. If you decide to use the new SDN Fabrics, remember to remove the `/etc/default/frr` file so that the daemons get disabled correctly after an SDN Fabric is deleted. * * * ### cgroup V1 Removal Please note that since Proxmox VE 7.0, the default environment is pure cgroupv2. While it was still possible to manually enable the legacy cgroupv1 environment with Proxmox VE 8, this is no longer possible with Proxmox VE 9, which does not support the legacy cgroupv1 environment. This means Containers running systemd version 230 (released in 2016!) or older will not be supported by Proxmox VE 9. If you still run such container (e.g., CentOS 7 or Ubuntu 16.04), please use the remaining Proxmox VE 8 support cycle (estimated EOL is July 2026) as time window to migrate to newer, still supported versions of the respective Container OS. * * * ### NVIDIA vGPU Compatibility If you are using NVIDIA's GRID/vGPU technology, its driver must be compatible with the kernel you are using. Make sure you use at least GRID version 18.3 (driver version `570.158.02` - current as of July 2025) on the host before upgrading, since older versions (e.g. 15.x) are not compatible with kernel versions >= 6.0 and Proxmox VE 9.0 ships with at least 6.14. Note that we cannot guarantee compatibility during the beta, for the definitive list of tested versions see: [https://pve.proxmox.com/wiki/NVIDIA\_vGPU\_on\_Proxmox\_VE](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE) * * * ### VM Memory Consumption Shown is Higher In some situations you might see that the `Memory usage` of a VM is higher after the upgrade. Maybe even a bit over 100%. If the VM does not report detailed memory usage, Proxmox VE will show the host's view of the memory usage. With Proxmox VE 9, the accounting of the memory usage on the host has been adapted and takes the memory overhead of the VM into account. Therefore, the percentage may spike to over 100% in some cases. If the new `Host memory usage` field is the same as the `Memory Usage` field in the VM's summary panel, then Proxmox VE was unable to gather the VM's internal memory usage information. This happens if one of the following conditions applies: * The `Ballooning Device` has been disabled in the advanced memory settings of the VM. This removes the communication channel to gather the guest's internal memory usage information. * The guest does not report back any detailed memory usage information. * For example, FreeBSD is known to not report memory usage details, which includes popular firewalls like _pfSense_ or _OPNsense_. * If the `BalloonService` on a Windows guest is not installed or not running. * * * ### Veeam Backup broken for VMs using QEMU machine version >= 10.0 In preparation for features like snapshots on thick LVM, it was necessary to change how Proxmox VE attaches disks to QEMU internally. This is in effect for virtual machines using a QEMU machine version `10.0` or higher. Veeam has not adapted to these changes yet. Either pin the machine version to `9.2+pve1` for the affected virtual machines or postpone the upgrade. * * * ### Host PCI passthrough with kernel 6.14 for virtual machines sometimes broken Some users reported that virtual machines using PCI passthrough are not able to start anymore when using kernel 6.14. A workaround is booting an older kernel. Pin the old kernel to make this persistent. ### systemd-sysctl no longer reads /etc/sysctl.conf In the systemd-sysctl version shipped with Proxmox VE 9, `/etc/sysctl.conf` is no [longer honored](https://www.debian.org/releases/trixie/release-notes/issues.en.html#etc-sysctl-conf-is-no-longer-honored) . Therefore, any values set there will not get applied anymore. Instead, they should be moved or re-created in `/etc/sysctl.d/-.conf`, where `NN` should be a two-digit number defining the ordering of the config file. For more information on how these files are used see the [sysctl.d(5) man page](https://manpages.debian.org/trixie/systemd/sysctl.d.5.en.html) . When using EVPN with exit nodes, the documentation previously instructed overriding the `rp_filter` setting via `/etc/sysctl.conf`. This setting will no longer be applied after rebooting. Oftentimes additional settings, such as enabling IP forwarding, are set via `/etc/sysctl.conf` as well. It is recommended to check the content of the file before upgrading and migrate any settings from there. Troubleshooting --------------- ### Failing upgrade to "trixie" Make sure that the repository configuration for Trixie is correct. If there was a network failure and the upgrade was only partially completed, try to repair the situation with apt -f install If you see the following message: W: (pve-apt-hook) You are attempting to remove the meta-package 'proxmox-ve'! then one or more of the currently existing packages cannot be upgraded since the proper Trixie repository is not configured. Check which of the previously used repositories (i.e. for Bookworm) do not exist for Trixie or have not been upgraded to Bookworm ones. If a corresponding Trixie repository exists, upgrade the configuration (see also the section on [updating the Ceph Package repository](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Update_the_Ceph_Package_Repository) ). If an upgrade is not possible, configure all repositories as they were before the upgrade attempt, then run: apt update again. Then remove **all** packages which are currently installed from that repository. Following this, start the [upgrade procedure](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Add_the_Proxmox_VE_9_Package_Repository) again. ### Unable to boot due to grub failure See [Recover From Grub Failure](https://pve.proxmox.com/wiki/Recover_From_Grub_Failure "Recover From Grub Failure") If your system was installed on ZFS using legacy BIOS boot before the Proxmox VE 6.4 ISO, incompatibilities between the ZFS implementation in grub and newer ZFS versions can lead to a broken boot. Check the article on switching to `proxmox-boot-tool` [ZFS: Switch Legacy-Boot to Proxmox Boot Tool](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool "ZFS: Switch Legacy-Boot to Proxmox Boot Tool") for more details. External links -------------- [Release Notes for Debian 13 (trixie), 64-bit PC](https://www.debian.org/releases/trixie/release-notes/) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Upgrade\_from\_8\_to\_9&oldid=12531](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&oldid=12531) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Installation](https://pve.proxmox.com/wiki/Category:Installation "Category:Installation") * [Upgrade](https://pve.proxmox.com/wiki/Category:Upgrade "Category:Upgrade") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Category:Archive - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Categories) Category:Archive ================ From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Category:Archive#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Category:Archive#searchInput) Pages in category "Archive" --------------------------- The following 27 pages are in this category, out of 27 total. ### F * [Fencing](https://pve.proxmox.com/wiki/Fencing "Fencing") ### G * [Generating SSL Certificate in DAB Appliances](https://pve.proxmox.com/wiki/Generating_SSL_Certificate_in_DAB_Appliances "Generating SSL Certificate in DAB Appliances") * [Get Appliance Info](https://pve.proxmox.com/wiki/Get_Appliance_Info "Get Appliance Info") ### H * [High Availability Cluster](https://pve.proxmox.com/wiki/High_Availability_Cluster "High Availability Cluster") * [High Availability Cluster 4.x](https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x "High Availability Cluster 4.x") * [HTTPS Certificate Configuration (Version 3.x and earlier)](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_3.x_and_earlier) "HTTPS Certificate Configuration (Version 3.x and earlier)") ### I * [Install PECL Extensions in OpenVZ Debian Appliances](https://pve.proxmox.com/wiki/Install_PECL_Extensions_in_OpenVZ_Debian_Appliances "Install PECL Extensions in OpenVZ Debian Appliances") * [Install Proxmox VE on Debian Jessie](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Jessie "Install Proxmox VE on Debian Jessie") * [Install Proxmox VE on Debian Squeeze](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze "Install Proxmox VE on Debian Squeeze") * [Install Proxmox VE on Debian Squeeze on 32-Bit Processor](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze_on_32-Bit_Processor "Install Proxmox VE on Debian Squeeze on 32-Bit Processor") * [Install Proxmox VE on Debian Wheezy](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy "Install Proxmox VE on Debian Wheezy") ### J * [Java Console (Ubuntu)](https://pve.proxmox.com/wiki/Java_Console_(Ubuntu) "Java Console (Ubuntu)") ### N * [Nagios check mk](https://pve.proxmox.com/wiki/Nagios_check_mk "Nagios check mk") ### O * [Open Source](https://pve.proxmox.com/wiki/Open_Source "Open Source") * [OpenVZ Console](https://pve.proxmox.com/wiki/OpenVZ_Console "OpenVZ Console") ### P * [Porting Templates / Migrating OpenVZ Containers across PVE 1.x and PVE 2.x](https://pve.proxmox.com/wiki/Porting_Templates_/_Migrating_OpenVZ_Containers_across_PVE_1.x_and_PVE_2.x "Porting Templates / Migrating OpenVZ Containers across PVE 1.x and PVE 2.x") * [Proxmox SSL Error Fixing](https://pve.proxmox.com/wiki/Proxmox_SSL_Error_Fixing "Proxmox SSL Error Fixing") * [Proxmox VE 2.0 Cluster](https://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster "Proxmox VE 2.0 Cluster") * [Proxmox VE 4.x Cluster](https://pve.proxmox.com/wiki/Proxmox_VE_4.x_Cluster "Proxmox VE 4.x Cluster") ### S * [SimpleInvoices Deployment Screenshots](https://pve.proxmox.com/wiki/SimpleInvoices_Deployment_Screenshots "SimpleInvoices Deployment Screenshots") * [Storage: Nexenta](https://pve.proxmox.com/wiki/Storage:_Nexenta "Storage: Nexenta") * [Stunnel in DAB appliances](https://pve.proxmox.com/wiki/Stunnel_in_DAB_appliances "Stunnel in DAB appliances") ### T * [Two-Node High Availability Cluster](https://pve.proxmox.com/wiki/Two-Node_High_Availability_Cluster "Two-Node High Availability Cluster") ### U * [Unattended installation of Proxmox](https://pve.proxmox.com/wiki/Unattended_installation_of_Proxmox "Unattended installation of Proxmox") * [Unlock Locked OpenVZ Container](https://pve.proxmox.com/wiki/Unlock_Locked_OpenVZ_Container "Unlock Locked OpenVZ Container") ### X * [X11 LXDE in OpenVZ](https://pve.proxmox.com/wiki/X11_LXDE_in_OpenVZ "X11 LXDE in OpenVZ") * [Xenmigrate](https://pve.proxmox.com/wiki/Xenmigrate "Xenmigrate") Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Category:Archive&oldid=11408](https://pve.proxmox.com/mediawiki/index.php?title=Category:Archive&oldid=11408) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Dead-end pages - Proxmox VE Dead-end pages ============== [Jump to navigation](https://pve.proxmox.com/wiki/Special:DeadendPages#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:DeadendPages#searchInput) The following pages do not link to other pages in Proxmox VE. Showing below up to **50** results in range #**1** to #**50**. View (previous 50 | [next 50](https://pve.proxmox.com/mediawiki/index.php?title=Special:DeadendPages&limit=50&offset=50 "Next 50 results") ) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:DeadendPages&limit=20&offset=0 "Show 20 results per page") | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:DeadendPages&limit=100&offset=0 "Show 100 results per page") | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:DeadendPages&limit=250&offset=0 "Show 250 results per page") | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:DeadendPages&limit=500&offset=0 "Show 500 results per page") ) 1. [Anatomy of LXC Container Config File](https://pve.proxmox.com/wiki/Anatomy_of_LXC_Container_Config_File "Anatomy of LXC Container Config File") 2. [Automated Installation](https://pve.proxmox.com/wiki/Automated_Installation "Automated Installation") 3. [BTRFS](https://pve.proxmox.com/wiki/BTRFS "BTRFS") 4. [Backup and Restore](https://pve.proxmox.com/wiki/Backup_and_Restore "Backup and Restore") 5. [Bibliography](https://pve.proxmox.com/wiki/Bibliography "Bibliography") 6. [Bypassing backup and restore when upgrading](https://pve.proxmox.com/wiki/Bypassing_backup_and_restore_when_upgrading "Bypassing backup and restore when upgrading") 7. [Calendar Events](https://pve.proxmox.com/wiki/Calendar_Events "Calendar Events") 8. [Ceph Jewel to Luminous](https://pve.proxmox.com/wiki/Ceph_Jewel_to_Luminous "Ceph Jewel to Luminous") 9. [Ceph Luminous to Nautilus](https://pve.proxmox.com/wiki/Ceph_Luminous_to_Nautilus "Ceph Luminous to Nautilus") 10. [Ceph RBD Mirroring](https://pve.proxmox.com/wiki/Ceph_RBD_Mirroring "Ceph RBD Mirroring") 11. [Ceph mClock Tuning](https://pve.proxmox.com/wiki/Ceph_mClock_Tuning "Ceph mClock Tuning") 12. [Certificate Management](https://pve.proxmox.com/wiki/Certificate_Management "Certificate Management") 13. [Cisco UCS](https://pve.proxmox.com/wiki/Cisco_UCS "Cisco UCS") 14. [Cluster Manager](https://pve.proxmox.com/wiki/Cluster_Manager "Cluster Manager") 15. [Convert Debian CT to Kali](https://pve.proxmox.com/wiki/Convert_Debian_CT_to_Kali "Convert Debian CT to Kali") 16. [DRBD](https://pve.proxmox.com/wiki/DRBD "DRBD") 17. [DRBD9](https://pve.proxmox.com/wiki/DRBD9 "DRBD9") 18. [Debugging Installation](https://pve.proxmox.com/wiki/Debugging_Installation "Debugging Installation") 19. [Deploy Hyper-Converged Ceph Cluster](https://pve.proxmox.com/wiki/Deploy_Hyper-Converged_Ceph_Cluster "Deploy Hyper-Converged Ceph Cluster") 20. [Disk Health Email Alerts](https://pve.proxmox.com/wiki/Disk_Health_Email_Alerts "Disk Health Email Alerts") 21. [Disk Health Monitoring](https://pve.proxmox.com/wiki/Disk_Health_Monitoring "Disk Health Monitoring") 22. [Enable Core Dump systemd](https://pve.proxmox.com/wiki/Enable_Core_Dump_systemd "Enable Core Dump systemd") 23. [External Metric Server](https://pve.proxmox.com/wiki/External_Metric_Server "External Metric Server") 24. [FAQ](https://pve.proxmox.com/wiki/FAQ "FAQ") 25. [Fail2ban](https://pve.proxmox.com/wiki/Fail2ban "Fail2ban") 26. [Firewall](https://pve.proxmox.com/wiki/Firewall "Firewall") 27. [Firmware Updates](https://pve.proxmox.com/wiki/Firmware_Updates "Firmware Updates") 28. [FreeBSD Guest Notes](https://pve.proxmox.com/wiki/FreeBSD_Guest_Notes "FreeBSD Guest Notes") 29. [Get support](https://pve.proxmox.com/wiki/Get_support "Get support") 30. [Getting Help](https://pve.proxmox.com/wiki/Getting_Help "Getting Help") 31. [Graphical User Interface](https://pve.proxmox.com/wiki/Graphical_User_Interface "Graphical User Interface") 32. [Guest Time drift](https://pve.proxmox.com/wiki/Guest_Time_drift "Guest Time drift") 33. [High Availability](https://pve.proxmox.com/wiki/High_Availability "High Availability") 34. [Host-bios-upgrade](https://pve.proxmox.com/wiki/Host-bios-upgrade "Host-bios-upgrade") 35. [Host Bootloader](https://pve.proxmox.com/wiki/Host_Bootloader "Host Bootloader") 36. [Host System Administration](https://pve.proxmox.com/wiki/Host_System_Administration "Host System Administration") 37. [Hotplug (qemu disk,nic,cpu,memory)](https://pve.proxmox.com/wiki/Hotplug_(qemu_disk,nic,cpu,memory) "Hotplug (qemu disk,nic,cpu,memory)") 38. [Hyper-converged Infrastructure](https://pve.proxmox.com/wiki/Hyper-converged_Infrastructure "Hyper-converged Infrastructure") 39. [IO Scheduler](https://pve.proxmox.com/wiki/IO_Scheduler "IO Scheduler") 40. [Import certificate in browser](https://pve.proxmox.com/wiki/Import_certificate_in_browser "Import certificate in browser") 41. [Improving the Proxmox VE Documentation](https://pve.proxmox.com/wiki/Improving_the_Proxmox_VE_Documentation "Improving the Proxmox VE Documentation") 42. [Infiniband](https://pve.proxmox.com/wiki/Infiniband "Infiniband") 43. [Install PECL Extensions in OpenVZ Debian Appliances](https://pve.proxmox.com/wiki/Install_PECL_Extensions_in_OpenVZ_Debian_Appliances "Install PECL Extensions in OpenVZ Debian Appliances") 44. [Install Proxmox VE on Debian 11 Bullseye](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye "Install Proxmox VE on Debian 11 Bullseye") 45. [Install Proxmox VE on Debian 12 Bookworm](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_12_Bookworm "Install Proxmox VE on Debian 12 Bookworm") 46. [Install Proxmox VE on Debian 13 Trixie](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie "Install Proxmox VE on Debian 13 Trixie") 47. [Installation](https://pve.proxmox.com/wiki/Installation "Installation") 48. [Introduction](https://pve.proxmox.com/wiki/Introduction "Introduction") 49. [Iscsi/nappit](https://pve.proxmox.com/wiki/Iscsi/nappit "Iscsi/nappit") 50. [Iscsi/tests](https://pve.proxmox.com/wiki/Iscsi/tests "Iscsi/tests") View (previous 50 | [next 50](https://pve.proxmox.com/mediawiki/index.php?title=Special:DeadendPages&limit=50&offset=50 "Next 50 results") ) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:DeadendPages&limit=20&offset=0 "Show 20 results per page") | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:DeadendPages&limit=100&offset=0 "Show 100 results per page") | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:DeadendPages&limit=250&offset=0 "Show 250 results per page") | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:DeadendPages&limit=500&offset=0 "Show 500 results per page") ) Retrieved from "[https://pve.proxmox.com/wiki/Special:DeadendPages](https://pve.proxmox.com/wiki/Special:DeadendPages) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Notifications Overview[](https://pve.proxmox.com/pve-docs-8/chapter-notifications.html#chapter_notifications "Permalink to this heading") ---------------------------------------------------------------------------------------------------------------------------- * Proxmox VE emits [Notification Events](https://pve.proxmox.com/pve-docs/chapter-notifications.html#notification_events) in case of storage replication failures, node fencing, finished/failed backups and other events. These events are handled by the notification system. A notification event has metadata, for example a timestamp, a severity level, a type, and other optional metadata fields. * [Notification Matchers](https://pve.proxmox.com/pve-docs/chapter-notifications.html#notification_matchers) route a notification event to one or more notification targets. A matcher can have match rules to selectively route based on the metadata of a notification event. * [Notification Targets](https://pve.proxmox.com/pve-docs/chapter-notifications.html#notification_targets) are a destination to which a notification event is routed to by a matcher. There are multiple types of target, mail-based (Sendmail and SMTP) and Gotify. Backup jobs have a configurable [Notification Mode](https://pve.proxmox.com/pve-docs/chapter-notifications.html#notification_mode) . It allows you to choose between the notification system and a legacy mode for sending notification emails. The legacy mode is equivalent to the way notifications were handled before Proxmox VE 8.1. The notification system can be configured in the GUI under Datacenter → Notifications. The configuration is stored in /etc/pve/notifications.cfg and /etc/pve/priv/notifications.cfg - the latter contains sensitive configuration options such as passwords or authentication tokens for notification targets and can only be read by root. Notification Targets[](https://pve.proxmox.com/pve-docs-8/chapter-notifications.html#notification_targets "Permalink to this heading") --------------------------------------------------------------------------------------------------------------------------------------- Proxmox VE offers multiple types of notification targets. ### Sendmail[](https://pve.proxmox.com/pve-docs-8/chapter-notifications.html#notification_targets_sendmail "Permalink to this heading") [![screenshot/gui-datacenter-notification-sendmail.png](https://pve.proxmox.com/pve-docs-8/images/screenshot/gui-datacenter-notification-sendmail.png)](https://pve.proxmox.com/pve-docs-8/images/screenshot/gui-datacenter-notification-sendmail.png) The sendmail binary is a program commonly found on Unix-like operating systems that handles the sending of email messages. It is a command-line utility that allows users and applications to send emails directly from the command line or from within scripts. The sendmail notification target uses the sendmail binary to send emails to a list of configured users or email addresses. If a user is selected as a recipient, the email address configured in user’s settings will be used. For the root@pam user, this is the email address entered during installation. A user’s email address can be configured in Datacenter → Permissions → Users. If a user has no associated email address, no email will be sent. | | | | --- | --- | | ![Note]() | In standard Proxmox VE installations, the sendmail binary is provided by Postfix. It may be necessary to configure Postfix so that it can deliver mails correctly - for example by setting an external mail relay (smart host). In case of failed delivery, check the system logs for messages logged by the Postfix daemon. | The configuration for Sendmail target plugins has the following options: * mailto: E-Mail address to which the notification shall be sent to. Can be set multiple times to accommodate multiple recipients. * mailto-user: Users to which emails shall be sent to. The user’s email address will be looked up in users.cfg. Can be set multiple times to accommodate multiple recipients. * author: Sets the author of the E-Mail. Defaults to Proxmox VE. * from-address: Sets the from address of the E-Mail. If the parameter is not set, the plugin will fall back to the email\_from setting from datacenter.cfg. If that is also not set, the plugin will default to root@$hostname, where $hostname is the hostname of the node. * comment: Comment for this target The From header in the email will be set to $author <$from-address>. Example configuration (/etc/pve/notifications.cfg): sendmail: example mailto-user root@pam mailto-user admin@pve mailto max@example.com from-address pve1@example.com comment Send to multiple users/addresses ### SMTP[](https://pve.proxmox.com/pve-docs-8/chapter-notifications.html#notification_targets_smtp "Permalink to this heading") [![screenshot/gui-datacenter-notification-smtp.png](https://pve.proxmox.com/pve-docs-8/images/screenshot/gui-datacenter-notification-smtp.png)](https://pve.proxmox.com/pve-docs-8/images/screenshot/gui-datacenter-notification-smtp.png) SMTP notification targets can send emails directly to an SMTP mail relay. This target does not use the system’s MTA to deliver emails. Similar to sendmail targets, if a user is selected as a recipient, the user’s configured email address will be used. | | | | --- | --- | | ![Note]() | Unlike sendmail targets, SMTP targets do not have any queuing/retry mechanism in case of a failed mail delivery. | The configuration for SMTP target plugins has the following options: * mailto: E-Mail address to which the notification shall be sent to. Can be set multiple times to accommodate multiple recipients. * mailto-user: Users to which emails shall be sent to. The user’s email address will be looked up in users.cfg. Can be set multiple times to accommodate multiple recipients. * author: Sets the author of the E-Mail. Defaults to Proxmox VE. * from-address: Sets the From-address of the email. SMTP relays might require that this address is owned by the user in order to avoid spoofing. The From header in the email will be set to $author <$from-address>. * username: Username to use during authentication. If no username is set, no authentication will be performed. The PLAIN and LOGIN authentication methods are supported. * password: Password to use when authenticating. * mode: Sets the encryption mode (insecure, starttls or tls). Defaults to tls. * server: Address/IP of the SMTP relay * port: The port to connect to. If not set, the used port defaults to 25 (insecure), 465 (tls) or 587 (starttls), depending on the value of mode. * comment: Comment for this target Example configuration (/etc/pve/notifications.cfg): smtp: example mailto-user root@pam mailto-user admin@pve mailto max@example.com from-address pve1@example.com username pve1 server mail.example.com mode starttls The matching entry in /etc/pve/priv/notifications.cfg, containing the secret token: smtp: example password somepassword ### Gotify[](https://pve.proxmox.com/pve-docs-8/chapter-notifications.html#notification_targets_gotify "Permalink to this heading") [![screenshot/gui-datacenter-notification-gotify.png](https://pve.proxmox.com/pve-docs-8/images/screenshot/gui-datacenter-notification-gotify.png)](https://pve.proxmox.com/pve-docs-8/images/screenshot/gui-datacenter-notification-gotify.png) [Gotify](http://gotify.net/) is an open-source self-hosted notification server that allows you to send and receive push notifications to various devices and applications. It provides a simple API and web interface, making it easy to integrate with different platforms and services. The configuration for Gotify target plugins has the following options: * server: The base URL of the Gotify server, e.g. http://:8888 * token: The authentication token. Tokens can be generated within the Gotify web interface. * comment: Comment for this target | | | | --- | --- | | ![Note]() | The Gotify target plugin will respect the HTTP proxy settings from the [datacenter configuration](https://pve.proxmox.com/pve-docs/pve-admin-guide.html#datacenter_configuration_file) | Example configuration (/etc/pve/notifications.cfg): gotify: example server http://gotify.example.com:8888 comment Send to multiple users/addresses The matching entry in /etc/pve/priv/notifications.cfg, containing the secret token: gotify: example token somesecrettoken ### Webhook[](https://pve.proxmox.com/pve-docs-8/chapter-notifications.html#notification_targets_webhook "Permalink to this heading") Webhook notification targets perform HTTP requests to a configurable URL. The following configuration options are available: * url: The URL to which to perform the HTTP requests. Supports templating to inject message contents, metadata and secrets. * method: HTTP Method to use (POST/PUT/GET) * header: Array of HTTP headers that should be set for the request. Supports templating to inject message contents, metadata and secrets. * body: HTTP body that should be sent. Supports templating to inject message contents, metadata and secrets. * secret: Array of secret key-value pairs. These will be stored in a protected configuration file only readable by root. Secrets can be accessed in body/header/URL templates via the secrets namespace. * comment: Comment for this target. For configuration options that support templating, the [Handlebars](https://handlebarsjs.com/) syntax can be used to access the following properties: * {{ title }}: The rendered notification title * {{ message }}: The rendered notification body * {{ severity }}: The severity of the notification (info, notice, warning, error, unknown) * {{ timestamp }}: The notification’s timestamp as a UNIX epoch (in seconds). * {{ fields. }}: Sub-namespace for any metadata fields of the notification. For instance, fields.type contains the notification type - for all available fields refer to [Notification Events](https://pve.proxmox.com/pve-docs/chapter-notifications.html#notification_events) . * {{ secrets. }}: Sub-namespace for secrets. For instance, a secret named token is accessible via secrets.token. For convenience, the following helpers are available: * {{ url-encode }}: URL-encode a property/literal. * {{ escape }}: Escape any control characters that cannot be safely represented as a JSON string. * {{ json }}: Render a value as JSON. This can be useful to pass a whole sub-namespace (e.g. fields) as a part of a JSON payload (e.g. {{ json fields }}). #### Examples[](https://pve.proxmox.com/pve-docs-8/chapter-notifications.html#_examples "Permalink to this heading") ##### ntfy.sh[](https://pve.proxmox.com/pve-docs-8/chapter-notifications.html#_span_class_monospaced_ntfy_sh_span "Permalink to this heading") * Method: POST * URL: https://ntfy.sh/{{ secrets.channel }} * Headers: * Markdown: Yes * Body: \`\`\` {{ message }} \`\`\` * Secrets: * channel: ##### Discord[](https://pve.proxmox.com/pve-docs-8/chapter-notifications.html#_discord "Permalink to this heading") * Method: POST * URL: https://discord.com/api/webhooks/{{ secrets.token }} * Headers: * Content-Type: application/json * Body: { "content": "\`\`\` {{ escape message }}\`\`\`" } * Secrets: * token: ##### Slack[](https://pve.proxmox.com/pve-docs-8/chapter-notifications.html#_slack "Permalink to this heading") * Method: POST * URL: https://hooks.slack.com/services/{{ secrets.token }} * Headers: * Content-Type: application/json * Body: { "text": "\`\`\` {{escape message}}\`\`\`", "type": "mrkdwn" } * Secrets: * token: Notification Matchers[](https://pve.proxmox.com/pve-docs-8/chapter-notifications.html#notification_matchers "Permalink to this heading") ----------------------------------------------------------------------------------------------------------------------------------------- [![screenshot/gui-datacenter-notification-matcher.png](https://pve.proxmox.com/pve-docs-8/images/screenshot/gui-datacenter-notification-matcher.png)](https://pve.proxmox.com/pve-docs-8/images/screenshot/gui-datacenter-notification-matcher.png) Notification matchers route notifications to notification targets based on their matching rules. These rules can match certain properties of a notification, such as the timestamp (match-calendar), the severity of the notification (match-severity) or metadata fields (match-field). If a notification is matched by a matcher, all targets configured for the matcher will receive the notification. An arbitrary number of matchers can be created, each with with their own matching rules and targets to notify. Every target is notified at most once for every notification, even if the target is used in multiple matchers. A matcher without any matching rules is always true; the configured targets will always be notified. matcher: always-matches target admin comment This matcher always matches ### Matcher Options[](https://pve.proxmox.com/pve-docs-8/chapter-notifications.html#_matcher_options "Permalink to this heading") * target: Determine which target should be notified if the matcher matches. can be used multiple times to notify multiple targets. * invert-match: Inverts the result of the whole matcher * mode: Determines how the individual match rules are evaluated to compute the result for the whole matcher. If set to all, all matching rules must match. If set to any, at least one rule must match. a matcher must be true. Defaults to all. * match-calendar: Match the notification’s timestamp against a schedule * match-field: Match the notification’s metadata fields * match-severity: Match the notification’s severity * comment: Comment for this matcher ### Calendar Matching Rules[](https://pve.proxmox.com/pve-docs-8/chapter-notifications.html#notification_matchers_calendar "Permalink to this heading") A calendar matcher matches the time when a notification is sent against a configurable schedule. * match-calendar 8-12 * match-calendar 8:00-15:30 * match-calendar mon-fri 9:00-17:00 * match-calendar sun,tue-wed,fri 9-17 ### Field Matching Rules[](https://pve.proxmox.com/pve-docs-8/chapter-notifications.html#notification_matchers_field "Permalink to this heading") Notifications have a selection of metadata fields that can be matched. When using exact as a matching mode, a , can be used as a separator. The matching rule then matches if the metadata field has **any** of the specified values. * match-field exact:type=vzdump Only match notifications about backups. * match-field exact:type=replication,fencing Match replication and fencing notifications. * match-field regex:hostname=^.+\\.example\\.com$ Match the hostname of the node. If a matched metadata field does not exist, the notification will not be matched. For instance, a match-field regex:hostname=.\* directive will only match notifications that have an arbitrary hostname metadata field, but will not match if the field does not exist. ### Severity Matching Rules[](https://pve.proxmox.com/pve-docs-8/chapter-notifications.html#notification_matchers_severity "Permalink to this heading") A notification has a associated severity that can be matched. * match-severity error: Only match errors * match-severity warning,error: Match warnings and error The following severities are in use: info, notice, warning, error, unknown. ### Examples[](https://pve.proxmox.com/pve-docs-8/chapter-notifications.html#_examples_2 "Permalink to this heading") matcher: workday match-calendar mon-fri 9-17 target admin comment Notify admins during working hours matcher: night-and-weekend match-calendar mon-fri 9-17 invert-match true target on-call-admins comment Separate target for non-working hours matcher: backup-failures match-field exact:type=vzdump match-severity error target backup-admins comment Send notifications about backup failures to one group of admins matcher: cluster-failures match-field exact:type=replication,fencing target cluster-admins comment Send cluster-related notifications to other group of admins Notification Events[](https://pve.proxmox.com/pve-docs-8/chapter-notifications.html#notification_events "Permalink to this heading") ------------------------------------------------------------------------------------------------------------------------------------- | Event | type | Severity | Metadata fields (in addition to type) | | --- | --- | --- | --- | | System updates available | package-updates | info | hostname | | Cluster node fenced | fencing | error | hostname | | Storage replication job failed | replication | error | hostname, job-id | | Backup succeeded | vzdump | info | hostname, job-id (only for backup jobs) | | Backup failed | vzdump | error | hostname, job-id (only for backup jobs) | | Mail for root | system-mail | unknown | hostname | | Field name | Description | | --- | --- | | type | Type of the notification | | hostname | Hostname, without domain (e.g. pve1) | | job-id | Job ID | | | | | --- | --- | | ![Note]() | Backup job notifications only have job-id set if the backup job was executed automatically based on its schedule, but not if it was triggered manually by the _Run now_ button in the UI. | System Mail Forwarding[](https://pve.proxmox.com/pve-docs-8/chapter-notifications.html#_system_mail_forwarding "Permalink to this heading") -------------------------------------------------------------------------------------------------------------------------------------------- Certain local system daemons, such as smartd, generate notification emails that are initially directed to the local root user. Proxmox VE will feed these mails into the notification system as a notification of type system-mail and with severity unknown. When the email is forwarded to a sendmail target, the mail’s content and headers are forwarded as-is. For all other targets, the system tries to extract both a subject line and the main text body from the email content. In instances where emails solely consist of HTML content, they will be transformed into plain text format during this process. Permissions[](https://pve.proxmox.com/pve-docs-8/chapter-notifications.html#_permissions "Permalink to this heading") ---------------------------------------------------------------------------------------------------------------------- To modify/view the configuration for notification targets, the Mapping.Modify/Mapping.Audit permissions are required for the /mapping/notifications ACL node. Testing a target requires Mapping.Use, Mapping.Audit or Mapping.Modify permissions on /mapping/notifications Notification Mode[](https://pve.proxmox.com/pve-docs-8/chapter-notifications.html#notification_mode "Permalink to this heading") --------------------------------------------------------------------------------------------------------------------------------- A backup job configuration has the notification-mode option which can have one of three values. * auto: Use the legacy-sendmail mode if no email address is entered in the mailto/Send email to field. If no email address is entered, the notification-system mode is used. * legacy-sendmail: Send notification emails via the system’s sendmail command. The notification system will be bypassed and any configured targets/matchers will be ignored. This mode is equivalent to the notification behavior for version before Proxmox VE 8.1 . * notification-system: Use the new, flexible notification system. If the notification-mode option is not set, Proxmox VE will default to auto. The legacy-sendmail mode might be removed in a later release of Proxmox VE. * * * --- # pvenode(1) ☰ NAME[](https://pve.proxmox.com/pve-docs/pvenode.1.html#_name "Permalink to this heading") ------------------------------------------------------------------------------------------ pvenode - Proxmox VE Node Management SYNOPSIS[](https://pve.proxmox.com/pve-docs/pvenode.1.html#_synopsis "Permalink to this heading") -------------------------------------------------------------------------------------------------- **pvenode** \[ARGS\] \[OPTIONS\][](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode "Permalink to this heading") **pvenode acme account deactivate** \[\][](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_acme_account_deactivate "Permalink to this heading") Deactivate existing ACME account at CA. : (_default =_ default) ACME account config file name. **pvenode acme account info** \[\] \[FORMAT\_OPTIONS\][](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_acme_account_info "Permalink to this heading") Return existing ACME account information. : (_default =_ default) ACME account config file name. **pvenode acme account list**[](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_acme_account_list "Permalink to this heading") ACMEAccount index. **pvenode acme account register** \[\] {} \[OPTIONS\][](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_acme_account_register "Permalink to this heading") Register a new ACME account with a compatible CA. : (_default =_ default) ACME account config file name. : Contact email addresses. \--directory ^https?://.\* URL of ACME CA directory endpoint. **pvenode acme account update** \[\] \[OPTIONS\][](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_acme_account_update "Permalink to this heading") Update existing ACME account information with CA. Note: not specifying any new account information triggers a refresh. : (_default =_ default) ACME account config file name. \--contact Contact email addresses. **pvenode acme cert order** \[OPTIONS\][](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_acme_cert_order "Permalink to this heading") Order a new certificate from ACME-compatible CA. \--force (_default =_ 0) Overwrite existing custom certificate. **pvenode acme cert renew** \[OPTIONS\][](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_acme_cert_renew "Permalink to this heading") Renew existing certificate from CA. \--force (_default =_ 0) Force renewal even if expiry is more than 30 days away. **pvenode acme cert revoke**[](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_acme_cert_revoke "Permalink to this heading") Revoke existing certificate from CA. **pvenode acme plugin add** \[OPTIONS\][](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_acme_plugin_add "Permalink to this heading") Add ACME plugin configuration. : ACME challenge type. : ACME Plugin ID name \--api <1984hosting | acmedns | acmeproxy | active24 | ad | ali | alviy | anx | artfiles | arvan | aurora | autodns | aws | azion | azure | beget | bookmyname | bunny | cf | clouddns | cloudns | cn | conoha | constellix | cpanel | curanet | cyon | da | ddnss | desec | df | dgon | dnsexit | dnshome | dnsimple | dnsservices | doapi | domeneshop | dp | dpi | dreamhost | duckdns | durabledns | dyn | dynu | dynv6 | easydns | edgecenter | edgedns | euserv | exoscale | fornex | freedns | freemyip | gandi\_livedns | gcloud | gcore | gd | geoscaling | googledomains | he | he\_ddns | hetzner | hexonet | hostingde | huaweicloud | infoblox | infomaniak | internetbs | inwx | ionos | ionos\_cloud | ipv64 | ispconfig | jd | joker | kappernet | kas | kinghost | knot | la | leaseweb | lexicon | limacity | linode | linode\_v4 | loopia | lua | maradns | me | miab | mijnhost | misaka | myapi | mydevil | mydnsjp | mythic\_beasts | namecheap | namecom | namesilo | nanelo | nederhost | neodigit | netcup | netlify | nic | njalla | nm | nsd | nsone | nsupdate | nw | oci | omglol | one | online | openprovider | openstack | opnsense | ovh | pdns | pleskxml | pointhq | porkbun | rackcorp | rackspace | rage4 | rcode0 | regru | scaleway | schlundtech | selectel | selfhost | servercow | simply | technitium | tele3 | tencent | timeweb | transip | udr | ultra | unoeuro | variomedia | veesp | vercel | vscale | vultr | websupport | west\_cn | world4you | yandex360 | yc | zilore | zone | zoneedit | zonomi> API plugin name \--data File with one key-value pair per line, will be base64url encode for storage in plugin config. DNS plugin data. (base64 encoded) \--disable Flag to disable the config. \--nodes List of cluster node names. \--validation-delay (0 - 172800) (_default =_ 30) Extra delay in seconds to wait before requesting validation. Allows to cope with a long TTL of DNS records. **pvenode acme plugin config** \[FORMAT\_OPTIONS\][](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_acme_plugin_config "Permalink to this heading") Get ACME plugin configuration. : Unique identifier for ACME plugin instance. **pvenode acme plugin list** \[OPTIONS\] \[FORMAT\_OPTIONS\][](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_acme_plugin_list "Permalink to this heading") ACME plugin index. \--type Only list ACME plugins of a specific type **pvenode acme plugin remove** [](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_acme_plugin_remove "Permalink to this heading") Delete ACME plugin configuration. : Unique identifier for ACME plugin instance. **pvenode acme plugin set** \[OPTIONS\][](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_acme_plugin_set "Permalink to this heading") Update ACME plugin configuration. : ACME Plugin ID name \--api <1984hosting | acmedns | acmeproxy | active24 | ad | ali | alviy | anx | artfiles | arvan | aurora | autodns | aws | azion | azure | beget | bookmyname | bunny | cf | clouddns | cloudns | cn | conoha | constellix | cpanel | curanet | cyon | da | ddnss | desec | df | dgon | dnsexit | dnshome | dnsimple | dnsservices | doapi | domeneshop | dp | dpi | dreamhost | duckdns | durabledns | dyn | dynu | dynv6 | easydns | edgecenter | edgedns | euserv | exoscale | fornex | freedns | freemyip | gandi\_livedns | gcloud | gcore | gd | geoscaling | googledomains | he | he\_ddns | hetzner | hexonet | hostingde | huaweicloud | infoblox | infomaniak | internetbs | inwx | ionos | ionos\_cloud | ipv64 | ispconfig | jd | joker | kappernet | kas | kinghost | knot | la | leaseweb | lexicon | limacity | linode | linode\_v4 | loopia | lua | maradns | me | miab | mijnhost | misaka | myapi | mydevil | mydnsjp | mythic\_beasts | namecheap | namecom | namesilo | nanelo | nederhost | neodigit | netcup | netlify | nic | njalla | nm | nsd | nsone | nsupdate | nw | oci | omglol | one | online | openprovider | openstack | opnsense | ovh | pdns | pleskxml | pointhq | porkbun | rackcorp | rackspace | rage4 | rcode0 | regru | scaleway | schlundtech | selectel | selfhost | servercow | simply | technitium | tele3 | tencent | timeweb | transip | udr | ultra | unoeuro | variomedia | veesp | vercel | vscale | vultr | websupport | west\_cn | world4you | yandex360 | yc | zilore | zone | zoneedit | zonomi> API plugin name \--data File with one key-value pair per line, will be base64url encode for storage in plugin config. DNS plugin data. (base64 encoded) \--delete A list of settings you want to delete. \--digest Prevent changes if current configuration file has a different digest. This can be used to prevent concurrent modifications. \--disable Flag to disable the config. \--nodes List of cluster node names. \--validation-delay (0 - 172800) (_default =_ 30) Extra delay in seconds to wait before requesting validation. Allows to cope with a long TTL of DNS records. **pvenode cert delete** \[\][](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_cert_delete "Permalink to this heading") DELETE custom certificate chain and key. : (_default =_ 0) Restart pveproxy. **pvenode cert info** \[FORMAT\_OPTIONS\][](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_cert_info "Permalink to this heading") Get information about node’s certificates. **pvenode cert set** \[\] \[OPTIONS\] \[FORMAT\_OPTIONS\][](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_cert_set "Permalink to this heading") Upload or update custom certificate chain and key. : PEM encoded certificate (chain). : PEM encoded private key. \--force (_default =_ 0) Overwrite existing custom or ACME certificate files. \--restart (_default =_ 0) Restart pveproxy. **pvenode config get** \[OPTIONS\][](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_config_get "Permalink to this heading") Get node configuration options. \--property (_default =_ all) Return only a specific property from the node configuration. **pvenode config set** \[OPTIONS\][](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_config_set "Permalink to this heading") Set node configuration options. \--acme \[account=\] \[,domains=\] Node specific ACME settings. \--acmedomain\[n\] \[domain=\] \[,alias=\] \[,plugin=\] ACME domain and validation plugin \--ballooning-target (0 - 100) (_default =_ 80) RAM usage target for ballooning (in percent of total memory) \--delete A list of settings you want to delete. \--description Description for the Node. Shown in the web-interface node notes panel. This is saved as comment inside the configuration file. \--digest Prevent changes if current configuration file has different SHA1 digest. This can be used to prevent concurrent modifications. \--startall-onboot-delay (0 - 300) (_default =_ 0) Initial delay in seconds, before starting all the Virtual Guests with on-boot enabled. \--wakeonlan \[mac=\] \[,bind-interface=\] \[,broadcast-address=\] Node specific wake on LAN settings. **pvenode help** \[OPTIONS\][](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_help "Permalink to this heading") Get help about specified command. \--extra-args Shows help for a specific command \--verbose Verbose output format. **pvenode migrateall** \[OPTIONS\][](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_migrateall "Permalink to this heading") Migrate all VMs and Containers. : Target node. \--maxworkers (1 - N) Maximal number of parallel migration job. If not set, uses’max\_workers' from datacenter.cfg. One of both must be set! \--vms Only consider Guests with these IDs. \--with-local-disks Enable live storage migration for local disk **pvenode startall** \[OPTIONS\][](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_startall "Permalink to this heading") Start all VMs and containers located on this node (by default only those with onboot=1). \--force (_default =_ off) Issue start command even if virtual guest have _onboot_ not set or set to off. \--vms Only consider guests from this comma separated list of VMIDs. **pvenode stopall** \[OPTIONS\][](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_stopall "Permalink to this heading") Stop all VMs and Containers. \--force-stop (_default =_ 1) Force a hard-stop after the timeout. \--timeout (0 - 7200) (_default =_ 180) Timeout for each guest shutdown task. Depending on force-stop, the shutdown gets then simply aborted or a hard-stop is forced. \--vms Only consider Guests with these IDs. **pvenode task list** \[OPTIONS\] \[FORMAT\_OPTIONS\][](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_task_list "Permalink to this heading") Read task list for one node (finished tasks). \--errors (_default =_ 0) Only list tasks with a status of ERROR. \--limit (0 - N) (_default =_ 50) Only list this number of tasks. \--since Only list tasks since this UNIX epoch. \--source (_default =_ archive) List archived, active or all tasks. \--start (0 - N) (_default =_ 0) List tasks beginning from this offset. \--statusfilter List of Task States that should be returned. \--typefilter Only list tasks of this type (e.g., vzstart, vzdump). \--until Only list tasks until this UNIX epoch. \--userfilter Only list tasks from this user. \--vmid (100 - 999999999) Only list tasks for this VM. **pvenode task log** \[OPTIONS\][](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_task_log "Permalink to this heading") Read task log. : The task’s unique ID. \--download Whether the tasklog file should be downloaded. This parameter can’t be used in conjunction with other parameters \--start (0 - N) (_default =_ 0) Start at this line when reading the tasklog **pvenode task status** \[FORMAT\_OPTIONS\][](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_task_status "Permalink to this heading") Read task status. : The task’s unique ID. **pvenode wakeonlan** [](https://pve.proxmox.com/pve-docs/pvenode.1.html#cli_pvenode_wakeonlan "Permalink to this heading") Try to wake a node via _wake on LAN_ network packet. : target node for wake on LAN packet DESCRIPTION[](https://pve.proxmox.com/pve-docs/pvenode.1.html#_description "Permalink to this heading") -------------------------------------------------------------------------------------------------------- The Proxmox VE node management tool (pvenode) allows you to control node specific settings and resources. Currently pvenode allows you to set a node’s description, run various bulk operations on the node’s guests, view the node’s task history, and manage the node’s SSL certificates, which are used for the API and the web GUI through pveproxy. FORMAT\_OPTIONS[](https://pve.proxmox.com/pve-docs/pvenode.1.html#_format_options "Permalink to this heading") --------------------------------------------------------------------------------------------------------------- It is possible to specify the output format using the \--output-format parameter. The default format _text_ uses ASCII-art to draw nice borders around tables. It additionally transforms some values into human-readable text, for example: * Unix epoch is displayed as ISO 8601 date string. * Durations are displayed as week/day/hour/minute/second count, i.e 1d 5h. * Byte sizes value include units (B, KiB, MiB, GiB, TiB, PiB). * Fractions are display as percentage, i.e. 1.0 is displayed as 100%. You can also completely suppress output using option \--quiet. \--human-readable (_default =_ 1) Call output rendering functions to produce human readable text. \--noborder (_default =_ 0) Do not draw borders (for _text_ format). \--noheader (_default =_ 0) Do not show column headers (for _text_ format). \--output-format (_default =_ text) Output format. \--quiet Suppress printing results. ### Examples[](https://pve.proxmox.com/pve-docs/pvenode.1.html#_examples "Permalink to this heading") Install an externally provided certificate pvenode cert set certificate.crt certificate.key -force Both files need to be PEM encoded. certificate.key contains the private key and certificate.crt contains the whole certificate chain. Setup ACME account and order a certificate for the local node. pvenode acme account register default mail@example.invalid pvenode config set --acme domains=example.invalid pvenode acme cert order systemctl restart pveproxy ### Wake-on-LAN[](https://pve.proxmox.com/pve-docs/pvenode.1.html#_wake_on_lan "Permalink to this heading") Wake-on-LAN (WoL) allows you to switch on a sleeping computer in the network, by sending a magic packet. At least one NIC must support this feature, and the respective option needs to be enabled in the computer’s firmware (BIOS/UEFI) configuration. The option name can vary from _Enable Wake-on-Lan_ to _Power On By PCIE Device_; check your motherboard’s vendor manual, if you’re unsure. ethtool can be used to check the WoL configuration of by running: ethtool | grep Wake-on pvenode allows you to wake sleeping members of a cluster via WoL, using the command: pvenode wakeonlan This broadcasts the WoL magic packet on UDP port 9, containing the MAC address of obtained from the wakeonlan property. The node-specific wakeonlan property can be set using the following command: pvenode config set -wakeonlan XX:XX:XX:XX:XX:XX The interface via which to send the WoL packet is determined from the default route. It can be overwritten by setting the bind-interface via the following command: pvenode config set -wakeonlan XX:XX:XX:XX:XX:XX,bind-interface= The broadcast address (default 255.255.255.255) used when sending the WoL packet can further be changed by setting the broadcast-address explicitly using the following command: pvenode config set -wakeonlan XX:XX:XX:XX:XX:XX,broadcast-address= ### Task History[](https://pve.proxmox.com/pve-docs/pvenode.1.html#_task_history "Permalink to this heading") When troubleshooting server issues, for example, failed backup jobs, it can often be helpful to have a log of the previously run tasks. With Proxmox VE, you can access the nodes’s task history through the pvenode task command. You can get a filtered list of a node’s finished tasks with the list subcommand. For example, to get a list of tasks related to VM _100_ that ended with an error, the command would be: pvenode task list --errors --vmid 100 The log of a task can then be printed using its UPID: pvenode task log UPID:pve1:00010D94:001CA6EA:6124E1B9:vzdump:100:root@pam: ### Bulk Guest Power Management[](https://pve.proxmox.com/pve-docs/pvenode.1.html#_bulk_guest_power_management "Permalink to this heading") In case you have many VMs/containers, starting and stopping guests can be carried out in bulk operations with the startall and stopall subcommands of pvenode. By default, pvenode startall will only start VMs/containers which have been set to automatically start on boot (see [Automatic Start and Shutdown of Virtual Machines](https://pve.proxmox.com/pve-docs/qm.1.html#qm_startup_and_shutdown) ), however, you can override this behavior with the \--force flag. Both commands also have a \--vms option, which limits the stopped/started guests to the specified VMIDs. For example, to start VMs _100_, _101_, and _102_, regardless of whether they have onboot set, you can use: pvenode startall --vms 100,101,102 --force To stop these guests (and any other guests that may be running), use the command: pvenode stopall | | | | --- | --- | | ![Note]() | The stopall command first attempts to perform a clean shutdown and then waits until either all guests have successfully shut down or an overridable timeout (3 minutes by default) has expired. Once that happens and the force-stop parameter is not explicitly set to 0 (false), all virtual guests that are still running are hard stopped. | ### First Guest Boot Delay[](https://pve.proxmox.com/pve-docs/pvenode.1.html#first_guest_boot_delay "Permalink to this heading") In case your VMs/containers rely on slow-to-start external resources, for example an NFS server, you can also set a per-node delay between the time Proxmox VE boots and the time the first VM/container that is configured to autostart boots (see [Automatic Start and Shutdown of Virtual Machines](https://pve.proxmox.com/pve-docs/qm.1.html#qm_startup_and_shutdown) ). You can achieve this by setting the following (where 10 represents the delay in seconds): pvenode config set --startall-onboot-delay 10 ### Bulk Guest Migration[](https://pve.proxmox.com/pve-docs/pvenode.1.html#_bulk_guest_migration "Permalink to this heading") In case an upgrade situation requires you to migrate all of your guests from one node to another, pvenode also offers the migrateall subcommand for bulk migration. By default, this command will migrate every guest on the system to the target node. It can however be set to only migrate a set of guests. For example, to migrate VMs _100_, _101_, and _102_, to the node _pve2_, with live-migration for local disks enabled, you can run: pvenode migrateall pve2 --vms 100,101,102 --with-local-disks ### RAM Usage Target for Ballooning[](https://pve.proxmox.com/pve-docs/pvenode.1.html#ballooning-target "Permalink to this heading") The target percentage for [automatic memory allocation](https://pve.proxmox.com/pve-docs/qm.1.html#qm_ballooning) defaults to 80%. You can customize this target per node by setting the ballooning-target property. For example, to target 90% host memory usage instead: pvenode config set --ballooning-target 90 Copyright and Disclaimer[](https://pve.proxmox.com/pve-docs/pvenode.1.html#_copyright_and_disclaimer "Permalink to this heading") ---------------------------------------------------------------------------------------------------------------------------------- Copyright © 2007-2022 Proxmox Server Solutions GmbH This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details. You should have received a copy of the GNU Affero General Public License along with this program. If not, see [https://www.gnu.org/licenses/](https://www.gnu.org/licenses/) * * * --- # PVE QEMU Event Daemon qmeventd is a daemon that listens on PATH for incoming connections from a qemu qmp socket, and waits for SHUTDOWN events. When a client then disconnects, it executes /usr/sbin/qm cleanup. This makes it easy to clean up leftover tap devices, vgpus, etc. * * * --- # pvesubscription(1) ☰ NAME[](https://pve.proxmox.com/pve-docs/pvesubscription.1.html#_name "Permalink to this heading") -------------------------------------------------------------------------------------------------- pvesubscription - Proxmox VE Subscription Manager SYNOPSIS[](https://pve.proxmox.com/pve-docs/pvesubscription.1.html#_synopsis "Permalink to this heading") ---------------------------------------------------------------------------------------------------------- **pvesubscription** \[ARGS\] \[OPTIONS\][](https://pve.proxmox.com/pve-docs/pvesubscription.1.html#cli_pvesubscription "Permalink to this heading") **pvesubscription delete**[](https://pve.proxmox.com/pve-docs/pvesubscription.1.html#cli_pvesubscription_delete "Permalink to this heading") Delete subscription key of this node. **pvesubscription get**[](https://pve.proxmox.com/pve-docs/pvesubscription.1.html#cli_pvesubscription_get "Permalink to this heading") Read subscription info. **pvesubscription help** \[OPTIONS\][](https://pve.proxmox.com/pve-docs/pvesubscription.1.html#cli_pvesubscription_help "Permalink to this heading") Get help about specified command. \--extra-args Shows help for a specific command \--verbose Verbose output format. **pvesubscription set** [](https://pve.proxmox.com/pve-docs/pvesubscription.1.html#cli_pvesubscription_set "Permalink to this heading") Set subscription key. : \\s\*pve(\[1248\])(\[cbsp\])-\[0-9a-f\]{10}\\s\* Proxmox VE subscription key **pvesubscription set-offline-key** [](https://pve.proxmox.com/pve-docs/pvesubscription.1.html#cli_pvesubscription_set-offline-key "Permalink to this heading") Internal use only! To set an offline key, use the package proxmox-offline-mirror-helper instead. : A signed subscription info blob **pvesubscription update** \[OPTIONS\][](https://pve.proxmox.com/pve-docs/pvesubscription.1.html#cli_pvesubscription_update "Permalink to this heading") Update subscription info. \--force (_default =_ 0) Always connect to server, even if local cache is still valid. DESCRIPTION[](https://pve.proxmox.com/pve-docs/pvesubscription.1.html#_description "Permalink to this heading") ---------------------------------------------------------------------------------------------------------------- This tool is used to handle Proxmox VE subscriptions. Copyright and Disclaimer[](https://pve.proxmox.com/pve-docs/pvesubscription.1.html#_copyright_and_disclaimer "Permalink to this heading") ------------------------------------------------------------------------------------------------------------------------------------------ Copyright © 2007-2022 Proxmox Server Solutions GmbH This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details. You should have received a copy of the GNU Affero General Public License along with this program. If not, see [https://www.gnu.org/licenses/](https://www.gnu.org/licenses/) * * * --- # Talk:Upgrade from 4.x to 5.0 - Proxmox VE Talk:Upgrade from 4.x to 5.0 ============================ From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Talk:Upgrade_from_4.x_to_5.0#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Talk:Upgrade_from_4.x_to_5.0#searchInput) What should be the video for a vm? the text says in one place: change from cirrus to std since cirrus has bugs and below: change from vga to cirrus Can some knowldedgeable person make a synthesis of these 2 different advices? Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Talk:Upgrade\_from\_4.x\_to\_5.0&oldid=10064](https://pve.proxmox.com/mediawiki/index.php?title=Talk:Upgrade_from_4.x_to_5.0&oldid=10064) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Iscsi/tests - Proxmox VE Iscsi/tests =========== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Iscsi/tests#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Iscsi/tests#searchInput) Contents -------- * [1 fio](https://pve.proxmox.com/wiki/Iscsi/tests#fio) * [2 mir's tests](https://pve.proxmox.com/wiki/Iscsi/tests#mir's_tests) * [3 sys4 tests](https://pve.proxmox.com/wiki/Iscsi/tests#sys4_tests) * [3.1 raidz1 with a log drive](https://pve.proxmox.com/wiki/Iscsi/tests#raidz1_with_a_log_drive) * [3.1.1 lxc](https://pve.proxmox.com/wiki/Iscsi/tests#lxc) * [3.1.2 kvm](https://pve.proxmox.com/wiki/Iscsi/tests#kvm) * [3.2 4 drive mirror, without a log drive](https://pve.proxmox.com/wiki/Iscsi/tests#4_drive_mirror,_without_a_log_drive) * [3.2.1 lxc](https://pve.proxmox.com/wiki/Iscsi/tests#lxc_2) * [3.2.2 kvm](https://pve.proxmox.com/wiki/Iscsi/tests#kvm_2) * [3.3 6 sata drive mirror with ssd log](https://pve.proxmox.com/wiki/Iscsi/tests#6_sata_drive_mirror_with_ssd_log) * [4 2 drive sata mirror](https://pve.proxmox.com/wiki/Iscsi/tests#2_drive_sata_mirror) fio --- for more info on fio see: TBD apt-get install fio create /root/fio.cfg : echo "# from mir pve forum \[global\] description=Emulation of Intel IOmeter File Server Access Pattern \[iometer\] bssplit=512/10:1k/5:2k/5:4k/60:8k/2:16k/4:32k/4:64k/10 rw=randrw rwmixread=80 direct=1 size=4g ioengine=libaio # IOMeter defines the server loads as the following: # iodepth=1 Linear # iodepth=4 Very Light # iodepth=8 Light # iodepth=64 Moderate # iodepth=256 Heavy iodepth=64" > /root/fio.cfg mir's tests ----------- * without nobarrier /dev/sdb1 on /media/disk type ext4 (rw,relatime,data=ordered) Run status group 0 (all jobs): READ: io=3274.5MB, aggrb=18596KB/s, minb=18,596KB/s, maxb=18,596KB/s, mint=18,0281msec, maxt=18,0281msec WRITE: io=841688KB, aggrb=4668KB/s, minb=4,668KB/s, maxb=4,668KB/s, mint=18,0281msec, maxt=180281msec Disk stats (read/write): sdb: ios=549723/137605, merge=1/36, ticks=9265908/2204204, in\_queue=11639448, util=100.00% * nobarrier /dev/sdb1 on /media/disk type ext4 (rw,relatime,nobarrier,data=ordered) Run status group 0 (all jobs): READ: io=3274.5MB, aggrb=30,526KB/s, minb=30,526KB/s, maxb=30,526KB/s, mint=10,9826msec, maxt=10,9826msec WRITE: io=841688KB, aggrb=7,663KB/s, minb=7,663KB/s, maxb=7,663KB/s, mint=10,9826msec, maxt=10,9826msec Disk stats (read/write): sdb: ios=550055/137665, merge=13/24, ticks=5510488/1558668, in\_queue=7071272, util=100.00% using XFS as filesystem inside the VM. /dev/sdb1 on /media/disk type xfs (rw,relatime,attr2,inode64,noquota) Run status group 0 (all jobs): READ: io=3274.5MB, aggrb=38,831KB/s, minb=38,831KB/s, maxb=38,831KB/s, mint=86,337msec, maxt=86,337msec WRITE: io=841688KB, aggrb=9,748KB/s, minb=9,748KB/s, maxb=9,748KB/s, mint=86337msec, maxt=86337msec Disk stats (read/write): sdb: ios=549888/137583, merge=0/3, ticks=375584/77740, in\_queue=452892, util=94.83% sys4 tests ---------- napp-it/omnios , motherboard: supermicro x9xcl-f , memory 28GB , cpu: Xeon(R) CPU E3-1280 V2 @ 3.60GHz \[htop shows 8 cores \] two SAS2008 IT mode HBA cards this testing system had multipath issues. will try to redo tests on final system. the following tests use a debian jessie virtual machines. ### raidz1 with a log drive zfs: raidz1 : 5 intel ssd pro series 2500 480GB + zil intel ssd s3700 #### lxc iometer: (g=0): rw=randrw, bs=512-64K/512-64K/512-64K, ioengine=libaio, iodepth=64 fio-2.1.11 Starting 1 process iometer: Laying out IO file(s) (1 file(s) / 4096MB) Jobs: 1 (f=1): \[m(1)\] \[100.0% done\] \[252.7MB/65052KB/0KB /s\] \[59.3K/14.8K/0 iops\] \[eta 00m:00s\] iometer: (groupid=0, jobs=1): err= 0: pid=2513: Sat Apr 9 15:24:14 2016 Description  : \[Emulation of Intel IOmeter File Server Access Pattern\] read : io=3274.5MB, bw=303130KB/s, iops=49742, runt= 11060msec slat (usec): min=2, max=588, avg= 7.45, stdev=18.05 clat (usec): min=160, max=252974, avg=885.66, stdev=2765.50 lat (usec): min=167, max=252977, avg=893.38, stdev=2765.43 clat percentiles (usec): | 1.00th=\[ 334\], 5.00th=\[ 406\], 10.00th=\[ 482\], 20.00th=\[ 580\], | 30.00th=\[ 652\], 40.00th=\[ 716\], 50.00th=\[ 772\], 60.00th=\[ 836\], | 70.00th=\[ 892\], 80.00th=\[ 980\], 90.00th=\[ 1128\], 95.00th=\[ 1304\], | 99.00th=\[ 1832\], 99.50th=\[ 2320\], 99.90th=\[20608\], 99.95th=\[38656\], | 99.99th=\[136192\] bw (KB /s): min=118739, max=444443, per=100.00%, avg=305665.86, stdev=75220.28 write: io=841688KB, bw=76102KB/s, iops=12445, runt= 11060msec slat (usec): min=3, max=1020, avg= 9.17, stdev=20.35 clat (usec): min=395, max=264907, avg=1552.83, stdev=5218.00 lat (usec): min=402, max=264915, avg=1562.29, stdev=5217.88 clat percentiles (usec): | 1.00th=\[ 644\], 5.00th=\[ 804\], 10.00th=\[ 908\], 20.00th=\[ 1032\], | 30.00th=\[ 1128\], 40.00th=\[ 1208\], 50.00th=\[ 1288\], 60.00th=\[ 1384\], | 70.00th=\[ 1480\], 80.00th=\[ 1624\], 90.00th=\[ 1864\], 95.00th=\[ 2128\], | 99.00th=\[ 2960\], 99.50th=\[ 4320\], 99.90th=\[61696\], 99.95th=\[121344\], | 99.99th=\[252928\] bw (KB /s): min=28575, max=111024, per=100.00%, avg=76804.24, stdev=18922.29 lat (usec) : 250=0.01%, 500=9.42%, 750=27.66%, 1000=31.51% lat (msec) : 2=29.46%, 4=1.58%, 10=0.12%, 20=0.06%, 50=0.12% lat (msec) : 100=0.02%, 250=0.03%, 500=0.01% cpu  : usr=12.19%, sys=56.86%, ctx=17722, majf=0, minf=8 IO depths  : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0% submit  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0% complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.1%, >=64=0.0% issued  : total=r=550156/w=137644/d=0, short=r=0/w=0/d=0 latency  : target=0, window=0, percentile=100.00%, depth=64 Run status group 0 (all jobs): READ: io=3274.5MB, aggrb=303130KB/s, minb=303130KB/s, maxb=303130KB/s, mint=11060msec, maxt=11060msec WRITE: io=841688KB, aggrb=76101KB/s, minb=76101KB/s, maxb=76101KB/s, mint=11060msec, maxt=11060msec Disk stats (read/write): dm-2: ios=543761/136160, merge=0/0, ticks=349496/178408, in\_queue=527996, util=99.14%, aggrios=547260/137478, aggrmerge=2955/219, aggrticks=351272/179892, aggrin\_queue=530992, aggrutil=98.92% sdk: ios=547260/137478, merge=2955/219, ticks=351272/179892, in\_queue=530992, util=98.92% #### kvm /dev/sda1 on / type ext4 (rw,relatime,nobarrier,data=ordered) at pve cache set to default nocache. iometer: (g=0): rw=randrw, bs=512-64K/512-64K/512-64K, ioengine=libaio, iodepth=64 fio-2.1.11 Starting 1 process Jobs: 1 (f=1): \[m(1)\] \[100.0% done\] \[13251KB/3173KB/0KB /s\] \[3093/735/0 iops\] \[eta 00m:00s\] iometer: (groupid=0, jobs=1): err= 0: pid=695: Sat Apr 9 19:12:16 2016 Description  : \[Emulation of Intel IOmeter File Server Access Pattern\] read : io=3274.5MB, bw=13694KB/s, iops=2247, runt=244825msec slat (usec): min=1, max=34337, avg=10.52, stdev=160.01 clat (usec): min=96, max=485692, avg=22701.29, stdev=14578.86 lat (usec): min=660, max=485701, avg=22712.10, stdev=14578.48 clat percentiles (usec): | 1.00th=\[ 1112\], 5.00th=\[ 2800\], 10.00th=\[ 4960\], 20.00th=\[ 9152\], | 30.00th=\[13504\], 40.00th=\[17792\], 50.00th=\[22144\], 60.00th=\[26496\], | 70.00th=\[30848\], 80.00th=\[35072\], 90.00th=\[40192\], 95.00th=\[43264\], | 99.00th=\[52480\], 99.50th=\[60160\], 99.90th=\[85504\], 99.95th=\[113152\], | 99.99th=\[296960\] bw (KB /s): min= 5004, max=25066, per=100.00%, avg=13713.01, stdev=3454.14 write: io=841688KB, bw=3437.1KB/s, iops=562, runt=244825msec slat (usec): min=3, max=32123, avg=17.92, stdev=409.82 clat (usec): min=868, max=483835, avg=23016.88, stdev=14330.54 lat (usec): min=881, max=483848, avg=23035.12, stdev=14335.88 clat percentiles (usec): | 1.00th=\[ 1416\], 5.00th=\[ 3056\], 10.00th=\[ 5216\], 20.00th=\[ 9536\], | 30.00th=\[13888\], 40.00th=\[18304\], 50.00th=\[22400\], 60.00th=\[26752\], | 70.00th=\[31104\], 80.00th=\[35584\], 90.00th=\[40192\], 95.00th=\[43776\], | 99.00th=\[53504\], 99.50th=\[61184\], 99.90th=\[85504\], 99.95th=\[98816\], | 99.99th=\[264192\] bw (KB /s): min= 1422, max= 6579, per=100.00%, avg=3443.28, stdev=926.27 lat (usec) : 100=0.01%, 250=0.01%, 500=0.01%, 750=0.04%, 1000=0.51% lat (msec) : 2=2.47%, 4=4.68%, 10=13.98%, 20=23.24%, 50=53.71% lat (msec) : 100=1.32%, 250=0.04%, 500=0.02% cpu  : usr=10.73%, sys=23.07%, ctx=673631, majf=0, minf=8 IO depths  : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0% submit  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0% complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.1%, >=64=0.0% issued  : total=r=550156/w=137644/d=0, short=r=0/w=0/d=0 latency  : target=0, window=0, percentile=100.00%, depth=64 Run status group 0 (all jobs): READ: io=3274.5MB, aggrb=13693KB/s, minb=13693KB/s, maxb=13693KB/s, mint=244825msec, maxt=244825msec WRITE: io=841688KB, aggrb=3437KB/s, minb=3437KB/s, maxb=3437KB/s, mint=244825msec, maxt=244825msec Disk stats (read/write): sda: ios=539489/137206, merge=11367/712, ticks=12209328/3240400, in\_queue=15451416, util=100.00% ### 4 drive mirror, without a log drive four intel ssd pro series 2500 480GB attached to its own HBA. #### lxc 3032-jessie ~ # fio /root/fio.cfg iometer: (g=0): rw=randrw, bs=512-64K/512-64K/512-64K, ioengine=libaio, iodepth=64 fio-2.1.11 Starting 1 process Jobs: 1 (f=1): \[m(1)\] \[100.0% done\] \[93189KB/23350KB/0KB /s\] \[21.7K/5469/0 iops\] \[eta 00m:00s\] iometer: (groupid=0, jobs=1): err= 0: pid=1857: Tue Apr 12 09:39:34 2016 Description  : \[Emulation of Intel IOmeter File Server Access Pattern\] read : io=3274.5MB, bw=109922KB/s, iops=18037, runt= 30500msec slat (usec): min=2, max=8635, avg= 6.00, stdev=16.12 clat (usec): min=144, max=43100, avg=2123.05, stdev=2388.69 lat (usec): min=166, max=43103, avg=2129.27, stdev=2388.60 clat percentiles (usec): | 1.00th=\[ 318\], 5.00th=\[ 418\], 10.00th=\[ 486\], 20.00th=\[ 604\], | 30.00th=\[ 732\], 40.00th=\[ 892\], 50.00th=\[ 1160\], 60.00th=\[ 1624\], | 70.00th=\[ 2384\], 80.00th=\[ 3312\], 90.00th=\[ 4896\], 95.00th=\[ 6496\], | 99.00th=\[10816\], 99.50th=\[13248\], 99.90th=\[22144\], 99.95th=\[24192\], | 99.99th=\[31616\] bw (KB /s): min=79049, max=218569, per=100.00%, avg=110088.87, stdev=30276.89 write: io=841688KB, bw=27596KB/s, iops=4512, runt= 30500msec slat (usec): min=3, max=8921, avg= 7.78, stdev=35.57 clat (usec): min=462, max=54371, avg=5654.28, stdev=3658.82 lat (usec): min=469, max=54379, avg=5662.30, stdev=3658.89 clat percentiles (usec): | 1.00th=\[ 1032\], 5.00th=\[ 1448\], 10.00th=\[ 1880\], 20.00th=\[ 2704\], | 30.00th=\[ 3408\], 40.00th=\[ 4128\], 50.00th=\[ 4896\], 60.00th=\[ 5728\], | 70.00th=\[ 6752\], 80.00th=\[ 8096\], 90.00th=\[10304\], 95.00th=\[12352\], | 99.00th=\[17536\], 99.50th=\[21632\], 99.90th=\[28288\], 99.95th=\[31104\], | 99.99th=\[41216\] bw (KB /s): min=19175, max=53703, per=100.00%, avg=27661.45, stdev=7629.12 lat (usec) : 250=0.09%, 500=8.83%, 750=16.25%, 1000=10.74% lat (msec) : 2=18.74%, 4=21.13%, 10=20.97%, 20=2.96%, 50=0.31% lat (msec) : 100=0.01% cpu  : usr=5.42%, sys=19.14%, ctx=91520, majf=0, minf=8 IO depths  : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0% submit  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0% complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.1%, >=64=0.0% issued  : total=r=550156/w=137644/d=0, short=r=0/w=0/d=0 latency  : target=0, window=0, percentile=100.00%, depth=64 Run status group 0 (all jobs): READ: io=3274.5MB, aggrb=109921KB/s, minb=109921KB/s, maxb=109921KB/s, mint=30500msec, maxt=30500msec WRITE: io=841688KB, aggrb=27596KB/s, minb=27596KB/s, maxb=27596KB/s, mint=30500msec, maxt=30500msec Disk stats (read/write): dm-3: ios=547778/137138, merge=0/0, ticks=1112764/760488, in\_queue=1873360, util=99.74%, aggrios=545238/137415, aggrmerge=5086/405, aggrticks=1107748/761360, aggrin\_queue=1868864, aggrutil=99.63% sdp: ios=545238/137415, merge=5086/405, ticks=1107748/761360, in\_queue=1868864, util=99.63% #### kvm * ext4 rw,relatime,nobarrier,data=ordered,errors=remount-ro 0 1 iometer: (g=0): rw=randrw, bs=512-64K/512-64K/512-64K, ioengine=libaio, iodepth=64 fio-2.1.11 Starting 1 process Jobs: 1 (f=1): \[m(1)\] \[100.0% done\] \[28797KB/6663KB/0KB /s\] \[6617/1530/0 iops\] \[eta 00m:00s\] iometer: (groupid=0, jobs=1): err= 0: pid=686: Tue Apr 12 10:12:28 2016 Description  : \[Emulation of Intel IOmeter File Server Access Pattern\] read : io=3274.5MB, bw=19017KB/s, iops=3120, runt=176293msec slat (usec): min=1, max=93960, avg=53.38, stdev=181.43 clat (usec): min=111, max=1536.1K, avg=16315.84, stdev=22454.79 lat (usec): min=433, max=1536.1K, avg=16372.43, stdev=22449.84 clat percentiles (usec): | 1.00th=\[ 964\], 5.00th=\[ 2096\], 10.00th=\[ 3440\], 20.00th=\[ 6048\], | 30.00th=\[ 8640\], 40.00th=\[11200\], 50.00th=\[13888\], 60.00th=\[16512\], | 70.00th=\[19584\], 80.00th=\[23424\], 90.00th=\[29312\], 95.00th=\[34560\], | 99.00th=\[49408\], 99.50th=\[82432\], 99.90th=\[329728\], 99.95th=\[460800\], | 99.99th=\[749568\] bw (KB /s): min= 555, max=29968, per=100.00%, avg=19030.43, stdev=5338.76 write: io=841688KB, bw=4774.4KB/s, iops=780, runt=176293msec slat (usec): min=2, max=29676, avg=67.29, stdev=300.20 clat (usec): min=179, max=1534.6K, avg=16353.61, stdev=22471.60 lat (usec): min=452, max=1534.6K, avg=16424.05, stdev=22467.04 clat percentiles (usec): | 1.00th=\[ 956\], 5.00th=\[ 2096\], 10.00th=\[ 3440\], 20.00th=\[ 6048\], | 30.00th=\[ 8640\], 40.00th=\[11328\], 50.00th=\[13888\], 60.00th=\[16768\], | 70.00th=\[19584\], 80.00th=\[23424\], 90.00th=\[29312\], 95.00th=\[34560\], | 99.00th=\[49920\], 99.50th=\[84480\], 99.90th=\[321536\], 99.95th=\[444416\], | 99.99th=\[741376\] bw (KB /s): min= 42, max= 7746, per=100.00%, avg=4778.38, stdev=1386.59 lat (usec) : 250=0.01%, 500=0.05%, 750=0.32%, 1000=0.74% lat (msec) : 2=3.53%, 4=7.44%, 10=23.16%, 20=35.92%, 50=27.86% lat (msec) : 100=0.59%, 250=0.23%, 500=0.12%, 750=0.03%, 1000=0.01% lat (msec) : 2000=0.01% cpu  : usr=3.12%, sys=48.14%, ctx=319451, majf=0, minf=8 IO depths  : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0% submit  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0% complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.1%, >=64=0.0% issued  : total=r=550156/w=137644/d=0, short=r=0/w=0/d=0 latency  : target=0, window=0, percentile=100.00%, depth=64 Run status group 0 (all jobs): READ: io=3274.5MB, aggrb=19017KB/s, minb=19017KB/s, maxb=19017KB/s, mint=176293msec, maxt=176293msec WRITE: io=841688KB, aggrb=4774KB/s, minb=4774KB/s, maxb=4774KB/s, mint=176293msec, maxt=176293msec Disk stats (read/write): sda: ios=539868/137353, merge=10782/802, ticks=8688496/2847176, in\_queue=11534452, util=100.00% * default ext4 errors=remount-ro 0 1 iometer: (g=0): rw=randrw, bs=512-64K/512-64K/512-64K, ioengine=libaio, iodepth=64 fio-2.1.11 Starting 1 process iometer: Laying out IO file(s) (1 file(s) / 4096MB) Jobs: 1 (f=1): \[m(1)\] \[100.0% done\] \[22426KB/5431KB/0KB /s\] \[5174/1254/0 iops\] \[eta 00m:00s\] iometer: (groupid=0, jobs=1): err= 0: pid=707: Tue Apr 12 10:04:43 2016 Description  : \[Emulation of Intel IOmeter File Server Access Pattern\] read : io=3274.5MB, bw=27987KB/s, iops=4592, runt=119793msec slat (usec): min=2, max=8121, avg=138.38, stdev=78.30 clat (usec): min=61, max=878540, avg=10981.79, stdev=26616.61 lat (usec): min=205, max=878545, avg=11122.39, stdev=26610.60 clat percentiles (msec): | 1.00th=\[ 6\], 5.00th=\[ 8\], 10.00th=\[ 9\], 20.00th=\[ 10\], | 30.00th=\[ 10\], 40.00th=\[ 10\], 50.00th=\[ 10\], 60.00th=\[ 10\], | 70.00th=\[ 10\], 80.00th=\[ 11\], 90.00th=\[ 12\], 95.00th=\[ 13\], | 99.00th=\[ 17\], 99.50th=\[ 19\], 99.90th=\[ 627\], 99.95th=\[ 693\], | 99.99th=\[ 848\] bw (KB /s): min= 419, max=56905, per=100.00%, avg=29243.35, stdev=10428.05 write: io=841688KB, bw=7026.2KB/s, iops=1149, runt=119793msec slat (usec): min=3, max=8183, avg=149.49, stdev=114.76 clat (usec): min=564, max=878335, avg=11044.70, stdev=27526.77 lat (usec): min=608, max=878344, avg=11196.21, stdev=27539.90 clat percentiles (msec): | 1.00th=\[ 6\], 5.00th=\[ 8\], 10.00th=\[ 9\], 20.00th=\[ 10\], | 30.00th=\[ 10\], 40.00th=\[ 10\], 50.00th=\[ 10\], 60.00th=\[ 10\], | 70.00th=\[ 10\], 80.00th=\[ 11\], 90.00th=\[ 12\], 95.00th=\[ 13\], | 99.00th=\[ 17\], 99.50th=\[ 20\], 99.90th=\[ 635\], 99.95th=\[ 693\], | 99.99th=\[ 873\] bw (KB /s): min= 69, max=14976, per=100.00%, avg=7341.69, stdev=2672.17 lat (usec) : 100=0.01%, 250=0.01%, 500=0.01%, 750=0.01%, 1000=0.01% lat (msec) : 2=0.06%, 4=0.32%, 10=76.18%, 20=23.02%, 50=0.19% lat (msec) : 100=0.02%, 250=0.02%, 500=0.04%, 750=0.13%, 1000=0.02% cpu  : usr=2.64%, sys=81.63%, ctx=480152, majf=0, minf=8 IO depths  : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0% submit  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0% complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.1%, >=64=0.0% issued  : total=r=550156/w=137644/d=0, short=r=0/w=0/d=0 latency  : target=0, window=0, percentile=100.00%, depth=64 Run status group 0 (all jobs): READ: io=3274.5MB, aggrb=27986KB/s, minb=27986KB/s, maxb=27986KB/s, mint=119793msec, maxt=119793msec WRITE: io=841688KB, aggrb=7026KB/s, minb=7026KB/s, maxb=7026KB/s, mint=119793msec, maxt=119793msec Disk stats (read/write): sda: ios=548732/137547, merge=838/94, ticks=976940/269344, in\_queue=1243892, util=95.91% ### 6 sata drive mirror with ssd log I scrapped this set up. and went with a 2 drive mirror with the newest disks \[ some of the others were 4-5 years old \]. kvm jessie-template ~ # fio /fbc/adm/fio.cfg # fio.cfg contains mir's code above . TBD upload fio.cfg or copy paste to screen iometer: (g=0): rw=randrw, bs=512-64K/512-64K/512-64K, ioengine=libaio, iodepth=64 fio-2.1.11 Starting 1 process iometer: Laying out IO file(s) (1 file(s) / 4096MB) Jobs: 1 (f=1): \[m(1)\] \[100.0% done\] \[119.1MB/31420KB/0KB /s\] \[28.5K/7151/0 iops\] \[eta 00m:00s\] iometer: (groupid=0, jobs=1): err= 0: pid=1369: Mon Jun 6 12:49:29 2016 Description  : \[Emulation of Intel IOmeter File Server Access Pattern\] read : io=3274.5MB, bw=164191KB/s, iops=26943, runt= 20419msec slat (usec): min=1, max=1030, avg= 6.10, stdev= 4.59 clat (usec): min=117, max=166663, avg=1716.19, stdev=4230.12 lat (usec): min=126, max=166670, avg=1722.55, stdev=4230.16 clat percentiles (usec): | 1.00th=\[ 524\], 5.00th=\[ 876\], 10.00th=\[ 940\], 20.00th=\[ 996\], | 30.00th=\[ 1032\], 40.00th=\[ 1064\], 50.00th=\[ 1096\], 60.00th=\[ 1144\], | 70.00th=\[ 1192\], 80.00th=\[ 1272\], 90.00th=\[ 1624\], 95.00th=\[ 2160\], | 99.00th=\[21120\], 99.50th=\[37632\], 99.90th=\[55040\], 99.95th=\[57600\], | 99.99th=\[62720\] bw (KB /s): min=95414, max=313106, per=100.00%, avg=164904.00, stdev=49364.41 write: io=841688KB, bw=41221KB/s, iops=6740, runt= 20419msec slat (usec): min=2, max=44634, avg= 8.04, stdev=137.58 clat (usec): min=419, max=89028, avg=2592.06, stdev=5228.52 lat (usec): min=526, max=89034, avg=2600.37, stdev=5230.32 clat percentiles (usec): | 1.00th=\[ 1096\], 5.00th=\[ 1240\], 10.00th=\[ 1304\], 20.00th=\[ 1368\], | 30.00th=\[ 1416\], 40.00th=\[ 1464\], 50.00th=\[ 1512\], 60.00th=\[ 1576\], | 70.00th=\[ 1656\], 80.00th=\[ 1816\], 90.00th=\[ 2448\], 95.00th=\[ 4896\], | 99.00th=\[30848\], 99.50th=\[41216\], 99.90th=\[56576\], 99.95th=\[59136\], | 99.99th=\[61696\] bw (KB /s): min=23379, max=78212, per=100.00%, avg=41429.42, stdev=12385.69 lat (usec) : 250=0.11%, 500=0.62%, 750=1.42%, 1000=14.84% lat (msec) : 2=74.72%, 4=5.20%, 10=0.72%, 20=1.05%, 50=1.12% lat (msec) : 100=0.21%, 250=0.01% cpu  : usr=11.13%, sys=25.59%, ctx=304291, majf=0, minf=8 IO depths  : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0% submit  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0% complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.1%, >=64=0.0% issued  : total=r=550156/w=137644/d=0, short=r=0/w=0/d=0 latency  : target=0, window=0, percentile=100.00%, depth=64 Run status group 0 (all jobs): READ: io=3274.5MB, aggrb=164191KB/s, minb=164191KB/s, maxb=164191KB/s, mint=20419msec, maxt=20419msec WRITE: io=841688KB, aggrb=41220KB/s, minb=41220KB/s, maxb=41220KB/s, mint=20419msec, maxt=20419msec Disk stats (read/write): vda: ios=548282/137250, merge=0/0, ticks=934124/351920, in\_queue=1286136, util=99.50% 2 drive sata mirror ------------------- with zil and cache on a intel super ssd \[model later if needed, 200GB recommended model \] Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Iscsi/tests&oldid=9538](https://pve.proxmox.com/mediawiki/index.php?title=Iscsi/tests&oldid=9538) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # ZFS: Switch Legacy-Boot to Proxmox Boot Tool - Proxmox VE ZFS: Switch Legacy-Boot to Proxmox Boot Tool ============================================ From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#mw-head) [Jump to search](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#Introduction) * [1.1 Problem Description](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#Problem_Description) * [1.2 Solution Overview](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#Solution_Overview) * [2 Switching to proxmox-boot-tool from a Running Proxmox VE System](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#Switching_to_proxmox-boot-tool_from_a_Running_Proxmox_VE_System) * [2.1 Checks](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#Checks) * [2.1.1 1\. Check if root is on ZFS](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#1._Check_if_root_is_on_ZFS) * [2.1.2 2\. Check which bootloader is used](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#2._Check_which_bootloader_is_used) * [2.1.3 3\. Finding potential ESPs](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#3._Finding_potential_ESPs) * [2.2 Switching to proxmox-boot-tool](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#Switching_to_proxmox-boot-tool) * [2.2.1 0\. Upgrade to Proxmox VE 6.4](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#0._Upgrade_to_Proxmox_VE_6.4) * [2.2.2 1\. Format the new intermediate boot devices](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#1._Format_the_new_intermediate_boot_devices) * [2.2.3 2\. Initialize & Add the new intermediate boot devices](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#2._Initialize_&_Add_the_new_intermediate_boot_devices) * [2.2.4 3\. Verify the status](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#3._Verify_the_status) * [3 Repairing a System Stuck in the GRUB Rescue Shell](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#Repairing_a_System_Stuck_in_the_GRUB_Rescue_Shell) * [4 Background](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#Background) * [4.1 zpool Features and GRUB](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#zpool_Features_and_GRUB) Introduction ------------ This HOWTO is meant for legacy-booted systems, with root on ZFS, installed using a Proxmox VE ISO between 5.4 and 6.3, and which are booted using grub. You will _not_ need this if any of the following points are true: * System installed using Proxmox VE ISO 6.4 or later * System uses UEFI to boot and was installed in UEFI mode * System is not using ZFS as the root filesystem ### Problem Description On systems booting from GRUB legacy BIOS boot with root filesystem on ZFS, doing a `zpool upgrade` on the 'rpool' will **break boot**. For more details see [#Background](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#Background) ### Solution Overview The system will be adapted to carry out the first boot steps from a small, separate partition with a simple FAT based file-system instead of the more complex ZFS directly. The `EFI System Partition` (ESP), which often already exists, will be set up and used to hold that initial RAM disk (`initrd`). In the end, both legacy BIOS or UEFI can use this setup for booting. Switching to proxmox-boot-tool from a Running Proxmox VE System --------------------------------------------------------------- ### Checks The following checks will help you to determine if you boot from ZFS directly through GRUB and thus would benefit from this how-to. #### 1\. Check if root is on ZFS Run the following command as root: `findmnt /` The system has its root on ZFS, if the output says that FSTYPE is zfs. For example, if it looks like: \# findmnt / TARGET SOURCE FSTYPE OPTIONS / rpool/ROOT/pve-1 zfs rw,relatime,xattr,noacl #### 2\. Check which bootloader is used See the [reference documentation section](https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysboot_determine_bootloader_used) about how to find out which boot-loader is being used in your system. If you use ZFS on root and the command `ls /sys/firmware/efi` outputs "No such file or directory", the chances are high that you boot from GRUB and thus would benefit from switching to proxmox-boot-tool, using the steps in this how-to. #### 3\. Finding potential ESPs Any partition or block device with a size of 512M or more can be used by `proxmox-boot-tool` as a target. Systems installed using a Proxmox VE ISO newer than 5.4 already set up a second VFAT partition (for example /dev/sda2) with size 512 M. You can check the partitions with `lsblk`. For instance, here is a system with root on a RAID-Z1, installed with Proxmox VE 5.4: \# lsblk -o +FSTYPE NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT FSTYPE sda 8:0 0 12G 0 disk zfs\_member ├─sda1 8:1 0 1007K 0 part zfs\_member ├─sda2 8:2 0 512M 0 part └─sda3 8:3 0 11.5G 0 part zfs\_member sdb 8:16 0 12G 0 disk zfs\_member ├─sdb1 8:17 0 1007K 0 part zfs\_member ├─sdb2 8:18 0 512M 0 part └─sdb3 8:19 0 11.5G 0 part zfs\_member sdc 8:32 0 12G 0 disk zfs\_member ├─sdc1 8:33 0 1007K 0 part zfs\_member ├─sdc2 8:34 0 512M 0 part └─sdc3 8:35 0 11.5G 0 part zfs\_member All three disks (sda, sdb and sdc) have a second partition with 512M size and no FS type (sda2, sdb2 and sdc2). This means that in the above example, the three partitions sda2, sdb2 and sdc2 would be used with `proxmox-boot-tool` in the next steps. ### Switching to proxmox-boot-tool #### 0\. Upgrade to Proxmox VE 6.4 The support for booting a ZFS legacy-GRUB setup through the proxmox-boot-tool is only available since Proxmox VE 6.4 \# pveversion pve-manager/6.4-5/6c7bf5de (running kernel: 5.4.106-1-pve) See the [11\. How can I upgrade Proxmox VE to the next release?](https://pve.proxmox.com/pve-docs/chapter-pve-faq.html#:~:text=How%20can%20I%20upgrade%20Proxmox%20VE%20to%20the%20next%20release?) point in the documentation's FAQ, if you're unsure about how to do that. You can check if your Proxmox VE version is recent enough for using proxmox-boot-tool by simply executing \# proxmox-boot-tool help That should print a usage help. #### 1\. Format the new intermediate boot devices **Hint**: You could skip this step if the partition already has a `vfat` partition set up. If you never plan to boot via EFI you may still want to re-format by adding the `--force` flag to below's format command to get a clean setup without the EFI bootloader configured and taking up space. For each 512M sized block device you found when following the section [Finding potential ESPs](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#3._Finding_potential_ESPs) , you will now set up a fresh, new VFAT partition using `proxmox-boot-tool format /dev/sdXY` For the example used in the section [Finding potential ESPs](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#3._Finding_potential_ESPs) , you would execute: \# proxmox-boot-tool format /dev/sda2 # proxmox-boot-tool format /dev/sdb2 # proxmox-boot-tool format /dev/sdc2 **NOTE**: Be sure that you're passing the correct partitions; **the format command will destroy any data on the passed partition**! #### 2\. Initialize & Add the new intermediate boot devices Now we add the newly formatted VFAT partitions to the proxmox-boot-tool configuration using `proxmox-boot-tool init /dev/sdXY` For the example used in the section [Finding potential ESPs](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#3._Finding_potential_ESPs) , you would execute: \# proxmox-boot-tool init /dev/sda2 # proxmox-boot-tool init /dev/sdb2 # proxmox-boot-tool init /dev/sdc2 `proxmox-boot-tool` may print a warning about a non-exisiting UUID like: `WARN: /dev/disk/by-uuid/E8A5-779A does not exist - clean '/etc/kernel/proxmox-boot-uuids'! - skipping`. You can run the `clean` command in that case: \# proxmox-boot-tool clean Which will simply remove any non-existent parition from the Proxmox boot tool configuration. #### 3\. Verify the status To verify that everything has been set up correctly, you can run the status command: \# proxmox-boot-tool status Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace.. 373A-957C is configured with: grub 3961-474D is configured with: grub 3C07-40DC is configured with: grub In the above example, we see all three partitions from the three ZFS disks setup for "grub" only. It is totally fine if some or all disks display `uefi,grub` instead. Following this, it should be possible to boot the systems from any of the 3 disks. Repairing a System Stuck in the GRUB Rescue Shell ------------------------------------------------- If you end up with a system stuck in the `grub rescue>` shell, the following steps should make it bootable again: 1. Boot using a Proxmox VE version 6.4 or newer ISO 2. Select `Install Proxmox VE (Debug Mode)` 3. Exit the first debug shell by typing `Ctrl + D` or `exit` 4. The second debug shell contains all the necessary binaries for the following steps 5. Import the root pool (usually named `rpool`) with an alternative mountpoint of `/mnt`: zpool import -f -R /mnt rpool 6. Find the partition to use for `proxmox-boot-tool`, following the instructions from [Finding potential ESPs](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#3._Finding_potential_ESPs) 7. Bind-mount all virtual filesystems needed for running `proxmox-boot-tool`: mount -o rbind /proc /mnt/proc mount -o rbind /sys /mnt/sys mount -o rbind /dev /mnt/dev mount -o rbind /run /mnt/run 8. change root into `/mnt` chroot /mnt /bin/bash 9. Format and initialize the partitions in the chroot - see [Switching to proxmox-boot-tool](https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#Switching_to_proxmox-boot-tool) 10. Exit the chroot-shell (`Ctrl + D` or `exit`) and reset the system (for example by pressing `CTRL + ALT + DEL`) 11. **Note**: The next boot can end up in an `initramfs` shell, due to the `hostid` mismatch (from importing the pool in the installer). If this is the case, simply import it again with using the force `-f` flag: \# zpool import -f rpool After the import you can just reboot. The system should now boot successfully with the new, more robust, boot setup. Background ========== Grub has a limited implementation for reading data from ZFS. #### zpool Features and GRUB * ZFS changes the on-disk format with zpool features, documented in the `zpool-features(5)` [man-page](https://openzfs.github.io/openzfs-docs/man/5/zpool-features.5.html) * Features are only added in minor version upgrades (e.g. from 0.7.x -> 0.8.x , or 0.8.x -> 2.0.x) - see [https://github.com/openzfs/zfs/blob/master/RELEASES.md](https://github.com/openzfs/zfs/blob/master/RELEASES.md) * Running `zpool upgrade` on a pool _enables_ the features * [READ-ONLY COMPATIBLE features](https://openzfs.github.io/openzfs-docs/man/5/zpool-features.5.html) should not cause any problems * A new feature should only be problematic if it is _active_ (e.g. setting the compression to zstd on a dataset will cause the `feature@zstd_compress` feature to become _active_) * GRUB is not able to read data from a pool which has an incompatible (and not read-only compatible) _active_ feature * The list of features supported by grub can be seen on: * [Debian Buster Root on ZFS](https://openzfs.github.io/openzfs-docs/Getting%20Started/Debian/Debian%20Buster%20Root%20on%20ZFS.html) * [http://git.savannah.gnu.org/cgit/grub.git/tree/grub-core/fs/zfs/zfs.c#n276](http://git.savannah.gnu.org/cgit/grub.git/tree/grub-core/fs/zfs/zfs.c#n276) To check which features are active on your `rpool` run: \# zpool get all rpool |grep active While it usually takes active actions by an administrator to cause a system to become unbootable, these can happen by accident. Examples of actions and circumstances that will render a pool unbootable: * Running `zpool upgrade rpool`, then setting the compression feature to use `zstd` on any dataset in `rpool` * Setting the `dnodesize` property of any dataset on `rpool` to `auto` (or any value apart from `legacy`) * The drivers for certain disk controllers (e.g. some HP SmartArray models) in GRUB can only read the first 2TB of the disk - combined with the nature of ZFS Copy-on-Write, this means that the system can become unbootable simply by installing a new kernel-image (which ends up after 2TB on disk). The fragility of booting from ZFS with GRUB is the reason why recent Proxmox systems read the kernel and initrd image from a 512MB vfat partition, which is created in front of the ZFS partition (since PVE 5.4). The kernel and initrd images are copied to the vfat partition by `proxmox-boot-tool` (before Proxmox VE 6.4, the utility was called `pve-efiboot-tool`) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=ZFS:\_Switch\_Legacy-Boot\_to\_Proxmox\_Boot\_Tool&oldid=11315](https://pve.proxmox.com/mediawiki/index.php?title=ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool&oldid=11315) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # QEMU/KVM ACPI Guest Shutdown - Proxmox VE QEMU/KVM ACPI Guest Shutdown ============================ From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/QEMU/KVM_ACPI_Guest_Shutdown#mw-head) [Jump to search](https://pve.proxmox.com/wiki/QEMU/KVM_ACPI_Guest_Shutdown#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/QEMU/KVM_ACPI_Guest_Shutdown#Introduction) * [2 Linux](https://pve.proxmox.com/wiki/QEMU/KVM_ACPI_Guest_Shutdown#Linux) * [3 Windows](https://pve.proxmox.com/wiki/QEMU/KVM_ACPI_Guest_Shutdown#Windows) * [3.1 Windows HAL Links](https://pve.proxmox.com/wiki/QEMU/KVM_ACPI_Guest_Shutdown#Windows_HAL_Links) * [4 QEMU Guest Agent as Alternative](https://pve.proxmox.com/wiki/QEMU/KVM_ACPI_Guest_Shutdown#QEMU_Guest_Agent_as_Alternative) Introduction ============ Proxmox VE uses ACPI by default to send shutdown signals to the Virtual Machines (QEMU/KVM). That means that your Virtual Machines needs to support ACPI, so that it may react to such signals. You should check if your VM reacts properly to the ACPI signals, as else the VM may not shutdown and Proxmox VE will force-stop it after a timeout on some API calls. Such a stop can lead to data loss in the worst case. Linux ===== For Linux VMs you need to make sure that the ACPI event daemon is installed and running. Desktop distributions should already have it setup out of the box, but minimal- or server distributions often do not. For Ubuntu and Debian install the 'acpid' package in the Virtual Machine. apt update apt install acpid Windows ======= For Windows, make sure an ACPI HAL is installed. On older Windows Server 2003/8 also make sure to change policy to allow shutdown without being logged into the system. Start -> Run: gpedit.msc Find the following key: Computer Configuration\\Windows Settings\\Security Settings\\Local Policies\\Security Options\\Shutdown: Allow system to be shut down without having to log on Change it to "Enabled". ### Windows HAL Links * [Microsoft HAL KB](http://support.microsoft.com/kb/309283) * [Moving from one HAL to another](http://www.techsupportforum.com/hardware-support/motherboards-bios-cpu/212903-truly-unique-problem-acpi-hal.html) QEMU Guest Agent as Alternative =============================== ACPI shutdown may not always work, one can setup the [QEMU Guest Agent (QGA)](https://pve.proxmox.com/wiki/Qemu-guest-agent "Qemu-guest-agent") as an alternative. Just ensure that you enable it in the VMs Options in the Proxmox VE webinterface, and to install and run the agent inside the VM. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=QEMU/KVM\_ACPI\_Guest\_Shutdown&oldid=10857](https://pve.proxmox.com/mediawiki/index.php?title=QEMU/KVM_ACPI_Guest_Shutdown&oldid=10857) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Qemu/KVM](https://pve.proxmox.com/wiki/Category:Qemu/KVM "Category:Qemu/KVM") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Qemu-guest-agent - Proxmox VE Qemu-guest-agent ================ From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Qemu-guest-agent#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Qemu-guest-agent#searchInput) Contents -------- * [1 Introduction - What is qemu-guest-agent](https://pve.proxmox.com/wiki/Qemu-guest-agent#Introduction_-_What_is_qemu-guest-agent) * [2 Installation](https://pve.proxmox.com/wiki/Qemu-guest-agent#Installation) * [2.1 Host](https://pve.proxmox.com/wiki/Qemu-guest-agent#Host) * [2.2 Guest](https://pve.proxmox.com/wiki/Qemu-guest-agent#Guest) * [2.2.1 Linux](https://pve.proxmox.com/wiki/Qemu-guest-agent#Linux) * [2.2.2 Windows](https://pve.proxmox.com/wiki/Qemu-guest-agent#Windows) * [2.3 Testing that the communication with the guest agent is working](https://pve.proxmox.com/wiki/Qemu-guest-agent#Testing_that_the_communication_with_the_guest_agent_is_working) * [3 See Also](https://pve.proxmox.com/wiki/Qemu-guest-agent#See_Also) Introduction - What is qemu-guest-agent --------------------------------------- The qemu-guest-agent is a helper daemon, which is installed in the guest. It is used to exchange information between the host and guest, and to execute command in the guest. In Proxmox VE, the qemu-guest-agent is used for mainly two things: 1. To properly shutdown the guest, instead of relying on ACPI commands or windows policies 2. To freeze the guest file system when making a backup/snapshot (on windows, use the volume shadow copy service VSS). If the guest agent is enabled and running, it calls _guest-fsfreeze-freeze_ and _guest-fsfreeze-thaw_ to improve consistency. Installation ------------ ### Host You have to install guest-agent in each VM and then enable it, you can do that in the Proxmox VE Webinterface (GUI) [![QEMU Guest Agent Option](https://pve.proxmox.com/mediawiki/images/6/6d/Proxmox_VE_-_QEMU_Guest_Agent_Option.png)](https://pve.proxmox.com/wiki/File:Proxmox_VE_-_QEMU_Guest_Agent_Option.png "QEMU Guest Agent Option") or via CLI: `qm set VMID --agent 1` ### Guest #### Linux On Linux you have to simply install the qemu-guest-agent, please refer to the documentation of your system. We show here the commands for Debian/Ubuntu and Redhat based systems: on Debian/Ubuntu based systems (with apt-get) run: apt-get install qemu-guest-agent and on Redhat based systems (with yum): yum install qemu-guest-agent Depending on the distribution, the guest agent might not start automatically after the installation. Start it either directly with systemctl start qemu-guest-agent Then enable the service to autostart (permanently) if not auto started, with systemctl enable qemu-guest-agent (should work for most distributions) or reboot the guest. #### Windows [![](https://pve.proxmox.com/mediawiki/images/thumb/3/3f/Screen-vioserial-device-manager.png/600px-Screen-vioserial-device-manager.png)](https://pve.proxmox.com/wiki/File:Screen-vioserial-device-manager.png) [![](https://pve.proxmox.com/mediawiki/images/thumb/f/f3/Screen-vioserial-driver.png/600px-Screen-vioserial-driver.png)](https://pve.proxmox.com/wiki/File:Screen-vioserial-driver.png) First you have to download the virtio-win driver iso (see [Windows VirtIO Drivers](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers "Windows VirtIO Drivers") ). Then install the virtio-serial driver: 1. Attach the ISO to your windows VM (virtio-\*.iso) 2. Go to the windows Device Manager 3. Look for "PCI Simple Communications Controller" 4. Right Click -> Update Driver and select on the mounted iso in DRIVE:\\vioserial\\\\ where is your Windows Version (e.g. 2k12R2 for Windows 2012 R2) After that, you have to install the qemu-guest-agent: 1. Go to the mounted ISO in explorer 2. The guest agent installer is in the directory **guest-agent** 3. Execute the installer with double click (either **qemu-ga-x86\_64.msi** (64-bit) or **qemu-ga-i386.msi** (32-bit) After that the qemu-guest-agent should be up and running. You can validate this in the list of Window Services, or in a PowerShell with: PS C:\\Users\\Administrator> Get-Service QEMU-GA Status Name DisplayName ------ ---- ----------- Running QEMU-GA QEMU Guest Agent If it is not running, you can use the **Services** control panel to start it and make sure that it will start automatically on the next boot. ### Testing that the communication with the guest agent is working The communication with the guest agent takes place over a unix socket located in /var/run/qemu-server/.qga You can test the communication qm agent: qm agent ping if the qemu-guest-agent is correctly runnning in the VM, it will return without an error message. See Also -------- [http://wiki.qemu.org/Features/GuestAgent](http://wiki.qemu.org/Features/GuestAgent) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Qemu-guest-agent&oldid=12431](https://pve.proxmox.com/mediawiki/index.php?title=Qemu-guest-agent&oldid=12431) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Installation](https://pve.proxmox.com/wiki/Category:Installation "Category:Installation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # HTTPS Certificate Configuration (Version 4.x, 5.0 and 5.1) - Proxmox VE HTTPS Certificate Configuration (Version 4.x, 5.0 and 5.1) ========================================================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#mw-head) [Jump to search](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#searchInput) ℹ️ **Note**: Article about old Proxmox VE 4.x, 5.0 and 5.1 releases. From Proxmox VE 5.2 this is part of the reference documentation see: [Certificate Management](https://pve.proxmox.com/wiki/Certificate_Management "Certificate Management") or [http://pve.proxmox.com/pve-docs/](http://pve.proxmox.com/pve-docs/) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#Introduction) * [2 Revert to default configuration](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#Revert_to_default_configuration) * [3 CAs other than Let's Encrypt](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#CAs_other_than_Let's_Encrypt) * [3.1 Install certificate chain and key](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#Install_certificate_chain_and_key) * [4 Let's Encrypt using acme.sh](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#Let's_Encrypt_using_acme.sh) * [4.1 Prerequisites](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#Prerequisites) * [4.2 Install certificate chain and key](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#Install_certificate_chain_and_key_2) * [4.2.1 0) Upgrade from le.sh to acme.sh](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#0)_Upgrade_from_le.sh_to_acme.sh) * [4.2.2 1) Install acme.sh](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#1)_Install_acme.sh) * [4.2.3 2) Run the install script](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#2)_Run_the_install_script) * [4.2.4 3) Check the account config](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#3)_Check_the_account_config) * [4.2.5 4) Make sure port 80 is open from the public](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#4)_Make_sure_port_80_is_open_from_the_public) * [4.2.6 5) Issue your first certificate](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#5)_Issue_your_first_certificate) * [4.2.7 6\. Check it's working](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#6._Check_it's_working) * [4.2.8 7\. Set up automatic renewal](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#7._Set_up_automatic_renewal) * [4.3 Updating acme.sh](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#Updating_acme.sh) * [4.4 Account key](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#Account_key) * [5 Let's Encrypt using eff.org's certbot](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#Let's_Encrypt_using_eff.org's_certbot) * [5.1 Installing certbot](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#Installing_certbot) * [5.2 Obtaining your certificate](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#Obtaining_your_certificate) * [5.3 Getting your certificate into Proxmox](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#Getting_your_certificate_into_Proxmox) * [5.4 Setting up renewal](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#Setting_up_renewal) * [6 Let's Encrypt using other Clients](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#Let's_Encrypt_using_other_Clients) Introduction ------------ This is a howto for changing the web server certificate used by Proxmox VE, in order to enable the usage of publicly trusted certificates issued by a CA of your choice (like Let's Encrypt or a commercial CA). It has been tested on a Proxmox VE 4.1 installation, using certificates from [https://www.letsencrypt.org](https://www.letsencrypt.org/) . _Note: the previous, outdated version of this HowTo is archived at [HTTPS Certificate Configuration (Version 3.x and earlier)](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_3.x_and_earlier) "HTTPS Certificate Configuration (Version 3.x and earlier)") _ Revert to default configuration ------------------------------- If you have used the previous HowTo and replaced any of the certificate or key files generated by PVE, you need to revert to the default state before proceeding. Delete or move the following files: * /etc/pve/pve-root-ca.pem * /etc/pve/priv/pve-root-ca.key * /etc/pve/nodes//pve-ssl.pem * /etc/pve/nodes//pve-ssl.key The latter two need to be repeated for all nodes if you have a cluster. Afterwards, run the following command on each node of the cluster to re-generate the certificates and keys: pvecm updatecerts -f CAs other than Let's Encrypt ---------------------------- ### Install certificate chain and key Since pve-manager 4.1-20, it is possible to provide alternative SSL files for each node's web interface. The following steps need to be repeated for each node where you want to use alternative certificate files. First check your version of pve-manager and upgrade if necessary: pveversion You will need the following two files provided by your CA: * fullchain.pem (your certificate and all intermediate certificates, excluding the root certificate, in PEM format) * private-key.pem (your private key, in PEM format, without a password) Now copy those files to the override locations in /etc/pve/nodes/ (make sure to use the correct certificate files and node!): cp fullchain.pem /etc/pve/nodes//pveproxy-ssl.pem cp private-key.pem /etc/pve/nodes//pveproxy-ssl.key and restart the web interface: systemctl restart pveproxy The system log should inform you about the usage of the alternative SSL certificate ("Using '/etc/pve/local/pveproxy-ssl.pem' as certificate for the web interface."): journalctl -b -u pveproxy.service When accessing the web interface on this node, you should be presented with the new certificate. Note that the alternative certificate is only used by the web interface (including noVNC), but not by the Spice Console/Shell. Let's Encrypt using acme.sh --------------------------- ### Prerequisites Let's Encrypt enables everyone with a publicly resolvable domain name to be issued SSL certificates for free. Your domain name needs to be publicly resolvable both ways. (Check with \`$ drill -x Your.Ip.Address\` or \`$ dig -x Your.Ip.Address\`) The following steps show how to achieve this using the acme.sh bash script and standalone HTTP authentication. These steps need to be repeated on each node where you want to use Let's Encrypt certificates. You need at least pve-manager >= 4.1-20 (see \`$ pveversion\`), so upgrade if necesasry. For some discussions and resolving non-mentioned problems see [https://forum.proxmox.com/threads/let%E2%80%99s-encrypt-with-proxmox-ve.26842/](https://forum.proxmox.com/threads/let%E2%80%99s-encrypt-with-proxmox-ve.26842/) ### Install certificate chain and key #### 0) Upgrade from le.sh to acme.sh If you followed a previous version of this HowTo using le.sh, please uninstall le.sh and proceed with "Install acme.sh": le.sh uninstall acme.sh is the 2.X release of le.sh, the existing configuration should be migrated automatically when installing acme.sh. #### 1) Install acme.sh Install the acme.sh script from [https://github.com/Neilpang/acme.sh](https://github.com/Neilpang/acme.sh) (this howto was tested with commit 2d39b3df8893cd256257fe1f32ca6b0485a90dcf): Via git: git clone [https://github.com/Neilpang/acme.sh.git](https://github.com/Neilpang/acme.sh.git) acme.sh-master Or direct download: wget '[https://github.com/Neilpang/acme.sh/archive/master.zip'](https://github.com/Neilpang/acme.sh/archive/master.zip') unzip master.zip #### 2) Run the install script You must do this from within the script's directory, otherwise it won't find acme.sh! Take care to replace $EMAIL with the address that you want to register with at Let's Encrypt. Let's Encrypt will send automatic expiration reminders to this address! mkdir /etc/pve/.le cd /root/acme.sh-master ./acme.sh --install --accountconf /etc/pve/.le/account.conf --accountkey /etc/pve/.le/account.key --accountemail "$EMAIL" After the installation, you need to close and reopen your shell (acme.sh is installed to ~/.acme.sh and sets up your shell's $PATH accordingly). #### 3) Check the account config Check the config file in /etc/pve/.le/account.conf and verify: * the ACCOUNT\_EMAIL variable should be set to your email address * the ACCOUNT\_KEY\_PATH variable should be set to "/etc/pve/.le/account.key" You can edit this file with your favourite text editor if either of those is incorrect. #### 4) Make sure port 80 is open from the public As part of the certificate creation process, acme.sh will listen for a confirmation from LetsEncrypt's servers on port 80. Check that this port is therefore not blocked by any firewall between the machine you are certifying and the public internet. You can close the port once you're done issuing all certificates for your cluster. However, be aware that as part of the certificate renewal process (managed with a cron job that acme.sh installs), port 80 must also be open. You may therefore need to work out an automated way (not covered in this guide) of opening up port 80 for the renewal process. #### 5) Issue your first certificate Now you can issue your first certificate, replacing $DOMAIN with your node's fully qualified domain: acme.sh --issue --standalone --keypath /etc/pve/local/pveproxy-ssl.key --fullchainpath /etc/pve/local/pveproxy-ssl.pem --reloadcmd "systemctl restart pveproxy" -d $DOMAIN Warnings like "cp: preserving permissions for ‘/etc/pve/local/pveproxy-ssl.pem.bak’: Function not implemented" can be safely ignored. By appending the previous command with \--test you can issue a certificate using the staging (i.e., testing) CA instead of the production CA: acme.sh --issue --standalone --keypath /etc/pve/local/pveproxy-ssl.key --fullchainpath /etc/pve/local/pveproxy-ssl.pem --reloadcmd "systemctl restart pveproxy" -d $DOMAIN --test To "upgrade" to a production certificate, you need to rerun the issue command with an appended \--force instead of \--test, in order to replace the existing (test) certificate even though it is not yet expired. This can also be used to force a premature renewal in case the node's domain name has changed: acme.sh --issue --standalone --keypath /etc/pve/local/pveproxy-ssl.key --fullchainpath /etc/pve/local/pveproxy-ssl.pem --reloadcmd "systemctl restart pveproxy" -d $DOMAIN --force #### 6\. Check it's working If necessary, close the firewall port again. The system log should inform you about the usage of the alternative SSL certificate ("Using '/etc/pve/local/pveproxy-ssl.pem' as certificate for the web interface."): journalctl -b -u pveproxy.service When accessing the web interface on this node, you should be presented with the new certificate. Note that the alternative certificate is only used by the web interface (including noVNC), but not by the Spice Console/Shell. #### 7\. Set up automatic renewal acme.sh installs a cron job that checks the installed certificate(s) and automatically renews them before they expire. The crontab entry should look like this (crontab -l): 0 0 \* \* \* "/root/.acme.sh"/acme.sh --cron --home "/root/.acme.sh" > /dev/null It's a good idea to test the cron entry by running it manually from the command line, just copy the following command (including the quotes): "/root/.acme.sh"/acme.sh --cron --home "/root/.acme.sh" NOTE: The requirements for issuing certificates apply for renewals as well: the configured domain name **must be resolvable and reachable on port 80 from the public internet when the renewal cron job runs**. ### Updating acme.sh acme.sh can be updated with the following commands when installed from the git repository: cd /root/acme.sh-master git pull ./acme.sh --install --accountconf /etc/pve/.le/account.conf --accountkey /etc/pve/.le/account.key --accountemail "YOUR@EMAIL.ADDRESS" ### Account key It is recommended to do an off-site/offline backup of the account key file in /etc/pve/.le/account.key, in case one of your certificate private key files is lost or compromised, it can be used to revoke the associated certificate. Let's Encrypt using eff.org's certbot ------------------------------------- ### Installing certbot certbot is packaged in Debian (the building base of Proxmox VE), so you may just install it with apt: apt install certbot If you run PVE 4.X (Debian Jessie) or run into any problems which are fixed by a newer version, you may enable the backports repository ( [http://backports.debian.org/Instructions/](http://backports.debian.org/Instructions/) ) and run: apt -t stretch-backports install certbot or respectively: apt -t jessie-backports install certbot ### Obtaining your certificate Just run the following command and follow the on screen output to obtain your certificate. certbot certonly ### Getting your certificate into Proxmox You need to copy the certificate from the LE directory to the PVE directory: cp /etc/letsencrypt/live//fullchain.pem /etc/pve/local/pveproxy-ssl.pem cp /etc/letsencrypt/live//privkey.pem /etc/pve/local/pveproxy-ssl.key Than restart the PVE proxy: systemctl restart pveproxy ### Setting up renewal Create a new bash script with the commands used to copy the certificate and restart the proxy from the previous step and make it executable, lets assume that you put it into /usr/local/bin/renew-pve-certs.sh Than edit your /etc/crontab with the editor your like and add the following line: 30 6 1,15 \* \* root /usr/bin/certbot renew --quiet --post-hook /usr/local/bin/renew-pve-certs.sh This will check two times each month (on the first and the 15th) at 06:30 AM if it needs to issue a new certificate. As certificates are valid for three months, this frequency should be high enough to ensure a certificate gets always renewed on time. Let's Encrypt using other Clients --------------------------------- It should also be possible to use other Let's Encrypt clients, as long as care is taken that the issued as well as renewed certificates and the associated keys are copied to the correct locations, and the pveproxy service is restarted afterwards. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=HTTPS\_Certificate\_Configuration\_(Version\_4.x,\_5.0\_and\_5.1)&oldid=10500](https://pve.proxmox.com/mediawiki/index.php?title=HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)&oldid=10500) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Proxmox VE 4.x](https://pve.proxmox.com/mediawiki/index.php?title=Category:Proxmox_VE_4.x&action=edit&redlink=1 "Category:Proxmox VE 4.x (page does not exist)") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # OpenVZ Console - Proxmox VE OpenVZ Console ============== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/OpenVZ_Console#mw-head) [Jump to search](https://pve.proxmox.com/wiki/OpenVZ_Console#searchInput) ℹ️ **Note**: Article about old Proxmox VE releases up to 3.x Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/OpenVZ_Console#Introduction) * [2 Debian 5,6,7](https://pve.proxmox.com/wiki/OpenVZ_Console#Debian_5,6,7) * [2.1 Editing the config file via the host](https://pve.proxmox.com/wiki/OpenVZ_Console#Editing_the_config_file_via_the_host) * [2.2 Editing the configuration file inside the container](https://pve.proxmox.com/wiki/OpenVZ_Console#Editing_the_configuration_file_inside_the_container) * [3 Ubuntu](https://pve.proxmox.com/wiki/OpenVZ_Console#Ubuntu) * [3.1 Ubuntu 10.04, 12.04, 14.04](https://pve.proxmox.com/wiki/OpenVZ_Console#Ubuntu_10.04,_12.04,_14.04) * [4 Centos](https://pve.proxmox.com/wiki/OpenVZ_Console#Centos) * [4.1 Centos 5 / 7](https://pve.proxmox.com/wiki/OpenVZ_Console#Centos_5_/_7) * [4.2 Centos 6](https://pve.proxmox.com/wiki/OpenVZ_Console#Centos_6) * [5 Alpine Linux](https://pve.proxmox.com/wiki/OpenVZ_Console#Alpine_Linux) * [5.1 Alpine v3.5.1](https://pve.proxmox.com/wiki/OpenVZ_Console#Alpine_v3.5.1) * [6 Troubleshooting](https://pve.proxmox.com/wiki/OpenVZ_Console#Troubleshooting) * [7 Java browser plugin](https://pve.proxmox.com/wiki/OpenVZ_Console#Java_browser_plugin) * [8 Modifying your templates](https://pve.proxmox.com/wiki/OpenVZ_Console#Modifying_your_templates) Introduction ------------ Beginning with Proxmox VE 2.2, we introduced a new console view (with login capability). Especially for beginners it is not that easy to understand and manage containers but with the new console this is big step forward. OpenVZ and KVM console now look quite similar. But as most OpenVZ templates have disabled terminals, you need to enable it first. This article describes the changes needed for an already running OpenVZ container. **Note:** All Debian templates created with latest [Debian Appliance Builder](https://pve.proxmox.com/wiki/Debian_Appliance_Builder "Debian Appliance Builder") have already got this set of changes, just download them via GUI to your Proxmox VE storage (Debian 6 and 7 templates are up2date, 32 and 64 bit) Debian 5,6,7 ------------ This will also work in debian8 if you use sysv-init instead of systemd ### Editing the config file via the host You can do this on the host without entering CT (but the CT must be running). Just log in to the Proxmox VE host and: edit all inittabs under /var/lib/vz/root/ : nano /var/lib/vz/root/\*/etc/inittab # add this 1:2345:respawn:/sbin/getty 38400 tty1 ### Editing the configuration file inside the container [![](https://pve.proxmox.com/mediawiki/images/thumb/b/b8/Screen-Debian-5-OpenVZ-console.png/600px-Screen-Debian-5-OpenVZ-console.png)](https://pve.proxmox.com/wiki/File:Screen-Debian-5-OpenVZ-console.png) Login via SSH (or use the VNC "Shell") to your Proxmox VE host and 'vzctl enter CTID' the container: List all running container: proxmox-ve:~# vzlist CTID NPROC STATUS IP\_ADDR HOSTNAME 108 23 running 192.168.9.20 ubuntu-1204.proxmox.com 109 18 running 192.168.9.21 centos63-64.proxmox.com 111 15 running 192.168.9.23 centos5-64.proxmox.com 114 14 running 192.168.9.30 deb6-32.proxmox.com 115 15 running 192.168.9.31 deb7-32.proxmox.com 122 14 running 192.168.9.36 deb5.proxmox.com Enter the container: proxmox-ve:~# vzctl enter 122 root@debian:/# nano /etc/inittab On the bottom of /etc/inittab just add the following line: 1:2345:respawn:/sbin/getty 38400 tty1 Save the changes and shutdown/start the container via Console. Ubuntu ------ ### Ubuntu 10.04, 12.04, 14.04 [![](https://pve.proxmox.com/mediawiki/images/thumb/9/99/Screen-Ubuntu-12.04-OpenVZ-console.png/600px-Screen-Ubuntu-12.04-OpenVZ-console.png)](https://pve.proxmox.com/wiki/File:Screen-Ubuntu-12.04-OpenVZ-console.png) Works for Ubuntu 16.04 if [_systemd_ is replaced with _SysV init_](http://without-systemd.org/wiki/index.php/How_to_remove_systemd_from_an_Ubuntu_Xenial_installation) . Login via SSH (or use the VNC "Shell") to your Proxmox VE host and 'vzctl enter CTID' the container: List all running container: proxmox-ve:~# vzlist CTID NPROC STATUS IP\_ADDR HOSTNAME 108 23 running 192.168.9.20 ubuntu-1404.proxmox.com 109 18 running 192.168.9.21 centos63-64.proxmox.com 111 15 running 192.168.9.23 centos5-64.proxmox.com 114 14 running 192.168.9.30 deb6-32.proxmox.com 115 15 running 192.168.9.31 deb7-32.proxmox.com 122 14 running 192.168.9.36 deb5.proxmox.com Enter the container: proxmox-ve:~# vzctl enter 108 root@ubuntu-1404:/# nano /etc/init/tty1.conf Change/Create the file that it looks exactly like this: \# tty1 - getty # # This service maintains a getty on tty1 from the point the system is # started until it is shut down again. start on stopped rc RUNLEVEL=\[2345\] stop on runlevel \[!2345\] respawn exec /sbin/getty -8 38400 tty1 Save the changes and shutdown/start the container via Console. Centos ------ ### Centos 5 / 7 [![](https://pve.proxmox.com/mediawiki/images/thumb/9/9d/Screen-Centos-5-OpenVZ-console.png/600px-Screen-Centos-5-OpenVZ-console.png)](https://pve.proxmox.com/wiki/File:Screen-Centos-5-OpenVZ-console.png) Login via SSH (or use the VNC "Shell") to your Proxmox VE host and 'vzctl enter CTID' the container: List all running container: proxmox-ve:~# vzlist CTID NPROC STATUS IP\_ADDR HOSTNAME 108 23 running 192.168.9.20 ubuntu-1204.proxmox.com 109 18 running 192.168.9.21 centos63-64.proxmox.com 111 15 running 192.168.9.23 centos5-64.proxmox.com 114 14 running 192.168.9.30 deb6-32.proxmox.com 115 15 running 192.168.9.31 deb7-32.proxmox.com 122 14 running 192.168.9.36 deb5.proxmox.com Enter the container: proxmox-ve:~# vzctl enter 111 root@centos5-64:/# nano /etc/inittab On the bottom of /etc/inittab just add the following line: 1:2345:respawn:/sbin/agetty tty1 38400 linux Save the changes and shutdown/start the container via Console. ### Centos 6 [![](https://pve.proxmox.com/mediawiki/images/thumb/3/3e/Screen-Centos-6-OpenVZ-console.png/600px-Screen-Centos-6-OpenVZ-console.png)](https://pve.proxmox.com/wiki/File:Screen-Centos-6-OpenVZ-console.png) Login via SSH (or use the VNC "Shell") to your Proxmox VE host and 'vzctl enter CTID' the container: List all running container: proxmox-ve:~# vzlist CTID NPROC STATUS IP\_ADDR HOSTNAME 108 23 running 192.168.9.20 ubuntu-1204.proxmox.com 109 18 running 192.168.9.21 centos63-64.proxmox.com 111 15 running 192.168.9.23 centos5-64.proxmox.com 114 14 running 192.168.9.30 deb6-32.proxmox.com 115 15 running 192.168.9.31 deb7-32.proxmox.com 122 14 running 192.168.9.36 deb5.proxmox.com Enter the container: proxmox-ve:~# vzctl enter 109 root@centos63-64:/# nano /etc/init/tty.conf Change/Create the file that it looks exactly like this: \# This service maintains a getty on tty1 from the point the system is # started until it is shut down again. start on stopped rc RUNLEVEL=\[2345\] stop on runlevel \[!2345\] respawn exec /sbin/agetty -8 tty1 38400 Either run "start tty" without rebooting the container, or save the changes and shutdown/start the container via Console. Alpine Linux ------------ ### Alpine v3.5.1 [![](https://pve.proxmox.com/mediawiki/images/thumb/0/0d/Screen-AlpineLinux-3.5.1-OpenVZ-console.png/600px-Screen-AlpineLinux-3.5.1-OpenVZ-console.png)](https://pve.proxmox.com/wiki/File:Screen-AlpineLinux-3.5.1-OpenVZ-console.png) The /etc/inittab should have: \# START ------------------------------------- ::sysinit:/sbin/openrc sysinit ::sysinit:/sbin/openrc boot ::wait:/sbin/openrc default \# Set up a couple of getty's #tty1::respawn:/sbin/getty 38400 tty1 #tty2::respawn:/sbin/getty 38400 tty2 #tty3::respawn:/sbin/getty 38400 tty3 #tty4::respawn:/sbin/getty 38400 tty4 #tty5::respawn:/sbin/getty 38400 tty5 #tty6::respawn:/sbin/getty 38400 tty6 \# Put a getty on the serial port #ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100 \# Stuff to do for the 3-finger salute ::ctrlaltdel:/sbin/reboot \# Stuff to do before rebooting ::shutdown:/sbin/openrc shutdown 1:2345:respawn:/sbin/getty 38400 console 2:2345:respawn:/sbin/getty 38400 tty2 \# END --------------------------------------- Note that the last 2 lines are not commented out. On reboot, this will bloat the file /var/log/messages with errors like: Feb 6 17:47:38 test daemon.info init: can't open /dev/1: No such file or directory Feb 6 17:47:38 test daemon.info init: can't open /dev/2: No such file or directory Feb 6 17:47:39 test daemon.info init: process '/sbin/getty 38400 console' (pid 770) exited. Scheduling for restart. Feb 6 17:47:39 test daemon.info init: process '/sbin/getty 38400 tty2' (pid 771) exited. Scheduling for restart. This is [remedied](https://lennartb.home.xs4all.nl/rescuedisk/node7.html) with: mknod /dev/1 c 4 1 mknod /dev/2 c 4 2 mknod /dev/tty2 c 4 2 rm /dev/tty1 > /var/log/messages On reboot, and a NoVNC login and logout will populate the /var/log/messages with just: Feb 6 17:47:39 test daemon.info init: starting pid 774, tty '/dev/1': '/sbin/getty 38400 console' Feb 6 17:47:50 test daemon.info init: starting pid 797, tty '/dev/2': '/sbin/getty 38400 tty2' Feb 6 17:51:50 test auth.info login\[1016\]: root login on 'console' Feb 6 17:51:54 test daemon.info init: process '/sbin/getty 38400 console' (pid 774) exited. Scheduling for restart. Feb 6 17:51:54 test daemon.info init: starting pid 1022, tty '/dev/1': '/sbin/getty 38400 console' The above assumes that the last line of /etc/vz/dists/[alpine.conf](https://src.openvz.org/projects/OVZL/repos/vzctl/browse/etc/dists/alpine.conf?at=vzctl-4.9) is: SET\_CONSOLE=set\_console.sh where the /etc/vz/dists/scripts/[set\_console.sh](http://code.metager.de/source/xref/openvz/vzctl/etc/dists/scripts/set_console.sh) has: #!/bin/sh \# Copyright (C) 2012-2014, Parallels, Inc. All rights reserved. # \# This program is free software; you can redistribute it and/or modify \# it under the terms of the GNU General Public License as published by \# the Free Software Foundation; either version 2 of the License, or \# (at your option) any later version. # \# This program is distributed in the hope that it will be useful, \# but WITHOUT ANY WARRANTY; without even the implied warranty of \# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the \# GNU General Public License for more details. # \# You should have received a copy of the GNU General Public License \# along with this program; if not, write to the Free Software \# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA # # \# Configures getty in a container on /dev/tty1 (aka /dev/console) \# and /dev/tty2. Invoked during vzctl start. Needed for vzctl console. if \[ \-x /lib/systemd/systemd \]; then SYSTEMD\_DIR\=/lib/systemd/system else SYSTEMD\_DIR\=/usr/lib/systemd/system fi ETC\_SYSTEMD\_DIR\="/etc/systemd/system" SYSTEMD\_GETTY\_SERVICE\=$SYSTEMD\_DIR/getty@.service create\_dev() { local dev\=$1 local major\=$2 local minor\=$3 if \[ ! \-c /dev/$dev \-o \-L /dev/$dev \]; then rm \-f /dev/$dev 2\>/dev/null mknod /dev/$dev c $major $minor fi } fix\_shell\_console() { \[ \-f $SYSTEMD\_DIR/console-getty.service \] && return 0 echo '# This file is part of systemd. # \# systemd is free software; you can redistribute it and/or modify it \# under the terms of the GNU General Public License as published by \# the Free Software Foundation; either version 2 of the License, or \# (at your option) any later version. \[Unit\] Description=Console Shell After=systemd-user-sessions.service plymouth-quit-wait.service Before=getty.target \[Service\] Environment=HOME=/root WorkingDirectory=/root ExecStart=-/sbin/agetty --noclear -s console 115200,38400,9600 Restart=always RestartSec=0 UtmpIdentifier=cons TTYPath=/dev/console TTYReset=yes TTYVHangup=yes StandardInput=tty-force StandardOutput=inherit StandardError=inherit KillMode=process \# Bash ignores SIGTERM, so we send SIGHUP instead, to ensure that bash \# terminates cleanly. KillSignal=SIGHUP \[Install\] WantedBy=getty.target' \> $SYSTEMD\_DIR/console-getty.service rm \-f $SYSTEMD\_DIR/console-shell.service } setup\_systemd\_console() { if grep \-q \-e 'ConditionPathExists=!/run/openvz' \\ \-e 'ConditionPathExists=!/proc/vz' $SYSTEMD\_GETTY\_SERVICE 2\>/dev/null; then sed \-i \-e '/ConditionPathExists=!\\/run\\/openvz/d' \\ \-e '/ConditionPathExists=!\\/proc\\/vz/d' $SYSTEMD\_GETTY\_SERVICE fi \[ \-L $SYSTEMD\_DIR/getty.target.wants/getty@tty1.service \] && \\ rm \-f $SYSTEMD\_DIR/getty.target.wants/getty@tty1.service \[ \-L $ETC\_SYSTEMD\_DIR/getty.target.wants/getty@tty1.service \] && \\ rm \-f $ETC\_SYSTEMD\_DIR/getty.target.wants/getty@tty1.service \[ \-L $SYSTEMD\_DIR/getty.target.wants/getty@tty2.service \] || \\ ln \-sf $SYSTEMD\_DIR/getty@.service $ETC\_SYSTEMD\_DIR/getty.target.wants/getty@tty2.service \[ \-f $SYSTEMD\_DIR/console-shell.service \] && fix\_shell\_console } setup\_upstart\_console() { local file\=/etc/init/$1.conf local getty if \[ \-x /sbin/mingetty \]; then getty\='exec /sbin/mingetty' elif \[ \-x /sbin/getty \]; then getty\='exec /sbin/getty 38400' else echo "Unable to find suitable getty, console setup is skipped" return 0 fi echo "start on stopped rc RUNLEVEL=\[2345\] stop on runlevel \[!2345\] respawn $getty $1" \> $file } setup\_upstart\_event\_console() { local file\=/etc/init.d/$1 local getty if \[ \-x /sbin/mingetty \]; then getty\='exec /sbin/mingetty' elif \[ \-x /sbin/getty \]; then getty\='exec /sbin/getty 38400' else echo "Unable to find suitable getty console setup is skipped" return 0 fi echo "start on stopped rc2 start on stopped rc3 start on stopped rc4 stop on runlevel 0 stop on runlevel 1 stop on runlevel 6 $getty $1" \> $file } setup\_inittab() { local line local getty1 local getty2 if \[ \-x /sbin/mingetty \]; then getty1\='/sbin/mingetty console' getty2\='/sbin/mingetty tty2' elif \[ \-x /sbin/getty \]; then getty1\='/sbin/getty 38400 console' getty2\='/sbin/getty 38400 tty2' elif \[ \-x /sbin/agetty \]; then getty1\='/sbin/agetty console 38400' getty2\='/sbin/agetty tty2 38400' else echo "Unable to find suitable getty, console setup is skipped" return 0 fi line\="1:2345:respawn:$getty1" if ! grep \-q "$line" /etc/inittab; then echo $line \>> /etc/inittab fi line\="2:2345:respawn:$getty2" if ! grep \-q "$line" /etc/inittab; then echo $line \>> /etc/inittab fi } setup\_console() { if \[ \-f "$SYSTEMD\_GETTY\_SERVICE" \]; then setup\_systemd\_console elif \[ \-d '/etc/init' \]; then setup\_upstart\_console console setup\_upstart\_console tty2 elif \[ \-d "/etc/event.d" \]; then setup\_upstart\_event\_console console setup\_upstart\_event\_console tty2 elif \[ \-f "/etc/inittab" \]; then setup\_inittab fi create\_dev console 5 1 create\_dev tty2 4 2 } setup\_console exit 0 Troubleshooting --------------- If you still want to use the previous method (vzctl enter CTID) you can open the host **Shell** and just type _vzctl enter CTID_ to manage your containers. Java browser plugin ------------------- The console is using a Java applet, therefore you need latest Oracle (Sun) Java browser plugin installed and enabled in your browser (Google Chrome and Firefox preferred). If you are on Windows desktop, just go to java.com, if you run a Linux desktop you need to make sure that you run Oracle (Sun) Java plugin instead of the default openjdk. For Debian/Ubuntu based desktops, see [Java\_Console\_(Ubuntu)](https://pve.proxmox.com/wiki/Java_Console_(Ubuntu) "Java Console (Ubuntu)") Modifying your templates ------------------------ If you don't want to commit the changes above for every single CT you create, you can simply update the templates accordingly. For this, simply place the file you want to insert into your template (like etc/inittab for debian containers) into your template folder and update the template. The following is specific to CentOS 6, just replace filename/path and contents with the appropriate contents found above. cd \[TEMPLATE LOCATION\] #Modify this mkdir -p etc/init cat <etc/init/tty.conf # This service maintains a getty on tty1 from the point the system is # started until it is shut down again. start on stopped rc RUNLEVEL=\[2345\] stop on runlevel \[!2345\] respawn exec /sbin/agetty -8 tty1 38400 EOF gunzip centos-6-standard\_6.3-1\_amd64.tar.gz tar -rf centos-6-standard\_6.3-1\_amd64.tar etc gzip centos-6-standard\_6.3-1\_amd64.tar rm etc/init/tty.conf rmdir -p etc/init | Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=OpenVZ\_Console&oldid=10444](https://pve.proxmox.com/mediawiki/index.php?title=OpenVZ_Console&oldid=10444) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Pages using deprecated source tags](https://pve.proxmox.com/mediawiki/index.php?title=Category:Pages_using_deprecated_source_tags&action=edit&redlink=1 "Category:Pages using deprecated source tags (page does not exist)") * [Proxmox VE 3.x](https://pve.proxmox.com/wiki/Category:Proxmox_VE_3.x "Category:Proxmox VE 3.x") * [Archive](https://pve.proxmox.com/wiki/Category:Archive "Category:Archive") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # High Availability Cluster - Proxmox VE High Availability Cluster ========================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/High_Availability_Cluster#mw-head) [Jump to search](https://pve.proxmox.com/wiki/High_Availability_Cluster#searchInput) ℹ️ **Note**: This article is about the old stable Proxmox VE 3.x releases. See [High Availability](https://pve.proxmox.com/wiki/High_Availability "High Availability") for the current release. Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/High_Availability_Cluster#Introduction) * [1.1 Update to the latest version](https://pve.proxmox.com/wiki/High_Availability_Cluster#Update_to_the_latest_version) * [2 System requirements](https://pve.proxmox.com/wiki/High_Availability_Cluster#System_requirements) * [3 HA Configuration](https://pve.proxmox.com/wiki/High_Availability_Cluster#HA_Configuration) * [3.1 Fencing](https://pve.proxmox.com/wiki/High_Availability_Cluster#Fencing) * [3.2 Configure VM or Containers for HA](https://pve.proxmox.com/wiki/High_Availability_Cluster#Configure_VM_or_Containers_for_HA) * [3.2.1 Enable a KVM VM or a Container for HA](https://pve.proxmox.com/wiki/High_Availability_Cluster#Enable_a_KVM_VM_or_a_Container_for_HA) * [3.3 HA Cluster maintenance (node reboots)](https://pve.proxmox.com/wiki/High_Availability_Cluster#HA_Cluster_maintenance_(node_reboots)) * [4 Video Tutorials](https://pve.proxmox.com/wiki/High_Availability_Cluster#Video_Tutorials) * [5 Certified Configurations and Examples](https://pve.proxmox.com/wiki/High_Availability_Cluster#Certified_Configurations_and_Examples) * [6 Testing](https://pve.proxmox.com/wiki/High_Availability_Cluster#Testing) * [6.1 Useful command line tools](https://pve.proxmox.com/wiki/High_Availability_Cluster#Useful_command_line_tools) Introduction ------------ Proxmox VE High Availability Cluster (Proxmox VE HA Cluster) enables the definition of high available virtual machines. In simple words, if a virtual machine (VM) is configured as HA and the physical host fails, the VM is automatically restarted on one of the remaining Proxmox VE Cluster nodes. The Proxmox VE HA Cluster is based on proven Linux HA technologies, providing stable and reliable HA service. [![Screen-HA-status](https://pve.proxmox.com/mediawiki/images/6/6d/Screen-HA-status.png)](https://pve.proxmox.com/wiki/File:Screen-HA-status.png "Screen-HA-status") ### Update to the latest version Before you start, make sure you have installed the latest packages, just run this on all nodes: apt-get update && apt-get dist-upgrade System requirements ------------------- If you run HA, only high end server hardware with no single point of failure should be used. This includes redundant disks (Hardware Raid), redundant power supply, UPS systems, network bonding. * [Fencing](https://pve.proxmox.com/wiki/Fencing "Fencing") device(s) - reliable and TESTED! **NOTE:** this is NEEDED, **there isn't software fencing**. * Fully configured [Proxmox\_VE\_2.0\_Cluster](https://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster "Proxmox VE 2.0 Cluster") (version 2.0 and later), with at least 3 nodes (maximum supported configuration: currently 16 nodes per cluster). Note that, with certain limitations, 2-node configuration is also possible ([Two-Node High Availability Cluster](https://pve.proxmox.com/wiki/Two-Node_High_Availability_Cluster "Two-Node High Availability Cluster") ). * Shared storage (SAN or NAS/NFS for Virtual Disk Image Store for HA KVM) * Reliable, redundant network, suitable configured * A extra network for Cluster communication, one network for VM traffic and one network for Storage traffic. * NFS for Containers It is essential that you use redundant network connections for the cluster communication (bonding). Else a simple switch reboot (or power loss on the switch) can lock all HA nodes (see [bug #105](http://bugzilla.proxmox.com/show_bug.cgi?id=105) ) HA Configuration ---------------- Adding and managing VM´s and containers for HA should be done via GUI. The configuration of fence devices is CLI only. ### Fencing Fencing is an essential part for Proxmox VE HA (version 2.0 and later), without fencing, HA will not work. REMEMBER: you NEED at least a fencing device for every node. Detailed steps to configure and test fencing can be found [here](https://pve.proxmox.com/wiki/Fencing "Fencing") . ### Configure VM or Containers for HA Review again if you have everything you need and if all systems are running reliable. It makes no sense to configure HA cluster setup on unreliable hardware. * See [High\_Availability\_Cluster#System\_requirements](https://pve.proxmox.com/wiki/High_Availability_Cluster#System_requirements) #### Enable a KVM VM or a Container for HA See also the video tutorial on [Proxmox VE Youtube channel](http://www.youtube.com/user/ProxmoxVE) **Note**: Make sure that the VMs or CTs are not running when you add them to HA. [![Screen-Add-HA-managed_VM-CT](https://pve.proxmox.com/mediawiki/images/8/8d/Screen-Add-HA-managed_VM-CT.png)](https://pve.proxmox.com/wiki/File:Screen-Add-HA-managed_VM-CT.png "Screen-Add-HA-managed_VM-CT") [![Screen-Show-HA-managed_VM-CT](https://pve.proxmox.com/mediawiki/images/1/14/Screen-Show-HA-managed_VM-CT.png)](https://pve.proxmox.com/wiki/File:Screen-Show-HA-managed_VM-CT.png "Screen-Show-HA-managed_VM-CT") ### HA Cluster maintenance (node reboots) If you need to reboot a node, e.g. because of a kernel update you need to stop rgmanager. By doing this, all resources are stopped and moved to other nodes. All KVM guests will get a ACPI shutdown request (if this does not work due to VM internal setting just a 'stop'). You can stop the rgmanager service via GUI or just run: /etc/init.d/rgmanager stop The command will take a while, monitor the "tasks" and the VM´s and CT´s on the GUI. as soon as the rgmanager is stopped, you can reboot your node. as soon as the node is up again, continue with the next node and so on. Video Tutorials --------------- [Proxmox VE Youtube channel](http://www.youtube.com/user/ProxmoxVE) Certified Configurations and Examples ------------------------------------- * [Intel Modular Server HA](https://pve.proxmox.com/mediawiki/index.php?title=Intel_Modular_Server_HA&action=edit&redlink=1 "Intel Modular Server HA (page does not exist)") * tbe Testing ------- Before going in production do as many tests as possible. ### Useful command line tools Here is a list of useful CLI tools: * clustat - Cluster Status Utility * clusvcadm - Cluster User Service Administration Utility * ccs\_config\_validate - validate cluster.conf file * fence\_tool - a utility for the fenced daemon * fence\_node - a utility to run fence agents * fence\_ack\_manual - a utility to manually manage fencing using /bin/false Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=High\_Availability\_Cluster&oldid=10466](https://pve.proxmox.com/mediawiki/index.php?title=High_Availability_Cluster&oldid=10466) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Archive](https://pve.proxmox.com/wiki/Category:Archive "Category:Archive") * [Proxmox VE 3.x](https://pve.proxmox.com/wiki/Category:Proxmox_VE_3.x "Category:Proxmox VE 3.x") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Troubleshooting - Proxmox VE Troubleshooting =============== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Troubleshooting#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Troubleshooting#searchInput) Contents -------- * [1 Switch novnc KVM console](https://pve.proxmox.com/wiki/Troubleshooting#Switch_novnc_KVM_console) * [2 How can I send sysrq to Linux KVM guests?](https://pve.proxmox.com/wiki/Troubleshooting#How_can_I_send_sysrq_to_Linux_KVM_guests?) * [3 How can I access Linux guests through a serial terminal](https://pve.proxmox.com/wiki/Troubleshooting#How_can_I_access_Linux_guests_through_a_serial_terminal) * [4 How can I assign a physical disk to a VM?](https://pve.proxmox.com/wiki/Troubleshooting#How_can_I_assign_a_physical_disk_to_a_VM?) * [5 How can I assign a physical disk to a CT?](https://pve.proxmox.com/wiki/Troubleshooting#How_can_I_assign_a_physical_disk_to_a_CT?) * [6 "error: out of partition" after a fresh install](https://pve.proxmox.com/wiki/Troubleshooting#%22error:_out_of_partition%22_after_a_fresh_install) * [7 NFS Client Mount Error: "mount.nfs: No such device"](https://pve.proxmox.com/wiki/Troubleshooting#NFS_Client_Mount_Error:_%22mount.nfs:_No_such_device%22) Switch novnc KVM console ------------------------ I can't switch virtual consoles in Linux KVM guests with alt-F1, alt-F2... VNC viewer does not pass some key combinations or they may be intercepted by your operating system. To send custom key combinations to the guest, go to "Monitor" in Virtual Machine Configuration for a given guest and use "sendkey" command. For example, to switch to the third console (tty3) you would use: sendkey alt-f3 How can I send sysrq to Linux KVM guests? ----------------------------------------- Similarly to the above, go to "Monitor" in Virtual Machine Configuration for a given guest and use "sendkey" command. For example, to issue "Emergency Sync", you would use: sendkey alt-sysrq-s In the VNC viewer for the given guest you should see: SysRq : Emergency Sync You should also see this entry if you run "dmesg" on this guest. See also [http://en.wikipedia.org/wiki/Magic\_SysRq\_key](http://en.wikipedia.org/wiki/Magic_SysRq_key) for a full reference of possible combinations. How can I access Linux guests through a serial terminal ------------------------------------------------------- See [Serial Terminal](https://pve.proxmox.com/wiki/Serial_Terminal "Serial Terminal") How can I assign a physical disk to a VM? ----------------------------------------- You don't have to do anything at host level (i.e. not add to fstab or anything), just set is as available directly to the KVM guest: qm set -ide# /dev/sdb Or: qm set -ide# /dev/disk/by-id/\[your disk ID\] ...since having the drive letter change (should you add a drive) might have unintended consequences. Also see /etc/qemu-server/.conf if you want to add it editing the conf file by hand (i.e. adding ide1: /dev/sdb2). After that you can run the VM as usual, and you will have the new storage device available inside it. Beware that you can't assign it to more than one running VM if the filesystem is not designed for such scenario. How can I assign a physical disk to a CT? ----------------------------------------- ℹ️ **Note**: Article about the stable Proxmox VE 4.x releases See [Linux\_Container](https://pve.proxmox.com/wiki/Linux_Container#pct_container_storage "Linux Container") ℹ️ **Note**: Article about the old stable Proxmox VE 3.x releases See [http://wiki.openvz.org/Bind\_mounts](http://wiki.openvz.org/Bind_mounts) "error: out of partition" after a fresh install ----------------------------------------------- The error message below may happens when you had two or more harddrives connected during the installation. Try to disconnect all but one disk. error: out of partition. grub rescue> NFS Client Mount Error: "mount.nfs: No such device" --------------------------------------------------- ℹ️ **Note**: Article about the old stable Proxmox VE 3.x releases By default NFS cannot be mounted in VZ containers. See this page to set-it-up: [OpenVZ: NFS](http://wiki.openvz.org/NFS) See also this page to make an host's directory visible to a container: [OpenVZ: Bind mounts](http://wiki.openvz.org/Bind_mounts) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Troubleshooting&oldid=9511](https://pve.proxmox.com/mediawiki/index.php?title=Troubleshooting&oldid=9511) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Troubleshooting](https://pve.proxmox.com/wiki/Category:Troubleshooting "Category:Troubleshooting") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Storage: ZFS over ISCSI - Proxmox VE Storage: ZFS over ISCSI ======================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Storage:_ZFS_over_ISCSI#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Storage:_ZFS_over_ISCSI#searchInput) Storage pool type: zfs This backend accesses a remote machine having a ZFS pool as storage and an iSCSI target implementation via ssh. For each guest disk it creates a ZVOL and, exports it as iSCSI LUN. This LUN is used by Proxmox VE for the guest disk. The following iSCSI target implementations are supported: * LIO (Linux) * IET (Linux) * ISTGT (FreeBSD) * Comstar (Solaris) | | | | --- | --- | | ![Note]() | This plugin needs a ZFS capable remote storage appliance, you cannot use it to create a ZFS Pool on a regular Storage Appliance/SAN | Configuration ------------- In order to use the ZFS over iSCSI plugin you need to configure the remote machine (target) to accept ssh connections from the Proxmox VE node. Proxmox VE connects to the target for creating the ZVOLs and exporting them via iSCSI. Authentication is done through a ssh-key (without password protection) stored in /etc/pve/priv/zfs/\_id\_rsa The following steps create a ssh-key and distribute it to the storage machine with IP 192.0.2.1: mkdir /etc/pve/priv/zfs ssh-keygen -f /etc/pve/priv/zfs/192.0.2.1\_id\_rsa ssh-copy-id -i /etc/pve/priv/zfs/192.0.2.1\_id\_rsa.pub root@192.0.2.1 ssh -i /etc/pve/priv/zfs/192.0.2.1\_id\_rsa root@192.0.2.1 The backend supports the common storage properties content, nodes, disable, and the following ZFS over ISCSI specific properties: pool The ZFS pool/filesystem on the iSCSI target. All allocations are done within that pool. portal iSCSI portal (IP or DNS name with optional port). target iSCSI target. iscsiprovider The iSCSI target implementation used on the remote machine comstar\_tg target group for comstar views. comstar\_hg host group for comstar views. lio\_tpg target portal group for Linux LIO targets nowritecache disable write caching on the target blocksize Set ZFS blocksize parameter. sparse Use ZFS thin-provisioning. A sparse volume is a volume whose reservation is not equal to the volume size. Configuration Examples (/etc/pve/storage.cfg) zfs: lio blocksize 4k iscsiprovider LIO pool tank portal 192.0.2.111 target iqn.2003-01.org.linux-iscsi.lio.x8664:sn.xxxxxxxxxxxx content images lio\_tpg tpg1 sparse 1 zfs: solaris blocksize 4k target iqn.2010-08.org.illumos:02:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:tank1 pool tank iscsiprovider comstar portal 192.0.2.112 content images zfs: freebsd blocksize 4k target iqn.2007-09.jp.ne.peach.istgt:tank1 pool tank iscsiprovider istgt portal 192.0.2.113 content images zfs: iet blocksize 4k target iqn.2001-04.com.example:tank1 pool tank iscsiprovider iet portal 192.0.2.114 content images Storage Features ---------------- The ZFS over iSCSI plugin provides a shared storage, which is capable of snapshots. You need to make sure that the ZFS appliance does not become a single point of failure in your deployment. | | | | | | | --- | --- | --- | --- | --- |Table 1. Storage features for backend iscsi | Content types | Image formats | Shared | Snapshots | Clones | | --- | --- | --- | --- | --- | | images | raw | yes | yes | no | See Also -------- * [Legacy: ZFS over iSCSI](https://pve.proxmox.com/wiki/Legacy:_ZFS_over_iSCSI) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Storage:\_ZFS\_over\_ISCSI&oldid=11954](https://pve.proxmox.com/mediawiki/index.php?title=Storage:_ZFS_over_ISCSI&oldid=11954) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Reference Documentation](https://pve.proxmox.com/wiki/Category:Reference_Documentation "Category:Reference Documentation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Two-Factor Authentication - Proxmox VE Two-Factor Authentication ========================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Two-Factor_Authentication#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Two-Factor_Authentication#searchInput) For a general overview of Two Factor authentication in PVE see the [corresponding User Management section](https://pve.proxmox.com/wiki/User_Management#_two_factor_authentication "User Management") . For a complete step-by-step guide to setup OATH OTP two-factor authentication (2FA) see [Two Factor Authentication section of our Documentation](https://pve.proxmox.com/pve-docs/pve-admin-guide.html#pveum_tfa_auth) . For a demonstration setup for Yubico OTP see [the YubiKey article](https://pve.proxmox.com/wiki/YubiKey "YubiKey") . Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Two-Factor\_Authentication&oldid=10495](https://pve.proxmox.com/mediawiki/index.php?title=Two-Factor_Authentication&oldid=10495) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Proxmox Datacenter Manager Upgrade from Alpha to 1 - Proxmox VE Proxmox Datacenter Manager Upgrade from Alpha to 1 ================================================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1#Introduction) * [2 In-Place Upgrade](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1#In-Place_Upgrade) * [2.1 Prerequisites](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1#Prerequisites) * [2.2 Actions Step-by-Step](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1#Actions_Step-by-Step) * [2.2.1 Continuously use the pdmAtoB Checklist Script](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1#Continuously_use_the_pdmAtoB_Checklist_Script) * [2.2.2 Update the Configured APT Repositories](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1#Update_the_Configured_APT_Repositories) * [2.2.2.1 Ensure Repository Archive Keyring is Installed](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1#Ensure_Repository_Archive_Keyring_is_Installed) * [2.2.2.2 Update Debian Base Repositories to Trixie](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1#Update_Debian_Base_Repositories_to_Trixie) * [2.2.2.3 Add the Proxmox Datacenter Manager 1 Package Repository](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1#Add_the_Proxmox_Datacenter_Manager_1_Package_Repository) * [2.2.3 Upgrade the System](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1#Upgrade_the_System) * [2.2.4 Check Result & Reboot Into Updated Kernel](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1#Check_Result_&_Reboot_Into_Updated_Kernel) * [2.3 Following the Proxmox Datacenter Manager Upgrade](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1#Following_the_Proxmox_Datacenter_Manager_Upgrade) * [2.3.1 Check Status of Services](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1#Check_Status_of_Services) * [2.3.2 Optional: Modernize APT Repository Sources](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1#Optional:_Modernize_APT_Repository_Sources) * [3 Potential Issues](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1#Potential_Issues) * [3.1 Older Hardware and New 6.14 Kernel](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1#Older_Hardware_and_New_6.14_Kernel) * [3.2 Network Interface Name Changes](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1#Network_Interface_Name_Changes) * [3.3 Systemd-Boot Meta-Package Changes the Bootloader Configuration Automatically and Should Be Uninstalled](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1#Systemd-Boot_Meta-Package_Changes_the_Bootloader_Configuration_Automatically_and_Should_Be_Uninstalled) Introduction ============ Proxmox Datacenter Manager Beta is based on Debian 13 Trixie, a new major release, and introduces several new major features and changes. You should plan the upgrade carefully, **make and verify backups** before beginning, and test extensively. Depending on the existing configuration, several manual steps — including some downtime — may be required. **Note:** A valid and tested backup is _always_ required before starting the upgrade process. You can test the backup beforehand, for example, in a (virtualized) test lab setup. In case the system is customized and/or uses additional packages or any other third party repositories/packages, ensure those packages are also upgraded to and compatible with Debian Trixie. In-Place Upgrade ================ Prerequisites ------------- * Perform these actions via SSH, a physical console or a remote management console like iKVM or IPMI. * If you use SSH, you should use a terminal multiplexer (for example, tmux or screen) to ensure the upgrade can continue even if the SSH connection gets interrupted. * Do not carry out the upgrade via the web UI console directly, as this will get interrupted during the upgrade. * Upgraded to the latest version of Proxmox Datacenter Manager Alpha, see the [roadmap](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap "Proxmox Datacenter Manager Roadmap") for potential important changes in the stable release. Use `apt update` and `apt dist-upgrade` (still with Debian Bookworm repos setup) to upgrade to the latest Alpha release * Verify version: The command `proxmox-datacenter-manager-admin versions` should print: `proxmox-datacenter-manager 0.1.12 running version: 0.1.12` (or higher) Note: The last command has only been introduced in Proxmox Datacenter Manager version 0.1.12, so if the above command fails, you are not running a new enough version. You should upgrade to that first. * If you do not get updates, check that your [package repositories](https://pve.proxmox.com/wiki/Package_Repositories#_debian_base_repositories "Package Repositories") configuration is correct. * Make a backup of `/etc/proxmox-datacenter-manager` to ensure that in the worst case, any relevant configuration can be recovered: tar czf "pdm-alpha-etc-backup-$(date -I).tar.gz" -C "/etc" "proxmox-datacenter-manager" * Ensure that you have at least 10 GB free disk space on the root mount point: df -h / In-place upgrades are carried out via APT. Basic familiarity with APT is required to proceed with this upgrade mechanism. Actions Step-by-Step -------------------- Before starting the upgrade process, ensure that your Proxmox Datacenter Manager host is up-to-date. ### Continuously use the pdmAtoB Checklist Script A small checklist program named pdmAtoB is included in the latest Proxmox Datacenter Manager Alpha packages. The program will provide hints and warnings about potential issues before, during and after the upgrade process. You can call it by executing: pdmAtoB This script only checks and reports things. By default, no changes to the system are made and thus, none of the issues will be automatically fixed. You should keep in mind that Proxmox Datacenter Manager can be heavily customized, so the script may not recognize all the possible problems with a particular setup! It is recommended to re-run the script after each attempt to fix an issue. This ensures that the actions taken actually fixed the respective warning. ### Update the Configured APT Repositories First, make sure that the system is using the latest Proxmox Datacenter Manager packages: apt update apt dist-upgrade proxmox-datacenter-manager-admin versions The last command should report a version of at least `0.1.12` or newer. #### Ensure Repository Archive Keyring is Installed To ensure your system trusts the new APT archive keyring for our Debian Trixie-based releases, install the `proxmox-archive-keyring` package before switching the repos to Trixie. apt install proxmox-archive-keyring #### Update Debian Base Repositories to Trixie Update all repository entries to Trixie: sed -i 's/bookworm/trixie/g' /etc/apt/sources.list Ensure that there are no remaining Debian Bookworm specific repositories left. Check all files in the /etc/apt/sources.list.d/ folder (like `pbs-enterprise.list`) and also the top-level `/etc/apt/sources.list` file. If you are already using sources in the new deb822 format, you will also need to check `.sources` files in the same location. ℹ️ **Note**: Instead of removing older repositories, you can also disable them. In `.list` files simply comment them out by adding a `#` to the beginning of the line. In `.sources` files, you can add the line `Enabled: no` to any stanza you want to disable. See the [Package Repositories](https://pve.proxmox.com/wiki/Package_Repositories#_debian_base_repositories "Package Repositories") section in the reference docs for the correct Proxmox Datacenter Manager Beta / Debian Trixie repositories. #### Add the Proxmox Datacenter Manager 1 Package Repository You should be able to add the pdm-enterprise repository with this command: cat > /etc/apt/sources.list.d/pdm-test.sources << EOF Types: deb URIs: [https://enterprise.proxmox.com/debian/pdm](https://enterprise.proxmox.com/debian/pdm) Suites: trixie Components: pdm-enterprise Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg EOF Make sure that `apt` picks it up correctly by running `apt update` and checking the output of `apt policy`. Then remove the previous Proxmox Datacenter Manager Alpha repository from either the `/etc/apt/sources.list`, `/etc/apt/sources-list.d/pdm-test.list` or any other `.list` or `.sources` file you may have added it to. You can use `apt update` and `apt policy` again to make sure the old repository is not being used anymore. ℹ️ **Note**: Instead of removing older repositories, you can also disable them. In `.list` files simply comment them out by adding a `#` to the beginning of the line. In `.sources` files, you can add the line `Enabled: no` to any stanza you want to disable. Make sure to check that all the `.list` and `.sources` files you added in /etc/apt/sources.list.d/ got switched over to Trixie correctly. To make sure that all package repositories are being picked up correctly first run the following command to refresh the package index: apt update Note that this command does not start the upgrade itself, it only refreshes the package index and must not return any error. Then run: apt policy Verify that the output of this command shows only Trixie repositories and that the Proxmox Datacenter Manager repository shows up correctly. ### Upgrade the System Note that the time required for finishing this step heavily depends on the system's performance, especially the root filesystem's IOPS and bandwidth. A slow spinner can take up to 60 minutes or more, while for a high-performance server with SSD storage, the upgrade can be finished in less than 5 minutes. ℹ️ **Note**: While the packages are being upgraded certain operations and requests to the API might fail (for example, logging in as a system user in the `pam` realm) To upgrade the packages, run: apt update apt dist-upgrade While running the `apt dist-upgrade` command, you may be asked to approve changes to configuration files and some service restarts among other prompts. This includes: * The output of `apt-listchanges`: You can simply exit it by pressing q. * Selecting your default keyboard settings: Simply use the arrow keys to navigate to the one applicable in your case and hit enter. * Questions about service restarts (like `Restart services during package upgrades without asking?`): Use the default if unsure, as the reboot after the upgrade will restart all services cleanly anyway. * Questions about (default) configuration changes: It is suggested to check the difference for each file in question and choose the answer accordingly to what's most appropriate for your setup. Common configuration files with changes, and the recommended choices are: * `/etc/issue` -> Proxmox Datacenter Manager will auto-generate this file on boot, and it has only cosmetic effects on the login console. Using the default "No" (keep your currently-installed version) is safe here. * `/etc/ssh/sshd_config` -> If you have not changed this file manually, the only differences should be a replacement of `ChallengeResponseAuthentication no` with `KbdInteractiveAuthentication no` and some irrelevant changes in comments (lines starting with `#`). If this is the case, both options are safe, though we would recommend installing the package maintainer's version in order to move away from the deprecated `ChallengeResponseAuthentication` option. If there are other changes, we suggest to inspect them closely and decide accordingly. * `/etc/default/grub` -> Here you may want to take special care, as this is normally only asked for if you changed it manually, e.g., for adding some kernel command line option. It's recommended to check the difference for any relevant change, note that changes in comments (lines starting with `#`) are not relevant. If unsure, we suggest selecting "No" (keep your currently-installed version) ### Check Result & Reboot Into Updated Kernel If the command exits successfully, you can reboot the system in order to enable the new kernel. systemctl reboot Please note that you should reboot even if you already used the 6.14 kernel previously, through the opt-in package on Proxmox Datacenter Manager Alpha. Following the Proxmox Datacenter Manager Upgrade ------------------------------------------------ Empty the browser cache and/or force-reload the Web UI (CTRL + SHIFT + R, or for MacOS ⌘ + Alt + R). ### Check Status of Services Check that the statuses of the main services are `active (running)` systemctl status proxmox-datacenter-api.service proxmox-datacenter-privileged-api.service ### Optional: Modernize APT Repository Sources You can migrate existing repository sources to the recommended deb822 style format, by running: apt modernize-sources By answering the following prompt with "n" you can check the changes the command would make before applying them. To apply them simply run the command again and respond to the prompt with "Y". The command will also keep the old `.list` files around by appending `.bak` to them. So you will have the new `.sources` files and the old repository configurations in the `.list.bak` files. You can remove the leftover backup files once you verified that everything works smoothly with the new format. Potential Issues ================ As a Debian based distribution, Proxmox Datacenter Manager is affected by most issues and changes affecting Debian. Thus, ensure that you read the [upgrade specific issues for Debian Trixie](https://www.debian.org/releases/trixie/release-notes/issues.en.html) . Please also check the known issue list from the [Proxmox Datacenter Manager 1.0 changelog](https://pdm.proxmox.com/docs/roadmap.html#known-issues-breaking-changes) . Older Hardware and New 6.14 Kernel ---------------------------------- Compatibility of old hardware (released >= 10 years ago) is not as thoroughly tested as more recent hardware. For old hardware we highly recommend testing compatibility of Proxmox Datacenter Manager with identical (or at least similar) hardware before upgrading any production machines. We will expand this section with potential pitfalls and workarounds once they arise. Network Interface Name Changes ------------------------------ The new kernel can recognize more hardware features such as virtual function of PCI(e) devices. Since network names are usually derived from PIC(e) addresses and features recognized by the kernel, the network configuration might need to be adapted to match the new interface names. In such cases, the network connection to a Proxmox Datacenter Manager host might be lost during or after the upgrade process. Hence, it is generally recommended to have either physical access or an independent remote connection to the host (for example, via IPMI or iKVM). Systemd-Boot Meta-Package Changes the Bootloader Configuration Automatically and Should Be Uninstalled ------------------------------------------------------------------------------------------------------ With Debian Trixie the `systemd-boot` package got split up a bit further into `systemd-boot-efi` (containing the EFI-binary used for booting), `systemd-boot-tools` (containing `bootctl`) and the `systemd-boot` meta-package (containing hooks which run upon upgrades of itself and other packages and install systemd-boot as bootloader). As Proxmox Systems usually handle the installation of `systemd-boot` as bootloader using `proxmox-boot-tool` the meta-package should be removed. The package was automatically shipped for systems installed from the Proxmox Datacenter Manager Alpha to Proxmox Datacenter Manager ISOs, as it contained `bootctl` in bookworm. If the `pdmAtoB` checklist script suggests it, the `systemd-boot` meta-package is safe to remove unless you manually installed it and are using `systemd-boot` as a bootloader. Should `systemd-boot-efi` and `systemd-boot-tools` be required, `pdmAtoB` will warn you accordingly. The `pdmAtoB` checklist script will change its output depending on the state of the upgrade, and should be [run continuously before and after the upgrade](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1#Continuously_use_the_pdmAtoB_Checklist_Script) . It will print which packages should be removed or added at the appropriate time. The only situation where you should keep the meta-package systemd-boot installed is if you manually setup `systemd-boot` for your system. See also [bug for systemd-boot](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1110177) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Proxmox\_Datacenter\_Manager\_Upgrade\_from\_Alpha\_to\_1&oldid=12442](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1&oldid=12442) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Upgrade](https://pve.proxmox.com/wiki/Category:Upgrade "Category:Upgrade") * [Proxmox Datacenter Manager](https://pve.proxmox.com/wiki/Category:Proxmox_Datacenter_Manager "Category:Proxmox Datacenter Manager") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # MediaWiki:Restricted-displaytitle-ignored - Proxmox VE MediaWiki:Restricted-displaytitle-ignored ========================================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/MediaWiki:Restricted-displaytitle-ignored#mw-head) [Jump to search](https://pve.proxmox.com/wiki/MediaWiki:Restricted-displaytitle-ignored#searchInput) Pages with ignored display titles Retrieved from "[https://pve.proxmox.com/wiki/MediaWiki:Restricted-displaytitle-ignored](https://pve.proxmox.com/wiki/MediaWiki:Restricted-displaytitle-ignored) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # MediaWiki:Node-count-exceeded-category - Proxmox VE MediaWiki:Node-count-exceeded-category ====================================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/MediaWiki:Node-count-exceeded-category#mw-head) [Jump to search](https://pve.proxmox.com/wiki/MediaWiki:Node-count-exceeded-category#searchInput) Pages where node count is exceeded Retrieved from "[https://pve.proxmox.com/wiki/MediaWiki:Node-count-exceeded-category](https://pve.proxmox.com/wiki/MediaWiki:Node-count-exceeded-category) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Talk:Storage: LVM Thin - Proxmox VE Talk:Storage: LVM Thin ====================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Talk:Storage:_LVM_Thin#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Talk:Storage:_LVM_Thin#searchInput) Two lines (steps): **lvcreate -L 100G -n data pve** **lvconvert --type thin-pool pve/data** Can be changed with: **lvcreate -L 100G -T -n data pve** **\-T** switch creates thin pool P.S. Why i can not update the content ? Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Talk:Storage:\_LVM\_Thin&oldid=9988](https://pve.proxmox.com/mediawiki/index.php?title=Talk:Storage:_LVM_Thin&oldid=9988) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Talk:Storage: NFS - Proxmox VE Talk:Storage: NFS ================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Talk:Storage:_NFS#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Talk:Storage:_NFS#searchInput) In a clustered installation, if a node of the cluster is also a NFS server for all the cluster, the node can hung on reboot/shutdown, because all node, so the server itself, mount the NFS share. In that node it is betetr to force a determined order in service shutdown, eg shutdown the NFS server before the pve-manager service. It suffices to create the file (and also create the folder /etc/systemd/system/pve-manager.service.d if not existant) /etc/systemd/system/pve-manager.service.d/after-nfs.conf with inside simply: \[Unit\] After=nfs-kernel-server.service and then reload systemd: systemctl daemon-reload Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Talk:Storage:\_NFS&oldid=9442](https://pve.proxmox.com/mediawiki/index.php?title=Talk:Storage:_NFS&oldid=9442) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Template:Langif - Proxmox VE Template:Langif =============== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Template:Langif#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Template:Langif#searchInput)  • \[\[{{{1}}}|{{{2}}}\]\] Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Template:Langif&oldid=16](https://pve.proxmox.com/mediawiki/index.php?title=Template:Langif&oldid=16) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Category talk:Virtual Appliances - Proxmox VE Category talk:Virtual Appliances ================================ From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Category_talk:Virtual_Appliances#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Category_talk:Virtual_Appliances#searchInput) Please create a BlueOnyx category. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Category\_talk:Virtual\_Appliances&oldid=826](https://pve.proxmox.com/mediawiki/index.php?title=Category_talk:Virtual_Appliances&oldid=826) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Proxmox VE Mobile Companion Data Protection - Proxmox VE Proxmox VE Mobile Companion Data Protection =========================================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Proxmox_VE_Mobile_Companion_Data_Protection#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Proxmox_VE_Mobile_Companion_Data_Protection#searchInput) #### Privacy Overview The **Proxmox VE Mobile Companion** app only saves data locally on your device. This includes details of any previously logged-in Proxmox VE servers, along with your username and the most recent login ticket (valid for two hours from the last renewal). You can clear this information by deleting the local data via the app menu in the Android settings. On iOS, the locally stored data will be deleted when you uninstall the app, as with any other app's local data. #### Data Collection Proxmox Server Solutions GmbH, the developer of this app, does not collect, use or store any of your personal data, nor do they have access to it. The app does not send any information to Proxmox Server Solutions GmbH or third parties. All app settings are stored locally on your device and are not considered personal data. If you choose to use biometric authentication, your biometric information will only be processed and stored securely on your device. If you installed the app through the Google Play Store, some information such as the app version or crash details may be reported to Google servers and made visible to us in the Google Play Store developer console. This happens for all apps served through the Play Store and is out of our control. Visit [https://policies.google.com/privacy?hl=en](https://policies.google.com/privacy?hl=en) to view Google's privacy policy. #### User Account Deletion Proxmox Server Solutions GmbH provides software that users can install and manage on their own hardware. The Proxmox VE Mobile Companion app is solely an interface for these instances. Therefore, only the instance administrator has full control over accounts, including the ability to delete them, on Proxmox VE instances. This is outside the control of Proxmox Server Solutions GmbH. If you wish to delete an account, you must therefore contact the administrator of the relevant instance. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Proxmox\_VE\_Mobile\_Companion\_Data\_Protection&oldid=12372](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_VE_Mobile_Companion_Data_Protection&oldid=12372) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Template:VZAPL - Proxmox VE Template:VZAPL ============== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Template:VZAPL#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Template:VZAPL#searchInput) Appliance Details ----------------- | | | | --- | --- | | Package: | {{{package}}} | | Version: | {{{version}}} | | Certified: | {{{certified}}} | | Section: | {{{section}}} | | Location: | {{{location}}} | | Maintainer: | {{{maintainer}}} | | OS: | {{{os}}} | Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Template:VZAPL&oldid=1122](https://pve.proxmox.com/mediawiki/index.php?title=Template:VZAPL&oldid=1122) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Talk:Backup and Restore - Proxmox VE Talk:Backup and Restore ======================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Talk:Backup_and_Restore#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Talk:Backup_and_Restore#searchInput) The [scheduled backup](https://pve.proxmox.com/wiki/Backup_and_Restore#Scheduled_Backup "Backup and Restore") section currently offers no instructions regarding the steps and nature of scheduled backups. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Talk:Backup\_and\_Restore&oldid=7124](https://pve.proxmox.com/mediawiki/index.php?title=Talk:Backup_and_Restore&oldid=7124) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Certificate Management - Proxmox VE Certificate Management ====================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Certificate_Management#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Certificate_Management#searchInput) Certificates for Intra-Cluster Communication -------------------------------------------- Each Proxmox VE cluster creates by default its own (self-signed) Certificate Authority (CA) and generates a certificate for each node which gets signed by the aforementioned CA. These certificates are used for encrypted communication with the cluster’s pveproxy service and the Shell/Console feature if SPICE is used. The CA certificate and key are stored in the [Proxmox Cluster File System (pmxcfs)](https://pve.proxmox.com/wiki/Proxmox_Cluster_File_System_(pmxcfs)#chapter_pmxcfs) . Certificates for API and Web GUI -------------------------------- The REST API and web GUI are provided by the pveproxy service, which runs on each node. You have the following options for the certificate used by pveproxy: 1. By default the node-specific certificate in /etc/pve/nodes/NODENAME/pve-ssl.pem is used. This certificate is signed by the cluster CA and therefore not automatically trusted by browsers and operating systems. 2. use an externally provided certificate (e.g. signed by a commercial CA). 3. use ACME (Let’s Encrypt) to get a trusted certificate with automatic renewal, this is also integrated in the Proxmox VE API and web interface. For options 2 and 3 the file /etc/pve/local/pveproxy-ssl.pem (and /etc/pve/local/pveproxy-ssl.key, which needs to be without password) is used. | | | | --- | --- | | ![Note]() | Keep in mind that /etc/pve/local is a node specific symlink to /etc/pve/nodes/NODENAME. | Certificates are managed with the Proxmox VE Node management command (see the pvenode(1) manpage). | | | | --- | --- | | ![Warning]() | Do not replace or manually modify the automatically generated node certificate files in /etc/pve/local/pve-ssl.pem and /etc/pve/local/pve-ssl.key or the cluster CA files in /etc/pve/pve-root-ca.pem and /etc/pve/priv/pve-root-ca.key. | Upload Custom Certificate ------------------------- If you already have a certificate which you want to use for a Proxmox VE node you can upload that certificate simply over the web interface. [![screenshot/gui-node-certs-upload-custom.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-node-certs-upload-custom.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-node-certs-upload-custom.png) Note that the certificates key file, if provided, mustn’t be password protected. Trusted certificates via Let’s Encrypt (ACME) --------------------------------------------- Proxmox VE includes an implementation of the **A**utomatic **C**ertificate **M**anagement **E**nvironment **ACME** protocol, allowing Proxmox VE admins to use an ACME provider like Let’s Encrypt for easy setup of TLS certificates which are accepted and trusted on modern operating systems and web browsers out of the box. Currently, the two ACME endpoints implemented are the [Let’s Encrypt (LE)](https://letsencrypt.org/) production and its staging environment. Our ACME client supports validation of http-01 challenges using a built-in web server and validation of dns-01 challenges using a DNS plugin supporting all the DNS API endpoints [acme.sh](https://acme.sh/) does. ### ACME Account [![screenshot/gui-datacenter-acme-register-account.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-datacenter-acme-register-account.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-datacenter-acme-register-account.png) You need to register an ACME account per cluster with the endpoint you want to use. The email address used for that account will serve as contact point for renewal-due or similar notifications from the ACME endpoint. You can register and deactivate ACME accounts over the web interface Datacenter -> ACME or using the pvenode command-line tool. pvenode acme account register account-name mail@example.com | | | | --- | --- | | ![Tip]() | Because of [rate-limits](https://letsencrypt.org/docs/rate-limits/)
you should use LE staging for experiments or if you use ACME for the first time. | ### ACME Plugins The ACME plugins task is to provide automatic verification that you, and thus the Proxmox VE cluster under your operation, are the real owner of a domain. This is the basis building block for automatic certificate management. The ACME protocol specifies different types of challenges, for example the http-01 where a web server provides a file with a certain content to prove that it controls a domain. Sometimes this isn’t possible, either because of technical limitations or if the address of a record to is not reachable from the public internet. The dns-01 challenge can be used in these cases. This challenge is fulfilled by creating a certain DNS record in the domain’s zone. [![screenshot/gui-datacenter-acme-overview.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-datacenter-acme-overview.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-datacenter-acme-overview.png) Proxmox VE supports both of those challenge types out of the box, you can configure plugins either over the web interface under Datacenter -> ACME, or using the pvenode acme plugin add command. ACME Plugin configurations are stored in /etc/pve/priv/acme/plugins.cfg. A plugin is available for all nodes in the cluster. ### Node Domains Each domain is node specific. You can add new or manage existing domain entries under Node -> Certificates, or using the pvenode config command. [![screenshot/gui-node-certs-add-domain.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-node-certs-add-domain.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-node-certs-add-domain.png) After configuring the desired domain(s) for a node and ensuring that the desired ACME account is selected, you can order your new certificate over the web interface. On success the interface will reload after 10 seconds. Renewal will happen [automatically](https://pve.proxmox.com/wiki/Certificate_Management#sysadmin_certs_acme_automatic_renewal) . ACME HTTP Challenge Plugin -------------------------- There is always an implicitly configured standalone plugin for validating http-01 challenges via the built-in webserver spawned on port 80. | | | | --- | --- | | ![Note]() | The name standalone means that it can provide the validation on it’s own, without any third party service. So, this plugin works also for cluster nodes. | There are a few prerequisites to use it for certificate management with Let’s Encrypts ACME. * You have to accept the ToS of Let’s Encrypt to register an account. * **Port 80** of the node needs to be reachable from the internet. * There **must** be no other listener on port 80. * The requested (sub)domain needs to resolve to a public IP of the Node. ACME DNS API Challenge Plugin ----------------------------- On systems where external access for validation via the http-01 method is not possible or desired, it is possible to use the dns-01 validation method. This validation method requires a DNS server that allows provisioning of TXT records via an API. ### Configuring ACME DNS APIs for validation Proxmox VE re-uses the DNS plugins developed for the acme.sh \[acme.sh [https://github.com/acmesh-official/acme.sh](https://github.com/acmesh-official/acme.sh)\ \] project, please refer to its documentation for details on configuration of specific APIs. The easiest way to configure a new plugin with the DNS API is using the web interface (Datacenter -> ACME). [![screenshot/gui-datacenter-acme-add-dns-plugin.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-datacenter-acme-add-dns-plugin.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-datacenter-acme-add-dns-plugin.png) Choose DNS as challenge type. Then you can select your API provider, enter the credential data to access your account over their API. The validation delay determines the time in seconds between setting the DNS record and prompting the ACME provider to validate it, as providers often need some time to propagate the record in their infrastructure. | | | | --- | --- | | ![Tip]() | See the acme.sh [How to use DNS API](https://github.com/acmesh-official/acme.sh/wiki/dnsapi#how-to-use-dns-api)
wiki for more detailed information about getting API credentials for your provider. | As there are many DNS providers and API endpoints Proxmox VE automatically generates the form for the credentials for some providers. For the others you will see a bigger text area, simply copy all the credentials KEY\=VALUE pairs in there. ### DNS Validation through CNAME Alias A special alias mode can be used to handle the validation on a different domain/DNS server, in case your primary/real DNS does not support provisioning via an API. Manually set up a permanent CNAME record for \_acme-challenge.domain1.example pointing to \_acme-challenge.domain2.example and set the alias property on the corresponding acmedomainX key in the Proxmox VE node configuration file to domain2.example to allow the DNS server of domain2.example to validate all challenges for domain1.example. ### Combination of Plugins Combining http-01 and dns-01 validation is possible in case your node is reachable via multiple domains with different requirements / DNS provisioning capabilities. Mixing DNS APIs from multiple providers or instances is also possible by specifying different plugin instances per domain. | | | | --- | --- | | ![Tip]() | Accessing the same service over multiple domains increases complexity and should be avoided if possible. | Automatic renewal of ACME certificates -------------------------------------- If a node has been successfully configured with an ACME-provided certificate (either via pvenode or via the GUI), the certificate will be automatically renewed by the pve-daily-update.service. Currently, renewal will be attempted if the certificate has expired already, or will expire in the next 30 days. | | | | --- | --- | | ![Note]() | If you are using a custom directory that issues short-lived certificates, disabling the random delay for the pve-daily-update.timer unit might be advisable to avoid missing a certificate renewal after a reboot. | ACME Examples with pvenode -------------------------- ### Example: Sample pvenode invocation for using Let’s Encrypt certificates root@proxmox:~# pvenode acme account register default mail@example.invalid Directory endpoints: 0) Let's Encrypt V2 (https://acme-v02.api.letsencrypt.org/directory) 1) Let's Encrypt V2 Staging (https://acme-staging-v02.api.letsencrypt.org/directory) 2) Custom Enter selection: 1 Terms of Service: https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf Do you agree to the above terms? \[y|N\]y ... Task OK root@proxmox:~# pvenode config set --acme domains=example.invalid root@proxmox:~# pvenode acme cert order Loading ACME account details Placing ACME order ... Status is 'valid'! All domains validated! ... Downloading certificate Setting pveproxy certificate and key Restarting pveproxy Task OK ### Example: Setting up the OVH API for validating a domain | | | | --- | --- | | ![Note]() | the account registration steps are the same no matter which plugins are used, and are not repeated here. | | | | | --- | --- | | ![Note]() | OVH\_AK and OVH\_AS need to be obtained from OVH according to the OVH API documentation | First you need to get all information so you and Proxmox VE can access the API. root@proxmox:~# cat /path/to/api-token OVH\_AK=XXXXXXXXXXXXXXXX OVH\_AS=YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY root@proxmox:~# source /path/to/api-token root@proxmox:~# curl -XPOST -H"X-Ovh-Application: $OVH\_AK" -H "Content-type: application/json" \\ https://eu.api.ovh.com/1.0/auth/credential -d '{ "accessRules": \[\ {"method": "GET","path": "/auth/time"},\ {"method": "GET","path": "/domain"},\ {"method": "GET","path": "/domain/zone/\*"},\ {"method": "GET","path": "/domain/zone/\*/record"},\ {"method": "POST","path": "/domain/zone/\*/record"},\ {"method": "POST","path": "/domain/zone/\*/refresh"},\ {"method": "PUT","path": "/domain/zone/\*/record/"},\ {"method": "DELETE","path": "/domain/zone/\*/record/\*"}\ \] }' {"consumerKey":"ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ","state":"pendingValidation","validationUrl":"https://eu.api.ovh.com/auth/?credentialToken=AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA"} (open validation URL and follow instructions to link Application Key with account/Consumer Key) root@proxmox:~# echo "OVH\_CK=ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ" >> /path/to/api-token Now you can setup the the ACME plugin: root@proxmox:~# pvenode acme plugin add dns example\_plugin --api ovh --data /path/to/api\_token root@proxmox:~# pvenode acme plugin config example\_plugin ┌────────┬──────────────────────────────────────────┐ │ key │ value │ ╞════════╪══════════════════════════════════════════╡ │ api │ ovh │ ├────────┼──────────────────────────────────────────┤ │ data │ OVH\_AK=XXXXXXXXXXXXXXXX │ │ │ OVH\_AS=YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY │ │ │ OVH\_CK=ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ │ ├────────┼──────────────────────────────────────────┤ │ digest │ 867fcf556363ca1bea866863093fcab83edf47a1 │ ├────────┼──────────────────────────────────────────┤ │ plugin │ example\_plugin │ ├────────┼──────────────────────────────────────────┤ │ type │ dns │ └────────┴──────────────────────────────────────────┘ At last you can configure the domain you want to get certificates for and place the certificate order for it: root@proxmox:~# pvenode config set -acmedomain0 example.proxmox.com,plugin=example\_plugin root@proxmox:~# pvenode acme cert order Loading ACME account details Placing ACME order Order URL: https://acme-staging-v02.api.letsencrypt.org/acme/order/11111111/22222222 Getting authorization details from 'https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/33333333' The validation for example.proxmox.com is pending! \[Wed Apr 22 09:25:30 CEST 2020\] Using OVH endpoint: ovh-eu \[Wed Apr 22 09:25:30 CEST 2020\] Checking authentication \[Wed Apr 22 09:25:30 CEST 2020\] Consumer key is ok. \[Wed Apr 22 09:25:31 CEST 2020\] Adding record \[Wed Apr 22 09:25:32 CEST 2020\] Added, sleep 10 seconds. Add TXT record: \_acme-challenge.example.proxmox.com Triggering validation Sleeping for 5 seconds Status is 'valid'! \[Wed Apr 22 09:25:48 CEST 2020\] Using OVH endpoint: ovh-eu \[Wed Apr 22 09:25:48 CEST 2020\] Checking authentication \[Wed Apr 22 09:25:48 CEST 2020\] Consumer key is ok. Remove TXT record: \_acme-challenge.example.proxmox.com All domains validated! Creating CSR Checking order status Order is ready, finalizing order valid! Downloading certificate Setting pveproxy certificate and key Restarting pveproxy Task OK ### Example: Switching from the staging to the regular ACME directory Changing the ACME directory for an account is unsupported, but as Proxmox VE supports more than one account you can just create a new one with the production (trusted) ACME directory as endpoint. You can also deactivate the staging account and recreate it. Example: Changing the default ACME account from staging to directory using pvenode root@proxmox:~# pvenode acme account deactivate default Renaming account file from '/etc/pve/priv/acme/default' to '/etc/pve/priv/acme/\_deactivated\_default\_4' Task OK root@proxmox:~# pvenode acme account register default example@proxmox.com Directory endpoints: 0) Let's Encrypt V2 (https://acme-v02.api.letsencrypt.org/directory) 1) Let's Encrypt V2 Staging (https://acme-staging-v02.api.letsencrypt.org/directory) 2) Custom Enter selection: 0 Terms of Service: https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf Do you agree to the above terms? \[y|N\]y ... Task OK Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Certificate\_Management&oldid=12070](https://pve.proxmox.com/mediawiki/index.php?title=Certificate_Management&oldid=12070) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Reference Documentation](https://pve.proxmox.com/wiki/Category:Reference_Documentation "Category:Reference Documentation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Talk:Storage: LVM - Proxmox VE Talk:Storage: LVM ================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Talk:Storage:_LVM#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Talk:Storage:_LVM#searchInput) Under Section: [https://pve.proxmox.com/wiki/Storage](https://pve.proxmox.com/wiki/Storage) You have noted: **3: It is possible to use LVM on top of an iSCSI or FC-based storage. That way you get a shared LVM storage** But here ([https://pve.proxmox.com/wiki/Talk:Storage:\_LVM](https://pve.proxmox.com/wiki/Talk:Storage:_LVM) ) you did not mention Fibre Channel (**FC**) storage at all. Maybe also to add the reference document related to **Multipath** which mention: * **LVM** on top of **Multipath + iSCSI** * **LVM** on top of **Multipath + FC** [https://pve.proxmox.com/wiki/Multipath](https://pve.proxmox.com/wiki/Multipath) So please correct this. * * * ... any update (2025-12-23) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Talk:Storage:\_LVM&oldid=12454](https://pve.proxmox.com/mediawiki/index.php?title=Talk:Storage:_LVM&oldid=12454) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Talk:Storage: RBD - Proxmox VE Talk:Storage: RBD ================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Talk:Storage:_RBD#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Talk:Storage:_RBD#searchInput) cannot map rbd -------------- For **krbd** beware that the _kernel module_ may not support all features on the images. Notably, current (as of 2018-05) kernel does not support _object-map fast-diff deep-flatten_, and spills errors if you try to map an image using one of those. This implies that 'df' will be horribly slow, for example. Pray to Supreme Being to fix up the kernel module. -- [Grin](https://pve.proxmox.com/wiki/User:Grin "User:Grin") ([talk](https://pve.proxmox.com/mediawiki/index.php?title=User_talk:Grin&action=edit&redlink=1 "User talk:Grin (page does not exist)") ) 12:10, 4 May 2018 (CEST) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Talk:Storage:\_RBD&oldid=10087](https://pve.proxmox.com/mediawiki/index.php?title=Talk:Storage:_RBD&oldid=10087) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Subscriptions - Proxmox VE Subscriptions ============= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Subscriptions#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Subscriptions#searchInput) See [https://www.proxmox.com/en/proxmox-ve/pricing](https://www.proxmox.com/en/proxmox-ve/pricing) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Subscriptions&oldid=10762](https://pve.proxmox.com/mediawiki/index.php?title=Subscriptions&oldid=10762) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Talk:Debian Appliance Builder - Proxmox VE Talk:Debian Appliance Builder ============================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Talk:Debian_Appliance_Builder#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Talk:Debian_Appliance_Builder#searchInput) If we choose to generate a random password for mysql at deployment time, how do we refer to it in the script for making the template? If it is the first time **make** is run on a new ProxMox install after the dab has been installed, then after the **make clean**, you will have to run **make** and **make clean** again. This is because of a lot of dependancy warnings. The second time, the packages are already downloaded in the cache folder and so all dependancy warnings will be gone and the **make** proceeds flawlesly. The created template must be moved to the cache folder before executing make clean otherwise it will be deleted. The following dab.conf parameter is missing in the wiki ManageUrl: http://\_\_IPADDRESS\_\_/ A list of usable variables like the \_\_IPADDRESS\_\_ must be included in the page. A means to place additional Infopage URLs in the dab.conf could be useful. In the example applications download, the joomla appliance joomla.conf file in dab-pve-appliances\_2009-01-19/debian-5.0-joomla needs to replace it's first line:- ServerAdmin webmaster@loalhost with ServerAdmin webmaster@localhost A sample install of dab: ~# apt-get install dab Reading package lists... Done Building dependency tree... Done The following extra packages will be installed: binutils make Suggested packages: binutils-doc make-doc-non-dfsg The following NEW packages will be installed: binutils dab make 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 3046kB of archives. After unpacking 8835kB of additional disk space will be used. Do you want to continue \[Y/n\]? y Get:1 http://download.proxmox.com etch/pve dab 1.1-1 \[25.8kB\] Get:2 http://ftp.debian.org etch/main binutils 2.17-3 \[2630kB\] Get:3 http://ftp.debian.org etch/main make 3.81-2 \[390kB\] Fetched 3046kB in 22s (136kB/s) Selecting previously deselected package binutils. (Reading database ... 24508 files and directories currently installed.) Unpacking binutils (from .../binutils\_2.17-3\_amd64.deb) ... Selecting previously deselected package make. Unpacking make (from .../archives/make\_3.81-2\_amd64.deb) ... Selecting previously deselected package dab. Unpacking dab (from .../apt/archives/dab\_1.1-1\_all.deb) ... Setting up binutils (2.17-3) ... Setting up make (3.81-2) ... Setting up dab (1.1-1) ... Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Talk:Debian\_Appliance\_Builder&oldid=842](https://pve.proxmox.com/mediawiki/index.php?title=Talk:Debian_Appliance_Builder&oldid=842) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Calendar Events - Proxmox VE Calendar Events =============== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Calendar_Events#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Calendar_Events#searchInput) Schedule Format --------------- Proxmox VE has a very flexible scheduling configuration. It is based on the systemd time calendar event format. \[see man 7 systemd.time for more information\] Calendar events may be used to refer to one or more points in time in a single expression. Such a calendar event uses the following format: \[WEEKDAY\] \[\[YEARS-\]MONTHS-DAYS\] \[HOURS:MINUTES\[:SECONDS\]\] This format allows you to configure a set of days on which the job should run. You can also set one or more start times. It tells the replication scheduler the moments in time when a job should start. With this information we, can create a job which runs every workday at 10 PM: 'mon,tue,wed,thu,fri 22' which could be abbreviated to: 'mon..fri 22', most reasonable schedules can be written quite intuitive this way. | | | | --- | --- | | ![Note]() | Hours are formatted in 24-hour format. | To allow a convenient and shorter configuration, one or more repeat times per guest can be set. They indicate that replications are done on the start-time(s) itself and the start-time(s) plus all multiples of the repetition value. If you want to start replication at 8 AM and repeat it every 15 minutes until 9 AM you would use: '8:00/15' Here you see that if no hour separation (:), is used the value gets interpreted as minute. If such a separation is used, the value on the left denotes the hour(s), and the value on the right denotes the minute(s). Further, you can use \* to match all possible values. To get additional ideas look at [more Examples below](https://pve.proxmox.com/wiki/Calendar_Events#pvesr_schedule_format_examples) . Detailed Specification ---------------------- weekdays Days are specified with an abbreviated English version: sun, mon, tue, wed, thu, fri and sat. You may use multiple days as a comma-separated list. A range of days can also be set by specifying the start and end day separated by “..”, for example mon..fri. These formats can be mixed. If omitted '\*' is assumed. time-format A time format consists of hours and minutes interval lists. Hours and minutes are separated by ':'. Both hour and minute can be list and ranges of values, using the same format as days. First are hours, then minutes. Hours can be omitted if not needed. In this case '\*' is assumed for the value of hours. The valid range for values is 0-23 for hours and 0-59 for minutes. | | | | --- | --- | | ![Note]() | You can use systemd-analyze calendar to see whether a given calendar event specification is valid and when it would be triggered next. By passing the \--iterations= flag you can also let it output the next times the calendar event would trigger (you need to replace with a valid integer). | ### Examples: There are some special values that have a specific meaning: | | | | --- | --- |Table 1. Special Values | Value | Syntax | | --- | --- | | minutely | \*-\*-\* \*:\*:00 | | hourly | \*-\*-\* \*:00:00 | | daily | \*-\*-\* 00:00:00 | | weekly | mon \*-\*-\* 00:00:00 | | monthly | \*-\*-01 00:00:00 | | yearly or annually | \*-01-01 00:00:00 | | quarterly | \*-01,04,07,10-01 00:00:00 | | semiannually or semi-annually | \*-01,07-01 00:00:00 | | | | | | --- | --- | --- |Table 2. Schedule Examples | Schedule String | Alternative | Meaning | | --- | --- | --- | | mon,tue,wed,thu,fri | mon..fri | Every working day at 0:00 | | sat,sun | sat..sun | Only on weekends at 0:00 | | mon,wed,fri | — | Only on Monday, Wednesday and Friday at 0:00 | | 12:05 | 12:05 | Every day at 12:05 PM | | \*/5 | 0/5 | Every five minutes | | mon..wed 30/10 | mon,tue,wed 30/10 | Monday, Tuesday, Wednesday 30, 40 and 50 minutes after every full hour | | mon..fri 8..17,22:0/15 | — | Every working day every 15 minutes between 8 AM and 6 PM and between 10 PM and 11 PM | | fri 12..13:5/20 | fri 12,13:5/20 | Friday at 12:05, 12:25, 12:45, 13:05, 13:25 and 13:45 | | 12,14,16,18,20,22:5 | 12/2:5 | Every day starting at 12:05 until 22:05, every 2 hours | | \* | \*/1 | Every minute (minimum interval) | | \*-05 | — | On the 5th day of every Month | | Sat \*-1..7 15:00 | — | First Saturday each Month at 15:00 | | 2015-10-21 | — | 21st October 2015 at 00:00 | Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Calendar\_Events&oldid=12289](https://pve.proxmox.com/mediawiki/index.php?title=Calendar_Events&oldid=12289) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Reference Documentation](https://pve.proxmox.com/wiki/Category:Reference_Documentation "Category:Reference Documentation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # BTRFS - Proxmox VE BTRFS ===== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/BTRFS#mw-head) [Jump to search](https://pve.proxmox.com/wiki/BTRFS#searchInput) | | | | --- | --- | | ![Warning]() | BTRFS integration is currently a **technology preview** in Proxmox VE. | BTRFS is a modern copy on write file system natively supported by the Linux kernel, implementing features such as snapshots, built-in RAID and self healing via checksums for data and metadata. Starting with Proxmox VE 7.0, BTRFS is introduced as optional selection for the root file system. General BTRFS advantages * Main system setup almost identical to the traditional ext4 based setup * Snapshots * Data compression on file system level * Copy-on-write clone * RAID0, RAID1 and RAID10 * Protection against data corruption * Self healing * Natively supported by the Linux kernel Caveats * RAID levels 5/6 are experimental and dangerous, see [BTRFS Status](https://btrfs.readthedocs.io/en/latest/Status.html) Installation as Root File System -------------------------------- When you install using the Proxmox VE installer, you can choose BTRFS for the root file system. You need to select the RAID type at installation time: | | | | --- | --- | | RAID0 | Also called “striping”. The capacity of such volume is the sum of the capacities of all disks. But RAID0 does not add any redundancy, so the failure of a single drive makes the volume unusable. | | RAID1 | Also called “mirroring”. Data is written identically to all disks. This mode requires at least 2 disks with the same size. The resulting capacity is that of a single disk. | | RAID10 | A combination of RAID0 and RAID1. Requires at least 4 disks. | The installer automatically partitions the disks and creates an additional subvolume at /var/lib/pve/local-btrfs. In order to use that with the Proxmox VE tools, the installer creates the following configuration entry in /etc/pve/storage.cfg: dir: local path /var/lib/vz content iso,vztmpl,backup disable btrfs: local-btrfs path /var/lib/pve/local-btrfs content iso,vztmpl,backup,images,rootdir This explicitly disables the default local storage in favor of a BTRFS specific storage entry on the additional subvolume. The btrfs command is used to configure and manage the BTRFS file system, After the installation, the following command lists all additional subvolumes: \# btrfs subvolume list / ID 256 gen 6 top level 5 path var/lib/pve/local-btrfs BTRFS Administration -------------------- This section gives you some usage examples for common tasks. ### Creating a BTRFS file system To create BTRFS file systems, mkfs.btrfs is used. The \-d and \-m parameters are used to set the profile for metadata and data respectively. With the optional \-L parameter, a label can be set. Generally, the following modes are supported: single, raid0, raid1, raid10. Create a BTRFS file system on a single disk /dev/sdb with the label My-Storage: # mkfs.btrfs -m single -d single -L My-Storage /dev/sdb Or create a RAID1 on the two partitions /dev/sdb1 and /dev/sdc1: # mkfs.btrfs -m raid1 -d raid1 -L My-Storage /dev/sdb1 /dev/sdc1 ### Mounting a BTRFS file system The new file-system can then be mounted either manually, for example: # mkdir /my-storage # mount /dev/sdb /my-storage A BTRFS can also be added to /etc/fstab like any other mount point, automatically mounting it on boot. It’s recommended to avoid using block-device paths but use the UUID value the mkfs.btrfs command printed, especially there is more than one disk in a BTRFS setup. For example: File /etc/fstab \# ... other mount points left out for brevity # using the UUID from the mkfs.btrfs output is highly recommended UUID=e2c0c3ff-2114-4f54-b767-3a203e49f6f3 /my-storage btrfs defaults 0 0 | | | | --- | --- | | ![Tip]() | If you do not have the UUID available anymore you can use the blkid tool to list all properties of block-devices. | Afterwards you can trigger the first mount by executing: mount /my-storage After the next reboot this will be automatically done by the system at boot. ### Adding a BTRFS file system to Proxmox VE You can add an existing BTRFS file system to Proxmox VE via the web interface, or using the CLI, for example: pvesm add btrfs my-storage --path /my-storage ### Creating a subvolume Creating a subvolume links it to a path in the BTRFS file system, where it will appear as a regular directory. \# btrfs subvolume create /some/path Afterwards /some/path will act like a regular directory. ### Deleting a subvolume Contrary to directories removed via rmdir, subvolumes do not need to be empty in order to be deleted via the btrfs command. \# btrfs subvolume delete /some/path ### Creating a snapshot of a subvolume BTRFS does not actually distinguish between snapshots and normal subvolumes, so taking a snapshot can also be seen as creating an arbitrary copy of a subvolume. By convention, Proxmox VE will use the read-only flag when creating snapshots of guest disks or subvolumes, but this flag can also be changed later on. \# btrfs subvolume snapshot -r /some/path /a/new/path This will create a read-only "clone" of the subvolume on /some/path at /a/new/path. Any future modifications to /some/path cause the modified data to be copied before modification. If the read-only (\-r) option is left out, both subvolumes will be writable. ### Enabling compression By default, BTRFS does not compress data. To enable compression, the compress mount option can be added. Note that data already written will not be compressed after the fact. By default, the rootfs will be listed in /etc/fstab as follows: UUID= / btrfs defaults 0 1 You can simply append compress=zstd, compress=lzo, or compress=zlib to the defaults above like so: UUID= / btrfs defaults,compress=zstd 0 1 This change will take effect after rebooting. ### Checking Space Usage The classic df tool may output confusing values for some BTRFS setups. For a better estimate use the btrfs filesystem usage /PATH command, for example: \# btrfs fi usage /my-storage Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=BTRFS&oldid=12075](https://pve.proxmox.com/mediawiki/index.php?title=BTRFS&oldid=12075) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Reference Documentation](https://pve.proxmox.com/wiki/Category:Reference_Documentation "Category:Reference Documentation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Template:Db" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Template:Db" ================================ ← [Template:Db](https://pve.proxmox.com/mediawiki/index.php?title=Template:Db&action=edit&redlink=1 "Template:Db (page does not exist)") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Template:Db#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Template:Db#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Template:Db](https://pve.proxmox.com/mediawiki/index.php?title=Template:Db&action=edit&redlink=1 "Template:Db (page does not exist)") **: Displaying 2 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Template:Db&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Template:Db&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Template:Db&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Template:Db&limit=500) ) * [User:Benjamin Redling](https://pve.proxmox.com/wiki/User:Benjamin_Redling "User:Benjamin Redling") (transclusion) ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User%3ABenjamin+Redling "Special:WhatLinksHere") ) * [User:Benjamin Rampe](https://pve.proxmox.com/wiki/User:Benjamin_Rampe "User:Benjamin Rampe") (transclusion) ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User%3ABenjamin+Rampe "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Template:Db&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Template:Db&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Template:Db&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Template:Db&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Template:Db](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Template:Db) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Debugging Installation" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Debugging Installation" =========================================== ← [Debugging Installation](https://pve.proxmox.com/wiki/Debugging_Installation "Debugging Installation") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Debugging_Installation#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Debugging_Installation#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Debugging Installation](https://pve.proxmox.com/wiki/Debugging_Installation "Debugging Installation") **: Displaying 1 item. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Debugging_Installation&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Debugging_Installation&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Debugging_Installation&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Debugging_Installation&limit=500) ) * [Quick installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Quick+installation "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Debugging_Installation&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Debugging_Installation&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Debugging_Installation&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Debugging_Installation&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Debugging\_Installation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Debugging_Installation) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # OVMF/UEFI Boot Entries - Proxmox VE OVMF/UEFI Boot Entries ====================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/OVMF/UEFI_Boot_Entries#mw-head) [Jump to search](https://pve.proxmox.com/wiki/OVMF/UEFI_Boot_Entries#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/OVMF/UEFI_Boot_Entries#Introduction) * [2 Add a Boot Option](https://pve.proxmox.com/wiki/OVMF/UEFI_Boot_Entries#Add_a_Boot_Option) * [2.1 Short How-To](https://pve.proxmox.com/wiki/OVMF/UEFI_Boot_Entries#Short_How-To) * [2.2 Detailed How-To](https://pve.proxmox.com/wiki/OVMF/UEFI_Boot_Entries#Detailed_How-To) * [3 References](https://pve.proxmox.com/wiki/OVMF/UEFI_Boot_Entries#References) Introduction ------------ If a VM boots via OVMF (UEFI[\[1\]](https://pve.proxmox.com/wiki/OVMF/UEFI_Boot_Entries#cite_note-uefi-1) ), the firmware has to know which bootloader it has to start from the ESP[\[2\]](https://pve.proxmox.com/wiki/OVMF/UEFI_Boot_Entries#cite_note-esp-2) . When no boot entries exist in the EFIVARS store, it tries to load the fallback `$ESP/EFI/BOOT/BOOTX64.efi` loader. Should that also fail, the VM gets booted into the EFI Shell Add a Boot Option ----------------- ### Short How-To 1. Start-up the VM and press ESC exactly once when the splash screen appears. * On current versions of Proxmox VE, select the "EFI Firmware Setup" entry to get into the OVMF menu. * On older versions of Proxmox VE, you should be in the OVMF menu already. 2. Then "Boot Maintenance Manager" -> "Boot Options" -> "Add Boot Option" -> choose Disk with the EFI System Partition. 3. Now find the EFI executable, for example for Debian: `EFI/debian/grubx64.efi` or for Fedora: `EFI/fedora/shimx64-fedora.efi`. 4. Name it ("Input the description") and "Commit Change" 5. Use "Change Boot Order" to order the new entry to the top. ### Detailed How-To To add an entry of an existing bootloader go into the OVMF menu. Press 'ESC' exactly once during boot when the splash screen appears. On current versions of Proxmox VE, select the 'EFI Firmware Setup' entry. On older versions of Proxmox VE, you are already in the OVMF menu after pressing escape. Then select 'Boot Maintenance Manager': [![OVMF Menu](https://pve.proxmox.com/mediawiki/images/c/c8/Efi02.png)](https://pve.proxmox.com/wiki/File:Efi02.png "OVMF Menu") Select 'Boot Options': [![Boot Maintenance Manager](https://pve.proxmox.com/mediawiki/images/3/35/Efi03.png)](https://pve.proxmox.com/wiki/File:Efi03.png "Boot Maintenance Manager") Select 'Add Boot Option': [![Boot Options](https://pve.proxmox.com/mediawiki/images/8/82/Efi04.png)](https://pve.proxmox.com/wiki/File:Efi04.png "Boot Options") Choose the Hard Drive with the ESP: [![Add Boot Option](https://pve.proxmox.com/mediawiki/images/8/85/Efi05.png)](https://pve.proxmox.com/wiki/File:Efi05.png "Add Boot Option") Navigate the folder structure to your bootloader (EFI/debian/shimx64.efi in this example) [![Bootloader File Chooser /](https://pve.proxmox.com/mediawiki/images/7/78/Efi06.png)](https://pve.proxmox.com/wiki/File:Efi06.png "Bootloader File Chooser /") → [![Bootloader File Chooser /EFI](https://pve.proxmox.com/mediawiki/images/7/7d/Efi07.png)](https://pve.proxmox.com/wiki/File:Efi07.png "Bootloader File Chooser /EFI") → [![Bootloader File Chooser /EFI/debian](https://pve.proxmox.com/mediawiki/images/2/26/Efi08.png)](https://pve.proxmox.com/wiki/File:Efi08.png "Bootloader File Chooser /EFI/debian") After that, enter a name and commit: [![Modify Boot Option](https://pve.proxmox.com/mediawiki/images/d/d0/Efi09.png)](https://pve.proxmox.com/wiki/File:Efi09.png "Modify Boot Option") → [![Modify Boot Option](https://pve.proxmox.com/mediawiki/images/e/ef/Efi10.png)](https://pve.proxmox.com/wiki/File:Efi10.png "Modify Boot Option") → [![Modify Boot Option](https://pve.proxmox.com/mediawiki/images/4/4e/Efi11.png)](https://pve.proxmox.com/wiki/File:Efi11.png "Modify Boot Option") To make it the default boot entry, you now have to change the boot order: [![Boot Options](https://pve.proxmox.com/mediawiki/images/8/80/Efi12.png)](https://pve.proxmox.com/wiki/File:Efi12.png "Boot Options") Press enter, select the boot entry with the arrow keys and move it up and down with '+' and '-' respectively. Then press enter again and commit your changes: [![Change Boot Order](https://pve.proxmox.com/mediawiki/images/1/12/Efi13.png)](https://pve.proxmox.com/wiki/File:Efi13.png "Change Boot Order") → [![Change Boot Order](https://pve.proxmox.com/mediawiki/images/d/d5/Efi14.png)](https://pve.proxmox.com/wiki/File:Efi14.png "Change Boot Order") The last step is to reset the VM via OVMF, after that it should boot using the just configured boot entry. [![OVMF Menu](https://pve.proxmox.com/mediawiki/images/8/89/Efi15.png)](https://pve.proxmox.com/wiki/File:Efi15.png "OVMF Menu") References ---------- 1. [↑](https://pve.proxmox.com/wiki/OVMF/UEFI_Boot_Entries#cite_ref-uefi_1-0) [https://en.wikipedia.org/wiki/Unified\_Extensible\_Firmware\_Interface](https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface) 2. [↑](https://pve.proxmox.com/wiki/OVMF/UEFI_Boot_Entries#cite_ref-esp_2-0) EFI System Partition. [https://en.wikipedia.org/wiki/EFI\_system\_partition](https://en.wikipedia.org/wiki/EFI_system_partition) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=OVMF/UEFI\_Boot\_Entries&oldid=12527](https://pve.proxmox.com/mediawiki/index.php?title=OVMF/UEFI_Boot_Entries&oldid=12527) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Hotplug (qemu disk,nic,cpu,memory)" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Hotplug (qemu disk,nic,cpu,memory)" ======================================================= ← [Hotplug (qemu disk,nic,cpu,memory)](https://pve.proxmox.com/wiki/Hotplug_(qemu_disk,nic,cpu,memory) "Hotplug (qemu disk,nic,cpu,memory)") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Hotplug_(qemu_disk,nic,cpu,memory)#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Hotplug_(qemu_disk,nic,cpu,memory)#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Hotplug (qemu disk,nic,cpu,memory)](https://pve.proxmox.com/wiki/Hotplug_(qemu_disk,nic,cpu,memory) "Hotplug (qemu disk,nic,cpu,memory)") **: Displaying 1 item. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Hotplug_(qemu_disk,nic,cpu,memory)&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Hotplug_(qemu_disk,nic,cpu,memory)&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Hotplug_(qemu_disk,nic,cpu,memory)&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Hotplug_(qemu_disk,nic,cpu,memory)&limit=500) ) * [NUMA](https://pve.proxmox.com/wiki/NUMA "NUMA") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=NUMA "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Hotplug_(qemu_disk,nic,cpu,memory)&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Hotplug_(qemu_disk,nic,cpu,memory)&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Hotplug_(qemu_disk,nic,cpu,memory)&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Hotplug_(qemu_disk,nic,cpu,memory)&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Hotplug\_(qemu\_disk,nic,cpu,memory)](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Hotplug_(qemu_disk,nic,cpu,memory)) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Talk:Cluster Manager - Proxmox VE Talk:Cluster Manager ==================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Talk:Cluster_Manager#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Talk:Cluster_Manager#searchInput) Corosync Ports are outdated. Since Corosync v3, ports 5405-5412 are used instead of 5405 and 5404. --[Marco Gabriel](https://pve.proxmox.com/wiki/User:Marco_Gabriel "User:Marco Gabriel") ([talk](https://pve.proxmox.com/wiki/User_talk:Marco_Gabriel "User talk:Marco Gabriel") ) 10:10, 6 May 2022 (CEST) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Talk:Cluster\_Manager&oldid=11363](https://pve.proxmox.com/mediawiki/index.php?title=Talk:Cluster_Manager&oldid=11363) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Recover From Grub Failure - Proxmox VE Recover From Grub Failure ========================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Recover_From_Grub_Failure#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Recover_From_Grub_Failure#searchInput) Contents -------- * [1 General advice](https://pve.proxmox.com/wiki/Recover_From_Grub_Failure#General_advice) * [1.1 LVM (Ext4/XFS) based systems](https://pve.proxmox.com/wiki/Recover_From_Grub_Failure#LVM_(Ext4/XFS)_based_systems) * [1.2 ZFS based systems](https://pve.proxmox.com/wiki/Recover_From_Grub_Failure#ZFS_based_systems) * [1.3 Mount relevant filesystems and hostpaths](https://pve.proxmox.com/wiki/Recover_From_Grub_Failure#Mount_relevant_filesystems_and_hostpaths) * [1.4 Chroot and repair](https://pve.proxmox.com/wiki/Recover_From_Grub_Failure#Chroot_and_repair) * [2 Recovering from grub "disk not found" error when booting from LVM](https://pve.proxmox.com/wiki/Recover_From_Grub_Failure#Recovering_from_grub_%22disk_not_found%22_error_when_booting_from_LVM) * [2.1 PVE 7.x](https://pve.proxmox.com/wiki/Recover_From_Grub_Failure#PVE_7.x) * [2.1.1 Temporary Workaround](https://pve.proxmox.com/wiki/Recover_From_Grub_Failure#Temporary_Workaround) * [2.1.2 Permanent Fix](https://pve.proxmox.com/wiki/Recover_From_Grub_Failure#Permanent_Fix) * [2.2 PVE 8](https://pve.proxmox.com/wiki/Recover_From_Grub_Failure#PVE_8) * [2.2.1 Temporary Workaround](https://pve.proxmox.com/wiki/Recover_From_Grub_Failure#Temporary_Workaround_2) * [2.2.2 Permanent Fix](https://pve.proxmox.com/wiki/Recover_From_Grub_Failure#Permanent_Fix_2) General advice -------------- The following article provides pointers how to prepare a `chroot` environment for Proxmox VE systems, when repairing issues with boot-loaders. One example is finding oneself confronted with: * `grub rescue >` You can use the current Proxmox installation ISO and select debug mode. On the second prompt you'll have the full Linux tools, including LVM, ZFS, ..., available mounting your filesystems and entering a `chroot` for repair. (After you exit that prompt (using Ctrl+D or `exit`) you will come to the installation screens, simply hit abort there and reset the system). Alternatively, one can use a 64 bit version of Ubuntu or Debian Rescue CD, if you do not use ZFS as root filesystem (as this is usually not available in most rescue CDs). The following commands need to be run as `root` or using `sudo` or similar. We will use `/media/RESCUE` as mountpoint for the root-fs, and `/dev/sdX` as device on which Proxmox VE is installed in the examples. Create the mountpoint: mkdir /media/RESCUE ### LVM (Ext4/XFS) based systems Enable the volume-group and all LVs within: vgscan vgchange -ay Mount the relevant filesystems Your paths will vary depending on your drive configuration. mount /dev/pve/root /media/RESCUE/ ### ZFS based systems Import the pool with alternative root: zpool import -f -R /media/RESCUE rpool As the `hostid` in the installer is different, you will need to run `zpool import -f rpool` in the initramfs once after booting back into your system. ### Mount relevant filesystems and hostpaths mount -o rbind /proc /media/RESCUE/proc mount -o rbind /sys /media/RESCUE/sys mount -o rbind /dev /media/RESCUE/dev mount -o rbind /run /media/RESCUE/run ### Chroot and repair Chroot into your install. chroot /media/RESCUE Inside the `chroot` first check if your system is using `proxmox-boot-tool`: proxmox-boot-tool status If it is not used it will print: E: /etc/kernel/proxmox-boot-uuids does not exist. * If `proxmox-boot-tool` is used then run: proxmox-boot-tool reinit * If not - then mount the ESP and reinistall grub: mount /dev/sdX2 /boot/efi grub-install /dev/sdX If there are no error messages, you should be able to reboot now. Credit: [https://www.nerdoncoffee.com/operating-systems/re-install-grub-on-proxmox/](https://www.nerdoncoffee.com/operating-systems/re-install-grub-on-proxmox/) Recovering from grub "disk not found" error when booting from LVM ----------------------------------------------------------------- This section applies to the following setups: * PVE 7.4 (or earlier) hosts with their boot disk on LVM * PVE 8 hosts that have their boot disk on LVM, boot in UEFI mode and were upgraded from PVE 7 In these setups, the host might end up in a state in which grub fails to boot and prints an error ``disk `lvmid//` not found``. An example (of course, the UUIDs vary): Welcome to GRUB! error: disk \`lvmid/p3y5O2-jync-R2Ao-Gtlj-It3j-FZXE-ipEDYG/bApewq-qSRB-zYqT-mzvP-pGiV-VQaf-di4Rcz\` not found. grub rescue> This error "disk \`...\` not found" error is originally [caused by a grub bug](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987008) . LVM metadata is stored on-disk in a ring buffer, so occasionally the current metadata will wrap around the end of the ring buffer. However, if there is a wraparound in the ring buffer, grub fails to parse the metadata and fails to boot with the above error. The recommended steps differ between the PVE 7.4 and PVE 8. ### PVE 7.x This subsection applies to PVE 7.4 (or earlier) hosts with their boot disk on LVM. PVE 7.4 ships `grub 2.06-3~deb11u5` which is affected by the [bug](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987008) (though earlier versions may also be affected). This was also reported multiple times in the forum already, see [here](https://forum.proxmox.com/threads/98761/) and [here](https://forum.proxmox.com/threads/123512/) . #### Temporary Workaround In order to **temporarily** work around this bug and get the host to a bootable state again, it is sufficient to trigger an LVM metadata update. The updated metadata will reside in one contiguous section of the metadata ring buffer, so no wraparound occurs anymore. grub will then be able to parse the metadata correctly and boot again. One simple way to trigger an LVM metadata update is to create a small logical volume: * Boot from a live USB/CD/DVD with LVM support, e.g. [grml](https://grml.org/) * Run `vgscan` * Create a 4MB logical volume named `grubtemp` in the `pve` volume group: `lvcreate -L 4M pve -n grubtemp` * Reboot. PVE should boot normally again. * You can now remove the `grubtemp` volume: `lvremove pve/grubtemp` Note that there are many other options for triggering a metadata update, e.g. using `lvchange` to extend an existing logical volume or add a tag to an existing logical volume. The workaround is only temporary: If the host is (re)booted at a time when there is again a wraparound in the metadata ring buffer, grub will fail to boot again. On a running PVE system, you can check whether there is a wraparound in the metadata ring buffer using the following command: vgscan -vvv 2>&1 | grep "Reading metadata" If the output lines end with `(+0)`, there is no wraparound. If they end with `(+N)` for any other number `N`, there is a wraparound and the grub will most likely fail to boot after a reboot. #### Permanent Fix The only **permanent** fix for PVE 7.x is: * Apply the temporary workaround to be able to boot PVE again * Upgrade to PVE 8 by following the [upgrade guide](https://pve.proxmox.com/wiki/Upgrade_from_7_to_8 "Upgrade from 7 to 8") . ### PVE 8 This subsection applies to PVE 8 hosts that have their boot disk on LVM, boot in UEFI mode and were upgraded from PVE 7. PVE 8 ships `grub 2.06-13` in which the [grub bug](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987008) is fixed. However, on hosts that boot in UEFI mode and were upgraded from PVE 7, it can happen that the updated grub 2.06-13 EFI binary is not installed to the EFI system partition (ESP) at `/boot/efi/EFI/proxmox/grubx64.efi`. As a result, when booting in UEFI mode, the host still runs the older `grub 2.06-3~deb11u5` binary that is affected by the grub bug. To find out whether this is the case, check its mtime using `ls -l /boot/efi/EFI/proxmox/grubx64.efi`. If it is older than the time of the upgrade from PVE 7 to 8, the host still runs the older grub binary when booting in UEFI mode. #### Temporary Workaround The temporary workaround for PVE 8 to get the host in a bootable state [is the same as for PVE 7.x (see above)](https://pve.proxmox.com/wiki/Recover_From_Grub_Failure#Temporary_Workaround) . #### Permanent Fix The issue can be fixed permanently on PVE 8 by installing the correct grub metapackage for UEFI and choosing the correct UEFI boot entry. First, apply the [temporary workaround](https://pve.proxmox.com/wiki/Recover_From_Grub_Failure#Temporary_Workaround) to be able to boot into PVE 8 again. When booted into PVE 8, run the following command. It checks if the host is indeed booted in UEFI mode, and if yes, installs the correct grub metapackage for UEFI: \[ -d /sys/firmware/efi \] && apt install grub-efi-amd64 This will remove the `grub-pc` package, and update the binary on the ESP. You can verify that the mtime of `/boot/efi/EFI/proxmox/grubx64.efi` was updated. Note that this will not update the default EFI binary at `/boot/efi/EFI/BOOT/BOOTx64.EFI`, which might still be the grub binary that is affected by the bug. Consequently, make sure that you select the `proxmox` boot entry when booting in UEFI mode. If needed, you can adjust the boot order directly in the UEFI firmware or using the `efibootmgr` tool (see [its manpage](https://manpages.debian.org/stable/efibootmgr/efibootmgr.8.en.html#Changing_the_boot_order) ). Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Recover\_From\_Grub\_Failure&oldid=12337](https://pve.proxmox.com/mediawiki/index.php?title=Recover_From_Grub_Failure&oldid=12337) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Ports - Proxmox VE Ports ===== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Ports#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Ports#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Ports#Introduction) * [2 Proxmox VE 6.x and later port list](https://pve.proxmox.com/wiki/Ports#Proxmox_VE_6.x_and_later_port_list) * [3 Proxmox VE 4.x and later port list](https://pve.proxmox.com/wiki/Ports#Proxmox_VE_4.x_and_later_port_list) * [4 Proxmox VE 3.x port list](https://pve.proxmox.com/wiki/Ports#Proxmox_VE_3.x_port_list) * [5 Proxmox VE 2.x and earlier port list](https://pve.proxmox.com/wiki/Ports#Proxmox_VE_2.x_and_earlier_port_list) Introduction ------------ Proxmox VE host needs firewall protection. The default installation uses the Proxmox VE Firewall, which is not activated by default. Set up your [Proxmox VE Firewall](https://pve.proxmox.com/wiki/Proxmox_VE_Firewall "Proxmox VE Firewall") the way it fits your needs. For additional protection use an external hardware firewall. Proxmox VE 6.x and later port list ---------------------------------- See official docs: [https://pve.proxmox.com/pve-docs/pve-admin-guide.html#\_ports\_used\_by\_proxmox\_ve](https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_ports_used_by_proxmox_ve) Proxmox VE 4.x and later port list ---------------------------------- * Web interface: 8006 * pvedaemon (listens only on 127.0.0.1): 85 * SPICE proxy: 3128 * sshd (used for cluster actions): 22 * rpcbind: 111 * corosync multicast (if you run a cluster): 5404, 5405 UDP Proxmox VE 3.x port list ------------------------ * Web interface: 8006 * VNC Web console: 5900-5999 * SPICE console: 3128 * SSH access (only optional): 22 * CMAN multicast (if you run a cluster): 5404, 5405 UDP Proxmox VE 2.x and earlier port list ------------------------------------ * Web interface: 443 * VNC Web console: 5900-5999 * SSH access (only optional): 22 Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Ports&oldid=11362](https://pve.proxmox.com/mediawiki/index.php?title=Ports&oldid=11362) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Installation](https://pve.proxmox.com/wiki/Category:Installation "Category:Installation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Win7 Guest DHCP not working fix - Proxmox VE Win7 Guest DHCP not working fix =============================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Win7_Guest_DHCP_not_working_fix#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Win7_Guest_DHCP_not_working_fix#searchInput) If you have problem with Win7 or Win2012 KVM guest with dhcp not working, you can try to disable checksum offloading * Click Start - Search and type “regedit”. * Go to the following registry key: HKEY\_LOCAL\_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\Tcpip\\Parameters * Add a DWORD(32bit) Value named "DisableTaskOffload" and set it to "1". * Restart the Windows PC to make the changes happen. ### Custom NIC Checksum Settings If you need to set NIC checksum only for IPv4/Pv6, TCP/UDP, RX/TX you can use the NIC Advanced setting here: [![](https://pve.proxmox.com/mediawiki/images/9/94/NIC_Checksum.jpg)](https://pve.proxmox.com/wiki/File:NIC_Checksum.jpg) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Win7\_Guest\_DHCP\_not\_working\_fix&oldid=9144](https://pve.proxmox.com/mediawiki/index.php?title=Win7_Guest_DHCP_not_working_fix&oldid=9144) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Troubleshooting](https://pve.proxmox.com/wiki/Category:Troubleshooting "Category:Troubleshooting") * [Qemu/KVM](https://pve.proxmox.com/wiki/Category:Qemu/KVM "Category:Qemu/KVM") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Getting Help - Proxmox VE Getting Help ============ From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Getting_Help#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Getting_Help#searchInput) Proxmox VE Wiki --------------- The primary source of information is the [Proxmox VE Wiki](https://pve.proxmox.com/wiki/) . It combines the reference documentation with user contributed content. Community Support Forum ----------------------- Proxmox VE itself is fully open source, so we always encourage our users to discuss and share their knowledge using the [Proxmox VE Community Forum](https://forum.proxmox.com/) . The forum is moderated by the Proxmox support team, and has a large user base from all around the world. Needless to say, such a large forum is a great place to get information. Mailing Lists ------------- This is a fast way to communicate with the Proxmox VE community via email. * Mailing list for users: [Proxmox VE User List](http://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user) Proxmox VE is fully open source and contributions are welcome! The primary communication channel for developers is the: * Mailing list for developers: [Proxmox VE development discussion](http://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel) Commercial Support ------------------ Proxmox Server Solutions GmbH also offers enterprise support available as [Proxmox VE Subscription Service Plans](https://proxmox.com/en/proxmox-virtual-environment/pricing) . All users with a subscription get access to the Proxmox VE [Enterprise Repository](https://pve.proxmox.com/wiki/Package_Repositories#sysadmin_enterprise_repo) , and—with a Basic, Standard or Premium subscription—also to the Proxmox Customer Portal. The customer portal provides help and support with guaranteed response times from the Proxmox VE developers. For volume discounts, or more information in general, please contact [sales@proxmox.com](mailto:sales@proxmox.com) . Bug Tracker ----------- Proxmox runs a public bug tracker at [https://bugzilla.proxmox.com](https://bugzilla.proxmox.com/) . If an issue appears, file your report there. An issue can be a bug as well as a request for a new feature or enhancement. The bug tracker helps to keep track of the issue and will send a notification once it has been solved. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Getting\_Help&oldid=11947](https://pve.proxmox.com/mediawiki/index.php?title=Getting_Help&oldid=11947) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Reference Documentation](https://pve.proxmox.com/wiki/Category:Reference_Documentation "Category:Reference Documentation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # USB Redirector - Proxmox VE USB Redirector ============== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/USB_Redirector#mw-head) [Jump to search](https://pve.proxmox.com/wiki/USB_Redirector#searchInput) For more recent versions of Proxmox, see [USB physical port mapping](https://pve.proxmox.com/wiki/USB_physical_port_mapping "USB physical port mapping") . * * * When trying to use USB and especially USB2 devices in a KVM VM it's most likely that you will fail because qemu/KVM does not support USB pass thru too well. But there is a solution for this problem: The Incentives Pro USB Redirector [http://www.incentivespro.com](http://www.incentivespro.com/) The Linux part is free, the Windows part is not. But when you need reliable support for devices connected to the server in a KVM Windows VM it's worth the few bucks. The Linux part of the software consists of the following components: * a kernel module(tusbd.ko) * a daemon (usbsrvd) * a control application (usbsrv) Currently (01/2011) there are a few problems with the setup of the kernel module because the official source code of USB Redirector is not up to date and does not work out of the box wicht current kernels - e.g. 2.6.35. You need: * the official distribution source: [http://incentivespro.com/usb-server-x64.tar.gz](http://incentivespro.com/usb-server-x64.tar.gz) * a more recent version of tusdb.ko source: [http://incentivespro.com/tusbd2.6.31.zip](http://incentivespro.com/tusbd2.6.31.zip) * a patch for the 2.6.31 version: [http://www.fnarfbargle.com/tusbd-2.6.36.patch.gz](http://www.fnarfbargle.com/tusbd-2.6.36.patch.gz) ### Setup The following asumes that all files are located in /tmp. First resolve the dependencies. You require a basic development environment: apt-get install build-essential pve-headers-\`uname -r\` then extract the base distribution: cd /tmp tar xfz usb-server-x64.tar.gz unzip the replacement kernel module source: unzip tusbd2.6.31.zip and copy it to it's destination: cd tusbd2.6.3 cp \* /tmp/usb-server/modules/src/tusbd/ now patch the source: cd /tmp/usb-server/modules/src/tusbd/ zcat /tmp/tusbd-2.6.36.patch.gz | patch -p1 the patch should apply with out any rejects. The last step is to patch the installer. Go to the main folder: cd /tmp/usb-server and edit the intaller by: sed -i 's/KERNELDIR=\\/usr\\/src\\/linux/KERNELDIR=\\/usr\\/src\\/linux-headers-\`uname -r\`/' installer.sh now you are ready to do the install by: ./installer.sh It should show no errors and report success. Now you are ready to share connected USB devices. First list the detected devices: usbsrv -l this displays some thing like this: \================= USB SERVER OPERATION SUCCESSFUL =============== List of USB devices: 1: SE USB Device ServerEngines / Composite USB Device Vid: 0000 Pid: 0000 Port: 6-1 Status: plugged 2: Wireless Desktop MLK / Composite USB Device Vid: 046a Pid: 0101 Port: 8-2 Status: plugged 3: FreeAgent Go Seagate / USB Mass Storage Device Vid: 0bc2 Pid: 2101 Port: 1-3.3 Status: plugged 4: FreeAgent Go Seagate / USB Mass Storage Device Vid: 0bc2 Pid: 2101 Port: 1-3.4 Status: plugged 5: CANON DR-5010C CANON Vid: 04a9 Pid: 1606 Port: 2-5 Status: not plugged, shared ===================== ======================= =================== If you want to share the Canon Scanner do: usbsrv -share 5 where 5 is the ID of the device showen in the listing. Completely redundant is: usbsrv -share -vid 04a9 -pid 1606 -usbport 2-5 Now you are ready to connect the Windows client. For a how to see: [http://www.incentivespro.com/usb-redirector.html](http://www.incentivespro.com/usb-redirector.html) ### Links [http://forum.proxmox.com/threads/4719-BSOD-with-USB-device-passthrough-on-Windows-XP-virtual-machine](http://forum.proxmox.com/threads/4719-BSOD-with-USB-device-passthrough-on-Windows-XP-virtual-machine) [http://www.incentivespro.com/forum/viewtopic.php?t=295&highlight=64bit](http://www.incentivespro.com/forum/viewtopic.php?t=295&highlight=64bit) [http://www.incentivespro.com/forum/viewtopic.php?t=512](http://www.incentivespro.com/forum/viewtopic.php?t=512) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=USB\_Redirector&oldid=5594](https://pve.proxmox.com/mediawiki/index.php?title=USB_Redirector&oldid=5594) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # SPICE - Proxmox VE SPICE ===== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/SPICE#mw-head) [Jump to search](https://pve.proxmox.com/wiki/SPICE#searchInput) [![](https://pve.proxmox.com/mediawiki/images/thumb/6/62/Screen-enable-spice.png/600px-Screen-enable-spice.png)](https://pve.proxmox.com/wiki/File:Screen-enable-spice.png) Enable SPICE [![](https://pve.proxmox.com/mediawiki/images/thumb/e/e0/Screen-start-spice-viewer.png/600px-Screen-start-spice-viewer.png)](https://pve.proxmox.com/wiki/File:Screen-start-spice-viewer.png) Start SPICE console [![](https://pve.proxmox.com/mediawiki/images/thumb/2/26/Spice_Add_USB_Device.png/600px-Spice_Add_USB_Device.png)](https://pve.proxmox.com/wiki/File:Spice_Add_USB_Device.png) Add USB Device for passthrough from the client [![](https://pve.proxmox.com/mediawiki/images/thumb/a/a9/Audio_Devices.png/600px-Audio_Devices.png)](https://pve.proxmox.com/wiki/File:Audio_Devices.png) Add an audio device to a VM Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/SPICE#Introduction) * [2 Requirements for SPICE](https://pve.proxmox.com/wiki/SPICE#Requirements_for_SPICE) * [3 SPICE client](https://pve.proxmox.com/wiki/SPICE#SPICE_client) * [4 Enable SPICE for a VM](https://pve.proxmox.com/wiki/SPICE#Enable_SPICE_for_a_VM) * [4.1 Caution](https://pve.proxmox.com/wiki/SPICE#Caution) * [5 OS specific settings for VM](https://pve.proxmox.com/wiki/SPICE#OS_specific_settings_for_VM) * [5.1 Windows](https://pve.proxmox.com/wiki/SPICE#Windows) * [5.1.1 Windows 7/8/10 and Windows 2012/2016](https://pve.proxmox.com/wiki/SPICE#Windows_7/8/10_and_Windows_2012/2016) * [5.2 Linux](https://pve.proxmox.com/wiki/SPICE#Linux) * [6 Start your SPICE session](https://pve.proxmox.com/wiki/SPICE#Start_your_SPICE_session) * [7 Using client USB devices](https://pve.proxmox.com/wiki/SPICE#Using_client_USB_devices) * [7.1 Caution](https://pve.proxmox.com/wiki/SPICE#Caution_2) * [8 Using Audio](https://pve.proxmox.com/wiki/SPICE#Using_Audio) * [9 SPICE Enhancements](https://pve.proxmox.com/wiki/SPICE#SPICE_Enhancements) * [10 Troubleshooting](https://pve.proxmox.com/wiki/SPICE#Troubleshooting) * [10.1 Can't start Spice session](https://pve.proxmox.com/wiki/SPICE#Can't_start_Spice_session) * [10.2 Guest resolution does not resize to Remote Viewer window](https://pve.proxmox.com/wiki/SPICE#Guest_resolution_does_not_resize_to_Remote_Viewer_window) * [11 Alternatives](https://pve.proxmox.com/wiki/SPICE#Alternatives) * [12 Video Tutorials](https://pve.proxmox.com/wiki/SPICE#Video_Tutorials) Introduction ------------ [SPICE](http://www.spice-space.org/) (Simple Protocol for Independent Computing Environments) is an open remote computing solution built for virtual environments which allows users to view a computing "desktop" environment. The integrating of Spice into Proxmox VE provides a solution for interaction with virtualized desktop devices, like keyboard, mouse, audio and video. Interaction between front-end and back-end is done using Virtual Device Interfaces (VDI). Spice achieves a user experience similar to an interaction with a local machine. It is suitable for both LAN and WAN usage, without compromising on the user experience. Using Spice on Proxmox VE is easy and secure. It is integrated in the cluster environment, the user- and authentication system - and of course, all traffic is fully encrypted. Spice was first introduced with Proxmox VE 3.1. Requirements for SPICE ---------------------- In order to use Spice you need the following: * Spice client on your desktop OS * Spice drivers inside your VM (VirtIO, QXL Graphic card drivers) SPICE client ------------ * Windows: virt-viewer 0.5.6 or higher, [http://www.spice-space.org/download.html](http://www.spice-space.org/download.html) * Linux: virt-viewer 0.5.6 or higher * OS X (not yet working as expected): virt-viewer 0.5.7 or higher, [https://www.spice-space.org/osx-client.html](https://www.spice-space.org/osx-client.html) Enable SPICE for a VM --------------------- Spice is not enabled by default. To enable it set the Display in the Hardware section of the VM to Spice (shown in the screenshot at the top). Increase the memory if you intend to use SPICE with high resolutions. 32 MiB is plenty for 4K resolutions. #### Caution Before changing the Display setting to SPICE check the following section. You may need to install QXL/SPICE drivers depending on the guest OS. OS specific settings for VM --------------------------- ### Windows #### Windows 7/8/10 and Windows 2012/2016 Fully supported. Before you switch the Display to SPICE install the Windows SPICE guest tools 0.132 or higher (spice-guest-tools-0.132.exe or higher) * [http://www.spice-space.org/download.html](http://www.spice-space.org/download.html) ### Linux All Linux distributions released after 2011 have the necessary qxl driver included as a part of the Xorg package. Start your SPICE session ------------------------ A Spice session can be started by clicking directly on the Console button or by opening the Console sub menu and selecting Spice explicitly. This will trigger the download of the connection config file. Open this file with Remote Viewer to start the session. The association is automatic for Chrome and Internet Explorer (they use the mime type association from the OS). For Firefox, the association must be done manually, as Firefox has his own internal mime type association (See Options/Applications). Using client USB devices ------------------------ You can pass USB devices from the client into the VM. Add a USB device of the type _Spice Port_ in the Hardware section of the VM. Old methods of editing the config file directly are not necessary anymore with recent versions of Proxmox VE. #### Caution * The Windows version of the virt-viewer does not support it. Using Audio ----------- Audio devices can be added in the Hardware section of the VM. Three audio devices are supported: * ich9-intel-hda: emulates Intel HDA Audio on ICH9 chipsets * intel-hda: emulates Intel HDA Audio on ICH6 chipsets. Use if the ICH9 one does not work properly * AC97: useful for older OS\`s like Windows XP Manually editing the config file of the VM is not necessary with recent versions of Proxmox VE. SPICE Enhancements ------------------ SPICE Enhancements are optional features that can improve the remote viewer experience. They can be enabled in the Options panel of a VM. Two enhancements are currently available: * Foldersharing * Videostreaming Foldersharing enables you to share a local folder with the VM you are connecting to. The "spice-webdavd" daemon needs to be installed in the VM. **HINT:** only the Linux version of Virt-viewer (remote-viewer) supports this. Videostreaming will encode fast refreshing areas in a lossy video stream. A general recommendation cannot be given but depending on your situation this can greatly improve the performance. More information can be found in the reference manual by clicking the "Help" button in the dialog to enable the enhancements. Troubleshooting --------------- #### Can't start Spice session If you can't start a Spice session from the PVE Web gui, you can try the following shell script: [https://git.proxmox.com/?p=pve-manager.git;a=blob\_plain;f=spice-example-sh;hb=HEAD](https://git.proxmox.com/?p=pve-manager.git;a=blob_plain;f=spice-example-sh;hb=HEAD) #### Guest resolution does not resize to Remote Viewer window Make sure the _spice-vdagent_ service is installed and running in the VM. If the guest stops resizing once you go higher than a certain size it is possible that the video memory is not enough. Increase the Memory settings of the Display in the Hardware section of the VM by a few MiB. For the changes to take effect you have to shutdown the VM and do a clean start. Alternatives ------------ Depending on your situation SPICE might not be the best solution. Alternatives are: * RDP (Remote Desktop Protocol) for Windows Guests * [X2GO](https://wiki.x2go.org/) for Linux Guests Video Tutorials --------------- * [Proxmox VE Youtube channel](http://www.youtube.com/user/ProxmoxVE) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=SPICE&oldid=10600](https://pve.proxmox.com/mediawiki/index.php?title=SPICE&oldid=10600) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Staging](https://pve.proxmox.com/mediawiki/index.php?title=Category:Staging&action=edit&redlink=1 "Category:Staging (page does not exist)") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Install Proxmox VE on Debian Buster - Proxmox VE Install Proxmox VE on Debian Buster =================================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster#Introduction) * [2 Install a standard Debian Buster (amd64)](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster#Install_a_standard_Debian_Buster_(amd64)) * [2.1 Add an /etc/hosts entry for your IP address](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster#Add_an_/etc/hosts_entry_for_your_IP_address) * [3 Install Proxmox VE](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster#Install_Proxmox_VE) * [3.1 Adapt your sources.list](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster#Adapt_your_sources.list) * [3.2 Install Proxmox VE packages](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster#Install_Proxmox_VE_packages) * [3.2.1 Recommended: remove the os-prober package](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster#Recommended:_remove_the_os-prober_package) * [3.2.2 Recommended: install ifupdown2](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster#Recommended:_install_ifupdown2) * [4 Connect to the Proxmox VE web interface](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster#Connect_to_the_Proxmox_VE_web_interface) * [5 Troubleshooting](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster#Troubleshooting) * [5.1 resolv.conf gets overwritten](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster#resolv.conf_gets_overwritten) * [5.2 ipcc\_send\_rec\[1\] failed](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster#ipcc_send_rec[1]_failed) * [6 Recommended Optional Steps](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster#Recommended_Optional_Steps) * [6.1 Optional: Remove the Debian kernel](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster#Optional:_Remove_the_Debian_kernel) * [6.2 Optional: Install ifupdown2](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster#Optional:_Install_ifupdown2) Introduction ------------ The installation of a supported Proxmox VE server should be done via Bare-metal\_ISO\_Installer. In some cases it makes sense to install Proxmox VE on top of a running Debian Buster 64-bit, especially if you want a custom partition layout. For this How-To we used the 10.8 Debian Buster netinst ISO[\[1\]](https://cdimage.debian.org/mirror/cdimage/archive/10.8.0/amd64/iso-cd/debian-10.8.0-amd64-netinst.iso) , but any official Buster installation medium should work. Install a standard Debian Buster (amd64) ---------------------------------------- Install a standard Debian Buster, for details see [Debian](https://www.debian.org/releases/stable/amd64/index.en.html) , and configure a static IP. It is recommended to only install the "standard" package selection, and nothing else, as Proxmox VE brings its own packages for qemu, lxc. A desktop environment is not necessary. ### Add an /etc/hosts entry for your IP address Please make sure that your machine's hostname is resolvable via `/etc/hosts`, _i.e._ you need an entry in `/etc/hosts` which assigns an address to its hostname. Make sure that you have configured one of the following addresses in `/etc/hosts` for your hostname: * 1 IPv4 or * 1 IPv6 or * 1 IPv4 and 1 IPv6 **Note**: This also means removing the address `127.0.1.1` that might be present as default. For instance, if your IP address is `192.168.15.77`, and your hostname `prox4m1`, then your `/etc/hosts` file could look like: 127.0.0.1 localhost.localdomain localhost 192.168.15.77 prox4m1.proxmox.com prox4m1 # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters You can test if your setup is ok using the `hostname` command: hostname --ip-address 192.168.15.77 # should return your IP address here Install Proxmox VE ------------------ ### Adapt your sources.list Add the Proxmox VE repository: echo "deb \[arch=amd64\] [http://download.proxmox.com/debian/pve](http://download.proxmox.com/debian/pve) buster pve-no-subscription" > /etc/apt/sources.list.d/pve-install-repo.list Add the Proxmox VE repository key: wget [http://download.proxmox.com/debian/proxmox-ve-release-6.x.gpg](http://download.proxmox.com/debian/proxmox-ve-release-6.x.gpg) -O /etc/apt/trusted.gpg.d/proxmox-ve-release-6.x.gpg chmod +r /etc/apt/trusted.gpg.d/proxmox-ve-release-6.x.gpg # optional, if you have a non-default umask Update your repository and system by running: apt update && apt full-upgrade ### Install Proxmox VE packages Install the Proxmox VE packages apt install proxmox-ve postfix open-iscsi Configure packages which require user input on installation according to your needs (e.g. Samba asking about WINS/DHCP support). If you have a mail server in your network, you should configure postfix as a **satellite system**, your existing mail server will then be the _relay host_ which will route the emails sent by the Proxmox server to their final recipient. If you don't know what to enter here, choose **local only** and leave the _system name_ as is. Finally, reboot your system, the new Proxmox VE kernel should be automatically selected in the GRUB menu. **Note**: If you have a subscription key don't forget to switch to the enterprise repository after installation, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") . #### Recommended: remove the os-prober package The os-prober package scans all the partitions of your host, including those assigned to guests VMs, to create dual-boot GRUB entries. If you didn't install Proxmox VE as dual boot beside another Operating System, you can safely remove the os-prober package. apt remove os-prober #### Recommended: install ifupdown2 With `ifupdown2` you can apply a new network configuration to the host without rebooting it. apt install ifupdown2 The old package, `ifupdown` will be removed. Connect to the Proxmox VE web interface --------------------------------------- Connect to the admin web interface (https://youripaddress:8006). If you have a fresh install and didn't add any users yet, you should use the root account with your linux root password, and select "PAM Authentication" to log in. Once logged in, create a `Linux Bridge` called `vmbr0`, and add your first network interface to it. [![Adapt vmbr0 settings](https://pve.proxmox.com/mediawiki/images/8/84/Screen-vmbr0-setup-for-ext6.png)](https://pve.proxmox.com/wiki/File:Screen-vmbr0-setup-for-ext6.png "Adapt vmbr0 settings") Troubleshooting --------------- ### resolv.conf gets overwritten The PVE GUI expects to control DNS management and will no longer take its DNS settings from `/etc/network/interfaces`. Any package that auto-generates (overwrites) `/etc/resolv.conf` will cause DNS to fail, e.g. packages 'resolvconf' for IPv4 and 'rdnssd' for IPv6. ### ipcc\_send\_rec\[1\] failed If you see ipcc\_send\_rec\[1\] failed: Connection refused then you should review your `/etc/hosts` file according to the instructions above. Recommended Optional Steps -------------------------- ### Optional: Remove the Debian kernel apt remove linux-image-amd64 'linux-image-4.19\*' Update and check grub2 config by running: update-grub ### Optional: Install ifupdown2 With `ifupdown2` you can apply a new network configuration to the host without rebooting it. apt install ifupdown2 The old package, `ifupdown` will be removed. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Install\_Proxmox\_VE\_on\_Debian\_Buster&oldid=11374](https://pve.proxmox.com/mediawiki/index.php?title=Install_Proxmox_VE_on_Debian_Buster&oldid=11374) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Installation](https://pve.proxmox.com/wiki/Category:Installation "Category:Installation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "QEMU/KVM Virtual Machines" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "QEMU/KVM Virtual Machines" ============================================== ← [QEMU/KVM Virtual Machines](https://pve.proxmox.com/wiki/QEMU/KVM_Virtual_Machines "QEMU/KVM Virtual Machines") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/QEMU/KVM_Virtual_Machines#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/QEMU/KVM_Virtual_Machines#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[QEMU/KVM Virtual Machines](https://pve.proxmox.com/wiki/QEMU/KVM_Virtual_Machines "QEMU/KVM Virtual Machines") **: Displaying 2 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/QEMU/KVM_Virtual_Machines&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/QEMU/KVM_Virtual_Machines&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/QEMU/KVM_Virtual_Machines&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/QEMU/KVM_Virtual_Machines&limit=500) ) * [Main Page](https://pve.proxmox.com/wiki/Main_Page "Main Page") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Main+Page "Special:WhatLinksHere") ) * [NVIDIA vGPU on Proxmox VE](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE "NVIDIA vGPU on Proxmox VE") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=NVIDIA+vGPU+on+Proxmox+VE "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/QEMU/KVM_Virtual_Machines&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/QEMU/KVM_Virtual_Machines&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/QEMU/KVM_Virtual_Machines&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/QEMU/KVM_Virtual_Machines&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/QEMU/KVM\_Virtual\_Machines](https://pve.proxmox.com/wiki/Special:WhatLinksHere/QEMU/KVM_Virtual_Machines) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Full Mesh Network for Ceph Server - Proxmox VE Full Mesh Network for Ceph Server ================================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Introduction) * [1.1 Failure Scenarios](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Failure_Scenarios) * [1.1.1 Loss of a Node](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Loss_of_a_Node) * [1.1.2 Loss of a Connection](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Loss_of_a_Connection) * [2 Example](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Example) * [3 Routed Setup (with Fallback)](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Routed_Setup_(with_Fallback)) * [3.1 Using SDN Fabrics](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Using_SDN_Fabrics) * [3.2 Manual](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Manual) * [3.2.1 /etc/frr/daemons](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#/etc/frr/daemons) * [3.2.2 /etc/frr/frr.conf](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#/etc/frr/frr.conf) * [3.2.3 /etc/network/interfaces](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#/etc/network/interfaces) * [3.2.4 Ceph Initialization](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Ceph_Initialization) * [4 Routed Setup (Simple)](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Routed_Setup_(Simple)) * [4.1 Node1](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Node1) * [4.1.1 /etc/network/interface](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#/etc/network/interface) * [4.1.2 Route](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Route) * [4.2 Node2](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Node2) * [4.2.1 /etc/network/interface](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#/etc/network/interface_2) * [4.2.2 Route](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Route_2) * [4.3 Node3](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Node3) * [4.3.1 /etc/network/interface](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#/etc/network/interface_3) * [4.3.2 Route](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Route_3) * [5 RSTP Loop Setup](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#RSTP_Loop_Setup) * [5.1 /etc/network/interface](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#/etc/network/interface_4) * [6 Broadcast Setup](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Broadcast_Setup) * [6.1 GUI](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#GUI) * [6.2 Command-Line](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Command-Line) Introduction ------------ This wiki page describes how to configure a three node ["Meshed Network"](https://en.wikipedia.org/wiki/Mesh_networking) Proxmox VE (or any other Debian based Linux distribution), which can be, for example, used for connecting [Ceph Servers](https://pve.proxmox.com/wiki/Deploy_Hyper-Converged_Ceph_Cluster "Deploy Hyper-Converged Ceph Cluster") or nodes in a [Proxmox VE Cluster](https://pve.proxmox.com/wiki/Cluster_Manager "Cluster Manager") with the maximum possible bandwidth and without using a switch. We recommend to use switches for clusters larger than 3 nodes or if a 3 node cluster should be expanded in the future. The big advantage of this setup is that you can achieve a fast network connection between the nodes (10, 25, 40 or 100Gbit/s) WITHOUT buying expensive switches which can handle these fast speeds. You need at least two available NICs in each server which each connect to one of the other servers. ┌───────┐ ┌────┤ Node1 ├────┐ │ └───────┘ │ ┌───┴───┐ ┌───┴───┐ │ Node2 ├─────────┤ Node3 │ └───────┘ └───────┘ There are a few possible ways to set up such a network: 1. [Routed (with fallback)](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Routed_Setup_(with_fallback)) : Each packet is sent to the addressed node only. If the direct connection is down, the packets will be routed via the node in between. 2. [Routed (simple)](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Routed_Setup_(simple)) : Each packet is sent to the addressed node only 3. [RSTP](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#RSTP_Loop_Setup) : A loop with the rapid spanning tree protocol enabled 4. [Broadcast](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Broadcast_setup) : Each packet is sent to both other nodes Each setup has benefits and caveats. The **simple routed** one does not need any additional software and delivers the best performance. The **routed with fallback** approach delivers similar performance but can handle the loss of one connection in the mesh by routing the traffic via the middle node. Because of this, performance could be impacted in such a scenario. The **RSTP** setup gives you similar fault tolerance as the routed setup with fallback. If the loop is complete, RSTP will create an artificial cut-off between two nodes, e.g. between Node 1 and Node 3. This means, Node 2 is in between Node 1 and 3 and the traffic between Node 1 and Node 3 is going via Node 2. Should a cable or NIC fail somewhere else, for example between Node 1 and Node 2, RSTP will remove the cut-off within a few seconds. Node 3 is now in between Node 1 and 2 and has to handle that traffic as well. Once the broken part has been replaced and the loop if complete again, RSTP will introduce another artificial cut-off. The advantage of the **broadcast** method is an easier setup process, but it will send all data to both other nodes, using up more bandwidth. ### Failure Scenarios #### Loss of a Node ┌───────┐ ┌────┤ Node1 ├────┐ │ └───────┘ │ ┌───┴───┐ ┌───┴───┐ │ Node2 ├─────────┤ XXXXX │ └───────┘ └───────┘ If a node is going down, for example Node 3, the Ceph and Proxmox VE cluster will remain functioning, though with reduced redundancy. #### Loss of a Connection ┌───────┐ ┌────┤ Node1 ├────┐ │ └───────┘ X ┌───┴───┐ ┌───┴───┐ │ Node2 ├─────────┤ Node3 │ └───────┘ └───────┘ If one of the connections is failing, for example between Node 1 and Node 3, the resulting behavior depends on the chosen setup variant. For the **RSTP** and **Routed (with fallback)**, everything will **stay functioning**. With RSTP it might take a short moment for it to remove the artificial cut-off. With a bit of luck, the artificial cut-off was exactly at the failed connection. When using the Routed (with fallback) setup, the traffic that used to go directly between Node 1 and Node 3 will now be routed via Node 2, resulting in a bit higher latency. This can have a bit of an impact on performance, but the cluster will stay fully functional. For the **Broadcast** and **Routed (simple)** setups, such a situation is more **problematic**, because the nodes now have a different view, Node 2 can communicate with Node 3, while that is not possible for Node 1 anymore. You will see behavior such as Ceph showing the services on Node 3 to be down. To reduce the chances of a failed connection, you could combine the Broadcast and Routed (simple) with a bond to increase fault tolerance at the cost of more NICs and cables. Example ------- 3 servers: * Node1 with IP addresses x.x.x.50 * Node2 with IP addresses x.x.x.51 * Node3 with IP addresses x.x.x.52 3 to 4 Network ports in each server: * ens18, ens19 will be used for the actual full mesh. Physical direct connections to the other two servers, 10.15.15.y/24 * ens20 connection to WAN (internet/router), using at vmbr0 192.168.2.y * ens21 (optional) LAN (for Proxmox VE cluster traffic, etc.) 10.14.14.y Direct connections between servers: * Node1/ens18 - Node2/ens19 * Node2/ens18 - Node3/ens19 * Node3/ens18 - Node1/ens19 Please adapt the NIC names and IP addresses according to your situation. ┌───────────┐ │ Node1 │ ├─────┬─────┤ │ens18│ens19│ └──┬──┴──┬──┘ │ │ ┌───────┬─────┐ │ │ ┌─────┬───────┐ │ │ens19├────────┘ └────────┤ens18│ │ │ Node2 ├─────┤ ├─────┤ Node3 │ │ │ens18├───────────────────────┤ens19│ │ └───────┴─────┘ └─────┴───────┘ Routed Setup (with Fallback) ---------------------------- We can make use of the OpenFabric protocol which _is a routing protocol derived from IS-IS, providing link-state routing_. [FRR](https://frrouting.org/) has a working [implementation](https://docs.frrouting.org/en/latest/fabricd.html) . ### Using SDN Fabrics Starting with PVE 9 it is possible to create fabrics from the GUI using the [Proxmox VE SDN](https://pve.proxmox.com/pve-docs/chapter-pvesdn.html) stack. ℹ️ **Note**: IP addresses used in this example are in the `10.15.15.0/24` subnet. Adapt this according to your situation. ℹ️ **Note**: If this setup is configured with virtualized nodes, ensure that the fabric interfaces on each node are either on separate bridges or use different VLANs. Otherwise, routing loops may occur. [![](https://pve.proxmox.com/mediawiki/images/thumb/a/a3/Gui-datacenter-fabrics-overview.png/600px-Gui-datacenter-fabrics-overview.png)](https://pve.proxmox.com/wiki/File:Gui-datacenter-fabrics-overview.png) To create the setup using the new SDN Fabrics, the following steps are necessary: 1. Navigate to the Datacenter → SDN → Fabrics panel 2. Create a new fabric using the "Add Fabric" button 3. Select which protocol the fabric will use, in this example _OpenFabric_. Proxmox VE currently supports OSPF and OpenFabric. For simple setups, such as this one, we recommend OpenFabric, as it's easier to set up than OSPF. 4. In the "Create: OpenFabric" window, enter the name of the fabric, for example _ceph_. This is used as an identifier for the fabric. 5. Enter an IPv4 and/or IPv6 prefix - for this example we create an IPv4 only fabric with the IPv4 prefix `10.15.15.0/24`. The IP prefix defines the subnet in which all IPs of the nodes are contained. 6. Optionally change the default values for the _Hello-Interval_ to 1 and _CSNP-Interval_ to 2. Lower numbers mean that the network will fail over faster in the case of link failures, but nodes will generate more traffic since the time between keep-alive messages is shorter. [![](https://pve.proxmox.com/mediawiki/images/b/b5/Gui-datacenter-create-fabric-openfabric.png)](https://pve.proxmox.com/wiki/File:Gui-datacenter-create-fabric-openfabric.png) Now it is time to add nodes to the fabric, in order to add Node 1 to the fabric the following steps are necessary: 1. Click the `+` button on the row of the fabric or select the fabric and click "_Add Node_" in the top bar. 2. This will open a window where you can select all available nodes in the cluster, the first node is already pre-selected. Only nodes that are not yet part of the fabric can be selected. 3. The next two input fields are for the IPv4 and IPv6 addresses of the node, which are also the _router-id_s. For our example, enter an IPv4 address from IP prefix of the fabric (`10.15.15.0/24`), for example `10.15.15.50`. The nodes will be reachable via the configured IP addresses inside the fabric. 4. Select the interfaces of the node that should be part of the fabric. In our example Node 1 uses `ens18` and `ens19`. Leave the other fields empty. If the interface has no IP address configured, it will operate in unnumbered mode (interface inherits the IP from the node). Optionally you can define dedicated IP addresses for the interfaces that will then be used instead of the router IP to create adjacencies between the nodes. 5. Repeat this for every node that should be part of the fabric. If there are more nodes to configure you can click on "Create Another", otherwise click 'Create' and the window will close. [![](https://pve.proxmox.com/mediawiki/images/thumb/b/b2/Gui-datacenter-create-node-openfabric.png/600px-Gui-datacenter-create-node-openfabric.png)](https://pve.proxmox.com/wiki/File:Gui-datacenter-create-node-openfabric.png) To finish and apply the changes navigate to the main SDN panel under Datacenter → SDN and use the "_Apply Configuration_" button. This will generate and apply the underlying FRR configuration on each node. To check if our fabric converges use the _vtysh_ FRR shell: vtysh OpenFabric neighbors and routes can be seen with the following commands: show openfabric neighbor show openfabric route To use this fabric as the underlying network for Ceph, do a regular installation of Ceph and make sure you select it in the initial configuration step for the Ceph network where it should show up in the drop-down list of available networks. ### Manual If we are using an older version of PVE or we want to manually create the fabric, we can follow these steps: ℹ️ **Note**: This will not work in combination with the EVPN functionality from the [Proxmox VE SDN](https://pve.proxmox.com/pve-docs/chapter-pvesdn.html) as it will overwrite our FRR configuration ℹ️ **Note**: If you install Ceph afterwards, you will have to do the initial Ceph configuration on the command line First ensure that FRR is installed: apt install frr #### /etc/frr/daemons Enable the OpenFabric daemon by changing the line in /etc/frr/daemons to "yes": \[...\] fabricd=yes \[...\] #### /etc/frr/frr.conf In this config file, 3 parameters need to be changed for each node: * hostname * IP address * NET The IP addresses, in our example, are the ones in the 10.15.15.y/24 network. The System ID in the NET (network entity title) needs to be unique. For example we can use the following ones for the three nodes: * 49.0001.1111.1111.1111.00 * 49.0001.2222.2222.2222.00 * 49.0001.3333.3333.3333.00 By configuring very short interval times, we can achieve almost instantaneous failover. \# default to using syslog. /etc/rsyslog.d/45-frr.conf places the log in # /var/log/frr/frr.log # # Note: # FRR's configuration shell, vtysh, dynamically edits the live, in-memory # configuration while FRR is running. When instructed, vtysh will persist the # live configuration to this file, overwriting its contents. If you want to # avoid this, you can edit this file manually before starting FRR, or instruct # vtysh to write configuration to a different file. frr defaults traditional hostname node1 log syslog warning ip forwarding no ipv6 forwarding service integrated-vtysh-config ! interface lo ip address 10.15.15.50/32 ip router openfabric 1 openfabric passive ! interface ens18 ip router openfabric 1 openfabric csnp-interval 2 openfabric hello-interval 1 openfabric hello-multiplier 2 ! interface ens19 ip router openfabric 1 openfabric csnp-interval 2 openfabric hello-interval 1 openfabric hello-multiplier 2 ! line vty ! router openfabric 1 net 49.0001.1111.1111.1111.00 lsp-gen-interval 1 max-lsp-lifetime 600 lsp-refresh-interval 180 ℹ️ **Note**: If the log level is set to _informational_, you might see log messages like OpenFabric: Initial synchronization on enp1s0f0np0 timed out! In that case, consider to increase the timeout values in each interface section for * csnp-interval * hello-interval * hello-multiplier and in the router section * lsp-gen-interval #### /etc/network/interfaces The network configuration itself is rather simple. We need to bring the interfaces used for the mesh network up. If we plan to use a large MTU, configure it here. ℹ️ **Note**: Starting with Proxmox VE 9, it is necessary to extend the post-up with a small check to avoid deadlocks in the service start ordering. auto lo iface lo inet loopback iface ens20 inet manual auto ens21 iface ens21 inet static address 10.14.14.51 netmask 255.255.255.0 auto vmbr0 iface vmbr0 inet static address 192.168.2.51 netmask 255.255.240.0 gateway 192.168.2.1 bridge\_ports ens20 bridge\_stp off bridge\_fd 0 post-up /usr/bin/systemctl is-active --quiet frr.service && /usr/bin/systemctl restart frr.service || true auto ens18 iface ens18 inet static mtu 9000 auto ens19 iface ens19 inet static mtu 9000 To apply the changes without a reboot, run the following commands: ifreload -a systemctl restart frr.service You can check the status via the FRR CLI. vtysh Then enter one of the commands detailed in the [FRR OpenFabric documentation](https://docs.frrouting.org/en/latest/fabricd.html#showing-openfabric-information) . For example, "show openfabric route". #### Ceph Initialization Since the IPs are configured in the FRR configuration and not in the /etc/network/interfaces file, the Ceph GUI configuration assistant won't show it to you. To do the initial Ceph configuration, run pveceph init --network 10.15.15.50/24 If you plan to use the Ceph Cluster Network on a different network, add the "--cluster-network" option. Next you will need to create the first monitor to get Ceph running. Either do that on the GUI or via the CLI on the node you just installed Ceph on with pveceph mon create Routed Setup (Simple) --------------------- The 3 nodes have to be configured as described in the following sections. Note that multicast is not possible with this method. ### Node1 #### /etc/network/interface auto lo iface lo inet loopback iface ens20 inet manual auto ens21 iface ens21 inet static address 10.14.14.50 netmask 255.255.255.0 # Connected to Node2 (.51) auto ens18 iface ens18 inet static address 10.15.15.50 netmask 255.255.255.0 up ip route add 10.15.15.51/32 dev ens18 down ip route del 10.15.15.51/32 # Connected to Node3 (.52) auto ens19 iface ens19 inet static address 10.15.15.50 netmask 255.255.255.0 up ip route add 10.15.15.52/32 dev ens19 down ip route del 10.15.15.52/32 auto vmbr0 iface vmbr0 inet static address 192.168.2.50 netmask 255.255.240.0 gateway 192.168.2.1 bridge\_ports ens20 bridge\_stp off bridge\_fd 0 #### Route root@pve-2-50:~# ip route default via 192.168.2.1 dev vmbr0 onlink 10.14.14.0/24 dev ens21 proto kernel scope link src 10.14.14.50 10.15.15.0/24 dev ens18 proto kernel scope link src 10.15.15.50 10.15.15.0/24 dev ens19 proto kernel scope link src 10.15.15.50 10.15.15.52 dev ens19 scope link 10.15.15.51 dev ens18 scope link 192.168.0.0/20 dev vmbr0 proto kernel scope link src 192.168.2.50 ### Node2 #### /etc/network/interface auto lo iface lo inet loopback iface ens20 inet manual auto ens21 iface ens21 inet static address 10.14.14.51 netmask 255.255.255.0 # Connected to Node3 (.52) auto ens18 iface ens18 inet static address 10.15.15.51 netmask 255.255.255.0 up ip route add 10.15.15.52/32 dev ens18 down ip route del 10.15.15.52/32 # Connected to Node1 (.50) auto ens19 iface ens19 inet static address 10.15.15.51 netmask 255.255.255.0 up ip route add 10.15.15.50/32 dev ens19 down ip route del 10.15.15.50/32 auto vmbr0 iface vmbr0 inet static address 192.168.2.51 netmask 255.255.240.0 gateway 192.168.2.1 bridge\_ports ens20 bridge\_stp off bridge\_fd 0 #### Route root@pve-2-51:/# ip route default via 192.168.2.1 dev vmbr0 onlink 10.14.14.0/24 dev ens21 proto kernel scope link src 10.14.14.51 10.15.15.0/24 dev ens18 proto kernel scope link src 10.15.15.51 10.15.15.0/24 dev ens19 proto kernel scope link src 10.15.15.51 10.15.15.52 dev ens18 scope link 10.15.15.50 dev ens19 scope link 192.168.0.0/20 dev vmbr0 proto kernel scope link src 192.168.2.51 ### Node3 #### /etc/network/interface auto lo iface lo inet loopback iface ens20 inet manual auto ens21 iface ens21 inet static address 10.14.14.52 netmask 255.255.255.0 # Connected to Node1 (.50) auto ens18 iface ens18 inet static address 10.15.15.52 netmask 255.255.255.0 up ip route add 10.15.15.50/32 dev ens18 down ip route del 10.15.15.50/32 # Connected to Node2 (.51) auto ens19 iface ens19 inet static address 10.15.15.52 netmask 255.255.255.0 up ip route add 10.15.15.51/32 dev ens19 down ip route del 10.15.15.51/32 auto vmbr0 iface vmbr0 inet static address 192.168.2.52 netmask 255.255.240.0 gateway 192.168.2.1 bridge\_ports ens20 bridge\_stp off bridge\_fd 0 #### Route root@pve-2-52:~# ip route default via 192.168.2.1 dev vmbr0 onlink 10.14.14.0/24 dev ens21 proto kernel scope link src 10.14.14.52 10.15.15.0/24 dev ens18 proto kernel scope link src 10.15.15.52 10.15.15.0/24 dev ens19 proto kernel scope link src 10.15.15.52 10.15.15.51 dev ens19 scope link 10.15.15.50 dev ens18 scope link 192.168.0.0/20 dev vmbr0 proto kernel scope link src 192.168.2.52 RSTP Loop Setup --------------- This setup requires the use of Open vSwitch (OVS) as it supports RSTP (Rapid spanning tree protocol). The Linux bridge itself only supports STP (without the rapid) which usually needs too long to react to a changed topology. In our tests we saw the RSTP setup to recover from one network connection going down within a few seconds while STP took about 30 seconds. This is long enough for Ceph to start to complain and throw some warnings. First the package \`openvswitch-switch\` needs to be installed on all nodes: apt install openvswitch-switch The network configuration will look the same for each node, except for the IP addresses. #### /etc/network/interface auto lo iface lo inet loopback iface ens20 inet manual auto ens21 iface ens21 inet static address 10.14.14.51 netmask 255.255.255.0 auto vmbr0 iface vmbr0 inet static address 192.168.2.51 netmask 255.255.240.0 gateway 192.168.2.1 bridge\_ports ens20 bridge\_stp off bridge\_fd 0 auto ens18 iface ens18 inet manual ovs\_type OVSPort ovs\_bridge vmbr1 ovs\_options other\_config:rstp-enable=true other\_config:rstp-path-cost=150 other\_config:rstp-port-admin-edge=false other\_config:rstp-port-auto-edge=false other\_config:rstp-port-mcheck=true vlan\_mode=native-untagged auto ens19 iface ens19 inet manual ovs\_type OVSPort ovs\_bridge vmbr1 ovs\_options other\_config:rstp-enable=true other\_config:rstp-path-cost=150 other\_config:rstp-port-admin-edge=false other\_config:rstp-port-auto-edge=false other\_config:rstp-port-mcheck=true vlan\_mode=native-untagged auto vmbr1 iface vmbr1 inet static address 10.15.15.50/24 ovs\_type OVSBridge ovs\_ports ens18 ens19 up ovs-vsctl set Bridge ${IFACE} rstp\_enable=true other\_config:rstp-priority=32768 other\_config:rstp-forward-delay=4 other\_config:rstp-max-age=6 post-up sleep 10 If needed, you can set the MTU with \`ovs\_mtu 9000\` in the \`vmbr1\`, \`eno18\` and \`eno19\` configs. You can check the RSTP status with ovs-appctl rstp/show Broadcast Setup --------------- Create a "broadcast" bond with the given interfaces on every node. This can be done over the GUI or on the command-line. ### GUI On the GUI go to the node level -> System -> Network. Then click on "Create" and select "Linux Bond". In the Wizard make your configuration without a gateway and set mode to "broadcast". Reboot the node to activate the new network settings. ### Command-Line Add the following lines to '/etc/network/interfaces'. auto bond iface bond inet static address netmask slaves bond\_miimon 100 bond\_mode broadcast #Full Mesh Then start the bond ifup bond In Node1 of the above described setup example /etc/network/interface will look like as follows: iface lo inet loopback iface ens20 inet manual auto ens21 iface ens21 inet static address 10.14.14.50 netmask 255.255.255.0 iface ens18 inet manual iface ens19 inet manual auto bond0 iface bond0 inet static address 10.15.15.50 netmask 255.255.255.0 slaves ens18 ens19 bond\_miimon 100 bond\_mode broadcast auto vmbr0 iface vmbr0 inet static address 192.168.2.50 netmask 255.255.240.0 gateway 192.168.2.1 bridge\_ports ens20 bridge\_stp off bridge\_fd 0 Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Full\_Mesh\_Network\_for\_Ceph\_Server&oldid=12533](https://pve.proxmox.com/mediawiki/index.php?title=Full_Mesh_Network_for_Ceph_Server&oldid=12533) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "High Availability" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "High Availability" ====================================== ← [High Availability](https://pve.proxmox.com/wiki/High_Availability "High Availability") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/High_Availability#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/High_Availability#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[High Availability](https://pve.proxmox.com/wiki/High_Availability "High Availability") **: Displaying 3 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/High_Availability&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/High_Availability&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/High_Availability&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/High_Availability&limit=500) ) * [Main Page](https://pve.proxmox.com/wiki/Main_Page "Main Page") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Main+Page "Special:WhatLinksHere") ) * [High Availability Cluster](https://pve.proxmox.com/wiki/High_Availability_Cluster "High Availability Cluster") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=High+Availability+Cluster "Special:WhatLinksHere") ) * [High Availability Cluster 4.x](https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x "High Availability Cluster 4.x") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=High+Availability+Cluster+4.x "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/High_Availability&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/High_Availability&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/High_Availability&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/High_Availability&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/High\_Availability](https://pve.proxmox.com/wiki/Special:WhatLinksHere/High_Availability) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # High Availability Cluster 4.x - Proxmox VE High Availability Cluster 4.x ============================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x#mw-head) [Jump to search](https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x#searchInput) ℹ️ **Note**: Most information was moved to our [reference documentation](http://pve.proxmox.com/pve-docs/) , see [High Availability](https://pve.proxmox.com/wiki/High_Availability "High Availability") . Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x#Introduction) * [2 HA Simulator](https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x#HA_Simulator) * [3 Hardware Watchdogs](https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x#Hardware_Watchdogs) * [3.1 iTCO Watchdog (module "iTCO\_wdt")](https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x#iTCO_Watchdog_(module_%22iTCO_wdt%22)) * [3.2 IPMI Watchdog (module "ipmi\_watchdog")](https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x#IPMI_Watchdog_(module_%22ipmi_watchdog%22)) * [3.3 Dell IDrac (module "ipmi\_watchdog")](https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x#Dell_IDrac_(module_%22ipmi_watchdog%22)) * [3.4 HP ILO (module "hpwdt" )](https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x#HP_ILO_(module_%22hpwdt%22_)) * [4 Troubleshooting](https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x#Troubleshooting) * [4.1 Error recovery](https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x#Error_recovery) * [4.2 Failed watchdog-mux or Multiple Watchdogs](https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x#Failed_watchdog-mux_or_Multiple_Watchdogs) * [4.3 Deleting Nodes From The Cluster](https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x#Deleting_Nodes_From_The_Cluster) * [4.4 Durations](https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x#Durations) * [4.5 Container](https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x#Container) * [5 Video Tutorials](https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x#Video_Tutorials) * [6 Testing](https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x#Testing) * [6.1 Useful command line tools](https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x#Useful_command_line_tools) Introduction ------------ Proxmox VE High Availability Cluster (Proxmox VE HA Cluster) enables the definition of high available virtual machines. In simple words, if a virtual machine (VM) is configured as HA and the physical host fails, the VM is automatically restarted on one of the remaining Proxmox VE Cluster nodes. The Proxmox VE HA Cluster is based on the Proxmox VE HA Manager (pve-ha-manager) - using watchdog fencing. Major benefit of Linux softdog or hardware watchdog is zero configuration - it just works out of the box. In order to learn more about functionality of the new Proxmox VE HA manager, install the HA simulator. For a more up to date documentation see [High Availability](https://pve.proxmox.com/wiki/High_Availability "High Availability") HA Simulator ------------ [![](https://pve.proxmox.com/mediawiki/images/thumb/d/d4/Screen-HA-4-simulator.png/600px-Screen-HA-4-simulator.png)](https://pve.proxmox.com/wiki/File:Screen-HA-4-simulator.png) HA Simulator in Action By using the HA simulator you can test and learn all functionalities of the Proxmox VE HA solutions. The simulator allows you to watch and test the behaviour of a real-world 3 node cluster with 6 VM's. You do not have to setup or configure a real cluster, the HA simulator runs out of the box on the current code base. Install with apt: apt-get install pve-ha-simulator To start the simulator you must have a X11 redirection to your current system. If you are on a Linux machine you can use: ssh root@ -Y On Windows it is working with [mobaxterm](http://mobaxterm.mobatek.net/) . After starting the simulator create a working directory: mkdir working To start the simulator type pve-ha-simulator working/ Hardware Watchdogs ------------------ if no hardware watchdog is defined, proxmox is loading the softdog module, which emulate the /dev/watchdog device. To enable a hardware watchdog, you need to specify the module to load /etc/default/pve-ha-manager WATCHDOG\_MODULE=mywatchdogmodule also, please disable nmi watchdog, which is embedeed in cpu apic. edit: /etc/default/grub GRUB\_CMDLINE\_LINUX\_DEFAULT="quiet nmi\_watchdog=0" the \# update-grub ### iTCO Watchdog (module "iTCO\_wdt") This is an hardware watchdog, available in almost all intels motherboard (ich chipset) since 15 years. ### IPMI Watchdog (module "ipmi\_watchdog") For IPMI Watchdogs you may have to set the action, else it may not do anything when it triggers. For this purpose edit the /etc/modprobe.d/ipmi\_watchdog.conf (simple create the file): options ipmi\_watchdog action=power\_cycle panic\_wdt\_timeout=10 **NOTE**: reboot or reload ipmi\_watchdog module to take the changes in effect. ### Dell IDrac (module "ipmi\_watchdog") For Dell IDrac, please desactivate the Automated System Recovery Agent in IDrac configuration. [![](https://pve.proxmox.com/mediawiki/images/thumb/9/95/Idrac-asr.png/600px-Idrac-asr.png)](https://pve.proxmox.com/wiki/File:Idrac-asr.png) If openmanage is installed, you need to disable watchdog management from openmanage /opt/dell/srvadmin/sbin/dcecfg command=removepopalias aliasname=dcifru and reboot server After restart, check that watchdog timer is 10s, and not overrided by openmanage idracadm getsysinfo -w Watchdog Information: Recovery Action = Power Cycle Present countdown value = 9 seconds Initial countdown value = 10 seconds or \# ipmitool mc watchdog get Watchdog Timer Use: SMS/OS (0x44) Watchdog Timer Is: Started/Running Watchdog Timer Actions: Hard Reset (0x01) Pre-timeout interval: 0 seconds Timer Expiration Flags: 0x00 Initial Countdown: 10 sec Present Countdown: 9 sec ### HP ILO (module "hpwdt" ) Users have reported crash with this module, please test and update the wiki if it's working fine also, disable HP ASR feature (Automatic Server Recovery). [http://h17007.www1.hp.com/docs/iss/proliant\_uefi/s\_asr\_status.html](http://h17007.www1.hp.com/docs/iss/proliant_uefi/s_asr_status.html) If you have installed hp management tools, you need to disable "hp-asrd" daemon Troubleshooting --------------- ### Error recovery See [High Availability - Error Recovery](https://pve.proxmox.com/wiki/High_Availability#ha_manager_error_recovery "High Availability") ### Failed watchdog-mux or Multiple Watchdogs Disable all BIOS watchdog functionality, those settings setup the watchdog in the expectancy that the OS resets it, that is not our desired use case here and may lead to problems - e.g.: reset of the node after a fixed amount of time. Intel AMT (OS Health Watchdog) should be disabled and with it the _mei_ and _mei\_me_ modules, as they may cause problems. If you host has multiple watchdogs available, only allow the one you want to use for HA, i.e. blacklist the other modules from loading. Our watchdog multiplexer will use /dev/watchdog which maps to /dev/watchdog0. Selecting a specific watchdog is not implemented, mainly for this quote from the linux-watchdog mailing list:[\[1\]](http://www.spinics.net/lists/linux-watchdog/msg04091.html) The watchdog device node <-> driver mapping is fragile and can change from one kernel version to the next or even across reboot, so users shouldn't assume it to be persistent. ### Deleting Nodes From The Cluster When deleting a node from a HA cluster you have to ensure the following: * all HA services were relocate to another node! * Remove the node from all defined groups. * Shutdown the node you want to remove, from now on this node **MUST NOT** come online in the same network again, without being reinstalled/cleared of all cluster configurations. * execute \`pvecm delnode nodename\` from an remaining node. The HA stack now places the node in an 'gone' state, you still see it in the manager status. After an hour in this state it will be auto deleted. This ensures that if the node died ungracefully the services still will be fenced and migrated to another node. ### Durations Note that some HA actions may take their time, and don't happen instantly. This avoids out of control feedback loops, and ensures that the HA stack is in a safe and consistent state all the time. ### Container Note that while containers may be put under HA, currently (PVE 4.1) they don't support live migration. So all migrate actions on them will be mapped to relocate (stop, move, start). Recoveries on node failure work, as long as you don't use local resources. Video Tutorials --------------- [Proxmox VE Youtube channel](http://www.youtube.com/user/ProxmoxVE) Testing ------- Before going into production it is highly recommended to do as many tests as possible. Then, do some more. ### Useful command line tools Here is a list of useful CLI tools: * ha-manager - to manage the ha stack of the cluster * pvecm - to manage the cluster-manager * corosync\* - to manipulate the corosync Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=High\_Availability\_Cluster\_4.x&oldid=10809](https://pve.proxmox.com/mediawiki/index.php?title=High_Availability_Cluster_4.x&oldid=10809) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Archive](https://pve.proxmox.com/wiki/Category:Archive "Category:Archive") * [Installation](https://pve.proxmox.com/wiki/Category:Installation "Category:Installation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Storage: BTRFS - Proxmox VE Storage: BTRFS ============== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Storage:_BTRFS#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Storage:_BTRFS#searchInput) Storage pool type: btrfs On the surface, this storage type is very similar to the directory storage type, so see the directory backend section for a general overview. The main difference is that with this storage type raw formatted disks will be placed in a subvolume, in order to allow taking snapshots and supporting offline storage migration with snapshots being preserved. | | | | --- | --- | | ![Note]() | BTRFS will honor the O\_DIRECT flag when opening files, meaning VMs should not use cache mode none, otherwise there will be checksum errors. | Configuration ------------- This backend is configured similarly to the directory storage. Note that when adding a directory as a BTRFS storage, which is not itself also the mount point, it is highly recommended to specify the actual mount point via the is\_mountpoint option. For example, if a BTRFS file system is mounted at /mnt/data2 and its pve-storage/ subdirectory (which may be a snapshot, which is recommended) should be added as a storage pool called data2, you can use the following entry: btrfs: data2 path /mnt/data2/pve-storage content rootdir,images is\_mountpoint /mnt/data2 Snapshots --------- When taking a snapshot of a subvolume or raw file, the snapshot will be created as a read-only subvolume with the same path followed by an @ and the snapshot’s name. See Also -------- * [Storage](https://pve.proxmox.com/wiki/Storage) * [BTRFS Sysadmin](https://pve.proxmox.com/wiki/BTRFS) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Storage:\_BTRFS&oldid=11130](https://pve.proxmox.com/mediawiki/index.php?title=Storage:_BTRFS&oldid=11130) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Reference Documentation](https://pve.proxmox.com/wiki/Category:Reference_Documentation "Category:Reference Documentation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # HTTPS Certificate Configuration (Version 3.x and earlier) - Proxmox VE HTTPS Certificate Configuration (Version 3.x and earlier) ========================================================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_3.x_and_earlier)#mw-head) [Jump to search](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_3.x_and_earlier)#searchInput) ℹ️ **Note**: Article about the old stable Proxmox VE 3.x releases. For the current version see [HTTPS Certificate Configuration (Version 4.x and newer)](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer) "HTTPS Certificate Configuration (Version 4.x and newer)") Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_3.x_and_earlier)#Introduction) * [2 HTTPS Certificate Configuration](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_3.x_and_earlier)#HTTPS_Certificate_Configuration) * [2.1 Backup PVE created files](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_3.x_and_earlier)#Backup_PVE_created_files) * [2.2 Copy your own certificates](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_3.x_and_earlier)#Copy_your_own_certificates) * [2.3 Using intermediate certificates](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_3.x_and_earlier)#Using_intermediate_certificates) * [2.4 Restart the API server and pvedaemon](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_3.x_and_earlier)#Restart_the_API_server_and_pvedaemon) Introduction ------------ This is a mini-howto for changing the web server certificate in Proxmox, so that you can have a certificate created with a custom CA. It has been tested on a Proxmox VE 3.0 installation, using certificates from [https://www.cacert.org/](https://www.cacert.org/) . HTTPS Certificate Configuration ------------------------------- [![](https://pve.proxmox.com/mediawiki/images/thumb/b/bf/Screen-custom-ssl-with-java-shell.png/600px-Screen-custom-ssl-with-java-shell.png)](https://pve.proxmox.com/wiki/File:Screen-custom-ssl-with-java-shell.png) 3 files are needed: * ca.pem  : CA certificate file in PEM format * server.key : non-password protected private key * server.pem : server certificate from CA in PEM format You can create the previous files following any standard openssl certificate generation HOWTO. ### Backup PVE created files cp /etc/pve/pve-root-ca.pem /etc/pve/pve-root-ca.pem.orig cp /etc/pve/local/pve-ssl.key /etc/pve/local/pve-ssl.key.orig cp /etc/pve/local/pve-ssl.pem /etc/pve/local/pve-ssl.pem.orig ### Copy your own certificates cp server.key /etc/pve/local/pve-ssl.key cp server.pem /etc/pve/local/pve-ssl.pem cp ca.pem /etc/pve/pve-root-ca.pem ### Using intermediate certificates [![](https://pve.proxmox.com/mediawiki/images/thumb/7/73/Intermediate_certificate_test.png/600px-Intermediate_certificate_test.png)](https://pve.proxmox.com/wiki/File:Intermediate_certificate_test.png) Using intermediate certificates requires a special pve-ssl.pem which has to contain both your server.pem and the intermediate\_certificate.pem. This must be created this way: cat server.pem intermediate\_certificate.pem > /etc/pve/local/pve-ssl.pem cat intermediate\_certificate.pem ca.pem > /etc/pve/pve-root-ca.pem After restarting pveproxy and pvedaemon you can verify that pve-ssl.pem is created the proper way by visiting this URL [SSL Certificate Tester](http://www.digicert.com/help/) If everything is properly configured you will be rewarded with something similarly as can be seen in the image. ### Restart the API server and pvedaemon service pveproxy restart service pvedaemon restart That's it. If you have a Proxmox cluster, this has to be done on all nodes (only the /etc/pve/local part). To test the changes in one node before changing configuration in other nodes, please make sure you log in the web interface in the correct node. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=HTTPS\_Certificate\_Configuration\_(Version\_3.x\_and\_earlier)&oldid=10453](https://pve.proxmox.com/mediawiki/index.php?title=HTTPS_Certificate_Configuration_(Version_3.x_and_earlier)&oldid=10453) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Archive](https://pve.proxmox.com/wiki/Category:Archive "Category:Archive") * [Proxmox VE 3.x](https://pve.proxmox.com/wiki/Category:Proxmox_VE_3.x "Category:Proxmox VE 3.x") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # User contributions for 2020media - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:User_contributions) User contributions for 2020media ================================ Results for [2020media](https://pve.proxmox.com/mediawiki/index.php?title=User:2020media&action=edit&redlink=1 "User:2020media (page does not exist)") [talk](https://pve.proxmox.com/mediawiki/index.php?title=User_talk:2020media&action=edit&redlink=1 "User talk:2020media (page does not exist)") [block log](https://pve.proxmox.com/mediawiki/index.php?title=Special:Log/block&page=User%3A2020media "Special:Log/block") [uploads](https://pve.proxmox.com/wiki/Special:ListFiles/2020media "Special:ListFiles/2020media") [logs](https://pve.proxmox.com/wiki/Special:Log/2020media "Special:Log/2020media") A user with 2 edits. Account created on 21 October 2010. [Jump to navigation](https://pve.proxmox.com/wiki/Special:Contributions/2020media#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:Contributions/2020media#searchInput) Search for contributionsExpandCollapse ⧼contribs-top⧽ IP address or username: Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection Associated namespace [Tag](https://pve.proxmox.com/wiki/Special:Tags "Special:Tags") filter: Manual revertNew redirectRemoved redirectReplacedRevertedRollbackUndoVisual edit: Switchedwikieditor (hidden tag) Invert selection Only show edits that are latest revisions Only show edits that are page creations Hide minor edits ⧼contribs-date⧽ From date: To date: Search #### 29 October 2010 * 10:15[10:15, 29 October 2010](https://pve.proxmox.com/mediawiki/index.php?title=FAQ&oldid=2590 "FAQ") [diff](https://pve.proxmox.com/mediawiki/index.php?title=FAQ&diff=prev&oldid=2590 "FAQ") [hist](https://pve.proxmox.com/mediawiki/index.php?title=FAQ&action=history "FAQ") +338 [FAQ](https://pve.proxmox.com/wiki/FAQ "FAQ") [→How do I configure bridged networking in an OpenVZ Ubuntu/Debian container?](https://pve.proxmox.com/wiki/FAQ#How_do_I_configure_bridged_networking_in_an_OpenVZ_Ubuntu/Debian_container? "FAQ") : add information concerning gateway device Retrieved from "[https://pve.proxmox.com/wiki/Special:Contributions/2020media](https://pve.proxmox.com/wiki/Special:Contributions/2020media) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Talk:Ceph Server - Proxmox VE Talk:Ceph Server ================ From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Talk:Ceph_Server#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Talk:Ceph_Server#searchInput) The screen captures and the doc show in fact a single network which is **both internal and public**. This makes difficult to use this for different cases where these are 2 different networks. In my case, for some reasons related to my config, I need to manually edit the conf file... but the doc here is not as helpful as it could be Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Talk:Ceph\_Server&oldid=10058](https://pve.proxmox.com/mediawiki/index.php?title=Talk:Ceph_Server&oldid=10058) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Windows 2008 guest best practices - Proxmox VE Windows 2008 guest best practices ================================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Windows_2008_guest_best_practices#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Windows_2008_guest_best_practices#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Windows_2008_guest_best_practices#Introduction) * [2 Install](https://pve.proxmox.com/wiki/Windows_2008_guest_best_practices#Install) * [2.1 Prepare](https://pve.proxmox.com/wiki/Windows_2008_guest_best_practices#Prepare) * [2.2 Launch Windows install](https://pve.proxmox.com/wiki/Windows_2008_guest_best_practices#Launch_Windows_install) * [2.3 Install additional VirtIO drivers](https://pve.proxmox.com/wiki/Windows_2008_guest_best_practices#Install_additional_VirtIO_drivers) * [3 further info](https://pve.proxmox.com/wiki/Windows_2008_guest_best_practices#further_info) * [3.1 raw vs qcow2](https://pve.proxmox.com/wiki/Windows_2008_guest_best_practices#raw_vs_qcow2) * [3.2 virtio drivers](https://pve.proxmox.com/wiki/Windows_2008_guest_best_practices#virtio_drivers) * [3.3 Power settings](https://pve.proxmox.com/wiki/Windows_2008_guest_best_practices#Power_settings) * [4 See also](https://pve.proxmox.com/wiki/Windows_2008_guest_best_practices#See_also) Introduction ------------ This is a set of best practices to follow when installing a Windows Server 2008 R2 guest on a Proxmox VE server 2.x (2.3 at time of writing). Right now it's a work in progress but hopefully soon it will be a comprehensive and reliable document. Please feel free to add to it, even if just to pose a potential best practice. Install ------- ### Prepare * ​After clicking "Create VM" enter a Name: for your vm, select your Resource Pool (if you have one) and click Next * Select Microsoft Windows 7/2008 in the OS tab and click Next. * Select an ISO Image: for Windows Server 2008 in the CD/DVD tab and click Next. * Select Bus/Device: IDE, Storage: "your preferred storage" and Cache: Write back in the Hard Disk tab and click Next. * Select number of Sockets and cores (the default of 1 is mostly sufficient) in the CPU tab and click Next. * Select Automatically allocate memory and set the Maximum memory to a number you may require in the memory tab and click Next. * Select Model: VirtIO (paravirtualized) in the Network tab and click Next * Click finish and go to the Hardware tab of your newly created VM and click Add -> CD/DVD drive * Select Storage:local and ISO image: virtio-win-x.x.iso and click create. * To add a temporary disk for installing VirtIO block driver go to the Hardware tab of your newly created VM again and click Add -> Hard Disk * Select Bus/Device: VIRTIO, Storage: "your preferred storage" and Cache: Write back and click Add ### Launch Windows install * start your newly created virtual machine using the "Start" link in the upper right. * wait until the vm icon has turned white before you login using the "Console" link in the upper right. (NOTE: Sometimes the java console does not start at the first attempt. Please click refresh/reload in this case)​​ * Start the server install with "Install Now" and select the Operating System Flavor you like and click next and select "Custom: Install Windows only" * Wait until Windows is installed and select a Password for the local Administrator account and login to Windows. ### Install additional VirtIO drivers * Start Explorer, Go to CDROM, copy folder WIN7\\AMD64 to C:\\Program Files\\ and rename AMD64 to C:\\Program Files\\VirtIO * open Device Manager and right click on Other Devices -> Ethernet Controller and select update driver software * select "Browse my computer" select folder "C:\\Program Files\\VirtIO" and click "Install" for Red Hat VirtIO Ethernet Adapter. * again in Device Manager right click on Other Devices -> PCI Device and select update driver software * again "Browse my computer" select folder "C:\\Program Files\\VirtIO" and click "Install" for VirtIO Ballon Driver. * open a powershell window, cd to "C:\\Program Files\\VirtIO" and enter: blnsvr.exe -i. The BallonService that can help free up memory is installed. The BallonService is also responsible for displaying the correct amount of memory in the Proxmox console. further info ------------ ### raw vs qcow2 Raw file format provides better performance while qcow2 offers advanced features such as copy on write and snapshots. As of Qemu 1.4 / PVE 2.3 qcow2 is expected to provide superior performance. ### virtio drivers Use virtio dirvers for best performance. More info: [Paravirtualized Block Drivers for Windows](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows "Paravirtualized Block Drivers for Windows") latest iso with virtio drivers : [https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/) ### Power settings * In Windows Server 2008, you need to disable the 'Shutdown Event Tracker'. This setting in Group Policy. If the server is part of a domain, you need to edit the group policy for the organizational unit with the server. If you're not using a domain, you can edit the local group policy. This can be accessed by doing the following: * Start -> Run -> gpedit.msc -> ok -> open "Computer Configuration" then "Policy" then "Administrative Templates" then "System". In the right pane, double click on 'Display Shutdown Event Tracker' and select 'disable' and OK. To make sure the new group policy is applied. Go to Start -> run -> cmd -> ok and type in 'gpupdate /force' without the quotes. Now when you select shutdown, you won't be promoted with the box asking why you are shutting down the server. * In order to make **Windows 2008 R2** guest shutdown cleanly on the event of a shutdown (power button) on the Proxmox VE host you need make the following changes: * Control Panel -> System and Security -> Power Options -> Edit Plan Settings -> Turn off the display: **Never** See also -------- [Windows 2003 guest best practices](https://pve.proxmox.com/wiki/Windows_2003_guest_best_practices "Windows 2003 guest best practices") [Windows 2012 guest best practices](https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices "Windows 2012 guest best practices") Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Windows\_2008\_guest\_best\_practices&oldid=9138](https://pve.proxmox.com/mediawiki/index.php?title=Windows_2008_guest_best_practices&oldid=9138) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Qemu/KVM](https://pve.proxmox.com/wiki/Category:Qemu/KVM "Category:Qemu/KVM") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # File:New Text Document.txt - Proxmox VE File:New Text Document.txt ========================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/File:New_Text_Document.txt#mw-head) [Jump to search](https://pve.proxmox.com/wiki/File:New_Text_Document.txt#searchInput) * [File](https://pve.proxmox.com/wiki/File:New_Text_Document.txt#file) * [File history](https://pve.proxmox.com/wiki/File:New_Text_Document.txt#filehistory) * [File usage](https://pve.proxmox.com/wiki/File:New_Text_Document.txt#filelinks) [New\_Text\_Document.txt](https://pve.proxmox.com/mediawiki/images/6/6a/New_Text_Document.txt "New Text Document.txt") (file size: 4 bytes, MIME type: text/plain) **Warning:** This file type may contain malicious code. By executing it, your system may be compromised. File history ------------ Click on a date/time to view the file as it appeared at that time. | | Date/Time | Dimensions | User | Comment | | --- | --- | --- | --- | --- | | current | [12:23, 23 August 2010](https://pve.proxmox.com/mediawiki/images/6/6a/New_Text_Document.txt) | (4 bytes) | [Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin")
([talk](https://pve.proxmox.com/wiki/User_talk:Martin "User talk:Martin")
\| [contribs](https://pve.proxmox.com/wiki/Special:Contributions/Martin "Special:Contributions/Martin")
) | | You cannot overwrite this file. File usage ---------- The following file is a duplicate of this file ([more details](https://pve.proxmox.com/wiki/Special:FileDuplicateSearch/New_Text_Document.txt "Special:FileDuplicateSearch/New Text Document.txt") ): * [File:New Text Document.tar.gz](https://pve.proxmox.com/wiki/File:New_Text_Document.tar.gz "File:New Text Document.tar.gz") There are no pages that use this file. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=File:New\_Text\_Document.txt&oldid=2384](https://pve.proxmox.com/mediawiki/index.php?title=File:New_Text_Document.txt&oldid=2384) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Firewall - Proxmox VE Firewall ======== From Proxmox VE (Redirected from [Proxmox VE Firewall](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_VE_Firewall&redirect=no "Proxmox VE Firewall") ) [Jump to navigation](https://pve.proxmox.com/wiki/Proxmox_VE_Firewall#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Proxmox_VE_Firewall#searchInput) Proxmox VE Firewall provides an easy way to protect your IT infrastructure. You can setup firewall rules for all hosts inside a cluster, or define rules for virtual machines and containers. Features like firewall macros, security groups, IP sets and aliases help to make that task easier. While all configuration is stored on the cluster file system, the iptables\-based firewall service runs on each cluster node, and thus provides full isolation between virtual machines. The distributed nature of this system also provides much higher bandwidth than a central firewall solution. The firewall has full support for IPv4 and IPv6. IPv6 support is fully transparent, and we filter traffic for both protocols by default. So there is no need to maintain a different set of rules for IPv6. Directions & Zones ------------------ The Proxmox VE firewall groups the network into multiple logical zones. You can define rules for each zone independently. Depending on the zone, you can define rules for incoming, outgoing or forwarded traffic. ### Directions There are 3 directions that you can choose from when defining rules for a zone: In Traffic that is arriving in a zone. Out Traffic that is leaving a zone. Forward Traffic that is passing through a zone. In the host zone this can be routed traffic (when the host is acting as a gateway or performing NAT). At a VNet-level this affects all traffic that is passing by a VNet, including traffic from/to bridged network interfaces. | | | | --- | --- | | ![Important]() | Creating rules for forwarded traffic is currently only possible when using the new [nftables-based proxmox-firewall](https://pve.proxmox.com/wiki/Firewall#pve_firewall_nft)
. Any forward rules will be ignored by the stock pve-firewall and have no effect! | ### Zones There are 3 different zones that you can define firewall rules for: Host Traffic going from/to a host, or traffic that is forwarded by a host. You can define rules for this zone either at the datacenter level or at the host level. Rules at host level take precedence over rules at datacenter level. VM Traffic going from/to a VM or CT. You cannot define rules for forwarded traffic, only for incoming / outgoing traffic. VNet Traffic passing through a SDN VNet, either from guest to guest or from host to guest and vice-versa. Since this traffic is always forwarded traffic, it is only possible to create rules with direction forward. | | | | --- | --- | | ![Important]() | Creating rules on a VNet-level is currently only possible when using the new [nftables-based proxmox-firewall](https://pve.proxmox.com/wiki/Firewall#pve_firewall_nft)
. Any VNet-level rules will be ignored by the stock pve-firewall and have no effect! | Configuration Files ------------------- All firewall related configuration is stored on the proxmox cluster file system. So those files are automatically distributed to all cluster nodes, and the pve-firewall service updates the underlying iptables rules automatically on changes. You can configure anything using the GUI (i.e. **Datacenter** → **Firewall**, or on a **Node** → **Firewall**), or you can edit the configuration files directly using your preferred editor. Firewall configuration files contain sections of key-value pairs. Lines beginning with a # and blank lines are considered comments. Sections start with a header line containing the section name enclosed in \[ and \]. ### Cluster Wide Setup The cluster-wide firewall configuration is stored at: /etc/pve/firewall/cluster.fw The configuration can contain the following sections: \[OPTIONS\] This is used to set cluster-wide firewall options. ebtables: (_default =_ 1) Enable ebtables rules cluster wide. enable: (0 - N) (_default =_ 0) Enable or disable the firewall cluster wide. log\_ratelimit: \[enable=\]<1|0> \[,burst=\] \[,rate=\] Log ratelimiting settings burst\= (0 - N) (_default =_ 5) Initial burst of packages which will always get logged before the rate is applied enable\= (_default =_ 1) Enable or disable log rate limiting rate\= (_default =_ 1/second) Frequency with which the burst bucket gets refilled policy\_forward: Forward policy. policy\_in: Input policy. policy\_out: Output policy. \[RULES\] This sections contains cluster-wide firewall rules for all nodes. \[IPSET \] Cluster wide IP set definitions. \[GROUP \] Cluster wide security group definitions. \[ALIASES\] Cluster wide Alias definitions. #### Enabling the Firewall The firewall is completely disabled by default, so you need to set the enable option here: \[OPTIONS\] # enable firewall (cluster-wide setting, default is disabled) enable: 1 | | | | --- | --- | | ![Important]() | If you enable the firewall, traffic to all hosts is blocked by default. Only exceptions is WebGUI(8006) and ssh(22) from your local network. | If you want to administrate your Proxmox VE hosts from remote, you need to create rules to allow traffic from those remote IPs to the web GUI (port 8006). You may also want to allow ssh (port 22), and maybe SPICE (port 3128). | | | | --- | --- | | ![Tip]() | Please open a SSH connection to one of your Proxmox VE hosts before enabling the firewall. That way you still have access to the host if something goes wrong . | To simplify that task, you can instead create an IPSet called “management”, and add all remote IPs there. This creates all required firewall rules to access the GUI from remote. ### Host Specific Configuration Host related configuration is read from: /etc/pve/nodes//host.fw This is useful if you want to overwrite rules from cluster.fw config. You can also increase log verbosity, and set netfilter related options. The configuration can contain the following sections: \[OPTIONS\] This is used to set host related firewall options. enable: (_default =_ 1) Enable host firewall rules. log\_level\_forward: Log level for forwarded traffic. log\_level\_in: Log level for incoming traffic. log\_level\_out: Log level for outgoing traffic. log\_nf\_conntrack: (_default =_ 0) Enable logging of conntrack information. ndp: (_default =_ 1) Enable NDP (Neighbor Discovery Protocol). nf\_conntrack\_allow\_invalid: (_default =_ 0) Allow invalid packets on connection tracking. nf\_conntrack\_helpers: (_default =_ \`\`) Enable conntrack helpers for specific protocols. Supported protocols: amanda, ftp, irc, netbios-ns, pptp, sane, sip, snmp, tftp nf\_conntrack\_max: (32768 - N) (_default =_ 262144) Maximum number of tracked connections. nf\_conntrack\_tcp\_timeout\_established: (7875 - N) (_default =_ 432000) Conntrack established timeout. nf\_conntrack\_tcp\_timeout\_syn\_recv: (30 - 60) (_default =_ 60) Conntrack syn recv timeout. nftables: (_default =_ 0) Enable nftables based firewall (tech preview) nosmurfs: Enable SMURFS filter. protection\_synflood: (_default =_ 0) Enable synflood protection protection\_synflood\_burst: (_default =_ 1000) Synflood protection rate burst by ip src. protection\_synflood\_rate: (_default =_ 200) Synflood protection rate syn/sec by ip src. smurf\_log\_level: Log level for SMURFS filter. tcp\_flags\_log\_level: Log level for illegal tcp flags filter. tcpflags: (_default =_ 0) Filter illegal combinations of TCP flags. \[RULES\] This sections contains host specific firewall rules. ### VM/Container Configuration VM firewall configuration is read from: /etc/pve/firewall/.fw and contains the following data: \[OPTIONS\] This is used to set VM/Container related firewall options. dhcp: (_default =_ 0) Enable DHCP. enable: (_default =_ 0) Enable/disable firewall rules. ipfilter: Enable default IP filters. This is equivalent to adding an empty ipfilter-net ipset for every interface. Such ipsets implicitly contain sane default restrictions such as restricting IPv6 link local addresses to the one derived from the interface’s MAC address. For containers the configured IP addresses will be implicitly added. log\_level\_in: Log level for incoming traffic. log\_level\_out: Log level for outgoing traffic. macfilter: (_default =_ 1) Enable/disable MAC address filter. ndp: (_default =_ 1) Enable NDP (Neighbor Discovery Protocol). policy\_in: Input policy. policy\_out: Output policy. radv: Allow sending Router Advertisement. \[RULES\] This sections contains VM/Container firewall rules. \[IPSET \] IP set definitions. \[ALIASES\] IP Alias definitions. #### Enabling the Firewall for VMs and Containers Each virtual network device has its own firewall enable flag. So you can selectively enable the firewall for each interface. This is required in addition to the general firewall enable option. ### VNet Configuration VNet related configuration is read from: /etc/pve/sdn/firewall/.fw This can be used for setting firewall configuration globally on a VNet level, without having to set firewall rules for each VM inside the VNet separately. It can only contain rules for the FORWARD direction, since there is no notion of incoming or outgoing traffic. This affects all traffic travelling from one bridge port to another, including the host interface. | | | | --- | --- | | ![Warning]() | This feature is currently only available for the new [nftables-based proxmox-firewall](https://pve.proxmox.com/wiki/Firewall#pve_firewall_nft) | Since traffic passing the FORWARD chain is bi-directional, you need to create rules for both directions if you want traffic to pass both ways. For instance if HTTP traffic for a specific host should be allowed, you would need to create the following rules: FORWARD ACCEPT -dest 10.0.0.1 -dport 80 FORWARD ACCEPT -source 10.0.0.1 -sport 80 \[OPTIONS\] This is used to set VNet related firewall options. enable: (_default =_ 0) Enable/disable firewall rules. log\_level\_forward: Log level for forwarded traffic. policy\_forward: Forward policy. \[RULES\] This section contains VNet specific firewall rules. Firewall Rules -------------- Firewall rules consists of a direction (IN, OUT or FORWARD) and an action (ACCEPT, DENY, REJECT). You can also specify a macro name. Macros contain predefined sets of rules and options. Rules can be disabled by prefixing them with |. Firewall rules syntax \[RULES\] DIRECTION ACTION \[OPTIONS\] |DIRECTION ACTION \[OPTIONS\] # disabled rule DIRECTION MACRO(ACTION) \[OPTIONS\] # use predefined macro The following options can be used to refine rule matches. \--dest Restrict packet destination address. This can refer to a single IP address, an IP set (_+ipsetname_) or an IP alias definition. You can also specify an address range like _20.34.101.207-201.3.9.99_, or a list of IP addresses and networks (entries are separated by comma). Please do not mix IPv4 and IPv6 addresses inside such lists. \--dport Restrict TCP/UDP destination port. You can use service names or simple numbers (0-65535), as defined in _/etc/services_. Port ranges can be specified with _\\d+:\\d+_, for example _80:85_, and you can use comma separated list to match several ports or ranges. \--icmp-type Specify icmp-type. Only valid if proto equals _icmp_ or _icmpv6_/_ipv6-icmp_. \--iface Network interface name. You have to use network configuration key names for VMs and containers (_net\\d+_). Host related rules can use arbitrary strings. \--log Log level for firewall rule. \--proto IP protocol. You can use protocol names (_tcp_/_udp_) or simple numbers, as defined in _/etc/protocols_. \--source Restrict packet source address. This can refer to a single IP address, an IP set (_+ipsetname_) or an IP alias definition. You can also specify an address range like _20.34.101.207-201.3.9.99_, or a list of IP addresses and networks (entries are separated by comma). Please do not mix IPv4 and IPv6 addresses inside such lists. \--sport Restrict TCP/UDP source port. You can use service names or simple numbers (0-65535), as defined in _/etc/services_. Port ranges can be specified with _\\d+:\\d+_, for example _80:85_, and you can use comma separated list to match several ports or ranges. Here are some examples: \[RULES\] IN SSH(ACCEPT) -i net0 IN SSH(ACCEPT) -i net0 # a comment IN SSH(ACCEPT) -i net0 -source 192.168.2.192 # only allow SSH from 192.168.2.192 IN SSH(ACCEPT) -i net0 -source 10.0.0.1-10.0.0.10 # accept SSH for IP range IN SSH(ACCEPT) -i net0 -source 10.0.0.1,10.0.0.2,10.0.0.3 #accept ssh for IP list IN SSH(ACCEPT) -i net0 -source +mynetgroup # accept ssh for ipset mynetgroup IN SSH(ACCEPT) -i net0 -source myserveralias #accept ssh for alias myserveralias |IN SSH(ACCEPT) -i net0 # disabled rule IN DROP # drop all incoming packages OUT ACCEPT # accept all outgoing packages Security Groups --------------- A security group is a collection of rules, defined at cluster level, which can be used in all VMs' rules. For example you can define a group named “webserver” with rules to open the _http_ and _https_ ports. \# /etc/pve/firewall/cluster.fw \[group webserver\] IN ACCEPT -p tcp -dport 80 IN ACCEPT -p tcp -dport 443 Then, you can add this group to a VM’s firewall \# /etc/pve/firewall/.fw \[RULES\] GROUP webserver IP Aliases ---------- IP Aliases allow you to associate IP addresses of networks with a name. You can then refer to those names: * inside IP set definitions * in source and dest properties of firewall rules ### Standard IP Alias local\_network This alias is automatically defined. Please use the following command to see assigned values: \# pve-firewall localnet local hostname: example local IP address: 192.168.2.100 network auto detect: 192.168.0.0/20 using detected local\_network: 192.168.0.0/20 The firewall automatically sets up rules to allow everything needed for cluster communication (corosync, API, SSH) using this alias. The user can overwrite these values in the cluster.fw alias section. If you use a single host on a public network, it is better to explicitly assign the local IP address \# /etc/pve/firewall/cluster.fw \[ALIASES\] local\_network 1.2.3.4 # use the single IP address IP Sets ------- IP sets can be used to define groups of networks and hosts. You can refer to them with ‘+name\` in the firewall rules’ source and dest properties. The following example allows HTTP traffic from the management IP set. IN HTTP(ACCEPT) -source +management ### Standard IP set management This IP set applies only to host firewalls (not VM firewalls). Those IPs are allowed to do normal management tasks (Proxmox VE GUI, VNC, SPICE, SSH). The local cluster network is automatically added to this IP set (alias cluster\_network), to enable inter-host cluster communication. (multicast,ssh,…) \# /etc/pve/firewall/cluster.fw \[IPSET management\] 192.168.2.10 192.168.2.10/24 ### Standard IP set blacklist Traffic from these IPs is dropped by every host’s and VM’s firewall. \# /etc/pve/firewall/cluster.fw \[IPSET blacklist\] 77.240.159.182 213.87.123.0/24 ### Standard IP set ipfilter-net\* These filters belong to a VM’s network interface and are mainly used to prevent IP spoofing. If such a set exists for an interface then any outgoing traffic with a source IP not matching its interface’s corresponding ipfilter set will be dropped. For containers with configured IP addresses these sets, if they exist (or are activated via the general IP Filter option in the VM’s firewall’s **options** tab), implicitly contain the associated IP addresses. For both virtual machines and containers they also implicitly contain the standard MAC-derived IPv6 link-local address in order to allow the neighbor discovery protocol to work. /etc/pve/firewall/.fw \[IPSET ipfilter-net0\] # only allow specified IPs on net0 192.168.2.10 Services and Commands --------------------- The firewall runs two service daemons on each node: * pvefw-logger: NFLOG daemon (ulogd replacement). * pve-firewall: updates iptables rules There is also a CLI command named pve-firewall, which can be used to start and stop the firewall service: \# pve-firewall start # pve-firewall stop To get the status use: \# pve-firewall status The above command reads and compiles all firewall rules, so you will see warnings if your firewall configuration contains any errors. If you want to see the generated iptables rules you can use: \# iptables-save Default firewall rules ---------------------- The following traffic is filtered by the default firewall configuration: ### Datacenter incoming/outgoing DROP/REJECT If the input or output policy for the firewall is set to DROP or REJECT, the following traffic is still allowed for all Proxmox VE hosts in the cluster: * traffic over the loopback interface * already established connections * traffic using the IGMP protocol * TCP traffic from management hosts to port 8006 in order to allow access to the web interface * TCP traffic from management hosts to the port range 5900 to 5999 allowing traffic for the VNC web console * TCP traffic from management hosts to port 3128 for connections to the SPICE proxy * TCP traffic from management hosts to port 22 to allow ssh access * UDP traffic in the cluster network to ports 5405-5412 for corosync * UDP multicast traffic in the cluster network * ICMP traffic type 3 (Destination Unreachable), 4 (congestion control) or 11 (Time Exceeded) The following traffic is dropped, but not logged even with logging enabled: * TCP connections with invalid connection state * Broadcast, multicast and anycast traffic not related to corosync, i.e., not coming through ports 5405-5412 * TCP traffic to port 43 * UDP traffic to ports 135 and 445 * UDP traffic to the port range 137 to 139 * UDP traffic form source port 137 to port range 1024 to 65535 * UDP traffic to port 1900 * TCP traffic to port 135, 139 and 445 * UDP traffic originating from source port 53 The rest of the traffic is dropped or rejected, respectively, and also logged. This may vary depending on the additional options enabled in **Firewall** → **Options**, such as NDP, SMURFS and TCP flag filtering. Please inspect the output of the # iptables-save system command to see the firewall chains and rules active on your system. This output is also included in a System Report, accessible over a node’s subscription tab in the web GUI, or through the pvereport command-line tool. ### VM/CT incoming/outgoing DROP/REJECT This drops or rejects all the traffic to the VMs, with some exceptions for DHCP, NDP, Router Advertisement, MAC and IP filtering depending on the set configuration. The same rules for dropping/rejecting packets are inherited from the datacenter, while the exceptions for accepted incoming/outgoing traffic of the host do not apply. Again, you can use [iptables-save (see above)](https://pve.proxmox.com/wiki/Firewall#pve_firewall_iptables_inspect) to inspect all rules and chains applied. Logging of firewall rules ------------------------- By default, all logging of traffic filtered by the firewall rules is disabled. To enable logging, the loglevel for incoming and/or outgoing traffic has to be set in **Firewall** → **Options**. This can be done for the host as well as for the VM/CT firewall individually. By this, logging of Proxmox VE’s standard firewall rules is enabled and the output can be observed in **Firewall** → **Log**. Further, only some dropped or rejected packets are logged for the standard rules (see [default firewall rules](https://pve.proxmox.com/wiki/Firewall#pve_firewall_default_rules) ). loglevel does not affect how much of the filtered traffic is logged. It changes a LOGID appended as prefix to the log output for easier filtering and post-processing. loglevel is one of the following flags: | loglevel | LOGID | | --- | --- | | nolog | — | | emerg | 0 | | alert | 1 | | crit | 2 | | err | 3 | | warning | 4 | | notice | 5 | | info | 6 | | debug | 7 | A typical firewall log output looks like this: VMID LOGID CHAIN TIMESTAMP POLICY: PACKET\_DETAILS In case of the host firewall, VMID is equal to 0. ### Logging of user defined firewall rules In order to log packets filtered by user-defined firewall rules, it is possible to set a log-level parameter for each rule individually. This allows to log in a fine grained manner and independent of the log-level defined for the standard rules in **Firewall** → **Options**. While the loglevel for each individual rule can be defined or changed easily in the web UI during creation or modification of the rule, it is possible to set this also via the corresponding pvesh API calls. Further, the log-level can also be set via the firewall configuration file by appending a \-log to the selected rule (see [possible log-levels](https://pve.proxmox.com/wiki/Firewall#pve_firewall_log_levels) ). For example, the following two are identical: IN REJECT -p icmp -log nolog IN REJECT -p icmp whereas IN REJECT -p icmp -log debug produces a log output flagged with the debug level. Tips and Tricks --------------- ### How to allow FTP FTP is an old style protocol which uses port 21 and several other dynamic ports. So you need a rule to accept port 21. In addition, you need to load the ip\_conntrack\_ftp module. So please run: modprobe ip\_conntrack\_ftp and add ip\_conntrack\_ftp to /etc/modules (so that it works after a reboot). ### Suricata IPS integration If you want to use the [Suricata IPS](https://suricata.io/) (Intrusion Prevention System), it’s possible. Packets will be forwarded to the IPS only after the firewall ACCEPTed them. Rejected/Dropped firewall packets don’t go to the IPS. Install suricata on proxmox host: \# apt-get install suricata # modprobe nfnetlink\_queue Don’t forget to add nfnetlink\_queue to /etc/modules for next reboot. Then, enable IPS for a specific VM with: \# /etc/pve/firewall/.fw \[OPTIONS\] ips: 1 ips\_queues: 0 ips\_queues will bind a specific cpu queue for this VM. Available queues are defined in \# /etc/default/suricata NFQUEUE=0 Notes on IPv6 ------------- The firewall contains a few IPv6 specific options. One thing to note is that IPv6 does not use the ARP protocol anymore, and instead uses NDP (Neighbor Discovery Protocol) which works on IP level and thus needs IP addresses to succeed. For this purpose link-local addresses derived from the interface’s MAC address are used. By default the NDP option is enabled on both host and VM level to allow neighbor discovery (NDP) packets to be sent and received. Beside neighbor discovery NDP is also used for a couple of other things, like auto-configuration and advertising routers. By default VMs are allowed to send out router solicitation messages (to query for a router), and to receive router advertisement packets. This allows them to use stateless auto configuration. On the other hand VMs cannot advertise themselves as routers unless the “Allow Router Advertisement” (radv: 1) option is set. As for the link local addresses required for NDP, there’s also an “IP Filter” (ipfilter: 1) option which can be enabled which has the same effect as adding an ipfilter-net\* ipset for each of the VM’s network interfaces containing the corresponding link local addresses. (See the [Standard IP set ipfilter-net\*](https://pve.proxmox.com/wiki/Firewall#pve_firewall_ipfilter_section) section for details.) Ports used by Proxmox VE ------------------------ * Web interface: 8006 (TCP, HTTP/1.1 over TLS) * VNC Web console: 5900-5999 (TCP, WebSocket) * SPICE proxy: 3128 (TCP) * sshd (used for cluster actions): 22 (TCP) * rpcbind: 111 (UDP) * sendmail: 25 (TCP, outgoing) * corosync cluster traffic: 5405-5412 UDP * live migration (VM memory and local-disk data): 60000-60050 (TCP) nftables -------- As an alternative to pve-firewall we offer proxmox-firewall, which is an implementation of the Proxmox VE firewall based on the newer [nftables](https://wiki.nftables.org/wiki-nftables/index.php/What_is_nftables%3F) rather than iptables. | | | | --- | --- | | ![Warning]() | proxmox-firewall is currently in tech preview. There might be bugs or incompatibilities with the original firewall. It is currently not suited for production use. | This implementation uses the same configuration files and configuration format, so you can use your old configuration when switching. It provides the exact same functionality with a few exceptions: * When using Linux bridges, no additional firewall bridges (fwbrX) will be created. Guest interfaces using OVS bridges will still have firewall bridges. * REJECT is currently not possible for guest traffic (traffic will instead be dropped). * Using the NDP, Router Advertisement or DHCP options will **always** create firewall rules, irregardless of your default policy. * firewall rules for guests are evaluated even for connections that have conntrack table entries. ### Installation and Usage Install the proxmox-firewall package: apt install proxmox-firewall Enable the nftables backend via the Web UI on your hosts (Host > Firewall > Options > nftables), or by enabling it in the configuration file for your hosts (/etc/pve/nodes//host.fw): \[OPTIONS\] nftables: 1 | | | | --- | --- | | ![Note]() | After enabling/disabling proxmox-firewall, all running VMs and containers need to be restarted for the old/new firewall to work properly. | After setting the nftables configuration key, the new proxmox-firewall service will take over. You can check if the new service is working by checking the systemctl status of proxmox-firewall: systemctl status proxmox-firewall You can also examine the generated ruleset. You can find more information about this in the section [Helpful Commands](https://pve.proxmox.com/wiki/Firewall#pve_firewall_nft_helpful_commands) . You should also check whether pve-firewall is no longer generating iptables rules, you can find the respective commands in the [Services and Commands](https://pve.proxmox.com/wiki/Firewall#pve_firewall_services_commands) section. Switching back to the old firewall can be done by simply setting the configuration value back to 0 / No. ### Usage proxmox-firewall will create two tables that are managed by the proxmox-firewall service: proxmox-firewall and proxmox-firewall-guests. If you want to create custom rules that live outside the Proxmox VE firewall configuration you can create your own tables to manage your custom firewall rules. proxmox-firewall will only touch the tables it generates, so you can easily extend and modify the behavior of the proxmox-firewall by adding your own tables. Instead of using the pve-firewall command, the nftables-based firewall uses proxmox-firewall. It is a systemd service, so you can start and stop it via systemctl: systemctl start proxmox-firewall systemctl stop proxmox-firewall Stopping the firewall service will remove all generated rules. To query the status of the firewall, you can query the status of the systemctl service: systemctl status proxmox-firewall ### Helpful Commands You can check the generated ruleset via the following command: nft list ruleset If you want to debug proxmox-firewall you can dump the commands generated by the firewall via the compile subcommand. Additionally, setting the PVE\_LOG environment variable will print log output to STDERR, which can be useful for debugging issues during the generation of the nftables ruleset: PVE\_LOG=trace /usr/libexec/proxmox/proxmox-firewall compile > firewall.json The nftables ruleset consists of the skeleton ruleset, that is included in the proxmox-firewall binary, as well as the rules generated from the firewall configuration. You can obtain the base ruleset via the skeleton subcommand: /usr/libexec/proxmox/proxmox-firewall skeleton The output of both commands can be piped directly to the nft executable. The following commands will re-create the whole nftables ruleset from scratch: /usr/libexec/proxmox/proxmox-firewall skeleton | nft -f - /usr/libexec/proxmox/proxmox-firewall compile | nft -j -f - You can also edit the systemctl service if you want to have detailed output for your firewall daemon while it is running: systemctl edit proxmox-firewall Then you need to add the override for the PVE\_LOG environment variable: \[Service\] Environment="PVE\_LOG=trace" This will generate a large amount of logs very quickly, so only use this for debugging purposes. Other, less verbose, log levels are info and debug. It can be helpful to trace packet flow through the different chains in order to debug firewall rules. This can be achieved by setting nftrace to 1 for packets that you want to track. It is advisable that you do not set this flag for **all** packets, in the example below we only examine ICMP packets. #!/usr/sbin/nft -f table bridge tracebridge delete table bridge tracebridge table bridge tracebridge { chain trace { meta l4proto icmp meta nftrace set 1 } chain prerouting { type filter hook prerouting priority -350; policy accept; jump trace } chain postrouting { type filter hook postrouting priority -350; policy accept; jump trace } } Saving this file, making it executable, and then running it once will create the respective tracing chains. You can then inspect the tracing output via the Proxmox VE Web UI (Firewall > Log) or via nft monitor trace. The above example traces traffic on all bridges, which is usually where guest traffic flows through. If you want to examine host traffic, create those chains in the inet table instead of the bridge table. | | | | --- | --- | | ![Note]() | Be aware that this can generate a **lot** of log spam and slow down the performance of your networking stack significantly. | You can remove the tracing rules via running the following command: nft delete table bridge tracebridge Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Firewall&oldid=12410](https://pve.proxmox.com/mediawiki/index.php?title=Firewall&oldid=12410) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Reference Documentation](https://pve.proxmox.com/wiki/Category:Reference_Documentation "Category:Reference Documentation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Import certificate in browser - Proxmox VE Import certificate in browser ============================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Import_certificate_in_browser#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Import_certificate_in_browser#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Import_certificate_in_browser#Introduction) * [2 Windows Systems](https://pve.proxmox.com/wiki/Import_certificate_in_browser#Windows_Systems) * [2.1 Extracting the Certificate](https://pve.proxmox.com/wiki/Import_certificate_in_browser#Extracting_the_Certificate) * [2.2 Installing the Certificate](https://pve.proxmox.com/wiki/Import_certificate_in_browser#Installing_the_Certificate) * [3 OS X System](https://pve.proxmox.com/wiki/Import_certificate_in_browser#OS_X_System) * [4 Other Browsers](https://pve.proxmox.com/wiki/Import_certificate_in_browser#Other_Browsers) * [4.1 Chrome / IE / Opera](https://pve.proxmox.com/wiki/Import_certificate_in_browser#Chrome_/_IE_/_Opera) * [4.2 Firefox](https://pve.proxmox.com/wiki/Import_certificate_in_browser#Firefox) Introduction ------------ Some browsers, like the new standard browser Edge in Windows 10, are denying custom SSL certificates, sometimes without an option to add them. As the Proxmox VE generates unique and secure certificates to ensure the integrity of the communication between the web interface and users, this "security feature" raises some issues for Proxmox VE users. Here is a step by step manual to add CA's to your Windows system. Browsers like Chrome or Opera relies on the Certificate Authority (CA) pool from the System, but give an option to visit the site nonetheless. Adding your Proxmox VE CA with this method gets rid of SSL security warnings permanently. Windows Systems --------------- ### Extracting the Certificate You find your Proxmox SSL certificate on any cluster under `/etc/pve/pve-root-ca.pem`. Copy it to the Windows machine via USB stick, Dropbox/drive/..., ssh, or your own favorite way. ### Installing the Certificate On the Windows system (tested with win7 and win10) search for "Internet Options" in the start menu or the settings window. Open it and select the content tab, there click the certificates button. The certificates window opens, there select the "Trusted Root Certification Authorities" Tab and click on import. [![](https://pve.proxmox.com/mediawiki/images/thumb/5/5d/Install_proxmox_cert_1_internet_options.png/900px-Install_proxmox_cert_1_internet_options.png)](https://pve.proxmox.com/wiki/File:Install_proxmox_cert_1_internet_options.png) The certification import wizard starts, continue to the file import, here browse to the `pve-root-ca.pem` file which you copied from the Proxmox VE server. **Attention:** you need to select to show "All Files" in the filter to see the Proxmox certificate. Open it and continue in the wizard until completion. [![](https://pve.proxmox.com/mediawiki/images/thumb/c/c5/Install_proxmox_cert_3_selected_cert.png/900px-Install_proxmox_cert_3_selected_cert.png)](https://pve.proxmox.com/wiki/File:Install_proxmox_cert_3_selected_cert.png) A new window pops up asking if you trust the imported certificate, answer it with yes and you're finished. [![](https://pve.proxmox.com/mediawiki/images/thumb/1/1e/Install_proxmox_cert_4_finish.png/358px-Install_proxmox_cert_4_finish.png)](https://pve.proxmox.com/wiki/File:Install_proxmox_cert_4_finish.png) [![](https://pve.proxmox.com/mediawiki/images/thumb/b/b4/Install_proxmox_cert_5_trust_screen.png/404px-Install_proxmox_cert_5_trust_screen.png)](https://pve.proxmox.com/wiki/File:Install_proxmox_cert_5_trust_screen.png) Now Edge, and also Internet Explorer can load the Proxmox VE Web Interface, indifferent whatever cluster you access it without complaints. If you manage different Proxmox VE instances you have to apply these steps also for them, as we generate an unique certificate for browser compatibility. OS X System ----------- On a macOS System launch Safari and enter the address of your Proxmox VE Web Interface, don't forget to begin with " _http**s**://_ ". A message should pop up, informing that the identity from the site couldn't be verified. Click the "Show Certificate" button. [![](https://pve.proxmox.com/mediawiki/images/thumb/3/3f/Pve_cert_mac_os_display_cert_file1.png/900px-Pve_cert_mac_os_display_cert_file1.png)](https://pve.proxmox.com/wiki/File:Pve_cert_mac_os_display_cert_file1.png) Check the "Always trust _certificate name here_ ..." box and click on "Continue" [![](https://pve.proxmox.com/mediawiki/images/thumb/a/ad/Pve_cert_mac_os_accept_cert_file2.png/900px-Pve_cert_mac_os_accept_cert_file2.png)](https://pve.proxmox.com/wiki/File:Pve_cert_mac_os_accept_cert_file2.png) Now the certificated is white listed, also for other browser (again, Firefox is an exception as it has its own certificate pool) and you should see the Proxmox VE Web Interface. If not, reenter your address and again, don't forget "_http**s**://_"! Other Browsers -------------- ### Chrome / IE / Opera Opera (tested version 30.0), Chrome (tested version 43) and Internet Explorer uses the system certificate pool but also gives you an option to continue to the interface, even if it is not yet added to the system. Use the steps described above to get rid of security warnings. ### Firefox Firefox uses its own build in pool of CA's and gives you the option to add an SSL CA when you load the interface (tested with version 38.0.1). Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Import\_certificate\_in\_browser&oldid=11573](https://pve.proxmox.com/mediawiki/index.php?title=Import_certificate_in_browser&oldid=11573) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # NUMA - Proxmox VE NUMA ==== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/NUMA#mw-head) [Jump to search](https://pve.proxmox.com/wiki/NUMA#searchInput) Non-uniform memory access (NUMA) and CPU pinning (Processor affinity) are technologies that try to avoid the bottleneck between the CPUs and memory regions on multi-socket computers. If you enable this feature, your system will try to arrange the resources such that a VM does have all its vCPUs on the same physical socket and only uses memory that is physically connected to that socket. Host requirements ----------------- As a rule of thumb your system is NUMA-aware if you have more than one CPU. \# numactl --hardware available: 2 nodes (0-1) node 0 cpus: 0 1 2 3 4 5 6 7 16 17 18 19 20 21 22 23 node 0 size: 128837 MB node 0 free: 1117 MB node 1 cpus: 8 9 10 11 12 13 14 15 24 25 26 27 28 29 30 31 node 1 size: 129021 MB node 1 free: 63 MB node distances: node 0 1 0: 10 21 1: 21 10 This example system has two NUMA nodes each of which has 128 GB of memory and 16 logical cores. VM configuration ---------------- Enabling NUMA can boost VM performance but is also a requirement for [hot-pluggable CPU and Memory](https://pve.proxmox.com/wiki/Hotplug_(qemu_disk,nic,cpu,memory) "Hotplug (qemu disk,nic,cpu,memory)") . If you didn't enable it with the VM creation wizard you can do so on the hardware tab. Choose "Processor" and press "edit". Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=NUMA&oldid=9717](https://pve.proxmox.com/mediawiki/index.php?title=NUMA&oldid=9717) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Proxmox VE 2.0 Cluster - Proxmox VE Proxmox VE 2.0 Cluster ====================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster#searchInput) ℹ️ **Note**: Article about old Proxmox VE releases up to 2.x Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster#Introduction) * [1.1 Main features](https://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster#Main_features) * [1.2 Requirements](https://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster#Requirements) * [2 Proxmox VE Cluster](https://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster#Proxmox_VE_Cluster) * [2.1 Create the Cluster](https://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster#Create_the_Cluster) * [2.2 Adding nodes to the Cluster](https://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster#Adding_nodes_to_the_Cluster) * [2.3 Remove a cluster node](https://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster#Remove_a_cluster_node) * [2.4 Re-installing a cluster node](https://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster#Re-installing_a_cluster_node) * [3 Working with Proxmox VE Cluster](https://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster#Working_with_Proxmox_VE_Cluster) * [4 Troubleshooting](https://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster#Troubleshooting) * [4.1 General](https://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster#General) * [4.2 Two nodes cluster and quorum issues](https://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster#Two_nodes_cluster_and_quorum_issues) * [4.2.1 The problem](https://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster#The_problem) * [4.2.2 The solution](https://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster#The_solution) * [5 Video Tutorials](https://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster#Video_Tutorials) Introduction ------------ Proxmox VE 2.x (and all versions above) Cluster enables central management of multiple physical servers. A Proxmox VE Cluster consists of several nodes (up to 16 physical nodes, probably more). ### Main features * Centralized web management, including secure VNC console * Support for multiple authentication sources (e.g. local, MS ADS, LDAP, ...) * Role based permission management for all objects (VM´s, storages, nodes, etc.) * Creates multi-master clusters (no single master anymore!) * [Proxmox Cluster file system (pmxcfs)](https://pve.proxmox.com/wiki/Proxmox_Cluster_file_system_(pmxcfs) "Proxmox Cluster file system (pmxcfs)") : Database-driven file system for storing configuration files, replicated in real-time on all nodes using corosync * Migration of Virtual Machines between physical hosts * Cluster-wide logging * RESTful web API ### Requirements * All nodes must be in the same network as it uses IP Multicast to communicate between nodes (See also [Corosync Cluster Engine](http://www.corosync.org/) ). Note: Some switches do not support IP multicast by default and must be manually enabled first. See [multicast notes](https://pve.proxmox.com/wiki/Multicast_notes "Multicast notes") for more information about multicast. * Date and time have to be synchronized * SSH tunnel on port 22 between nodes is used * VNC console traffic is secured via SSL, using ports between 5900 and 5999 * If you are interested in High Availability also, for reliable quorum you must have at least 3 active nodes at all times, or use a qdisk as seen in [Two-Node\_High\_Availability\_Cluster](https://pve.proxmox.com/wiki/Two-Node_High_Availability_Cluster "Two-Node High Availability Cluster") Proxmox VE Cluster ------------------ First, install the Proxmox VE nodes, see [Installation](https://pve.proxmox.com/wiki/Installation "Installation") . Make sure that each Proxmox VE node is installed with the final hostname and IP configuration. Changing the hostname and IP is not possible after cluster creation. Currently the cluster creation has to be done on the console, you can login to the Proxmox VE node via ssh. All settings can be done via "pvecm", the [Proxmox VE cluster manager toolkit](https://pve.proxmox.com/pve2-api-doc/man/pvecm.1.html) . ### Create the Cluster Login via ssh to the first Proxmox VE node. Use a unique name for your Cluster, this name cannot be changed later. **Create:** hp1# pvecm create YOUR-CLUSTER-NAME To check the state of cluster: hp1# pvecm status ### Adding nodes to the Cluster Login via ssh to the other Proxmox VE nodes. Please note, each nodes can't hold SAME VM ID, if yes you will get conflicts with identical VMID´s (to workaround, use vzdump to backup and to restore to a different VMID). **Add a node:** hp2# pvecm add IP-ADDRESS-CLUSTER For IP-ADDRESS-CLUSTER use an IP from an existing cluster node. To check the state of cluster: hp2# pvecm status **Display the state of cluster:** hp2# pvecm status Version: 6.2.0 Config Version: 4 Cluster Name: YOUR-CLUSTER-NAME Cluster Id: 31540 Cluster Member: Yes Cluster Generation: 152 Membership state: Cluster-Member Nodes: 4 Expected votes: 4 Total votes: 4 Node votes: 1 Quorum: 3 Active subsystems: 5 Flags: Ports Bound: 0 Node name: hp2 Node ID: 2 Multicast addresses: 239.192.123.175 Node addresses: 192.168.7.103 **Display the nodes of cluster:** hp2# pvecm nodes Node Sts Inc Joined Name 1 M 156 2011-09-05 10:39:09 hp1 2 M 156 2011-09-05 10:39:09 hp2 3 M 168 2011-09-05 11:24:12 hp4 4 M 160 2011-09-05 10:40:27 hp3 ### Remove a cluster node This procedure should be properly read as **delete a cluster node**, ie: **permanently remove**. Read carefully the procedure before proceeding, as it could not be what you want or need. Move all virtual machines out of the node, just use the [Central Web-based Management](https://pve.proxmox.com/wiki/Central_Web-based_Management "Central Web-based Management") to migrate or delete all VM´s. Make sure you have no local backups you want to keep, or save them accordingly. Log in to one remaining node via ssh. Issue a pvecm nodes command to identify the nodeID: hp1# pvecm nodes Node Sts Inc Joined Name 1 M 156 2011-09-05 10:39:09 hp1 2 M 156 2011-09-05 10:39:09 hp2 3 M 168 2011-09-05 11:24:12 hp4 4 M 160 2011-09-05 10:40:27 hp3 **ATTENTION: at this point you must power off the node to be removed and make sure that it will not power on again (in the network) as it is.** Re-read the warning that you just skipped right over. Go poweroff the node now. Remove the power cords, if you can. That node coming back online will cause a lot of problems. Log in to one remaining node via ssh. Issue the delete command (here deleting node hp2): hp1# pvecm delnode hp2 If the operation succeeds no output is returned, just check the node list again with 'pvecm nodes' (or just 'pvecm n'), you should see something like: hp1# pvecm nodes Node Sts Inc Joined Name 1 M 156 2011-09-05 10:39:09 hp1 3 M 168 2011-09-05 11:24:12 hp4 4 M 160 2011-09-05 10:40:27 hp3 ATTENTION: as said above, it is very important to power off the node **before** removal, and make sure that it will not power on again (in the network) as it is. If you power on that node as it is, your cluster will be screwed up and it could be difficult to restore a clean cluster state. If for whatever reason you would like to make that server to join again the same cluster, you have to * reinstall pve on it from scratch * as a **new node** * and then regularly join it, as said in the previous section. Referring to the above example, you can create a new **hp5** node, which will then join the cluster. ### Re-installing a cluster node Move all virtual machines off the node. Stop the following services: service pvestatd stop service pvedaemon stop service cman stop service pve-cluster stop Backup /var/lib/pve-cluster/ tar -czf /root/pve-cluster-backup.tar.gz /var/lib/pve-cluster Backup /root/.ssh/ , there are two symlinks here to the shared pve config authorized\_keys and authorized\_keys.orig , you need not worry about these two yet as they're stored in /var/lib/pve-cluster/ tar -czf /root/ssh-backup.tar.gz /root/.ssh Shut server down & re-install. Make sure the hostname is the same as it was before you continue. Stop the following services: service pvestatd stop service pvedaemon stop service cman stop service pve-cluster stop Restore the files in /root/.ssh/ cd / ; tar -xzf /root/ssh-backup.tar.gz Replace /var/lib/pve-cluster/ with your backup copy rm -rf /var/lib/pve-cluster cd / ; tar -xzf /root/pve-cluster-backup.tar.gz Start pve-cluster & cman: service pve-cluster start service cman start Restore the two ssh symlinks: ln -sf /etc/pve/priv/authorized\_keys /root/.ssh/authorized\_keys ln -sf /etc/pve/priv/authorized\_keys /root/.ssh/authorized\_keys.orig Start the rest of the services: service pvestatd start service pvedaemon start Working with Proxmox VE Cluster ------------------------------- Now, you can start creating Virtual Machines on Cluster nodes by using the [Central Web-based Management](https://pve.proxmox.com/wiki/Central_Web-based_Management "Central Web-based Management") on any node. Troubleshooting --------------- ### General * Date and time have to be synchronized (check "ntpdc -p") * Check /etc/hosts for an actual IP address of a system ### Two nodes cluster and quorum issues #### The problem If you have to bring down a node of a cluster which normally have two nodes, even if not under HA, you have to take the quorum in account, as in [this section](https://pve.proxmox.com/wiki/Two-Node_High_Availability_Cluster#Configuring_Fencing "Two-Node High Availability Cluster") If you have a two nodes cluster, not HA, by default you will have something like this \# pvecm status Version: 6.2.0 Config Version: 2 Cluster Name: pvecluster Cluster Id: 48308 Cluster Member: Yes Cluster Generation: 92 Membership state: Cluster-Member Nodes: 1 Expected votes: 2 Total votes: 1 Node votes: 1 Quorum: 2 Activity blocked Active subsystems: 5 Flags: Ports Bound: 0 Node name: pve2 Node ID: 1 Multicast addresses: 239.192.188.113 Node addresses: xxx.xxx.xxx.xxx When you bring one node **down**, maybe after you live migrated all vm/CT to the other node, your cluster becomes "non operational": you cannot add vms, all backups will fail, possibly more! One of the syntoms is: you get messages from the **up** pve node that it can't write in many places where it is normally expected to be able to, such as: /etc/pve/nodes//qemu-server/ because permissions became "read-only"! That is because as of the above default config, **2 votes** are needed, each node counts 1, and you have only 1 node of two alive! #### The solution **BEWARE** clustering is not an easy concept, and many things can (and will) go wrong, ranging from locked to destroyed, if you don't know exactly what you are doing. Applying the following solution could make the cluster run into a split brain, because each node is allowed to update values without having quorum. That said, this is a good (not brief) intro to HA clustering, using tools similar to those PVE uses today [2-Node Red Hat KVM Cluster Tutorial](https://alteeve.ca/w/2-Node_Red_Hat_KVM_Cluster_Tutorial) . * * * The simple solution is to "tell" to the cluster that you expect just 1 vote for the cluster to be operational: you can do this permanently, following instructions in [this section](https://pve.proxmox.com/wiki/Two-Node_High_Availability_Cluster#Configuring_Fencing "Two-Node High Availability Cluster") to add two\_node="1" expected\_votes="1" parameters in the start tag but until you get back alive the "down" node, you can't validate and apply the new config from the web GUI if you need, you can temporarily update the "expected" part of the pve cluster config issuing a simple command: #pvecm expected 1 that will instantly restore write permissions where thay should be, backups should work again, and all. Another solution would be to add a third "dummy node", which also counts 1, in a way similar to HA setups but without fencing, but that would take us slightly "off topic", because this section is named "**Two** nodes cluster and quorum issues" Video Tutorials --------------- * [Proxmox VE Youtube channel](http://www.youtube.com/user/ProxmoxVE) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Proxmox\_VE\_2.0\_Cluster&oldid=10447](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_VE_2.0_Cluster&oldid=10447) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Archive](https://pve.proxmox.com/wiki/Category:Archive "Category:Archive") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Paravirtualized Block Drivers for Windows - Proxmox VE Paravirtualized Block Drivers for Windows ========================================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows#Introduction) * [1.1 Download](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows#Download) * [2 Installation](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows#Installation) * [2.1 Setup On Running Windows](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows#Setup_On_Running_Windows) * [2.1.1 Setup Steps](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows#Setup_Steps) * [2.2 Setup During Windows Installation](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows#Setup_During_Windows_Installation) * [2.2.1 Old VFD Method](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows#Old_VFD_Method) * [3 See also](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows#See_also) Introduction ============ In order to improve disk performance, special paravirtualized block drivers can be installed in Windows guests. You have to download and install those drivers in the VM, as Windows does not provide them by default. ℹ️ **Note**: Proxmox recommends using SCSI with _VirtIO SCSI single_ as _SCSI Controller Type_ for VM disks, to have the most features and best performance. VirtIO block may get deprecated in the future. Download -------- See [Windows VirtIO Drivers#virtio-win Releases](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#virtio-win_Releases "Windows VirtIO Drivers") for information on how to download the virtio-win ISO, guest OS compatibility, and other useful VirtIO guest devices. Upload the ISO through the Proxmox VE WebUI: Select a Storage which allows ISO images in the Proxmox VE WebUI and switch to the _ISO Templates_ tab where you can use the "_Upload_" button or the "_Download from URL_" on the menu bar. Installation ============ Setup On Running Windows ------------------------ To switch an existing Windows installation to use the VirtIO-SCSI drivers and boot from them, it needs to see a disk requiring the driver before. This can be done by adding a small temporary disk. Installing the drivers and switching the boot disk to VirtIO SCSI right away (without a dummy disk) will result in a blue screen, claiming an "INACCESSIBLE BOOT DEVICE". In such a situation, you can revert your changes to get Windows to boot again. ### Setup Steps * Prerequisite: An installed running Windows OS and the [VirtIO driver ISO](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows#Download) * insert the VirtIO ISO into the VMs CDROM Drive. * add a small disk (1GB) with Bus Type SCSI (with _Options -> SCSI Controller Typ: VirtIO_) or VirtIO Block to the VM. * The disk should get hot plugged. If not, you need to reboot the VM. * Windows should detect the new disk. * If the drivers are not yet installed, it will be shown as a new unknown device and ask for drivers. If it doesn't, open the Device Manager, there should be an unknown device * Right-click this entry and select "Update Driver Software" * Select No when the wizard asks you to search for the driver software (online) * Select "Install from a list of specific location" * Use the Browse button and navigate to the driver CDROM * Usually, selecting the CDROM's top directory (e.g. _D:_) is enough on newer Windows versions. * If that doesn't work, select the appropriate folder for your guest version/architecture manually (use _vioscsi_ for SCSI and _vioblk_ for VirtIO) * Click Next to begin the installation. You may get a warning about the driver not being signed on older Windows Versions, select "Continue Anyway". * Finish the driver installation Once the drivers are installed, wait until the disk shows up in the "Disk Management" utility. (**Legacy Note**: Windows 2000 may report each disk 8 times in disk management, just install and use the first of each 8-tuple. In "My computer" you should see each disk only once.) Windows now has the VirtIO SCSI/Block driver installed, and we need to re-attach the VM disks as SCSI or VirtIO block. * Shut down the VM * _Detach_ and _Remove_ the dummy disk. After the Detach operation, it will show up as `unusedX` disk. Removing it right away is recommended to remove uncertainties in the next steps. * _Detach_ the disk you want to use as Virtio SCSI/Block. * reattach them by double-clicking the unused disk entry (or use the Edit button). Select _SCSI_ for VirtIO SCSI or _VirtIO block_. * **Important**: Adapt the _Boot Order_ under the VM's _Option_ tab. Make sure that the primary boot device is still the old boot disk. * You can now start the VM again, it should use the new disk controller. * If the VM does not boot, you can detach and re-attach the disk as IDE or SATA to redo the procedure with the dummy disk. Don't forget to adapt the boot order! After you are done, you can: * remove the temporary VirtIO disk if you haven't already done this and don't need it anymore * remove the ISO mounted as CD device ℹ️ **Note**: If you switch multiple disks to VirtIO drivers, you might have to bring them _Online_ in the Disk Management utility on the first boot after the switch by right-clicking on the disk. Setup During Windows Installation --------------------------------- Download the VirtIO drivers as described above. Set the drive type to SCSI (preferred) or VirtIO and the Network also to VirtIO for improved performance. Add a second IDE CDROM drive, in the first mount the Windows installer ISO and in the second the VirtIO driver ISO. Start the VM and the Installation process. When you arrive at the Disk/Partition selection, you won't see a Disk because the driver isn't loaded. Click on the _Load Driver_ button and then _Browse_. In the file browser, select the second CDROM drive with the VirtIO drivers and navigate to the _vioscsi/WINVERSION/amd64_ (or x86 if you have a 32 bit system) and click _OK_. A RedHat driver should show up in the _Driver Installer_ click next to install them. Repeat the process for other VirtIO driver (e.g. network, qxl, ...). The Disks should now show up, and you can continue with the installation process as usual. ### Old VFD Method **Note**: This is kept for legacy reasons, newer Windows versions (XP and newer) should use the above menthod. You can add the block drivers during install by manually adding a virtual floppy drive (vfd) and a second IDE CDROM Drive (for network VirtIO) to the VM for the initial install (thanks to meto & user100 in the forum). Download the VirtIO drivers as described above, upload VFD (for disks) and the ISO (for network) to PVE. Use: qm set -args '-fda /where/you/put/the/file/virtio-win-.vfd' to add the VFD as virtual floppy to the VM. Now start the VM and open the console. The standard boot sequence for a new KVM seems to be HDD - Floppy - CD, you can change this but it's just as easy to reboot using the Ctrl-Alt-Del button in the console, use F12 to bring up a boot selection window & boot from CD. Once windows starts to load, press F6 to get it to look for extra drivers to load. It will automatically load the floppy & away you go. Note that older VirtIO drivers aren't signed by Windows, so you need to tell the system to continue to load the drivers on a warning. More information on floppy drives can be found here : [http://www.linux-kvm.com/content/block-driver-updates-install-drivers-during-windows-installation](http://www.linux-kvm.com/content/block-driver-updates-install-drivers-during-windows-installation) And in the forum here : [http://forum.proxmox.com/threads/3711-Floppy-support-hack](http://forum.proxmox.com/threads/3711-Floppy-support-hack) See also ======== * [Windows VirtIO Drivers](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers "Windows VirtIO Drivers") * [Paravirtualized Network Drivers for Windows](https://pve.proxmox.com/wiki/Paravirtualized_Network_Drivers_for_Windows "Paravirtualized Network Drivers for Windows") * [Dynamic Memory Management](https://pve.proxmox.com/wiki/Dynamic_Memory_Management "Dynamic Memory Management") Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Paravirtualized\_Block\_Drivers\_for\_Windows&oldid=12445](https://pve.proxmox.com/mediawiki/index.php?title=Paravirtualized_Block_Drivers_for_Windows&oldid=12445) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Qemu/KVM](https://pve.proxmox.com/wiki/Category:Qemu/KVM "Category:Qemu/KVM") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Bibliography - Proxmox VE Bibliography ============ From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Bibliography#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Bibliography#searchInput) Books about Proxmox VE * \[Ahmed16\] Wasim Ahmed. _Mastering Proxmox - Third Edition_. Packt Publishing, 2017. ISBN 978-1788397605 * \[Ahmed15\] Wasim Ahmed. _Proxmox Cookbook_. Packt Publishing, 2015. ISBN 978-1783980901 * \[Cheng14\] Simon M.C. Cheng. _Proxmox High Availability_. Packt Publishing, 2014. ISBN 978-1783980888 * \[Goldman16\] Rik Goldman. _Learning Proxmox VE_. Packt Publishing, 2016. ISBN 978-1783981786 * \[Surber16\]\] Lee R. Surber. _Virtualization Complete: Business Basic Edition_. Linux Solutions (LRS-TEK), 2016. ASIN B01BBVQZT6 Books about related technology * \[Hertzog13\] Raphaël Hertzog, Roland Mas., Freexian SARL [The Debian Administrator's Handbook: Debian Bullseye from Discovery to Mastery](https://debian-handbook.info/get) , Freexian, 2021. ISBN 979-10-91414-20-3 * \[Bir96\] Kenneth P. Birman. _Building Secure and Reliable Network Applications_. Manning Publications Co, 1996. ISBN 978-1884777295 * \[Walsh10\] Norman Walsh. _DocBook 5: The Definitive Guide_. O’Reilly & Associates, 2010. ISBN 978-0596805029 * \[Richardson07\] Leonard Richardson & Sam Ruby. _RESTful Web Services_. O’Reilly Media, 2007. ISBN 978-0596529260 * \[Singh15\] Karan Singh. _Learning Ceph_. Packt Publishing, 2015. ISBN 978-1783985623 * \[Singh16\] Karan Signh. _Ceph Cookbook_ Packt Publishing, 2016. ISBN 978-1784393502 * \[Mauerer08\] Wolfgang Mauerer. _Professional Linux Kernel Architecture_. John Wiley & Sons, 2008. ISBN 978-0470343432 * \[Loshin03\] Pete Loshin, _IPv6: Theory, Protocol, and Practice, 2nd Edition_. Morgan Kaufmann, 2003. ISBN 978-1558608108 * \[Loeliger12\] Jon Loeliger & Matthew McCullough. _Version Control with Git: Powerful tools and techniques for collaborative software development_. O’Reilly and Associates, 2012. ISBN 978-1449316389 * \[Kreibich10\] Jay A. Kreibich. _Using SQLite_, O’Reilly and Associates, 2010. ISBN 978-0596521189 Books about related topics * \[Bessen09\] James Bessen & Michael J. Meurer, _Patent Failure: How Judges, Bureaucrats, and Lawyers Put Innovators at Risk_. Princeton Univ Press, 2009. ISBN 978-0691143217 Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Bibliography&oldid=11511](https://pve.proxmox.com/mediawiki/index.php?title=Bibliography&oldid=11511) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Reference Documentation](https://pve.proxmox.com/wiki/Category:Reference_Documentation "Category:Reference Documentation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "DRBD" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "DRBD" ========================= ← [DRBD](https://pve.proxmox.com/wiki/DRBD "DRBD") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/DRBD#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/DRBD#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[DRBD](https://pve.proxmox.com/wiki/DRBD "DRBD") **: Displaying 3 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/DRBD&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/DRBD&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/DRBD&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/DRBD&limit=500) ) * [Roadmap](https://pve.proxmox.com/wiki/Roadmap "Roadmap") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Roadmap "Special:WhatLinksHere") ) * [Proxmox VE News](https://pve.proxmox.com/wiki/Proxmox_VE_News "Proxmox VE News") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Proxmox+VE+News "Special:WhatLinksHere") ) * [Two-Node High Availability Cluster](https://pve.proxmox.com/wiki/Two-Node_High_Availability_Cluster "Two-Node High Availability Cluster") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Two-Node+High+Availability+Cluster "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/DRBD&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/DRBD&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/DRBD&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/DRBD&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/DRBD](https://pve.proxmox.com/wiki/Special:WhatLinksHere/DRBD) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # PVE2ClusterTestBed - Proxmox VE PVE2ClusterTestBed ================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/PVE2ClusterTestBed#mw-head) [Jump to search](https://pve.proxmox.com/wiki/PVE2ClusterTestBed#searchInput) This is a test bed I have done quickly in order to upgrade my operational procedures. Please tell me if there is some mistakes. After that, I will add explainations and publish it. And a question : this test bed procedure can be applied without changes to PVE 3.X ? Contents -------- * [1 initial setup](https://pve.proxmox.com/wiki/PVE2ClusterTestBed#initial_setup) * [2 delete cluster configuration, on both nodes :](https://pve.proxmox.com/wiki/PVE2ClusterTestBed#delete_cluster_configuration,_on_both_nodes_:) * [3 put the nodes in a cluster](https://pve.proxmox.com/wiki/PVE2ClusterTestBed#put_the_nodes_in_a_cluster) * [3.1 node A :](https://pve.proxmox.com/wiki/PVE2ClusterTestBed#node_A_:) * [3.2 node B :](https://pve.proxmox.com/wiki/PVE2ClusterTestBed#node_B_:) * [4 node A power failure, VM restart on node B, service OK](https://pve.proxmox.com/wiki/PVE2ClusterTestBed#node_A_power_failure,_VM_restart_on_node_B,_service_OK) * [4.1 node B :](https://pve.proxmox.com/wiki/PVE2ClusterTestBed#node_B_:_2) * [5 node A reinstallation](https://pve.proxmox.com/wiki/PVE2ClusterTestBed#node_A_reinstallation) * [5.1 node A :](https://pve.proxmox.com/wiki/PVE2ClusterTestBed#node_A_:_2) * [5.2 if "unable to copy ssh ID" - node B :](https://pve.proxmox.com/wiki/PVE2ClusterTestBed#if_%22unable_to_copy_ssh_ID%22_-_node_B_:) * [5.3 verification](https://pve.proxmox.com/wiki/PVE2ClusterTestBed#verification) ### initial setup * two nodes (A and B), with one admin network and one DRBD network configured * drbd configured * one KVM node id 100 installed on a LVM over DRBD, with no virtual CDROM inserted * node 100 live migration OK between the two nodes * backup of /etc/pve in /root/backup/pve ### delete cluster configuration, on both nodes : service pvestatd stop service pvedaemon stop service pve-cluster stop umount /etc/pve /etc/init.d/cman stop rm /etc/cluster/cluster.conf rm -rf /var/lib/pve-cluster/\* wait 20 seconds if the server has just restarted service pve-cluster start service cman start service pvestatd start service pvedaemon start ### put the nodes in a cluster #### node A : pvecm create if backup of previous /etc/pve configuration exists : cd /root/backup/pve cp storage.cfg /etc/pve/ cp nodes//qemu-server/100.conf /etc/pve/nodes//qemu-server/ else, configure DRBD storage, and install VM 100 Log into PVE WEB interface, verify storage, start VM 100, vm100 started. #### node B : pvecm add Log into PVE WEB interface, verify storage, live migrate VM 100, live migrate back to node A. ### node A power failure, VM restart on node B, service OK Remove power plug from node A (or push >4s power button) #### node B : pvecm nodes #shows node A as status "X" pvecm expected 1 mv /etc/pve/nodes//qemu-server/\*.conf /etc/pve/nodes//qemu-server/ Log into PVE WEB interface, start VM 100. ### node A reinstallation Install node A as in initial setup, without cluster configuration : to do this quickly in test platform : * stop node B (halt) * start node A * follow "delete cluster configuration, on both nodes", but just on node A * regenerate ssh keys on node A : /bin/rm /etc/ssh/ssh\_host\_\* && dpkg-reconfigure openssh-server * start node B #### node A : pvecm add **if you have error "unable to copy ssh ID", do next step and retry, else skip next step** #### if "unable to copy ssh ID" - node B : pvecm expected 1 #### verification on node A and node B, verify that the status is "M" for both nodes : pvecm nodes verify you can log into PVE WEB interface of the two nodes, verify you can live migrate Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=PVE2ClusterTestBed&oldid=5728](https://pve.proxmox.com/mediawiki/index.php?title=PVE2ClusterTestBed&oldid=5728) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Template:Languages - Proxmox VE Template:Languages ================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Template:Languages#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Template:Languages#searchInput) | | | | | --- | --- | --- | | [![Languages](https://pve.proxmox.com/mediawiki/images/5/59/Geographylogo.png)](https://pve.proxmox.com/wiki/File:Geographylogo.png "Languages") | **[Languages](https://pve.proxmox.com/wiki/Proxmox_VE:Language_policy "Proxmox VE:Language policy")
:** | [Template:Emptylang](https://pve.proxmox.com/mediawiki/index.php?title=Template:Emptylang&action=edit&redlink=1 "Template:Emptylang (page does not exist)")
[Template:Emptylang](https://pve.proxmox.com/mediawiki/index.php?title=Template:Emptylang&action=edit&redlink=1 "Template:Emptylang (page does not exist)") | Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Template:Languages&oldid=14](https://pve.proxmox.com/mediawiki/index.php?title=Template:Languages&oldid=14) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Pages using duplicate arguments in template calls](https://pve.proxmox.com/mediawiki/index.php?title=Category:Pages_using_duplicate_arguments_in_template_calls&action=edit&redlink=1 "Category:Pages using duplicate arguments in template calls (page does not exist)") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # User contributions for Hd-- - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:User_contributions) User contributions for Hd-- =========================== Results for [Hd--](https://pve.proxmox.com/mediawiki/index.php?title=User:Hd--&action=edit&redlink=1 "User:Hd-- (page does not exist)") [talk](https://pve.proxmox.com/mediawiki/index.php?title=User_talk:Hd--&action=edit&redlink=1 "User talk:Hd-- (page does not exist)") [block log](https://pve.proxmox.com/mediawiki/index.php?title=Special:Log/block&page=User%3AHd-- "Special:Log/block") [uploads](https://pve.proxmox.com/wiki/Special:ListFiles/Hd-- "Special:ListFiles/Hd--") [logs](https://pve.proxmox.com/wiki/Special:Log/Hd-- "Special:Log/Hd--") A user with 6 edits. Account created on 13 December 2023. [Jump to navigation](https://pve.proxmox.com/wiki/Special:Contributions/Hd--#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:Contributions/Hd--#searchInput) Search for contributionsExpandCollapse ⧼contribs-top⧽ IP address or username: Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection Associated namespace [Tag](https://pve.proxmox.com/wiki/Special:Tags "Special:Tags") filter: Manual revertNew redirectRemoved redirectReplacedRevertedRollbackUndoVisual edit: Switchedwikieditor (hidden tag) Invert selection Only show edits that are latest revisions Only show edits that are page creations Hide minor edits ⧼contribs-date⧽ From date: To date: Search #### 25 March 2026 * 11:40[11:40, 25 March 2026](https://pve.proxmox.com/mediawiki/index.php?title=Storage_Plugin_Development&oldid=12532 "Storage Plugin Development") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Storage_Plugin_Development&diff=prev&oldid=12532 "Storage Plugin Development") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Storage_Plugin_Development&action=history "Storage Plugin Development") +96 [Storage Plugin Development](https://pve.proxmox.com/wiki/Storage_Plugin_Development "Storage Plugin Development") extend testscenarios current #### 11 March 2026 * 09:46[09:46, 11 March 2026](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12520 "Developer Documentation") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&diff=prev&oldid=12520 "Developer Documentation") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&action=history "Developer Documentation") +9 [Developer Documentation](https://pve.proxmox.com/wiki/Developer_Documentation "Developer Documentation") No edit summary [Tag](https://pve.proxmox.com/wiki/Special:Tags "Special:Tags") : [Visual edit: Switched](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_VE:VisualEditor&action=edit&redlink=1 "Proxmox VE:VisualEditor (page does not exist)") #### 15 January 2025 * 09:19[09:19, 15 January 2025](https://pve.proxmox.com/mediawiki/index.php?title=Perl_Style_Guide&oldid=12115 "Perl Style Guide") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Perl_Style_Guide&diff=prev&oldid=12115 "Perl Style Guide") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Perl_Style_Guide&action=history "Perl Style Guide") +277 [Perl Style Guide](https://pve.proxmox.com/wiki/Perl_Style_Guide "Perl Style Guide") No edit summary #### 25 April 2024 * 11:12[11:12, 25 April 2024](https://pve.proxmox.com/mediawiki/index.php?title=Automated_Installation&oldid=11993 "Automated Installation") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Automated_Installation&diff=prev&oldid=11993 "Automated Installation") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Automated_Installation&action=history "Automated Installation") +7 [Automated Installation](https://pve.proxmox.com/wiki/Automated_Installation "Automated Installation") fix old toolname #### 15 April 2024 * 14:37[14:37, 15 April 2024](https://pve.proxmox.com/mediawiki/index.php?title=NVIDIA_vGPU_on_Proxmox_VE&oldid=11974 "NVIDIA vGPU on Proxmox VE") [diff](https://pve.proxmox.com/mediawiki/index.php?title=NVIDIA_vGPU_on_Proxmox_VE&diff=prev&oldid=11974 "NVIDIA vGPU on Proxmox VE") [hist](https://pve.proxmox.com/mediawiki/index.php?title=NVIDIA_vGPU_on_Proxmox_VE&action=history "NVIDIA vGPU on Proxmox VE") **+582** [NVIDIA vGPU on Proxmox VE](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE "NVIDIA vGPU on Proxmox VE") Mention AI Enterprise Driver testing #### 13 February 2024 * 08:59[08:59, 13 February 2024](https://pve.proxmox.com/mediawiki/index.php?title=NVIDIA_vGPU_on_Proxmox_VE&oldid=11921 "NVIDIA vGPU on Proxmox VE") [diff](https://pve.proxmox.com/mediawiki/index.php?title=NVIDIA_vGPU_on_Proxmox_VE&diff=prev&oldid=11921 "NVIDIA vGPU on Proxmox VE") [hist](https://pve.proxmox.com/mediawiki/index.php?title=NVIDIA_vGPU_on_Proxmox_VE&action=history "NVIDIA vGPU on Proxmox VE") +13 m [NVIDIA vGPU on Proxmox VE](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE "NVIDIA vGPU on Proxmox VE") fix duplicated word and add comma after sequence word Retrieved from "[https://pve.proxmox.com/wiki/Special:Contributions/Hd--](https://pve.proxmox.com/wiki/Special:Contributions/Hd--) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Proxmox VE News - Proxmox VE Proxmox VE News =============== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Proxmox_VE_News#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Proxmox_VE_News#searchInput) Outdated, please follow the Announcement Forum on: [https://forum.proxmox.com/forums/announcements.7/](https://forum.proxmox.com/forums/announcements.7/) ### Proxmox VE 3.1 released! We just released Proxmox VE 3.1, introducing great new features and services. We included [SPICE](https://pve.proxmox.com/wiki/SPICE "SPICE") , GlusterFS storage plugin and the ability to apply updates via GUI (including change logs). As an additional service for our commercial subscribers, we introduce the Proxmox VE Enterprise Repository. This is the default and recommended repository for production servers. To access the Enterprise Repository, each Proxmox VE Server needs a valid Subscription Key - these subscriptions start now at EUR 4,16 per months (was EUR 9,90). There is no change in licensing (AGPL v3), also packages for non-subscribers are still available. A big Thank-you to our active community for all feedback, testing, bug reporting and patch submissions. **Release notes** See [http://pve.proxmox.com/wiki/Roadmap#Proxmox\_VE\_3.1](http://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_3.1) **Download** [http://www.proxmox.com/downloads/category/proxmox-virtual-environment](http://www.proxmox.com/downloads/category/proxmox-virtual-environment) **New Package Repositories** [http://pve.proxmox.com/wiki/Package\_repositories](http://pve.proxmox.com/wiki/Package_repositories) \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 11:16, 21 August 2013 (CET) ### Updates for Proxmox VE 3.0 - including storage migration We just moved a bunch of packages from pvetest to our stable repository, including a lot of bug fixes, code cleanups, qemu 1.4.2 and also a new quite cool new feature - storage migration. A big Thank-you to our active community for all feedback, testing, bug reporting and patch submissions. More details: [http://forum.proxmox.com/threads/14183-Updates-for-Proxmox-VE-3-0-including-storage-migration](http://forum.proxmox.com/threads/14183-Updates-for-Proxmox-VE-3-0-including-storage-migration) \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 11:14, 17 June 2013 (CET) ### Proxmox VE 3.0 released! We just released Proxmox VE 3.0. Its based on the great Debian 7.0 release (Wheezy) and introduces a great new feature set: [http://pve.proxmox.com/wiki/VM\_Templates\_and\_Clones](http://pve.proxmox.com/wiki/VM_Templates_and_Clones) Under the hood, many improvements and optimizations are done, most important is the replacement of Apache2 by our own event driven API server. A big Thank-you to our active community for all feedback, testing, bug reporting and patch submissions. **Release notes** [http://pve.proxmox.com/wiki/Roadmap#Proxmox\_VE\_3.0](http://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_3.0) **Download** [http://www.proxmox.com/downloads](http://www.proxmox.com/downloads) **Upgrade from any 2.3 to 3.0** [http://pve.proxmox.com/wiki/Upgrade\_from\_2.3\_to\_3.0](http://pve.proxmox.com/wiki/Upgrade_from_2.3_to_3.0) **Install Proxmox VE on Debian Wheezy** [http://pve.proxmox.com/wiki/Install\_Proxmox\_VE\_on\_Debian\_Wheezy](http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy) \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 10:11, 24 May 2013 (CET) ### Proxmox VE 2.3 released! We just released Proxmox VE 2.3, including countless improvements and a lot of exiting new features like the new KVM Backup/Restore - without the need of LVM. For more details, see the release notes: [Roadmap#Proxmox\_VE\_2.3](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_2.3 "Roadmap") \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 11:41, 3 March 2013 (CET) ### Proxmox VE 2.2 released! We just released Proxmox VE 2.2, including countless improvements and a lot of exiting new features like live snapshots for KVM guests. For more details, see the release notes: [Roadmap#Proxmox\_VE\_2.2](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_2.2 "Roadmap") \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 10:41, 24 October 2012 (CET) ### KVM 1.1 and new Kernel We just moved a bunch of new packages to our stable repository, including latest stable OpenVZ Kernel (042stab057.1), stable KVM 1.1.1, new cluster package, bug fixes and a lot of code cleanups. Additionally, we added first packages to support two distributed storage technologies - ceph (client) and sheepdog. Both technologies are looking great but note, currently it’s not yet ready for production use. For more details, see the announcement: [http://forum.proxmox.com/threads/10408-KVM-1-1-and-new-Kernel](http://forum.proxmox.com/threads/10408-KVM-1-1-and-new-Kernel) \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 12:40, 25 July 2012 (CET) ### Proxmox VE 2.1 release! We just released Proxmox VE 2.1, including a lot of bug fixes the new [Virtual Machine Startup and Shutdown Behavior](https://pve.proxmox.com/mediawiki/index.php?title=Virtual_Machine_Startup_and_Shutdown_Behavior&action=edit&redlink=1 "Virtual Machine Startup and Shutdown Behavior (page does not exist)") . For more details, see the announcement: [http://forum.proxmox.com/threads/9417-Proxmox-VE-2-1-released](http://forum.proxmox.com/threads/9417-Proxmox-VE-2-1-released) ! \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 11:40, 27 April 2012 (CET) ### Proxmox VE 2.0 final release! We just released Proxmox VE 2.0! A big Thank-you to our active community for all feedback, testing, bug reporting and patch submissions. for more details, see the announcement: [http://forum.proxmox.com/threads/8928-Proxmox-VE-2-0-final-release-](http://forum.proxmox.com/threads/8928-Proxmox-VE-2-0-final-release-) !!! \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 10:44, 30 March 2012 (CET) ### Proxmox VE 2.0 rc1 released! We just uploaded the first release candidate of Proxmox VE 2.0, for more details, see the announcement: [http://forum.proxmox.com/threads/8359-Proxmox-VE-2-0-rc1-released](http://forum.proxmox.com/threads/8359-Proxmox-VE-2-0-rc1-released) ! \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 15:44, 16 February 2012 (CET) ### High Availablity for Proxmox VE 2.0 beta arrived! We just released new packages, introducing High Availability for Proxmox VE 2.0 (beta). For more details, see the announcement: [http://forum.proxmox.com/threads/7855-High-Availablity-for-Proxmox-VE-2-0-beta-arrived](http://forum.proxmox.com/threads/7855-High-Availablity-for-Proxmox-VE-2-0-beta-arrived) ! \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 12:44, 23 December 2011 (CET) ### Proxmox VE 2.0 Video tutorials We started to publish video tutorials for Proxmox VE 2.0 on our Youtube channel. [Proxmox VE Youtube channel](http://www.youtube.com/user/ProxmoxVE) \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 15:14, 21 December 2011 (CET) ### Proxmox VE 2.0 beta released! We just released our first Proxmox VE 2.0 beta (ISO)! Based on the experience with our stable Proxmox VE 1.x series (available since more than 3 years, more than 20.000 installations) we created a complete new architecture to remove all limitations of the current 1.x releases. A big Thank-you to our active community for all feedback, testing, bug reporting and patch submissions. As a commitment to Free Software (FOSS), we also opened today the code repository (git) and bug tracker for the 2.x code base for all. As more or less everything is new, it's quite impossible to list all in a short announcement so I just add important links: **Overview** [http://pve.proxmox.com/wiki/Roadmap#Roadmap\_for\_2.x](http://pve.proxmox.com/wiki/Roadmap#Roadmap_for_2.x) **Documentation** (work in progress) [http://pve.proxmox.com/wiki/Category:Proxmox\_VE\_2.0](http://pve.proxmox.com/wiki/Category:Proxmox_VE_2.0) **Get involved** (incl. links to the public git repository and bugzilla bugtracker): [http://www.proxmox.com/products/proxmox-ve/get-involved](http://www.proxmox.com/products/proxmox-ve/get-involved) **Proxmox VE 2.0 beta forum** [http://forum.proxmox.com](http://forum.proxmox.com/) **Download** [http://www.proxmox.com/downloads/proxmox-ve/17-iso-images](http://www.proxmox.com/downloads/proxmox-ve/17-iso-images) Happy testing, waiting for feedback! \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 11:52, 30 September 2011 (CET) ### Proxmox VE 1.9 released! We just released Proxmox VE 1.9, including the latest stable OpenVZ (2.6.32) and KVM. Release notes: [Roadmap](http://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_1.9) \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 12:14, 13 September 2011 (CET) ### New Proxmox VE 1.8 ISO with latest packages We just released an updated Proxmox VE 1.8 ISO image including our stable packages, especially our latest 2.6.32 Kernel with aacraid module 1.1-7\[28000\]. Release notes: [Roadmap](http://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_1.8) \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 11:15, 16 June 2011 (CET) ### New vzctl and dab, updated appliances We just released a new vzctl package, supporting the immediate reboot of a container using vzeventd. (you need a current 2.6.18 or 2.6.32 kernel, 2.6.24 will NOT work). Additionally, we fixed some issue in dab (supports now dependency based init) and updated a lot of appliances based on latest Debian Squeeze. If you build your own appliances with dab, you should take a look on the example appliances. Release notes: [http://forum.proxmox.com/threads/6316-New-vzctl-and-dab-updated-appliances](http://forum.proxmox.com/threads/6316-New-vzctl-and-dab-updated-appliances) \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 10:33, 10 May 2011 (CET) ### Proxmox VE 1.8 released! We just released Proxmox VE 1.8 including a lot of fixes and updates - a big thanks to all beta testers! This release includes the latest KVM 0.14 with a lot of performance improvements (2.6.32 and 2.6.35 kernel branch) and also the latest stable OpenVZ (see 2.6.18 Kernel branch). Release notes: [Roadmap](http://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_1.8) How to get the latest version: [Downloads](http://pve.proxmox.com/wiki/Downloads) \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 10:33, 30 March 2011 (CET) ### Roadmap for Proxmox VE 2.0 I just released the [Roadmap](http://pve.proxmox.com/wiki/Roadmap) for our upcoming Proxmox VE 2.0 - including some details about the complete new architecture. [http://pve.proxmox.com/wiki/Roadmap](http://pve.proxmox.com/wiki/Roadmap) \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 13:33, 23 February 2011 (CET) ### Proxmox VE 1.7 released! We just released Proxmox VE 1.7 including a lot of fixes and updates - a big thanks to all beta testers! Release notes: [Roadmap](http://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_1.7) How to get the latest version: [Downloads](http://pve.proxmox.com/wiki/Downloads) \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 12:33, 30 November 2010 (CET) ### New Proxmox VE 1.6 kernels, packages and ISO, also first 2.6.35 kernel We just released a bunch of new kernels and updated packages to the stable repository - a big thanks to all beta testers. We also got the first stable 2.6.35 kernel, support KSM again. Release notes: [Roadmap](http://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_1.6_.28updated.29_-_ISO_Installer_with_2.6.32_Kernel_with_OpenVZ_including_KVM_0.12.5) How to get the latest version: [Downloads](http://pve.proxmox.com/wiki/Downloads) \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 12:45, 18 October 2010 (CET) ### ADMIN-Magazine: Article about Proxmox VE (Only in German/Deutsch) The German ADMIM Magazine just published an article about Proxmox VE! Worth reading, especially for beginners. [Proxmox: Container- und Hardware-Virtualisierung unter einem Dach](http://www.admin-magazin.de/content/05-2010-virtualisierung-vom-virtuellen-server-zur-cloud) \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 16:45, 23 September 2010 (CET) ### New Kernels, including fixes for CVE-2010-3081 - and new ISO install image We just released new Kernels (2.6.18, 2.6.24 and 2.6.32) including the fix for CVE-2010-3081. Additionally a new ISO install image, including latest Intel and Broadcom Network drivers. Release notes: [Roadmap](https://pve.proxmox.com/wiki/Roadmap "Roadmap") How to get the latest version: see [Downloads](https://pve.proxmox.com/wiki/Downloads "Downloads") \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 15:45, 20 September 2010 (CET) ### Proxmox VE 1.6 released We just released Proxmox VE 1.6 - now based on the latest 2.6.32 Kernel with OpenVZ support. Release notes: [Roadmap](https://pve.proxmox.com/wiki/Roadmap "Roadmap") How to get the latest version: see [Downloads](https://pve.proxmox.com/wiki/Downloads "Downloads") \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 12:45, 02 September 2010 (CET) ### Proxmox Mail Gateway 2.5 and CYAN Secure Web 1.8.4 - both certified for Proxmox VE We are announcing the release of our Proxmox Mail Gateway 2.5 and CYAN Secure web. You can download the new releases directly via [Central Web-based Management](https://pve.proxmox.com/wiki/Central_Web-based_Management "Central Web-based Management") . Link to the Proxmox VE wiki page for: * [Proxmox\_Mail\_Gateway](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_Mail_Gateway&action=edit&redlink=1 "Proxmox Mail Gateway (page does not exist)") * [CYAN Secure Web](https://pve.proxmox.com/mediawiki/index.php?title=CYAN_Secure_Web&action=edit&redlink=1 "CYAN Secure Web (page does not exist)") \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 10:55, 1 June 2010 (CET) ### New Proxmox VE Kernels 2.6.24 and 2.6.32, including KVM 0.12.4 and gPXE We just released new Kernels (2.6.24 and 2.6.32), latest KVM and some other packages to the stable repository (bugfixes and some new features). Release notes: [Roadmap#Proxmox\_VE\_1.5\_-\_New\_Kernel\_2.6.24\_and\_2.6.32.2C\_including\_KVM\_0.12.4\_and\_gPXE](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_1.5_-_New_Kernel_2.6.24_and_2.6.32.2C_including_KVM_0.12.4_and_gPXE "Roadmap") How to get the latest version: see [Downloads](https://pve.proxmox.com/wiki/Downloads "Downloads") \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 11:45, 17 May 2010 (CET) ### Proxmox VE on Intel Modular Server We just added an [Intel Modular Server](http://www.intelmodularserver.com/) to our test lab and I created a first simple howto about an example configuration. All current and future versions of Proxmox VE will be tested and validated against this server. A big thanks to Intel, sponsoring the hardware to the Proxmox VE test lab! For all details, see [Intel Modular Server](https://pve.proxmox.com/mediawiki/index.php?title=Intel_Modular_Server&action=edit&redlink=1 "Intel Modular Server (page does not exist)") \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 12:05, 24 March 2010 (CET) ### LWN.net: Article about Proxmox VE Koen Vervloesem contributed an article on LWN.net: [Proxmox VE 1.5: combining KVM and OpenVZ](http://lwn.net/Articles/375075/) \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 12:05, 4 March 2010 (CET) ### Proxmox VE 1.5 released We just released Proxmox VE 1.5 - including a lot of fixes and updated drivers due to the feedback from beta testers - a big thanks to all. Release notes: [Roadmap](https://pve.proxmox.com/wiki/Roadmap "Roadmap") How to get the latest version: see [Downloads](https://pve.proxmox.com/wiki/Downloads "Downloads") \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 11:45, 20 January 2010 (CET) ### Updated appliances, including Request Tracker 3.8.7 (RT) based on Debian Squeeze We just released several updated appliances for Proxmox VE: (We used the [Debian\_Appliance\_Builder](https://pve.proxmox.com/wiki/Debian_Appliance_Builder "Debian Appliance Builder") to create all) **Updated OS appliances:** * [Debian 4.0 Standard](https://pve.proxmox.com/mediawiki/index.php?title=Debian_4.0_Standard&action=edit&redlink=1 "Debian 4.0 Standard (page does not exist)") * Debian 4.0 Standard (amd64) * [Debian 5.0 Standard](https://pve.proxmox.com/mediawiki/index.php?title=Debian_5.0_Standard&action=edit&redlink=1 "Debian 5.0 Standard (page does not exist)") * Debian 5.0 Standard (amd64) * [Debian 6.0 Standard](https://pve.proxmox.com/mediawiki/index.php?title=Debian_6.0_Standard&action=edit&redlink=1 "Debian 6.0 Standard (page does not exist)") * Debian 6.0 Standard (amd64) * [Ubuntu Hardy Standard](https://pve.proxmox.com/mediawiki/index.php?title=Ubuntu_Hardy_Standard&action=edit&redlink=1 "Ubuntu Hardy Standard (page does not exist)") * Ubuntu Hardy Standard (amd64) **Updated application appliances:** * [Proxmox Mail Gateway](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_Mail_Gateway&action=edit&redlink=1 "Proxmox Mail Gateway (page does not exist)") * [CYAN Secure Web](https://pve.proxmox.com/mediawiki/index.php?title=CYAN_Secure_Web&action=edit&redlink=1 "CYAN Secure Web (page does not exist)") * [Acquia Drupal](https://pve.proxmox.com/mediawiki/index.php?title=Acquia_Drupal&action=edit&redlink=1 "Acquia Drupal (page does not exist)") * [Drupal](https://pve.proxmox.com/mediawiki/index.php?title=Drupal&action=edit&redlink=1 "Drupal (page does not exist)") * [SugarCRM](https://pve.proxmox.com/mediawiki/index.php?title=SugarCRM&action=edit&redlink=1 "SugarCRM (page does not exist)") * [Zenoss](https://pve.proxmox.com/mediawiki/index.php?title=Zenoss&action=edit&redlink=1 "Zenoss (page does not exist)") * [MediaWiki](https://pve.proxmox.com/mediawiki/index.php?title=MediaWiki&action=edit&redlink=1 "MediaWiki (page does not exist)") * [Joomla!](https://pve.proxmox.com/mediawiki/index.php?title=Joomla!&action=edit&redlink=1 "Joomla! (page does not exist)") * [Wordpress](https://pve.proxmox.com/mediawiki/index.php?title=Wordpress&action=edit&redlink=1 "Wordpress (page does not exist)") * [Joomla!](https://pve.proxmox.com/mediawiki/index.php?title=Joomla!&action=edit&redlink=1 "Joomla! (page does not exist)") * [RT Request Tracker](https://pve.proxmox.com/mediawiki/index.php?title=RT_Request_Tracker&action=edit&redlink=1 "RT Request Tracker (page does not exist)") * [Wordpress](https://pve.proxmox.com/mediawiki/index.php?title=Wordpress&action=edit&redlink=1 "Wordpress (page does not exist)") You can download all appliances directly to your Proxmox VE via "VM Manager/Appliance Templates - Download". For a complete list, see [Get\_Virtual\_Appliances](https://pve.proxmox.com/mediawiki/index.php?title=Get_Virtual_Appliances&action=edit&redlink=1 "Get Virtual Appliances (page does not exist)") \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 15:04, 14 January 2010 (CET) ### New Proxmox VE Kernel with kvm-kmod-2.6.31.6 We just moved the latest kernel (pve-kernel-2.6.24-9-pve\_2.6.24-18\_amd64.deb) from the testing to the stable repository (pve). Release notes: * update kvm to kvm-kmod-2.6.31.6.tar.bz2 * update e1000e to e1000e-1.0.15.tar.gz * kernel security fixes \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 10:05, 19 November 2009 (CET) ### Proxmox VE 1.4 released We just released Proxmox VE 1.4 - including a lot of fixes and updated drivers due to the feedback from beta testers - a big thanks to all. This is the first stable release supporting the new storage model (iSCSI, NFS, DRBD, FC,...). Release notes: [Roadmap](https://pve.proxmox.com/wiki/Roadmap "Roadmap") How to get the latest version: see [Downloads](https://pve.proxmox.com/wiki/Downloads "Downloads") \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 19:05, 19 October 2009 (CET) ### Proxmox VE 1.4 beta2 released - new KVM We just released Proxmox VE 1.4 beta2 - including a lot of fixes and updated drivers due to the feedback from beta testers - a big thanks to all. Additionally, we included a new KVM version. This is beta release so its not intended for production use without special attention. Please report all issue and comments into this forum. Release notes: [Roadmap](https://pve.proxmox.com/wiki/Roadmap "Roadmap") How to get the latest version: see [Downloads](https://pve.proxmox.com/wiki/Downloads "Downloads") \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 15:05, 29 September 2009 (CET) ### Montanalinux.org: Interview with Martin Maurer (CEO) about Proxmox VE Scott Dowdle from Montanalinux published an Interview on his blog: [http://www.montanalinux.org/proxmox-ve-martin-interview.html](http://www.montanalinux.org/proxmox-ve-martin-interview.html) \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 15:05, 18 September 2009 (CET) ### Proxmox VE 1.4 beta1 released - New storage model!!! We just released Proxmox VE 1.4 beta1 - a major milestone and a really big step forward. I also published two new wiki articles: [Storage\_Model](https://pve.proxmox.com/mediawiki/index.php?title=Storage_Model&action=edit&redlink=1 "Storage Model (page does not exist)") and [DRBD](https://pve.proxmox.com/wiki/DRBD "DRBD") We encourage everybody to test all new features including the new vzdump (KVM). This is beta release so its not intended for production use without special attention. Please report all issue and comments into this forum. For all translators: Please grab the latest [po file](ftp://download.proxmox.com/sources/po-files/) and submit it directly to martin(at)proxmox.com - big thanks in advance for this. Release notes: [Roadmap](https://pve.proxmox.com/wiki/Roadmap "Roadmap") How to get the latest version: see [Downloads](https://pve.proxmox.com/wiki/Downloads "Downloads") \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 12:05, 11 September 2009 (CET) ### ...and the winner is: Proxmox VE - Constantinus Award 2009 Open source We got it! Many thanks to the whole development team and all active users and community members. \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 10:06, 17 June 2009 (CET) ### Proxmox VE 1.3 (Lenny based, KVM-86, build 4023) released We just released Proxmox VE 1.3 including the latest KVM-86. Release notes: [Roadmap](https://pve.proxmox.com/wiki/Roadmap "Roadmap") How to get the latest version: see [Downloads](https://pve.proxmox.com/wiki/Downloads "Downloads") \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 10:57, 4 June 2009 (CET) ### Proxmox VE project is nominated for Constantinus Award 2009 The CONSTANTINUS Award has become the leading national award for knowledge-based services in Austria and has been recognized by the Austrian Federal Government as the sole qualifying process for the Federal State Award (Staatspreis) 'Consulting/Knowledge based services'. Proxmox VE is nominated in the category "Open Source". Information in German: Der Constantinus Award ist Österreichs großer IT- und Beraterpreis, der heuer bereits zum siebenten Mal verliehen wird. Mitglieder des Fachverbandes Unternehmensberatung und IT (UBIT) konnten ab Februar 2009 ihre besten Beratungsprojekte in den fünf Kategorien Informationstechnologie, Kommunikation & Netzwerke, Management Consulting, Open Source und Personal & Training einreichen. Im Rahmen der Constantinus Gala am 16. Juni 2009 werden die besten Projekte dieser Kategorien ausgezeichnet. Vergeben werden außerdem die Sonderpreise "Constantinus International", der "Jungunternehmerpreis" und die Auszeichnung in der Kategorie "Rechnungswesen". Erstmals wird in diesem Jahr in Kooperation mit "u19 - freestyle computing" der Ars Electronica auch die Auszeichnung "Junior Constantinus" für herausragende Projekte des IT-Nachwuchses vergeben. Mit 147 Einreichungen wurde heuer ein Teilnahmerekord verzeichnet, der zeigt, dass sich der Constantinus als fixe Größe der österreichischen Beraterszene etabliert hat und in Zeiten unsicherer Konjunkturprognosen noch an Bedeutung gewonnen hat. \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 17:06, 1 June 2009 (CET) ### Proxmox VE 1.2 (Lenny based, KVM-85, build 3892) released We just released Proxmox VE 1.2. This is the first Debian Lenny based version, including the lastest KVM-85. Release notes: [Roadmap](https://pve.proxmox.com/wiki/Roadmap "Roadmap") How to get the latest version: see [Downloads](https://pve.proxmox.com/wiki/Downloads "Downloads") \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 14:06, 12 May 2009 (CET) ### Updated Cyan Secure Web (1.6.4) and Acquia Drupal (1.2.8) Appliances We just released two updated Appliances for Proxmox VE: * [Acquia\_Drupal](https://pve.proxmox.com/mediawiki/index.php?title=Acquia_Drupal&action=edit&redlink=1 "Acquia Drupal (page does not exist)") (based on Debian Lenny) * [CYAN Secure Web](https://pve.proxmox.com/mediawiki/index.php?title=CYAN_Secure_Web&action=edit&redlink=1 "CYAN Secure Web (page does not exist)") (based on Ubuntu 8.04 Hardy) **What is special here?** Both appliances are built and tested from the Proxmox team but also tested and certified from the vendor - Acquia and Cyan Networks. For both appliances you need a commercial subscription but therefore you have support from the Proxmox platform and the application vendor - that's a big advantage and one reason why software from Redmond is so successful in the enterprise world. With Proxmox VE you can also get this with open source based Linux software. We used the [Debian\_Appliance\_Builder](https://pve.proxmox.com/wiki/Debian_Appliance_Builder "Debian Appliance Builder") to create both and we encourage other open source and commercial Linux application vendors to jump in into this successful way to distribute software to the enterprise. \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 12:42, 7 May 2009 (CEST) ### New Mail Gateway V 2.3 release for Proxmox VE We are announcing the final release of our Proxmox Mail Gateway 2.3 for Proxmox VE. You can download the new release directy via [Central Web-based Management](https://pve.proxmox.com/wiki/Central_Web-based_Management "Central Web-based Management") . For detailed information see [release notes](http://www.proxmox.com/cms_proxmox/en/home/news/2009-03-16-proxmox-mail-gateway-2.3-released.html) Link to the Proxmox VE wiki page for: [Proxmox\_Mail\_Gateway](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_Mail_Gateway&action=edit&redlink=1 "Proxmox Mail Gateway (page does not exist)") \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 10:55, 17 March 2009 (CET) ### New SugarCRM and Zenoss (Ubuntu based) Appliances We just released two new Appliances for Proxmox VE: * [SugarCRM](https://pve.proxmox.com/mediawiki/index.php?title=SugarCRM&action=edit&redlink=1 "SugarCRM (page does not exist)") (based on Debian Lenny) * [Zenoss](https://pve.proxmox.com/mediawiki/index.php?title=Zenoss&action=edit&redlink=1 "Zenoss (page does not exist)") (based on Ubuntu 8.04 Hardy) We used the [Debian\_Appliance\_Builder](https://pve.proxmox.com/wiki/Debian_Appliance_Builder "Debian Appliance Builder") to create both appliances. About SugarCRM: SugarCRM is the world's leading provider of commercial open source customer relationship management (CRM) software for companies of all sizes. About Zenoss: Zenoss Core is an award-winning open source IT monitoring product that delivers the functionality to effectively manage the configuration, health and performance of networks, servers and applications through a single, integrated software package. You can download all appliances directly to your Proxmox VE via "VM Manager/Appliance Templates - Download". \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 10:46, 27 January 2009 (CET) ### New Appliances, including Request Tracker (RT) We just released two new Appliances for Proxmox VE and updated all the rest: [RT Request Tracker](https://pve.proxmox.com/mediawiki/index.php?title=RT_Request_Tracker&action=edit&redlink=1 "RT Request Tracker (page does not exist)") and [Wordpress](https://pve.proxmox.com/mediawiki/index.php?title=Wordpress&action=edit&redlink=1 "Wordpress (page does not exist)") (We used the [Debian\_Appliance\_Builder](https://pve.proxmox.com/wiki/Debian_Appliance_Builder "Debian Appliance Builder") to create all) About Request Tracker: RT is the leading open-source issue- and ticket-tracking system, providing enterprise-grade quality and reliability. About Wordpress: WordPress is a state-of-the-art publishing platform with a focus on aesthetics, web standards, and usability. WordPress is both free and priceless at the same time. Updated appliances: * [MediaWiki](https://pve.proxmox.com/mediawiki/index.php?title=MediaWiki&action=edit&redlink=1 "MediaWiki (page does not exist)") * [Acquia Drupal](https://pve.proxmox.com/mediawiki/index.php?title=Acquia_Drupal&action=edit&redlink=1 "Acquia Drupal (page does not exist)") * [Drupal](https://pve.proxmox.com/mediawiki/index.php?title=Drupal&action=edit&redlink=1 "Drupal (page does not exist)") * [Joomla!](https://pve.proxmox.com/mediawiki/index.php?title=Joomla!&action=edit&redlink=1 "Joomla! (page does not exist)") * [Debian 4.0 Standard](https://pve.proxmox.com/mediawiki/index.php?title=Debian_4.0_Standard&action=edit&redlink=1 "Debian 4.0 Standard (page does not exist)") * [Debian 5.0 Standard](https://pve.proxmox.com/mediawiki/index.php?title=Debian_5.0_Standard&action=edit&redlink=1 "Debian 5.0 Standard (page does not exist)") * [Ubuntu Hardy Standard](https://pve.proxmox.com/mediawiki/index.php?title=Ubuntu_Hardy_Standard&action=edit&redlink=1 "Ubuntu Hardy Standard (page does not exist)") You can download all appliances directly to your Proxmox VE via "VM Manager/Appliance Templates - Download". \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 11:49, 21 January 2009 (CET) ### 'dab' Debian/Ubuntu Appliance Builder released! We just published our Debian/Ubuntu appliance builder for OpenVZ (of course perfectly usable on Proxmox VE). Anybody is talking about the economic and financial crisis – a good chance to bring powerful open source software to the enterprise customer – start now using OpenVZ for virtual appliances! All details: [Debian\_Appliance\_Builder](https://pve.proxmox.com/wiki/Debian_Appliance_Builder "Debian Appliance Builder") \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 10:06, 20 January 2009 (CET) ### New Proxmox VE 1.1 (build 3664) released We just released a Proxmox VE 1.1. Main feature is an improved Kernel including the latest version of KVM (KVM-83). * Updated Kernel - new e1000/e1000e drivers * New KVM with many improvements (KVM-83) * New Chinese translations * Minor pve-manager updates and bug fixes Howto get the lastest version: see [Downloads](https://pve.proxmox.com/wiki/Downloads "Downloads") \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 11:06, 15 January 2009 (CET) ### Zimbra on Proxmox VE Just created a wiki page describing how to install [Zimbra](http://www.zimbra.com/community/) on Proxmox VE. Zimbra is a client and server platform for next-generation messaging and collaboration - a very interesting alternative to MS Exchange. Link to the wiki page: [Zimbra](https://pve.proxmox.com/mediawiki/index.php?title=Zimbra&action=edit&redlink=1 "Zimbra (page does not exist)") \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 10:55, 2 December 2008 (CET) ### Commercial support for Proxmox VE Proxmox VE is used in many productive environments. In order to get guaranteed direct support from the developers support ticket subscription can be [purchased](https://www.maurer-it.com/shop/index.php?cPath=31) . All support details: [Get\_support](https://pve.proxmox.com/wiki/Get_support "Get support") \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 11:29, 28 November 2008 (CET) ### New Proxmox VE 1.0 (build 3451) released We just released a few new Proxmox VE 1.0 packages, containing small bug fixes. * Installer fixes (including the ability to install if the motherboard BIOS has an old time) * pve-manager update * added ability to add 'Notes' for VMs * fix shutdown problem * fix RFB protocol problem * fix SOAP serializer bug * fix url redirect bug * fix utf8 problem for error messages * updated translations (hu, ro) * vzctl template fix * qemu-server (fix status problem) **HowTo upgrade a running Proxmox VE 1.0 to 3451** Just run: apt-get update apt-get upgrade \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 14:12, 14 November 2008 (CET) ### New Joomla! (1.5.8) and Zenoss (2.3) Appliances We just released two new Appliances for Proxmox VE. [Joomla!](https://pve.proxmox.com/mediawiki/index.php?title=Joomla!&action=edit&redlink=1 "Joomla! (page does not exist)") and [Zenoss](https://pve.proxmox.com/mediawiki/index.php?title=Zenoss&action=edit&redlink=1 "Zenoss (page does not exist)") You can download all appliances directly to your Proxmox VE via "VM Manager/Appliance Templates - Download". About Joomla!: Joomla! is one of the most powerful Open Source Content Management Systems on the planet. It is used all over the world for everything from simple websites to complex corporate applications. Joomla! is easy to install, simple to manage, and reliable. About Zenoss: Zenoss Core is an award-winning open source IT monitoring product that delivers the functionality to effectively manage the configuration, health and performance of networks, servers and applications through a single, integrated software package. \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 12:31, 14 November 2008 (CET) ### New Video Tutorials We just released a bunch of [Video Tutorials](https://pve.proxmox.com/mediawiki/index.php?title=Category:Video_Tutorials&action=edit&redlink=1 "Category:Video Tutorials (page does not exist)") . This is an easy way to introduce Proxmox VE features to users. If you miss something just make suggestions for new tutorials. \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 12:57, 13 November 2008 (CET) ### Backup with vzdump - new GUI We introduced a new GUI for vzdump. Now its possible to create multiple scheduled backups via web interface. * Including support to store the backups on remote locations (Samba share, NFS) * Support for containers (OpenVZ) and KVM virtual machines For details see: [Backup - Restore - Live Migration](https://pve.proxmox.com/mediawiki/index.php?title=Backup_-_Restore_-_Live_Migration&action=edit&redlink=1 "Backup - Restore - Live Migration (page does not exist)") \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 15:50, 30 October 2008 (CET) ### Certified Appliances Certified appliances are fully supported from the Proxmox VE team AND the software vendor. They are ready for production use. * [Get Certified Virtual Appliances](https://pve.proxmox.com/mediawiki/index.php?title=Get_Certified_Virtual_Appliances&action=edit&redlink=1 "Get Certified Virtual Appliances (page does not exist)") \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 13:57, 30 October 2008 (CET) ### Updated Appliances Release of updated appliances, based on Debian 4.0r5. All Debian based appliances are fully supported from the Proxmox VE team and production ready. * [SugarCRM](https://pve.proxmox.com/mediawiki/index.php?title=SugarCRM&action=edit&redlink=1 "SugarCRM (page does not exist)") * [Zenoss](https://pve.proxmox.com/mediawiki/index.php?title=Zenoss&action=edit&redlink=1 "Zenoss (page does not exist)") * [MediaWiki](https://pve.proxmox.com/mediawiki/index.php?title=MediaWiki&action=edit&redlink=1 "MediaWiki (page does not exist)") * [Acquia Drupal](https://pve.proxmox.com/mediawiki/index.php?title=Acquia_Drupal&action=edit&redlink=1 "Acquia Drupal (page does not exist)") * [Drupal](https://pve.proxmox.com/mediawiki/index.php?title=Drupal&action=edit&redlink=1 "Drupal (page does not exist)") * [Joomla!](https://pve.proxmox.com/mediawiki/index.php?title=Joomla!&action=edit&redlink=1 "Joomla! (page does not exist)") Update OS templates: * [Debian 4.0 Standard](https://pve.proxmox.com/mediawiki/index.php?title=Debian_4.0_Standard&action=edit&redlink=1 "Debian 4.0 Standard (page does not exist)") * [CentOS 5 Standard](https://pve.proxmox.com/mediawiki/index.php?title=CentOS_5_Standard&action=edit&redlink=1 "CentOS 5 Standard (page does not exist)") * [CentOS 4 Standard](https://pve.proxmox.com/mediawiki/index.php?title=CentOS_4_Standard&action=edit&redlink=1 "CentOS 4 Standard (page does not exist)") * [Fedora 9 Standard](https://pve.proxmox.com/mediawiki/index.php?title=Fedora_9_Standard&action=edit&redlink=1 "Fedora 9 Standard (page does not exist)") \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 13:57, 29 October 2008 (CET) ### Proxmox VE 1.0 - First stable release Released 29.10.2008: See [Downloads](https://pve.proxmox.com/wiki/Downloads "Downloads") Including: * KVM and OpenVZ live migration * Web interface for vzdump backups * Improved vzdump, now support KVM guests * New templates available * Support multiple languages (see [Translations](https://pve.proxmox.com/wiki/Translations "Translations") for details) * Improved installer (use grub as boot loader, automatic country/keyboard detection) * Support up to 16 CPUs * Based on Debian 4.0r5 * KVM updates (kvm-75) * OpenVZ updates, Fedora support added * Improved Kernel (includes drivers for ISCSI, AoE 6-64, DRBD 8.2.6, qlogic firmware for ISCSI/FC HBAs) * Many bugfixes \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 12:57, 29 October 2008 (CET) ### Proxmox VE 0.9beta2 released Released 22.7.2008, see [Proxmox VE 0.9beta2 released!](http://www.proxmox.com/forum/showthread.php?t=533) Including: * Extend pre-built Virtual Appliances downloads * Multi-bridge support * Bonding * VLAN support * Extend web interface for KVM guests (add hard drives, network cards, etc.) * Many bug fixes \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 12:57, 22 July 2008 (CET) ### Proxmox VE 0.9 released First public release: 15.4.2008 \--[Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin") 12:57, 15 April 2008 (CET) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Proxmox\_VE\_News&oldid=8143](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_VE_News&oldid=8143) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Upgrade from 1.9 to 2.0" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Upgrade from 1.9 to 2.0" ============================================ ← [Upgrade from 1.9 to 2.0](https://pve.proxmox.com/wiki/Upgrade_from_1.9_to_2.0 "Upgrade from 1.9 to 2.0") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Upgrade_from_1.9_to_2.0#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Upgrade_from_1.9_to_2.0#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Upgrade from 1.9 to 2.0](https://pve.proxmox.com/wiki/Upgrade_from_1.9_to_2.0 "Upgrade from 1.9 to 2.0") **: Displaying 1 item. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_1.9_to_2.0&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_1.9_to_2.0&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_1.9_to_2.0&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_1.9_to_2.0&limit=500) ) * [Downloads](https://pve.proxmox.com/wiki/Downloads "Downloads") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Downloads "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_1.9_to_2.0&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_1.9_to_2.0&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_1.9_to_2.0&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_1.9_to_2.0&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Upgrade\_from\_1.9\_to\_2.0](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Upgrade_from_1.9_to_2.0) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Help:Contents" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Help:Contents" ================================== ← [Help:Contents](https://pve.proxmox.com/mediawiki/index.php?title=Help:Contents&action=edit&redlink=1 "Help:Contents (page does not exist)") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Help:Contents#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Help:Contents#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Help:Contents](https://pve.proxmox.com/mediawiki/index.php?title=Help:Contents&action=edit&redlink=1 "Help:Contents (page does not exist)") **: Displaying 50 items. View (previous 50 | [next 50](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Help:Contents&limit=50&dir=next&offset=3%7C598) ) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Help:Contents&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Help:Contents&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Help:Contents&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Help:Contents&limit=500) ) * [Talk:Schtirliz](https://pve.proxmox.com/wiki/Talk:Schtirliz "Talk:Schtirliz") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Talk%3ASchtirliz "Special:WhatLinksHere") ) * [User talk:Martin Maurer](https://pve.proxmox.com/wiki/User_talk:Martin_Maurer "User talk:Martin Maurer") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AMartin+Maurer "Special:WhatLinksHere") ) * [User talk:Test test1](https://pve.proxmox.com/wiki/User_talk:Test_test1 "User talk:Test test1") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3ATest+test1 "Special:WhatLinksHere") ) * [User talk:Carlos Palacio](https://pve.proxmox.com/wiki/User_talk:Carlos_Palacio "User talk:Carlos Palacio") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3ACarlos+Palacio "Special:WhatLinksHere") ) * [User talk:Michael Bunk](https://pve.proxmox.com/wiki/User_talk:Michael_Bunk "User talk:Michael Bunk") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AMichael+Bunk "Special:WhatLinksHere") ) * [User talk:Federico Pereira](https://pve.proxmox.com/wiki/User_talk:Federico_Pereira "User talk:Federico Pereira") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AFederico+Pereira "Special:WhatLinksHere") ) * [User talk:Edson Maia dos Reis](https://pve.proxmox.com/wiki/User_talk:Edson_Maia_dos_Reis "User talk:Edson Maia dos Reis") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AEdson+Maia+dos+Reis "Special:WhatLinksHere") ) * [User talk:Pcravero](https://pve.proxmox.com/wiki/User_talk:Pcravero "User talk:Pcravero") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3APcravero "Special:WhatLinksHere") ) * [User talk:Skyblaster](https://pve.proxmox.com/wiki/User_talk:Skyblaster "User talk:Skyblaster") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3ASkyblaster "Special:WhatLinksHere") ) * [User talk:Stuart Robertson](https://pve.proxmox.com/wiki/User_talk:Stuart_Robertson "User talk:Stuart Robertson") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AStuart+Robertson "Special:WhatLinksHere") ) * [User talk:David Henriks](https://pve.proxmox.com/wiki/User_talk:David_Henriks "User talk:David Henriks") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3ADavid+Henriks "Special:WhatLinksHere") ) * [User talk:Tristan Donkers](https://pve.proxmox.com/wiki/User_talk:Tristan_Donkers "User talk:Tristan Donkers") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3ATristan+Donkers "Special:WhatLinksHere") ) * [User talk:Johan Borg](https://pve.proxmox.com/wiki/User_talk:Johan_Borg "User talk:Johan Borg") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AJohan+Borg "Special:WhatLinksHere") ) * [User talk:Simon CORSIN](https://pve.proxmox.com/wiki/User_talk:Simon_CORSIN "User talk:Simon CORSIN") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3ASimon+CORSIN "Special:WhatLinksHere") ) * [User talk:Marcus Elmang](https://pve.proxmox.com/wiki/User_talk:Marcus_Elmang "User talk:Marcus Elmang") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AMarcus+Elmang "Special:WhatLinksHere") ) * [User talk:Slotti](https://pve.proxmox.com/wiki/User_talk:Slotti "User talk:Slotti") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3ASlotti "Special:WhatLinksHere") ) * [User talk:Harald Kapper](https://pve.proxmox.com/wiki/User_talk:Harald_Kapper "User talk:Harald Kapper") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AHarald+Kapper "Special:WhatLinksHere") ) * [User talk:Denis Arnaud](https://pve.proxmox.com/wiki/User_talk:Denis_Arnaud "User talk:Denis Arnaud") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3ADenis+Arnaud "Special:WhatLinksHere") ) * [User talk:Deejay2](https://pve.proxmox.com/wiki/User_talk:Deejay2 "User talk:Deejay2") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3ADeejay2 "Special:WhatLinksHere") ) * [User talk:Juliencosmao](https://pve.proxmox.com/wiki/User_talk:Juliencosmao "User talk:Juliencosmao") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AJuliencosmao "Special:WhatLinksHere") ) * [User talk:Fidel Alvarez Glez](https://pve.proxmox.com/wiki/User_talk:Fidel_Alvarez_Glez "User talk:Fidel Alvarez Glez") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AFidel+Alvarez+Glez "Special:WhatLinksHere") ) * [User talk:Renow](https://pve.proxmox.com/wiki/User_talk:Renow "User talk:Renow") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3ARenow "Special:WhatLinksHere") ) * [User talk:Holger Ernst](https://pve.proxmox.com/wiki/User_talk:Holger_Ernst "User talk:Holger Ernst") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AHolger+Ernst "Special:WhatLinksHere") ) * [User talk:Aaron C. de Bruyn](https://pve.proxmox.com/wiki/User_talk:Aaron_C._de_Bruyn "User talk:Aaron C. de Bruyn") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AAaron+C.+de+Bruyn "Special:WhatLinksHere") ) * [User talk:Caihexin](https://pve.proxmox.com/wiki/User_talk:Caihexin "User talk:Caihexin") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3ACaihexin "Special:WhatLinksHere") ) * [User talk:Joshua Shoemaker](https://pve.proxmox.com/wiki/User_talk:Joshua_Shoemaker "User talk:Joshua Shoemaker") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AJoshua+Shoemaker "Special:WhatLinksHere") ) * [User talk:Pedro.larva](https://pve.proxmox.com/wiki/User_talk:Pedro.larva "User talk:Pedro.larva") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3APedro.larva "Special:WhatLinksHere") ) * [User talk:Stanislav](https://pve.proxmox.com/wiki/User_talk:Stanislav "User talk:Stanislav") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AStanislav "Special:WhatLinksHere") ) * [User talk:Matt Boyle](https://pve.proxmox.com/wiki/User_talk:Matt_Boyle "User talk:Matt Boyle") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AMatt+Boyle "Special:WhatLinksHere") ) * [User talk:Ahe](https://pve.proxmox.com/wiki/User_talk:Ahe "User talk:Ahe") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AAhe "Special:WhatLinksHere") ) * [User talk:Alexandre Derumier](https://pve.proxmox.com/wiki/User_talk:Alexandre_Derumier "User talk:Alexandre Derumier") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AAlexandre+Derumier "Special:WhatLinksHere") ) * [User talk:Robert Brockway](https://pve.proxmox.com/wiki/User_talk:Robert_Brockway "User talk:Robert Brockway") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3ARobert+Brockway "Special:WhatLinksHere") ) * [User talk:Frank Ernesto](https://pve.proxmox.com/wiki/User_talk:Frank_Ernesto "User talk:Frank Ernesto") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AFrank+Ernesto "Special:WhatLinksHere") ) * [User talk:Emmanuel Borlet](https://pve.proxmox.com/wiki/User_talk:Emmanuel_Borlet "User talk:Emmanuel Borlet") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AEmmanuel+Borlet "Special:WhatLinksHere") ) * [User talk:Benjamin Redling](https://pve.proxmox.com/wiki/User_talk:Benjamin_Redling "User talk:Benjamin Redling") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3ABenjamin+Redling "Special:WhatLinksHere") ) * [User talk:Oleg](https://pve.proxmox.com/wiki/User_talk:Oleg "User talk:Oleg") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AOleg "Special:WhatLinksHere") ) * [User talk:Ikux](https://pve.proxmox.com/wiki/User_talk:Ikux "User talk:Ikux") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AIkux "Special:WhatLinksHere") ) * [User talk:Fabrizio Barnini](https://pve.proxmox.com/wiki/User_talk:Fabrizio_Barnini "User talk:Fabrizio Barnini") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AFabrizio+Barnini "Special:WhatLinksHere") ) * [User talk:Jose Raul Romero Mera](https://pve.proxmox.com/wiki/User_talk:Jose_Raul_Romero_Mera "User talk:Jose Raul Romero Mera") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AJose+Raul+Romero+Mera "Special:WhatLinksHere") ) * [User talk:André Ulrich](https://pve.proxmox.com/wiki/User_talk:Andr%C3%A9_Ulrich "User talk:André Ulrich") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AAndr%C3%A9+Ulrich "Special:WhatLinksHere") ) * [User talk:Jorarome](https://pve.proxmox.com/wiki/User_talk:Jorarome "User talk:Jorarome") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AJorarome "Special:WhatLinksHere") ) * [User talk:Marc Cirauqui](https://pve.proxmox.com/wiki/User_talk:Marc_Cirauqui "User talk:Marc Cirauqui") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AMarc+Cirauqui "Special:WhatLinksHere") ) * [User talk:Wade Klaver](https://pve.proxmox.com/wiki/User_talk:Wade_Klaver "User talk:Wade Klaver") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AWade+Klaver "Special:WhatLinksHere") ) * [User talk:José Román Bilbao-Castro](https://pve.proxmox.com/wiki/User_talk:Jos%C3%A9_Rom%C3%A1n_Bilbao-Castro "User talk:José Román Bilbao-Castro") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AJos%C3%A9+Rom%C3%A1n+Bilbao-Castro "Special:WhatLinksHere") ) * [User talk:Koen Calliauw](https://pve.proxmox.com/wiki/User_talk:Koen_Calliauw "User talk:Koen Calliauw") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AKoen+Calliauw "Special:WhatLinksHere") ) * [User talk:Eric Blevins](https://pve.proxmox.com/wiki/User_talk:Eric_Blevins "User talk:Eric Blevins") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AEric+Blevins "Special:WhatLinksHere") ) * [User talk:Jieqiong ou](https://pve.proxmox.com/wiki/User_talk:Jieqiong_ou "User talk:Jieqiong ou") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AJieqiong+ou "Special:WhatLinksHere") ) * [User talk:Jose Luis Moya](https://pve.proxmox.com/wiki/User_talk:Jose_Luis_Moya "User talk:Jose Luis Moya") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AJose+Luis+Moya "Special:WhatLinksHere") ) * [User talk:Alaa](https://pve.proxmox.com/wiki/User_talk:Alaa "User talk:Alaa") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AAlaa "Special:WhatLinksHere") ) * [User talk:Niall Douglas](https://pve.proxmox.com/wiki/User_talk:Niall_Douglas "User talk:Niall Douglas") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3ANiall+Douglas "Special:WhatLinksHere") ) View (previous 50 | [next 50](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Help:Contents&limit=50&dir=next&offset=3%7C598) ) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Help:Contents&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Help:Contents&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Help:Contents&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Help:Contents&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Help:Contents](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Help:Contents) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # MediaWiki:Noindex-category - Proxmox VE MediaWiki:Noindex-category ========================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/MediaWiki:Noindex-category#mw-head) [Jump to search](https://pve.proxmox.com/wiki/MediaWiki:Noindex-category#searchInput) Noindexed pages Retrieved from "[https://pve.proxmox.com/wiki/MediaWiki:Noindex-category](https://pve.proxmox.com/wiki/MediaWiki:Noindex-category) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Template:Emptylang" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Template:Emptylang" ======================================= ← [Template:Emptylang](https://pve.proxmox.com/mediawiki/index.php?title=Template:Emptylang&action=edit&redlink=1 "Template:Emptylang (page does not exist)") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Template:Emptylang#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Template:Emptylang#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Template:Emptylang](https://pve.proxmox.com/mediawiki/index.php?title=Template:Emptylang&action=edit&redlink=1 "Template:Emptylang (page does not exist)") **: Displaying 1 item. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Template:Emptylang&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Template:Emptylang&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Template:Emptylang&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Template:Emptylang&limit=500) ) * [Template:Languages](https://pve.proxmox.com/wiki/Template:Languages "Template:Languages") (transclusion) ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Template%3ALanguages "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Template:Emptylang&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Template:Emptylang&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Template:Emptylang&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Template:Emptylang&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Template:Emptylang](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Template:Emptylang) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Install Proxmox VE on Debian 11 Bullseye - Proxmox VE Install Proxmox VE on Debian 11 Bullseye ======================================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye#Introduction) * [2 Install a standard Debian Bullseye (amd64)](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye#Install_a_standard_Debian_Bullseye_(amd64)) * [2.1 Add an /etc/hosts entry for your IP address](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye#Add_an_/etc/hosts_entry_for_your_IP_address) * [3 Install Proxmox VE](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye#Install_Proxmox_VE) * [3.1 Adapt your sources.list](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye#Adapt_your_sources.list) * [3.2 Install the Proxmox VE Kernel](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye#Install_the_Proxmox_VE_Kernel) * [3.3 Install the Proxmox VE packages](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye#Install_the_Proxmox_VE_packages) * [3.4 Remove the Debian Kernel](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye#Remove_the_Debian_Kernel) * [3.5 Recommended: Remove the os-prober Package](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye#Recommended:_Remove_the_os-prober_Package) * [4 Connect to the Proxmox VE web interface](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye#Connect_to_the_Proxmox_VE_web_interface) * [4.1 Create a Linux Bridge](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye#Create_a_Linux_Bridge) * [4.2 Upload Subscription Key](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye#Upload_Subscription_Key) * [5 Troubleshooting](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye#Troubleshooting) * [5.1 resolv.conf gets overwritten](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye#resolv.conf_gets_overwritten) * [5.2 ipcc\_send\_rec\[1\] failed](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye#ipcc_send_rec[1]_failed) Introduction ------------ The installation of a supported Proxmox VE server should be done via [bare-metal ISO installer](https://pve.proxmox.com/wiki/Installation) . In some cases it makes sense to install Proxmox VE on top of a running Debian Bullseye 64-bit, especially if you want a custom partition layout. For this How-To any official Bullseye installation medium should work. Install a standard Debian Bullseye (amd64) ------------------------------------------ Install a standard Debian Bullseye, for details consider the [Debian installation guide](https://www.debian.org/releases/stable/amd64/index.en.html) , and configure a static IP. It is recommended to only install the "standard system utilities" and "SSH server" package selection, as Proxmox VE brings its own packages for QEMU and LXC. A desktop environment is not necessary. ### Add an /etc/hosts entry for your IP address The hostname of your machine must be resolvable via /etc/hosts. This means that in /etc/hosts you need one of the following entries for your hostname: * 1 IPv4 or * 1 IPv6 or * 1 IPv4 and 1 IPv6 **Note**: This also means removing the address 127.0.1.1 that is present as default. For instance, if your IP address is 192.168.15.77, and your hostname prox4m1, then your /etc/hosts file could look like: 127.0.0.1 localhost 192.168.15.77 prox4m1.proxmox.com prox4m1 # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters You can test if your setup is ok using the hostname command: hostname --ip-address 192.168.15.77 # should return your IP address here Install Proxmox VE ------------------ ### Adapt your sources.list Add the Proxmox VE repository: echo "deb \[arch=amd64\] [http://download.proxmox.com/debian/pve](http://download.proxmox.com/debian/pve) bullseye pve-no-subscription" > /etc/apt/sources.list.d/pve-install-repo.list Add the Proxmox VE repository key as root (or use sudo): wget [https://enterprise.proxmox.com/debian/proxmox-release-bullseye.gpg](https://enterprise.proxmox.com/debian/proxmox-release-bullseye.gpg) -O /etc/apt/trusted.gpg.d/proxmox-release-bullseye.gpg # verify sha512sum /etc/apt/trusted.gpg.d/proxmox-release-bullseye.gpg 7fb03ec8a1675723d2853b84aa4fdb49a46a3bb72b9951361488bfd19b29aab0a789a4f8c7406e71a69aabbc727c936d3549731c4659ffa1a08f44db8fdcebfa /etc/apt/trusted.gpg.d/proxmox-release-bullseye.gpg Update your repository and system by running: apt update && apt full-upgrade ### Install the Proxmox VE Kernel First you need to install and boot the Proxmox VE kernel, as some packages depend on specific kernel compile flags to be set or feature extensions (e.g., for apparmor) to be available. apt install pve-kernel-5.15 systemctl reboot Note that while the `pve-kernel-5.15` is the default stable kernel for the Proxmox VE 7.x series, there's also a newer opt-in kernel available with `pve-kernel-6.2`, possibly helping to resolve some hardware related woes on modern systems. ### Install the Proxmox VE packages Install the Proxmox VE packages apt install proxmox-ve postfix open-iscsi Configure packages which require user input on installation according to your needs. If you have a mail server in your network, you should configure postfix as a **satellite system**. Your existing mail server will then be the _relay host_ which will route the emails sent by Proxmox VE to their final recipient. If you don't know what to enter here, choose **local only** and leave the _system name_ as is. ### Remove the Debian Kernel Proxmox VE ships its own kernel and keeping the Debian default kernel can lead to trouble on upgrades, for example, with Debian point releases. Therefore, you must remove the default Debian kernel: apt remove linux-image-amd64 'linux-image-5.10\*' Update and check grub2 config by running: update-grub ### Recommended: Remove the os-prober Package The `os-prober` package scans all the partitions of your host to create dual-boot GRUB entries. But the scanned partitions can also include those assigned to virtual machines, which one doesn't want to add as boot entry. If you didn't install Proxmox VE as dual boot beside another OS, you can safely remove the `os-prober` package: apt remove os-prober Connect to the Proxmox VE web interface --------------------------------------- Connect to the admin web interface (`[https://your-ip-address:8006](https://your-ip-address:8006/) `). If you have a fresh install and have not added any users yet, you should select PAM authentication realm and login with `root` user account. ### Create a Linux Bridge Once logged in, create a Linux Bridge called vmbr0, and add your first network interface to it. [![Adapt vmbr0 settings](https://pve.proxmox.com/mediawiki/images/8/84/Screen-vmbr0-setup-for-ext6.png)](https://pve.proxmox.com/wiki/File:Screen-vmbr0-setup-for-ext6.png "Adapt vmbr0 settings") ### Upload Subscription Key The Proxmox VE enterprise repository is set up automatically during the installation as it's the recommended repository for stable, enterprise usage. Access to that repository is one of the benefits of a Proxmox VE subscription, see [this forum thread for more info about why you should get one](https://forum.proxmox.com/threads/proxmox-ve-support-subscriptions-and-why-everybody-should-buy-one.9244/) . You should **upload your subscription key** now in the web interface, then you can remove the no-subscription repository added for installation. rm /etc/apt/sources.list.d/pve-install-repo.list Troubleshooting --------------- ### resolv.conf gets overwritten The PVE GUI expects to control DNS management and will no longer take its DNS settings from /etc/network/interfaces. Any package that auto-generates (overwrites) /etc/resolv.conf will cause DNS to fail, e.g. packages 'resolvconf' for IPv4 and 'rdnssd' for IPv6. ### ipcc\_send\_rec\[1\] failed If you see ipcc\_send\_rec\[1\] failed: Connection refused then you should review your /etc/hosts file according to the instructions above. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Install\_Proxmox\_VE\_on\_Debian\_11\_Bullseye&oldid=11640](https://pve.proxmox.com/mediawiki/index.php?title=Install_Proxmox_VE_on_Debian_11_Bullseye&oldid=11640) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Installation](https://pve.proxmox.com/wiki/Category:Installation "Category:Installation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Passthrough Physical Disk to Virtual Machine (VM) - Proxmox VE Passthrough Physical Disk to Virtual Machine (VM) ================================================= From Proxmox VE (Redirected from [Using a Raw Physical Hard Drive as Passthrough to QEMU/KVM Virtual Machine(VM) on Proxmox VE(PVE)](https://pve.proxmox.com/mediawiki/index.php?title=Using_a_Raw_Physical_Hard_Drive_as_Passthrough_to_QEMU/KVM_Virtual_Machine(VM)_on_Proxmox_VE(PVE)&redirect=no "Using a Raw Physical Hard Drive as Passthrough to QEMU/KVM Virtual Machine(VM) on Proxmox VE(PVE)") ) [Jump to navigation](https://pve.proxmox.com/wiki/Using_a_Raw_Physical_Hard_Drive_as_Passthrough_to_QEMU/KVM_Virtual_Machine(VM)_on_Proxmox_VE(PVE)#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Using_a_Raw_Physical_Hard_Drive_as_Passthrough_to_QEMU/KVM_Virtual_Machine(VM)_on_Proxmox_VE(PVE)#searchInput) By adding the raw physical device to the Virtual machine, you can test installers and other disk repair tools that work with disk controllers like `ddrescue`, Clonezilla or Ubuntu Rescue Remix. **NOTE**: This guide is meant for QEMU/KVM based Virtual Machines, **not** for Container. For the latter see [https://forum.proxmox.com/threads/container-with-physical-disk.42280/#post-203292](https://forum.proxmox.com/threads/container-with-physical-disk.42280/#post-203292) As the disk is attached to the physical and virtual host, this will also prevent Virtual Machine live migration. A second side effect is host system IO wait, when running ddrescue, other VM's running on the host can stutter. Contents -------- * [1 Attach Pass Through Disk](https://pve.proxmox.com/wiki/Using_a_Raw_Physical_Hard_Drive_as_Passthrough_to_QEMU/KVM_Virtual_Machine(VM)_on_Proxmox_VE(PVE)#Attach_Pass_Through_Disk) * [1.1 Identify Disk](https://pve.proxmox.com/wiki/Using_a_Raw_Physical_Hard_Drive_as_Passthrough_to_QEMU/KVM_Virtual_Machine(VM)_on_Proxmox_VE(PVE)#Identify_Disk) * [1.1.1 lshw](https://pve.proxmox.com/wiki/Using_a_Raw_Physical_Hard_Drive_as_Passthrough_to_QEMU/KVM_Virtual_Machine(VM)_on_Proxmox_VE(PVE)#lshw) * [1.1.2 List disk by-id with lsblk](https://pve.proxmox.com/wiki/Using_a_Raw_Physical_Hard_Drive_as_Passthrough_to_QEMU/KVM_Virtual_Machine(VM)_on_Proxmox_VE(PVE)#List_disk_by-id_with_lsblk) * [1.1.3 Short List](https://pve.proxmox.com/wiki/Using_a_Raw_Physical_Hard_Drive_as_Passthrough_to_QEMU/KVM_Virtual_Machine(VM)_on_Proxmox_VE(PVE)#Short_List) * [1.2 Update Configuration](https://pve.proxmox.com/wiki/Using_a_Raw_Physical_Hard_Drive_as_Passthrough_to_QEMU/KVM_Virtual_Machine(VM)_on_Proxmox_VE(PVE)#Update_Configuration) * [1.2.1 Hot-Plug/Add physical device as new virtual SCSI disk](https://pve.proxmox.com/wiki/Using_a_Raw_Physical_Hard_Drive_as_Passthrough_to_QEMU/KVM_Virtual_Machine(VM)_on_Proxmox_VE(PVE)#Hot-Plug/Add_physical_device_as_new_virtual_SCSI_disk) * [1.2.2 Hot-Unplug/Remove virtual disk](https://pve.proxmox.com/wiki/Using_a_Raw_Physical_Hard_Drive_as_Passthrough_to_QEMU/KVM_Virtual_Machine(VM)_on_Proxmox_VE(PVE)#Hot-Unplug/Remove_virtual_disk) * [1.3 Check Configuration File](https://pve.proxmox.com/wiki/Using_a_Raw_Physical_Hard_Drive_as_Passthrough_to_QEMU/KVM_Virtual_Machine(VM)_on_Proxmox_VE(PVE)#Check_Configuration_File) * [1.4 Stop and Restart KVM Virtual Machine](https://pve.proxmox.com/wiki/Using_a_Raw_Physical_Hard_Drive_as_Passthrough_to_QEMU/KVM_Virtual_Machine(VM)_on_Proxmox_VE(PVE)#Stop_and_Restart_KVM_Virtual_Machine) * [2 Tutorial](https://pve.proxmox.com/wiki/Using_a_Raw_Physical_Hard_Drive_as_Passthrough_to_QEMU/KVM_Virtual_Machine(VM)_on_Proxmox_VE(PVE)#Tutorial) * [3 Disk Recovery Tools](https://pve.proxmox.com/wiki/Using_a_Raw_Physical_Hard_Drive_as_Passthrough_to_QEMU/KVM_Virtual_Machine(VM)_on_Proxmox_VE(PVE)#Disk_Recovery_Tools) Attach Pass Through Disk ======================== Identify Disk ------------- Before adding a physical disk to host make note of vendor, serial so that you'll know which disk to share in /dev/disk/by-id/ ### lshw lshw is not installed by default on Proxmox VE (see `lsblk` for that below), you can install it by executing `apt install lshw` lshw -class disk -class storage ... \*-disk description: ATA Disk product: ST3000DM001-1CH1 vendor: Seagate physical id: 0.0.0 bus info: scsi@3:0.0.0 logical name: /dev/sda version: CC27 serial: Z1F41BLC size: 2794GiB (3TB) configuration: ansiversion=5 sectorsize=4096 ... Note that device names like `/dev/sdc` should never be used, as this can change between reboots. Use the stable `/dev/disk/by-id` paths instead. Check by listing all of that directory then look for the disk added by matching serial number from lshw and the physical disk: ls -l /dev/disk/by-id/ata-ST3000DM001-1CH166\_Z1F41BLC lrwxrwxrwx 1 root root 9 Jan 21 10:10 /dev/disk/by-id/ata-ST3000DM001-1CH166\_Z1F41BLC -> ../../sda or try ls -l /dev/disk/by-id | grep Z1F41BLC ### List disk by-id with lsblk The `lsblk` is pre-installed, you can print and map the serial and WWN identifiers of attached disks using the following two commands: lsblk -o +MODEL,SERIAL,WWN ls -l /dev/disk/by-id/ You can also use an extended one liner to get the path directly: lsblk |awk 'NR==1{print $0" DEVICE-ID(S)"}NR>1{dev=$1;printf $0" ";system("find /dev/disk/by-id -lname \\"\*"dev"\\" -printf \\" %p\\"");print "";}'|grep -v -E 'part|lvm' NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT DEVICE-ID(S) sda 8:0 0 7.3T 0 disk /dev/disk/by-id/wwn-0x5000c500c35cd719 /dev/disk/by-id/ata-ST8000DM004-2CX188\_ZCT1DNY1 sdb 8:16 1 29G 0 disk /dev/disk/by-id/usb-Generic\_STORAGE\_DEVICE-0:0 sdc 8:32 0 931.5G 0 disk /dev/disk/by-id/usb-JMicron\_Generic\_0123456789ABCDEF-0:0 sdd 8:48 0 1.8T 0 disk /dev/disk/by-id/wwn-0x5000c500661eeebd /dev/disk/by-id/ata-ST2000DX001-1CM164\_Z1E783H2 [make-lsblk-list-devices-by-id](https://unix.stackexchange.com/questions/387855/make-lsblk-list-devices-by-id) ### Short List find /dev/disk/by-id/ -type l|xargs -I{} ls -l {}|grep -v -E '\[0-9\]$' |sort -k11|cut -d' ' -f9,10,11,12 /dev/disk/by-id/ata-ST8000DM004-2CX188\_ZCT1DNY1 -> ../../sda /dev/disk/by-id/wwn-0x5000c500c35cd719 -> ../../sda /dev/disk/by-id/usb-Generic\_STORAGE\_DEVICE-0:0 -> ../../sdb /dev/disk/by-id/usb-JMicron\_Generic\_0123456789ABCDEF-0:0 -> ../../sdc /dev/disk/by-id/ata-ST2000DX001-1CM164\_Z1E783H2 -> ../../sdd /dev/disk/by-id/wwn-0x5000c500661eeebd -> ../../sdd Update Configuration -------------------- ### Hot-Plug/Add physical device as new virtual SCSI disk qm set 592 -scsi2 /dev/disk/by-id/ata-ST3000DM001-1CH166\_Z1F41BLC update VM 592: -scsi2 /dev/disk/by-id/ata-ST3000DM001-1CH166\_Z1F41BLC ### Hot-Unplug/Remove virtual disk qm unlink 592 --idlist scsi2 update VM 592: -delete scsi2 Check Configuration File ------------------------ grep Z1F41BLC /etc/pve/qemu-server/592.conf scsi2: /dev/disk/by-id/ata-ST3000DM001-1CH166\_Z1F41BLC,size=2930266584K Stop and Restart KVM Virtual Machine ------------------------------------ You may need to configure the guest operating system now that the disk is available. Tutorial ======== [Example with screenshots](https://dannyda.com/2020/08/26/how-to-passthrough-hdd-ssd-physical-disks-to-vm-on-proxmox-vepve/) Disk Recovery Tools =================== 1. Ubuntu Rescue Remix - [how to use Ubuntu Rescue Remix and Ddrescue](http://www.geekyprojects.com/storage/how-to-recover-data-even-when-hard-drive-is-damaged/) 2. ddrescue 3. gnu ddrescue 4. Clonezilla 5. TestDisk 6. PhotoRec 7. Recuva 8. Foremost 9. Parted Magic 10. SpinRite - Low Cost Commercial - Smartctl tutoral for Proxmox VE planned Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Passthrough\_Physical\_Disk\_to\_Virtual\_Machine\_(VM)&oldid=11538](https://pve.proxmox.com/mediawiki/index.php?title=Passthrough_Physical_Disk_to_Virtual_Machine_(VM)&oldid=11538) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Legacy: ZFS over iSCSI" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Legacy: ZFS over iSCSI" =========================================== ← [Legacy: ZFS over iSCSI](https://pve.proxmox.com/wiki/Legacy:_ZFS_over_iSCSI "Legacy: ZFS over iSCSI") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Legacy:_ZFS_over_iSCSI#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Legacy:_ZFS_over_iSCSI#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Legacy: ZFS over iSCSI](https://pve.proxmox.com/wiki/Legacy:_ZFS_over_iSCSI "Legacy: ZFS over iSCSI") **: Displaying 1 item. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Legacy:_ZFS_over_iSCSI&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Legacy:_ZFS_over_iSCSI&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Legacy:_ZFS_over_iSCSI&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Legacy:_ZFS_over_iSCSI&limit=500) ) * [Storage: ZFS over iSCSI](https://pve.proxmox.com/mediawiki/index.php?title=Storage:_ZFS_over_iSCSI&redirect=no "Storage: ZFS over iSCSI") (redirect page) ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Storage%3A+ZFS+over+iSCSI "Special:WhatLinksHere") ) * [Main Page](https://pve.proxmox.com/wiki/Main_Page "Main Page") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Main+Page "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Legacy:_ZFS_over_iSCSI&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Legacy:_ZFS_over_iSCSI&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Legacy:_ZFS_over_iSCSI&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Legacy:_ZFS_over_iSCSI&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Legacy:\_ZFS\_over\_iSCSI](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Legacy:_ZFS_over_iSCSI) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Storage Replication - Proxmox VE Storage Replication =================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Storage_Replication#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Storage_Replication#searchInput) The pvesr command-line tool manages the Proxmox VE storage replication framework. Storage replication brings redundancy for guests using local storage and reduces migration time. It replicates guest volumes to another node so that all data is available without using shared storage. Replication uses snapshots to minimize traffic sent over the network. Therefore, new data is sent only incrementally after the initial full sync. In the case of a node failure, your guest data is still available on the replicated node. The replication is done automatically in configurable intervals. The minimum replication interval is one minute, and the maximal interval once a week. The format used to specify those intervals is a subset of systemd calendar events, see [Schedule Format](https://pve.proxmox.com/wiki/Storage_Replication#pvesr_schedule_time_format) section: It is possible to replicate a guest to multiple target nodes, but not twice to the same target node. Each replications bandwidth can be limited, to avoid overloading a storage or server. Only changes since the last replication (so-called deltas) need to be transferred if the guest is migrated to a node to which it already is replicated. This reduces the time needed significantly. The replication direction automatically switches if you migrate a guest to the replication target node. For example: VM100 is currently on nodeA and gets replicated to nodeB. You migrate it to nodeB, so now it gets automatically replicated back from nodeB to nodeA. If you migrate to a node where the guest is not replicated, the whole disk data must send over. After the migration, the replication job continues to replicate this guest to the configured nodes. | | | | --- | --- | | ![Important]() | High-Availability is allowed in combination with storage replication, but there may be some data loss between the last synced time and the time a node failed. | Supported Storage Types ----------------------- | | | | | | --- | --- | --- | --- |Table 1. Storage Types | Description | Plugin type | Snapshots | Stable | | --- | --- | --- | --- | | ZFS (local) | zfspool | yes | yes | Schedule Format --------------- Replication uses [calendar events](https://pve.proxmox.com/wiki/Calendar_Events#chapter_calendar_events) for configuring the schedule. Error Handling -------------- If a replication job encounters problems, it is placed in an error state. In this state, the configured replication intervals get suspended temporarily. The failed replication is repeatedly tried again in a 30 minute interval. Once this succeeds, the original schedule gets activated again. ### Possible issues Some of the most common issues are in the following list. Depending on your setup there may be another cause. * Network is not working. * No free space left on the replication target storage. * Storage with the same storage ID is not available on the target node. | | | | --- | --- | | ![Note]() | You can always use the replication log to find out what is causing the problem. | ### Migrating a guest in case of Error In the case of a grave error, a virtual guest may get stuck on a failed node. You then need to move it manually to a working node again. ### Example Let’s assume that you have two guests (VM 100 and CT 200) running on node A and replicate to node B. Node A failed and can not get back online. Now you have to migrate the guest to Node B manually. * connect to node B over ssh or open its shell via the web UI * check if that the cluster is quorate \# pvecm status * If you have no quorum, we strongly advise to fix this first and make the node operable again. Only if this is not possible at the moment, you may use the following command to enforce quorum on the current node: \# pvecm expected 1 | | | | --- | --- | | ![Warning]() | Avoid changes which affect the cluster if expected votes are set (for example adding/removing nodes, storages, virtual guests) at all costs. Only use it to get vital guests up and running again or to resolve the quorum issue itself. | * move both guest configuration files form the origin node A to node B: \# mv /etc/pve/nodes/A/qemu-server/100.conf /etc/pve/nodes/B/qemu-server/100.conf # mv /etc/pve/nodes/A/lxc/200.conf /etc/pve/nodes/B/lxc/200.conf * Now you can start the guests again: \# qm start 100 # pct start 200 Remember to replace the VMIDs and node names with your respective values. Managing Jobs ------------- [![screenshot/gui-qemu-add-replication-job.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-qemu-add-replication-job.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-qemu-add-replication-job.png) You can use the web GUI to create, modify, and remove replication jobs easily. Additionally, the command-line interface (CLI) tool pvesr can be used to do this. You can find the replication panel on all levels (datacenter, node, virtual guest) in the web GUI. They differ in which jobs get shown: all, node- or guest-specific jobs. When adding a new job, you need to specify the guest if not already selected as well as the target node. The replication [schedule](https://pve.proxmox.com/wiki/Storage_Replication#pvesr_schedule_time_format) can be set if the default of all 15 minutes is not desired. You may impose a rate-limit on a replication job. The rate limit can help to keep the load on the storage acceptable. A replication job is identified by a cluster-wide unique ID. This ID is composed of the VMID in addition to a job number. This ID must only be specified manually if the CLI tool is used. Network ------- By default, replication traffic will go through the same network as the guest migration traffic. If the migration network is not set, this will in turn default to the management network. To use a different network for the replication traffic, configure the Replication Network in the web interface under Datacenter -> Options -> Replication Settings or set the replication property in the datacenter.cfg file: \# use dedicated replication network replication: secure,network=10.1.2.0/24 Command-line Interface Examples ------------------------------- Create a replication job which runs every 5 minutes with a limited bandwidth of 10 Mbps (megabytes per second) for the guest with ID 100. \# pvesr create-local-job 100-0 pve1 --schedule "\*/5" --rate 10 Disable an active job with ID 100-0. \# pvesr disable 100-0 Enable a deactivated job with ID 100-0. \# pvesr enable 100-0 Change the schedule interval of the job with ID 100-0 to once per hour. \# pvesr update 100-0 --schedule '\*/00' Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Storage\_Replication&oldid=12417](https://pve.proxmox.com/mediawiki/index.php?title=Storage_Replication&oldid=12417) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Reference Documentation](https://pve.proxmox.com/wiki/Category:Reference_Documentation "Category:Reference Documentation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Linux Container - Proxmox VE Linux Container =============== From Proxmox VE (Redirected from [LXC Bind Mounts](https://pve.proxmox.com/mediawiki/index.php?title=LXC_Bind_Mounts&redirect=no "LXC Bind Mounts") ) [Jump to navigation](https://pve.proxmox.com/wiki/LXC_Bind_Mounts#mw-head) [Jump to search](https://pve.proxmox.com/wiki/LXC_Bind_Mounts#searchInput) Containers are a lightweight alternative to fully virtualized machines (VMs). They use the kernel of the host system that they run on, instead of emulating a full operating system (OS). This means that containers can access resources on the host system directly. The runtime costs for containers is low, usually negligible. However, there are some drawbacks that need be considered: * Only Linux distributions can be run in Proxmox Containers. It is not possible to run other operating systems like, for example, FreeBSD or Microsoft Windows inside a container. * For security reasons, access to host resources needs to be restricted. Therefore, containers run in their own separate namespaces. Additionally some syscalls (user space requests to the Linux kernel) are not allowed within containers. Proxmox VE uses [Linux Containers (LXC)](https://linuxcontainers.org/lxc/introduction/) as its underlying container technology. The “Proxmox Container Toolkit” (pct) simplifies the usage and management of LXC, by providing an interface that abstracts complex tasks. Containers are tightly integrated with Proxmox VE. This means that they are aware of the cluster setup, and they can use the same network and storage resources as virtual machines. You can also use the Proxmox VE firewall, or manage containers using the HA framework. Our primary goal has traditionally been to offer an environment that provides the benefits of using a VM, but without the additional overhead. This means that Proxmox Containers have been primarily categorized as “System Containers”. With the introduction of OCI (**O**pen **C**ontainer **I**nitiative) image support, Proxmox VE now also integrates “Application Containers” as a technology preview. When creating a container from an OCI image, the image is automatically converted to the LXC stack that Proxmox VE uses. This approach allows users to benefit from a wide ecosystem of pre-packaged applications while retaining the robust management features of Proxmox VE. While running lightweight “Application Containers” directly offers significant advantages over a full VM, for use cases demanding maximum isolation and the ability to live-migrate, nesting containers inside a Proxmox QEMU VM remains a recommended practice. Technology Overview ------------------- * LXC ([https://linuxcontainers.org/](https://linuxcontainers.org/) ) * Integrated into Proxmox VE graphical web user interface (GUI) * Easy to use command-line tool pct * Access via Proxmox VE REST API * _lxcfs_ to provide containerized /proc file system * Control groups (_cgroups_) for resource isolation and limitation * _AppArmor_ and _seccomp_ to improve security * Modern Linux kernels * Image based deployment ([templates](https://pve.proxmox.com/wiki/Linux_Container#pct_supported_distributions) ) * Uses Proxmox VE [storage library](https://pve.proxmox.com/wiki/Storage#chapter_storage) * Container setup from host (network, DNS, storage, etc.) Supported Distributions ----------------------- List of officially supported distributions can be found below. Templates for the following distributions are available through our repositories. You can use [pveam](https://pve.proxmox.com/wiki/Linux_Container#pct_container_images) tool or the Graphical User Interface to download them. ### Alpine Linux Alpine Linux is a security-oriented, lightweight Linux distribution based on musl libc and busybox. — [https://alpinelinux.org](https://alpinelinux.org/) For currently supported releases see: [https://alpinelinux.org/releases/](https://alpinelinux.org/releases/) ### Arch Linux Arch Linux, a lightweight and flexible Linux® distribution that tries to Keep It Simple. — [https://archlinux.org/](https://archlinux.org/) Arch Linux is using a rolling-release model, see its wiki for more details: [https://wiki.archlinux.org/title/Arch\_Linux](https://wiki.archlinux.org/title/Arch_Linux) ### CentOS, Almalinux, Rocky Linux #### CentOS / CentOS Stream The CentOS Linux distribution is a stable, predictable, manageable and reproducible platform derived from the sources of Red Hat Enterprise Linux (RHEL) — [https://centos.org](https://centos.org/) For currently supported releases see: [https://en.wikipedia.org/wiki/CentOS#End-of-support\_schedule](https://en.wikipedia.org/wiki/CentOS#End-of-support_schedule) #### Almalinux An Open Source, community owned and governed, forever-free enterprise Linux distribution, focused on long-term stability, providing a robust production-grade platform. AlmaLinux OS is 1:1 binary compatible with RHEL® and pre-Stream CentOS. — [https://almalinux.org](https://almalinux.org/) For currently supported releases see: [https://en.wikipedia.org/wiki/AlmaLinux#Releases](https://en.wikipedia.org/wiki/AlmaLinux#Releases) #### Rocky Linux Rocky Linux is a community enterprise operating system designed to be 100% bug-for-bug compatible with America’s top enterprise Linux distribution now that its downstream partner has shifted direction. — [https://rockylinux.org](https://rockylinux.org/) For currently supported releases see: [https://en.wikipedia.org/wiki/Rocky\_Linux#Releases](https://en.wikipedia.org/wiki/Rocky_Linux#Releases) ### Debian Debian is a free operating system, developed and maintained by the Debian project. A free Linux distribution with thousands of applications to meet our users' needs. — [https://www.debian.org/intro/index#software](https://www.debian.org/intro/index#software) For currently supported releases see: [https://www.debian.org/releases/stable/releasenotes](https://www.debian.org/releases/stable/releasenotes) ### Devuan Devuan GNU+Linux is a fork of Debian without systemd that allows users to reclaim control over their system by avoiding unnecessary entanglements and ensuring Init Freedom. — [https://www.devuan.org](https://www.devuan.org/) For currently supported releases see: [https://www.devuan.org/os/releases](https://www.devuan.org/os/releases) ### Fedora Fedora creates an innovative, free, and open source platform for hardware, clouds, and containers that enables software developers and community members to build tailored solutions for their users. — [https://getfedora.org](https://getfedora.org/) For currently supported releases see: [https://fedoraproject.org/wiki/Releases](https://fedoraproject.org/wiki/Releases) ### Gentoo a highly flexible, source-based Linux distribution. — [https://www.gentoo.org](https://www.gentoo.org/) Gentoo is using a rolling-release model. ### OpenSUSE The makers' choice for sysadmins, developers and desktop users. — [https://www.opensuse.org](https://www.opensuse.org/) For currently supported releases see: [https://get.opensuse.org/leap/](https://get.opensuse.org/leap/) ### Ubuntu Ubuntu is the modern, open source operating system on Linux for the enterprise server, desktop, cloud, and IoT. — [https://ubuntu.com/](https://ubuntu.com/) For currently supported releases see: [https://wiki.ubuntu.com/Releases](https://wiki.ubuntu.com/Releases) Container Images ---------------- Container images, sometimes also referred to as “templates” or “appliances”, are tar archives which contain everything to run a container. Proxmox VE can utilize two main types of images: **System Container Templates** for creating full virtual environments, and **Application Container Images** based on the OCI standard for running specific applications. ### System Container Templates Proxmox VE itself provides a variety of basic templates for the [most common Linux distributions](https://pve.proxmox.com/wiki/Linux_Container#pct_supported_distributions) . They can be downloaded using the GUI or the pveam (short for Proxmox VE Appliance Manager) command-line utility. Additionally, [TurnKey Linux](https://www.turnkeylinux.org/) container templates are also available to download. The list of available templates is updated daily through the _pve-daily-update_ timer. You can also trigger an update manually by executing: \# pveam update To view the list of available images run: \# pveam available You can restrict this large list by specifying the section you are interested in, for example basic system images: List available system images \# pveam available --section system system alpine-3.12-default\_20200823\_amd64.tar.xz system alpine-3.13-default\_20210419\_amd64.tar.xz system alpine-3.14-default\_20210623\_amd64.tar.xz system archlinux-base\_20210420-1\_amd64.tar.gz system centos-7-default\_20190926\_amd64.tar.xz system centos-8-default\_20201210\_amd64.tar.xz system debian-9.0-standard\_9.7-1\_amd64.tar.gz system debian-10-standard\_10.7-1\_amd64.tar.gz system devuan-3.0-standard\_3.0\_amd64.tar.gz system fedora-33-default\_20201115\_amd64.tar.xz system fedora-34-default\_20210427\_amd64.tar.xz system gentoo-current-default\_20200310\_amd64.tar.xz system opensuse-15.2-default\_20200824\_amd64.tar.xz system ubuntu-16.04-standard\_16.04.5-1\_amd64.tar.gz system ubuntu-18.04-standard\_18.04.1-1\_amd64.tar.gz system ubuntu-20.04-standard\_20.04-1\_amd64.tar.gz system ubuntu-20.10-standard\_20.10-1\_amd64.tar.gz system ubuntu-21.04-standard\_21.04-1\_amd64.tar.gz Before you can use such a template, you need to download them into one of your storages. If you’re unsure to which one, you can simply use the local named storage for that purpose. For clustered installations, it is preferred to use a shared storage so that all nodes can access those images. \# pveam download local debian-10.0-standard\_10.0-1\_amd64.tar.gz You are now ready to create containers using that image, and you can list all downloaded images on storage local with: \# pveam list local local:vztmpl/debian-10.0-standard\_10.0-1\_amd64.tar.gz 219.95MB | | | | --- | --- | | ![Tip]() | You can also use the Proxmox VE web interface GUI to download, list and delete container templates. | pct uses them to create a new container, for example: \# pct create 999 local:vztmpl/debian-10.0-standard\_10.0-1\_amd64.tar.gz The above command shows you the full Proxmox VE volume identifiers. They include the storage name, and most other Proxmox VE commands can use them. For example you can delete that image later with: \# pveam remove local:vztmpl/debian-10.0-standard\_10.0-1\_amd64.tar.gz ### Open Container Initiative (OCI) Images Proxmox VE can also use OCI images to create containers, both system containers but also application containers. Note that running application containers in Proxmox VE is currently considered a technology preview. A container created from an OCI image still uses the existing LXC framework. ### Obtaining OCI Images In the web interface an OCI image can be uploaded manually or pulled from a registry using the **Pull from OCI registry** button on the container template view of a storage. Once the template is on a storage, you can create the container with pct create or use the wizard in the web interface. Container Settings ------------------ ### General Settings [![screenshot/gui-create-ct-general.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-create-ct-general.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-create-ct-general.png) General settings of a container include * the **Node** : the physical server on which the container will run * the **CT ID**: a unique number in this Proxmox VE installation used to identify your container * **Hostname**: the hostname of the container * **Resource Pool**: a logical group of containers and VMs * **Password**: the root password of the container * **SSH Public Key**: a public key for connecting to the root account over SSH * **Unprivileged container**: this option allows to choose at creation time if you want to create a privileged or unprivileged container. * **Nesting**: expose procfs and sysfs to allow nested containers. Note that systemd also uses this to isolate services. #### Unprivileged Containers Unprivileged containers use a new kernel feature called user namespaces. The root UID 0 inside the container is mapped to an unprivileged user outside the container. This means that most security issues (container escape, resource abuse, etc.) in these containers will affect a random unprivileged user, and would be a generic kernel security bug rather than an LXC issue. The LXC team thinks unprivileged containers are safe by design. This is the default option when creating a new container. | | | | --- | --- | | ![Note]() | If the container uses systemd as an init system, please be aware the systemd version running inside the container should be equal to or greater than 220. | #### Privileged Containers Security in containers is achieved by using mandatory access control _AppArmor_ restrictions, _seccomp_ filters and Linux kernel namespaces. The LXC team considers this kind of container as unsafe, and they will not consider new container escape exploits to be security issues worthy of a CVE and quick fix. That’s why privileged containers should only be used in trusted environments. ### CPU [![screenshot/gui-create-ct-cpu.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-create-ct-cpu.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-create-ct-cpu.png) You can restrict the number of visible CPUs inside the container using the cores option. This is implemented using the Linux _cpuset_ cgroup (**c**ontrol **group**). A special task inside pvestatd tries to distribute running containers among available CPUs periodically. To view the assigned CPUs run the following command: \# pct cpusets --------------------- 102: 6 7 105: 2 3 4 5 108: 0 1 --------------------- Containers use the host kernel directly. All tasks inside a container are handled by the host CPU scheduler. Proxmox VE uses the Linux _CFS_ (**C**ompletely **F**air **S**cheduler) scheduler by default, which has additional bandwidth control options. | | | | --- | --- | | cpulimit: | You can use this option to further limit assigned CPU time. Please note that this is a floating point number, so it is perfectly valid to assign two cores to a container, but restrict overall CPU consumption to half a core.

cores: 2
cpulimit: 0.5 | | cpuunits: | This is a relative weight passed to the kernel scheduler. The larger the number is, the more CPU time this container gets. Number is relative to the weights of all the other running containers. The default is 100 (or 1024 if the host uses legacy cgroup v1). You can use this setting to prioritize some containers. | ### Memory [![screenshot/gui-create-ct-memory.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-create-ct-memory.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-create-ct-memory.png) Container memory is controlled using the cgroup memory controller. | | | | --- | --- | | memory: | Limit overall memory usage. This corresponds to the memory.limit\_in\_bytes cgroup setting. | | swap: | Allows the container to use additional swap memory from the host swap space. This corresponds to the memory.memsw.limit\_in\_bytes cgroup setting, which is set to the sum of both value (memory + swap). | ### Mount Points [![screenshot/gui-create-ct-root-disk.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-create-ct-root-disk.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-create-ct-root-disk.png) The root mount point is configured with the rootfs property. You can configure up to 256 additional mount points. The corresponding options are called mp0 to mp255. They can contain the following settings: rootfs: \[volume=\] \[,acl=<1|0>\] \[,mountoptions=\] \[,quota=<1|0>\] \[,replicate=<1|0>\] \[,ro=<1|0>\] \[,shared=<1|0>\] \[,size=\] Use volume as container root. See below for a detailed description of all options. mp\[n\]: \[volume=\] ,mp= \[,acl=<1|0>\] \[,backup=<1|0>\] \[,mountoptions=\] \[,quota=<1|0>\] \[,replicate=<1|0>\] \[,ro=<1|0>\] \[,shared=<1|0>\] \[,size=\] Use volume as container mount point. Use the special syntax STORAGE\_ID:SIZE\_IN\_GiB to allocate a new volume. acl\= Explicitly enable or disable ACL support. backup\= Whether to include the mount point in backups (only used for volume mount points). mountoptions\= Extra mount options for rootfs/mps. mp\= Path to the mount point as seen from inside the container. | | | | --- | --- | | ![Note]() | Must not contain any symlinks for security reasons. | quota\= Enable user quotas inside the container (not supported with zfs subvolumes) replicate\= (_default =_ 1) Will include this volume to a storage replica job. ro\= Read-only mount point shared\= (_default =_ 0) Mark this non-volume mount point as available on all nodes. | | | | --- | --- | | ![Warning]() | This option does not share the mount point automatically, it assumes it is shared already! | size\= Volume size (read only value). volume\= Volume, device or directory to mount into the container. Currently there are three types of mount points: storage backed mount points, bind mounts, and device mounts. Typical container rootfs configuration rootfs: thin1:base-100-disk-1,size=8G #### Storage Backed Mount Points Storage backed mount points are managed by the Proxmox VE storage subsystem and come in three different flavors: * Image based: these are raw images containing a single ext4 formatted file system. * ZFS subvolumes: these are technically bind mounts, but with managed storage, and thus allow resizing and snapshotting. * Directories: passing size=0 triggers a special case where instead of a raw image a directory is created. | | | | --- | --- | | ![Note]() | The special option syntax STORAGE\_ID:SIZE\_IN\_GB for storage backed mount point volumes will automatically allocate a volume of the specified size on the specified storage. For example, calling | pct set 100 -mp0 thin1:10,mp=/path/in/container will allocate a 10GB volume on the storage thin1 and replace the volume ID place holder 10 with the allocated volume ID, and setup the moutpoint in the container at /path/in/container #### Bind Mount Points Bind mounts allow you to access arbitrary directories from your Proxmox VE host inside a container. Some potential use cases are: * Accessing your home directory in the guest * Accessing an USB device directory in the guest * Accessing an NFS mount from the host in the guest Bind mounts are considered to not be managed by the storage subsystem, so you cannot make snapshots or deal with quotas from inside the container. With unprivileged containers you might run into permission problems caused by the user mapping and cannot use ACLs. | | | | --- | --- | | ![Note]() | The contents of bind mount points are not backed up when using vzdump. | | | | | --- | --- | | ![Warning]() | For security reasons, bind mounts should only be established using source directories especially reserved for this purpose, e.g., a directory hierarchy under /mnt/bindmounts. Never bind mount system directories like /, /var or /etc into a container - this poses a great security risk. | | | | | --- | --- | | ![Note]() | The bind mount source path must not contain any symlinks. | For example, to make the directory /mnt/bindmounts/shared accessible in the container with ID 100 under the path /shared, add a configuration line such as: mp0: /mnt/bindmounts/shared,mp=/shared into /etc/pve/lxc/100.conf. Or alternatively use the pct tool: pct set 100 -mp0 /mnt/bindmounts/shared,mp=/shared to achieve the same result. #### Device Mount Points Device mount points allow to mount block devices of the host directly into the container. Similar to bind mounts, device mounts are not managed by Proxmox VE’s storage subsystem, but the quota and acl options will be honored. | | | | --- | --- | | ![Note]() | Device mount points should only be used under special circumstances. In most cases a storage backed mount point offers the same performance and a lot more features. | | | | | --- | --- | | ![Note]() | The contents of device mount points are not backed up when using vzdump. | ### Network [![screenshot/gui-create-ct-network.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-create-ct-network.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-create-ct-network.png) You can configure up to 10 network interfaces for a single container. The corresponding options are called net0 to net9, and they can contain the following setting: net\[n\]: name= \[,bridge=\] \[,firewall=<1|0>\] \[,gw=\] \[,gw6=\] \[,host-managed=<1|0>\] \[,hwaddr=\] \[,ip=<(IPv4/CIDR|dhcp|manual)>\] \[,ip6=<(IPv6/CIDR|auto|dhcp|manual)>\] \[,link\_down=<1|0>\] \[,mtu=\] \[,rate=\] \[,tag=\] \[,trunks=\] \[,type=\] Specifies network interfaces for the container. bridge\= Bridge to attach the network device to. firewall\= Controls whether this interface’s firewall rules should be used. gw\= Default gateway for IPv4 traffic. gw6\= Default gateway for IPv6 traffic. host-managed\= Whether this interface’s IP configuration should be managed by the host. hwaddr\= A common MAC address with the I/G (Individual/Group) bit not set. ip\=<(IPv4/CIDR|dhcp|manual)> IPv4 address in CIDR format. ip6\=<(IPv6/CIDR|auto|dhcp|manual)> IPv6 address in CIDR format. link\_down\= Whether this interface should be disconnected (like pulling the plug). mtu\= (64 - 65535) Maximum transfer unit of the interface. (lxc.network.mtu) name\= Name of the network device as seen from inside the container. (lxc.network.name) rate\= Apply rate limiting to the interface tag\= (1 - 4094) VLAN tag for this interface. trunks\= VLAN ids to pass through the interface type\= Network interface type. ### Automatic Start and Shutdown of Containers To automatically start a container when the host system boots, select the option _Start at boot_ in the _Options_ panel of the container in the web interface or run the following command: \# pct set CTID -onboot 1 [![screenshot/gui-qemu-edit-start-order.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-qemu-edit-start-order.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-qemu-edit-start-order.png) ##### Start and Shutdown Order If you want to fine tune the boot order of your containers, you can use the following parameters: * **Start/Shutdown order**: Defines the start order priority. For example, set it to 1 if you want the CT to be the first to be started. (We use the reverse startup order for shutdown, so a container with a start order of 1 would be the last to be shut down) * **Startup delay**: Defines the interval between this container start and subsequent containers starts. For example, set it to 240 if you want to wait 240 seconds before starting other containers. * **Shutdown timeout**: Defines the duration in seconds Proxmox VE should wait for the container to be offline after issuing a shutdown command. By default this value is set to 60, which means that Proxmox VE will issue a shutdown request, wait 60s for the machine to be offline, and if after 60s the machine is still online will notify that the shutdown action failed. Please note that containers without a Start/Shutdown order parameter will always start after those where the parameter is set, and this parameter only makes sense between the machines running locally on a host, and not cluster-wide. If you require a delay between the host boot and the booting of the first container, see the section on [Proxmox VE Node Management](https://pve.proxmox.com/wiki/Proxmox_Node_Management#first_guest_boot_delay) . ### Hookscripts You can add a hook script to CTs with the config property hookscript. \# pct set 100 -hookscript local:snippets/hookscript.pl It will be called during various phases of the guests lifetime. For an example and documentation see the example script under /usr/share/pve-docs/examples/guest-example-hookscript.pl. Security Considerations ----------------------- Containers use the kernel of the host system. This exposes an attack surface for malicious users. In general, full virtual machines provide better isolation. This should be considered if containers are provided to unknown or untrusted people. To reduce the attack surface, LXC uses many security features like AppArmor, CGroups and kernel namespaces. ### AppArmor AppArmor profiles are used to restrict access to possibly dangerous actions. Some system calls, i.e. mount, are prohibited from execution. To trace AppArmor activity, use: \# dmesg | grep apparmor Although it is not recommended, AppArmor can be disabled for a container. This brings security risks with it. Some syscalls can lead to privilege escalation when executed within a container if the system is misconfigured or if a LXC or Linux Kernel vulnerability exists. To disable AppArmor for a container, add the following line to the container configuration file located at /etc/pve/lxc/CTID.conf: lxc.apparmor.profile = unconfined | | | | --- | --- | | ![Warning]() | Please note that this is not recommended for production use. | ### Control Groups (_cgroup_) _cgroup_ is a kernel mechanism used to hierarchically organize processes and distribute system resources. The main resources controlled via _cgroups_ are CPU time, memory and swap limits, and access to device nodes. _cgroups_ are also used to "freeze" a container before taking snapshots. The current version of _cgroups_ is [_cgroupv2_](https://www.kernel.org/doc/html/v6.14/admin-guide/cgroup-v2.html) . The [v1 version](https://www.kernel.org/doc/html/v6.14/admin-guide/cgroup-v1/index.html) of the cgroup subsystem was deprecated with the release of Proxmox VE 7.0 and removed entirely with Proxmox VE 9.0. Before Proxmox VE 7.0, a "hybrid" mode was the default. #### CGroup Version Compatibility The main difference between pure _cgroupv2_ and the old hybrid environments regarding Proxmox VE is that with _cgroupv2_ memory and swap are now controlled independently. The memory and swap settings for containers can map directly to these values, whereas previously only the memory limit and the limit of the **sum** of memory and swap could be limited. Another important difference is that the _devices_ controller is configured in a completely different way. Because of this, file system quotas are currently not supported in a pure _cgroupv2_ environment. _cgroupv2_ support by the container’s OS is needed to run in a pure _cgroupv2_ environment. Containers running _systemd_ version 231 or newer support _cgroupv2_ \[this includes all newest major versions of container templates shipped by Proxmox VE\] , as do containers not using _systemd_ as init system \[for example Alpine Linux\] . | | | | --- | --- | | ![Note]() | CentOS 7 and Ubuntu 16.10 are two prominent Linux distributions releases, which have a _systemd_ version that is too old to run in a _cgroupv2_ environment, you can either

* Upgrade the whole distribution to a newer release. For the examples above, that could be Ubuntu 18.04 or 20.04, and CentOS 8 (or RHEL/CentOS derivatives like AlmaLinux or Rocky Linux). This has the benefit to get the newest bug and security fixes, often also new features, and moving the EOL date in the future.

* Upgrade the Containers systemd version. If the distribution provides a backports repository this can be an easy and quick stop-gap measurement.

* Move the container, or its services, to a Virtual Machine. Virtual Machines have a much less interaction with the host, that’s why one can install decades old OS versions just fine there. | #### Changing CGroup Version Before Proxmox VE 9.0, you could switch back to the previous version with the following kernel command-line parameter: systemd.unified\_cgroup\_hierarchy=0 See [this section](https://pve.proxmox.com/wiki/Host_Bootloader#sysboot_edit_kernel_cmdline) on editing the kernel boot command line on where to add the parameter. Guest Operating System Configuration ------------------------------------ Proxmox VE tries to detect the Linux distribution in the container, and modifies some files. Here is a short list of things done at container startup: set /etc/hostname to set the container name modify /etc/hosts to allow lookup of the local hostname network setup pass the complete network setup to the container configure DNS pass information about DNS servers adapt the init system for example, fix the number of spawned getty processes set the root password when creating a new container rewrite ssh\_host\_keys so that each container has unique keys randomize crontab so that cron does not start at the same time on all containers Changes made by Proxmox VE are enclosed by comment markers: \# --- BEGIN PVE --- # --- END PVE --- Those markers will be inserted at a reasonable location in the file. If such a section already exists, it will be updated in place and will not be moved. Modification of a file can be prevented by adding a .pve-ignore. file for it. For instance, if the file /etc/.pve-ignore.hosts exists then the /etc/hosts file will not be touched. This can be a simple empty file created via: \# touch /etc/.pve-ignore.hosts Most modifications are OS dependent, so they differ between different distributions and versions. You can completely disable modifications by manually setting the ostype to unmanaged. OS type detection is done by testing for certain files inside the container. Proxmox VE first checks the /etc/os-release file \[/etc/os-release replaces the multitude of per-distribution release files [https://manpages.debian.org/stable/systemd/os-release.5.en.html](https://manpages.debian.org/stable/systemd/os-release.5.en.html)\ \] . If that file is not present, or it does not contain a clearly recognizable distribution identifier the following distribution specific release files are checked. Ubuntu inspect /etc/lsb-release (DISTRIB\_ID=Ubuntu) Debian test /etc/debian\_version Fedora test /etc/fedora-release RedHat or CentOS test /etc/redhat-release ArchLinux test /etc/arch-release Alpine test /etc/alpine-release Gentoo test /etc/gentoo-release | | | | --- | --- | | ![Note]() | Container start fails if the configured ostype differs from the auto detected type. | Container Storage ----------------- The Proxmox VE LXC container storage model is more flexible than traditional container storage models. A container can have multiple mount points. This makes it possible to use the best suited storage for each application. For example the root file system of the container can be on slow and cheap storage while the database can be on fast and distributed storage via a second mount point. See section [Mount Points](https://pve.proxmox.com/wiki/Linux_Container#pct_mount_points) for further details. Any storage type supported by the Proxmox VE storage library can be used. This means that containers can be stored on local (for example lvm, zfs or directory), shared external (like iSCSI, NFS) or even distributed storage systems like Ceph. Advanced storage features like snapshots or clones can be used if the underlying storage supports them. The vzdump backup tool can use snapshots to provide consistent container backups. Furthermore, local devices or local directories can be mounted directly using _bind mounts_. This gives access to local resources inside a container with practically zero overhead. Bind mounts can be used as an easy way to share data between containers. ### FUSE Mounts | | | | --- | --- | | ![Warning]() | Because of existing issues in the Linux kernel’s freezer subsystem the usage of FUSE mounts inside a container is strongly advised against, as containers need to be frozen for suspend or snapshot mode backups. | If FUSE mounts cannot be replaced by other mounting mechanisms or storage technologies, it is possible to establish the FUSE mount on the Proxmox host and use a bind mount point to make it accessible inside the container. ### Using Quotas Inside Containers Quotas allow to set limits inside a container for the amount of disk space that each user can use. | | | | --- | --- | | ![Note]() | This currently requires the use of legacy _cgroups_. | | | | | --- | --- | | ![Note]() | This only works on ext4 image based storage types and currently only works with privileged containers. | Activating the quota option causes the following mount options to be used for a mount point: usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0 This allows quotas to be used like on any other system. You can initialize the /aquota.user and /aquota.group files by running: \# quotacheck -cmug / # quotaon / Then edit the quotas using the edquota command. Refer to the documentation of the distribution running inside the container for details. | | | | --- | --- | | ![Note]() | You need to run the above commands for every mount point by passing the mount point’s path instead of just /. | ### Using ACLs Inside Containers The standard Posix **A**ccess **C**ontrol **L**ists are also available inside containers. ACLs allow you to set more detailed file ownership than the traditional user/group/others model. ### Backup of Container mount points To include a mount point in backups, enable the backup option for it in the container configuration. For an existing mount point mp0 mp0: guests:subvol-100-disk-1,mp=/root/files,size=8G add backup=1 to enable it. mp0: guests:subvol-100-disk-1,mp=/root/files,size=8G,backup=1 | | | | --- | --- | | ![Note]() | When creating a new mount point in the GUI, this option is enabled by default. | To disable backups for a mount point, add backup=0 in the way described above, or uncheck the **Backup** checkbox on the GUI. ### Replication of Containers mount points By default, additional mount points are replicated when the Root Disk is replicated. If you want the Proxmox VE storage replication mechanism to skip a mount point, you can set the **Skip replication** option for that mount point. As of Proxmox VE 5.0, replication requires a storage of type zfspool. Adding a mount point to a different type of storage when the container has replication configured requires to have **Skip replication** enabled for that mount point. Backup and Restore ------------------ ### Container Backup It is possible to use the vzdump tool for container backup. Please refer to the vzdump manual page for details. ### Restoring Container Backups Restoring container backups made with vzdump is possible using the pct restore command. By default, pct restore will attempt to restore as much of the backed up container configuration as possible. It is possible to override the backed up configuration by manually setting container options on the command line (see the pct manual page for details). | | | | --- | --- | | ![Note]() | pvesm extractconfig can be used to view the backed up configuration contained in a vzdump archive. | There are two basic restore modes, only differing by their handling of mount points: #### “Simple” Restore Mode If neither the rootfs parameter nor any of the optional mpX parameters are explicitly set, the mount point configuration from the backed up configuration file is restored using the following steps: 1. Extract mount points and their options from backup 2. Create volumes for storage backed mount points on the storage provided with the storage parameter (default: local). 3. Extract files from backup archive 4. Add bind and device mount points to restored configuration (limited to root user) | | | | --- | --- | | ![Note]() | Since bind and device mount points are never backed up, no files are restored in the last step, but only the configuration options. The assumption is that such mount points are either backed up with another mechanism (e.g., NFS space that is bind mounted into many containers), or not intended to be backed up at all. | This simple mode is also used by the container restore operations in the web interface. #### “Advanced” Restore Mode By setting the rootfs parameter (and optionally, any combination of mpX parameters), the pct restore command is automatically switched into an advanced mode. This advanced mode completely ignores the rootfs and mpX configuration options contained in the backup archive, and instead only uses the options explicitly provided as parameters. This mode allows flexible configuration of mount point settings at restore time, for example: * Set target storages, volume sizes and other options for each mount point individually * Redistribute backed up files according to new mount point scheme * Restore to device and/or bind mount points (limited to root user) Managing Containers with pct ---------------------------- The “Proxmox Container Toolkit” (pct) is the command-line tool to manage Proxmox VE containers. It enables you to create or destroy containers, as well as control the container execution (start, stop, reboot, migrate, etc.). It can be used to set parameters in the config file of a container, for example the network configuration or memory limits. ### CLI Usage Examples Create a container based on a Debian template (provided you have already downloaded the template via the web interface) \# pct create 100 /var/lib/vz/template/cache/debian-10.0-standard\_10.0-1\_amd64.tar.gz Start container 100 \# pct start 100 Start a login session via getty \# pct console 100 Enter the LXC namespace and run a shell as root user \# pct enter 100 Display the configuration \# pct config 100 Add a network interface called eth0, bridged to the host bridge vmbr0, set the address and gateway, while it’s running \# pct set 100 -net0 name=eth0,bridge=vmbr0,ip=192.168.15.147/24,gw=192.168.15.1 Reduce the memory of the container to 512MB \# pct set 100 -memory 512 Destroying a container always removes it from Access Control Lists and it always removes the firewall configuration of the container. You have to activate _\--purge_, if you want to additionally remove the container from replication jobs, backup jobs and HA resource configurations. | | | | --- | --- | | ![Note]() | Activating purge will also remove the HA resource from any affinity rules referencing it and will remove rules that have only this one remaining resource. | \# pct destroy 100 --purge Move a mount point volume to a different storage. \# pct move-volume 100 mp0 other-storage Reassign a volume to a different CT. This will remove the volume mp0 from the source CT and attaches it as mp1 to the target CT. In the background the volume is being renamed so that the name matches the new owner. \# pct move-volume 100 mp0 --target-vmid 200 --target-volume mp1 ### Obtaining Debugging Logs In case pct start is unable to start a specific container, it might be helpful to collect debugging output by passing the \--debug flag (replace CTID with the container’s CTID): \# pct start CTID --debug Alternatively, you can use the following lxc-start command, which will save the debug log to the file specified by the \-o output option: \# lxc-start -n CTID -F -l DEBUG -o /tmp/lxc-CTID.log This command will attempt to start the container in foreground mode, to stop the container run pct shutdown CTID or pct stop CTID in a second terminal. The collected debug log is written to /tmp/lxc-CTID.log. | | | | --- | --- | | ![Note]() | If you have changed the container’s configuration since the last start attempt with pct start, you need to run pct start at least once to also update the configuration used by lxc-start. | Migration --------- If you have a cluster, you can migrate your Containers with \# pct migrate This works as long as your Container is offline. If it has local volumes or mount points defined, the migration will copy the content over the network to the target host if the same storage is defined there. Running containers cannot live-migrated due to technical limitations. You can do a restart migration, which shuts down, moves and then starts a container again on the target node. As containers are very lightweight, this results normally only in a downtime of some hundreds of milliseconds. A restart migration can be done through the web interface or by using the \--restart flag with the pct migrate command. A restart migration will shut down the Container and kill it after the specified timeout (the default is 180 seconds). Then it will migrate the Container like an offline migration and when finished, it starts the Container on the target node. Configuration ------------- The /etc/pve/lxc/.conf file stores container configuration, where is the numeric ID of the given container. Like all other files stored inside /etc/pve/, they get automatically replicated to all other cluster nodes. | | | | --- | --- | | ![Note]() | CTIDs < 100 are reserved for internal purposes, and CTIDs need to be unique cluster wide. | Example Container Configuration ostype: debian arch: amd64 hostname: www memory: 512 swap: 512 net0: bridge=vmbr0,hwaddr=66:64:66:64:64:36,ip=dhcp,name=eth0,type=veth rootfs: local:107/vm-107-disk-1.raw,size=7G The configuration files are simple text files. You can edit them using a normal text editor, for example, vi or nano. This is sometimes useful to do small corrections, but keep in mind that you need to restart the container to apply such changes. For that reason, it is usually better to use the pct command to generate and modify those files, or do the whole thing using the GUI. Our toolkit is smart enough to instantaneously apply most changes to running containers. This feature is called “hot plug”, and there is no need to restart the container in that case. In cases where a change cannot be hot-plugged, it will be registered as a pending change (shown in red color in the GUI). They will only be applied after rebooting the container. ### File Format The container configuration file uses a simple colon separated key/value format. Each line has the following format: \# this is a comment OPTION: value Blank lines in those files are ignored, and lines starting with a # character are treated as comments and are also ignored. It is possible to add low-level, LXC style configuration directly, for example: lxc.init\_cmd: /sbin/my\_own\_init or lxc.init\_cmd = /sbin/my\_own\_init The settings are passed directly to the LXC low-level tools. ### Snapshots When you create a snapshot, pct stores the configuration at snapshot time into a separate snapshot section within the same configuration file. For example, after creating a snapshot called “testsnapshot”, your configuration file will look like this: Container configuration with snapshot memory: 512 swap: 512 parent: testsnaphot ... \[testsnaphot\] memory: 512 swap: 512 snaptime: 1457170803 ... There are a few snapshot related properties like parent and snaptime. The parent property is used to store the parent/child relationship between snapshots. snaptime is the snapshot creation time stamp (Unix epoch). ### Options arch: (_default =_ amd64) OS architecture type. cmode: (_default =_ tty) Console mode. By default, the console command tries to open a connection to one of the available tty devices. By setting cmode to _console_ it tries to attach to /dev/console instead. If you set cmode to _shell_, it simply invokes a shell inside the container (no login). console: (_default =_ 1) Attach a console device (/dev/console) to the container. cores: (1 - 8192) The number of cores assigned to the container. A container can use all available cores by default. cpulimit: (0 - 8192) (_default =_ 0) Limit of CPU usage. | | | | --- | --- | | ![Note]() | If the computer has 2 CPUs, it has a total of _2_ CPU time. Value _0_ indicates no CPU limit. | cpuunits: (0 - 500000) (_default =_ cgroup v1: 1024, cgroup v2: 100) CPU weight for a container. Argument is used in the kernel fair scheduler. The larger the number is, the more CPU time this container gets. Number is relative to the weights of all the other running guests. debug: (_default =_ 0) Try to be more verbose. For now this only enables debug log-level on start. description: Description for the Container. Shown in the web-interface CT’s summary. This is saved as comment inside the configuration file. dev\[n\]: \[\[path=\]\] \[,deny-write=<1|0>\] \[,gid=\] \[,mode=\] \[,uid=\] Device to pass through to the container deny-write\= (_default =_ 0) Deny the container to write to the device gid\= (0 - N) Group ID to be assigned to the device node mode\= Access mode to be set on the device node path\= Path to the device to pass through to the container uid\= (0 - N) User ID to be assigned to the device node entrypoint: (?^:\[^\\x00-\\x08\\x10-\\x1F\\x7F\]+) (_default =_ /sbin/init) Command to run as init, optionally with arguments; may start with an absolute path, relative path, or a binary in $PATH. env: (?^:(?:\\w+=\[^\\x00-\\x08\\x10-\\x1F\\x7F\]\*)(?:\\0\\w+=\[^\\x00-\\x08\\x10-\\x1F\\x7F\]\*)\*) The container runtime environment as NUL-separated list. Replaces any lxc.environment.runtime entries in the config. features: \[force\_rw\_sys=<1|0>\] \[,fuse=<1|0>\] \[,keyctl=<1|0>\] \[,mknod=<1|0>\] \[,mount=\] \[,nesting=<1|0>\] Allow containers access to advanced features. force\_rw\_sys\= (_default =_ 0) Mount /sys in unprivileged containers as rw instead of mixed. This can break networking under newer (>= v245) systemd-network use. fuse\= (_default =_ 0) Allow using _fuse_ file systems in a container. Note that interactions between fuse and the freezer cgroup can potentially cause I/O deadlocks. keyctl\= (_default =_ 0) For unprivileged containers only: Allow the use of the keyctl() system call. This is required to use docker inside a container. By default unprivileged containers will see this system call as non-existent. This is mostly a workaround for systemd-networkd, as it will treat it as a fatal error when some keyctl() operations are denied by the kernel due to lacking permissions. Essentially, you can choose between running systemd-networkd or docker. mknod\= (_default =_ 0) Allow unprivileged containers to use mknod() to add certain device nodes. This requires a kernel with seccomp trap to user space support (5.3 or newer). This is experimental. mount\= Allow mounting file systems of specific types. This should be a list of file system types as used with the mount command. Note that this can have negative effects on the container’s security. With access to a loop device, mounting a file can circumvent the mknod permission of the devices cgroup, mounting an NFS file system can block the host’s I/O completely and prevent it from rebooting, etc. nesting\= (_default =_ 0) Allow nesting. Best used with unprivileged containers with additional id mapping. Note that this will expose procfs and sysfs contents of the host to the guest. This is also required by systemd to isolate services. hookscript: Script that will be executed during various steps in the containers lifetime. hostname: Set a host name for the container. lock: Lock/unlock the container. memory: (16 - N) (_default =_ 512) Amount of RAM for the container in MB. mp\[n\]: \[volume=\] ,mp= \[,acl=<1|0>\] \[,backup=<1|0>\] \[,mountoptions=\] \[,quota=<1|0>\] \[,replicate=<1|0>\] \[,ro=<1|0>\] \[,shared=<1|0>\] \[,size=\] Use volume as container mount point. Use the special syntax STORAGE\_ID:SIZE\_IN\_GiB to allocate a new volume. acl\= Explicitly enable or disable ACL support. backup\= Whether to include the mount point in backups (only used for volume mount points). mountoptions\= Extra mount options for rootfs/mps. mp\= Path to the mount point as seen from inside the container. | | | | --- | --- | | ![Note]() | Must not contain any symlinks for security reasons. | quota\= Enable user quotas inside the container (not supported with zfs subvolumes) replicate\= (_default =_ 1) Will include this volume to a storage replica job. ro\= Read-only mount point shared\= (_default =_ 0) Mark this non-volume mount point as available on all nodes. | | | | --- | --- | | ![Warning]() | This option does not share the mount point automatically, it assumes it is shared already! | size\= Volume size (read only value). volume\= Volume, device or directory to mount into the container. nameserver: Sets DNS server IP address for a container. Create will automatically use the setting from the host if you neither set searchdomain nor nameserver. net\[n\]: name= \[,bridge=\] \[,firewall=<1|0>\] \[,gw=\] \[,gw6=\] \[,host-managed=<1|0>\] \[,hwaddr=\] \[,ip=<(IPv4/CIDR|dhcp|manual)>\] \[,ip6=<(IPv6/CIDR|auto|dhcp|manual)>\] \[,link\_down=<1|0>\] \[,mtu=\] \[,rate=\] \[,tag=\] \[,trunks=\] \[,type=\] Specifies network interfaces for the container. bridge\= Bridge to attach the network device to. firewall\= Controls whether this interface’s firewall rules should be used. gw\= Default gateway for IPv4 traffic. gw6\= Default gateway for IPv6 traffic. host-managed\= Whether this interface’s IP configuration should be managed by the host. hwaddr\= A common MAC address with the I/G (Individual/Group) bit not set. ip\=<(IPv4/CIDR|dhcp|manual)> IPv4 address in CIDR format. ip6\=<(IPv6/CIDR|auto|dhcp|manual)> IPv6 address in CIDR format. link\_down\= Whether this interface should be disconnected (like pulling the plug). mtu\= (64 - 65535) Maximum transfer unit of the interface. (lxc.network.mtu) name\= Name of the network device as seen from inside the container. (lxc.network.name) rate\= Apply rate limiting to the interface tag\= (1 - 4094) VLAN tag for this interface. trunks\= VLAN ids to pass through the interface type\= Network interface type. onboot: (_default =_ 0) Specifies whether a container will be started during system bootup. ostype: OS type. This is used to setup configuration inside the container, and corresponds to lxc setup scripts in /usr/share/lxc/config/.common.conf. Value _unmanaged_ can be used to skip and OS specific setup. protection: (_default =_ 0) Sets the protection flag of the container. This will prevent the CT or CT’s disk remove/update operation. rootfs: \[volume=\] \[,acl=<1|0>\] \[,mountoptions=\] \[,quota=<1|0>\] \[,replicate=<1|0>\] \[,ro=<1|0>\] \[,shared=<1|0>\] \[,size=\] Use volume as container root. acl\= Explicitly enable or disable ACL support. mountoptions\= Extra mount options for rootfs/mps. quota\= Enable user quotas inside the container (not supported with zfs subvolumes) replicate\= (_default =_ 1) Will include this volume to a storage replica job. ro\= Read-only mount point shared\= (_default =_ 0) Mark this non-volume mount point as available on all nodes. | | | | --- | --- | | ![Warning]() | This option does not share the mount point automatically, it assumes it is shared already! | size\= Volume size (read only value). volume\= Volume, device or directory to mount into the container. searchdomain: Sets DNS search domains for a container. Create will automatically use the setting from the host if you neither set searchdomain nor nameserver. startup: \`\[\[order=\]\\d+\] \[,up=\\d+\] \[,down=\\d+\] \` Startup and shutdown behavior. Order is a non-negative number defining the general startup order. Shutdown in done with reverse ordering. Additionally you can set the _up_ or _down_ delay in seconds, which specifies a delay to wait before the next VM is started or stopped. swap: (0 - N) (_default =_ 512) Amount of SWAP for the container in MB. tags: Tags of the Container. This is only meta information. template: (_default =_ 0) Enable/disable Template. timezone: Time zone to use in the container. If option isn’t set, then nothing will be done. Can be set to _host_ to match the host time zone, or an arbitrary time zone option from /usr/share/zoneinfo/zone.tab tty: (0 - 6) (_default =_ 2) Specify the number of tty available to the container unprivileged: (_default =_ 0) Makes the container run as unprivileged user. For creation, the default is 1. For restore, the default is the value from the backup. (Should not be modified manually.) unused\[n\]: \[volume=\] Reference to unused volumes. This is used internally, and should not be modified manually. volume\= The volume that is not used currently. Locks ----- Container migrations, snapshots and backups (vzdump) set a lock to prevent incompatible concurrent actions on the affected container. Sometimes you need to remove such a lock manually (e.g., after a power failure). \# pct unlock | | | | --- | --- | | ![Caution]() | Only do this if you are sure the action which set the lock is no longer running. | Migrate container from OpenVZ to Linux container ------------------------------------------------ Follow this howto: * [Convert OpenVZ to LXC](https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC "Convert OpenVZ to LXC") References ---------- * [Wikipedia Linux Container](https://en.wikipedia.org/wiki/LXC) * [Linux Container](https://linuxcontainers.org/) * [GIT Linux Container](https://github.com/lxc) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Linux\_Container&oldid=12407#\_bind\_mount\_points](https://pve.proxmox.com/mediawiki/index.php?title=Linux_Container&oldid=12407#_bind_mount_points) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Reference Documentation](https://pve.proxmox.com/wiki/Category:Reference_Documentation "Category:Reference Documentation") * [Installation](https://pve.proxmox.com/wiki/Category:Installation "Category:Installation") * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # File:New Text Document.tar.gz - Proxmox VE File:New Text Document.tar.gz ============================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/File:New_Text_Document.tar.gz#mw-head) [Jump to search](https://pve.proxmox.com/wiki/File:New_Text_Document.tar.gz#searchInput) * [File](https://pve.proxmox.com/wiki/File:New_Text_Document.tar.gz#file) * [File history](https://pve.proxmox.com/wiki/File:New_Text_Document.tar.gz#filehistory) * [File usage](https://pve.proxmox.com/wiki/File:New_Text_Document.tar.gz#filelinks) [New\_Text\_Document.tar.gz](https://pve.proxmox.com/mediawiki/images/c/c5/New_Text_Document.tar.gz "New Text Document.tar.gz") (file size: 4 bytes, MIME type: unknown/unknown) **Warning:** This file type may contain malicious code. By executing it, your system may be compromised. File history ------------ Click on a date/time to view the file as it appeared at that time. | | Date/Time | Dimensions | User | Comment | | --- | --- | --- | --- | --- | | current | [12:24, 23 August 2010](https://pve.proxmox.com/mediawiki/images/c/c5/New_Text_Document.tar.gz) | (4 bytes) | [Martin](https://pve.proxmox.com/wiki/User:Martin "User:Martin")
([talk](https://pve.proxmox.com/wiki/User_talk:Martin "User talk:Martin")
\| [contribs](https://pve.proxmox.com/wiki/Special:Contributions/Martin "Special:Contributions/Martin")
) | | You cannot overwrite this file. File usage ---------- The following file is a duplicate of this file ([more details](https://pve.proxmox.com/wiki/Special:FileDuplicateSearch/New_Text_Document.tar.gz "Special:FileDuplicateSearch/New Text Document.tar.gz") ): * [File:New Text Document.txt](https://pve.proxmox.com/wiki/File:New_Text_Document.txt "File:New Text Document.txt") There are no pages that use this file. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=File:New\_Text\_Document.tar.gz&oldid=2385](https://pve.proxmox.com/mediawiki/index.php?title=File:New_Text_Document.tar.gz&oldid=2385) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Storage Model" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Storage Model" ================================== ← [Storage Model](https://pve.proxmox.com/mediawiki/index.php?title=Storage_Model&action=edit&redlink=1 "Storage Model (page does not exist)") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Storage_Model#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Storage_Model#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Storage Model](https://pve.proxmox.com/mediawiki/index.php?title=Storage_Model&action=edit&redlink=1 "Storage Model (page does not exist)") **: Displaying 4 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Storage_Model&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Storage_Model&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Storage_Model&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Storage_Model&limit=500) ) * [Paravirtualized Network Drivers for Windows](https://pve.proxmox.com/wiki/Paravirtualized_Network_Drivers_for_Windows "Paravirtualized Network Drivers for Windows") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Paravirtualized+Network+Drivers+for+Windows "Special:WhatLinksHere") ) * [Proxmox VE News](https://pve.proxmox.com/wiki/Proxmox_VE_News "Proxmox VE News") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Proxmox+VE+News "Special:WhatLinksHere") ) * [Dynamic Memory Management](https://pve.proxmox.com/wiki/Dynamic_Memory_Management "Dynamic Memory Management") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Dynamic+Memory+Management "Special:WhatLinksHere") ) * [Convert OpenVZ to LXC](https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC "Convert OpenVZ to LXC") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Convert+OpenVZ+to+LXC "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Storage_Model&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Storage_Model&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Storage_Model&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Storage_Model&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Storage\_Model](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Storage_Model) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Cloud-Init Support - Proxmox VE Cloud-Init Support ================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Cloud-Init_Support#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Cloud-Init_Support#searchInput) [Cloud-Init](https://cloudinit.readthedocs.io/) is the de facto multi-distribution package that handles early initialization of a virtual machine instance. Using Cloud-Init, configuration of network devices and ssh keys on the hypervisor side is possible. When the VM starts for the first time, the Cloud-Init software inside the VM will apply those settings. Many Linux distributions provide ready-to-use Cloud-Init images, mostly designed for _OpenStack_. These images will also work with Proxmox VE. While it may seem convenient to get such ready-to-use images, we usually recommended to prepare the images by yourself. The advantage is that you will know exactly what you have installed, and this helps you later to easily customize the image for your needs. Once you have created such a Cloud-Init image we recommend to convert it into a VM template. From a VM template you can quickly create linked clones, so this is a fast method to roll out new VM instances. You just need to configure the network (and maybe the ssh keys) before you start the new VM. We recommend using SSH key-based authentication to login to the VMs provisioned by Cloud-Init. It is also possible to set a password, but this is not as safe as using SSH key-based authentication because Proxmox VE needs to store an encrypted version of that password inside the Cloud-Init data. Proxmox VE generates an ISO image to pass the Cloud-Init data to the VM. For that purpose, all Cloud-Init VMs need to have an assigned CD-ROM drive. Usually, a serial console should be added and used as a display. Many Cloud-Init images rely on this, it is a requirement for OpenStack. However, other images might have problems with this configuration. Switch back to the default display configuration if using a serial console doesn’t work. Preparing Cloud-Init Templates ------------------------------ The first step is to prepare your VM. Basically you can use any VM. Simply install the Cloud-Init packages **inside the VM** that you want to prepare. On Debian/Ubuntu based systems this is as simple as: apt-get install cloud-init | | | | --- | --- | | ![Warning]() | This command is **not** intended to be executed on the Proxmox VE host, but only inside the VM. | Already many distributions provide ready-to-use Cloud-Init images (provided as .qcow2 files), so alternatively you can simply download and import such images. For the following example, we will use the cloud image provided by Ubuntu at [https://cloud-images.ubuntu.com](https://cloud-images.ubuntu.com/) . \# download the image wget https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-amd64.img # create a new VM with VirtIO SCSI controller qm create 9000 --memory 2048 --net0 virtio,bridge=vmbr0 --scsihw virtio-scsi-pci # import the downloaded disk to the local-lvm storage, attaching it as a SCSI drive qm set 9000 --scsi0 local-lvm:0,import-from=/path/to/bionic-server-cloudimg-amd64.img | | | | --- | --- | | ![Note]() | Ubuntu Cloud-Init images require the virtio-scsi-pci controller type for SCSI drives. | [![screenshot/gui-cloudinit-hardware.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-cloudinit-hardware.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-cloudinit-hardware.png) ##### Add Cloud-Init CD-ROM drive The next step is to configure a CD-ROM drive, which will be used to pass the Cloud-Init data to the VM. qm set 9000 --ide2 local-lvm:cloudinit To be able to boot directly from the Cloud-Init image, set the boot parameter to order=scsi0 to restrict BIOS to boot from this disk only. This will speed up booting, because VM BIOS skips the testing for a bootable CD-ROM. qm set 9000 --boot order=scsi0 For many Cloud-Init images, it is required to configure a serial console and use it as a display. If the configuration doesn’t work for a given image however, switch back to the default display instead. qm set 9000 --serial0 socket --vga serial0 In a last step, it is helpful to convert the VM into a template. From this template you can then quickly create linked clones. The deployment from VM templates is much faster than creating a full clone (copy). qm template 9000 Deploying Cloud-Init Templates ------------------------------ [![screenshot/gui-cloudinit-config.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-cloudinit-config.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-cloudinit-config.png) You can easily deploy such a template by cloning: qm clone 9000 123 --name ubuntu2 Then configure the SSH public key used for authentication, and configure the IP setup: qm set 123 --sshkey ~/.ssh/id\_rsa.pub qm set 123 --ipconfig0 ip=10.0.10.123/24,gw=10.0.10.1 You can also configure all the Cloud-Init options using a single command only. We have simply split the above example to separate the commands for reducing the line length. Also make sure to adopt the IP setup for your specific environment. Custom Cloud-Init Configuration ------------------------------- The Cloud-Init integration also allows custom config files to be used instead of the automatically generated configs. This is done via the cicustom option on the command line: qm set 9000 --cicustom "user=,network=,meta=" The custom config files have to be on a storage that supports snippets and have to be available on all nodes the VM is going to be migrated to. Otherwise the VM won’t be able to start. For example: qm set 9000 --cicustom "user=local:snippets/userconfig.yaml" There are three kinds of configs for Cloud-Init. The first one is the user config as seen in the example above. The second is the network config and the third the meta config. They can all be specified together or mixed and matched however needed. The automatically generated config will be used for any that don’t have a custom config file specified. The generated config can be dumped to serve as a base for custom configs: qm cloudinit dump 9000 user The same command exists for network and meta. Cloud-Init on Windows --------------------- There is a reimplementation of Cloud-Init available for Windows called [cloudbase-init](https://cloudbase.it/) . Not every feature of Cloud-Init is available with Cloudbase-Init, and some features differ compared to Cloud-Init. Cloudbase-Init requires both ostype set to any Windows version and the citype set to configdrive2, which is the default with any Windows ostype. There are no ready-made cloud images for Windows available for free. Using Cloudbase-Init requires manually installing and configuring a Windows guest. Preparing Cloudbase-Init Templates ---------------------------------- The first step is to install Windows in a VM. Download and install Cloudbase-Init in the guest. It may be necessary to install the Beta version. Don’t run Sysprep at the end of the installation. Instead configure Cloudbase-Init first. A few common options to set would be: * _username_: This sets the username of the administrator * _groups_: This allows one to add the user to the Administrators group * _inject\_user\_password_: Set this to true to allow setting the password in the VM config * _first\_logon\_behaviour_: Set this to no to not require a new password on login * _rename\_admin\_user_: Set this to true to allow renaming the default Administrator user to the username specified with username * _metadata\_services_: Set this to cloudbaseinit.metadata.services.configdrive.ConfigDriveService for Cloudbase-Init to first check this service. Otherwise it may take a few minutes for Cloudbase-Init to configure the system after boot. Some plugins, for example the SetHostnamePlugin, require reboots and will do so automatically. To disable automatic reboots by Cloudbase-Init, you can set allow\_reboot to false. A full set of configuration options can be found in the [official cloudbase-init documentation](https://cloudbase-init.readthedocs.io/en/latest/config.html) . It can make sense to make a snapshot after configuring in case some parts of the config still need adjustments. After configuring Cloudbase-Init you can start creating the template. Shutdown the Windows guest, add a Cloud-Init disk and make it into a template. qm set 9000 --ide2 local-lvm:cloudinit qm template 9000 Clone the template into a new VM: qm clone 9000 123 --name windows123 Then set the password, network config and SSH key: qm set 123 --cipassword qm set 123 --ipconfig0 ip=10.0.10.123/24,gw=10.0.10.1 qm set 123 --sshkey ~/.ssh/id\_rsa.pub Make sure that the ostype is set to any Windows version before setting the password. Otherwise the password will be encrypted and Cloudbase-Init will use the encrypted password as plaintext password. When everything is set, start the cloned guest. On the first boot the login won’t work and it will reboot automatically for the changed hostname. After the reboot the new password should be set and login should work. Cloudbase-Init and Sysprep -------------------------- Sysprep is a feature to reset the configuration of Windows and provide a new system. This can be used in conjunction with Cloudbase-Init to create a clean template. When using Sysprep there are 2 configuration files that need to be adapted. The first one is the normal configuration file, the second one is the one ending in \-unattend.conf. Cloudbase-Init runs in 2 steps, first the Sysprep step using the \-unattend.conf and then the regular step using the primary config file. For Windows Server running Sysprep with the provided Unattend.xml file should work out of the box. Normal Windows versions however require additional steps: 1. Open a PowerShell instance 2. Enable the Administrator user: net user Administrator /active:yes\` 3. Install Cloudbase-Init using the Administrator user 4. Modify Unattend.xml to include the command to enable the Administrator user on the first boot after sysprepping: net user administrator /active:yes 1 Enable Administrator User Make sure the does not conflict with other synchronous commands. Modify of the Cloudbase-Init command to run after this one by increasing the number to a higher value: 2 5. (Windows 11 only) Remove the conflicting Microsoft.OneDriveSync package: Get-AppxPackage -AllUsers Microsoft.OneDriveSync | Remove-AppxPackage -AllUsers 6. cd into the Cloudbase-Init config directory: cd 'C:\\Program Files\\Cloudbase Solutions\\Cloudbase-Init\\conf' 7. (optional) Create a snapshot of the VM before Sysprep in case of a misconfiguration 8. Run Sysprep: C:\\Windows\\System32\\Sysprep\\sysprep.exe /generalize /oobe /unattend:Unattend.xml After following the above steps the VM should be in shut down state due to the Sysprep. Now you can make it into a template, clone it and configure it as needed. Cloud-Init specific Options --------------------------- cicustom: \[meta=\] \[,network=\] \[,user=\] \[,vendor=\] Specify custom files to replace the automatically generated ones at start. meta\= Specify a custom file containing all meta data passed to the VM via cloud-init. This is provider specific meaning configdrive2 and nocloud differ. network\= To pass a custom file containing all network data to the VM via cloud-init. user\= To pass a custom file containing all user data to the VM via cloud-init. vendor\= To pass a custom file containing all vendor data to the VM via cloud-init. cipassword: Password to assign the user. Using this is generally not recommended. Use ssh keys instead. Also note that older cloud-init versions do not support hashed passwords. citype: Specifies the cloud-init configuration format. The default depends on the configured operating system type (ostype. We use the nocloud format for Linux, and configdrive2 for windows. ciupgrade: (_default =_ 1) do an automatic package upgrade after the first boot. ciuser: User name to change ssh keys and password for instead of the image’s configured default user. ipconfig\[n\]: \[gw=\] \[,gw6=\] \[,ip=\] \[,ip6=\] Specify IP addresses and gateways for the corresponding interface. IP addresses use CIDR notation, gateways are optional but need an IP of the same type specified. The special string _dhcp_ can be used for IP addresses to use DHCP, in which case no explicit gateway should be provided. For IPv6 the special string _auto_ can be used to use stateless autoconfiguration. This requires cloud-init 19.4 or newer. If cloud-init is enabled and neither an IPv4 nor an IPv6 address is specified, it defaults to using dhcp on IPv4. gw\= Default gateway for IPv4 traffic. | | | | --- | --- | | ![Note]() | Requires option(s): ip | gw6\= Default gateway for IPv6 traffic. | | | | --- | --- | | ![Note]() | Requires option(s): ip6 | ip\= (_default =_ dhcp) IPv4 address in CIDR format. ip6\= (_default =_ dhcp) IPv6 address in CIDR format. nameserver: Sets DNS server IP address for a container. Create will automatically use the setting from the host if neither searchdomain nor nameserver are set. searchdomain: Sets DNS search domains for a container. Create will automatically use the setting from the host if neither searchdomain nor nameserver are set. sshkeys: Setup public SSH keys (one key per line, OpenSSH format). See Also -------- * [Qemu/KVM Virtual Machines](https://pve.proxmox.com/wiki/Qemu/KVM_Virtual_Machines) * [Cloud-Init\_FAQ](https://pve.proxmox.com/wiki/Cloud-Init_FAQ "Cloud-Init FAQ") Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Cloud-Init\_Support&oldid=12418](https://pve.proxmox.com/mediawiki/index.php?title=Cloud-Init_Support&oldid=12418) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Reference Documentation](https://pve.proxmox.com/wiki/Category:Reference_Documentation "Category:Reference Documentation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Dynamic Memory Management" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Dynamic Memory Management" ============================================== ← [Dynamic Memory Management](https://pve.proxmox.com/wiki/Dynamic_Memory_Management "Dynamic Memory Management") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Dynamic_Memory_Management#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Dynamic_Memory_Management#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Dynamic Memory Management](https://pve.proxmox.com/wiki/Dynamic_Memory_Management "Dynamic Memory Management") **: Displaying 14 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Dynamic_Memory_Management&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Dynamic_Memory_Management&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Dynamic_Memory_Management&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Dynamic_Memory_Management&limit=500) ) * [Paravirtualized Network Drivers for Windows](https://pve.proxmox.com/wiki/Paravirtualized_Network_Drivers_for_Windows "Paravirtualized Network Drivers for Windows") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Paravirtualized+Network+Drivers+for+Windows "Special:WhatLinksHere") ) * [KSM](https://pve.proxmox.com/mediawiki/index.php?title=KSM&redirect=no "KSM") (redirect page) ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=KSM "Special:WhatLinksHere") ) * [Paravirtualized Block Drivers for Windows](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows "Paravirtualized Block Drivers for Windows") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Paravirtualized+Block+Drivers+for+Windows "Special:WhatLinksHere") ) * [Windows 2012 guest best practices](https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices "Windows 2012 guest best practices") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Windows+2012+guest+best+practices "Special:WhatLinksHere") ) * [Windows 7 guest best practices](https://pve.proxmox.com/wiki/Windows_7_guest_best_practices "Windows 7 guest best practices") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Windows+7+guest+best+practices "Special:WhatLinksHere") ) * [Windows 8 guest best practices](https://pve.proxmox.com/wiki/Windows_8_guest_best_practices "Windows 8 guest best practices") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Windows+8+guest+best+practices "Special:WhatLinksHere") ) * [Windows VirtIO Drivers](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers "Windows VirtIO Drivers") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Windows+VirtIO+Drivers "Special:WhatLinksHere") ) * [Windows 10 guest best practices](https://pve.proxmox.com/wiki/Windows_10_guest_best_practices "Windows 10 guest best practices") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Windows+10+guest+best+practices "Special:WhatLinksHere") ) * [Windows 2019 guest best practices](https://pve.proxmox.com/wiki/Windows_2019_guest_best_practices "Windows 2019 guest best practices") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Windows+2019+guest+best+practices "Special:WhatLinksHere") ) * [Windows 2016 guest best practices](https://pve.proxmox.com/wiki/Windows_2016_guest_best_practices "Windows 2016 guest best practices") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Windows+2016+guest+best+practices "Special:WhatLinksHere") ) * [Windows 2022 guest best practices](https://pve.proxmox.com/wiki/Windows_2022_guest_best_practices "Windows 2022 guest best practices") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Windows+2022+guest+best+practices "Special:WhatLinksHere") ) * [Windows 11 guest best practices](https://pve.proxmox.com/wiki/Windows_11_guest_best_practices "Windows 11 guest best practices") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Windows+11+guest+best+practices "Special:WhatLinksHere") ) * [Windows 2025 guest best practices](https://pve.proxmox.com/wiki/Windows_2025_guest_best_practices "Windows 2025 guest best practices") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Windows+2025+guest+best+practices "Special:WhatLinksHere") ) * [Template:WinX-install-steps](https://pve.proxmox.com/wiki/Template:WinX-install-steps "Template:WinX-install-steps") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Template%3AWinX-install-steps "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Dynamic_Memory_Management&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Dynamic_Memory_Management&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Dynamic_Memory_Management&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Dynamic_Memory_Management&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Dynamic\_Memory\_Management](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Dynamic_Memory_Management) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # MediaWiki:Post-expand-template-inclusion-category - Proxmox VE MediaWiki:Post-expand-template-inclusion-category ================================================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/MediaWiki:Post-expand-template-inclusion-category#mw-head) [Jump to search](https://pve.proxmox.com/wiki/MediaWiki:Post-expand-template-inclusion-category#searchInput) Pages where template include size is exceeded Retrieved from "[https://pve.proxmox.com/wiki/MediaWiki:Post-expand-template-inclusion-category](https://pve.proxmox.com/wiki/MediaWiki:Post-expand-template-inclusion-category) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # MediaWiki:Unstrip-size-category - Proxmox VE MediaWiki:Unstrip-size-category =============================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/MediaWiki:Unstrip-size-category#mw-head) [Jump to search](https://pve.proxmox.com/wiki/MediaWiki:Unstrip-size-category#searchInput) Pages where the unstrip size limit is exceeded Retrieved from "[https://pve.proxmox.com/wiki/MediaWiki:Unstrip-size-category](https://pve.proxmox.com/wiki/MediaWiki:Unstrip-size-category) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Template:Tts - Proxmox VE Template:Tts ============ From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Template:Tts#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Template:Tts#searchInput) {{{{{}}}|{{{1}}}|{{{2}}}}} Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Template:Tts&oldid=17](https://pve.proxmox.com/mediawiki/index.php?title=Template:Tts&oldid=17) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # MediaWiki:Template-equals-category - Proxmox VE MediaWiki:Template-equals-category ================================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/MediaWiki:Template-equals-category#mw-head) [Jump to search](https://pve.proxmox.com/wiki/MediaWiki:Template-equals-category#searchInput) Pages which use = as a template Retrieved from "[https://pve.proxmox.com/wiki/MediaWiki:Template-equals-category](https://pve.proxmox.com/wiki/MediaWiki:Template-equals-category) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Passthrough Physical Disk to Virtual Machine (VM) - Proxmox VE Passthrough Physical Disk to Virtual Machine (VM) ================================================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Passthrough_Physical_Disk_to_Virtual_Machine_(VM)#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Passthrough_Physical_Disk_to_Virtual_Machine_(VM)#searchInput) By adding the raw physical device to the Virtual machine, you can test installers and other disk repair tools that work with disk controllers like `ddrescue`, Clonezilla or Ubuntu Rescue Remix. **NOTE**: This guide is meant for QEMU/KVM based Virtual Machines, **not** for Container. For the latter see [https://forum.proxmox.com/threads/container-with-physical-disk.42280/#post-203292](https://forum.proxmox.com/threads/container-with-physical-disk.42280/#post-203292) As the disk is attached to the physical and virtual host, this will also prevent Virtual Machine live migration. A second side effect is host system IO wait, when running ddrescue, other VM's running on the host can stutter. Contents -------- * [1 Attach Pass Through Disk](https://pve.proxmox.com/wiki/Passthrough_Physical_Disk_to_Virtual_Machine_(VM)#Attach_Pass_Through_Disk) * [1.1 Identify Disk](https://pve.proxmox.com/wiki/Passthrough_Physical_Disk_to_Virtual_Machine_(VM)#Identify_Disk) * [1.1.1 lshw](https://pve.proxmox.com/wiki/Passthrough_Physical_Disk_to_Virtual_Machine_(VM)#lshw) * [1.1.2 List disk by-id with lsblk](https://pve.proxmox.com/wiki/Passthrough_Physical_Disk_to_Virtual_Machine_(VM)#List_disk_by-id_with_lsblk) * [1.1.3 Short List](https://pve.proxmox.com/wiki/Passthrough_Physical_Disk_to_Virtual_Machine_(VM)#Short_List) * [1.2 Update Configuration](https://pve.proxmox.com/wiki/Passthrough_Physical_Disk_to_Virtual_Machine_(VM)#Update_Configuration) * [1.2.1 Hot-Plug/Add physical device as new virtual SCSI disk](https://pve.proxmox.com/wiki/Passthrough_Physical_Disk_to_Virtual_Machine_(VM)#Hot-Plug/Add_physical_device_as_new_virtual_SCSI_disk) * [1.2.2 Hot-Unplug/Remove virtual disk](https://pve.proxmox.com/wiki/Passthrough_Physical_Disk_to_Virtual_Machine_(VM)#Hot-Unplug/Remove_virtual_disk) * [1.3 Check Configuration File](https://pve.proxmox.com/wiki/Passthrough_Physical_Disk_to_Virtual_Machine_(VM)#Check_Configuration_File) * [1.4 Stop and Restart KVM Virtual Machine](https://pve.proxmox.com/wiki/Passthrough_Physical_Disk_to_Virtual_Machine_(VM)#Stop_and_Restart_KVM_Virtual_Machine) * [2 Tutorial](https://pve.proxmox.com/wiki/Passthrough_Physical_Disk_to_Virtual_Machine_(VM)#Tutorial) * [3 Disk Recovery Tools](https://pve.proxmox.com/wiki/Passthrough_Physical_Disk_to_Virtual_Machine_(VM)#Disk_Recovery_Tools) Attach Pass Through Disk ======================== Identify Disk ------------- Before adding a physical disk to host make note of vendor, serial so that you'll know which disk to share in /dev/disk/by-id/ ### lshw lshw is not installed by default on Proxmox VE (see `lsblk` for that below), you can install it by executing `apt install lshw` lshw -class disk -class storage ... \*-disk description: ATA Disk product: ST3000DM001-1CH1 vendor: Seagate physical id: 0.0.0 bus info: scsi@3:0.0.0 logical name: /dev/sda version: CC27 serial: Z1F41BLC size: 2794GiB (3TB) configuration: ansiversion=5 sectorsize=4096 ... Note that device names like `/dev/sdc` should never be used, as this can change between reboots. Use the stable `/dev/disk/by-id` paths instead. Check by listing all of that directory then look for the disk added by matching serial number from lshw and the physical disk: ls -l /dev/disk/by-id/ata-ST3000DM001-1CH166\_Z1F41BLC lrwxrwxrwx 1 root root 9 Jan 21 10:10 /dev/disk/by-id/ata-ST3000DM001-1CH166\_Z1F41BLC -> ../../sda or try ls -l /dev/disk/by-id | grep Z1F41BLC ### List disk by-id with lsblk The `lsblk` is pre-installed, you can print and map the serial and WWN identifiers of attached disks using the following two commands: lsblk -o +MODEL,SERIAL,WWN ls -l /dev/disk/by-id/ You can also use an extended one liner to get the path directly: lsblk |awk 'NR==1{print $0" DEVICE-ID(S)"}NR>1{dev=$1;printf $0" ";system("find /dev/disk/by-id -lname \\"\*"dev"\\" -printf \\" %p\\"");print "";}'|grep -v -E 'part|lvm' NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT DEVICE-ID(S) sda 8:0 0 7.3T 0 disk /dev/disk/by-id/wwn-0x5000c500c35cd719 /dev/disk/by-id/ata-ST8000DM004-2CX188\_ZCT1DNY1 sdb 8:16 1 29G 0 disk /dev/disk/by-id/usb-Generic\_STORAGE\_DEVICE-0:0 sdc 8:32 0 931.5G 0 disk /dev/disk/by-id/usb-JMicron\_Generic\_0123456789ABCDEF-0:0 sdd 8:48 0 1.8T 0 disk /dev/disk/by-id/wwn-0x5000c500661eeebd /dev/disk/by-id/ata-ST2000DX001-1CM164\_Z1E783H2 [make-lsblk-list-devices-by-id](https://unix.stackexchange.com/questions/387855/make-lsblk-list-devices-by-id) ### Short List find /dev/disk/by-id/ -type l|xargs -I{} ls -l {}|grep -v -E '\[0-9\]$' |sort -k11|cut -d' ' -f9,10,11,12 /dev/disk/by-id/ata-ST8000DM004-2CX188\_ZCT1DNY1 -> ../../sda /dev/disk/by-id/wwn-0x5000c500c35cd719 -> ../../sda /dev/disk/by-id/usb-Generic\_STORAGE\_DEVICE-0:0 -> ../../sdb /dev/disk/by-id/usb-JMicron\_Generic\_0123456789ABCDEF-0:0 -> ../../sdc /dev/disk/by-id/ata-ST2000DX001-1CM164\_Z1E783H2 -> ../../sdd /dev/disk/by-id/wwn-0x5000c500661eeebd -> ../../sdd Update Configuration -------------------- ### Hot-Plug/Add physical device as new virtual SCSI disk qm set 592 -scsi2 /dev/disk/by-id/ata-ST3000DM001-1CH166\_Z1F41BLC update VM 592: -scsi2 /dev/disk/by-id/ata-ST3000DM001-1CH166\_Z1F41BLC ### Hot-Unplug/Remove virtual disk qm unlink 592 --idlist scsi2 update VM 592: -delete scsi2 Check Configuration File ------------------------ grep Z1F41BLC /etc/pve/qemu-server/592.conf scsi2: /dev/disk/by-id/ata-ST3000DM001-1CH166\_Z1F41BLC,size=2930266584K Stop and Restart KVM Virtual Machine ------------------------------------ You may need to configure the guest operating system now that the disk is available. Tutorial ======== [Example with screenshots](https://dannyda.com/2020/08/26/how-to-passthrough-hdd-ssd-physical-disks-to-vm-on-proxmox-vepve/) Disk Recovery Tools =================== 1. Ubuntu Rescue Remix - [how to use Ubuntu Rescue Remix and Ddrescue](http://www.geekyprojects.com/storage/how-to-recover-data-even-when-hard-drive-is-damaged/) 2. ddrescue 3. gnu ddrescue 4. Clonezilla 5. TestDisk 6. PhotoRec 7. Recuva 8. Foremost 9. Parted Magic 10. SpinRite - Low Cost Commercial - Smartctl tutoral for Proxmox VE planned Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Passthrough\_Physical\_Disk\_to\_Virtual\_Machine\_(VM)&oldid=11538](https://pve.proxmox.com/mediawiki/index.php?title=Passthrough_Physical_Disk_to_Virtual_Machine_(VM)&oldid=11538) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Template:VirtIOFedoraISOFolderNames - Proxmox VE Template:VirtIOFedoraISOFolderNames =================================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Template:VirtIOFedoraISOFolderNames#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Template:VirtIOFedoraISOFolderNames#searchInput) In the iso file provided by Fedora Project drivers for different Windows versions are available, in several folders. The folder names can be a bit confusing, since they refer to the Microsoft legacy naming (i.e. lh=longhorn, that is Vista): you can refer to the schema below (showing also block/baloon drivers folder names): | OS | Numeric version | dir for Storage / Balloon | dir for Network | | --- | --- | --- | --- | | W2008 R2 / Windows 7 | 6.1 | Win7 (32/64) | Win7 (32/64) | | W2008 / Vista | 6.0 | Wlh (32/64) | Vista (32/64) | | W2003 | 5.2 | Wnet (32/64) | XP (32/64) | | XP | 5.1 - 32bit, 5.2 - 64bit | WXp (32 only) | XP (32/64) | Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Template:VirtIOFedoraISOFolderNames&oldid=6302](https://pve.proxmox.com/mediawiki/index.php?title=Template:VirtIOFedoraISOFolderNames&oldid=6302) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # MediaWiki:Math-tracking-category-mhchem-deprecation - Proxmox VE MediaWiki:Math-tracking-category-mhchem-deprecation =================================================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/MediaWiki:Math-tracking-category-mhchem-deprecation#mw-head) [Jump to search](https://pve.proxmox.com/wiki/MediaWiki:Math-tracking-category-mhchem-deprecation#searchInput) Pages that use a deprecated format of the chem tags Retrieved from "[https://pve.proxmox.com/wiki/MediaWiki:Math-tracking-category-mhchem-deprecation](https://pve.proxmox.com/wiki/MediaWiki:Math-tracking-category-mhchem-deprecation) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Storage: User Mode iSCSI" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Storage: User Mode iSCSI" ============================================= ← [Storage: User Mode iSCSI](https://pve.proxmox.com/wiki/Storage:_User_Mode_iSCSI "Storage: User Mode iSCSI") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Storage:_User_Mode_iSCSI#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Storage:_User_Mode_iSCSI#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Storage: User Mode iSCSI](https://pve.proxmox.com/wiki/Storage:_User_Mode_iSCSI "Storage: User Mode iSCSI") **: Displaying 1 item. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Storage:_User_Mode_iSCSI&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Storage:_User_Mode_iSCSI&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Storage:_User_Mode_iSCSI&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Storage:_User_Mode_iSCSI&limit=500) ) * [Main Page](https://pve.proxmox.com/wiki/Main_Page "Main Page") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Main+Page "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Storage:_User_Mode_iSCSI&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Storage:_User_Mode_iSCSI&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Storage:_User_Mode_iSCSI&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Storage:_User_Mode_iSCSI&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Storage:\_User\_Mode\_iSCSI](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Storage:_User_Mode_iSCSI) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Host System Administration" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Host System Administration" =============================================== ← [Host System Administration](https://pve.proxmox.com/wiki/Host_System_Administration "Host System Administration") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Host_System_Administration#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Host_System_Administration#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Host System Administration](https://pve.proxmox.com/wiki/Host_System_Administration "Host System Administration") **: Displaying 1 item. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Host_System_Administration&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Host_System_Administration&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Host_System_Administration&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Host_System_Administration&limit=500) ) * [Main Page](https://pve.proxmox.com/wiki/Main_Page "Main Page") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Main+Page "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Host_System_Administration&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Host_System_Administration&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Host_System_Administration&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Host_System_Administration&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Host\_System\_Administration](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Host_System_Administration) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # DRBD9 - Proxmox VE DRBD9 ===== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/DRBD9#mw-head) [Jump to search](https://pve.proxmox.com/wiki/DRBD9#searchInput) Introduction ------------ DRBD9 is removed from the Proxmox VE core distribution since 4.4 and is now maintained directly by Linbit, due to [license change](https://forum.proxmox.com/threads/drbdmanage-license-change.30404/) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=DRBD9&oldid=9623](https://pve.proxmox.com/mediawiki/index.php?title=DRBD9&oldid=9623) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Cisco UCS - Proxmox VE Cisco UCS ========= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Cisco_UCS#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Cisco_UCS#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Cisco_UCS#Introduction) * [2 Cisco UCS C-Series Rack Servers](https://pve.proxmox.com/wiki/Cisco_UCS#Cisco_UCS_C-Series_Rack_Servers) * [2.1 Proxmox 6](https://pve.proxmox.com/wiki/Cisco_UCS#Proxmox_6) * [2.1.1 C220 M4S](https://pve.proxmox.com/wiki/Cisco_UCS#C220_M4S) * [2.1.2 C240 M4SX](https://pve.proxmox.com/wiki/Cisco_UCS#C240_M4SX) * [2.2 Proxmox 5](https://pve.proxmox.com/wiki/Cisco_UCS#Proxmox_5) * [2.2.1 C220 M4S](https://pve.proxmox.com/wiki/Cisco_UCS#C220_M4S_2) * [2.2.2 C240 M4SX](https://pve.proxmox.com/wiki/Cisco_UCS#C240_M4SX_2) Introduction ============ A community created compatibility list for Cisco UCS Servers. Cisco UCS C-Series Rack Servers =============================== Proxmox 6 --------- ### C220 M4S | Hardware | PID | Firmware version | PVE Kernel version | Notes | | --- | --- | --- | --- | --- | | Cisco UCS VIC1227 VIC MLOM - Dual Port 10Gb SFP+ | UCSC-MLOM-CSC-02 | 4.0(2l) | 5.4.60-1-pve, 5.0.21-5-pve | Works out of the box | | Intel i350 GbE Ethernet controller | | 4.0(2l) | 5.4.60-1-pve, 5.0.21-5-pve | Works out of the box | | Cisco 12G SAS Modular Raid Controller | UCSC-MRAID12G | 4.0(2l) | 5.4.60-1-pve, 5.0.21-5-pve | Works out of the box | ### C240 M4SX | Hardware | PID | Firmware version | PVE Kernel version | Notes | | --- | --- | --- | --- | --- | | Cisco UCS VIC1227 VIC MLOM - Dual Port 10Gb SFP+ | UCSC-MLOM-CSC-02 | 4.0(2l) | 5.4.60-1-pve, 5.0.21-5-pve | Works out of the box | | Intel i350 GbE Ethernet controller | | 4.0(2l) | 5.4.60-1-pve, 5.0.21-5-pve | Works out of the box | | Cisco 12G SAS Modular Raid Controller | UCSC-MRAID12G | 4.0(2l) | 5.4.60-1-pve, 5.0.21-5-pve | Works out of the box | Proxmox 5 --------- ### C220 M4S | Hardware | PID | Firmware version | PVE Kernel version | Notes | | --- | --- | --- | --- | --- | | Cisco UCS VIC1227 VIC MLOM - Dual Port 10Gb SFP+ | UCSC-MLOM-CSC-02 | 3.0(3a) | 4.10.17-2-pve, 4.13.13-6-pve | Works out of the box | | Intel i350 GbE Ethernet controller | | 3.0(3a) | 4.10.17-2-pve, 4.13.13-6-pve | Works out of the box | | Cisco 12G SAS Modular Raid Controller | UCSC-MRAID12G | 3.0(3a) | 4.10.17-2-pve, 4.13.13-6-pve | Works out of the box | ### C240 M4SX | Hardware | PID | Firmware version | PVE Kernel version | Notes | | --- | --- | --- | --- | --- | | Cisco UCS VIC1227 VIC MLOM - Dual Port 10Gb SFP+ | UCSC-MLOM-CSC-02 | 3.0(3f) | 4.13.13-6-pve | Works out of the box | | Intel i350 GbE Ethernet controller | | 3.0(3f) | 4.13.13-6-pve | Works out of the box | | Cisco 12G SAS Modular Raid Controller | UCSC-MRAID12G | 3.0(3f) | 4.13.13-6-pve | Works out of the box | Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Cisco\_UCS&oldid=10847](https://pve.proxmox.com/mediawiki/index.php?title=Cisco_UCS&oldid=10847) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # MediaWiki:Double-px-category - Proxmox VE MediaWiki:Double-px-category ============================ From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/MediaWiki:Double-px-category#mw-head) [Jump to search](https://pve.proxmox.com/wiki/MediaWiki:Double-px-category#searchInput) Pages with image sizes containing extra px Retrieved from "[https://pve.proxmox.com/wiki/MediaWiki:Double-px-category](https://pve.proxmox.com/wiki/MediaWiki:Double-px-category) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Load - Proxmox VE Load ==== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Load#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Load#searchInput) In UNIX computing, the system load is much more than just another Number. Ok Great so what does that mean? Well I am glad you asked. The load number generally is under the format of x.xx (such as 0.23) and it simply expresses how many processes are waiting in the queue to access the processors. The smaller the number the better the load - and the higher the number - generally is associated with a decrease in server performance. While server load is just one of the factors out of many othes (such as cpu usage, swap file size, ram/memory usage etc) generally the load is influenced by each of the aforementioned. For example - if you run top and see that your swap file is being used heavily - chances are you may not have enough ram - since the swap file is on the hard drive - suddenly the disk now needs to spin not only to handle grabbing and writing data for its processes but also to act as RAM.... this causes the I/O to get higher and therefore the load to rise... While this is a simple fix - just add more internal memory - other issues may not be. Generally we suggest starting with the TOP command and looking at the amount of ram / swap in use. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Load&oldid=9023](https://pve.proxmox.com/mediawiki/index.php?title=Load&oldid=9023) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Troubleshooting](https://pve.proxmox.com/wiki/Category:Troubleshooting "Category:Troubleshooting") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "System Requirements" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "System Requirements" ======================================== ← [System Requirements](https://pve.proxmox.com/wiki/System_Requirements "System Requirements") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/System_Requirements#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/System_Requirements#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[System Requirements](https://pve.proxmox.com/wiki/System_Requirements "System Requirements") **: Displaying 1 item. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/System_Requirements&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/System_Requirements&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/System_Requirements&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/System_Requirements&limit=500) ) * [Quick installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Quick+installation "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/System_Requirements&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/System_Requirements&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/System_Requirements&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/System_Requirements&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/System\_Requirements](https://pve.proxmox.com/wiki/Special:WhatLinksHere/System_Requirements) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Performance Tweaks - Proxmox VE Performance Tweaks ================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Performance_Tweaks#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Performance_Tweaks#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Performance_Tweaks#Introduction) * [2 General](https://pve.proxmox.com/wiki/Performance_Tweaks#General) * [2.1 VirtIO](https://pve.proxmox.com/wiki/Performance_Tweaks#VirtIO) * [2.2 Disk Cache](https://pve.proxmox.com/wiki/Performance_Tweaks#Disk_Cache) * [2.2.1 Small Overview](https://pve.proxmox.com/wiki/Performance_Tweaks#Small_Overview) * [3 OS Specific](https://pve.proxmox.com/wiki/Performance_Tweaks#OS_Specific) * [3.1 Windows](https://pve.proxmox.com/wiki/Performance_Tweaks#Windows) * [3.1.1 USB Tablet Device](https://pve.proxmox.com/wiki/Performance_Tweaks#USB_Tablet_Device) * [3.1.2 Use raw disk image and not qcow2](https://pve.proxmox.com/wiki/Performance_Tweaks#Use_raw_disk_image_and_not_qcow2) * [3.1.3 Trace Flag T8038 with Microsoft SQL Server](https://pve.proxmox.com/wiki/Performance_Tweaks#Trace_Flag_T8038_with_Microsoft_SQL_Server) * [3.1.4 Do not use the Virtio Balloon Driver](https://pve.proxmox.com/wiki/Performance_Tweaks#Do_not_use_the_Virtio_Balloon_Driver) Introduction ============ This page is intended to be a collection of various performance tips/tweaks to help you get the most from your KVM virtual machines. General ======= ### VirtIO Use virtIO for disk and network for best performance. * Linux has the drivers built in since Linux 2.6.24 as experimental, and since Linux 3.8 as stable * [FreeBSD](http://freebsd.org/) has the drivers built in since 9.0 * Windows requires the [Windows VirtIO Drivers](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers "Windows VirtIO Drivers") to be downloaded and installed manually ### Disk Cache ℹ️ **Note**: The information below is based on using raw volumes, other volume formats may behave differently. #### Small Overview Note: The overview below is dependent of the specific hardware used, for example a HW Raid with a BBU backed disk cache works just fine with 'writeback' mode, so take it just as an general overview. | Mode | Host Page Cache | Disk Write Cache | Notes | | --- | --- | --- | --- | | none | disabled | enabled | balances performance and safety (better writes) | | writethrough | enabled | disabled | balances performance and safety (better reads) | | writeback | enabled | enabled | fast, can lose data on power outage depending on hardware used | | directsync | disabled | disabled | safest but slowest (relative to the others) | | unsafe | enabled | enabled | doesn't flush data, fastest and unsafest | [![](https://pve.proxmox.com/mediawiki/images/thumb/d/d7/Cache_mode_none.png/300px-Cache_mode_none.png)](https://pve.proxmox.com/wiki/File:Cache_mode_none.png) **cache=none** seems to be the best performance and is the default since Proxmox 2.X. * host page cache is not used * guest disk cache is set to writeback * Warning: like writeback, you can lose data in case of a power failure * You need to use the barrier option in your Linux guest's fstab if kernel < 2.6.37 to avoid FS corruption in case of power failure. > This mode causes qemu-kvm to interact with the disk image file or block device with O\_DIRECT semantics, so the host page cache is bypassed and I/O happens directly between the qemu-kvm userspace buffers and the storage device. Because the actual storage device may report a write as completed when placed in its write queue only, the guest's virtual storage adapter is informed that there is a writeback cache, so the guest would be expected to send down flush commands as needed to manage data integrity. Equivalent to direct access to your hosts' disk, performance wise. [![](https://pve.proxmox.com/mediawiki/images/thumb/1/18/Cache_mode_writethrough.png/300px-Cache_mode_writethrough.png)](https://pve.proxmox.com/wiki/File:Cache_mode_writethrough.png) **cache=writethrough** * host page cache is used as read cache * guest disk cache mode is writethrough * Writethrough causes an fsync for each write. It's the more secure cache mode, you can't lose data but it is also slower. > This mode causes qemu-kvm to interact with the disk image file or block device with O\_DSYNC semantics, where writes are reported as completed only when the data has been committed to the storage device. The host page cache is used in what can be termed a writethrough caching mode. Guest virtual storage adapter is informed that there is no writeback cache, so the guest would not need to send down flush commands to manage data integrity. The storage behaves as if there is a writethrough cache. [![](https://pve.proxmox.com/mediawiki/images/thumb/e/e4/Cache_mode_direct.png/300px-Cache_mode_direct.png)](https://pve.proxmox.com/wiki/File:Cache_mode_direct.png) **cache=directsync** * host page cache is not used * guest disk cache mode is writethrough * similar to writethrough, an fsync is made for each write. > This mode causes qemu-kvm to interact with the disk image file or block device with both O\_DSYNC and O\_DIRECT semantics, where writes are reported as completed only when the data has been committed to the storage device, and when it is also desirable to bypass the host page cache. Like cache=writethrough, it is helpful to guests that do not send flushes when needed. It was the last cache mode added, completing the possible combinations of caching and direct access semantics. [![](https://pve.proxmox.com/mediawiki/images/thumb/4/4f/Cache_mode_writeback.png/300px-Cache_mode_writeback.png)](https://pve.proxmox.com/wiki/File:Cache_mode_writeback.png) **cache=writeback** * host page cache is used as read & write cache * guest disk cache mode is writeback * Warning: you can lose data in case of a power failure * You need to use the barrier option in your Linux guest's fstab if kernel < 2.6.37 to avoid FS corruption in case of power failure. > This mode causes qemu-kvm to interact with the disk image file or block device with neither O\_DSYNC nor O\_DIRECT semantics, so the host page cache is used and writes are reported to the guest as completed when placed in the host page cache, and the normal page cache management will handle commitment to the storage device. Additionally, the guest's virtual storage adapter is informed of the writeback cache, so the guest would be expected to send down flush commands as needed to manage data integrity. Analogous to a raid controller with RAM cache. **cache=writeback (unsafe)** * as **writeback**, but ignores flush commands from the guest! * Warning: No data integrity even if the guest is sending flush commands. Not recommended for production use. * * * For read cache memory: try to add more memory in your guest, they already do the job with their buffer cache cache=writethrough or directsync can be also quite fast if you have a SAN or HW raid controller with battery backed cache. Using qcow2 backed disks and either cache=directsync or writethrough can make things slower. some interestings articles : cache mode and fsync : [http://www.ilsistemista.net/index.php/virtualization/23-kvm-storage-performance-and-cache-settings-on-red-hat-enterprise-linux-62.html?start=2](http://www.ilsistemista.net/index.php/virtualization/23-kvm-storage-performance-and-cache-settings-on-red-hat-enterprise-linux-62.html?start=2) OS Specific =========== Windows ------- ### USB Tablet Device Disabling the USB tablet device in windows VMs can reduce idle CPU usage and reduce context switches. This can be done on the GUI. You can use vmmouse to get the pointer in sync (load drivers inside your VM). [\[1\]](http://forum.proxmox.com/threads/9981-disable-quot-usbdevice-tablet-quot-for-all-VM) ### Use raw disk image and not qcow2 Consider using raw image or partition for a partition, especially with Microsoft SQL database files because qcow2 can be very slow under such type of load. ### Trace Flag T8038 with Microsoft SQL Server Setting the trace flag -T8038 will drastically reduce the number of context switches when running SQL 2005 or 2008. To change the trace flag: 1. Open the SQL server Configuration Manager 2. Open the properties for the SQL service typically named MSSQLSERVER 3. Go to the advanced tab 4. Append ;-T8038 to the end of the startup parameters option For additional references see: [Proxmox forum](http://forum.proxmox.com/threads/5770-Windows-guest-high-context-switch-rate-when-idle) ### Do not use the Virtio Balloon Driver The Balloon driver has been a source of performance problems on Windows, you should avoid it. (see [http://forum.proxmox.com/threads/20265-SOLVED-Hyper-Threading-vs-No-Hyper-Threading-Fixed-vs-Variable-Memory](http://forum.proxmox.com/threads/20265-SOLVED-Hyper-Threading-vs-No-Hyper-Threading-Fixed-vs-Variable-Memory) for the discussion thread) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Performance\_Tweaks&oldid=12235](https://pve.proxmox.com/mediawiki/index.php?title=Performance_Tweaks&oldid=12235) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Accessing Server using different URLs" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Accessing Server using different URLs" ========================================================== ← [Accessing Server using different URLs](https://pve.proxmox.com/mediawiki/index.php?title=Accessing_Server_using_different_URLs&action=edit&redlink=1 "Accessing Server using different URLs (page does not exist)") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Accessing_Server_using_different_URLs#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Accessing_Server_using_different_URLs#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Accessing Server using different URLs](https://pve.proxmox.com/mediawiki/index.php?title=Accessing_Server_using_different_URLs&action=edit&redlink=1 "Accessing Server using different URLs (page does not exist)") **: Displaying 1 item. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Accessing_Server_using_different_URLs&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Accessing_Server_using_different_URLs&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Accessing_Server_using_different_URLs&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Accessing_Server_using_different_URLs&limit=500) ) * [User:Apmuthu](https://pve.proxmox.com/wiki/User:Apmuthu "User:Apmuthu") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User%3AApmuthu "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Accessing_Server_using_different_URLs&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Accessing_Server_using_different_URLs&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Accessing_Server_using_different_URLs&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Accessing_Server_using_different_URLs&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Accessing\_Server\_using\_different\_URLs](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Accessing_Server_using_different_URLs) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # PBS Client CPU Benchmark - Proxmox VE PBS Client CPU Benchmark ======================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#mw-head) [Jump to search](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#Introduction) * [2 Comparison](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#Comparison) * [2.1 PBS Client Benchmark](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#PBS_Client_Benchmark) * [2.2 PBS Client Build](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#PBS_Client_Build) * [3 Data](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#Data) * [3.1 Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#Intel(R)_Xeon(R)_CPU_E5-2620_v3_@_2.40GHz) * [3.1.1 PBS Client Benchmark](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#PBS_Client_Benchmark_2) * [3.1.2 PBS Client Build](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#PBS_Client_Build_2) * [3.2 Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#Intel(R)_Core(TM)_i9-9900K_CPU_@_3.60GHz) * [3.2.1 PBS Client Build](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#PBS_Client_Build_3) * [3.2.2 PBS Client Benchmark](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#PBS_Client_Benchmark_3) * [3.3 Intel(R) Celeron(TM) J4105 CPU @ 1.50GHz](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#Intel(R)_Celeron(TM)_J4105_CPU_@_1.50GHz) * [3.3.1 PBS Client Benchmark](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#PBS_Client_Benchmark_4) * [3.4 Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#Intel(R)_Core(TM)2_Duo_CPU_E8500_@_3.16GHz) * [3.4.1 PBS Client Benchmark](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#PBS_Client_Benchmark_5) * [3.5 AMD Ryzen 7 5800x 8-Core Processor](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#AMD_Ryzen_7_5800x_8-Core_Processor) * [3.5.1 PBS Client Build](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#PBS_Client_Build_4) * [3.5.2 PBS Client Benchmark](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#PBS_Client_Benchmark_6) * [3.6 AMD Ryzen 7 3700X 8-Core Processor](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#AMD_Ryzen_7_3700X_8-Core_Processor) * [3.6.1 PBS Client Benchmark](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#PBS_Client_Benchmark_7) * [3.7 AMD EPYC 7302P 16-Core Processor](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#AMD_EPYC_7302P_16-Core_Processor) * [3.7.1 PBS Client Benchmark](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#PBS_Client_Benchmark_8) * [3.8 ARM64 Cortex-A72 - Raspberry Pi 4](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#ARM64_Cortex-A72_-_Raspberry_Pi_4) * [3.8.1 PBS Client Build](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#PBS_Client_Build_5) * [3.8.2 PBS Client Benchmark](https://pve.proxmox.com/wiki/PBS_Client_CPU_Benchmark#PBS_Client_Benchmark_9) Introduction ============ This article is using the benchmark included in the Proxmox Backup Server client and building said client from source as rough (!) comparison for different CPU performance and efficiency. Note that modern CPUs are really complex, benchmarks should always be seen as such. We use the PBS client benchmark as it replicates a real workload close to 1:1, and we use the compilation of the client as using a modern compiler is one of the hardest stress tests which is still replicating actual workload. It produces an efficiency score, which should be seen as "order of magnitude" score, i.e. logarithmic. A few points more or less may not be relevant and noise coming from input and architecture composition. But, a difference of factor 2 to 5, or even higher, should be seen as actual meaningful difference of that platforms, where the lower is clearly less suited for the workload when efficiency is in one mind. For raw performance the "Sum MiB/s" column can be used as, again rough, estimation. Comparison ========== PBS Client Benchmark -------------------- | Vendor | CPU Model | Arch | Release Y/Q | mTDP W | W/Cores | SHA256 MiB/s | zstd l1 compr. MiB/s | zstd l1 decompr. | Chunk Verify MiB/s | AES256GCM MiB/s | Sum MiB/s | Efficiency Score | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | Intel | Xeon E5-2620 v3 | amd64 | 2014/3 | 85 | 7.08 | 407.06 | 406.54 | 890.03 | 280.57 | 1870.60 | 3447.74 | 486.97 | | Intel | i9-9900K | amd64 | 2018/4 | 95 | 5.94 | 612.84 | 694.92 | 1518.13 | 438.38 | 4099.33 | 7363.6 | 1239.66 | | Intel | i9-10900X | amd64 | 2019/4 | 165 | 16.5 | 570.78 | 661.73 | 953.15 | 357.14 | 2106.38 | 4649.18 | 281.76 | | Intel | i7-12700K | amd64 | 2021/4 | 190 | 9.5 | 2442.16 | 891.44 | 1237.12 | 820.55 | 3235.00 | 8626.27 | 908.03 | | Intel | i3-1220P | amd64 | 2022/1 | 64 | 5.3 | 2047.1 | 728.86 | 1007.77 | 673.44 | 2544.34 | 7001.51 | 1321.04 | | Intel | Celeron J4105 | amd64 | 2017/4 | 10 | 2.5 | 615.88 | 221.56 | 526.61 | 279.93 | 945.39 | 2589.37 | 1035.75 | | Intel | Core 2 Duo E8500 | amd64 | 2008/1 | 65 | 32.5 | 239.43 | 315.91 | 632.83 | 175.24 | 121.06 | 1484.47 | 45.68 | | AMD | Ryzen 7 7900X | amd64 | 2022/3 | 230 | 9.58 | 2807.0 | 1173.26 | 1758.63 | 1081.55 | 3630.68 | 10451.12 | 1090.93 | | AMD | Ryzen 7 5800X | amd64 | 2020/4 | 142 | 8.87 | 2374.35 | 952.37 | 1893.54 | 930.41 | 4640.62 | 10791.29 | 1215.92 | | AMD | Ryzen 7 3700X | amd64 | 2019/3 | 95 | 5.93 | 2078.08 | 683.08 | 1384.11 | 836.79 | 3705.00 | 8687.06 | 1463.08 | | AMD | EPYC 7302P | amd64 | 2019/3 | 155 | 4.84 | 1624.23 | 539.71 | 1106.47 | 656.09 | 2978.71 | 6905.21 | 1426.70 | | BCM | 2711B0 Cortex-A72 | arm64 | 2015/2 | 10 | 2.5 | 142.41 | 123.64 | 300.87 | 95.29 | 23.46 | 685.67 | 274.27 | Efficiency score is calculated by dividing the sum of all benchmark result (unit `MiB/(s*core)` by the `W/Cores` metric, due to Watt being `J/s` this means the score has the unit of `MiB/Joule` and thus makes only sense when observed over time. Note that `Watt/Cores` was chosen as just comparing TDP makes one draw conclusions which will be wrong in real world - as the benchmark is mostly single core, and thus multicore systems look worse than they will in practice (where multiple backup jobs/verifications/GCs/... can run at the same time). PBS Client Build ---------------- | Vendor | CPU Model | Arch | Release Y/Q | Instructions # | Clock Cycles # | Avg. Instr./Cycle | Total Time s | | --- | --- | --- | --- | --- | --- | --- | --- | | Intel | Xeon E5-2620 v3 | amd64 | 2014/3 | 4,618,619,075,708 | 6,384,841,530,256 | 0.72 | 277.179347490 | | Intel | i9-9900K (in KVM) | amd64 | 2018/4 | 4,448,729,708,491 | 6,838,600,240,070 | 0.65 | 174.346811364 | | AMD | Ryzen 7 5800X | amd64 | 2020/4 | 4,384,063,783,832 | 5,229,554,881,150 | 0.84 | 116.030434890 | | BCM | 2711B0 Cortex-A72 | a**r**m64 | 2015/2 | 5,002,859,357,663 | 10,670,903,671,410 | 0.47 | 1920.615051800 | The quite modern Ryzen 7 5800X beats the Raspberry Pi 4's Cortex-A72 CPU by a factor of 16.5 (1655 % faster). For the PBS build more core help first, but at the end linking (which makes out a significant part of the total build time) is done in a single process, so one needs all three, high core count, high clock rate and high instructions per cycle rate to "win" here. Data ==== Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz ----------------------------------------- | | | | --- | --- | | Update date | 2021-03-05 | | PBS Version | 1.0.8 | | Linux Kernel | 5.4 | | Distro Version | Proxmox VE 6.3 | ### PBS Client Benchmark SHA256 speed: 407.06 MB/s Compression speed: 406.54 MB/s Decompress speed: 890.03 MB/s AES256/GCM speed: 1870.60 MB/s Verify speed: 280.57 MB/s ┌───────────────────────────────────┬────────────────────┐ │ Name │ Value │ ╞═══════════════════════════════════╪════════════════════╡ │ TLS (maximal backup upload speed) │ not tested │ ├───────────────────────────────────┼────────────────────┤ │ SHA256 checksum computation speed │ 407.06 MB/s (20%) │ ├───────────────────────────────────┼────────────────────┤ │ ZStd level 1 compression speed │ 406.54 MB/s (54%) │ ├───────────────────────────────────┼────────────────────┤ │ ZStd level 1 decompression speed │ 890.03 MB/s (74%) │ ├───────────────────────────────────┼────────────────────┤ │ Chunk verification speed │ 280.57 MB/s (37%) │ ├───────────────────────────────────┼────────────────────┤ │ AES256 GCM encryption speed │ 1870.60 MB/s (51%) │ └───────────────────────────────────┴────────────────────┘ ### PBS Client Build Performance counter stats for 'cargo build --release --bin proxmox-backup-client --bin pxar --bin dump-catalog-shell-cli': 2,445,836.61 msec task-clock # 8.824 CPUs utilized 515,060 context-switches # 0.211 K/sec 11,447 cpu-migrations # 0.005 K/sec 6,545,302 page-faults # 0.003 M/sec 6,384,841,530,256 cycles # 2.610 GHz 4,618,619,075,708 instructions # 0.72 insn per cycle 978,867,153,867 branches # 400.218 M/sec 39,652,439,215 branch-misses # 4.05% of all branches 277.179347490 seconds time elapsed 2406.400671000 seconds user 40.862553000 seconds sys Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ---------------------------------------- | | | | --- | --- | | Update date | 2021-03-05 | | PBS Version | 1.0.8 | | Linux Kernel | 5.4 | | Distro Version | Proxmox VE 6.3 | ### PBS Client Build Performance counter stats for 'cargo build --release --bin proxmox-backup-client --bin pxar --bin dump-catalog-shell-cli': 1,695,478.27 msec task-clock # 9.725 CPUs utilized 197,471 context-switches # 0.116 K/sec 18,272 cpu-migrations # 0.011 K/sec 6,382,947 page-faults # 0.004 M/sec 6,838,600,240,070 cycles # 4.033 GHz 4,448,729,708,491 instructions # 0.65 insn per cycle 943,595,955,517 branches # 556.537 M/sec 35,189,700,299 branch-misses # 3.73% of all branches 174.346811364 seconds time elapsed 1662.116788000 seconds user 39.862990000 seconds sys ### PBS Client Benchmark SHA256 speed: 612.84 MB/s Compression speed: 694.92 MB/s Decompress speed: 1518.13 MB/s AES256/GCM speed: 4099.33 MB/s Verify speed: 438.38 MB/s ┌───────────────────────────────────┬─────────────────────┐ │ Name │ Value │ ╞═══════════════════════════════════╪═════════════════════╡ │ TLS (maximal backup upload speed) │ not tested │ ├───────────────────────────────────┼─────────────────────┤ │ SHA256 checksum computation speed │ 612.84 MB/s (30%) │ ├───────────────────────────────────┼─────────────────────┤ │ ZStd level 1 compression speed │ 694.92 MB/s (92%) │ ├───────────────────────────────────┼─────────────────────┤ │ ZStd level 1 decompression speed │ 1518.13 MB/s (127%) │ ├───────────────────────────────────┼─────────────────────┤ │ Chunk verification speed │ 438.38 MB/s (58%) │ ├───────────────────────────────────┼─────────────────────┤ │ AES256 GCM encryption speed │ 4099.33 MB/s (112%) │ └───────────────────────────────────┴─────────────────────┘ Intel(R) Celeron(TM) J4105 CPU @ 1.50GHz ---------------------------------------- | | | | --- | --- | | Update date | 2021-03-05 | | PBS Version | 1.0.8 | | Linux Kernel | 5.4 | | Distro Version | Proxmox VE 6.3 | ### PBS Client Benchmark SHA256 speed: 615.88 MB/s Compression speed: 221.56 MB/s Decompress speed: 526.61 MB/s AES256/GCM speed: 945.39 MB/s Verify speed: 279.93 MB/s ┌───────────────────────────────────┬───────────────────┐ │ Name │ Value │ ╞═══════════════════════════════════╪═══════════════════╡ │ TLS (maximal backup upload speed) │ not tested │ ├───────────────────────────────────┼───────────────────┤ │ SHA256 checksum computation speed │ 615.88 MB/s (30%) │ ├───────────────────────────────────┼───────────────────┤ │ ZStd level 1 compression speed │ 221.56 MB/s (29%) │ ├───────────────────────────────────┼───────────────────┤ │ ZStd level 1 decompression speed │ 526.61 MB/s (44%) │ ├───────────────────────────────────┼───────────────────┤ │ Chunk verification speed │ 279.93 MB/s (37%) │ ├───────────────────────────────────┼───────────────────┤ │ AES256 GCM encryption speed │ 945.39 MB/s (26%) │ └───────────────────────────────────┴───────────────────┘ Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz ------------------------------------------ | | | | --- | --- | | Update date | 2021-03-23 | | PBS Version | 1.0.11 | | Linux Kernel | 5.4 | | Distro Version | Proxmox VE 6.3 | ### PBS Client Benchmark SHA256 speed: 239.43 MB/s Compression speed: 315.91 MB/s Decompress speed: 632.83 MB/s AES256/GCM speed: 121.06 MB/s Verify speed: 175.24 MB/s ┌───────────────────────────────────┬───────────────────┐ │ Name │ Value │ ╞═══════════════════════════════════╪═══════════════════╡ │ TLS (maximal backup upload speed) │ not tested │ ├───────────────────────────────────┼───────────────────┤ │ SHA256 checksum computation speed │ 239.43 MB/s (12%) │ ├───────────────────────────────────┼───────────────────┤ │ ZStd level 1 compression speed │ 315.91 MB/s (42%) │ ├───────────────────────────────────┼───────────────────┤ │ ZStd level 1 decompression speed │ 632.83 MB/s (53%) │ ├───────────────────────────────────┼───────────────────┤ │ Chunk verification speed │ 175.24 MB/s (23%) │ ├───────────────────────────────────┼───────────────────┤ │ AES256 GCM encryption speed │ 121.06 MB/s (3%) │ └───────────────────────────────────┴───────────────────┘ AMD Ryzen 7 5800x 8-Core Processor ---------------------------------- | | | | --- | --- | | Update date | 2021-03-05 | | PBS Version | 1.0.8 | | Linux Kernel | 5.10 | | Distro Version | Debian Sid (2020-03) | ### PBS Client Build Performance counter stats for 'cargo build --release --bin proxmox-backup-client --bin pxar --bin dump-catalog-shell-cli': 1,160,289.16 msec task-clock # 10.000 CPUs utilized 166,631 context-switches # 0.144 K/sec 10,292 cpu-migrations # 0.009 K/sec 6,427,491 page-faults # 0.006 M/sec 5,229,554,881,150 cycles # 4.507 GHz (2.18%) 13,378,977,812 stalled-cycles-frontend # 0.26% frontend cycles idle (2.19%) 187,718,252,978 stalled-cycles-backend # 3.59% backend cycles idle (2.18%) 4,384,063,783,832 instructions # 0.84 insn per cycle # 0.04 stalled cycles per insn (2.18%) 882,521,754,530 branches # 760.605 M/sec (2.18%) 37,025,573,266 branch-misses # 4.20% of all branches (2.16%) 1,720,800,625,889 L1-dcache-loads # 1483.079 M/sec (2.17%) 92,596,728,614 L1-dcache-load-misses # 5.38% of all L1-dcache accesses (2.19%) LLC-loads LLC-load-misses 116.030434890 seconds time elapsed 1141.607730000 seconds user ### PBS Client Benchmark SHA256 speed: 2374.35 MB/s Compression speed: 952.37 MB/s Decompress speed: 1893.54 MB/s AES256/GCM speed: 4640.62 MB/s Verify speed: 930.41 MB/s AMD Ryzen 7 3700X 8-Core Processor ---------------------------------- | | | | --- | --- | | Update date | 2021-03-05 | | PBS Version | 1.0.8 | | Linux Kernel | 5.4 | | Distro Version | Proxmox VE 6.3 | ### PBS Client Benchmark proxmox-backup-client benchmark SHA256 speed: 2078.08 MB/s Compression speed: 683.08 MB/s Decompress speed: 1384.11 MB/s AES256/GCM speed: 3705.00 MB/s Verify speed: 836.79 MB/s ┌───────────────────────────────────┬─────────────────────┐ │ Name │ Value │ ╞═══════════════════════════════════╪═════════════════════╡ │ TLS (maximal backup upload speed) │ not tested │ ├───────────────────────────────────┼─────────────────────┤ │ SHA256 checksum computation speed │ 2078.08 MB/s (103%) │ ├───────────────────────────────────┼─────────────────────┤ │ ZStd level 1 compression speed │ 683.08 MB/s (91%) │ ├───────────────────────────────────┼─────────────────────┤ │ ZStd level 1 decompression speed │ 1384.11 MB/s (116%) │ ├───────────────────────────────────┼─────────────────────┤ │ Chunk verification speed │ 836.79 MB/s (110%) │ ├───────────────────────────────────┼─────────────────────┤ │ AES256 GCM encryption speed │ 3705.00 MB/s (102%) │ └───────────────────────────────────┴─────────────────────┘ AMD EPYC 7302P 16-Core Processor -------------------------------- | | | | --- | --- | | Update date | 2021-03-05 | | PBS Version | 1.0.8 | | Linux Kernel | 5.4 | | Distro Version | Proxmox VE 6.3 | ### PBS Client Benchmark SHA256 speed: 1624.23 MB/s Compression speed: 539.71 MB/s Decompress speed: 1106.47 MB/s AES256/GCM speed: 2978.71 MB/s Verify speed: 656.09 MB/s ┌───────────────────────────────────┬────────────────────┐ │ Name │ Value │ ╞═══════════════════════════════════╪════════════════════╡ │ TLS (maximal backup upload speed) │ not tested │ ├───────────────────────────────────┼────────────────────┤ │ SHA256 checksum computation speed │ 1624.23 MB/s (80%) │ ├───────────────────────────────────┼────────────────────┤ │ ZStd level 1 compression speed │ 539.71 MB/s (72%) │ ├───────────────────────────────────┼────────────────────┤ │ ZStd level 1 decompression speed │ 1106.47 MB/s (92%) │ ├───────────────────────────────────┼────────────────────┤ │ Chunk verification speed │ 656.09 MB/s (87%) │ ├───────────────────────────────────┼────────────────────┤ │ AES256 GCM encryption speed │ 2978.71 MB/s (82%) │ └───────────────────────────────────┴────────────────────┘ ARM64 Cortex-A72 - Raspberry Pi 4 --------------------------------- | | | | --- | --- | | Update date | 2021-03-05 | | PBS Version | 1.0.8 | | Linux Kernel | 5.8 | | Distro Version | Ubuntu Server 20.10 | ### PBS Client Build Performance counter stats for 'cargo build --release --bin proxmox-backup-client --bin pxar --bin dump-catalog-shell-cli': 7,116,962.15 msec task-clock # 3.706 CPUs utilized 349,207 context-switches # 0.049 K/sec 5,272 cpu-migrations # 0.001 K/sec 6,070,961 page-faults # 0.853 K/sec 10,670,903,671,410 cycles # 1.499 GHz 5,002,859,357,663 instructions # 0.47 insn per cycle branches 56,010,658,667 branch-misses 1920.615051800 seconds time elapsed 7000.438300000 seconds user 112.304292000 seconds sys ### PBS Client Benchmark SHA256 speed: 142.41 MB/s Compression speed: 123.64 MB/s Decompress speed: 300.87 MB/s AES256/GCM speed: 23.46 MB/s Verify speed: 95.29 MB/s ┌───────────────────────────────────┬───────────────────┐ │ Name │ Value │ ╞═══════════════════════════════════╪═══════════════════╡ │ TLS (maximal backup upload speed) │ not tested │ ├───────────────────────────────────┼───────────────────┤ │ SHA256 checksum computation speed │ 142.41 MB/s (7%) │ ├───────────────────────────────────┼───────────────────┤ │ ZStd level 1 compression speed │ 123.64 MB/s (16%) │ ├───────────────────────────────────┼───────────────────┤ │ ZStd level 1 decompression speed │ 300.87 MB/s (25%) │ ├───────────────────────────────────┼───────────────────┤ │ Chunk verification speed │ 95.29 MB/s (13%) │ ├───────────────────────────────────┼───────────────────┤ │ AES256 GCM encryption speed │ 23.46 MB/s (1%) │ └───────────────────────────────────┴───────────────────┘ Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=PBS\_Client\_CPU\_Benchmark&oldid=11575](https://pve.proxmox.com/mediawiki/index.php?title=PBS_Client_CPU_Benchmark&oldid=11575) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Dell blade servers" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Dell blade servers" ======================================= ← [Dell blade servers](https://pve.proxmox.com/mediawiki/index.php?title=Dell_blade_servers&action=edit&redlink=1 "Dell blade servers (page does not exist)") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Dell_blade_servers#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Dell_blade_servers#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Dell blade servers](https://pve.proxmox.com/mediawiki/index.php?title=Dell_blade_servers&action=edit&redlink=1 "Dell blade servers (page does not exist)") **: Displaying 1 item. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Dell_blade_servers&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Dell_blade_servers&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Dell_blade_servers&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Dell_blade_servers&limit=500) ) * [Fencing](https://pve.proxmox.com/wiki/Fencing "Fencing") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Fencing "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Dell_blade_servers&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Dell_blade_servers&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Dell_blade_servers&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Dell_blade_servers&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Dell\_blade\_servers](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Dell_blade_servers) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Template:Warning - Proxmox VE Template:Warning ================ From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Template:Warning#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Template:Warning#searchInput) This template is used to mark some issues in the text. **Warning**: {{{1}}} Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Template:Warning&oldid=12392](https://pve.proxmox.com/mediawiki/index.php?title=Template:Warning&oldid=12392) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Template:Note - Proxmox VE Template:Note ============= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Template:Note#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Template:Note#searchInput) This template is used to visually mark out some important note in the text. ℹ️ **Note**: {{{1}}} Usage ----- Put the following code to your page: `{{Note|Some text.}}` The result will look like this: ℹ️ **Note**: Some text. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Template:Note&oldid=12391](https://pve.proxmox.com/mediawiki/index.php?title=Template:Note&oldid=12391) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # MxGPU with AMD S7150 under Proxmox VE 5.x - Proxmox VE MxGPU with AMD S7150 under Proxmox VE 5.x ========================================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#mw-head) [Jump to search](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#Introduction) * [2 Hardware Notes](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#Hardware_Notes) * [3 Host Configuration](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#Host_Configuration) * [4 Client Configuration](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#Client_Configuration) * [4.1 Windows 10](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#Windows_10) * [4.2 Ubuntu 18.04](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#Ubuntu_18.04) * [5 Notes](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#Notes) * [5.1 Stability](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#Stability) * [5.2 Debugging](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#Debugging) * [6 References](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#References) Introduction ------------ This is a Testing Report and How-To for using the MxGPU feature of an AMD S7150 Graphics card under PVE 5.x. These cards can provide hardware-accelerated 3D graphics to multiple VMs with a single card instead of using one card per VM (normal PCI passthrough) or using a software 3D graphics card (QXL/Spice). AMDs open source GIM driver[\[1\]](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#cite_note-gim-1) is needed on the host. **WARNING: Our tests showed that this may be unstable and experimental, please see the 'Notes' section below for more details.** Hardware Notes -------------- We tested the card in the following configurations: | Works | Hardware Type | Mainboard | CPU | Memory | Errors | Notes | | --- | --- | --- | --- | --- | --- | --- | | No | Consumer | ASUS Z170-A | Intel 6700k | 32GB DDR4 Memory | Loading GIM failed with a PCI Bus Error that it did not have sufficient resources. | The firmware of the Mainboard is not suited for this use. | | No | Low-end Server | Supermicro X10SDV-6C-TLN4F | Intel Xeon D-1528 | 32GB DDR4 Memory | PCI Bus Errors during use resulting in guest and host crashes. | The Platform is not suited for this use. | | Yes | High-end Server | Supermicro H11SSL-i | AMD Epyc 7351P 16-Core Processor | 64 GB DDR4 Memory | Linux guest instability | OPROM for this card has to be set to Legacy. | Host Configuration ------------------ Make sure that the 'amdgpu' module is blacklisted before installing the card. This can be done via a file in /etc/modprobe.d/. For example put blacklist amdgpu into /etc/modprobe.d/blacklist-amdgpu.conf Do not forget to update the initramfs[\[2\]](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#cite_note-initramfs-2) afterwards. After that, you have to compile and install GIM[\[1\]](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#cite_note-gim-1) . For this, you need at least the packages 'git', 'pve-headers', 'gcc' and 'make'. See their documentation about how you can compile and configure the module. You can install the module via DKMS[\[3\]](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#cite_note-3) (dynamic kernel module support), then the module gets automatically recompiled on every kernel upgrade. After installing the module, you can do modprobe gim and now you should see the virtual functions via 'lspci'. Example output: ... 41:00.0 VGA compatible controller: Advanced Micro Devices, Inc. \[AMD/ATI\] TongaXT GL \[FirePro S7150\] 41:02.0 VGA compatible controller: Advanced Micro Devices, Inc. \[AMD/ATI\] TongaXTV GL \[FirePro S7150V\] 41:02.1 VGA compatible controller: Advanced Micro Devices, Inc. \[AMD/ATI\] TongaXTV GL \[FirePro S7150V\] ... Those Devices (FirePro S7150V) can now be passed through via the standard PCI passthrough mechanism[\[4\]](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#cite_note-passthrough-4) . Client Configuration -------------------- ### Windows 10 Create a new VM, pass through a Virtual GPU, and install Windows 10. After that, enable Remote Desktop and install the Radeon Pro Drivers[\[5\]](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#cite_note-drivers-5) . After a reboot of the VM, you can now connect via Remote Desktop to the VM and use the graphics card. * [![Rendering with OpenCL in Blender in Windows 10](https://pve.proxmox.com/mediawiki/images/thumb/2/29/Windows_10_Blender.png/240px-Windows_10_Blender.png)](https://pve.proxmox.com/wiki/File:Windows_10_Blender.png "Rendering with OpenCL in Blender in Windows 10") Rendering with OpenCL in Blender in Windows 10 * [![Running Unigine Valley Benchmark in Windows 10](https://pve.proxmox.com/mediawiki/images/thumb/2/2b/Windows_10_Unigine_Valley.png/240px-Windows_10_Unigine_Valley.png)](https://pve.proxmox.com/wiki/File:Windows_10_Unigine_Valley.png "Running Unigine Valley Benchmark in Windows 10") Running Unigine Valley Benchmark in Windows 10 ### Ubuntu 18.04 Create a new VM without passing through the Virtual GPU yet, and install Ubuntu 18.04. After that, install the amdgpu-pro driver from AMDs homepage[\[5\]](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#cite_note-drivers-5) . While testing, we found that the AMDGPU Pro driver Version 18.40[\[6\]](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#cite_note-6) works most of the time. (18.30 did load but produced many guest kernel errors and prevented the use of it; 18.50 resulted in guest kernel oopses). Install a desktop environment (for example XFCE with the meta-package xubuntu-desktop) and a display manager (for instance lightdm). Install a VNC Server[\[7\]](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#cite_note-7) (or similar) to be able to access a local X server and configure it to start automatically. Now power off the VM, add the virtual function and start the VM again. Note: Depending on the exact guest kernel and driver version, there may be some kernel errors and warning even if it is working. At this point, you should be able to connect via VNC (or another protocol) and use the virtual GPU. * [![Unigine Valley on Ubuntu 18.04](https://pve.proxmox.com/mediawiki/images/thumb/5/53/Valley_ubuntu_18.04.png/240px-Valley_ubuntu_18.04.png)](https://pve.proxmox.com/wiki/File:Valley_ubuntu_18.04.png "Unigine Valley on Ubuntu 18.04") Unigine Valley on Ubuntu 18.04 * [![Super Tux Kart on Ubuntu 18.04](https://pve.proxmox.com/mediawiki/images/thumb/a/ae/Ubuntu_supertuxkart.png/240px-Ubuntu_supertuxkart.png)](https://pve.proxmox.com/wiki/File:Ubuntu_supertuxkart.png "Super Tux Kart on Ubuntu 18.04") Super Tux Kart on Ubuntu 18.04 Notes ----- ### Stability In our tests the Linux guest drivers were very unstable. It worked with a single Ubuntu guest, but led to chrashes/hangs (of the guests and the host) after another guest was started, regardless of the client OS of the other guests. The Windows guest drivers worked more stable, but there were occasional resets/crashes and sometimes blue screens in the guest after starting multiple Windows guests, this only occurred when at least one Linux guest was started since boot, so only starting and using Windows guests should work. (The relevant bug report is here: [https://github.com/GPUOpen-LibrariesAndSDKs/MxGPU-Virtualization/issues/16](https://github.com/GPUOpen-LibrariesAndSDKs/MxGPU-Virtualization/issues/16) ) ### Debugging For debugging purposes, AMD includes the useful tool 'GRU' with the sources of GIM[\[1\]](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#cite_note-gim-1) . This is found in the 'utils/gru' folder and can simply be built with 'make'. You can use this Tool to see which functions are in use and how much resources are used. Also, it provides a mechanism to reset the card and its functions. Here is an example output: GRU Copyright (C) 2017~2018 Advanced Micro Devices, Inc. Type 'help' for help. Optional launch parameter is index of card to use. GRU> status +-----+--------------+----------+------------+-----------+--------------------+ | GPU | Name | Cur Volt | GFX EngClk | Mem Usage | Current DPM Level | | | BusId | Temp | Avail VF | GFX Usage | Power Usage | +=====+==============+==========+============+===========+====================+ | 0 | S7150 | 0.5750 V | 313.10 MHz | 49.79 % | 1 | | | 0000:41:00.0 | 57.00 C | 2 | 45.17 % | 33.37 W | +-----+--------------+----------+------------+-----------+--------------------+ GRU> list +-----+--------------+---------+------------+--------+------------+-----------+ | GPU | Name | DPM Cap | FB Size | Max VF | GFX Engine | PL Speed | | | BusId | PWR Cap | Encoder | ECC | MAX Clock | PL Width | +=====+==============+=========+============+========+============+===========+ | 0 | S7150 | 8 | 8190 M | 4 | GFX8 | 8 GT/s | | | 0000:41:00.0 | 109 W | None | No | 1000 MHz | x16 | +-----+--------------+---------+------------+--------+------------+-----------+ GRU> open 0000:41:00.0 GRU>GPU:41:00.0> list +----+--------+--------------+------------+-----------+---------+-------------+ | VF | Type | BusId | Name | VF State | VF Size | GFX EngPart | +====+========+==============+============+===========+=========+=============+ | 0 | S7150 | 0000:41:02.0 | MxGPU\_V1\_4 | Active | 1968 M | 25% | +----+--------+--------------+------------+-----------+---------+-------------+ | 1 | S7150 | 0000:41:02.1 | MxGPU\_V1\_4 | Active | 1968 M | 25% | +----+--------+--------------+------------+-----------+---------+-------------+ | 2 | S7150 | 0000:41:02.2 | MxGPU\_V1\_4 | Available | 1968 M | 25% | +----+--------+--------------+------------+-----------+---------+-------------+ | 3 | S7150 | 0000:41:02.3 | MxGPU\_V1\_4 | Available | 1968 M | 25% | +----+--------+--------------+------------+-----------+---------+-------------+ GRU>GPU:41:00.0> status +----+-------------+--------------+--------------+--------------+-------------+ | VF | Type | BusId | Active Time | Running Time | Reset Times | +====+=============+==============+==============+==============+=============+ | 0 | S7150 | 0000:41:02.0 | 0:41:48 | 0:59:29 | 0 | +----+-------------+--------------+--------------+--------------+-------------+ | 1 | S7150 | 0000:41:02.1 | 0:14:13 | 0:31:50 | 0 | +----+-------------+--------------+--------------+--------------+-------------+ | 2 | S7150 | 0000:41:02.2 | 0:0:0 | 0:0:0 | 0 | +----+-------------+--------------+--------------+--------------+-------------+ | 3 | S7150 | 0000:41:02.3 | 0:0:0 | 0:0:0 | 0 | +----+-------------+--------------+--------------+--------------+-------------+ GRU>GPU:41:00.0> References ---------- 1. ↑ [1.0](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#cite_ref-gim_1-0) [1.1](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#cite_ref-gim_1-1) [1.2](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#cite_ref-gim_1-2) GIM Open Source Driver. [https://github.com/GPUOpen-LibrariesAndSDKs/MxGPU-Virtualization](https://github.com/GPUOpen-LibrariesAndSDKs/MxGPU-Virtualization) 2. [↑](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#cite_ref-initramfs_2-0) [https://pve.proxmox.com/pve-docs/chapter-qm.html#qm\_pci\_passthrough\_update\_initramfs](https://pve.proxmox.com/pve-docs/chapter-qm.html#qm_pci_passthrough_update_initramfs) 3. [↑](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#cite_ref-3) Debian DKMS documentation. [https://wiki.debian.org/KernelDKMS](https://wiki.debian.org/KernelDKMS) 4. [↑](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#cite_ref-passthrough_4-0) PCI Passthrough Documentation [https://pve.proxmox.com/pve-docs/chapter-qm.html#qm\_pci\_passthrough](https://pve.proxmox.com/pve-docs/chapter-qm.html#qm_pci_passthrough) 5. ↑ [5.0](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#cite_ref-drivers_5-0) [5.1](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#cite_ref-drivers_5-1) AMD Radeon Pro Drivers for S7150 [https://www.amd.com/en/support/professional-graphics/firepro/firepro-s-series/firepro-s7150-active-cooling](https://www.amd.com/en/support/professional-graphics/firepro/firepro-s-series/firepro-s7150-active-cooling) 6. [↑](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#cite_ref-6) AMDGPU Pro Driver 18.40. [https://www.amd.com/en/support/kb/release-notes/rn-prorad-lin-18-40](https://www.amd.com/en/support/kb/release-notes/rn-prorad-lin-18-40) 7. [↑](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x#cite_ref-7) [https://help.ubuntu.com/community/VNC/Servers](https://help.ubuntu.com/community/VNC/Servers) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=MxGPU\_with\_AMD\_S7150\_under\_Proxmox\_VE\_5.x&oldid=10244](https://pve.proxmox.com/mediawiki/index.php?title=MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x&oldid=10244) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Qemu/KVM](https://pve.proxmox.com/wiki/Category:Qemu/KVM "Category:Qemu/KVM") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Windows NT Guest Notes - Proxmox VE Windows NT Guest Notes ====================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Windows_NT_Guest_Notes#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Windows_NT_Guest_Notes#searchInput) Contents -------- * [1 Mouse](https://pve.proxmox.com/wiki/Windows_NT_Guest_Notes#Mouse) * [2 Network](https://pve.proxmox.com/wiki/Windows_NT_Guest_Notes#Network) * [2.1 Network drivers tested working](https://pve.proxmox.com/wiki/Windows_NT_Guest_Notes#Network_drivers_tested_working) * [3 Video Issues](https://pve.proxmox.com/wiki/Windows_NT_Guest_Notes#Video_Issues) Mouse ----- Mouse inside NT4 works, but often acts weird: * sometimes mouse movements are amplified * workaround: try to reach control panel > mouse, and reduce cursor acceleration & such... * sometimes mouse movements go crazy, pointer jumps all ov er the screen, buttons presses (never done), all kind of crazy things... * a reboot usually reset "normal" behaviour (until next time...) * seems to be this kind of thing [http://www.ilande.co.uk/index.php?/archives/7-Migrating-an-NT4-VM-from-VMWare-to-NT4-Part-2.html](http://www.ilande.co.uk/index.php?/archives/7-Migrating-an-NT4-VM-from-VMWare-to-NT4-Part-2.html) Network ------- ### Network drivers tested working * Realtek RTL8139: [http://support.lenovo.com/en\_US/downloads/detail.page?DocID=DS003083](http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS003083) Video Issues ------------ After using [Clonezilla](http://clonezilla.org/) to migrate an NT4 SP6a Workstation to a KVM container, the video driver was incorrect. The VM defaulted to the standard VGA driver @ 16 colors and 640x480. To resolve this issue, I downloaded and installed the latest version (2010.07.09) of the [VBEMP](http://www.navozhdeniye.narod.ru/vbemp.htm) driver inside the VM and rebooted. The NT4 VM didn't have network access or a floppy, so I had to boot the NT4 VHD on a Win2K VM located on the same PVE server in order to copy the driver zip file. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Windows\_NT\_Guest\_Notes&oldid=9145](https://pve.proxmox.com/mediawiki/index.php?title=Windows_NT_Guest_Notes&oldid=9145) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Qemu/KVM](https://pve.proxmox.com/wiki/Category:Qemu/KVM "Category:Qemu/KVM") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # File:Svn-export.tar.gz - Proxmox VE File:Svn-export.tar.gz ====================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/File:Svn-export.tar.gz#mw-head) [Jump to search](https://pve.proxmox.com/wiki/File:Svn-export.tar.gz#searchInput) * [File](https://pve.proxmox.com/wiki/File:Svn-export.tar.gz#file) * [File history](https://pve.proxmox.com/wiki/File:Svn-export.tar.gz#filehistory) * [File usage](https://pve.proxmox.com/wiki/File:Svn-export.tar.gz#filelinks) [Svn-export.tar.gz](https://pve.proxmox.com/mediawiki/images/a/a4/Svn-export.tar.gz "Svn-export.tar.gz") (file size: 1,016 bytes, MIME type: unknown/unknown) **Warning:** This file type may contain malicious code. By executing it, your system may be compromised. Bash script to download the changed files between SVN versions. File history ------------ Click on a date/time to view the file as it appeared at that time. | | Date/Time | Dimensions | User | Comment | | --- | --- | --- | --- | --- | | current | [10:11, 28 January 2011](https://pve.proxmox.com/mediawiki/images/a/a4/Svn-export.tar.gz) | (1,016 bytes) | [Apmuthu](https://pve.proxmox.com/wiki/User:Apmuthu "User:Apmuthu")
([talk](https://pve.proxmox.com/wiki/User_talk:Apmuthu "User talk:Apmuthu")
\| [contribs](https://pve.proxmox.com/wiki/Special:Contributions/Apmuthu "Special:Contributions/Apmuthu")
) | Bash script to download the changed files between SVN versions. | You cannot overwrite this file. File usage ---------- There are no pages that use this file. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=File:Svn-export.tar.gz&oldid=2744](https://pve.proxmox.com/mediawiki/index.php?title=File:Svn-export.tar.gz&oldid=2744) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Command line tools - PVE 3.x - Proxmox VE Command line tools - PVE 3.x ============================ From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#searchInput) ℹ️ **Note**: This article is about the previous Proxmox VE 3.x releases Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#Introduction) * [2 KVM specific](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#KVM_specific) * [2.1 qm](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#qm) * [3 OpenVZ specific](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#OpenVZ_specific) * [3.1 vzps](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#vzps) * [3.2 pvectl](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#pvectl) * [3.3 vzctl](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#vzctl) * [3.4 vztop](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#vztop) * [3.5 user\_beancounters](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#user_beancounters) * [3.6 vzlist](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#vzlist) * [4 Backup](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#Backup) * [4.1 vzdump](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#vzdump) * [4.2 vzrestore](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#vzrestore) * [4.3 qmrestore](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#qmrestore) * [5 Cluster management](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#Cluster_management) * [5.1 pvecm](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#pvecm) * [6 Software version check](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#Software_version_check) * [6.1 pveversion](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#pveversion) * [6.1.1 USAGE](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#USAGE) * [7 LVM](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#LVM) * [7.1 USAGE](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#USAGE_2) * [8 Debian Appliance Builder](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#Debian_Appliance_Builder) * [8.1 dab](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#dab) * [9 Other useful tools](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#Other_useful_tools) * [9.1 pveperf](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#pveperf) * [9.1.1 Example output](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#Example_output) * [9.2 pvesubscription](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#pvesubscription) * [9.3 Third party CLI Tools](https://pve.proxmox.com/wiki/Command_line_tools_-_PVE_3.x#Third_party_CLI_Tools) Introduction ------------ This page lists some important Proxmox VE 3x and Debian command line tools. KVM specific ------------ ### qm To view a list of KVMs: qm list VMID NAME STATUS MEM(MB) BOOTDISK(GB) PID 100 alpha001 running 2048 8.00 5858 101 WINXP002 running 1024 32.00 6177 102 Win2K running 2048 32.00 113893 105 axe002 running 16384 100.00 279613 To see how much memory your machine 101 has: qm config 101 | grep ^memory memory: 2048 see "man qm" for further info QEMU Emulator: [User Documentation](http://wiki.qemu.org/download/qemu-doc.html#QEMU-PC-System-emulator) | [Monitor Commands](https://en.wikibooks.org/wiki/QEMU/Monitor) OpenVZ specific --------------- ### vzps This utility program can be run on the Node just as the standard Linux ps. For information on the ps utility please consult the corresponding man page, vzps provides certain additional functionality related to monitoring separate Containers running on the Node. The vzps utility has the following functionality added: * The -E CT\_ID command line switch can be used to show only the processes running inside the Container with the specified ID. ### pvectl pvectl - vzctl wrapper to manage OpenVZ containers - see "man pvectl" ### vzctl vzctl - utility to control an OpenVZ container - see "man vzctl" ### vztop This utility program can be run on the Node just as the standard Linux top . For information on the top utility please consult the corresponding man page, vztop provides certain additional functionality related to monitoring separate Containers running on the Node. The vztop utility has the following functionality added: * The -E CT\_ID command line switch can be used to show only the processes running inside the Container with the ID specified. If -1 is specified as CT\_ID, the processes of all running Containers are displayed. * The e interactive command (the key pressed while top is running) can be used to show/hide the CTID column, which displays the Container where a particular process is running (0 stands for the Hardware Node itself). * The E interactive command can be used to select another Container the processes of which are to be shown. If -1 is specified, the processes of all running Containers are displayed. vztop - display top CPU processes 10:28:52 up 31 days, 11:18, 1 user, load average: 0.07, 0.06, 0.02 197 processes: 196 sleeping, 1 running, 0 zombie, 0 stopped CPU0 states: 0.2% user 0.1% system 0.0% nice 0.0% iowait 99.2% idle CPU1 states: 1.3% user 2.1% system 0.0% nice 0.0% iowait 96.1% idle CPU2 states: 6.3% user 0.1% system 0.0% nice 0.0% iowait 93.1% idle CPU3 states: 2.0% user 1.0% system 0.0% nice 0.0% iowait 96.4% idle Mem: 16251688k av, 16032764k used, 218924k free, 0k shrd, 364120k buff 4448576k active, 10983652k inactive Swap: 15728632k av, 36k used, 15728596k free 14170784k cached PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 390694 root 20 0 759M 528M 2432 S 6.7 3.3 244:53 1 kvm 566767 root 20 0 40464 8908 5320 S 6.7 0.0 0:54 0 apache2 7898 root 20 0 181M 34M 4076 S 0.3 0.2 73:12 2 pvestatd 1 root 20 0 10604 848 744 S 0.0 0.0 0:16 0 init 2 root 20 0 0 0 0 SW 0.0 0.0 0:00 2 kthreadd 3 root RT 0 0 0 0 SW 0.0 0.0 0:00 0 migration/0 4 root 20 0 0 0 0 SW 0.0 0.0 0:19 0 ksoftirqd/0 5 root RT 0 0 0 0 SW 0.0 0.0 0:00 0 migration/0 6 root RT 0 0 0 0 SW 0.0 0.0 0:02 0 watchdog/0 7 root RT 0 0 0 0 SW 0.0 0.0 0:00 1 migration/1 8 root RT 0 0 0 0 SW 0.0 0.0 0:00 1 migration/1 9 root 20 0 0 0 0 SW 0.0 0.0 0:24 1 ksoftirqd/1 10 root RT 0 0 0 0 SW 0.0 0.0 0:01 1 watchdog/1 11 root RT 0 0 0 0 SW 0.0 0.0 0:01 2 migration/2 12 root RT 0 0 0 0 SW 0.0 0.0 0:00 2 migration/2 13 root 20 0 0 0 0 SW 0.0 0.0 0:12 2 ksoftirqd/2 14 root RT 0 0 0 0 SW 0.0 0.0 0:01 2 watchdog/2 15 root RT 0 0 0 0 SW 0.0 0.0 0:07 3 migration/3 .. .. ### user\_beancounters cat /proc/user\_beancounters Version: 2.5 uid resource held maxheld barrier limit failcnt 101: kmemsize 11217945 16650240 243269632 268435456 0 lockedpages 0 418 65536 65536 0 privvmpages 134161 221093 9223372036854775807 9223372036854775807 0 shmpages 16 3232 9223372036854775807 9223372036854775807 0 dummy 0 0 0 0 0 numproc 56 99 9223372036854775807 9223372036854775807 0 physpages 96245 122946 0 131072 0 vmguarpages 0 0 0 9223372036854775807 0 oomguarpages 53689 78279 0 9223372036854775807 0 numtcpsock 49 82 9223372036854775807 9223372036854775807 0 numflock 8 20 9223372036854775807 9223372036854775807 0 numpty 0 6 9223372036854775807 9223372036854775807 0 numsiginfo 0 33 9223372036854775807 9223372036854775807 0 tcpsndbuf 927856 1619344 9223372036854775807 9223372036854775807 0 tcprcvbuf 802816 1343488 9223372036854775807 9223372036854775807 0 othersockbuf 152592 481248 9223372036854775807 9223372036854775807 0 dgramrcvbuf 0 4624 9223372036854775807 9223372036854775807 0 numothersock 124 152 9223372036854775807 9223372036854775807 0 dcachesize 6032652 12378728 121634816 134217728 0 numfile 629 915 9223372036854775807 9223372036854775807 0 dummy 0 0 0 0 0 dummy 0 0 0 0 0 dummy 0 0 0 0 0 numiptent 20 20 9223372036854775807 9223372036854775807 0 0: kmemsize 34634728 65306624 9223372036854775807 9223372036854775807 0 lockedpages 1360 6721 9223372036854775807 9223372036854775807 0 privvmpages 317475 507560 9223372036854775807 9223372036854775807 0 shmpages 4738 9645 9223372036854775807 9223372036854775807 0 dummy 0 0 9223372036854775807 9223372036854775807 0 numproc 190 220 9223372036854775807 9223372036854775807 0 physpages 3769163 3867750 9223372036854775807 9223372036854775807 0 vmguarpages 0 0 0 0 0 oomguarpages 182160 205746 9223372036854775807 9223372036854775807 0 numtcpsock 12 29 9223372036854775807 9223372036854775807 0 numflock 9 13 9223372036854775807 9223372036854775807 0 numpty 4 12 9223372036854775807 9223372036854775807 0 numsiginfo 3 84 9223372036854775807 9223372036854775807 0 tcpsndbuf 249512 1760544 9223372036854775807 9223372036854775807 0 tcprcvbuf 198920 1142000 9223372036854775807 9223372036854775807 0 othersockbuf 233512 276832 9223372036854775807 9223372036854775807 0 dgramrcvbuf 0 2576 9223372036854775807 9223372036854775807 0 numothersock 179 193 9223372036854775807 9223372036854775807 0 dcachesize 18688898 47058779 9223372036854775807 9223372036854775807 0 numfile 1141 1410 9223372036854775807 9223372036854775807 0 dummy 0 0 9223372036854775807 9223372036854775807 0 dummy 0 0 9223372036854775807 9223372036854775807 0 dummy 0 0 9223372036854775807 9223372036854775807 0 numiptent 20 20 9223372036854775807 9223372036854775807 0 ### vzlist vzlist CTID NPROC STATUS IP\_ADDR HOSTNAME 101 26 running - localhost 102 121 running 10.100.100.18 mediawiki 114 49 running - fbc14 * The fields for (**\-o** option) selective display are: **ctid, nproc, status, ip, hostname**. * All are case sensitive and are used with the options **\-H** (no header) and **\-o** \[field1, field2, ...\] * The binary is at: /usr/sbin/vzlist * by default, vzlist lists only RUNNING CTs, stopped ones won't appear in its output (qm list for VMs, instead, lists also stopped ones) See "man vzlist" for detailled options. Backup ------ ### vzdump vzdump - backup utility for virtual machine - see "man vzdump" ### vzrestore vzrestore - restore OpenVZ vzdump backups - see "man vzrestore" ### qmrestore qmrestore - restore KVM vzdump backups - see "man qmrestore" Cluster management ------------------ ### pvecm PVE Cluster Manager - see "man pvecm" for details. Software version check ---------------------- ### pveversion Proxmox VE version info - Print version information for Proxmox VE packages. #### USAGE pveversion \[--verbose\] * without any argument shows the version of pve-manager, something like: pve-manager/3.0/957f0862 * with -v argument it shows a list of programs versions related to pve, like: pve-manager: 3.0-23 (pve-manager/3.0/957f0862) running kernel: 2.6.32-20-pve proxmox-ve-2.6.32: 3.0-100 pve-kernel-2.6.32-20-pve: 2.6.32-100 lvm2: 2.02.95-pve3 clvm: 2.02.95-pve3 corosync-pve: 1.4.5-1 openais-pve: 1.1.4-3 libqb0: 0.11.1-2 redhat-cluster-pve: 3.2.0-2 resource-agents-pve: 3.9.2-4 fence-agents-pve: 4.0.0-1 pve-cluster: 3.0-4 qemu-server: 3.0-20 pve-firmware: 1.0-22 libpve-common-perl: 3.0-4 libpve-access-control: 3.0-4 libpve-storage-perl: 3.0-8 vncterm: 1.1-4 vzctl: 4.0-1pve3 vzprocps: 2.0.11-2 vzquota: 3.1-2 pve-qemu-kvm: 1.4-13 ksm-control-daemon: 1.1-1 LVM --- Most of the commands in LVM are very similar to each other. Each valid command is preceded by one of the following: * Physical Volume = pv * Volume Group = vg * Logical Volume = lv #### USAGE | | | | | | | --- | --- | --- | --- | --- | | | | **Physical Volume** | **Volume Group** | **Logical Volume** | | | **LVM** | **PV** | **VG** | **LV** | | s | No | Yes | Yes | Yes | | display | No | Yes | Yes | Yes | | create | No | Yes | Yes | Yes | | rename | No | No | Yes | Yes | | change | Yes | Yes | Yes | Yes | | move | No | Yes | Yes | No | | extend | No | No | Yes | Yes | | reduce | No | No | Yes | Yes | | resize | No | Yes | No | Yes | | split | No | No | Yes | No | | merge | No | No | Yes | No | | convert | No | No | Yes | Yes | | import | No | No | Yes | No | | export | No | No | Yes | No | | importclone | No | No | Yes | No | | cfgbackup | No | No | Yes | No | | cfgrestore | No | No | Yes | No | | ck | No | Yes | Yes | No | | scan | diskscan | Yes | Yes | Yes | | mknodes | No | No | Yes | No | | remove | No | Yes | Yes | Yes | | dump | Yes | No | No | No | Debian Appliance Builder ------------------------ ### dab See [Debian Appliance Builder](https://pve.proxmox.com/wiki/Debian_Appliance_Builder "Debian Appliance Builder") Other useful tools ------------------ ### pveperf Simple host performance test - see "man pveperf". Note: this command may require root privileges (or sudo) to run, otherwise you get an error after "HD SIZE" value, like: <> #### Example output CPU BOGOMIPS: 26341.80 REGEX/SECOND: 1554770 HD SIZE: 94.49 GB (/dev/mapper/pve-root) BUFFERED READS: 49.83 MB/sec AVERAGE SEEK TIME: 14.16 ms FSYNCS/SECOND: 1060.47 DNS EXT: 314.58 ms DNS INT: 236.94 ms (mypve.com) ### pvesubscription For managing a node's subscription key - see "man pvesubscription" ### Third party CLI Tools * [ProxBash](https://raymii.org/s/software/ProxBash.html) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Command\_line\_tools\_-\_PVE\_3.x&oldid=11540](https://pve.proxmox.com/mediawiki/index.php?title=Command_line_tools_-_PVE_3.x&oldid=11540) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Proxmox VE 3.x](https://pve.proxmox.com/wiki/Category:Proxmox_VE_3.x "Category:Proxmox VE 3.x") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # VNC - Proxmox VE VNC === From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/VNC#mw-head) [Jump to search](https://pve.proxmox.com/wiki/VNC#searchInput) VNC stands for Virtual Network Computing. It is, in essence, a remote display system which allows you to view a computing environment not only on the machine where it is running, but from anywhere on the Internet and from a wide variety of machine architectures. Proxmox VE uses VNC to provide access to virtual machines using the web-based noVNC client (which is independent from a possibly installed VNC server _inside_ a virtual machine), that means no special client software has to be installed, a web-browser is sufficient. In exceptional cases it may be requested to use another client software, look [here](https://pve.proxmox.com/wiki/VNC_Client_Access "VNC Client Access") for more information. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=VNC&oldid=9820](https://pve.proxmox.com/mediawiki/index.php?title=VNC&oldid=9820) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Unlock Locked OpenVZ Container - Proxmox VE Unlock Locked OpenVZ Container ============================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Unlock_Locked_OpenVZ_Container#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Unlock_Locked_OpenVZ_Container#searchInput) ℹ️ **Note**: OpenVZ Containers are only supported until Proxmox VE 3.4 * Sometimes when we have some action scripts that do not work properly, the OpenVZ container fails to start and becomes unresponsive, ie., it is now in a **locked** state. * The **pid** of the **/usr/sbin/vzctl _\[VEID\]_ start** process is stored in **/var.lib/vz/lock/_\[VEID\]_.lck file** appended with 2 line feeds. * If multiple attempts were made to **start / restart** the container in vain, then each such event will have a separate **pid**. All these **pid**s will have to be removed and finally the **lck** file as well. * These pids can be found from: ps aux | grep "/usr/sbin/vzctl start \[VEID\]" * Now the container can be stopped from the GUI. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Unlock\_Locked\_OpenVZ\_Container&oldid=10450](https://pve.proxmox.com/mediawiki/index.php?title=Unlock_Locked_OpenVZ_Container&oldid=10450) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Archive](https://pve.proxmox.com/wiki/Category:Archive "Category:Archive") * [Proxmox VE 3.x](https://pve.proxmox.com/wiki/Category:Proxmox_VE_3.x "Category:Proxmox VE 3.x") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "MediaWiki" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "MediaWiki" ============================== ← [MediaWiki](https://pve.proxmox.com/mediawiki/index.php?title=MediaWiki&action=edit&redlink=1 "MediaWiki (page does not exist)") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/MediaWiki#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/MediaWiki#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[MediaWiki](https://pve.proxmox.com/mediawiki/index.php?title=MediaWiki&action=edit&redlink=1 "MediaWiki (page does not exist)") **: Displaying 2 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/MediaWiki&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/MediaWiki&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/MediaWiki&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/MediaWiki&limit=500) ) * [Proxmox VE News](https://pve.proxmox.com/wiki/Proxmox_VE_News "Proxmox VE News") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Proxmox+VE+News "Special:WhatLinksHere") ) * [User:Apmuthu](https://pve.proxmox.com/wiki/User:Apmuthu "User:Apmuthu") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User%3AApmuthu "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/MediaWiki&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/MediaWiki&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/MediaWiki&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/MediaWiki&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/MediaWiki](https://pve.proxmox.com/wiki/Special:WhatLinksHere/MediaWiki) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Firmware Updates - Proxmox VE Firmware Updates ================ From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Firmware_Updates#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Firmware_Updates#searchInput) guests, e.g. when using device pass-through, depends strongly on your setup and is therefore out of scope. In addition to regular software updates, firmware updates are also important for reliable and secure operation. When obtaining and applying firmware updates, a combination of available options is recommended to get them as early as possible or at all. The term firmware is usually divided linguistically into microcode (for CPUs) and firmware (for other devices). Persistent Firmware ------------------- This section is suitable for all devices. Updated microcode, which is usually included in a BIOS/UEFI update, is stored on the motherboard, whereas other firmware is stored on the respective device. This persistent method is especially important for the CPU, as it enables the earliest possible regular loading of the updated microcode at boot time. | | | | --- | --- | | ![Caution]() | With some updates, such as for BIOS/UEFI or storage controller, the device configuration could be reset. Please follow the vendor’s instructions carefully and back up the current configuration. | Please check with your vendor which update methods are available. * Convenient update methods for servers can include Dell’s Lifecycle Manager or Service Packs from HPE. * Sometimes there are Linux utilities available as well. Examples are [_mlxup_](https://network.nvidia.com/support/firmware/mlxup-mft/) for NVIDIA ConnectX or [_bnxtnvm_/_niccli_](https://techdocs.broadcom.com/us/en/storage-and-ethernet-connectivity/ethernet-nic-controllers/bcm957xxx/adapters/software-installation/updating-the-firmware/manually-updating-the-adapter-firmware-on-linuxesx.html) for Broadcom network cards. * [LVFS](https://fwupd.org/) is also an option if there is a cooperation with the [hardware vendor](https://fwupd.org/lvfs/vendors/) and [supported hardware](https://fwupd.org/lvfs/devices/) in use. The technical requirement for this is that the system was manufactured after 2014 and is booted via UEFI. Proxmox VE ships its own version of the fwupd package to enable Secure Boot Support with the Proxmox signing key. This package consciously dropped the dependency recommendation for the udisks2 package, due to observed issues with its use on hypervisors. That means you must explicitly configure the correct mount point of the EFI partition in /etc/fwupd/daemon.conf, for example: File /etc/fwupd/daemon.conf \# Override the location used for the EFI system partition (ESP) path. EspLocation=/boot/efi | | | | --- | --- | | ![Tip]() | If the update instructions require a host reboot, make sure that it can be done safely. See also [Node Maintenance](https://pve.proxmox.com/wiki/High_Availability#ha_manager_node_maintenance)
. | Runtime Firmware Files ---------------------- This method stores firmware on the Proxmox VE operating system and will pass it to a device if its [persisted firmware](https://pve.proxmox.com/wiki/Firmware_Updates#sysadmin_firmware_persistent) is less recent. It is supported by devices such as network and graphics cards, but not by those that rely on persisted firmware such as the motherboard and hard disks. In Proxmox VE the package pve-firmware is already installed by default. Therefore, with the normal [system updates (APT)](https://pve.proxmox.com/wiki/System_Software_Updates#system_software_updates) , included firmware of common hardware is automatically kept up to date. An additional [Debian Firmware Repository](https://pve.proxmox.com/wiki/Package_Repositories#sysadmin_debian_firmware_repo) exists, but is not configured by default. If you try to install an additional firmware package but it conflicts, APT will abort the installation. Perhaps the particular firmware can be obtained in another way. CPU Microcode Updates --------------------- Microcode updates are intended to fix found security vulnerabilities and other serious CPU bugs. While the CPU performance can be affected, a patched microcode is usually still more performant than an unpatched microcode where the kernel itself has to do mitigations. Depending on the CPU type, it is possible that performance results of the flawed factory state can no longer be achieved without knowingly running the CPU in an unsafe state. To get an overview of present CPU vulnerabilities and their mitigations, run lscpu. Current real-world known vulnerabilities can only show up if the Proxmox VE host is [up to date](https://pve.proxmox.com/wiki/System_Software_Updates#system_software_updates) , its version not [end of life](https://pve.proxmox.com/wiki/FAQ#faq-support-table) , and has at least been rebooted since the last kernel update. Besides the recommended microcode update via [persistent](https://pve.proxmox.com/wiki/Firmware_Updates#sysadmin_firmware_persistent) BIOS/UEFI updates, there is also an independent method via **Early OS Microcode Updates**. It is convenient to use and also quite helpful when the motherboard vendor no longer provides BIOS/UEFI updates. Regardless of the method in use, a reboot is always needed to apply a microcode update. ### Set up Early OS Microcode Updates To set up microcode updates that are applied early on boot by the Linux kernel, you need to: 1. Enable the [Debian Firmware Repository](https://pve.proxmox.com/wiki/Package_Repositories#sysadmin_debian_firmware_repo) 2. Get the latest available packages apt update (or use the web interface, under Node → Updates) 3. Install the CPU-vendor specific microcode package: * For Intel CPUs: apt install intel-microcode * For AMD CPUs: apt install amd64-microcode 4. Reboot the Proxmox VE host Any future microcode update will also require a reboot to be loaded. ### Microcode Version To get the current running microcode revision for comparison or debugging purposes: \# grep microcode /proc/cpuinfo | uniq microcode : 0xf0 A microcode package has updates for many different CPUs. But updates specifically for your CPU might not come often. So, just looking at the date on the package won’t tell you when the company actually released an update for your specific CPU. If you’ve installed a new microcode package and rebooted your Proxmox VE host, and this new microcode is newer than both, the version baked into the CPU and the one from the motherboard’s firmware, you’ll see a message in the system log saying "microcode updated early". \# dmesg | grep microcode \[ 0.000000\] microcode: microcode updated early to revision 0xf0, date = 2021-11-12 \[ 0.896580\] microcode: Microcode Update Driver: v2.2. ### Troubleshooting For debugging purposes, the set up Early OS Microcode Update applied regularly at system boot can be temporarily disabled as follows: 1. make sure that the host can be rebooted [safely](https://pve.proxmox.com/wiki/High_Availability#ha_manager_node_maintenance) 2. reboot the host to get to the GRUB menu (hold SHIFT if it is hidden) 3. at the desired Proxmox VE boot entry press E 4. go to the line which starts with linux and append separated by a space **dis\_ucode\_ldr** 5. press CTRL-X to boot this time without an Early OS Microcode Update If a problem related to a recent microcode update is suspected, a package downgrade should be considered instead of package removal (apt purge ). Otherwise, a too old [persisted](https://pve.proxmox.com/wiki/Firmware_Updates#sysadmin_firmware_persistent) microcode might be loaded, even though a more recent one would run without problems. A downgrade is possible if an earlier microcode package version is available in the Debian repository, as shown in this example: \# apt list -a intel-microcode Listing... Done intel-microcode/stable-security,now 3.20230808.1~deb12u1 amd64 \[installed\] intel-microcode/stable 3.20230512.1 amd64 \# apt install intel-microcode=3.202305\* ... Selected version '3.20230512.1' (Debian:12.1/stable \[amd64\]) for 'intel-microcode' ... dpkg: warning: downgrading intel-microcode from 3.20230808.1~deb12u1 to 3.20230512.1 ... intel-microcode: microcode will be updated at next boot ... Make sure (again) that the host can be rebooted [safely](https://pve.proxmox.com/wiki/High_Availability#ha_manager_node_maintenance) . To apply an older microcode potentially included in the microcode package for your CPU type, reboot now. | | | | --- | --- | | ![Tip]() | It makes sense to hold the downgraded package for a while and try more recent versions again at a later time. Even if the package version is the same in the future, system updates may have fixed the experienced problem in the meantime.

\# apt-mark hold intel-microcode
intel-microcode set on hold.

\# apt-mark unhold intel-microcode
# apt update
# apt full-upgrade | Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Firmware\_Updates&oldid=12291](https://pve.proxmox.com/mediawiki/index.php?title=Firmware_Updates&oldid=12291) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Reference Documentation](https://pve.proxmox.com/wiki/Category:Reference_Documentation "Category:Reference Documentation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # User:Martin - Proxmox VE User:Martin =========== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/User:Martin#mw-head) [Jump to search](https://pve.proxmox.com/wiki/User:Martin#searchInput) [Martin Maurer](mailto:martin@proxmox.com) [Proxmox Server Solutions GmbH](http://www.proxmox.com/) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=User:Martin&oldid=3064](https://pve.proxmox.com/mediawiki/index.php?title=User:Martin&oldid=3064) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # ProxyPass Reverse - Proxmox VE ProxyPass Reverse ================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/ProxyPass_Reverse#mw-head) [Jump to search](https://pve.proxmox.com/wiki/ProxyPass_Reverse#searchInput) [http://opentox.github.io/installation/2012/10/08/set-up-virtual-machine-in-proxmox-virtual-environment/](http://opentox.github.io/installation/2012/10/08/set-up-virtual-machine-in-proxmox-virtual-environment/) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=ProxyPass\_Reverse&oldid=6629](https://pve.proxmox.com/mediawiki/index.php?title=ProxyPass_Reverse&oldid=6629) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # User contributions for ANeutrino - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:User_contributions) User contributions for ANeutrino ================================ Results for [ANeutrino](https://pve.proxmox.com/mediawiki/index.php?title=User:ANeutrino&action=edit&redlink=1 "User:ANeutrino (page does not exist)") [talk](https://pve.proxmox.com/mediawiki/index.php?title=User_talk:ANeutrino&action=edit&redlink=1 "User talk:ANeutrino (page does not exist)") [block log](https://pve.proxmox.com/mediawiki/index.php?title=Special:Log/block&page=User%3AANeutrino "Special:Log/block") [uploads](https://pve.proxmox.com/wiki/Special:ListFiles/ANeutrino "Special:ListFiles/ANeutrino") [logs](https://pve.proxmox.com/wiki/Special:Log/ANeutrino "Special:Log/ANeutrino") A user with 0 edits. Account created on 5 February 2009. [Jump to navigation](https://pve.proxmox.com/wiki/Special:Contributions/ANeutrino#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:Contributions/ANeutrino#searchInput) Search for contributionsExpandCollapse ⧼contribs-top⧽ IP address or username: Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection Associated namespace [Tag](https://pve.proxmox.com/wiki/Special:Tags "Special:Tags") filter: Manual revertNew redirectRemoved redirectReplacedRevertedRollbackUndoVisual edit: Switchedwikieditor (hidden tag) Invert selection Only show edits that are latest revisions Only show edits that are page creations Hide minor edits ⧼contribs-date⧽ From date: To date: Search No changes were found matching these criteria. Retrieved from "[https://pve.proxmox.com/wiki/Special:Contributions/ANeutrino](https://pve.proxmox.com/wiki/Special:Contributions/ANeutrino) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Proxmox VE inside VirtualBox - Proxmox VE Proxmox VE inside VirtualBox ============================ From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Proxmox_VE_inside_VirtualBox#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Proxmox_VE_inside_VirtualBox#searchInput) Running **Proxmox VE inside VirtualBox** is possible but is not recommended for production use. Virtualizing the Proxmox VE hypervisor inside VirtualBox is usually done for development and testing purposes. For example, wanting to use VirtualBox as a host for Proxmox on a laptop is a [common wish](http://forum.proxmox.com/google.php?cx=partner-pub-1240956337013298%3A0281164794&cof=FORID%3A9&ie=ISO-8859-1&q=virtualbox&sa.x=-1192&sa.y=-47&siteurl=forum.proxmox.com%2F&ref=&ss=1399j312179j10) but can be tricky to get right. This page covers special considerations necessary for Proxmox VE to function as expected when it is being hosted by the VirtualBox hypervisor. Unless otherwise stated, this page assumes you are using: * VirtualBox 4.3.16 or higher. * Proxmox VE 4.x or higher (i.e. for lxc containers only, OpenVz is not supported any more) Contents -------- * [1 Prerequisites](https://pve.proxmox.com/wiki/Proxmox_VE_inside_VirtualBox#Prerequisites) * [2 Nested Containers and simple Virtual Machines](https://pve.proxmox.com/wiki/Proxmox_VE_inside_VirtualBox#Nested_Containers_and_simple_Virtual_Machines) * [3 Network Considerations](https://pve.proxmox.com/wiki/Proxmox_VE_inside_VirtualBox#Network_Considerations) * [3.1 Internet access](https://pve.proxmox.com/wiki/Proxmox_VE_inside_VirtualBox#Internet_access) * [3.2 VirtualBox guest to Proxmox guest communication requires VirtualBox NIC in promiscuous mode](https://pve.proxmox.com/wiki/Proxmox_VE_inside_VirtualBox#VirtualBox_guest_to_Proxmox_guest_communication_requires_VirtualBox_NIC_in_promiscuous_mode) * [4 Install and Run Proxmox VE](https://pve.proxmox.com/wiki/Proxmox_VE_inside_VirtualBox#Install_and_Run_Proxmox_VE) Prerequisites ============= For Proxmox VE inside VirtualBox to work well, it's strongly recommended that your VirtualBox host (e.g., your laptop) meets the minimum hardware requirements and software configuration. Otherwise, Proxmox VE may still work but it can be extremely slow. * VirtualBox should support hardware virtualization acceleration. This means the feature is activated in EFI/BIOS. If you don't see this option in your EFI/BIOS screens, you should double-check to see if your CPU supports it. * Further, if you plan to host any guests within Proxmox and are running VirtualBox 6.1 or later, you should enable nested hardware virtualization acceleration in the VirtualBox settings for the Proxmox VE virtual machine itself. The setting is in the [VirtualBox Machine Processor Tab](https://www.virtualbox.org/manual/UserManual.html#settings-processor) (System → Processor → **Enable Nested VT-x/AMD-V**). * When creating the VirtualBox VM to host Proxmox VE, you should set its [OS type](https://www.virtualbox.org/manual/UserManual.html#settings-basic) to be run as **Linux: Debian (64-bit)** guest. Nested Containers and simple Virtual Machines ============================================= You can run LXC Containers in the virtualized Proxmox VE without any problems. It's also possible to create and configure fully nested virtual machines, so long as you enable VirtualBox's supported for nested VT-X/AMD-V hardware instructions, noted above. Nested virtual machines will run fairly well if they don't have any graphical interface and don't consume too many CPU resources. (This was tested with, e.g., [slax-router](http://slaxrouter.sourceforge.net/slax-router) .) Do be careful, though. If your nested VMs require too many resources, they will freeze up and can block your guest system too! Also, note that some VirtIO drivers are known to make problems if nested in a VirtualBox environment, although this seems to have gotten more reliable with later version of VirtualBox (specifically 6.1 and higher). For this reason, it's recommend to **use e1000** for the nested VM's network adapters if you can, especially since the improved performance offered by the _virtio_ driver is not typically required in a nested scenario such as this. Further, when using earlier VirtualBox versions, KVM hardware virtualization does not work and must not be set! The reason is that with these VirtualBox versions, nested hardware virtualization support is not possible. [Nested virtualization became possible starting in VirtualBox version 6.1](https://www.virtualbox.org/manual/UserManual.html#nested-virt) . Network Considerations ====================== Most [VirtualBox networking modes](https://www.virtualbox.org/manual/UserManual.html#networkingmodes) will work as expected when running Proxmox VE as a guest within VirtualBox. However, there are a few things to consider specially. Internet access --------------- The easiest way to give your Proxmox VE node access to the Internet when it is running as a guest within VirtualBox is to use VirtualBox's _NAT_ networking mode. (This is not the same as the _NAT network_ networking mode!) For example, configure the VirtualBox VM's "Adapter 1" to use the NAT networking mode and boot the Proxmox VE guest. When Proxmox starts, it will recognize its physical NIC and receive an IP address from VirtualBox's internal DHCP service. Usually, this is something like 10.0.x.x (for example: `10.0.2.15`). Your Proxmox VE node is now on its own, totally independent network, separated from VirtualBox host's network access. From here, you can configure any number of Proxmox VE guests as you normally would within Proxmox VE itself. However, since your Proxmox VE node is now behind a NAT router, you will not be able to access the Proxmox VE Web GUI nor the SSH port unless you also configure the VirtualBox NAT service to forward traffic for these services to the correct ports. For details, see [§6.3.1, "Configuring Port Forwarding with NAT", of the VirtualBox User Manual](https://www.virtualbox.org/manual/UserManual.html#natforward) . For example, if you forward host post 8006 to guest port 8006, you can access the Proxmox VE Web GUI via a URL such as [https://localhost:8006](https://localhost:8006/) in a browser running on your VirtualBox host. VirtualBox guest to Proxmox guest communication requires VirtualBox NIC in promiscuous mode ------------------------------------------------------------------------------------------- If you plan to have Proxmox VE host its own (nested) virtual machines or containers that are attached to a VirtualBox virtual network (as opposed to running entirely within Proxmox VE's own internal bridged networking) and would like those guests to be able to communicate with the VirtualBox host or with other VirtualBox-hosted (as opposed to Proxmox VE-hosted) virtual machines, you should [ensure that the relevant VirtualBox virtual network adapter is permitted to use promiscuous mode](https://forum.proxmox.com/threads/why-is-this-simple-bridge-network-not-receiving-arp-replies-correctly.75695/#post-337550) . This is not the default setting! Rather, by default, VirtualBox denies its guest VMs from effectively enabling promiscuous mode. (Its default setting is _Deny_.) The setting is available from the Network tab in a VirtualBox VM Machine Settings window (Network → Adapter N \[where N is the adapter number\] → Advanced → Promiscuous Mode) or can be changed via command line with: vboxmanage modifyvm --nicpromiscN Without this option changed away from _Deny_, communication from a VirtualBox-hosted VM to a (nested) Proxmox VE-hosted VM or container will fail. If communication from a VirtualBox-hosted guest to a nested Proxmox VE-hosted guest still fails after making the above change, try restarting the virtualized Proxmox VE node itself. Install and Run Proxmox VE ========================== The following instructions describe how to configure an example, simple, single virtualized Proxmox VE node within VirtualBox that is known to work reliably: 1\. Create a new VirtualBox Virtual Machine for Proxmox Sample settings: * Name: Proxmox-vm * OS Type: Linux * Version: Debian (64 bit) * Memory: 6GB * Disk: At least 8GB in size 2\. Edit the settings * Audio: disable * Storage: * IDE - Select Empty - click IDE Secondary - select the disk symbol, pick ISO for Proxmox * Network: * Adapter 1: Host-only Adapter, vboxnet0; recommended leave the advanced settings as they are, unless you plan to have VirtualBox-hosted VMs in communication with Proxmox VE-hosted guests, in which case be sure to allow Promiscuous Mode. (Paravirtualized Network (virtio-net)). * Adapter 2: NAT (again, this is not the same as _NAT network_!) Notably, the following networking modes caused trouble historically, but you may have better luck these days: * "NAT network" (note the additional word "network"!), nor * "Bridged Adapter" (to WLAN) Then start the newly created Virtual Machine normally. You should see the Proxmox VE installer and can continue with installing Proxmox VE inside VirtualBox as you like. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Proxmox\_VE\_inside\_VirtualBox&oldid=10832](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_VE_inside_VirtualBox&oldid=10832) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Split lock detection - Proxmox VE Split lock detection ==================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Split_lock_detection#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Split_lock_detection#searchInput) Contents -------- * [1 Symptoms](https://pve.proxmox.com/wiki/Split_lock_detection#Symptoms) * [2 Background](https://pve.proxmox.com/wiki/Split_lock_detection#Background) * [3 Options](https://pve.proxmox.com/wiki/Split_lock_detection#Options) Symptoms -------- If the host CPU supports split lock detection and VM guests perform misaligned atomic memory access, the host Linux kernel may artificially slow down the virtual CPUs of the guests as part of the split lock mitigation. For the VM, this looks like a virtual CPU core freezes for several milliseconds every time a misaligned atomic memory access is performed. In the case of Windows VMs, in-guest latency monitors may report a high amount of time spent handling Deferred Procedure Calls (DPCs). Your VM is affected by this if **all of the following** is true: * Your Proxmox VE host is running kernel 5.19 or higher. You can check the running kernel with the following command: pveversion * Your Proxmox VE host CPU supports the `split_lock_detect` flag. This is the case if the following command prints "1": lscpu | grep -c 'split\_lock\_detect' * The journal of your Proxmox VE host contains warnings like the following: Apr 15 09:20:19 myhost kernel: x86/split lock detection: #AC: CPU 0/KVM/5677 took a split\_lock trap at address: 0x56339a9888c3 You can run the following command to search for these log lines since the last boot: journalctl -b --grep split\_lock * Install the `bpftrace` package on the Proxmox VE host: `apt install bpftrace`. Then, run the following [bpftrace](https://github.com/bpftrace/bpftrace) command line: bpftrace -e 'kfunc:vmlinux:split\_lock\_warn /0<\*(uint32\*)kaddr("sysctl\_sld\_mitigate")/{time("%H:%M:%S: "); printf("slowing down %s (pid=%d) for >10ms\\n", comm, pid);}' If you run the VM workload and the `bpftrace` command starts printing **a lot of output** mentioning `CPU n/KVM` and the PID of your VM, split lock mitigation artificially slows down your VM. For example: 09:49:02: slowing down CPU 0/KVM (pid=10433) for >10ms 09:49:02: slowing down CPU 2/KVM (pid=10433) for >10ms 09:49:03: slowing down CPU 3/KVM (pid=10433) for >10ms 09:49:03: slowing down CPU 1/KVM (pid=10433) for >10ms 09:49:03: slowing down CPU 0/KVM (pid=10433) for >10ms 09:49:03: slowing down CPU 2/KVM (pid=10433) for >10ms See below for options how to remove these artificial slowdowns. ℹ️ **Note**: If the `bpftrace` command only sporadically prints a message (e.g., every few minutes), split lock detection probably does not have a large impact on VM performance. ℹ️ **Note**: For VMs using OVMF, the `bpftrace` command may print some messages during boot. This is not problematic and does not impact performance of the running VM. Split lock mitigation only affects VM performance if a large number of messages continues to appear after boot. Background ---------- As explained by this [LWN article](https://lwn.net/Articles/790464/) , split locks occur when an atomic instruction accesses memory that spans two cache lines, for example because of a misaligned memory access. To ensure that the instruction sees consistent data, the processor core acquires a global bus lock. This is much slower than an access within one cache line, and also slows down other cores. In case the host is a hypervisor running potentially untrusted VMs, this opens the door for denial-of-service attacks: A VM that performs a lot of unaligned memory accesses can force the processor to repeatedly acquire the global bus lock, which indirectly slows down other VMs. Starting with Linux kernel 5.19, every time a thread takes a split lock, the Linux kernel artificially slows down the thread by making it sleep for 10 milliseconds and synchronizing it with other threads taking split locks. This is controlled by the [`split_lock_mitigate` sysctl parameter](https://docs.kernel.org/6.2/admin-guide/sysctl/kernel.html#split-lock-mitigate-x86-only) . See the related [LWN article](https://lwn.net/Articles/911219/) for more details. This is done to make denial-of-service attacks infeasible and keeping the offending thread from affecting the other running processes. The first time a split lock is detected for a thread, the kernel prints a warning to the journal (`x86/split lock detection: #AC: [...] took a split_lock trap at address: [...]`). If a VM performs a lot of misaligned memory access, the host kernel will artificially slow down the VM. The `bpftrace` command above prints a message every time the kernel artificially slows down a thread. In the VM, this will be noticeable as virtual CPU freezes with various kinds of effects. In the case of Windows VMs, in-guest latency monitors may report a high amount of time spent handling DPCs during that time. Options ------- If a VM is artificially slowed down by split lock mitigation, * the **preferred solution** is to fix the in-guest workload that is responsible for the misaligned memory accesses. The responsible in-guest process should be adjusted to only perform aligned memory access, which will eliminate the split locks and thus the artificial slowdowns. However, this is only possible if you control the responsible in-guest process (e.g., because you can modify its source code). * If you cannot fix the in-guest workload, you can consider disabling the split lock mitigation. However, if the split lock mitigation is disabled, malicious VM guests can perform denial-of-service attacks against the host and other VM guests, as [described on LWN](https://lwn.net/Articles/790464/) : * If you are aware of the risks, you can disable split lock mitigation temporarily by running `sysctl -w kernel.split_lock_mitigate=0` (see the [kernel docs](https://docs.kernel.org/6.2/admin-guide/sysctl/kernel.html#split-lock-mitigate-x86-only) ). You can disable it permanently by creating a file `/etc/sysctl.d/50-split-lock.conf` with contents `kernel.split_lock_mitigate=0`, and running `sysctl -p /etc/sysctl.d/50-split-lock.conf`. You will still get the warnings in the journal, but the `bpftrace` script should report no more artificial slowdowns. * Alternatively, and if you are aware of the risks, you can generally disable split lock detection by adding `split_lock_detect=off` [parameter to the kernel command line](https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysboot_edit_kernel_cmdline) and rebooting. See the [kernel docs](https://www.kernel.org/doc/html/v6.2/admin-guide/kernel-parameters.html) for more information on the `split_lock_detect` parameter. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Split\_lock\_detection&oldid=12457](https://pve.proxmox.com/mediawiki/index.php?title=Split_lock_detection&oldid=12457) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Debian 4.0 Standard" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Debian 4.0 Standard" ======================================== ← [Debian 4.0 Standard](https://pve.proxmox.com/mediawiki/index.php?title=Debian_4.0_Standard&action=edit&redlink=1 "Debian 4.0 Standard (page does not exist)") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Debian_4.0_Standard#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Debian_4.0_Standard#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Debian 4.0 Standard](https://pve.proxmox.com/mediawiki/index.php?title=Debian_4.0_Standard&action=edit&redlink=1 "Debian 4.0 Standard (page does not exist)") **: Displaying 3 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Debian_4.0_Standard&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Debian_4.0_Standard&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Debian_4.0_Standard&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Debian_4.0_Standard&limit=500) ) * [Debian Etch standard (i386) Appliance](https://pve.proxmox.com/mediawiki/index.php?title=Debian_Etch_standard_(i386)_Appliance&redirect=no "Debian Etch standard (i386) Appliance") (redirect page) ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Debian+Etch+standard+%28i386%29+Appliance "Special:WhatLinksHere") ) * [Debian Etch Standard](https://pve.proxmox.com/mediawiki/index.php?title=Debian_Etch_Standard&redirect=no "Debian Etch Standard") (redirect page) ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Debian+Etch+Standard "Special:WhatLinksHere") ) * [Proxmox VE News](https://pve.proxmox.com/wiki/Proxmox_VE_News "Proxmox VE News") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Proxmox+VE+News "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Debian_4.0_Standard&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Debian_4.0_Standard&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Debian_4.0_Standard&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Debian_4.0_Standard&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Debian\_4.0\_Standard](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Debian_4.0_Standard) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Unattended installation of Proxmox - Proxmox VE Unattended installation of Proxmox ================================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Unattended_installation_of_Proxmox#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Unattended_installation_of_Proxmox#searchInput) ℹ️ **Note**: Article refers to Proxmox VE 3.x which is based on Debian wheezy; Proxmox VE 6.x is based on Debian buster, the article has to be updated and verified Introduction ------------ Remote unattended installation means installation of remote server without any human interference. This process is very useful for bare metal provisioning or automated installation on multiple servers. I have used FAI (Fully Automatic Installation) to automate remote installation of ProxmoxVE. I have used steps from "ProxmoxVE installation over Debian wheezy". So this does not install ProxmoxVE from ProxmoxVE ISO. It installs Debian wheezy first and then ProxmoxVE. FAI is a non-interactive system to install, customize and manage Linux systems and software configurations on computers as well as virtual machines and chroot environments, from small networks to large-scale infrastructures like clusters and cloud environments. It's a tool for unattended mass deployment of Linux. "FAI-Fully Automatic Installation" is used to automate headless installation of Proxmox or Debian. [http://fai-project.org/](http://fai-project.org/) Basic Architecture ------------------ **Components:** This setup has following components required. fai-server DHCP server NFS Server TFTP Server **Basic Process:** \- Client machine (On which Proxmox is going to be installed.) boots from Network PXE. \- It searches for DHCP Server. \- DHCP Server on FAIserver provides Network Details to Client such as IP address, Netmask, Gateway, etc. It also points clients to TFTP & NFS server. \- TFTP trasfers the kernel to Client Machine \- NFS Server Mounts the nfsroot on Client machine \- FAI Scripts starts the installation **Important Configurations files and folders of FAI:** | Configuration File/Directory | Details | | --- | --- | | /etc/fai/ | FAI configuration folder | | /etc/fai/fai.conf | FAI configuration file | | /etc/fai/nfsroot.conf | NFSroot configuration file | | /etc/fai/apt/ | FAI repositories which will be used while installation | | /srv/fai/config/ | FAI Client configuration space. It has scripts which will be used while installation of Client | | /srv/fai/package\_config/ | Configurations related to Package installation | | /srv/fai/disk\_config/ | Configurations related to disk partition layout | | /srv/fai/scripts | Miscellaneous scripts required for installations | | /srv/fai/nfsroot | NFS Root file system which will be shared by NFS and will be mounted as Root filesystem on client machine | | /etc/dhcp/dhcpd.conf | DHCP configuration file | | /etc/exports | NFS configuration file | | /etc/default/tftpd-hpa | TFTP configuration file | | /etc/hosts | Hosts declaration file / File DNS | Implementation: --------------- **Scenario:** To follow these steps require 2 machines Server & Client. Server is the one which has FAI Server configured on Debian Wheezy. Client is the one on which ProxmoxVE is going to be installed. Server Name: faiserver Server IPAddress: 192.168.0.1/24 Client Name: demohost Client IPAddress: 192.168.0.2/24 **Steps:** **Prepare FAI-Server:** 1\. Install Debian Wheezy with net-install ISO. Just install OpenSSH server nothing else on it. 2\. Install Required Applications apt-get -y install apache2 fai-quickstart fai-doc fai-server isc-dhcp-server tftpd-hpa nfs-kernel-server syslinux-common debmirror Create Local Debian Mirror: ln -s /files/scratch/debmirror /var/www/debmirror /usr/share/doc/fai-doc/examples/utils/mkdebmirror /etc/init.d/apache2 restart Configure /etc/hosts: Add below entries: 192.168.0.1 faiserver 192.168.0.2 demohost Configure /etc/fai/fai.conf: Make sure you have these entries in fai.conf SERVER=192.168.0.1 FAI\_CONFIG\_SRC=nfs://$SERVER/srv/fai/config # Account for saving log files and calling fai-chboot. LOGUSER=fai FAI\_LOGPROTO=ssh Configure /etc/fai/nfsroot.conf": Make sure nfsroot.conf looks like: FAI\_DEBOOTSTRAP="wheezy [http://http.debian.net/debian](http://http.debian.net/debian) " FAI\_ROOTPW='$1$kBnWcO.E$djxB128U7dMkrltJHPf6d1' NFSROOT=/srv/fai/nfsroot TFTPROOT=/srv/tftp/fai NFSROOT\_HOOKS=/etc/fai/nfsroot-hooks/ FAI\_DEBOOTSTRAP\_OPTS="--exclude=info" # Configuration space FAI\_CONFIGDIR=/srv/fai/config Configure /etc/fai/apt/sources.list: sources.list should look like below: deb [http://192.168.0.1/debmirror/debian](http://192.168.0.1/debmirror/debian) wheezy main contrib non-free deb [http://192.168.0.1/debmirror/debian-security](http://192.168.0.1/debmirror/debian-security) wheezy/updates main contrib non-free # PVE repository provided by proxmox.com, only for installation (this repo will stay on 3.1) deb [http://download.proxmox.com/debian](http://download.proxmox.com/debian) wheezy pve # security updates deb [http://security.debian.org/](http://security.debian.org/) wheezy/updates main contrib Prepare fai: Run fai-setup command to prepare fai $ fai-setup -v Configure /etc/dhcp/dhcpd.conf: Note down MAC address of NIC of the client machine. deny unknown-clients; option dhcp-max-message-size 2048; use-host-decl-names on; subnet 192.168.0.0 netmask 255.255.255.0 { option routers 192.168.0.1; option domain-name ""; option domain-name-servers 8.8.8.8; option time-servers 192.168.0.1; option ntp-servers 192.168.0.1; server-name faiserver; next-server faiserver; filename "pxelinux.0"; } host demohost {hardware ethernet ;fixed-address 192.168.0.2;} Restart Dhcp server: Run below command to restart dhcp server. Note that I am using init script here. /etc/init.d/isc-dhcp-server restart Configure /etc/exports for NFS share: fai-setup command will add required entries in /etc/exports. Still you need to do some modifications so please make sure it should look like as below: /srv/fai/config 192.168.0.0/24(async,ro,no\_root\_squash) /srv/fai/nfsroot 192.168.0.0/24(async,ro,no\_root\_squash) Restart NFS service: /etc/init.d/nfs-kernel-server restart Configure TFTP Server: Config file /etc/default/tftpd-hpa should look like below. TFTP\_USERNAME="tftp" TFTP\_DIRECTORY="/srv/tftp/fai" TFTP\_ADDRESS="0.0.0.0:69" TFTP\_OPTIONS="--secure" Create directory for tftp: mkdir -p /srv/tftp/fai/pxelinux.cfg Copy pxelinux.0, kernel and initrd to tftp root: cp /boot/vmlinuz-3.2.0-4-amd64 /srv/tftp/fai/ cp /usr/lib/syslinux/pxelinux.0 /srv/tftp/fai/ cp /boot/initrd.img-3.2.0-4-amd64 /srv/tftp/fai/ Restart tftpd service: /etc/init.d/tftpd-hpa restart Copy Sample configuration files to fai/config directories cp -a /usr/share/doc/fai-doc/examples/simple/\* /srv/fai/config Change ownership of /srv/fai/config: chown -R fai /srv/fai/config Disk Partition layout: - Remove all files from /srv/fai/config/disk\_config - Create new file name DEFAULT under /srv/fai/config/disk\_config/ and remove all other examples - Add below entries in it: disk\_config disk1 disklabel:msdos primary / 90% ext4 rw primary swap 10% swap sw Package installation config: - Make sure your /srv/fai/config/package\_config/DEFAULT look like below: PACKAGES aptitude initramfs-tools grub-pc pve-firmware pve-kernel-2.6.32-26-pve pve-headers-2.6.32-26-pve # explicitly delete these bootloaders # (just in case the base tgz contains them) PACKAGES aptitude grub-legacy- lilo- linux-image-amd64 linux-base Modifying /srv/fai/config/scripts/DEBIAN/40-misc: - Add below entries in /srv/fai/config/scripts/DEBIAN/40-misc before "exit $error" line ##### Add below entry to /etc/hosts of host:##### echo -e "192.168.0.2 demohost pvelocalhost" >> $target/etc/hosts ################################################################### ##### Add entries for /bin/proxmox\_install.sh ###### ##### This script install proxmox after first reboot ##### echo -e '#!/bin/bash' > $target/bin/proxmox\_install.sh echo -e 'echo -e "Installing Proxmox" > /root/pminstall.log' >> $target/bin/proxmox\_install.sh echo -e 'export DEBIAN\_FRONTEND=noninteractive' >> $target/bin/proxmox\_install.sh echo -e 'apt-get --force-yes -y install proxmox-ve-2.6.32 ntp ssh lvm2 postfix ksm-control-daemon vzprocps open-iscsi bootlogd' >> $target/bin/proxmox\_install.sh echo -e 'sed -i '/proxmox\_install/d' /etc/rc.local' >> $target/bin/proxmox\_install.sh echo -e 'reboot' >> $target/bin/proxmox\_install.sh sed -i '/default/a\\ /bin/proxmox\_install.sh' $target/etc/rc.local ################################################################## chmod 777 $target/bin/proxmox\_install.sh chmod 777 $target/etc/rc.local ##### Change Default kernel for Boot ##### sed -i 's/set default="0"/set default="2"/g' $target/boot/grub/grub.cfg sed -i 's/GRUB\_DEFAULT=0/GRUB\_DEFAULT=2/g' $target/etc/default/grub ################# END ################# Copy fai.conf inside nfsroot cp /etc/fai/fai.conf /srv/fai/nfsroot/etc/fai/ Add to /srv/fai/nfsroot/etc/ssh/ssh\_config StrictHostKeyChecking no Make sure /srv/fai/nfsroot/etc/hosts have below entry: 192.168.0.1 faiserver Initialize Bootloader config for demohost (client) fai-chboot -IB demohost Above command will create config file under /srv/tftp/fai/pxelinux.cfg/ File Name will be something like: C0A87A64 Just edit that file and make sure it should look like below: default fai-generated label fai-generated kernel vmlinuz-3.2.0-4-amd64 append initrd=initrd.img-3.2.0-4-amd64 ip=dhcp root=/dev/nfs nfsroot=192.168.0.1:/srv/fai/nfsroot:vers=3 aufs FAI\_FLAGS=verbose,sshd,reboot FAI\_ACTION=install **Now reboot client machine from Network PXE boot. It will get automatically Proxmox installed.** Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Unattended\_installation\_of\_Proxmox&oldid=10491](https://pve.proxmox.com/mediawiki/index.php?title=Unattended_installation_of_Proxmox&oldid=10491) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Archive](https://pve.proxmox.com/wiki/Category:Archive "Category:Archive") * [Installation](https://pve.proxmox.com/wiki/Category:Installation "Category:Installation") * [Proxmox VE 3.x](https://pve.proxmox.com/wiki/Category:Proxmox_VE_3.x "Category:Proxmox VE 3.x") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Ceph Server" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Ceph Server" ================================ ← [Ceph Server](https://pve.proxmox.com/wiki/Ceph_Server "Ceph Server") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Ceph_Server#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Ceph_Server#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Ceph Server](https://pve.proxmox.com/wiki/Ceph_Server "Ceph Server") **: Displaying 2 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Ceph_Server&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Ceph_Server&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Ceph_Server&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Ceph_Server&limit=500) ) * [Ceph Hammer to Jewel](https://pve.proxmox.com/wiki/Ceph_Hammer_to_Jewel "Ceph Hammer to Jewel") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Ceph+Hammer+to+Jewel "Special:WhatLinksHere") ) * [Talk:Storage: Ceph](https://pve.proxmox.com/wiki/Talk:Storage:_Ceph "Talk:Storage: Ceph") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Talk%3AStorage%3A+Ceph "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Ceph_Server&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Ceph_Server&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Ceph_Server&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Ceph_Server&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Ceph\_Server](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Ceph_Server) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Proxmox VE Mobile - Proxmox VE Proxmox VE Mobile ================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Proxmox_VE_Mobile#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Proxmox_VE_Mobile#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Proxmox_VE_Mobile#Introduction) * [2 Proxmox VE Android App](https://pve.proxmox.com/wiki/Proxmox_VE_Mobile#Proxmox_VE_Android_App) * [2.1 Key Features](https://pve.proxmox.com/wiki/Proxmox_VE_Mobile#Key_Features) * [2.2 Download](https://pve.proxmox.com/wiki/Proxmox_VE_Mobile#Download) * [2.3 SPICE console](https://pve.proxmox.com/wiki/Proxmox_VE_Mobile#SPICE_console) * [3 Proxmox VE HTML5 Mobile Client](https://pve.proxmox.com/wiki/Proxmox_VE_Mobile#Proxmox_VE_HTML5_Mobile_Client) * [3.1 Usage](https://pve.proxmox.com/wiki/Proxmox_VE_Mobile#Usage) * [3.1.1 How to control a VM](https://pve.proxmox.com/wiki/Proxmox_VE_Mobile#How_to_control_a_VM) * [3.2 SPICE console](https://pve.proxmox.com/wiki/Proxmox_VE_Mobile#SPICE_console_2) * [3.2.1 How to use Opaque on Android](https://pve.proxmox.com/wiki/Proxmox_VE_Mobile#How_to_use_Opaque_on_Android) * [3.3 HTML5 Console](https://pve.proxmox.com/wiki/Proxmox_VE_Mobile#HTML5_Console) * [3.4 Security Consideration](https://pve.proxmox.com/wiki/Proxmox_VE_Mobile#Security_Consideration) * [3.4.1 VPN](https://pve.proxmox.com/wiki/Proxmox_VE_Mobile#VPN) * [3.4.2 Two-Factor Authentication](https://pve.proxmox.com/wiki/Proxmox_VE_Mobile#Two-Factor_Authentication) Introduction ============ Proxmox VE can be accessed on mobile devices either through the HTML5-based mobile version of the web interface, or a modern App - currently available for Android. [![](https://pve.proxmox.com/mediawiki/images/thumb/d/da/Proxmox_VE_Android_App_-_Overview.png/400px-Proxmox_VE_Android_App_-_Overview.png)](https://pve.proxmox.com/wiki/File:Proxmox_VE_Android_App_-_Overview.png) Proxmox VE Android App ====================== Log in to your Proxmox Virtual Environment (VE) server and manage virtual machines, containers, hosts, and clusters. Based on the cutting edge Flutter framework you will get a beautiful and blazing fast experience. Key Features ------------ * Overview dashboard of Proxmox VE cluster or node status * Login manager to connect to different Proxmox VE clusters or nodes * Search and filter functionality for guest, storage, and nodes * Overview of users, API token, groups, roles, domains * Manage VM/container power settings (Start, Stop, Reboot, etc.) * RRD diagrams for nodes and guests * Migration of guests (offline, online) between cluster nodes * Back up data to different storages including Proxmox Backup Server * Storage view to access and or search content * Task history and current task overview Download -------- [![](https://pve.proxmox.com/mediawiki/images/thumb/7/7e/Proxmox_VE_Android_App_-_VM_View.png/400px-Proxmox_VE_Android_App_-_VM_View.png)](https://pve.proxmox.com/wiki/File:Proxmox_VE_Android_App_-_VM_View.png) Proxmox VE Android App - VM View Currently, the Proxmox VE Mobile App is available through the Google Play Store: [https://play.google.com/store/apps/details?id=com.proxmox.app.pve\_flutter\_frontend](https://play.google.com/store/apps/details?id=com.proxmox.app.pve_flutter_frontend) SPICE console ------------- You can use [SPICE](https://pve.proxmox.com/wiki/SPICE "SPICE") to get console access. In order to get this running, you need to purchase the [Opaque](https://play.google.com/store/apps/details?id=com.undatech.opaque) App. The Proxmox VE Android app is able to open the Opaque SPICE console viewer directly when using the "Console" button. Proxmox VE HTML5 Mobile Client ============================== [![](https://pve.proxmox.com/mediawiki/images/c/c3/Screen-ProxmoxVE-Mobile-Login.png)](https://pve.proxmox.com/wiki/File:Screen-ProxmoxVE-Mobile-Login.png) HTML5 - Login Form In addition to the full featured web interface, Proxmox VE Mobile (introduced in Proxmox VE 3.3 as technology preview) is designed specifically for the use on mobile devices (phones and tablets). It is not a complete replacement for the full admin web interface but it has already a lot of key functionality to manage Proxmox VE on the go, including the SPICE and HTML5 console. Currently, VM and CT handling and showing of their configuration (but no editing) is supported. [![](https://pve.proxmox.com/mediawiki/images/9/9f/Screen-ProxmoxVE-Mobile-Datacenter.png)](https://pve.proxmox.com/wiki/File:Screen-ProxmoxVE-Mobile-Datacenter.png) HTML5 - Datacenter Overview As Proxmox VE Mobile is a HTML5 app (build with [Sencha Touch](http://www.sencha.com/products/touch/) ), there is no installation or configuration needed. **Main features** * Supports Two-Factor Authentication * Manage all nodes inside your cluster with one login * View status and config of host, containers and VM * Start/Stop/Shutdown/Migrate * HTML5 Console (works on all browsers) * SPICE Console, for best user experience (Android only, third party APP needed) * Task log Usage ----- Just point your browser on your mobile device to the main URL, e.g. `[https://youripaddress:8006](https://youripaddress:8006/) ` If the auto-detection works correctly (phone browsers works most times, tablets not always), you will see the mobile interface directly. If not, just add the following to your URL: * `[https://youripaddress:8006/?mobile=1](https://youripaddress:8006/?mobile=1) ` This is also a good way to test the mobile interface via your desktop browser. If your browser can simulate a mobile device screen, this will help to test the application just from your desktop. If you want to switch to standard view (e.g. in order to change some configuration) specify * https://youripaddress:8006/?mobile=0 ### How to control a VM [![](https://pve.proxmox.com/mediawiki/images/1/11/Screen-ProxmoxVE-Mobile-VM-Details.png)](https://pve.proxmox.com/wiki/File:Screen-ProxmoxVE-Mobile-VM-Details.png) HTML5 - VM Details After connecting to server the Log In form is shown (fig. 1) * Enter User name and Password into the provided fields * If necessary select "Proxmox VE authentication server" by activating the pull down menu "Linux PAM standard authentication" * Select the "Log In" bar Now you are at "Datacenter" level, all cluster nodes are shown (fig. 2) * Select the node where the VM is located Now you are at node level, all VMs in that node are shown * Select the VM Now you see all data of the selected VM (fig. 3) * Select from menu top right what you want to to: \- Start: starts the VM \- Shutdown: performs an ACPI shutdown of the VM \- Stop: stops (power off) of the VM \- Migrate: migrates the VM to another node (note: after migration the VM disappeared from that node where you were connected to - therefore an error message is shown when try to return to VM - that´s not a fault: the machine belongs now to another node than before) \- Console: tries to open a HTML5 console \- Spice: opens a SPICE terminal (see below) \- Logout: ends the Proxmox session and returns to Log In form SPICE console ------------- For Android devices (preferred), you can use [SPICE](https://pve.proxmox.com/wiki/SPICE "SPICE") to get console access. In order to get this running, you need to purchase [Opaque](https://play.google.com/store/apps/details?id=com.undatech.opaque) ### How to use Opaque on Android * Purchase and install "Opaque" from Google Play * Make sure that your VM has a SPICE monitor configured (if not yet configured switch to standard view and change the VM configuration "Hardware" -> "Display" accordingly) * In web-browser: \- select the machine \- activate context menu (top right of VM´s window, see fig. 3) \- select "Spice" => file with access data will be downloaded (named pve-spice\[-n\].vv where "n" is a sequence number, starting with 1 if there are more than one file) * Open a file browser and select the just downloaded file and open it with "Opaque" Note: * Each access file can can only be used once - it will immediately be deleted after start of Opaque * On some devices opaque task has to be cancelled before starting a new session HTML5 Console ------------- If SPICE is not an option you can use an ordinary VNC client. In this case the VM configuration has to be adapted, look [here](https://pve.proxmox.com/wiki/Vnc_2.0#Enabling_Vnc_2.0_for_use_with_old_vnc_clients_.28Including_iOS_and_Android.29) for details. Security Consideration ---------------------- If you want to access Proxmox VE Mobile outside your LAN, you should use VPN and TFA to get maximum security. ### VPN To prevent unauthorized access, you should use a VPN to connect to your Proxmox VE hosts. ### Two-Factor Authentication Use [Two-Factor Authentication](https://pve.proxmox.com/wiki/Two-Factor_Authentication "Two-Factor Authentication") for secure login procedure. If your phone supports NFC, just use a Yubikey with NFC - easy to use and a quite secure one time password. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Proxmox\_VE\_Mobile&oldid=11364](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_VE_Mobile&oldid=11364) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Deploy Hyper-Converged Ceph Cluster" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Deploy Hyper-Converged Ceph Cluster" ======================================================== ← [Deploy Hyper-Converged Ceph Cluster](https://pve.proxmox.com/wiki/Deploy_Hyper-Converged_Ceph_Cluster "Deploy Hyper-Converged Ceph Cluster") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Deploy_Hyper-Converged_Ceph_Cluster#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Deploy_Hyper-Converged_Ceph_Cluster#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Deploy Hyper-Converged Ceph Cluster](https://pve.proxmox.com/wiki/Deploy_Hyper-Converged_Ceph_Cluster "Deploy Hyper-Converged Ceph Cluster") **: Displaying 2 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Deploy_Hyper-Converged_Ceph_Cluster&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Deploy_Hyper-Converged_Ceph_Cluster&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Deploy_Hyper-Converged_Ceph_Cluster&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Deploy_Hyper-Converged_Ceph_Cluster&limit=500) ) * [Main Page](https://pve.proxmox.com/wiki/Main_Page "Main Page") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Main+Page "Special:WhatLinksHere") ) * [Full Mesh Network for Ceph Server](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server "Full Mesh Network for Ceph Server") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Full+Mesh+Network+for+Ceph+Server "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Deploy_Hyper-Converged_Ceph_Cluster&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Deploy_Hyper-Converged_Ceph_Cluster&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Deploy_Hyper-Converged_Ceph_Cluster&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Deploy_Hyper-Converged_Ceph_Cluster&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Deploy\_Hyper-Converged\_Ceph\_Cluster](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Deploy_Hyper-Converged_Ceph_Cluster) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Upgrade a 4.x Installation using a newer ISO image - Proxmox VE Upgrade a 4.x Installation using a newer ISO image ================================================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Upgrade_a_4.x_Installation_using_a_newer_ISO_image#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Upgrade_a_4.x_Installation_using_a_newer_ISO_image#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Upgrade_a_4.x_Installation_using_a_newer_ISO_image#Introduction) * [2 Step by step upgrade process](https://pve.proxmox.com/wiki/Upgrade_a_4.x_Installation_using_a_newer_ISO_image#Step_by_step_upgrade_process) * [2.1 Create a mount point and update /etc/fstab accordingly](https://pve.proxmox.com/wiki/Upgrade_a_4.x_Installation_using_a_newer_ISO_image#Create_a_mount_point_and_update_/etc/fstab_accordingly) * [2.2 Mount the CD or an ISO image](https://pve.proxmox.com/wiki/Upgrade_a_4.x_Installation_using_a_newer_ISO_image#Mount_the_CD_or_an_ISO_image) * [2.3 Mount an empty directory over /media/cdrom/dev](https://pve.proxmox.com/wiki/Upgrade_a_4.x_Installation_using_a_newer_ISO_image#Mount_an_empty_directory_over_/media/cdrom/dev) * [2.4 Add a CD repository](https://pve.proxmox.com/wiki/Upgrade_a_4.x_Installation_using_a_newer_ISO_image#Add_a_CD_repository) * [2.5 Update and upgrade packages](https://pve.proxmox.com/wiki/Upgrade_a_4.x_Installation_using_a_newer_ISO_image#Update_and_upgrade_packages) * [2.6 Reboot](https://pve.proxmox.com/wiki/Upgrade_a_4.x_Installation_using_a_newer_ISO_image#Reboot) * [2.7 Cleanup: Remove the CD repository](https://pve.proxmox.com/wiki/Upgrade_a_4.x_Installation_using_a_newer_ISO_image#Cleanup:_Remove_the_CD_repository) Introduction ------------ If you have a valid subscription or you have enabled the "pve-no-subscription" repositories the upgrade process should be as easy as upgrading packages, i.e. apt-get update && apt-get dist-upgrade see Wiki article [Downloads](https://pve.proxmox.com/wiki/Downloads "Downloads") for exact steps for the upgrade of each releases, it is recommended to process according to it whenever possible. In exceptional cases, if you don't have access to internet but you have a 4.x ISO containing newer packages than your current 4.x installation you can use it to upgrade according the following example which describes an upgrade from 4.0 to 4.1. Step by step upgrade process ---------------------------- ### Create a mount point and update /etc/fstab accordingly mkdir /media/cdrom echo '/dev/sr0 /media/cdrom iso9660 noauto,ro 0 0' >> /etc/fstab # optional ### Mount the CD or an ISO image If you have a real CD/DVD or if running the Proxmox VE in another VM and using the ISO image: mount /dev/sr0 /media/cdrom or just (if you have an entry in the /etc/fstab): mount /media/cdrom If you have the downloaded ISO image: mount -o loop /path/to/proxmox-ve\_4.1-2f9650d4-21.iso /media/cdrom ### Mount an empty directory over /media/cdrom/dev Using apt-cdrom will fail while trying to scan /media/cdrom/dev/proc/self/fd directory. As a workaround create an empty file-system and mount it over /media/cdrom/dev: mkfs.cramfs /mnt /tmp/empty-image.img # /mnt being an empty directory mount -o loop /tmp/empty-image.img /media/cdrom/dev ls -l /media/cdrom/dev # shows an empty content ### Add a CD repository apt-cdrom --no-auto-detect --cdrom /media/cdrom --no-mount add This should scan the CD content, ask you for a name (use Proxmox 4.1) and add a repository in your /etc/apt/sources.list file. It creates also an entry in the /var/lib/apt/cdroms.list using the CD ID and given name. The content of the /var/lib/apt/cdroms.list should look like: CD::aa2253e1b6b98e93b17b38bef5b4d256-2 "Proxmox 4.1"; The added lines to the /etc/apt.sources.list should look like: deb cdrom:\[Proxmox 4.1\]/ jessie pve deb cdrom:\[Proxmox 4.1\]/proxmox/packages/ / ### Update and upgrade packages apt-get update && apt-get dist-upgrade ### Reboot systemctl reboot The packages should be updated from the CD/ISO image, a new kernel version should be 4.2.6-1-pve. ### Cleanup: Remove the CD repository You can disable or remove the CD repository by commenting out the corresponding lines in the /etc/apt/sources.list file, you can also remove the /var/lib/apt/cdroms.list file. Run apt-get update afterwards. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Upgrade\_a\_4.x\_Installation\_using\_a\_newer\_ISO\_image&oldid=9451](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_a_4.x_Installation_using_a_newer_ISO_image&oldid=9451) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Installation](https://pve.proxmox.com/wiki/Category:Installation "Category:Installation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Root Password Reset - Proxmox VE Root Password Reset =================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Root_Password_Reset#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Root_Password_Reset#searchInput) Contents -------- * [1 Resetting the root account password on the PVE Host](https://pve.proxmox.com/wiki/Root_Password_Reset#Resetting_the_root_account_password_on_the_PVE_Host) * [1.1 Method 1](https://pve.proxmox.com/wiki/Root_Password_Reset#Method_1) * [1.2 Method 2](https://pve.proxmox.com/wiki/Root_Password_Reset#Method_2) * [2 Resetting the root account password in a Container](https://pve.proxmox.com/wiki/Root_Password_Reset#Resetting_the_root_account_password_in_a_Container) * [3 References](https://pve.proxmox.com/wiki/Root_Password_Reset#References) Resetting the root account password on the PVE Host --------------------------------------------------- The following follows the general method for resetting a root password on a Linux machine, if you have access to the console see e.g.: * [the Debian Handbook](https://www.debian.org/doc/manuals/debian-reference/ch04.en.html#_securing_the_root_password) * [the Arch Linux Wiki entry](https://wiki.archlinux.org/title/Reset_lost_root_password) * [the entry in WikiBooks](https://en.wikibooks.org/wiki/Linux_Guide/Reset_a_forgotten_root_password) for similar suggestions. Keep in mind that editing the kernel command-line might need a different key-entry based on your boot-loader (`e` works for both `grub` and `systemd-boot` though). The method works for Proxmox VE until version 8.1 and should work for many other Linux based Operating systems as well: ### Method 1 * Boot into your bootloader (mostly `grub` or `systemd-boot`, select your preferred kernel but **do not press enter**. * Press **e** to go into **edit** mode. * Depending on the boot-loader go to the kernel-commandline entry: * For `grub`: scroll down to the `kernel` line you will boot from, it starts with `linux /vmlinuz-...` * For `systemd-boot` the kernel commandline is directly editable * Scroll to the end of that line, optionally remove the `quiet` in the line and append `init=/bin/bash` * For `grub` press `Ctrl X` to boot, for `systemd-boot` simply press Enter In the resulting shell: \# Remount / as Read/Write mount -o remount,rw / \# Change the root account password with passwd \# Change any other account password with passwd username \# type new password, confirm and hit enter and then reboot. ### Method 2 * Boot from a Live CD, which supports the `/` filesystem of your PVE installation (mostly relevant for installs on ZFS) (e.g. a Proxmox install ISO, in debug-mode (second debug-shell)) * Mount the `/` filesystem in read-write mode at a free directory (e.g.`/mnt` will be used in this example). * you might need to do other steps, based on the filesystem, e.g. `zpool import -f -R /mnt rpool` for ZFS. * Run `passwd -R /mnt` to set a new password for the `root` account. * Unmount/export the `/`\-filesystem and reboot. Resetting the root account password in a Container -------------------------------------------------- * Enter the working container and change the password using: pct enter passwd # enter new password in silent prompt exit * If you're still using OpenVZ containers, which are not supported in Proxmox VE 4 or newer, you can use `vzctl enter ` to enter the container. References ---------- * [Griffon's IT Library](http://c-nergy.be/blog/?p=1777) - [Cache](https://pve.proxmox.com/mediawiki/images/5/5a/Debian-PVE-root-Password-Reset_pdf.zip "Debian-PVE-root-Password-Reset pdf.zip") * [https://wiki.debian.org/Root](https://wiki.debian.org/Root) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Root\_Password\_Reset&oldid=11913](https://pve.proxmox.com/mediawiki/index.php?title=Root_Password_Reset&oldid=11913) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [System Administration](https://pve.proxmox.com/wiki/Category:System_Administration "Category:System Administration") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Solaris guest best practices - Proxmox VE Solaris guest best practices ============================ From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Solaris_guest_best_practices#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Solaris_guest_best_practices#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Solaris_guest_best_practices#Introduction) * [2 Solaris 10 up to 11.3](https://pve.proxmox.com/wiki/Solaris_guest_best_practices#Solaris_10_up_to_11.3) * [2.1 Known Issues](https://pve.proxmox.com/wiki/Solaris_guest_best_practices#Known_Issues) * [3 Solaris 11.4](https://pve.proxmox.com/wiki/Solaris_guest_best_practices#Solaris_11.4) Introduction ------------ This is a set of best practices when using Solaris in a VM. Solaris 10 up to 11.3 --------------------- These versions don't come with support for VirtIO out of the box. Use the following VM settings: * **Guest OS:** Solaris * **Disk:** SATA or IDE * **Network:** e1000 * **Machine-Type:** i440 ### Known Issues CPUs and cores are not detected properly. If you run `psrinfo -pv` or `mpstat`, it will detect sockets, but not all cores. Solaris 11.4 ------------ With Solaris 11.4, it will pick up the CPU cores correctly. Starting with SRU33 it comes with VirtIO drivers included. Therefore, if you install a new VM or upgrade from an older version, once you run 11.4 SRU33 or newer, you can use/switch to VirtIO devices. The following VM settings worked in our tests: * **Guest OS:** Solaris * **Disk:** VirtIO Block * **Network:** VirtIO * **Machine-Type:** Q35 To change the disk type of an already existing VM, _Detach_ it. It will then show up as `unused0`. Select and edit it. Then select _VirtIO Block_ as disk type, enable options like discard if wanted. Don't forget to adjust the _Boot Order_ in the _Options_ panel of the VM. Enable the `virtio` disk and move it to the top. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Solaris\_guest\_best\_practices&oldid=12186](https://pve.proxmox.com/mediawiki/index.php?title=Solaris_guest_best_practices&oldid=12186) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Qemu/KVM](https://pve.proxmox.com/wiki/Category:Qemu/KVM "Category:Qemu/KVM") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Ceph mClock Tuning - Proxmox VE Ceph mClock Tuning ================== From Proxmox VE (Redirected from [Ceph mclock tuning](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_mclock_tuning&redirect=no "Ceph mclock tuning") ) [Jump to navigation](https://pve.proxmox.com/wiki/Ceph_mclock_tuning#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Ceph_mclock_tuning#searchInput) With Ceph Quincy (17), the scheduler for OSD operations changed from _wpq_ to _mclock\_scheduler_. This brings some changes in how to tune an OSD, especially if the production performance is impacted by recovery or rebalance operations. The old methods of controlling how much performance is spent on backfilling and recovering are ignored by the _mclock\_scheduler_. These include parameters like _osd\_recovery\_sleep_ or _osd\_snap\_trim\_sleep_. Instead, it now uses profiles that define different types of operations, such as client or recovery. For each category, there are three basic parameters. A _limit_ of how many IOPS are allowed, as well as a _reservation_ to not starve it completely. For anything in between the limit and the reservation, a weight is used to balance the available IOPS between the different kind of operations. For more details, check out the Ceph documentation about the [Core Concepts of mclock\_scheduler](https://docs.ceph.com/en/latest/rados/configuration/osd-config-ref/#core-concepts) and the [mClock config reference](https://docs.ceph.com/en/latest/rados/configuration/mclock-config-ref/) . Contents -------- * [1 Check Current Scheduler](https://pve.proxmox.com/wiki/Ceph_mclock_tuning#Check_Current_Scheduler) * [2 Adjusting mClock Profile](https://pve.proxmox.com/wiki/Ceph_mclock_tuning#Adjusting_mClock_Profile) * [2.1 Example](https://pve.proxmox.com/wiki/Ceph_mclock_tuning#Example) * [3 Switch to Old Scheduler](https://pve.proxmox.com/wiki/Ceph_mclock_tuning#Switch_to_Old_Scheduler) * [3.1 ceph.conf](https://pve.proxmox.com/wiki/Ceph_mclock_tuning#ceph.conf) * [3.2 Config DB](https://pve.proxmox.com/wiki/Ceph_mclock_tuning#Config_DB) Check Current Scheduler ----------------------- To check which scheduler an OSD is using, run the following command: ceph config show-with-defaults osd. | grep op\_queue Adjusting mClock Profile ------------------------ If the default _[balanced](https://docs.ceph.com/en/latest/rados/configuration/mclock-config-ref/#built-in-profiles) _ profile does not prioritize client operations enough, consider switching to the _custom_ profile. This allows you to configure limits, reservations, and weights in more detail for the different types of operations. The following command will change it temporarily for all running OSDs. ceph tell osd.\* injectargs "--osd\_mclock\_profile=custom" To make it permanent, either configure it in the _ceph.conf_ file or in the config DB. The section [on switching to the old scheduler](https://pve.proxmox.com/wiki/Ceph_mclock_tuning#Switch_to_Old_Scheduler) has examples using a different parameter. Verify that the OSD is using the custom profile by running ceph config show-with-defaults osd. | grep mclock\_profile Then you can adjust the weight, limit and reservation for each type of operation (client, recovery, best-effort). The [available parameters](https://docs.ceph.com/en/latest/rados/configuration/mclock-config-ref/#mclock-config-options) are: * osd\_mclock\_scheduler\_client\_res * osd\_mclock\_scheduler\_client\_wgt * osd\_mclock\_scheduler\_client\_lim * osd\_mclock\_scheduler\_background\_recovery\_res * osd\_mclock\_scheduler\_background\_recovery\_wgt * osd\_mclock\_scheduler\_background\_recovery\_lim * osd\_mclock\_scheduler\_background\_best\_effort\_res * osd\_mclock\_scheduler\_background\_best\_effort\_wgt * osd\_mclock\_scheduler\_background\_best\_effort\_lim 'res' and 'lim' parameters are in IOPS while 'wgt' has no unit. You can try to weigh client OPs higher: ceph tell osd.\* injectargs "--osd\_mclock\_scheduler\_client\_wgt=4" Additionally, it could be useful to lower the limit and / or reservation for recovery OPs. To get the current values for these parameters, run: ceph config show-with-defaults osd. | grep mclock\_scheduler Run it against a few OSDs to get an idea how these values are. They will be a bit different for each OSD by default. To set them temporarily for all OSDs we use the `ceph tell osd.* injectargs` command. For example, to reduce the reservation for recovery OPs: ceph tell osd.\* injectargs "--osd\_mclock\_scheduler\_background\_recovery\_res={value}" If you want to apply a setting to only one specific OSD, use `osd.` instead of `osd.*`. It is still possible to adjust the number of backfills, [see Ceph docs](https://docs.ceph.com/en/latest/rados/configuration/mclock-config-ref/#recovery-backfill-options) . ℹ️ **Note**: The `res` and `lim` values are in IOPS up until Ceph version 17.2.6 ([archived docs](https://web.archive.org/web/20230127070453/https://docs.ceph.com/en/quincy/rados/configuration/osd-config-ref/#confval-osd_mclock_scheduler_background_recovery_res) ). From version 17.2.7 and 18.2.0 onward they are percent (0.0 to 1.0)! [(docs)](https://docs.ceph.com/en/latest/rados/configuration/osd-config-ref/#confval-osd_mclock_scheduler_background_recovery_res) ### Example Switch to the custom profile, increase client weight and pin background recovery IOPS. Which values for the background recovery limit and reservation work is something you need to find out. Maybe start a bit higher and if it is still impacting production, lower it. ceph tell osd.\* injectargs "--osd\_mclock\_profile=custom" ceph tell osd.\* injectargs "--osd\_mclock\_scheduler\_client\_wgt=4" ceph tell osd.\* injectargs "--osd\_mclock\_scheduler\_background\_recovery\_lim=0.1" ceph tell osd.\* injectargs "--osd\_mclock\_scheduler\_background\_recovery\_res=0.1" Switch to Old Scheduler ----------------------- For now, it is possible to use the old _wpq_ scheduler. At some point it the future, it will most likely be deprecated. To switch back, you need to set it either in the _ceph.conf_ file or in the config DB. ### ceph.conf Add the following section to the _ceph.conf_ file: \[osd\] osd\_op\_queue = wpq ### Config DB ceph config set osd osd\_op\_queue wpq Afterwards, a restart of the OSDs is needed. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Ceph\_mClock\_Tuning&oldid=11811](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_mClock_Tuning&oldid=11811) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # OpenVZ on ISCSI howto - Proxmox VE OpenVZ on ISCSI howto ===================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/OpenVZ_on_ISCSI_howto#mw-head) [Jump to search](https://pve.proxmox.com/wiki/OpenVZ_on_ISCSI_howto#searchInput) ℹ️ **Note**: Article about the old stable Proxmox VE 3.x releases Contents -------- * [1 OpenVZ on iSCSI](https://pve.proxmox.com/wiki/OpenVZ_on_ISCSI_howto#OpenVZ_on_iSCSI) * [1.1 Add the iSCSI target to the master server](https://pve.proxmox.com/wiki/OpenVZ_on_ISCSI_howto#Add_the_iSCSI_target_to_the_master_server) * [1.2 Set ISCSI to automatic connection](https://pve.proxmox.com/wiki/OpenVZ_on_ISCSI_howto#Set_ISCSI_to_automatic_connection) * [1.3 Setting up the LUN for OpenVZ](https://pve.proxmox.com/wiki/OpenVZ_on_ISCSI_howto#Setting_up_the_LUN_for_OpenVZ) * [1.4 Mounting the filesystem](https://pve.proxmox.com/wiki/OpenVZ_on_ISCSI_howto#Mounting_the_filesystem) * [1.5 Copying your containers and booting up](https://pve.proxmox.com/wiki/OpenVZ_on_ISCSI_howto#Copying_your_containers_and_booting_up) * [1.6 Setting up the cluster nodes](https://pve.proxmox.com/wiki/OpenVZ_on_ISCSI_howto#Setting_up_the_cluster_nodes) * [1.7 Testing migration out](https://pve.proxmox.com/wiki/OpenVZ_on_ISCSI_howto#Testing_migration_out) OpenVZ on iSCSI --------------- This is fairly straight forward to accomplish and also allows (offline) migration between Proxmox cluster nodes. Offline migration means there is a 5 second outage between being relocated to another node in the cluster. The phase 1 sync is done while online, the container is then shutdown, and phase 2 sync is completed and then the container is brought up on the other node. Of course this does depend on how long the services etc take to shutdown and how much data there is in the Phase 2 sync. So don't quote me on the times :) (The time mentioned was for a DNS,DHCP,File Server I've tested personally). This assumes you have already setup a cluster, and SAN. Also this setup example is for a 3 node cluster. So if you have more nodes or only 1, just use your brains to work it out from this example. **NOTE:** OpenVZ cannot share the same [LUN](http://en.wikipedia.org/wiki/Logical_Unit_Number) (Logical\_Unit\_Number) on different nodes. So you need ONE LUN PER CLUSTER NODE. You can however have as many containers per node/LUN. For example: * Master node0 connects to - LUN1 - 10 containers * Cluster node1 connects to - LUN2 - 5 containers * Cluster node2 connects to - LUN3 - 40 containers * Etc.......... You can also run KVM instances at the same time however they require their OWN LUN's ### Add the iSCSI target to the master server * Before you do this lets get a look at our system devices * Open an SSH connection to the Proxmox Master Node. * Run fdisk -l so we have a before and after view of system devices. You will end up with something similar to the following. Make a note of what are your local system devices so you know what is there already. This goes for whether you have existing SAN connections or not - it's best to know what the system looks like so you can see what devices are added and easily reference them later. ie: /dev/sda1; /dev/sda2 etc prox:~# fdisk -l Disk /dev/sda: 8589 MB, 8589934592 bytes 255 heads, 63 sectors/track, 1044 cylinders Units = cylinders of 16065 \* 512 = 8225280 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 \* 1 66 524288 83 Linux Partition 1 does not end on cylinder boundary. /dev/sda2 66 1044 7861610 8e Linux LVM Disk /dev/dm-0: 1073 MB, 1073741824 bytes 255 heads, 63 sectors/track, 130 cylinders Units = cylinders of 16065 \* 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-0 doesn't contain a valid partition table Disk /dev/dm-1: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders Units = cylinders of 16065 \* 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-1 doesn't contain a valid partition table Disk /dev/dm-2: 3758 MB, 3758096384 bytes 255 heads, 63 sectors/track, 456 cylinders Units = cylinders of 16065 \* 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-2 doesn't contain a valid partition table * Go to the web interface for Proxmox and add the iSCSI target under storage. * If you have multiple targets ensure you add each target for all the LUN's you need. ### Set ISCSI to automatic connection * Now Edit the iSCSI node config file per instance of target/lun you have added. For mine I have a single target, with all LUNS being used by openVZ availble on that single target. If you like to use one target per LUN that can also be done, but just make sure you edit each node config file as follows: nano -w /etc/iscsi/node/iqn\_for\_your\_node\_here/IP\_Address\_and\_port\_here/default You should end up with something like this - you can hit tab of course to help you with this path as you are entering it: nano -w /etc/iscsi/nodes/iqn.2006-01.com.openfiler\\:tsn.672802aca9d8/10.5.0.6\\,3260\\,1/default * Near the top of the file change node.startup to automatic node.startup = automatic * Near the bottom change node.conn\[0\] to automatic node.conn\[0\].startup = automatic * Exit and save the file. * Restart the open-iscsi service with the following command: prox1:#/etc/init.d/open-iscsi restart Disconnecting iSCSI targets:Logging out of session \[sid: 1, target: iqn.2006-01.com.openfiler:tsn.672802aca9d8, portal:10.5.0.6,3260\] Logout of \[sid: 1, target: iqn.2006-01.com.openfiler:tsn.672802aca9d8, portal: 10.5.0.6,3260\]: successful Stopping iSCSI initiator service:. Starting iSCSI initiator service: iscsid. Setting up iSCSI targets: Logging in to \[iface: default, target: iqn.2006-01.com.openfiler:tsn.672802aca9d8, portal: 10.5.0.6,3260\] Login to \[iface: default, target: iqn.2006-01.com.openfiler:tsn.672802aca9d8, portal: 10.5.0.6,3260\]: successful Mounting network filesystems:. **NOTE:**I have noticed that sometimes this is changed automatically back to manual. It is important to have this set to automatic if you have any servers set to boot at startup. It is also important to check this file on ALL cluster nodes to ensure they are also set, because the file replicates it with the setting as manual. SO this needs to be completed on each cluster node! * This config file is also where you setup authentication for iscsi targets if you are using CHAP authentication (not recommended) ### Setting up the LUN for OpenVZ * First confirm that the LUN you are wanting to use for this cluster node is now available to the system with fdisk -l. Your output should now look something like the following: prox:# fdisk -l Disk /dev/sda: 8589 MB, 8589934592 bytes 255 heads, 63 sectors/track, 1044 cylinders Units = cylinders of 16065 \* 512 = 8225280 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 \* 1 66 524288 83 Linux Partition 1 does not end on cylinder boundary. /dev/sda2 66 1044 7861610 8e Linux LVM Disk /dev/dm-0: 1073 MB, 1073741824 bytes 255 heads, 63 sectors/track, 130 cylinders Units = cylinders of 16065 \* 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-0 doesn't contain a valid partition table Disk /dev/dm-1: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders Units = cylinders of 16065 \* 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-1 doesn't contain a valid partition table Disk /dev/dm-2: 3758 MB, 3758096384 bytes 255 heads, 63 sectors/track, 456 cylinders Units = cylinders of 16065 \* 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-2 doesn't contain a valid partition table Disk /dev/sdb: 176.1 GB, 176160768000 bytes 255 heads, 63 sectors/track, 21416 cylinders Units = cylinders of 16065 \* 512 = 8225280 bytes Disk identifier: 0xf2cc6ee0 Disk /dev/sdb doesn't contain a valid partition table Disk /dev/sdc: 176.1 GB, 176160768000 bytes 255 heads, 63 sectors/track, 21416 cylinders Units = cylinders of 16065 \* 512 = 8225280 bytes Disk identifier: 0xf8fa13a9 Disk /dev/sdc doesn't contain a valid partition table Disk /dev/sdd: 176.1 GB, 176160768000 bytes 255 heads, 63 sectors/track, 21416 cylinders Units = cylinders of 16065 \* 512 = 8225280 bytes Disk identifier: 0xd1403fdb Disk /dev/sdd doesn't contain a valid partition table As you can see from the above output /dev/sdb; /dev/sdc; & /dev/sdd have been added to my system. These are the 3 LUNS (1 per node) that we will be adding. **NOTE:** The disk identifiers MAY also appear as 0000000000 until you create the partitions and file system as detailed below. To make it clear they will be used as follows: /dev/sdb - prox (cluster node 1) /dev/sdc - prox1 (cluster node 2) /dev/sdd - prox2 (cluster node 3) * So now we know what device we will be using for node 1 we do the following to create a partition on it: prox1:#fdisk /dev/sdb Type 'n' and press enter to create a new partition Type 'p' and enter for primary partition Type '1' and enter for the 1st (and only) partition Press enter to accept the default start cylinder Press enter to accept the default end cylinder Type 't' and enter to set the system type Type '83' and enter to set it as Linux Type 'w' and enter to save changes and exit * Now create the file system on the partition you just created by running: prox1:#mkfs.ext3 /dev/sdb1 (Obviously set the /dev/???1 to whatever your device is in your system) You should see similar to the following output: prox1:# mkfs.ext3 /dev/sdb1 mke2fs 1.41.3 (12-Oct-2008) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 10756096 inodes, 43005997 blocks 2150299 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=4294967296 1313 block groups 32768 blocks per group, 32768 fragments per group 8192 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872 Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 38 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. * Repeat creating the partition and filesystem on any other LUNS you will be using for openvz on other cluster nodes. This is so we can obtain the disk identifier and easily reference what disk is being used in what system. * Running fdisk -l now will look something like this for the example 3 LUNS: Disk /dev/sdb: 176.1 GB, 176160768000 bytes 255 heads, 63 sectors/track, 21416 cylinders Units = cylinders of 16065 \* 512 = 8225280 bytes Disk identifier: 0xf2cc6ee0 Device Boot Start End Blocks Id System /dev/sdb1 1 21416 172023988+ 83 Linux Disk /dev/sdc: 176.1 GB, 176160768000 bytes 255 heads, 63 sectors/track, 21416 cylinders Units = cylinders of 16065 \* 512 = 8225280 bytes Disk identifier: 0xf8fa13a9 Device Boot Start End Blocks Id System /dev/sdc1 1 21416 172023988+ 83 Linux Disk /dev/sdd: 176.1 GB, 176160768000 bytes 255 heads, 63 sectors/track, 21416 cylinders Units = cylinders of 16065 \* 512 = 8225280 bytes Disk identifier: 0xd1403fdb Device Boot Start End Blocks Id System /dev/sdd1 1 21416 172023988+ 83 Linux **NOTE:** Make a note of the disk identifiers as these will be the same on all 3 nodes, but the /dev/???1 device mount point can change. ### Mounting the filesystem * Now you can mount the filesystem you have just created. As we are wanting to use the iSCSI to hold openVZ containers we will have to remount the local copy to another folder. So first create a folder \# mkdir /var/lib/vz1 (or whatever name you want to give it) * Now we open up fstab and edit the local mount and add in our iscsi mount point \# nano -w /etc/fstab * You will see a line similar or the same as this near the top of the file: /dev/pve/data /var/lib/vz ext3 defaults 0 1 CHANGE that to point to the new folder you just created - for example: /dev/pve/data /var/lib/vz1 ext3 defaults 0 1 * At the bottom of the file you will need to add in the following line: /dev/sdb1 /var/lib/vz ext3 defaults,auto,\_netdev 0 0 **Note:** Obviously change the /dev/???1 to whatever device is in your system * Now exit and save the file * At this point **ENSURE** there are **NO VZ** containers running * Now run umount /var/lib/vz and mount -a prox1:#umount /var/lib/vz prox1:# prox1:#mount -a prox1:# **Note:** You don't want to see errors at this point, or any feedback at this point otherwise you've done something wrong * If successfull you can now look at the filesystems mounted in your server with: prox1:#df -h You will see something similar to this: prox1:#/etc/qemu-server# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/pve-root 17G 5.3G 11G 34% / tmpfs 16G 0 16G 0% /lib/init/rw udev 10M 616K 9.4M 7% /dev tmpfs 16G 0 16G 0% /dev/shm /dev/mapper/pve-data 38G 4.7G 34G 13% /var/lib/vz1 /dev/sda1 504M 31M 448M 7% /boot 172.15.241.29:/mnt/luns/nfs/ISO 24G 172M 23G 1% /mnt/pve/ISO /dev/sdb1 162G 188M 154G 1% /var/lib/vz Notice how the local disk is now mounted to the new location and the iscsi is mounted to the default openVZ folder ### Copying your containers and booting up * Now that you have the filesystem mounted and setup correctly you can now copy the local openVZ files along with any existing containers into the /var/lib/vz folder. Complete this step even if you have no existing containers as the file structure and system files are still required to exist BEFORE you start adding them like you would normally via the proxmox web interface. prox1:#cp -vpr /var/lib/vz1/. /var/lib/vz/. - this will recursively copy all existing data across to the SAN If you want to confirm that this is actually happening you can simply run the df -h command and you will see the Used and Avail sizes changing for /dev/???1 ### Setting up the cluster nodes * As we have now (in steps 2 & 3) already partitioned and created the filesytem for the other LUNs, you only need to repeat steps 4 & 5 on any of your cluster nodes. Just ensure that for each node you are setting up that you change the relevant commands and config files to point to the correct device for each node. **NOTE:** If you are adding new LUNs then of course you will need to repeat all steps Each server **MIGHT** mount the devices in a different order or with different names **SO ALWAYS CHECK THE DISK IDENTIFIER TO ENSURE YOU ARE FORMATTING THE CORRECT LUN** In this example I have 3 nodes in total, so I will use the following /dev/sdb1 - lun0 - master cluster node 0 /dev/sdc1 - lun1 - cluster node 1 /dev/sdd1 - lun2 - cluster node 2 ### Testing migration out * Once you have setup **all** nodes successfully!! you can then start migrating to your hearts content * Only offline migrations work. But as stated there is minimal downtime even for offline migrations * Things to consider 1\. There is significant network and cpu overhead while migrating containers because this is NOT a shared filesystem as in KVM. So ALL data for the container you are migrating is copied from one LUN to the other LUN via the host nodes you are migrating from and to, if you do this via the Proxmox gui. 2\. vzmigrate is the script that is used to migrate the containers from one node to the other, however by default it removes the source container from the current host after migrating. Instead of doing this via the gui you can run the rsync command manually with a custom script that accepts a from and to vraiable which runs rsync, then vzctl stop, then a final rsync, then vzctl start. This is effectively what an offline vzmigrate does, but of course if you do this manually then you are only synchronising changes not the entire folder and therefore you are significantly reducing network and cpu load in the process. **NOTE:** This is only for containers that you might frequently want to move from one cluster node to another. For example less critical services that may spike in load at times and impact more critical services on that node. If say after hours you synch containers that are candidates for frequent migration, then during critical times it would take only a matter of seconds potentially to migrate the container (with little to no impact on other more critical services), instead of minutes (with severe impact on other servers due to high network and cpu load) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=OpenVZ\_on\_ISCSI\_howto&oldid=9243](https://pve.proxmox.com/mediawiki/index.php?title=OpenVZ_on_ISCSI_howto&oldid=9243) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Proxmox VE 3.x](https://pve.proxmox.com/wiki/Category:Proxmox_VE_3.x "Category:Proxmox VE 3.x") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Editing corosync.conf" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Editing corosync.conf" ========================================== ← [Editing corosync.conf](https://pve.proxmox.com/mediawiki/index.php?title=Editing_corosync.conf&action=edit&redlink=1 "Editing corosync.conf (page does not exist)") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Editing_corosync.conf#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Editing_corosync.conf#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Editing corosync.conf](https://pve.proxmox.com/mediawiki/index.php?title=Editing_corosync.conf&action=edit&redlink=1 "Editing corosync.conf (page does not exist)") **: Displaying 2 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Editing_corosync.conf&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Editing_corosync.conf&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Editing_corosync.conf&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Editing_corosync.conf&limit=500) ) * [Fencing](https://pve.proxmox.com/wiki/Fencing "Fencing") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Fencing "Special:WhatLinksHere") ) * [Multicast notes](https://pve.proxmox.com/wiki/Multicast_notes "Multicast notes") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Multicast+notes "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Editing_corosync.conf&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Editing_corosync.conf&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Editing_corosync.conf&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Editing_corosync.conf&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Editing\_corosync.conf](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Editing_corosync.conf) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Certified Appliance: CYAN Secure Web - Proxmox VE Certified Appliance: CYAN Secure Web ==================================== From Proxmox VE Redirect page [Jump to navigation](https://pve.proxmox.com/wiki/Certified_Appliance:_CYAN_Secure_Web#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Certified_Appliance:_CYAN_Secure_Web#searchInput) Redirect to: * [CYAN Secure Web](https://pve.proxmox.com/mediawiki/index.php?title=CYAN_Secure_Web&action=edit&redlink=1 "CYAN Secure Web (page does not exist)") Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Certified\_Appliance:\_CYAN\_Secure\_Web&oldid=355](https://pve.proxmox.com/mediawiki/index.php?title=Certified_Appliance:_CYAN_Secure_Web&oldid=355) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # File System level backups with LVM snapshots - Proxmox VE File System level backups with LVM snapshots ============================================ From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#mw-head) [Jump to search](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#Introduction) * [2 Requirements](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#Requirements) * [2.1 Tools needed on target Windows host](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#Tools_needed_on_target_Windows_host) * [3 Procedure](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#Procedure) * [3.1 Create "**backup**" user](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#Create_%22backup%22_user) * [3.2 Install **Cygwin** as backup user](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#Install_Cygwin_as_backup_user) * [3.3 **cyg\_server** user setup](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#cyg_server_user_setup) * [3.4 **ssh service** setup.](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#ssh_service_setup.) * [3.5 ssh client setup](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#ssh_client_setup) * [3.6 "Forced command" setup](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#%22Forced_command%22_setup) * [3.7 Host scripts](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#Host_scripts) * [3.8 PVE scripts](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#PVE_scripts) * [4 Utilities](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#Utilities) * [5 Host scripts configuration](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#Host_scripts_configuration) * [5.1 **host.conf** file](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#host.conf_file) * [5.2 Setup of optional commands to run before and after the snapshot](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#Setup_of_optional_commands_to_run_before_and_after_the_snapshot) * [5.3 Snapshot testing](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#Snapshot_testing) * [6 Test acl backup from remote BackupPC host](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#Test_acl_backup_from_remote_BackupPC_host) * [7 BackupPC host configuration](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#BackupPC_host_configuration) * [7.1 **Xfer**](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#Xfer) * [7.2 **Backup Settings**](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#Backup_Settings) * [8 Verify cyg\_server permissions](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#Verify_cyg_server_permissions) * [9 Backuppc-snap download page](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#Backuppc-snap_download_page) Introduction ============ The general idea consists in combining an external tool which is able to do filesystem level incremental backups ( rsync by means of [BackupPC](http://backuppc.sourceforge.net/) in this document) with the possibility to take snapshots of LVM based storage of virtual machines. Main constraints in designing this solution were: * Do not change fundamentally the configuration of an host under BackupPC * Preserve easy interactive restore directly on the host. Basically the target host, when a backup is required via ssh connection, instead of directly executing the rsync command, intercepts it and runs a script ("[forced command](https://binblog.info/2008/10/20/openssh-going-flexible-with-forced-commands/) ") which: 1. Prepares backup operations (for instance, save ACL in case of Windows host) 2. Stops or Suspends services which can do important changes on filesystem, or require a logical consistency on filesystem (e.g: Databases). 3. Triggers a snapshot of his own storage on PVE host it is runnng on. 4. Revert machine to normal operating state. 5. Redirects original rsync command towards PVE hosts and the snapshot. * Redirected rsync runs on PVE: mount fs, optionally save MBR and PBS, save ntfs metadata for Windows hosts, run rsync. 6. Triggers snapshot snapshot removal on PVE. [![](https://pve.proxmox.com/mediawiki/images/8/87/Backuppc-snap-schema.png)](https://pve.proxmox.com/wiki/File:Backuppc-snap-schema.png) During interactive restore, instead, rsync process runs directly on the host. In the following paragraphs you will find detailed configuration steps for a Windows host. Requirements ============ * Local user "backup", member of Administrators and Backup Operators Tools needed on target Windows host ----------------------------------- * [CYGWIN](http://www.cygwin.com/) * sshd * rsync * iconv * subversion (used for script update) * vim * [SetACL](http://helgeklein.com/setacl/) * [Sync](http://technet.microsoft.com/en-us/sysinternals/bb897438) [Proxmox Backup Server](https://pve.proxmox.com/wiki/Storage:_Proxmox_Backup_Server "Storage: Proxmox Backup Server") (PBS) is another facility. * PBS 1.x was only introduced with PVE 6.x * PBS 2.x with PVE 7.x * So PVE 5.x and earlier doesn't know that yet. Procedure ========= Create "**backup**" user ------------------------ * Add "backup" user to "Administrators" and "Backup Operators" groups. * Connect to the host as "backup" user. * If you have quotes activated for some disk, check that "backup" entry is "no limit" (interactively restored files are initially owned by this user.). Install **Cygwin** as backup user --------------------------------- * Create C:\\cygwin folder * Copy from another server c:\\cygwin\\cygwin-data folder (or install from the net if this is the first host configured). * Copy locally and run as backup the Cygwin install file "Setup.exe" * Install for all users * Leave default setup (c:\\cygwin) for root cygwin folder. * Set local folder as repository and use c:\\cygwin\\cygwin-data as source. * Add following packages: * **openssh** * **rsync** (**NOTE:** install **3.0.7**; **3.0.8** is problematic.) * **libiconv** * **libiconv2** * **subversion** * **vim** * Proceed, accepting Desktop and Start menu shortcuts creation. * Enter bash shell using Desktop icon; wait default settings creation for "backup" user; exit bash shell. **cyg\_server** user setup -------------------------- **NOTE:** Skip this step for Windows XP hosts; in that case sshd will run with system account privileges. * Create a domain level user with Administrator privileges called **cyg\_server** , this user will run sshd service. (You can use another existing user, providing it to the sshd service configuration script below when asked). * Reconnect to the host with a Domain Administrator account; enter bash, and run: mkpasswd -l -d | grep cyg\_server >> /etc/ which adds in /etc/passwd cygwin file an entry for domain user **cyg\_server**, ssh daemon will run with this user account. * Add cyg\_server to local Administrators. * **NOTE:** It's important to check that cyg\_server is listed as Domain Administrator in /etc/passwd, and that the same user is a local Administrator, before proceeding with following steps. **ssh service** setup. ---------------------- * Reconnect as local "backup" user. * Run from bash "**ssh-host-config**" script; see in the following section the responses to various requests ("\*\*\* Query:" sections). $ ssh-host-config \*\*\* Query: Overwrite existing /etc/ssh\_config file? (yes/no) **yes** \*\*\* Info: Creating default /etc/ssh\_config file \*\*\* Query: Overwrite existing /etc/sshd\_config file? (yes/no) **yes** \*\*\* Info: Creating default /etc/sshd\_config file \*\*\* Info: Privilege separation is set to yes by default since OpenSSH 3.3. \*\*\* Info: However, this requires a non-privileged account called 'sshd'. \*\*\* Info: For more info on privilege separation read /usr/share/doc/openssh/README.privsep. \*\*\* Query: Should privilege separation be used? (yes/no) **yes** \*\*\* Info: Note that creating a new user requires that the current account have \*\*\* Info: Administrator privileges. Should this script attempt to create a \*\*\* Query:new local account 'sshd'? **yes** \*\*\* Info: Updating /etc/sshd\_config file \*\*\* Warning: The following functions require administrator privileges! \*\*\* Query: Do you want to install sshd as a service? \*\*\* Query: (Say "no" if it is already installed as a service) (yes/no) **yes** \*\*\* Query: Enter the value of CYGWIN for the daemon: \[\] **ntsec** \*\*\* Info: On Windows Server 2003, Windows Vista, and above, the \*\*\* Info: SYSTEM account cannot setuid to other users -- a capability \*\*\* Info: sshd requires. You need to have or to create a privileged \*\*\* Info: account. This script will help you do so. \*\*\* Info: You appear to be running Windows XP 64bit, Windows 2003 Server, \*\*\* Info: or later. On these systems, it's not possible to use the LocalSystem \*\*\* Info: account for services that can change the user id without an \*\*\* Info: explicit password (such as passwordless logins \[e.g. public key\ \*\*\* Info: authentication\] via sshd). \*\*\* Info: If you want to enable that functionality, it's required to create \*\*\* Info: a new account with special privileges (unless a similar account \*\*\* Info: already exists). This account is then used to run these special \*\*\* Info: servers. \*\*\* Info: Note that creating a new user requires that the current account \*\*\* Info: have Administrator privileges itself. \*\*\* Info: This script plans to use 'cyg\_server'. \*\*\* Info: 'cyg\_server' will only be used by registered services. \*\*\* Query: Do you want to use a different name? (yes/no) **no** \*\*\* Info: Please enter a password for new user cyg\_server. Please be sure \*\*\* Info: that this password matches the password rules given on your system. \*\*\* Info: Entering no password will exit the configuration. \*\*\* Query: Please enter the password: \*\*\* Query: Reenter: \*\*\* Info: Also keep in mind that the user 'cyg\_server' needs read permissions \*\*\* Info: on all users' relevant files for the services running as 'cyg\_server'. \*\*\* Info: In particular, for the sshd server all users' .ssh/authorized\_keys \*\*\* Info: files must have appropriate permissions to allow public key \*\*\* Info: authentication. (Re-)running ssh-user-config for each user will set \*\*\* Info: these permissions correctly. \[Similar restrictions apply, for\ \*\*\* Info: instance, for .rhosts files if the rshd server is running, etc\]. **NOTE:** In some cases (probably if you forgot to add cyg\_server to local Administrators), errors like following could happen: \*\*\* Warning: cyg\_server is in /etc/passwd, but the local \*\*\* Warning: machine's SAM does not know about cyg\_server. \*\*\* Warning: Perhaps cyg\_server is a pre-existing domain account. \*\*\* Warning: Continuing, but check if this is ok. In that case, [verify cyg\_server permissions](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#Verify_cyg_server_permissions) as shown at the end of this document. * Start ssh service net start sshd ssh client setup ---------------- * Copy from another backup host the ssh backup key scp :/home/backup/id\_rsa\_backup /home/backup/ All virtual machines connect to PVE hosts with the same key (generic access with this key is filtered with a forced command on PVE). * Connect with this key to all (already [configured](https://pve.proxmox.com/wiki/File_System_level_backups_with_LVM_snapshots#PVE_scripts) , otherwise you will obtain a normal root shell) PVE nodes, after accepting pve ssh public key insertion in ~/.ssh/known\_hosts file. The result should be always: $ ssh -i id\_rsa\_backup -l root pve1 Rejected Connection to pve1 closed. If you try to send qm status 101 (assuming that 101 is the ID of a VM running on pve1) command, instead: $ ssh -i id\_rsa\_backup -l root pve1 'qm status 101' status: running This confirms that ssh forced comman on PVE side works as expected. "Forced command" setup ---------------------- Edit ~/.ssh/authorized keys, adding forced command for backup connections: command="/home/backup/backup-restore" ssh-rsa AAAAB3Nza... where AAAAB3Nza... is the remote backuppc user public key. Host scripts ------------ Download [vm side](https://webapps.comune.trento.it/backuppc-snap/backup-host.tgz) scripts (updated October 30 2012) and extract them inside /home/backup directory. PVE scripts ----------- * Download [PVE side](https://webapps.comune.trento.it/backuppc-snap/pve-host.tgz) scripts (updated October 30 2012) and extract them in a directory of your choice (e.g.: /opt/snap) * Configure forced command inside PVE "authorized\_keys" file: command="/opt/snap/snap-backup-restore" ssh-rsa AAAAB3NzaC1... where AAAAB3Nza... is the public counterpart of the id\_rsa\_backup configured on virtual machines. **NOTE:** Take care that /opt/snap/snap-backup-restore is the correct location of the snapshot master script. * You will need on PVE also a recent version of **ntfs-3g** (Debian Squeeze package is currently too old, Wheezy version is ok), and the **attr** package. Utilities ========= * Copy in a directory of your choice (scripts are configured with C:\\App\\Scripts\\bin\\ by default) the executable **SetACL.exe** * It's the Open Source tool that takes care of backup and iteractive restore of Windows ACL. * Copy in a directory of your choice (scripts are configured with C:\\App\\Scripts\\bin\\ by default ) the executable **sync.exe** * **N.B.**: sync.exe is NOT Open Source software, and you need to execute it the first time from GUI for aknowledging the EULA; Host scripts configuration ========================== **host.conf** file ------------------ * Edit **/home/backup/host.conf** backup configuration file. (You can rename ad edit **host.conf.tpl**). There is one line, uncommented, listing the hostnames of PVE nodes in the cluster, and multiple lines, **which are to be left commented**, one per disk (partition) subject to backup: * Example (for hypotetical host-to-backup host): PVE\_LIST="pve1 pve2 pve3" #VMID DISK PART FSTYPE RELATIVE\_MP STORAGE MBR\_SAVE SNAP\_SIZE(MB) MP\_PREFIX #101 1 1 ntfs /cygdrive/c/ lvmstorage mbryes 30%FREE #101 1 1 ntfs /cygdrive/d/ lvmstorage mbrno 1000 Where: * **PVE\_LIST** is the list of DNS hostnames for PVE cluster host-to-backup is running into. * **VMID** is the Virtual machine ID inside cluster PVE. * **DISK** is the disk number (inside PVE VM configuration 101.conf) * **PART** is the one-based partition number in DISK * **FSTYPE** is the filesystem type; it's the value that will be used as "-t" flag of "mount" command for mounting snapshot filesystem on PVE. * **RELATIVE\_MP** it's the mount point relative to the directory on PVE ( /tmp// ) reserved for snapshots; . * **STORAGE** is the storage name in PVE containing DISK. **IMPORTANT**: If your STORAGE is an LVM Group, and its name is different, **use the Volume Group name here**. If you use the predefined "local" storage, a snapshot of the 'data' LV will be made, inside the 'pve' VG. * **MBR\_SAVE** tells if to save Master Boot Record (mbryes) for the disk or not (mbrno). * **SNAP\_SIZE(MB)** it's the snapshot size as a percentage of free space inside the Volume Group DISK is part of; es: 30%FREE. It is also possible to set a fixed size in Megabytes. * **MP\_PREFIX** Is an optional mount point prefix; useful on linux hosts for making mount points independent. **NOTE:** trailing slash in RELATIVE\_MP is important. Setup of optional commands to run before and after the snapshot --------------------------------------------------------------- * Create tasks file; copy and modify from template: cp tasks.tpl tasks inserting commands inside tasks\_before() and tasks\_after() functions. If you want to stop a Lotus Domino service before the snapshot and start it after, for example: #!/bin/bash tasks\_before() { echo "Stopping Lotus Domino..." net stop "Lotus Domino Server (LotusDominodata)" } tasks\_after() { echo "Starting Lotus Domino..." net start "Lotus Domino Server (LotusDominodata)" } Snapshot testing ---------------- * cd inside backup scripts root: cd /home/backup * **create** a snapshot for /cygdrive/c/ drive: ./snap.sh create /cygdrive/c/ * **remove** it: ./snap.sh remove /cygdrive/c/ **NOTE**: optional commands before and after snapshot are skipped by default; for a complete test set variabile NO\_TASKS to false inside snap.sh. Test acl backup from remote BackupPC host ========================================= * Connect to BackupPC host and run: \# su - backuppc assuming backuppc user identity * Try to connect to target host, adding it to known\_hosts answering **yes** to the related question. Then, generic ssh should be Rejected: ssh backup@host-to-backup Rejected Connection to host-to-backup closed. this is OK. * Test acl backup funcion: ssh -q -x -l backup acl-backup "" **For example**, for /cygdrive/c/ on host-to-backup: ssh -q -x -l backup host-to-backup acl-backup "/cygdrive/c" Check that **.acl.bak** and **acl.bak.err** files are correctly created; .acl.bak.err content is "0" if acl saving is ok. **NOTE:** In some cases it is necessary to modify /etc/bashrc cygwin file on the target host, moving following lines: \# If not running interactively, don't do anything \[\[ "$-" != \*i\* \]\] && return to the beginning of file, just before: \# Check that we haven't already been sourced. (\[\[ -z ${CYG\_SYS\_BASHRC} \]\] && CYG\_SYS\_BASHRC="1") || return This avoids standard output pollution when rsync is redirected, causing a lock in rsync operation. A symptom is the presence of lines like the followings in BackupPC host log, after having manually killed the backup job: Executing DumpPreShareCmd: /usr/bin/ssh -q -x -l backup host-to-backup acl-backup "/cygdrive/d" incr backup started back to 2011-11-15 10:39:20 (backup #0) for directory /cygdrive/d Running: /usr/bin/ssh -q -x -l backup host-to-backup /usr/bin/rsync-backup --server --sender --numeric-ids --perms --owner --group -D --links --hard-links --times --block-size=2048 --recursive --one-file-system . /cygdrive/d/ Xfer PIDs are now 19432 Got remote protocol 1668572463 Fatal error (bad version): /etc/bash.bashrc: line 13: 5028 Aborted ( \[\[ -z ${CYG\_SYS\_BASHRC} \]\] && CYG\_SYS\_BASHRC="1" ) BackupPC host configuration =========================== * Connect to BackupPC host. * Add target DNS host name to "**Edit Hosts**" section , indicating authorized users. * Move in "**Hosts Summary**"; the new machine will be listed as "Host without backups". Select the link of the machine. * Select "**Edit Config**" for the machine. **NOTE:** **Pay attention** to not select by mistake the global"**Edit Config**" in "**Server**" section below. **Xfer** -------- * Set in "**RsyncShareName**" the paths to save ("shares" in BackupPC terminology); for Windows machine use Cygwin syntax, paths will start everytime with /cygdrive/; eg: /cygdrive/c. * Set Exclusions: ("**BackupFilesExclude**"); share name is the prefix, and after that relative paths to exclude. For windows hosts, for example, under /cygdrive/c you may want to exclude pagefile.sys and hiberfil.sys * Set "**RsyncClientCmd**" * Modify default ssh user from root to backup. * Add "\-backup" suffix to "$rsyncPath"; you will read then "$rsyncPath-backup". The final configuration will be: $sshPath -q -x -l backup $host $rsyncPath-backup $argList+ * Set "**RsyncClientRestoreCmd**" * Modify default ssh user from root to backup. * Add "\-restore" suffix to "$rsyncPath"; you will read then "$rsyncPath-restore". The final configuration will be: $sshPath -q -x -l backup $host $rsyncPath-restore $argList+ **Backup Settings** ------------------- * Insert in "**DumpPreShareCmd**" the following command for saving ACL before every backup (it is the formerly tested command): $sshPath -q -x -l backup $host acl-backup "$share" * Insert in "**RestorePostUserCmd**" the following command which sets ACL after every restore: $sshPath -q -x -l backup $host acl-restore "$share" "$pathHdrSrc" "$pathHdrDest" "$fileList" Do other configurations as usual. * * * Verify cyg\_server permissions ============================== **cyg\_server** user should have the following permissions: SeTcbPrivilege SeCreateTokenPrivilege SeAssignPrimaryTokenPrivilege SeServiceLogonRight For verifying run: $ editrights -u cyg\_server -l In case of missing permissions, add them: editrights -a SeTcbPrivilege -u cyg\_server editrights -a SeCreateTokenPrivilege -u cyg\_server editrights -a SeAssignPrimaryTokenPrivilege -u cyg\_server editrights -a SeServiceLogonRight -u cyg\_server * * * Backuppc-snap download page =========================== Download the scripts from [this page](https://webapps.comune.trento.it/backuppc-snap/) . Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=File\_System\_level\_backups\_with\_LVM\_snapshots&oldid=11481](https://pve.proxmox.com/mediawiki/index.php?title=File_System_level_backups_with_LVM_snapshots&oldid=11481) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Certified Appliance: Proxmox Mail Gateway - Proxmox VE Certified Appliance: Proxmox Mail Gateway ========================================= From Proxmox VE Redirect page [Jump to navigation](https://pve.proxmox.com/wiki/Certified_Appliance:_Proxmox_Mail_Gateway#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Certified_Appliance:_Proxmox_Mail_Gateway#searchInput) Redirect to: * [Proxmox Mail Gateway](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_Mail_Gateway&action=edit&redlink=1 "Proxmox Mail Gateway (page does not exist)") Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Certified\_Appliance:\_Proxmox\_Mail\_Gateway&oldid=352](https://pve.proxmox.com/mediawiki/index.php?title=Certified_Appliance:_Proxmox_Mail_Gateway&oldid=352) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Category:Upgrade" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Category:Upgrade" ===================================== ← [Category:Upgrade](https://pve.proxmox.com/wiki/Category:Upgrade "Category:Upgrade") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Category:Upgrade#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Category:Upgrade#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Category:Upgrade](https://pve.proxmox.com/wiki/Category:Upgrade "Category:Upgrade") **: Displaying 3 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Category:Upgrade&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Category:Upgrade&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Category:Upgrade&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Category:Upgrade&limit=500) ) * [Main Page](https://pve.proxmox.com/wiki/Main_Page "Main Page") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Main+Page "Special:WhatLinksHere") ) * [Quick installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Quick+installation "Special:WhatLinksHere") ) * [Pvebash](https://pve.proxmox.com/wiki/Pvebash "Pvebash") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Pvebash "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Category:Upgrade&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Category:Upgrade&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Category:Upgrade&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Category:Upgrade&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Category:Upgrade](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Category:Upgrade) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Install Proxmox VE on Debian Wheezy - Proxmox VE Install Proxmox VE on Debian Wheezy =================================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy#searchInput) ℹ️ **Note**: Article about the old stable Proxmox VE 3.x releases Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy#Introduction) * [2 Install a standard Debian Wheezy (amd64)](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy#Install_a_standard_Debian_Wheezy_(amd64)) * [2.1 Check /etc/hosts](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy#Check_/etc/hosts) * [3 Install Proxmox VE](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy#Install_Proxmox_VE) * [3.1 Adapt your sources.list](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy#Adapt_your_sources.list) * [3.2 Install Proxmox VE Kernel](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy#Install_Proxmox_VE_Kernel) * [3.3 Install Proxmox VE packages](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy#Install_Proxmox_VE_packages) * [4 Connect to the Proxmox VE web interface](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy#Connect_to_the_Proxmox_VE_web_interface) * [5 Configure apt to use the new packages repositories](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy#Configure_apt_to_use_the_new_packages_repositories) * [6 Optional: Developer Workstations with Proxmox VE and X11](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy#Optional:_Developer_Workstations_with_Proxmox_VE_and_X11) Introduction ------------ The installation of a supported Proxmox VE server should be done via [Bare-metal\_ISO\_Installer](https://pve.proxmox.com/mediawiki/index.php?title=Bare-metal_ISO_Installer&action=edit&redlink=1 "Bare-metal ISO Installer (page does not exist)") . In some case it makes sense to install Proxmox VE on top of a running Debian Wheezy 64-bit, especially if you want a custom partition layout. For this HowTO the following Debian Wheezy ISO was used: [debian-7.8.0-amd64-netinst.iso](http://cdimage.debian.org/cdimage/archive/latest-oldstable/amd64/iso-cd/debian-7.8.0-amd64-netinst.iso) . Suggested partition layout with LVM: Device Boot Start End Blocks Id System /dev/sda1 1 122 975872 83 Linux /dev/sda2 122 5222 40965120 8e Linux LVM LVM: LV VG Attr LSize Origin Snap% Move Log Copy% Convert data pve -wi-ao 30.69g root pve -wi-ao 3.72g swap pve -wi-ao 1.86g We recommend to use ext3 filesystem for best OpenVZ performance and stability. Install a standard Debian Wheezy (amd64) ---------------------------------------- Install a standard Debian Wheezy (amd64), for details see [Debian](http://www.debian.org/) . Go for a LVM based partitioning and a fixed IP and take care that you have enough free space for snapshots (needed for online LVM backup with vzdump, OpenVZ containers only) ### Check /etc/hosts Please make sure that your hostname is resolvable via /etc/hosts, i.e you need an entry in /etc/hosts which assigns an IPv4 address to that hostname. **Note**: Make sure that no IPv6 address for your hostname is specified in /etc/hosts Example /etc/hosts file: root@proxmox-6-177:~# cat /etc/hosts 127.0.0.1 localhost.localdomain localhost 192.168.6.177 proxmox-6-177.proxmox.com proxmox-6-177 pvelocalhost # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts Install Proxmox VE ------------------ ### Adapt your sources.list Adapt your sources.list and add the Proxmox VE repository: nano /etc/apt/sources.list deb http://ftp.at.debian.org/debian wheezy main contrib # PVE repository provided by proxmox.com, only for installation (this repo will stay on 3.1) deb http://download.proxmox.com/debian wheezy pve # security updates deb http://security.debian.org/ wheezy/updates main contrib **NOTE:** Due to a bug in debian/apt(?) it may be required to alter the above sources.list entry to say the following, if apt-get complains about not being able to find /binary-i386: "Unable to find expected entry 'pve/binary-i386/Packages'" (despite it being a 64bit debian install!) deb \[arch=amd64\] http://download.proxmox.com/debian wheezy pve If it does not work for **apt-get** of some files, then replace **http://** with **ftp://** especially in the first two urls above. Add the Proxmox VE repository key: wget -O- "http://download.proxmox.com/debian/key.asc" | apt-key add - Update your repository and system by running: apt-get update && apt-get dist-upgrade ### Install Proxmox VE Kernel apt-get install pve-firmware pve-kernel-2.6.32-26-pve Optional - install Kernel headers: apt-get install pve-headers-2.6.32-26-pve * Make sure to select Proxmox VE Kernel on the boot loader (grub2) - Attention: Default is the 3.2 kernel * Reboot: Now restart the system using the Proxmox VE kernel. ### Install Proxmox VE packages Make sure you are running the Proxmox VE Kernel, otherwise the installation will fail. Check the currently active Kernel: uname -a Linux 2.6.32-26-pve ... Remove the Debian kernel: apt-get remove linux-image-amd64 linux-image-3.2.0-4-amd64 linux-base Check grub2 config by running: update-grub Install the Proxmox VE packages: apt-get install proxmox-ve-2.6.32 ntp ssh lvm2 postfix ksm-control-daemon vzprocps open-iscsi bootlogd Accept the suggestion to remove Exim and configure postfix according to your network. **Note**: Apache2 is not needed anymore as we use our own web server. Connect to the Proxmox VE web interface --------------------------------------- Connect to the admin web interface (https://youripaddress:8006) and configure the vmbr0 and review all other settings, finally reboot to check if everything is running as expected. [![Adapt vmbr0 settings](https://pve.proxmox.com/mediawiki/images/b/ba/Screen-vmbr0-setup-for-pve2.png)](https://pve.proxmox.com/wiki/File:Screen-vmbr0-setup-for-pve2.png "Adapt vmbr0 settings") Configure apt to use the new packages repositories -------------------------------------------------- In order to get latest updates, you need to add one of the new package repositories, see [Package repositories](https://pve.proxmox.com/wiki/Package_repositories "Package repositories") Optional: Developer Workstations with Proxmox VE and X11 -------------------------------------------------------- Proxmox VE is primarily used as virtualization platform with NO additional software installed. In some case it makes sense to have a full desktop running on Proxmox VE, for example for developers using Proxmox VE as their primary workstation/desktop. For example, just install XFCE4 desktop and Firefox/Iceweasel browser: apt-get install xfce4 iceweasel lightdm If you prefer LXDE desktop instead just do: apt-get install lxde iceweasel Make sure network-manager is not used, else pve-cluster will not start in some cases apt-get purge network-manager Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Install\_Proxmox\_VE\_on\_Debian\_Wheezy&oldid=10471](https://pve.proxmox.com/mediawiki/index.php?title=Install_Proxmox_VE_on_Debian_Wheezy&oldid=10471) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Archive](https://pve.proxmox.com/wiki/Category:Archive "Category:Archive") * [Installation](https://pve.proxmox.com/wiki/Category:Installation "Category:Installation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Upgrade from 3.x to 4.0" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Upgrade from 3.x to 4.0" ============================================ ← [Upgrade from 3.x to 4.0](https://pve.proxmox.com/wiki/Upgrade_from_3.x_to_4.0 "Upgrade from 3.x to 4.0") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Upgrade_from_3.x_to_4.0#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Upgrade_from_3.x_to_4.0#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Upgrade from 3.x to 4.0](https://pve.proxmox.com/wiki/Upgrade_from_3.x_to_4.0 "Upgrade from 3.x to 4.0") **: Displaying 2 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_3.x_to_4.0&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_3.x_to_4.0&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_3.x_to_4.0&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_3.x_to_4.0&limit=500) ) * [Downloads](https://pve.proxmox.com/wiki/Downloads "Downloads") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Downloads "Special:WhatLinksHere") ) * [Upgrade from 3.x to 4.x (Debian wheezy to jessie)](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_3.x_to_4.x_(Debian_wheezy_to_jessie)&redirect=no "Upgrade from 3.x to 4.x (Debian wheezy to jessie)") (redirect page) ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Upgrade+from+3.x+to+4.x+%28Debian+wheezy+to+jessie%29 "Special:WhatLinksHere") ) * [Upgrade from 3.x to 4.x](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_3.x_to_4.x&redirect=no "Upgrade from 3.x to 4.x") (redirect page) ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Upgrade+from+3.x+to+4.x "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_3.x_to_4.0&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_3.x_to_4.0&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_3.x_to_4.0&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_3.x_to_4.0&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Upgrade\_from\_3.x\_to\_4.0](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Upgrade_from_3.x_to_4.0) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Windows XP Guest Notes - Proxmox VE Windows XP Guest Notes ====================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Windows_XP_Guest_Notes#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Windows_XP_Guest_Notes#searchInput) This page is a collection of notes for configuring and performance tuning Windows XP guest virtual machines. Contents -------- * [1 CAUTION!](https://pve.proxmox.com/wiki/Windows_XP_Guest_Notes#CAUTION!) * [2 Use VirtIO Drivers](https://pve.proxmox.com/wiki/Windows_XP_Guest_Notes#Use_VirtIO_Drivers) * [3 Shrinking Qcow2 Disk Files](https://pve.proxmox.com/wiki/Windows_XP_Guest_Notes#Shrinking_Qcow2_Disk_Files) * [4 The Page File](https://pve.proxmox.com/wiki/Windows_XP_Guest_Notes#The_Page_File) * [5 See Also](https://pve.proxmox.com/wiki/Windows_XP_Guest_Notes#See_Also) CAUTION! -------- Changing your drive from IDE/SATA to VIRTIO may causing blue dead screen Windows, so please make a Backup first! **IMPORTANT:** I've tried to be as accurate as possible, but I'm doing a "brain dump" very quickly. Use these notes at your own risk and always take backups of your VM's before attempting any system level modifications like these. Use VirtIO Drivers ------------------ When you build an XP guest VM, chances are you use the IDE driver to get up and running right away. The IDE driver works OK for locally stored VMs, but performance will degrade significantly when accessing disk files over the network. Below are (rough) steps to switching to the Red Hat virtio drivers in a Windows XP guest. * Build your Windows XP VM using the IDE disk driver and the rtl8139 NIC driver. These are both recognized by default on Windows XP. * Boot the XP VM and verify that Internet access works. * Download and install [wincdemu](http://wincdemu.sysprogs.org/) inside the XP guest. * Download the latest [virtio-win iso](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/) from the Fedora Project into the Windows XP VM. * **Note:** It's a good idea to leave this iso stored inside your VM. You may need it outside of this original setup. * Shut down the XP VM. * In the Proxmox web admin, click on the VM, and then on it's **Hardware** tab. * Add an ethernet device, and select **virtio** as the model. * Add a hard disk, select **qcow2** (faster creation than raw) as the format and **virtio** as the bus. * Boot into the XP VM. * The "found new hardware wizard" should appear. Leave this window open, you need to mount the virtio driver iso first. * Locate the virtio iso, right-click on it and click **Select drive letter & mount**. It defaults to the **V:** drive - click OK. * Go back to the "found new hardware wizard". Click next and verify its looking for the ethernet controller. Point the drivers to **V:\\NetKVM\\XP\\** (where is either amd64 or x86). Finish the driver installation, click **Continue** when asked if you want to install an unsigned driver. * Go through the same process for the virtio scsi controller. Drivers are in **V:\\viostor\\WXp\\** (it looks like only x86 is currently available, as of 2011-01-13). * Shut down the XP VM. * Delete the second (virtio) disk and remove it (it's not needed). * Delete the primary IDE disk (doesn't actually delete it, it just removes it from being used by the VM). * Add a new hard disk, and in the lower section, choose the original IDE disk file. Change the bus to virtio and save it. * Boot the XP VM. * You may be prompted to install the virtio storage driver again. Do so. * Reboot the XP VM to ensure that your virtio drivers are working without issue. * If you remove the realtek network adapter, you may be prompted to reinstall the virtio network driver on reboot. Do so. Shrinking Qcow2 Disk Files -------------------------- See [Shrink Qcow2 Disk Files](https://pve.proxmox.com/wiki/Shrink_Qcow2_Disk_Files "Shrink Qcow2 Disk Files") for information on reducing the size of your \*.qcow2 virtual disk files. The Page File ------------- * Whether a page file is necessary in a virtual XP machine may be discussed elsewhere. * **Myth:** At least part of the Windows Pagefile need to be on the boot partition. * Boxes running 2000 Server, 2003 Server, 2008 Server and XP Pro, all of which can be setup with no Pagefile on the Boot partition. For best performance, setup dedicated partitions/disks for all pagefile activity. The following makes for it's shift out to a different (virtual) drive. My computer > Properties > Advanced ; Performance > Settings; Advanced; Virtual memory > Change; select Boot partition > No paging file. The **12 MB** minimum that is spoken of, is a **system wide** minimum, that the system must have available to it. However, the discs that the pagefile is spread over (to make up the 12 MB minimum or more), are totally configurable. See Also -------- * [Shrink Qcow2 Disk Files](https://pve.proxmox.com/wiki/Shrink_Qcow2_Disk_Files "Shrink Qcow2 Disk Files") Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Windows\_XP\_Guest\_Notes&oldid=9143](https://pve.proxmox.com/mediawiki/index.php?title=Windows_XP_Guest_Notes&oldid=9143) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Qemu/KVM](https://pve.proxmox.com/wiki/Category:Qemu/KVM "Category:Qemu/KVM") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Upgrade from 5.x to 6.0" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Upgrade from 5.x to 6.0" ============================================ ← [Upgrade from 5.x to 6.0](https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0 "Upgrade from 5.x to 6.0") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Upgrade_from_5.x_to_6.0#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Upgrade_from_5.x_to_6.0#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Upgrade from 5.x to 6.0](https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0 "Upgrade from 5.x to 6.0") **: Displaying 3 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_5.x_to_6.0&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_5.x_to_6.0&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_5.x_to_6.0&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_5.x_to_6.0&limit=500) ) * [Downloads](https://pve.proxmox.com/wiki/Downloads "Downloads") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Downloads "Special:WhatLinksHere") ) * [Quick installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Quick+installation "Special:WhatLinksHere") ) * [Upgrade from 5.x to 6.0](https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0 "Upgrade from 5.x to 6.0") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Upgrade+from+5.x+to+6.0 "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_5.x_to_6.0&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_5.x_to_6.0&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_5.x_to_6.0&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_5.x_to_6.0&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Upgrade\_from\_5.x\_to\_6.0](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Upgrade_from_5.x_to_6.0) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "User Management" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "User Management" ==================================== ← [User Management](https://pve.proxmox.com/wiki/User_Management "User Management") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/User_Management#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/User_Management#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[User Management](https://pve.proxmox.com/wiki/User_Management "User Management") **: Displaying 2 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/User_Management&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/User_Management&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/User_Management&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/User_Management&limit=500) ) * [Main Page](https://pve.proxmox.com/wiki/Main_Page "Main Page") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Main+Page "Special:WhatLinksHere") ) * [Two-Factor Authentication](https://pve.proxmox.com/wiki/Two-Factor_Authentication "Two-Factor Authentication") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Two-Factor+Authentication "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/User_Management&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/User_Management&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/User_Management&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/User_Management&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/User\_Management](https://pve.proxmox.com/wiki/Special:WhatLinksHere/User_Management) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Graphical User Interface - Proxmox VE Graphical User Interface ======================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Graphical_User_Interface#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Graphical_User_Interface#searchInput) Proxmox VE is simple. There is no need to install a separate management tool, and everything can be done through your web browser (Latest Firefox or Google Chrome is preferred). A built-in HTML5 console is used to access the guest console. As an alternative, [SPICE](https://www.spice-space.org/) can be used. Because we use the Proxmox cluster file system (pmxcfs), you can connect to any node to manage the entire cluster. Each node can manage the entire cluster. There is no need for a dedicated manager node. You can use the web-based administration interface with any modern browser. When Proxmox VE detects that you are connecting from a mobile device, you are redirected to a simpler, touch-based user interface. The web interface can be reached via [https://youripaddress:8006](https://youripaddress:8006/) (default login is: _root_, and the password is specified during the installation process). Features -------- * Seamless integration and management of Proxmox VE clusters * AJAX technologies for dynamic updates of resources * Secure access to all Virtual Machines and Containers via SSL encryption (https) * Fast search-driven interface, capable of handling hundreds and probably thousands of VMs * Secure HTML5 console or SPICE * Role based permission management for all objects (VMs, storages, nodes, etc.) * Support for multiple authentication sources (e.g. local, MS ADS, LDAP, …) * Two-Factor Authentication (OATH, Yubikey) * Based on ExtJS 7.x JavaScript framework Login ----- [![screenshot/gui-login-window.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-login-window.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-login-window.png) When you connect to the server, you will first see the login window. Proxmox VE supports various authentication backends (_Realm_), and you can select the language here. The GUI is translated to more than 20 languages. | | | | --- | --- | | ![Note]() | You can save the user name on the client side by selecting the checkbox at the bottom. This saves some typing when you login next time. | GUI Overview ------------ [![screenshot/gui-datacenter-summary.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-datacenter-summary.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-datacenter-summary.png) The Proxmox VE user interface consists of four regions. | | | | --- | --- | | Header | On top. Shows status information and contains buttons for most important actions. | | Resource Tree | At the left side. A navigation tree where you can select specific objects. | | Content Panel | Center region. Selected objects display configuration options and status here. | | Log Panel | At the bottom. Displays log entries for recent tasks. You can double-click on those log entries to get more details, or to abort a running task. | | | | | --- | --- | | ![Note]() | You can shrink and expand the size of the resource tree and log panel, or completely hide the log panel. This can be helpful when you work on small displays and want more space to view other content. | ### Header On the top left side, the first thing you see is the Proxmox logo. Next to it is the current running version of Proxmox VE. In the search bar nearside you can search for specific objects (VMs, containers, nodes, …). This is sometimes faster than selecting an object in the resource tree. The right part of the header contains four buttons: | | | | --- | --- | | Documentation | Opens a new browser window showing the reference documentation. | | Create VM | Opens the virtual machine creation wizard. | | Create CT | Open the container creation wizard. | | User Menu | Displays the identity of the user you’re currently logged in with, and clicking it opens a menu with user-specific options.

In the user menu, you’ll find the _My Settings_ dialog, which provides local UI settings. Below that, there are shortcuts for _TFA_ (Two-Factor Authentication) and _Password_ self-service. You’ll also find options to change the _Language_ and the _Color Theme._ Finally, at the bottom of the menu is the _Logout_ option. | ### My Settings [![screenshot/gui-my-settings.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-my-settings.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-my-settings.png) The _My Settings_ window allows you to set locally stored settings. These include the _Dashboard Storages_ which allow you to enable or disable specific storages to be counted towards the total amount visible in the datacenter summary. If no storage is checked the total is the sum of all storages, same as enabling every single one. Below the dashboard settings you find the stored user name and a button to clear it as well as a button to reset every layout in the GUI to its default. On the right side there are _xterm.js Settings_. These contain the following options: | | | | --- | --- | | Font-Family | The font to be used in xterm.js (e.g. Arial). | | Font-Size | The preferred font size to be used. | | Letter Spacing | Increases or decreases spacing between letters in text. | | Line Height | Specify the absolute height of a line. | ### Resource Tree This is the main navigation tree. On top of the tree you can select some predefined views, which change the structure of the tree below. The default view is the **Server View**, and it shows the following object types: | | | | --- | --- | | Datacenter | Contains cluster-wide settings (relevant for all nodes). | | Node | Represents the hosts inside a cluster, where the guests run. | | Guest | VMs, containers and templates. | | Storage | Data Storage. | | Pool | It is possible to group guests using a pool to simplify management. | The following view types are available: | | | | --- | --- | | Server View | Shows all kinds of objects, grouped by nodes. | | Folder View | Shows all kinds of objects, grouped by object type. | | Pool View | Show VMs and containers, grouped by pool. | | Tag View | Show VMs and containers, grouped by tags. | ### Log Panel The main purpose of the log panel is to show you what is currently going on in your cluster. Actions like creating an new VM are executed in the background, and we call such a background job a _task_. Any output from such a task is saved into a separate log file. You can view that log by simply double-click a task log entry. It is also possible to abort a running task there. Please note that we display the most recent tasks from all cluster nodes here. So you can see when somebody else is working on another cluster node in real-time. | | | | --- | --- | | ![Note]() | We remove older and finished task from the log panel to keep that list short. But you can still find those tasks within the node panel in the _Task History_. | Some short-running actions simply send logs to all cluster members. You can see those messages in the _Cluster log_ panel. Content Panels -------------- When you select an item from the resource tree, the corresponding object displays configuration and status information in the content panel. The following sections provide a brief overview of this functionality. Please refer to the corresponding chapters in the reference documentation to get more detailed information. ### Datacenter [![screenshot/gui-datacenter-search.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-datacenter-search.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-datacenter-search.png) On the datacenter level, you can access cluster-wide settings and information. * **Search:** perform a cluster-wide search for nodes, VMs, containers, storage devices, and pools. * **Summary:** gives a brief overview of the cluster’s health and resource usage. * **Cluster:** provides the functionality and information necessary to create or join a cluster. * **Options:** view and manage cluster-wide default settings. * **Storage:** provides an interface for managing cluster storage. * **Backup:** schedule backup jobs. This operates cluster wide, so it doesn’t matter where the VMs/containers are on your cluster when scheduling. * **Replication:** view and manage replication jobs. * **Permissions:** manage user, group, and API token permissions, and LDAP, MS-AD and Two-Factor authentication. * **HA:** manage Proxmox VE High Availability. * **ACME:** set up ACME (Let’s Encrypt) certificates for server nodes. * **Firewall:** configure and make templates for the Proxmox Firewall cluster wide. * **Metric Server:** define external metric servers for Proxmox VE. * **Notifications:** configurate notification behavior and targets for Proxmox VE. * **Support:** display information about your support subscription. ### Nodes [![screenshot/gui-node-summary.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-node-summary.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-node-summary.png) Nodes in your cluster can be managed individually at this level. The top header has useful buttons such as _Reboot_, _Shutdown_, _Shell_, _Bulk Actions_ and _Help_. _Shell_ has the options _noVNC_, _SPICE_ and _xterm.js_. _Bulk Actions_ has the options _Bulk Start_, _Bulk Shutdown_ and _Bulk Migrate_. * **Search:** search a node for VMs, containers, storage devices, and pools. * **Summary:** display a brief overview of the node’s resource usage. * **Notes:** write custom comments in [Markdown syntax](https://pve.proxmox.com/wiki/Markdown_Primer#markdown_basics) . * **Shell:** access to a shell interface for the node. * **System:** configure network, DNS and time settings, and access the syslog. * **Updates:** upgrade the system and see the available new packages. * **Firewall:** manage the Proxmox Firewall for a specific node. * **Disks:** get an overview of the attached disks, and manage how they are used. * **Ceph:** is only used if you have installed a Ceph server on your host. In this case, you can manage your Ceph cluster and see the status of it here. * **Replication:** view and manage replication jobs. * **Task History:** see a list of past tasks. * **Subscription:** upload a subscription key, and generate a system report for use in support cases. ### Guests [![screenshot/gui-qemu-summary.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-qemu-summary.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-qemu-summary.png) There are two different kinds of guests and both can be converted to a template. One of them is a Kernel-based Virtual Machine (KVM) and the other is a Linux Container (LXC). Navigation for these are mostly the same; only some options are different. To access the various guest management interfaces, select a VM or container from the menu on the left. The header contains commands for items such as power management, migration, console access and type, cloning, HA, and help. Some of these buttons contain drop-down menus, for example, _Shutdown_ also contains other power options, and _Console_ contains the different console types: _SPICE_, _noVNC_ and _xterm.js_. The panel on the right contains an interface for whatever item is selected from the menu on the left. The available interfaces are as follows. * **Summary:** provides a brief overview of the VM’s activity and a Notes field for [Markdown syntax](https://pve.proxmox.com/wiki/Markdown_Primer#markdown_basics) comments. * **Console:** access to an interactive console for the VM/container. * **(KVM)Hardware:** define the hardware available to the KVM VM. * **(LXC)Resources:** define the system resources available to the LXC. * **(LXC)Network:** configure a container’s network settings. * **(LXC)DNS:** configure a container’s DNS settings. * **Options:** manage guest options. * **Task History:** view all previous tasks related to the selected guest. * **(KVM) Monitor:** an interactive communication interface to the KVM process. * **Backup:** create and restore system backups. * **Replication:** view and manage the replication jobs for the selected guest. * **Snapshots:** create and restore VM snapshots. * **Firewall:** configure the firewall on the VM level. * **Permissions:** manage permissions for the selected guest. ### Storage [![screenshot/gui-storage-summary-local.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-storage-summary-local.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-storage-summary-local.png) As with the guest interface, the interface for storage consists of a menu on the left for certain storage elements and an interface on the right to manage these elements. In this view we have a two partition split-view. On the left side we have the storage options and on the right side the content of the selected option will be shown. * **Summary:** shows important information about the storage, such as the type, usage, and content which it stores. * **Content:** a menu item for each content type which the storage stores, for example, Backups, ISO Images, CT Templates. * **Permissions:** manage permissions for the storage. ### Pools [![screenshot/gui-pool-summary-development.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-pool-summary-development.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-pool-summary-development.png) Again, the pools view comprises two partitions: a menu on the left, and the corresponding interfaces for each menu item on the right. * **Summary:** shows a description of the pool. * **Members:** display and manage pool members (guests and storage). * **Permissions:** manage the permissions for the pool. Tags ---- [![screenshot/gui-qemu-summary-tags-edit.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-qemu-summary-tags-edit.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-qemu-summary-tags-edit.png) For organizational purposes, it is possible to set tags for guests. Currently, these only provide informational value to users. Tags are displayed in two places in the web interface: in the Resource Tree and in the status line when a guest is selected. Tags can be added, edited, and removed in the status line of the guest by clicking on the pencil icon. You can add multiple tags by pressing the + button and remove them by pressing the \- button. To save or cancel the changes, you can use the ✓ and x button respectively. Tags can also be set via the CLI, where multiple tags are separated by semicolons. For example: \# qm set ID --tags 'myfirsttag;mysecondtag' ### Style Configuration [![screenshot/gui-datacenter-tag-style.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-datacenter-tag-style.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-datacenter-tag-style.png) By default, the tag colors are derived from their text in a deterministic way. The color, shape in the resource tree, and case-sensitivity, as well as how tags are sorted, can be customized. This can be done via the web interface under _Datacenter → Options → Tag Style Override_. Alternatively, this can be done via the CLI. For example: \# pvesh set /cluster/options --tag-style color-map=example:000000:FFFFFF sets the background color of the tag example to black (#000000) and the text color to white (#FFFFFF). ### Permissions [![screenshot/gui-datacenter-options.png](https://pve.proxmox.com/pve-docs/images/screenshot/gui-datacenter-options.png)](https://pve.proxmox.com/pve-docs/images/screenshot/gui-datacenter-options.png) By default, users with the privilege VM.Config.Options on a guest (/vms/ID) can set any tags they want (see [Permission Management](https://pve.proxmox.com/wiki/User_Management#pveum_permission_management) ). If you want to restrict this behavior, appropriate permissions can be set under _Datacenter → Options → User Tag Access_: * free: users are not restricted in setting tags (Default) * list: users can set tags based on a predefined list of tags * existing: like list but users can also use already existing tags * none: users are restricted from using tags The same can also be done via the CLI. Note that a user with the Sys.Modify privileges on / is always able to set or delete any tags, regardless of the settings here. Additionally, there is a configurable list of registered tags which can only be added and removed by users with the privilege Sys.Modify on /. The list of registered tags can be edited under _Datacenter → Options → Registered Tags_ or via the CLI. For more details on the exact options and how to invoke them in the CLI, see [Datacenter Configuration](https://pve.proxmox.com/wiki/General#datacenter_configuration_file) . Consent Banner -------------- A custom consent banner that has to be accepted before login can be configured in _Datacenter → Options → Consent Text_. If there is no content, the consent banner will not be displayed. The text will be stored as a base64 string in the /etc/pve/datacenter.cfg config file. See Also -------- * link:/wiki/Central\_Web-based\_Management Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Graphical\_User\_Interface&oldid=12299](https://pve.proxmox.com/mediawiki/index.php?title=Graphical_User_Interface&oldid=12299) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Reference Documentation](https://pve.proxmox.com/wiki/Category:Reference_Documentation "Category:Reference Documentation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Build your first DAB Appliance Template" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Build your first DAB Appliance Template" ============================================================ ← [Build your first DAB Appliance Template](https://pve.proxmox.com/mediawiki/index.php?title=Build_your_first_DAB_Appliance_Template&action=edit&redlink=1 "Build your first DAB Appliance Template (page does not exist)") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Build_your_first_DAB_Appliance_Template#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Build_your_first_DAB_Appliance_Template#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Build your first DAB Appliance Template](https://pve.proxmox.com/mediawiki/index.php?title=Build_your_first_DAB_Appliance_Template&action=edit&redlink=1 "Build your first DAB Appliance Template (page does not exist)") **: Displaying 2 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Build_your_first_DAB_Appliance_Template&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Build_your_first_DAB_Appliance_Template&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Build_your_first_DAB_Appliance_Template&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Build_your_first_DAB_Appliance_Template&limit=500) ) * [Debian Appliance Builder](https://pve.proxmox.com/wiki/Debian_Appliance_Builder "Debian Appliance Builder") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Debian+Appliance+Builder "Special:WhatLinksHere") ) * [User talk:Apmuthu](https://pve.proxmox.com/wiki/User_talk:Apmuthu "User talk:Apmuthu") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AApmuthu "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Build_your_first_DAB_Appliance_Template&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Build_your_first_DAB_Appliance_Template&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Build_your_first_DAB_Appliance_Template&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Build_your_first_DAB_Appliance_Template&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Build\_your\_first\_DAB\_Appliance\_Template](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Build_your_first_DAB_Appliance_Template) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # OpenVZ - Proxmox VE OpenVZ ====== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/OpenVZ#mw-head) [Jump to search](https://pve.proxmox.com/wiki/OpenVZ#searchInput) ℹ️ **Note**: Article about the old stable Proxmox VE 3.x releases **NOTE: OpenVZ is supported until Proxmox 3.4 and will end with Debian Wheezy security updates (expected end in April 2016)** OpenVZ is container-based virtualization for Linux. OpenVZ creates multiple secure, isolated containers (otherwise known as VEs or VPSs) on a single physical server enabling better server utilization and ensuring that applications do not conflict. Each container performs and executes exactly like a stand-alone server; a container can be rebooted independently and have root access, users, IP addresses, memory, processes, files, applications, system libraries and configuration files. Currently all Proxmox VE Appliances are OpenVZ based and are "production ready". For details see [OpenVZ](http://openvz.org/) . Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=OpenVZ&oldid=9239](https://pve.proxmox.com/mediawiki/index.php?title=OpenVZ&oldid=9239) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Proxmox VE 3.x](https://pve.proxmox.com/wiki/Category:Proxmox_VE_3.x "Category:Proxmox VE 3.x") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Guest Boot Problems - Proxmox VE Guest Boot Problems =================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Guest_Boot_Problems#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Guest_Boot_Problems#searchInput) When a guest fails to start, the GUI doesn't present you with an immediate error. Below are some steps you can try: * SSH into the Proxmox VE server. KVM --- * Review the contents of `syslog`: tail -50 /var/log/syslog * Try starting the VM from the shell. This should reveal problems that are preventing the VM from booting. * **Note:** Change VMID to the guest VM's ID number: qm start VMID The last step noted above made me aware that an ISO I was using for the VM's CD drive was missing. The ISO had been deleted some how. Here's the output of the command from my server: vm3:/storage/template/iso# qm start 104 volume 'local:iso/clonezilla-live-1.2.6-24-i686.iso' does not exist LXC --- See [Linux\_Container](https://pve.proxmox.com/wiki/Linux_Container#_managing_containers_with_tt_span_class_monospaced_pct_span_tt "Linux Container") paragraph "Obtaining Debugging Logs". Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Guest\_Boot\_Problems&oldid=9512](https://pve.proxmox.com/mediawiki/index.php?title=Guest_Boot_Problems&oldid=9512) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Troubleshooting](https://pve.proxmox.com/wiki/Category:Troubleshooting "Category:Troubleshooting") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Kernel Samepage Merging (KSM) - Proxmox VE Kernel Samepage Merging (KSM) ============================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Kernel_Samepage_Merging_(KSM)#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Kernel_Samepage_Merging_(KSM)#searchInput) Kernel Samepage Merging (KSM) is an optional memory deduplication feature offered by the Linux kernel, which is enabled by default in Proxmox VE. KSM works by scanning a range of physical memory pages for identical content, and identifying the virtual pages that are mapped to them. If identical pages are found, the corresponding virtual pages are re-mapped so that they all point to the same physical page, and the old pages are freed. The virtual pages are marked as "copy-on-write", so that any writes to them will be written to a new area of memory, leaving the shared physical page intact. Implications of KSM ------------------- KSM can optimize memory usage in virtualization environments, as multiple VMs running similar operating systems or workloads could potentially share a lot of common memory pages. However, while KSM can reduce memory usage, it also comes with some security risks, as it can expose VMs to side-channel attacks. Research has shown that it is possible to infer information about a running VM via a second VM on the same host, by exploiting certain characteristics of KSM. Thus, if you are using Proxmox VE to provide hosting services, you should consider disabling KSM, in order to provide your users with additional security. Furthermore, you should check your country’s regulations, as disabling KSM may be a legal requirement. Disabling KSM ------------- KSM can be disabled on a node or on a per-VM basis. ##### Disabe KSM on a Node To see if KSM is active on a node, you can check the output of: \# systemctl status ksmtuned If it is, it can be disabled immediately with: \# systemctl disable --now ksmtuned Finally, to unmerge all the currently merged pages, run: \# echo 2 > /sys/kernel/mm/ksm/run ##### Disabe KSM for a Specific VM The allow-ksm VM configuration option controls whether memory page merging is allowed for a given VM. The option defaults to true and can be disabled with: \# qm set --allow-ksm 0 Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Kernel\_Samepage\_Merging\_(KSM)&oldid=12406](https://pve.proxmox.com/mediawiki/index.php?title=Kernel_Samepage_Merging_(KSM)&oldid=12406) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Reference Documentation](https://pve.proxmox.com/wiki/Category:Reference_Documentation "Category:Reference Documentation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Command Line Tools - Proxmox VE Command Line Tools ================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Command_Line_Tools#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Command_Line_Tools#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Command_Line_Tools#Introduction) * [2 Virtual Machines (QEMU/KVM) specific](https://pve.proxmox.com/wiki/Command_Line_Tools#Virtual_Machines_(QEMU/KVM)_specific) * [2.1 qm](https://pve.proxmox.com/wiki/Command_Line_Tools#qm) * [3 Container (LXC)](https://pve.proxmox.com/wiki/Command_Line_Tools#Container_(LXC)) * [4 Backup](https://pve.proxmox.com/wiki/Command_Line_Tools#Backup) * [4.1 vzdump](https://pve.proxmox.com/wiki/Command_Line_Tools#vzdump) * [4.2 Restore](https://pve.proxmox.com/wiki/Command_Line_Tools#Restore) * [4.3 VM Restore](https://pve.proxmox.com/wiki/Command_Line_Tools#VM_Restore) * [4.4 Container Restore](https://pve.proxmox.com/wiki/Command_Line_Tools#Container_Restore) * [5 Cluster Management](https://pve.proxmox.com/wiki/Command_Line_Tools#Cluster_Management) * [6 Software version check](https://pve.proxmox.com/wiki/Command_Line_Tools#Software_version_check) * [7 Storage](https://pve.proxmox.com/wiki/Command_Line_Tools#Storage) * [7.1 LVM](https://pve.proxmox.com/wiki/Command_Line_Tools#LVM) * [8 Debian Appliance Builder](https://pve.proxmox.com/wiki/Command_Line_Tools#Debian_Appliance_Builder) * [8.1 dab](https://pve.proxmox.com/wiki/Command_Line_Tools#dab) * [9 Other useful tools](https://pve.proxmox.com/wiki/Command_Line_Tools#Other_useful_tools) * [9.1 pveperf](https://pve.proxmox.com/wiki/Command_Line_Tools#pveperf) * [9.2 Example output](https://pve.proxmox.com/wiki/Command_Line_Tools#Example_output) * [9.3 pvesubscription](https://pve.proxmox.com/wiki/Command_Line_Tools#pvesubscription) Introduction ============ This page lists some important Proxmox VE and Debian command line tools. Virtual Machines (QEMU/KVM) specific ==================================== qm -- To view a list of KVMs: qm list VMID NAME STATUS MEM(MB) BOOTDISK(GB) PID 100 alpha001 running 2048 8.00 5858 101 WINXP002 running 1024 32.00 6177 102 Win2K running 2048 32.00 113893 105 axe002 running 16384 100.00 279613 To see how much memory your machine 101 has: qm config 101 | grep ^memory memory: 2048 see `man qm` ([available online](https://pve.proxmox.com/pve-docs/qm.1.html) ) for further info Container (LXC) =============== `pct list` Backup ====== vzdump ------ vzdump - backup utility for virtual machine - see "man vzdump" Restore ------- VM Restore ---------- `qmrestore` - restore QEMU/KVM vzdump backups - see "man qmrestore" Container Restore ----------------- pct restore Cluster Management ================== `pvecm status` PVE Cluster Manager - see "man pvecm" for details. Software version check ====================== `pveversion -v` Proxmox VE version info - Print version information for Proxmox VE packages. Storage ======= LVM --- Most of the commands in LVM are very similar to each other. Each valid command is preceded by one of the following: * Physical Volume = pv * Volume Group = vg * Logical Volume = lv Debian Appliance Builder ======================== dab --- See [Debian Appliance Builder](https://pve.proxmox.com/wiki/Debian_Appliance_Builder "Debian Appliance Builder") Other useful tools ================== ### pveperf Simple host performance test - see "man pveperf". Note: this command may require root privileges (or sudo) to run, otherwise you get an error after "HD SIZE" value, like: <> ### Example output CPU BOGOMIPS: 26341.80 REGEX/SECOND: 1554770 HD SIZE: 94.49 GB (/dev/mapper/pve-root) BUFFERED READS: 49.83 MB/sec AVERAGE SEEK TIME: 14.16 ms FSYNCS/SECOND: 1060.47 DNS EXT: 314.58 ms DNS INT: 236.94 ms (mypve.com) pvesubscription --------------- For managing a node's subscription key - see "man pvesubscription" Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Command\_Line\_Tools&oldid=11544](https://pve.proxmox.com/mediawiki/index.php?title=Command_Line_Tools&oldid=11544) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Debian Etch Standard - Proxmox VE Debian Etch Standard ==================== From Proxmox VE Redirect page [Jump to navigation](https://pve.proxmox.com/wiki/Debian_Etch_Standard#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Debian_Etch_Standard#searchInput) Redirect to: * [Debian 4.0 Standard](https://pve.proxmox.com/mediawiki/index.php?title=Debian_4.0_Standard&action=edit&redlink=1 "Debian 4.0 Standard (page does not exist)") Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Debian\_Etch\_Standard&oldid=551](https://pve.proxmox.com/mediawiki/index.php?title=Debian_Etch_Standard&oldid=551) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "DotDEB Page" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "DotDEB Page" ================================ ← [DotDEB Page](https://pve.proxmox.com/mediawiki/index.php?title=DotDEB_Page&action=edit&redlink=1 "DotDEB Page (page does not exist)") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/DotDEB_Page#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/DotDEB_Page#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[DotDEB Page](https://pve.proxmox.com/mediawiki/index.php?title=DotDEB_Page&action=edit&redlink=1 "DotDEB Page (page does not exist)") **: Displaying 1 item. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/DotDEB_Page&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/DotDEB_Page&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/DotDEB_Page&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/DotDEB_Page&limit=500) ) * [User talk:Apmuthu](https://pve.proxmox.com/wiki/User_talk:Apmuthu "User talk:Apmuthu") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User+talk%3AApmuthu "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/DotDEB_Page&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/DotDEB_Page&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/DotDEB_Page&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/DotDEB_Page&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/DotDEB\_Page](https://pve.proxmox.com/wiki/Special:WhatLinksHere/DotDEB_Page) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "FengOffice" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "FengOffice" =============================== ← [FengOffice](https://pve.proxmox.com/mediawiki/index.php?title=FengOffice&action=edit&redlink=1 "FengOffice (page does not exist)") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/FengOffice#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/FengOffice#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[FengOffice](https://pve.proxmox.com/mediawiki/index.php?title=FengOffice&action=edit&redlink=1 "FengOffice (page does not exist)") **: Displaying 1 item. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/FengOffice&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/FengOffice&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/FengOffice&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/FengOffice&limit=500) ) * [User:Apmuthu](https://pve.proxmox.com/wiki/User:Apmuthu "User:Apmuthu") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User%3AApmuthu "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/FengOffice&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/FengOffice&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/FengOffice&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/FengOffice&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/FengOffice](https://pve.proxmox.com/wiki/Special:WhatLinksHere/FengOffice) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Proxmox VE API - Proxmox VE Proxmox VE API ============== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Proxmox_VE_API#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Proxmox_VE_API#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Proxmox_VE_API#Introduction) * [2 JSON and JSON Schema](https://pve.proxmox.com/wiki/Proxmox_VE_API#JSON_and_JSON_Schema) * [3 API Stability & Breakage](https://pve.proxmox.com/wiki/Proxmox_VE_API#API_Stability_&_Breakage) * [4 API URL](https://pve.proxmox.com/wiki/Proxmox_VE_API#API_URL) * [5 Authentication](https://pve.proxmox.com/wiki/Proxmox_VE_API#Authentication) * [5.1 Ticket Cookie](https://pve.proxmox.com/wiki/Proxmox_VE_API#Ticket_Cookie) * [5.1.1 Example: Get a New Ticket and the CSRF Prevention Token](https://pve.proxmox.com/wiki/Proxmox_VE_API#Example:_Get_a_New_Ticket_and_the_CSRF_Prevention_Token) * [5.1.2 Example: Use the New Ticket](https://pve.proxmox.com/wiki/Proxmox_VE_API#Example:_Use_the_New_Ticket) * [5.1.3 Example: Ticket & CSRF for PUT, POST, DELETE](https://pve.proxmox.com/wiki/Proxmox_VE_API#Example:_Ticket_&_CSRF_for_PUT,_POST,_DELETE) * [5.2 API Tokens](https://pve.proxmox.com/wiki/Proxmox_VE_API#API_Tokens) * [5.2.1 Example: Use API Token](https://pve.proxmox.com/wiki/Proxmox_VE_API#Example:_Use_API_Token) * [6 Step-by-step Example of Container Create Using the API](https://pve.proxmox.com/wiki/Proxmox_VE_API#Step-by-step_Example_of_Container_Create_Using_the_API) * [6.1 Export Variables](https://pve.proxmox.com/wiki/Proxmox_VE_API#Export_Variables) * [6.2 Save an Authorization Cookie on the Filesystem](https://pve.proxmox.com/wiki/Proxmox_VE_API#Save_an_Authorization_Cookie_on_the_Filesystem) * [6.3 Save a CSRF Token Locally](https://pve.proxmox.com/wiki/Proxmox_VE_API#Save_a_CSRF_Token_Locally) * [6.4 Test auth credentials](https://pve.proxmox.com/wiki/Proxmox_VE_API#Test_auth_credentials) * [6.5 Creates a LXC Container](https://pve.proxmox.com/wiki/Proxmox_VE_API#Creates_a_LXC_Container) * [7 Using 'pvesh' to Access the API](https://pve.proxmox.com/wiki/Proxmox_VE_API#Using_'pvesh'_to_Access_the_API) * [7.1 Examples](https://pve.proxmox.com/wiki/Proxmox_VE_API#Examples) * [8 API Client Libraries](https://pve.proxmox.com/wiki/Proxmox_VE_API#API_Client_Libraries) * [8.1 Official Proxmox Maintained](https://pve.proxmox.com/wiki/Proxmox_VE_API#Official_Proxmox_Maintained) * [8.2 Community Maintained](https://pve.proxmox.com/wiki/Proxmox_VE_API#Community_Maintained) * [8.2.1 Python](https://pve.proxmox.com/wiki/Proxmox_VE_API#Python) * [8.2.2 PowerShell](https://pve.proxmox.com/wiki/Proxmox_VE_API#PowerShell) * [8.2.3 Ruby](https://pve.proxmox.com/wiki/Proxmox_VE_API#Ruby) * [8.2.4 NodeJS](https://pve.proxmox.com/wiki/Proxmox_VE_API#NodeJS) * [8.2.5 C#](https://pve.proxmox.com/wiki/Proxmox_VE_API#C#) * [8.2.6 PHP](https://pve.proxmox.com/wiki/Proxmox_VE_API#PHP) * [8.2.7 Java](https://pve.proxmox.com/wiki/Proxmox_VE_API#Java) * [8.2.8 Perl](https://pve.proxmox.com/wiki/Proxmox_VE_API#Perl) * [8.2.9 Go](https://pve.proxmox.com/wiki/Proxmox_VE_API#Go) * [8.2.10 Terraform](https://pve.proxmox.com/wiki/Proxmox_VE_API#Terraform) * [9 References](https://pve.proxmox.com/wiki/Proxmox_VE_API#References) Introduction ------------ Proxmox VE uses a REST like API. The concept is described in \[1\] (Resource Oriented Architecture - ROA). We choose JSON as primary data format, and the whole API is formally defined using JSON Schema \[2\]. You can explore the API documentation at [http://pve.proxmox.com/pve-docs/api-viewer/index.html](http://pve.proxmox.com/pve-docs/api-viewer/index.html) JSON and JSON Schema -------------------- The API use JSON as data format, because it is simple and parse-able by any web browser. Additionally, we use JSON Schema \[2\] to formally describe our API. So we can automatically generate the whole API Documentation, and we can verify all parameters and return values. An great side effect was that we are able to use JSON Schema to produce command line argument parsers automatically. In fact, the REST API and the command line tools use the same code. A small utility called 'pvesh' exposes the whole REST API on the command line. So here is a summary of the advantage: * easy, human-readable data format (native web browser format) * automatic parameter verification (we can also verify return values) * automatic generation of API documentation * easy way to create command line tools (use the same API) API Stability & Breakage ------------------------ Proxmox VE tries to stay API compatible in a major release. For example, an API call that worked with 6.0 should also work with 6.4 but has no guarantee to do so with 7.0. A breaking change is defined as: * Removing an API endpoint entirely * Moving an API endpoint to a new path. Normally we add the new one already and move the legacy option on the next major version bump. * Removing parameters from an API endpoint * Changing the return type from a non-null type to another type The following examples are **not** considered as breaking change: * Changing an endpoint's return type from `null` to anything else is **not** considered as breaking change * Adding new parameters * Adding new properties to returned objects * Changing the type of an object's property to property string (nested object flattened into comma-separated list of key=value pairs) with the original property as default key * Slight semantic changes, as this is often a requirement for a bug fix, albeit we either try * to guard those under opt-in parameters * to mirror the Linux Kernel "never break user-space" principle. I.e., we break it as long as deemed small enough and useful, but we are open for addressing complaints by actual users and find a solution, or switch the behavior back to the previous one. * Adding new API endpoints API URL ------- The API uses the HTTPS protocol and the server listens to port 8006. So the base URL for that API is [https://your.server:8006/api2/json/](https://your.server:8006/api2/json/) Parameters can be passed using standard HTTP techniques: * via the URL * using `x-www-form-urlencoded` content-type for PUT and POST request. It is possible to specify the return format in the URL. Above example uses `JSON`, but you can use any of the following values: * `json`: JSON * `extjs`: JSON, but result nested inside an object, with `data` object, variant compatible with ExtJS forms * `html`: HTML formatted text - sometimes useful for debugging * `text`: plain text - sometimes useful for debugging Please contact use on the development mailing list if you need other data formats. Authentication -------------- Proxmox VE uses a ticket or token based authentication, all request to the API need to include a ticket inside a Cookie (header) or sending an API token through the Authorization header. **NOTE**: The following examples use the cURL tool in an unsafe way because they pass authentication HTTP headers through the command line. Since the command line can be read by other users, this method is not secure on untrusted systems. We recommend placing the entire header in a file accessible only by your user. For example, place it in your home directory. Then, use the `-H @/path/to/secure/file.headers` option to pass this to cURL. ### Ticket Cookie A ticket is a signed random text value with the user and creation time included. Tickets are signed by the cluster-wide authentication key that is rotated once per day. Additionally, any write (POST/PUT/DELETE) request must include a CSRF prevention token inside the HTTP header. The following examples use the `curl` command line tool. #### Example: Get a New Ticket and the CSRF Prevention Token Request - warning, command line parameters are visible to the whole system, avoid running below on untrusted hosts: `curl -k -d 'username=root@pam' --data-urlencode 'password=xxxxxxxxx' [https://10.0.0.1:8006/api2/json/access/ticket](https://10.0.0.1:8006/api2/json/access/ticket) ` Safer variant with the password in a file only readable for the user): `curl -k -d 'username=root@pam' --data-urlencode "password@$HOME/.pve-pass-file" [https://10.0.0.1:8006/api2/json/access/ticket](https://10.0.0.1:8006/api2/json/access/ticket) ` Note that we're using `--data-urlencode` for the password parameter to ensure neither curl nor the API gets confused about special characters in the password. Example Response { "data": { "CSRFPreventionToken":"4EEC61E2:lwk7od06fa1+DcPUwBTXCcndyAY", "ticket":"PVE:root@pam:4EEC61E2::rsKoApxDTLYPn6H3NNT6iP2mv...", "username":"root@pam" } } NOTE: Tickets have a limited lifetime of 2 hours. But you can simply get a new ticket by passing the old ticket as password to the `/access/ticket` method before its lifetime expired. #### Example: Use the New Ticket You need to pass the returned ticket with a cookie to any further request: `curl -k -b "PVEAuthCookie=PVE:root@pam:4EEC61E2::rsKoApxDTLYPn6H3NNT6iP2mv..." [https://10.0.0.1:8006/api2/json/](https://10.0.0.1:8006/api2/json/) ` Response: { "data": \[\ { "subdir": "version" },\ { "subdir": "cluster" },\ { "subdir": "nodes" },\ { "subdir": "storage" },\ { "subdir": "access" },\ { "subdir": "pools" }\ \] } #### Example: Ticket & CSRF for PUT, POST, DELETE Additionally, any write request (POST, PUT, DELETE) must include the `CSRFPreventionToken` header: `curl -XDELETE -H "CSRFPreventionToken: 4EEC61E2:lwk7od06fa1+DcPUwBTXCcndyAY" ...` ### API Tokens API tokens allow stateless access to most parts of the REST API by another system, software or API client. Tokens can be generated for individual users and can be given separate permissions and expiration dates to limit the scope and duration of the access. Should the API token get compromised it can be revoked without disabling the user itself. To use an API token, set the HTTP `Authorization` header value to the form of `PVEAPIToken=USER@REALM!TOKENID=UUID` when making API requests, or refer to your API client documentation. #### Example: Use API Token `curl -H 'Authorization: PVEAPIToken=root@pam!monitoring=aaaaaaaaa-bbb-cccc-dddd-ef0123456789' [https://10.0.0.1:8006/api2/json/](https://10.0.0.1:8006/api2/json/) ` Note: API tokens do not need CSRF values for POST, PUT or DELETE. Tokens are normally not used in a browser context, so the main attack vector of CSRF is not applicable in the first place. Step-by-step Example of Container Create Using the API ------------------------------------------------------ Assumptions: * the node where we log in is called APINODE * the node on which is the container will be created is called TARGETNODE * the auth cookie will be placed in the file "cookie" * the CSRF token will be placed in the file "csrftoken" Note: for ease of use we use the `jq` package which parses and pretty prints JSON data ### Export Variables export APINODE=pve4 export TARGETNODE=pve4 ### Save an Authorization Cookie on the Filesystem curl --silent --insecure --data "username=root@pam&password=yourpassword" \\ [https://$APINODE:8006/api2/json/access/ticket](https://$apinode:8006/api2/json/access/ticket) \\ | jq --raw-output '.data.ticket' | sed 's/^/PVEAuthCookie=/' > cookie ### Save a CSRF Token Locally curl --silent --insecure --data "username=root@pam&password=yourpassword" \\ [https://$APINODE:8006/api2/json/access/ticket](https://$apinode:8006/api2/json/access/ticket) \\ | jq --raw-output '.data.CSRFPreventionToken' | sed 's/^/CSRFPreventionToken:/' > csrftoken ### Test auth credentials Let's display the target node status to test that the ticket creation worked: curl --insecure --cookie "$( /sys/block/sda/queue/scheduler Set the scheduler for /dev/sda to BFQ: echo bfq > /sys/block/sda/queue/scheduler Set IO Schedulers permanently ----------------------------- This can be done via udev rules. For a basic example, the following is a rule to set the BFQ scheduler for all SCSI/SAS/SATA attached disks. Create `/etc/udev/rules.d/60-io-scheduler.rules` with content: ACTION=="add|change", KERNEL=="sd\[a-z\]\*", ATTR{queue/scheduler}="bfq" Links ----- * [https://www.kernel.org/doc/html/v6.8/block/bfq-iosched.html](https://www.kernel.org/doc/html/v6.8/block/bfq-iosched.html) * [https://www.kernel.org/doc/html/v6.8/block/blk-mq.html](https://www.kernel.org/doc/html/v6.8/block/blk-mq.html) * [https://www.kernel.org/doc/html/v6.8/block/deadline-iosched.html](https://www.kernel.org/doc/html/v6.8/block/deadline-iosched.html) * [https://cromwell-intl.com/open-source/performance-tuning/disks.html](https://cromwell-intl.com/open-source/performance-tuning/disks.html) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=IO\_Scheduler&oldid=12139](https://pve.proxmox.com/mediawiki/index.php?title=IO_Scheduler&oldid=12139) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [System Administration](https://pve.proxmox.com/wiki/Category:System_Administration "Category:System Administration") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Install Proxmox VE on Debian 13 Trixie - Proxmox VE Install Proxmox VE on Debian 13 Trixie ====================================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie#Introduction) * [2 Install a Standard Debian Trixie](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie#Install_a_Standard_Debian_Trixie) * [2.1 Ensure Hostname Resolves to Hosts IP Address](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie#Ensure_Hostname_Resolves_to_Hosts_IP_Address) * [2.1.1 Resolve Node IP Address Through /etc/hosts Entry](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie#Resolve_Node_IP_Address_Through_/etc/hosts_Entry) * [3 Install Proxmox VE](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie#Install_Proxmox_VE) * [3.1 Add Proxmox VE Repository](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie#Add_Proxmox_VE_Repository) * [3.2 Install the Proxmox VE Kernel](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie#Install_the_Proxmox_VE_Kernel) * [3.3 Install the Proxmox VE Packages](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie#Install_the_Proxmox_VE_Packages) * [3.4 Remove the Debian Kernel](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie#Remove_the_Debian_Kernel) * [3.5 Remove the os-prober Package](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie#Remove_the_os-prober_Package) * [4 Connect to the Proxmox VE Web Interface](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie#Connect_to_the_Proxmox_VE_Web_Interface) * [4.1 Create a Linux Bridge](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie#Create_a_Linux_Bridge) * [4.2 Upload Subscription Key](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie#Upload_Subscription_Key) * [5 Troubleshooting](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie#Troubleshooting) * [5.1 Proxmox VE Kernel Fails to Boot](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie#Proxmox_VE_Kernel_Fails_to_Boot) * [5.2 resolv.conf Gets Overwritten](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie#resolv.conf_Gets_Overwritten) * [5.3 ipcc\_send\_rec\[1\] failed](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie#ipcc_send_rec[1]_failed) Introduction ------------ The installation of a supported Proxmox VE server should be done via [bare-metal ISO installer](https://pve.proxmox.com/wiki/Installation) . In some cases it makes sense to install Proxmox VE on top of a running Debian Trixie 64-bit, especially if you want a custom partition layout. For this How-To any official Trixie installation medium should work. Install a Standard Debian Trixie -------------------------------- Install a standard Debian Trixie (amd64), using the expert mode found in the advanced options in order to configure a static IP address during network setup. For details consider the [Debian installation guide](https://www.debian.org/releases/stable/amd64/index.en.html) . It is recommended to only install the "standard system utilities" and "SSH server" package selection, as Proxmox VE brings its own packages for QEMU and LXC. A desktop environment is not necessary. **Note**: Installation of Proxmox VE on top of Debian is not supported when using the (experimental) systemd-boot method and Secure Boot enabled. ### Ensure Hostname Resolves to Hosts IP Address The hostname of your machine must be resolvable to an IP address. This IP address must not be a loopback one like `127.0.0.1` but one that you and other hosts can connect to. The two main options for configuring this are either through an entry in `/etc/hosts` or through a record in matching DNS zone. This article will document the `/etc/hosts` entry as its independent of the specific DNS implementation and your domain/provider. #### Resolve Node IP Address Through /etc/hosts Entry For a `/etc/hosts` record you need one of the following entries for your hostname: * 1 IPv4 or * 1 IPv6 or * 1 IPv4 and 1 IPv6 While you could keep the entry that maps the `127.0.1.1` loopback address to the hostname, as Proxmox VE's cluster system cycles through all addresses until it finds a non-loopback one, it's recommended to remove the hostname from that record if unsure as this avoids any ambiguity. For instance, if your IP address is `192.168.15.77`, and your hostname `prox4m1`, then your `/etc/hosts` file could look like: 127.0.0.1 localhost 192.168.15.77 prox4m1.proxmox.com prox4m1 # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters You can test if your setup is ok using the `hostname` command: hostname --ip-address 192.168.15.77 # should return at least one non-loopback IP address here Install Proxmox VE ------------------ ### Add Proxmox VE Repository Add the Proxmox VE repository sources using the preferred deb822 style format: cat > /etc/apt/sources.list.d/pve-install-repo.sources << EOL Types: deb URIs: [http://download.proxmox.com/debian/pve](http://download.proxmox.com/debian/pve) Suites: trixie Components: pve-no-subscription Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg EOL Add the Proxmox VE repository key as root (or use sudo): wget [https://enterprise.proxmox.com/debian/proxmox-archive-keyring-trixie.gpg](https://enterprise.proxmox.com/debian/proxmox-archive-keyring-trixie.gpg) -O /usr/share/keyrings/proxmox-archive-keyring.gpg # verify sha256sum /usr/share/keyrings/proxmox-archive-keyring.gpg 136673be77aba35dcce385b28737689ad64fd785a797e57897589aed08db6e45 /usr/share/keyrings/proxmox-archive-keyring.gpg md5sum /usr/share/keyrings/proxmox-archive-keyring.gpg 77c8b1166d15ce8350102ab1bca2fcbf /usr/share/keyrings/proxmox-archive-keyring.gpg **Note**: To migrate pre-existing repository sources to the recommended deb822 style format, you can run: apt modernize-sources Update your repository and system by running: apt update && apt full-upgrade ### Install the Proxmox VE Kernel First you need to install and boot the Proxmox VE kernel, as some packages depend on specific kernel compile flags to be set or feature extensions (e.g., for apparmor) to be available. apt install proxmox-default-kernel systemctl reboot ### Install the Proxmox VE Packages Install the Proxmox VE packages apt install proxmox-ve postfix open-iscsi chrony Note that you can replace `chrony` with any other NTP daemon, but we recommend against using `systemd-timesyncd` on server systems, and the `ntpsec-ntpdate` option might conflict with bringing up networking on boot on some hardware. Configure packages which require user input on installation according to your needs. If you have a mail server in your network, you should configure postfix as a **satellite system**. Your existing mail server will then be the _relay host_ which will route the emails sent by Proxmox VE to their final recipient. If you don't know what to enter here, choose **local only** and leave the _system name_ as is. ### Remove the Debian Kernel Proxmox VE ships its own kernel and keeping the Debian default kernel can lead to trouble on upgrades, for example, with Debian point releases. Therefore, you **must** remove the default Debian kernel: apt remove linux-image-amd64 'linux-image-6.12\*' Update and check grub2 config by running (not required if `systemd-boot` is used): update-grub ### Remove the os-prober Package It is recommended to remove the `os-prober` package, as it scans all the partitions of the host to create dual-boot GRUB entries. However, the scanned partitions can also include those assigned to virtual machines, which should not be added as boot entries. If Proxmox VE was not installed as dual boot option beside another OS, it is safe to remove the `os-prober` package by running: apt remove os-prober Connect to the Proxmox VE Web Interface --------------------------------------- Connect to the admin web interface (`[https://your-ip-address:8006](https://your-ip-address:8006/) `). If you have a fresh install and have not added any users yet, you should select PAM authentication realm and login with `root` user account. ### Create a Linux Bridge Create a Linux Bridge called `vmbr0`, and add your first network interface to it. The recommended default configuration can be adapted from the example given in the documentation. See the [default configuration using a bridge](https://pve.proxmox.com/wiki/Network_Configuration#_default_configuration_using_a_bridge) . ### Upload Subscription Key The Proxmox VE enterprise repository is set up automatically during the installation as it's the recommended repository for stable, enterprise usage. Access to that repository is one of the benefits of a Proxmox VE subscription, see [this forum thread for more info about why you should get one](https://forum.proxmox.com/threads/proxmox-ve-support-subscriptions-and-why-everybody-should-buy-one.9244/) . You should **upload your subscription key** now in the web interface, then you can remove the no-subscription repository added for installation. rm /etc/apt/sources.list.d/pve-install-repo.sources Troubleshooting --------------- ### Proxmox VE Kernel Fails to Boot If the kernel fails to boot with `error: bad shim signature.`, make sure Secure Boot is disabled. ### resolv.conf Gets Overwritten The Proxmox VE GUI expects to control DNS management and will no longer take its DNS settings from `/etc/network/interfaces`. Any package that auto-generates (overwrites) `/etc/resolv.conf` will cause DNS to fail, e.g. packages 'resolvconf' for IPv4 and 'rdnssd' for IPv6. ### ipcc\_send\_rec\[1\] failed If you see messages like `ipcc_send_rec[1] failed: Connection refused` then you should review your `/etc/hosts` file according to the instructions above. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Install\_Proxmox\_VE\_on\_Debian\_13\_Trixie&oldid=12339](https://pve.proxmox.com/mediawiki/index.php?title=Install_Proxmox_VE_on_Debian_13_Trixie&oldid=12339) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Installation](https://pve.proxmox.com/wiki/Category:Installation "Category:Installation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # OpenVZ VM First Boot Setup Tips - Proxmox VE OpenVZ VM First Boot Setup Tips =============================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/OpenVZ_VM_First_Boot_Setup_Tips#mw-head) [Jump to search](https://pve.proxmox.com/wiki/OpenVZ_VM_First_Boot_Setup_Tips#searchInput) ℹ️ **Note**: Article about the old stable Proxmox VE 3.x releases If we copy over a setup script into a VM Template during it's build, we can execute it on first boot up of it's newly created VM and on script completion we can remove the script and hence prevent it from running on subsequent boot ups. Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/OpenVZ_VM_First_Boot_Setup_Tips#Introduction) * [1.1 Advanced Bash Scripting Guide](https://pve.proxmox.com/wiki/OpenVZ_VM_First_Boot_Setup_Tips#Advanced_Bash_Scripting_Guide) * [1.2 Current IP of the container](https://pve.proxmox.com/wiki/OpenVZ_VM_First_Boot_Setup_Tips#Current_IP_of_the_container) * [1.3 Fully Qualified Domain Name of the container](https://pve.proxmox.com/wiki/OpenVZ_VM_First_Boot_Setup_Tips#Fully_Qualified_Domain_Name_of_the_container) * [1.4 Generate Random Password](https://pve.proxmox.com/wiki/OpenVZ_VM_First_Boot_Setup_Tips#Generate_Random_Password) * [1.5 Generate an MD5 hash (lowercase) of a random number](https://pve.proxmox.com/wiki/OpenVZ_VM_First_Boot_Setup_Tips#Generate_an_MD5_hash_(lowercase)_of_a_random_number) * [1.6 MySQL Random root Password](https://pve.proxmox.com/wiki/OpenVZ_VM_First_Boot_Setup_Tips#MySQL_Random_root_Password) Introduction ------------ This article lists some useful oneliners especially for building OpenVZ templates using the [Debian Appliance Builder](https://pve.proxmox.com/wiki/Debian_Appliance_Builder "Debian Appliance Builder") . Here are some bash shell script statements that perform some common tasks that may be used in such a script (the value will be placed in a variable for example **VAR** and it can be used with **${VAR}** in the scripts): #### Advanced Bash Scripting Guide Get the 2.50 MB Free eBook at: [http://tldp.org/LDP/abs/abs-guide.pdf](http://tldp.org/LDP/abs/abs-guide.pdf) #### Current IP of the container MYIP=\`ifconfig venet0:0 | grep "inet" | cut -d":" -f 2 | cut -d " " -f 1\` #### Fully Qualified Domain Name of the container FQDNAME=\`hostname\`.\`dnsdomainname\` #### Generate Random Password The following will generate a 12 character random password **with special characters**: UPASSWD=\`openssl rand -base64 12\` The following will generate a 12 character random password **without special characters**: UPASSWD=\`dd if=/dev/urandom count=200 bs=1 2>/dev/null|tr "\\n" " "|sed 's/\[^a-zA-Z0-9\]//g'|cut -c-12\` Do not use reserved keywords like **PASSWD**, **HOSTNAME**, etc., as userland variables, since **squeeze** does not like **bashisms** and Debian is progressing to strict **dash** from lenient **bash**.... #### Generate an MD5 hash (lowercase) of a random number SKEY3=\`dd if=/dev/urandom count=2000 bs=1 2>/dev/null|tr "\\n" " "|sed 's/\[^0-9\]//g'|cut -c-32\` UNIQAPPKEY=\`echo -n ${SKEY3} | md5sum |cut -d ' ' -f 1\` #### MySQL Random root Password echo Current \\"root\\" password for MySQL is stored in \\"/root/.my.cnf\\" file echo ...... and is \\"\`cat /root/.my.cnf | grep password | cut -d'"' -f 2\`\\" Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=OpenVZ\_VM\_First\_Boot\_Setup\_Tips&oldid=9242](https://pve.proxmox.com/mediawiki/index.php?title=OpenVZ_VM_First_Boot_Setup_Tips&oldid=9242) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Proxmox VE 3.x](https://pve.proxmox.com/wiki/Category:Proxmox_VE_3.x "Category:Proxmox VE 3.x") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Intel Modular Server HA" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Intel Modular Server HA" ============================================ ← [Intel Modular Server HA](https://pve.proxmox.com/mediawiki/index.php?title=Intel_Modular_Server_HA&action=edit&redlink=1 "Intel Modular Server HA (page does not exist)") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Intel_Modular_Server_HA#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Intel_Modular_Server_HA#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Intel Modular Server HA](https://pve.proxmox.com/mediawiki/index.php?title=Intel_Modular_Server_HA&action=edit&redlink=1 "Intel Modular Server HA (page does not exist)") **: Displaying 2 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Intel_Modular_Server_HA&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Intel_Modular_Server_HA&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Intel_Modular_Server_HA&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Intel_Modular_Server_HA&limit=500) ) * [Fencing](https://pve.proxmox.com/wiki/Fencing "Fencing") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Fencing "Special:WhatLinksHere") ) * [High Availability Cluster](https://pve.proxmox.com/wiki/High_Availability_Cluster "High Availability Cluster") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=High+Availability+Cluster "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Intel_Modular_Server_HA&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Intel_Modular_Server_HA&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Intel_Modular_Server_HA&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Intel_Modular_Server_HA&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Intel\_Modular\_Server\_HA](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Intel_Modular_Server_HA) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Manual: cpu-models.conf - Proxmox VE Manual: cpu-models.conf ======================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Manual:_cpu-models.conf#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Manual:_cpu-models.conf#searchInput) NAME ---- cpu-models.conf - Custom CPU model configuration file SYNOPSIS -------- _/etc/pve/virtual-guest/cpu-models.conf_ DESCRIPTION ----------- The /etc/pve/virtual-guest/cpu-models.conf file stores custom CPU models, which can be used by VMs to get access to advanced CPU features (for example custom CPU flags). File Format ----------- CPU models each have their own section in the file, beginning with the header: cpu-model: Note that does not include the _custom-_ prefix, which is required in VM configs to denote custom CPU models. For example, if the is _foobar_, the CPU for a VM would need to be configured as _custom-foobar_. Each section can specify several options. They are indented by either one TAB character or multiple spaces. Every option and its value is separated by one space, for example: reported-model qemu64 See below for all available options. Blank lines and those starting with a # are ignored. Options ------- flags: <+FLAG\[;-FLAG...\]> List of additional CPU flags separated by _;_. Use _+FLAG_ to enable, _\-FLAG_ to disable a flag. There is a special _nested-virt_ shorthand which controls nested virtualization for the current CPU (_svm_ for AMD and _vmx_ for Intel). Custom CPU models can specify any flag supported by QEMU/KVM, VM-specific flags must be from the following set for security reasons: nested-virt, md-clear, pcid, spec-ctrl, ssbd, ibpb, virt-ssbd, amd-ssbd, amd-no-ssb, pdpe1gb, hv-tlbflush, hv-evmcs, aes guest-phys-bits: (32 - 64) Number of physical address bits available to the guest. hidden: (_default =_ 0) Do not identify as a KVM virtual machine. hv-vendor-id: The Hyper-V vendor ID. Some drivers or programs inside Windows guests need a specific ID. phys-bits: <8-64|host> The physical memory address bits that are reported to the guest OS. Should be smaller or equal to the host’s. Set to _host_ to use value from host CPU, but note that doing so will break live migration to CPUs with other values. reported-model: <486 | Broadwell | Broadwell-IBRS | Broadwell-noTSX | Broadwell-noTSX-IBRS | Cascadelake-Server | Cascadelake-Server-noTSX | Cascadelake-Server-v2 | Cascadelake-Server-v4 | Cascadelake-Server-v5 | Conroe | Cooperlake | Cooperlake-v2 | EPYC | EPYC-Genoa | EPYC-IBPB | EPYC-Milan | EPYC-Milan-v2 | EPYC-Rome | EPYC-Rome-v2 | EPYC-Rome-v3 | EPYC-Rome-v4 | EPYC-v3 | EPYC-v4 | GraniteRapids | Haswell | Haswell-IBRS | Haswell-noTSX | Haswell-noTSX-IBRS | Icelake-Client | Icelake-Client-noTSX | Icelake-Server | Icelake-Server-noTSX | Icelake-Server-v3 | Icelake-Server-v4 | Icelake-Server-v5 | Icelake-Server-v6 | IvyBridge | IvyBridge-IBRS | KnightsMill | Nehalem | Nehalem-IBRS | Opteron\_G1 | Opteron\_G2 | Opteron\_G3 | Opteron\_G4 | Opteron\_G5 | Penryn | SandyBridge | SandyBridge-IBRS | SapphireRapids | SapphireRapids-v2 | Skylake-Client | Skylake-Client-IBRS | Skylake-Client-noTSX-IBRS | Skylake-Client-v4 | Skylake-Server | Skylake-Server-IBRS | Skylake-Server-noTSX-IBRS | Skylake-Server-v4 | Skylake-Server-v5 | Westmere | Westmere-IBRS | athlon | core2duo | coreduo | host | kvm32 | kvm64 | max | pentium | pentium2 | pentium3 | phenom | qemu32 | qemu64> (_default =_ kvm64) CPU model and vendor to report to the guest. Must be a QEMU/KVM supported model. Only valid for custom CPU model definitions, default models will always report themselves to the guest OS. Example File ------------ cpu-model: avx flags +avx;+avx2 phys-bits host hidden 0 hv-vendor-id proxmox reported-model kvm64 Copyright and Disclaimer ------------------------ Copyright © 2007-2022 Proxmox Server Solutions GmbH This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details. You should have received a copy of the GNU Affero General Public License along with this program. If not, see [https://www.gnu.org/licenses/](https://www.gnu.org/licenses/) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Manual:\_cpu-models.conf&oldid=12404](https://pve.proxmox.com/mediawiki/index.php?title=Manual:_cpu-models.conf&oldid=12404) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Reference Documentation](https://pve.proxmox.com/wiki/Category:Reference_Documentation "Category:Reference Documentation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Storage" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Storage" ============================ ← [Storage](https://pve.proxmox.com/wiki/Storage "Storage") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Storage#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Storage#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Storage](https://pve.proxmox.com/wiki/Storage "Storage") **: Displaying 4 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Storage&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Storage&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Storage&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Storage&limit=500) ) * [Main Page](https://pve.proxmox.com/wiki/Main_Page "Main Page") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Main+Page "Special:WhatLinksHere") ) * [Benchmarking Storage](https://pve.proxmox.com/wiki/Benchmarking_Storage "Benchmarking Storage") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Benchmarking+Storage "Special:WhatLinksHere") ) * [Live Snapshots](https://pve.proxmox.com/wiki/Live_Snapshots "Live Snapshots") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Live+Snapshots "Special:WhatLinksHere") ) * [Storage Plugin Development](https://pve.proxmox.com/wiki/Storage_Plugin_Development "Storage Plugin Development") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Storage+Plugin+Development "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Storage&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Storage&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Storage&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Storage&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Storage](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Storage) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Windows 2003 guest best practices" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Windows 2003 guest best practices" ====================================================== ← [Windows 2003 guest best practices](https://pve.proxmox.com/wiki/Windows_2003_guest_best_practices "Windows 2003 guest best practices") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Windows_2003_guest_best_practices#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Windows_2003_guest_best_practices#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Windows 2003 guest best practices](https://pve.proxmox.com/wiki/Windows_2003_guest_best_practices "Windows 2003 guest best practices") **: Displaying 3 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Windows_2003_guest_best_practices&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Windows_2003_guest_best_practices&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Windows_2003_guest_best_practices&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Windows_2003_guest_best_practices&limit=500) ) * [Windows 2008 guest best practices](https://pve.proxmox.com/wiki/Windows_2008_guest_best_practices "Windows 2008 guest best practices") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Windows+2008+guest+best+practices "Special:WhatLinksHere") ) * [Windows 2012 guest best practices](https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices "Windows 2012 guest best practices") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Windows+2012+guest+best+practices "Special:WhatLinksHere") ) * [Additional ways to migrate to Proxmox VE](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE "Additional ways to migrate to Proxmox VE") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Additional+ways+to+migrate+to+Proxmox+VE "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Windows_2003_guest_best_practices&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Windows_2003_guest_best_practices&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Windows_2003_guest_best_practices&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Windows_2003_guest_best_practices&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Windows\_2003\_guest\_best\_practices](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Windows_2003_guest_best_practices) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Upgrade from 6.x to 7.0" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Upgrade from 6.x to 7.0" ============================================ ← [Upgrade from 6.x to 7.0](https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0 "Upgrade from 6.x to 7.0") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Upgrade_from_6.x_to_7.0#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Upgrade_from_6.x_to_7.0#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Upgrade from 6.x to 7.0](https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0 "Upgrade from 6.x to 7.0") **: Displaying 4 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_6.x_to_7.0&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_6.x_to_7.0&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_6.x_to_7.0&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_6.x_to_7.0&limit=500) ) * [Downloads](https://pve.proxmox.com/wiki/Downloads "Downloads") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Downloads "Special:WhatLinksHere") ) * [Quick installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Quick+installation "Special:WhatLinksHere") ) * [Upgrade from 6.x to 7.0](https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0 "Upgrade from 6.x to 7.0") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Upgrade+from+6.x+to+7.0 "Special:WhatLinksHere") ) * [Ceph Octopus to Pacific](https://pve.proxmox.com/wiki/Ceph_Octopus_to_Pacific "Ceph Octopus to Pacific") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Ceph+Octopus+to+Pacific "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_6.x_to_7.0&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_6.x_to_7.0&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_6.x_to_7.0&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Upgrade_from_6.x_to_7.0&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Upgrade\_from\_6.x\_to\_7.0](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Upgrade_from_6.x_to_7.0) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Proxmox Datacenter Manager Upgrade from Alpha to 1 - Proxmox VE Proxmox Datacenter Manager Upgrade from Alpha to 1 ================================================== From Proxmox VE (Redirected from [Proxmox Datacenter Manager Upgrade from Alpha to Beta](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta&redirect=no "Proxmox Datacenter Manager Upgrade from Alpha to Beta") ) [Jump to navigation](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta#Introduction) * [2 In-Place Upgrade](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta#In-Place_Upgrade) * [2.1 Prerequisites](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta#Prerequisites) * [2.2 Actions Step-by-Step](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta#Actions_Step-by-Step) * [2.2.1 Continuously use the pdmAtoB Checklist Script](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta#Continuously_use_the_pdmAtoB_Checklist_Script) * [2.2.2 Update the Configured APT Repositories](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta#Update_the_Configured_APT_Repositories) * [2.2.2.1 Ensure Repository Archive Keyring is Installed](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta#Ensure_Repository_Archive_Keyring_is_Installed) * [2.2.2.2 Update Debian Base Repositories to Trixie](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta#Update_Debian_Base_Repositories_to_Trixie) * [2.2.2.3 Add the Proxmox Datacenter Manager 1 Package Repository](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta#Add_the_Proxmox_Datacenter_Manager_1_Package_Repository) * [2.2.3 Upgrade the System](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta#Upgrade_the_System) * [2.2.4 Check Result & Reboot Into Updated Kernel](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta#Check_Result_&_Reboot_Into_Updated_Kernel) * [2.3 Following the Proxmox Datacenter Manager Upgrade](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta#Following_the_Proxmox_Datacenter_Manager_Upgrade) * [2.3.1 Check Status of Services](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta#Check_Status_of_Services) * [2.3.2 Optional: Modernize APT Repository Sources](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta#Optional:_Modernize_APT_Repository_Sources) * [3 Potential Issues](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta#Potential_Issues) * [3.1 Older Hardware and New 6.14 Kernel](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta#Older_Hardware_and_New_6.14_Kernel) * [3.2 Network Interface Name Changes](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta#Network_Interface_Name_Changes) * [3.3 Systemd-Boot Meta-Package Changes the Bootloader Configuration Automatically and Should Be Uninstalled](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta#Systemd-Boot_Meta-Package_Changes_the_Bootloader_Configuration_Automatically_and_Should_Be_Uninstalled) Introduction ============ Proxmox Datacenter Manager Beta is based on Debian 13 Trixie, a new major release, and introduces several new major features and changes. You should plan the upgrade carefully, **make and verify backups** before beginning, and test extensively. Depending on the existing configuration, several manual steps — including some downtime — may be required. **Note:** A valid and tested backup is _always_ required before starting the upgrade process. You can test the backup beforehand, for example, in a (virtualized) test lab setup. In case the system is customized and/or uses additional packages or any other third party repositories/packages, ensure those packages are also upgraded to and compatible with Debian Trixie. In-Place Upgrade ================ Prerequisites ------------- * Perform these actions via SSH, a physical console or a remote management console like iKVM or IPMI. * If you use SSH, you should use a terminal multiplexer (for example, tmux or screen) to ensure the upgrade can continue even if the SSH connection gets interrupted. * Do not carry out the upgrade via the web UI console directly, as this will get interrupted during the upgrade. * Upgraded to the latest version of Proxmox Datacenter Manager Alpha, see the [roadmap](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap "Proxmox Datacenter Manager Roadmap") for potential important changes in the stable release. Use `apt update` and `apt dist-upgrade` (still with Debian Bookworm repos setup) to upgrade to the latest Alpha release * Verify version: The command `proxmox-datacenter-manager-admin versions` should print: `proxmox-datacenter-manager 0.1.12 running version: 0.1.12` (or higher) Note: The last command has only been introduced in Proxmox Datacenter Manager version 0.1.12, so if the above command fails, you are not running a new enough version. You should upgrade to that first. * If you do not get updates, check that your [package repositories](https://pve.proxmox.com/wiki/Package_Repositories#_debian_base_repositories "Package Repositories") configuration is correct. * Make a backup of `/etc/proxmox-datacenter-manager` to ensure that in the worst case, any relevant configuration can be recovered: tar czf "pdm-alpha-etc-backup-$(date -I).tar.gz" -C "/etc" "proxmox-datacenter-manager" * Ensure that you have at least 10 GB free disk space on the root mount point: df -h / In-place upgrades are carried out via APT. Basic familiarity with APT is required to proceed with this upgrade mechanism. Actions Step-by-Step -------------------- Before starting the upgrade process, ensure that your Proxmox Datacenter Manager host is up-to-date. ### Continuously use the pdmAtoB Checklist Script A small checklist program named pdmAtoB is included in the latest Proxmox Datacenter Manager Alpha packages. The program will provide hints and warnings about potential issues before, during and after the upgrade process. You can call it by executing: pdmAtoB This script only checks and reports things. By default, no changes to the system are made and thus, none of the issues will be automatically fixed. You should keep in mind that Proxmox Datacenter Manager can be heavily customized, so the script may not recognize all the possible problems with a particular setup! It is recommended to re-run the script after each attempt to fix an issue. This ensures that the actions taken actually fixed the respective warning. ### Update the Configured APT Repositories First, make sure that the system is using the latest Proxmox Datacenter Manager packages: apt update apt dist-upgrade proxmox-datacenter-manager-admin versions The last command should report a version of at least `0.1.12` or newer. #### Ensure Repository Archive Keyring is Installed To ensure your system trusts the new APT archive keyring for our Debian Trixie-based releases, install the `proxmox-archive-keyring` package before switching the repos to Trixie. apt install proxmox-archive-keyring #### Update Debian Base Repositories to Trixie Update all repository entries to Trixie: sed -i 's/bookworm/trixie/g' /etc/apt/sources.list Ensure that there are no remaining Debian Bookworm specific repositories left. Check all files in the /etc/apt/sources.list.d/ folder (like `pbs-enterprise.list`) and also the top-level `/etc/apt/sources.list` file. If you are already using sources in the new deb822 format, you will also need to check `.sources` files in the same location. ℹ️ **Note**: Instead of removing older repositories, you can also disable them. In `.list` files simply comment them out by adding a `#` to the beginning of the line. In `.sources` files, you can add the line `Enabled: no` to any stanza you want to disable. See the [Package Repositories](https://pve.proxmox.com/wiki/Package_Repositories#_debian_base_repositories "Package Repositories") section in the reference docs for the correct Proxmox Datacenter Manager Beta / Debian Trixie repositories. #### Add the Proxmox Datacenter Manager 1 Package Repository You should be able to add the pdm-enterprise repository with this command: cat > /etc/apt/sources.list.d/pdm-test.sources << EOF Types: deb URIs: [https://enterprise.proxmox.com/debian/pdm](https://enterprise.proxmox.com/debian/pdm) Suites: trixie Components: pdm-enterprise Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg EOF Make sure that `apt` picks it up correctly by running `apt update` and checking the output of `apt policy`. Then remove the previous Proxmox Datacenter Manager Alpha repository from either the `/etc/apt/sources.list`, `/etc/apt/sources-list.d/pdm-test.list` or any other `.list` or `.sources` file you may have added it to. You can use `apt update` and `apt policy` again to make sure the old repository is not being used anymore. ℹ️ **Note**: Instead of removing older repositories, you can also disable them. In `.list` files simply comment them out by adding a `#` to the beginning of the line. In `.sources` files, you can add the line `Enabled: no` to any stanza you want to disable. Make sure to check that all the `.list` and `.sources` files you added in /etc/apt/sources.list.d/ got switched over to Trixie correctly. To make sure that all package repositories are being picked up correctly first run the following command to refresh the package index: apt update Note that this command does not start the upgrade itself, it only refreshes the package index and must not return any error. Then run: apt policy Verify that the output of this command shows only Trixie repositories and that the Proxmox Datacenter Manager repository shows up correctly. ### Upgrade the System Note that the time required for finishing this step heavily depends on the system's performance, especially the root filesystem's IOPS and bandwidth. A slow spinner can take up to 60 minutes or more, while for a high-performance server with SSD storage, the upgrade can be finished in less than 5 minutes. ℹ️ **Note**: While the packages are being upgraded certain operations and requests to the API might fail (for example, logging in as a system user in the `pam` realm) To upgrade the packages, run: apt update apt dist-upgrade While running the `apt dist-upgrade` command, you may be asked to approve changes to configuration files and some service restarts among other prompts. This includes: * The output of `apt-listchanges`: You can simply exit it by pressing q. * Selecting your default keyboard settings: Simply use the arrow keys to navigate to the one applicable in your case and hit enter. * Questions about service restarts (like `Restart services during package upgrades without asking?`): Use the default if unsure, as the reboot after the upgrade will restart all services cleanly anyway. * Questions about (default) configuration changes: It is suggested to check the difference for each file in question and choose the answer accordingly to what's most appropriate for your setup. Common configuration files with changes, and the recommended choices are: * `/etc/issue` -> Proxmox Datacenter Manager will auto-generate this file on boot, and it has only cosmetic effects on the login console. Using the default "No" (keep your currently-installed version) is safe here. * `/etc/ssh/sshd_config` -> If you have not changed this file manually, the only differences should be a replacement of `ChallengeResponseAuthentication no` with `KbdInteractiveAuthentication no` and some irrelevant changes in comments (lines starting with `#`). If this is the case, both options are safe, though we would recommend installing the package maintainer's version in order to move away from the deprecated `ChallengeResponseAuthentication` option. If there are other changes, we suggest to inspect them closely and decide accordingly. * `/etc/default/grub` -> Here you may want to take special care, as this is normally only asked for if you changed it manually, e.g., for adding some kernel command line option. It's recommended to check the difference for any relevant change, note that changes in comments (lines starting with `#`) are not relevant. If unsure, we suggest selecting "No" (keep your currently-installed version) ### Check Result & Reboot Into Updated Kernel If the command exits successfully, you can reboot the system in order to enable the new kernel. systemctl reboot Please note that you should reboot even if you already used the 6.14 kernel previously, through the opt-in package on Proxmox Datacenter Manager Alpha. Following the Proxmox Datacenter Manager Upgrade ------------------------------------------------ Empty the browser cache and/or force-reload the Web UI (CTRL + SHIFT + R, or for MacOS ⌘ + Alt + R). ### Check Status of Services Check that the statuses of the main services are `active (running)` systemctl status proxmox-datacenter-api.service proxmox-datacenter-privileged-api.service ### Optional: Modernize APT Repository Sources You can migrate existing repository sources to the recommended deb822 style format, by running: apt modernize-sources By answering the following prompt with "n" you can check the changes the command would make before applying them. To apply them simply run the command again and respond to the prompt with "Y". The command will also keep the old `.list` files around by appending `.bak` to them. So you will have the new `.sources` files and the old repository configurations in the `.list.bak` files. You can remove the leftover backup files once you verified that everything works smoothly with the new format. Potential Issues ================ As a Debian based distribution, Proxmox Datacenter Manager is affected by most issues and changes affecting Debian. Thus, ensure that you read the [upgrade specific issues for Debian Trixie](https://www.debian.org/releases/trixie/release-notes/issues.en.html) . Please also check the known issue list from the [Proxmox Datacenter Manager 1.0 changelog](https://pdm.proxmox.com/docs/roadmap.html#known-issues-breaking-changes) . Older Hardware and New 6.14 Kernel ---------------------------------- Compatibility of old hardware (released >= 10 years ago) is not as thoroughly tested as more recent hardware. For old hardware we highly recommend testing compatibility of Proxmox Datacenter Manager with identical (or at least similar) hardware before upgrading any production machines. We will expand this section with potential pitfalls and workarounds once they arise. Network Interface Name Changes ------------------------------ The new kernel can recognize more hardware features such as virtual function of PCI(e) devices. Since network names are usually derived from PIC(e) addresses and features recognized by the kernel, the network configuration might need to be adapted to match the new interface names. In such cases, the network connection to a Proxmox Datacenter Manager host might be lost during or after the upgrade process. Hence, it is generally recommended to have either physical access or an independent remote connection to the host (for example, via IPMI or iKVM). Systemd-Boot Meta-Package Changes the Bootloader Configuration Automatically and Should Be Uninstalled ------------------------------------------------------------------------------------------------------ With Debian Trixie the `systemd-boot` package got split up a bit further into `systemd-boot-efi` (containing the EFI-binary used for booting), `systemd-boot-tools` (containing `bootctl`) and the `systemd-boot` meta-package (containing hooks which run upon upgrades of itself and other packages and install systemd-boot as bootloader). As Proxmox Systems usually handle the installation of `systemd-boot` as bootloader using `proxmox-boot-tool` the meta-package should be removed. The package was automatically shipped for systems installed from the Proxmox Datacenter Manager Alpha to Proxmox Datacenter Manager ISOs, as it contained `bootctl` in bookworm. If the `pdmAtoB` checklist script suggests it, the `systemd-boot` meta-package is safe to remove unless you manually installed it and are using `systemd-boot` as a bootloader. Should `systemd-boot-efi` and `systemd-boot-tools` be required, `pdmAtoB` will warn you accordingly. The `pdmAtoB` checklist script will change its output depending on the state of the upgrade, and should be [run continuously before and after the upgrade](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta#Continuously_use_the_pdmAtoB_Checklist_Script) . It will print which packages should be removed or added at the appropriate time. The only situation where you should keep the meta-package systemd-boot installed is if you manually setup `systemd-boot` for your system. See also [bug for systemd-boot](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1110177) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Proxmox\_Datacenter\_Manager\_Upgrade\_from\_Alpha\_to\_1&oldid=12442](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1&oldid=12442) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Upgrade](https://pve.proxmox.com/wiki/Category:Upgrade "Category:Upgrade") * [Proxmox Datacenter Manager](https://pve.proxmox.com/wiki/Category:Proxmox_Datacenter_Manager "Category:Proxmox Datacenter Manager") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Cloud-Init FAQ - Proxmox VE Cloud-Init FAQ ============== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#searchInput) Contents -------- * [1 What is cloud-init?](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#What_is_cloud-init?) * [2 Usage in Proxmox VE](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#Usage_in_Proxmox_VE) * [2.1 Options](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#Options) * [2.1.1 User](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#User) * [2.1.2 Password](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#Password) * [2.1.3 SSH public key](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#SSH_public_key) * [2.1.4 DNS domain and DNS server](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#DNS_domain_and_DNS_server) * [2.1.5 IP Config (ethX)](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#IP_Config_(ethX)) * [2.1.6 citype (CLI only)](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#citype_(CLI_only)) * [3 Quirks and Requirements for cloud init images.](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#Quirks_and_Requirements_for_cloud_init_images.) * [3.1 Networking](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#Networking) * [3.2 Hostname](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#Hostname) * [4 Creating a custom cloud image](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#Creating_a_custom_cloud_image) * [4.1 Step 1: Install the base system](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#Step_1:_Install_the_base_system) * [4.2 Step 2: System preparation](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#Step_2:_System_preparation) * [4.2.1 Rename network devices](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#Rename_network_devices) * [4.2.2 Add a default user](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#Add_a_default_user) * [4.2.3 Install standard packages](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#Install_standard_packages) * [4.2.4 Setup a serial terminal](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#Setup_a_serial_terminal) * [4.2.5 Clean up the image](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#Clean_up_the_image) * [4.3 Step 3: Install and configure cloud-init](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#Step_3:_Install_and_configure_cloud-init) * [4.3.1 Configure data sources](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#Configure_data_sources) * [4.3.2 Set the default user name](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#Set_the_default_user_name) * [4.4 Troubleshooting](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#Troubleshooting) * [5 See Also](https://pve.proxmox.com/wiki/Cloud-Init_FAQ#See_Also) What is cloud-init? =================== Cloud-init is basically a program which runs in a guest machine on boot, which search for configuration data to apply to the guest system during initialization. The idea is to have a defined OS independent configuration format for options common to many systems (such as the hostname and networking configuration). In practice this doesn't always work very well, so there are a few quirks and issues you should be aware of, as we will _not_ be adding OS and cloud-init-version specific workarounds, as that would defeat the whole point of this system. See the [Cloud-Init Support](https://pve.proxmox.com/wiki/Cloud-Init_Support "Cloud-Init Support") page of the reference documentation for detailed command line examples. Usage in Proxmox VE =================== In Proxmox VE cloud-init images are attached as ISO images via a virtual CDROM drive. In order to start using the `cloud-init` tab in the Web UI, you'll have to add such a drive. This can be done in the `Hardware` tab, by clicking the `Add` button and selecting `CloudInit Drive`. Afterwards, the options in the `cloud-init` tab become usable. Options ------- ### User Cloud Images are often setup to setup a user's password and/or ssh keys. This is usually done for a default user often named after the distribution running. This option may be used to change which user to setup. Using this should create a user of the specified name and apply the password and ssh key settings. ### Password The password option should be straightforward. Take note however, that before cloud-init version 17.1, only plaintext passwords were supported. Our API by default pre-hashes passwords sent as plaintext, so to set a password on older cloud images, the plaintext passwords would need to be manually written into the VM config in `/etc/pve/qemu-server/${vmid}.conf` ### SSH public key This can be one or multiple SSH public keys setup for the above configured user. When loading them from a file, however, note that Proxmox VE currently will not accept comment lines. ### DNS domain and DNS server These work similar to their container counterparts, and similarly multiple DNS servers can be specified as a whitespace separated list. ### IP Config (ethX) Much like with containers, this will configure the guest's IP address. There should be one such entry per network interface. Note that the way the network configuration is passed to the guest can be quite different depending on what type of cloud-init image is being used. This can be changed via the `citype` option. See below. ### citype (CLI only) Currently Proxmox VE supports two types of cloud-init images: nocloud v1 (the default and recommended type), and configdrive v2. Most images from major distributions should work fine with the default. In the future, nocloud v2 may be supported as well, which should offer a more robust way to configure network devices as it does not depend on specific device names (see the Networking section below). The configdrive v2 variant may work for Windows guests using cloudbase-init, but this is not officially supported. Quirks and Requirements for cloud init images. ============================================== Ideally the cloud image should be running an up-to-date cloud-init version, at least 18.2 or newer. There are several issues with older versions mentioned below. Networking ---------- For legacy reasons the network device names of cloud images are required to use the "old" network device names: (eth0, eth1, ...). This is because older cloud-init configuration formats made the same mistake as everyone else before, matching interfaces by name with no other option. Newer cloud-init versions support netplan-like configurations where you can match by mac address or driver, but these aren't widely available in the current cloud-init images. (At the time of writing, only the ubuntu bionic images supported this.). The newer nocloud v2 config format will be supported in the future, where this requirement is lifted. Note that (at the time of writing) the cloud-init version shipped with centos 7 images does cannot handle CIDR notation for IPv4 addresses which we use in our Proxmox VE 5.2 release version. Hostname -------- Before cloud-init version 18.2, the host name was not set before DHCP requests, meaning the image's default host name is being used at that point, leading to hostname clashes. Creating a custom cloud image ============================= Step 1: Install the base system ------------------------------- This can be any system for which you can install a working cloud-init package. Note that if you create this image yourself, it would be a good idea to try to install a more recent version of cloud-init than what you find in various upstream distribution repositories. Step 2: System preparation -------------------------- ### Rename network devices For best compatibility, specifically when using older cloud-init versions, you'll want to setup udev rules / systemd-networkd configuration/link files etc. to revert from predictable device names to kernel names (`eth0` and so on). See the Predictable Network Interface Names <[https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/](https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/) \> chapter on freedesktop.org. ### Add a default user Typically when using cloud-init you'll log into a predefined user other than root, although this is optional. The user name can be configured in the cloud-init package, and overridden by Proxmox VE's cloud-init configuration options. ### Install standard packages Since you usually won't be logging in as root and get a preconfigured user setup, you'll want to install `sudo` in order to be able to perform administrative tasks later on. Besides setting a user password, you can also provide ssh keys deployed by cloud-init on boot, so you most likely also want to setup an ssh server and perform some initial configuration on it (such as choosing an alternate port, disabling root access, limiting ciphers, etc.) ### Setup a serial terminal Many cloud images expect a serial line to be available. Kernel messages and a loging prompt are often configured for `ttyS0`. If you're going to boot with `grub`, you can use the following configuration: \# /etc/default/grub (...) GRUB\_CMDLINE\_LINUX\_DEFAULT="console=tty1 console=ttyS0" (...) After changing this, you'll have to recreate your grub configuration (eg. `update-grub`). Alternatively you can configure your `inittab` appropriately if you have one, or run the equivalent of `systemctl enable getty@ttyS0.service`. ### Clean up the image After setting up the default user and `sudo`, you may want to remove the root password (and any others you don't want to include in the template) to not have some default root password in a template deployed in various locations. Step 3: Install and configure cloud-init ---------------------------------------- Once everything is prepared, the last step is to install and configure the cloud-init package. (`apt install cloud-init`, `yum install cloud-init` and so on.). ### Configure data sources Proxmox VE currently supports the nocloud-v1 and configdrive-v2 data sources. If you're only using the template with Proxmox VE you can use the following configuration snipppet as a boot-time optimization: \# /etc/cloud/cloud.cfg.d/99\_pve.cfg datasource\_list: \[ NoCloud, ConfigDrive \] ### Set the default user name The default user is usually found in `/etc/cloud/cloud.cfg`'s `system_info` section under `default_user`. You can change its `name` property. Distributions often use the distribution's name in lower case as the default user name there. Eg. on Ubuntu you'll find the following section: \# /etc/cloud/cloud.cfg (...) system\_info: default\_user: name: ubuntu (...) There are various additional options you can add here (such as what kind of line should be added to the `sudoers` file). For more detailed information see the upstream cloud-init documentation. Troubleshooting --------------- Once your template is ready, you'll want to test it. If you chose to cleanup the login data and the user setup doesn't work for some reason, you may have just created a system you cannot log into. You can use all the usual ways to try to debug this, but here are some useful reminders: * For a systemd based distribution you can use grub's 'edit' mode to add `systemd.debug-shell=1` to the kernel command line, giving you a root shell on Ctrl+Alt+F9 early on. * Attaching a live iso to the VM allows you to chroot into it and read the syslogs / journal of the previous boot attempts (`journalctl -b-1`). * Since cloud-init is often setup to disable root login, a temporary debug user with `sudo` access can be added before setting up cloud-init which you can remove or disable later on. See Also ======== * [Cloud-Init Support](https://pve.proxmox.com/wiki/Cloud-Init_Support "Cloud-Init Support") Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Cloud-Init\_FAQ&oldid=11321](https://pve.proxmox.com/mediawiki/index.php?title=Cloud-Init_FAQ&oldid=11321) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Pages using deprecated source tags](https://pve.proxmox.com/mediawiki/index.php?title=Category:Pages_using_deprecated_source_tags&action=edit&redlink=1 "Category:Pages using deprecated source tags (page does not exist)") * [Pages with syntax highlighting errors](https://pve.proxmox.com/mediawiki/index.php?title=Category:Pages_with_syntax_highlighting_errors&action=edit&redlink=1 "Category:Pages with syntax highlighting errors (page does not exist)") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Template:WinX-install-steps - Proxmox VE Template:WinX-install-steps =========================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Template:WinX-install-steps#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Template:WinX-install-steps#searchInput) Contents -------- * [1 Install](https://pve.proxmox.com/wiki/Template:WinX-install-steps#Install) * [1.1 Prepare](https://pve.proxmox.com/wiki/Template:WinX-install-steps#Prepare) * [1.2 Launch Windows install](https://pve.proxmox.com/wiki/Template:WinX-install-steps#Launch_Windows_install) * [2 Install Guest Agent and Services](https://pve.proxmox.com/wiki/Template:WinX-install-steps#Install_Guest_Agent_and_Services) * [2.1 Guest Agent](https://pve.proxmox.com/wiki/Template:WinX-install-steps#Guest_Agent) * [2.2 Drivers and Services](https://pve.proxmox.com/wiki/Template:WinX-install-steps#Drivers_and_Services) * [2.3 Check for missing drivers](https://pve.proxmox.com/wiki/Template:WinX-install-steps#Check_for_missing_drivers) * [2.4 Installing WSL(g)](https://pve.proxmox.com/wiki/Template:WinX-install-steps#Installing_WSL(g)) Install ------- ### Prepare To obtain a good level of performance, we will install the [Windows VirtIO Drivers](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers "Windows VirtIO Drivers") during the Windows installation. * Create a new VM, select "Microsoft Windows {{{osgroup}}}" as Guest OS and enable the "Qemu Agent" in the System tab. Continue and mount your Windows {{{osversion}}} ISO in the CDROM drive * For your virtual hard disk select "SCSI" as bus with "VirtIO SCSI single" as controller. Set "Write back" as cache option for best performance (the "No cache" default [is safer, but slower](https://pve.proxmox.com/wiki/Performance_Tweaks#Disk_Cache "Performance Tweaks") ) and tick "Discard" to optimally use disk space (TRIM). For the best performance, also make sure that IO Thread is enabled. * Configure your memory settings as needed, continue and set "VirtIO (paravirtualized)" as network device, finish your VM creation. * For the VirtIO drivers, upload the driver ISO (see [Windows VirtIO Drivers#virtio-win Releases](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#virtio-win_Releases "Windows VirtIO Drivers") for information on how to download it) to your storage, create a new CDROM drive (use "Add -> CD/DVD drive" in the hardware tab) **with Bus "IDE" and number 0**. Load the Virtio Drivers ISO in the new virtual CDROM drive. * Now your ready to start the VM, just follow the Windows installer. * Note for Older Version of Windows like Windows-2012 (use the stable older version of VirtIO ISO - virtio-win-0.1.189.iso, [download it from here](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.189-1/virtio-win-0.1.189.iso) ) ### Launch Windows install * After starting your VM launch the noVNC console * Follow the installer steps until you reach the installation type selection where you need to select "Custom (advanced)" * Now click "Load driver" to install the VirtIO drivers for hard disk and the network. * Hard disk: Browse to the CD drive where you mounted the VirtIO driver and select folder "vioscsi\\{{{driverdir}}}\\amd64" and confirm. Select the "Red Hat VirtIO SCSI pass-through controller" and click next to install it. Now you should see your drive. * Network: Repeat the steps from above (click again "Load driver", etc.) and select the folder "NetKVM\\{{{driverdir}}}\\amd64", confirm it and select "Redhat VirtIO Ethernet Adapter" and click next. * Memory Ballooning: Again, repeat the steps but this time select the "Balloon\\{{{driverdir}}}\\amd64" folder, then the "VirtIO Balloon Driver" and install it by clicking next. With these three drivers you should be good covered to run a fast virtualized Windows {{{osversion}}} system. * Choose the drive and continue the Windows installer steps. **HINT:** There is a [video showing the process](https://www.proxmox.com/en/services/training-courses/videos/proxmox-virtual-environment/install-windows-2016-server-on-proxmox-ve) for a Windows Server 2016 installation which is the same as for Windows {{{osversion}}}. Install Guest Agent and Services -------------------------------- ### Guest Agent If you enabled the Qemu Agent option for the VM the mouse pointer will probably be off after the first boot. To remedy this install the "Qemu Guest Agent". The installer is located on the driver CD under guest-agent\\qemu-ga-x86\_64.msi. ### Drivers and Services [![](https://pve.proxmox.com/mediawiki/images/thumb/f/fd/Win10_virtio_guest_tool_installer.png/400px-Win10_virtio_guest_tool_installer.png)](https://pve.proxmox.com/wiki/File:Win10_virtio_guest_tool_installer.png) VirtIO guest tools installer The easiest way to install missing drivers and services is to use the provided MSI installer. It is available on the driver CD since version 0.1.173-2. Run the "virtio-win-gt-x64.msi" file located directly on the CD. If you do not plan to use [SPICE](https://pve.proxmox.com/wiki/SPICE "SPICE") you can deselect the "Qxl" and "Spice" features. Restart the VM after the installer is done. After all this the RAM usage and IP configuration should be shown correctly in the summary page of the VM. For more information and configuration about ballooning, see [Dynamic Memory Management](https://pve.proxmox.com/wiki/Dynamic_Memory_Management "Dynamic Memory Management") ### Check for missing drivers _See also: [Paravirtualized Block Drivers for Windows](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows "Paravirtualized Block Drivers for Windows") _ [![](https://pve.proxmox.com/mediawiki/images/thumb/9/9c/Win10_unknown_dev.png/400px-Win10_unknown_dev.png)](https://pve.proxmox.com/wiki/File:Win10_unknown_dev.png) Unknown device in device manager [![](https://pve.proxmox.com/mediawiki/images/thumb/5/5e/Win10_update_driver_cd_selection.png/400px-Win10_update_driver_cd_selection.png)](https://pve.proxmox.com/wiki/File:Win10_update_driver_cd_selection.png) Make sure to include subfolders Go to the Device Manager to see if there are any drivers missing. For any unknown device: * Right click an select "Update driver". * Select "Browse my computer for driver software". * Select the Driver CD. Make sure that "Include subfolders" is checked. * Once a driver has been found you might be prompted with a security warning asking if you "Would like to install this device software". Click "Install". ### Installing WSL(g) To run WSL (Windows Subsystem for Linux) you need to enable [Nested Virtualization](https://pve.proxmox.com/wiki/Nested_Virtualization "Nested Virtualization") . Make sure to set your processor to 'host'; if you already set up your VM and did not select 'host' as processor, you can change it in the 'Hardware' section of your VM in the web interface. Follow the [official instructions](https://learn.microsoft.com/en-us/windows/wsl/install) . If you are using a GPU via PCI(e) passthrough, you might need to add args: -cpu host,kvm=off to your config file at _/etc/pve/qemu-server/.conf_, see [the vfio blog](http://vfio.blogspot.com/2014/08/vfiovga-faq.html) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Template:WinX-install-steps&oldid=12447](https://pve.proxmox.com/mediawiki/index.php?title=Template:WinX-install-steps&oldid=12447) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # PVE-zsync - Proxmox VE PVE-zsync ========= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/PVE-zsync#mw-head) [Jump to search](https://pve.proxmox.com/wiki/PVE-zsync#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/PVE-zsync#Introduction) * [2 Main features](https://pve.proxmox.com/wiki/PVE-zsync#Main_features) * [3 Limitations](https://pve.proxmox.com/wiki/PVE-zsync#Limitations) * [4 System requirements](https://pve.proxmox.com/wiki/PVE-zsync#System_requirements) * [5 PVE Storage Replication and PVE-zsync](https://pve.proxmox.com/wiki/PVE-zsync#PVE_Storage_Replication_and_PVE-zsync) * [5.1 Migrate form pve-zsync to Storage Replication](https://pve.proxmox.com/wiki/PVE-zsync#Migrate_form_pve-zsync_to_Storage_Replication) * [6 Configuration and use](https://pve.proxmox.com/wiki/PVE-zsync#Configuration_and_use) * [6.1 Sync a VM or ZFS dataset one time](https://pve.proxmox.com/wiki/PVE-zsync#Sync_a_VM_or_ZFS_dataset_one_time) * [6.2 Create a recurring sync job](https://pve.proxmox.com/wiki/PVE-zsync#Create_a_recurring_sync_job) * [6.3 Delete a recurring sync job](https://pve.proxmox.com/wiki/PVE-zsync#Delete_a_recurring_sync_job) * [6.4 Pause a sync job](https://pve.proxmox.com/wiki/PVE-zsync#Pause_a_sync_job) * [6.5 Reactivate a sync job](https://pve.proxmox.com/wiki/PVE-zsync#Reactivate_a_sync_job) * [6.6 Changing parameters](https://pve.proxmox.com/wiki/PVE-zsync#Changing_parameters) * [6.7 Information about the jobs](https://pve.proxmox.com/wiki/PVE-zsync#Information_about_the_jobs) * [6.8 Recovering an VM](https://pve.proxmox.com/wiki/PVE-zsync#Recovering_an_VM) * [7 Troubelshooting](https://pve.proxmox.com/wiki/PVE-zsync#Troubelshooting) * [7.1 Job status is on error and data-set can't be erased on destination system](https://pve.proxmox.com/wiki/PVE-zsync#Job_status_is_on_error_and_data-set_can't_be_erased_on_destination_system) * [8 Video Tutorials](https://pve.proxmox.com/wiki/PVE-zsync#Video_Tutorials) * [9 tips](https://pve.proxmox.com/wiki/PVE-zsync#tips) Introduction ------------ With the Proxmox VE ZFS replication manager (pve-zsync) you can synchronize your virtual machine (virtual disks and VM configuration) or directory stored on ZFS between two servers. By synchronizing, you have a full copy of your virtual machine on the second host and you can start your virtual machines on the second server (in case of data loss on the first server). By default, the tool syncs every 15 minutes, but the synchronization interval is fully configurable via the integrated cron job setup. The configuration of pve-zsync can be done either on the source server or on the target server. This is useful for advanced backup strategies. **Note:** pve-zsync was introduced in Proxmox VE 3.4 as technology preview. The package can also be installed on plain Debian Wheezy, Jessie or Stretch servers, as long as ZFS is configured. **Note:** Our ZFS is configured to auto-mount all subvols, so keep this in mind if you use pve-zsync. Also, zvol will be scanned by lvm. Main features ------------- * Speed limiter * Syncing interval can be set by cron * Syncing VM (disks and config) but also ZFS Datasets * Can keep multiple backups * Can be used in both directions * Can send on local host * Traffic is encrypted Limitations ----------- * not possible to sync recursive * only ssh for transfer * email notification is done by cron * Name resolution not taken into account, you have to use IP Addresses, even using hosts file hostnames will not work System requirements ------------------- * Both, target and source server must support ZFS (best practice: use Proxmox VE hosts). * SSH must be installed and configured * to receive email-notifications, a working mail server is required (e.g. postfix). * cstream * perl * scp * JASON.pm (libjson-perl this is the Debian package name, e.g. needed on Wheezy) PVE Storage Replication and PVE-zsync ------------------------------------- PVE Storage Replication and PVE-zsync work completely independent and do not harm each other, as long the following requirements are followed: * The destination pool / subset are different. * You do not migrate a guest to an other node. Sum up of the differences: | Characteristic | PVE Storage Replication | PVE-zsync | | --- | --- | --- | | Replication | Cluster Wide | to every Node which meets the requirements | | Operation mode | push | push or pull | | Management | GUI and Command line | Command line only | | Keep snapshot | no | yes | | Migration | yes | no | | Main Goal | redundancy | offsite backup | ### Migrate form pve-zsync to Storage Replication When you have a cluster and would like to switch to Storage Replication, you have to destroy the pve-zsync job, clean up the storage and create a new Storage Replication job. pve-zsync destroy \[--jobname \] Then you have to cleanup the zfs storage. Start at the source side and remove all snapshots which start with '@rep\_' zfs destroy /\[/\]vm---@ Then destroy all guest datasets on the destination side. zfs destroy -R vm--\*- Now you can create a new Storage Replication job More information about see [Storage Replication](https://pve.proxmox.com/wiki/Storage_Replication "Storage Replication") Configuration and use --------------------- Install the package with apt, on your Proxmox VE host: apt-get install pve-zsync This tool need basically no configuration. On the the first usage, when you create a job with a unknown host, the tool will ask you about the password for the remote server. ### Sync a VM or ZFS dataset one time (N.B. this is also possible if a recurring job for that VM already exists, here you must have in mind that the naming in --name must be the same). root@zfs1:~# pve-zsync sync --source 100 --dest 192.168.1.2:tank/backup --verbose --maxsnap 2 --name test1 --limit 512 This command sync VM 100 witch is located on the server where the tool is called and sent it to the server 192.168.1.2 on the zpool tank which has an subset backup. The --maxsnap tells that it should be kept 2 backups, if there are more then 2 backups, the 3 one will be erased (sorted by creation time). Name is only needed if there is already a sync job. The --limit param sets the speed limit what is used for syncing, here it would be 512 KBytes/s. ### Create a recurring sync job root@zfs2:~# pve-zsync create --source 192.168.1.1:100 --dest tank/backup --verbose --maxsnap 2 --name test1 --limit 512 --skip The --skip parameter disables the initial sync, that normally would be done immediately but can take a while, depending on the size of the backup. The initial sync will be done at the first sync time. ### Delete a recurring sync job if you delete a job, the former backup data will not be erased only the config will be erased. root@zfs2:~# pve-zsync destroy --source 192.168.1.1:100 --name test1 Name is not necessary if it is default. ### Pause a sync job If you want to pause a job, say maintenance the source server! root@zfs2:~# pve-zsync disable --source 192.168.1.1:100 --name test1 ### Reactivate a sync job to reactivate a job, because the job was paused or the job failed use. root@zfs2:~# pve-zsync enable --source 192.168.1.1:100 --name test1 This will reset the error flag in case of failure. ### Changing parameters You can edit the configuration in /etc/cron.d/pve-zsync or destroy the job and create it new. ### Information about the jobs To get a overview about all jobs use: root@zfs94:~# pve-zsync list SOURCE NAME STATE LAST SYNC TYPE 192.168.15.95:100 testing1 ok 2015-05-13\_14:44:00 ssh 192.168.15.95:data/test1 testing1 syncing2015-05-13\_14:44:11 ssh root@zfs94:~# pve-zsync status SOURCE NAME STATUS 192.168.15.95:100 testing1 ok 192.168.15.95:data/test1 testing1 syncing ### Recovering an VM You must recover the VM or dataset manually. (In one of the upcoming releases, the restore for Proxmox VE VM will be integrated). First, stop the sync job for the VM or dataset in question. **NOTE:** if not you can be interfere the sync job or your snapshot will removed before you are able to send it. root@zfs2:~# pve-zsync disable --source 192.168.15.1:100 --name test root@zfs2:~# pve-zsync list SOURCE NAME STATE LAST SYNC TYPE 192.168.15.1:100 test stopped2015-06-12\_11:03:01 ssh Then you can send the VM or Dataset to the selected target. SSH is only needed if you send to a remote sever. zfs send /\[/\]vm--disk-@ | \[ssh root@\] zfs receive //vm--disk- If you have a VM you must also copy the config and you need to correct the virtual disk storage configuration accordingly. cp /var/lib/pve-zsync/.conf.rep\_\_ /etc/pve/qemu-server/.conf **NOTE:** On PVE 4.2+ the path is: /var/lib/pve-zsync/data/.conf.rep\_\_ Example restore VM 100 with 2 disk from 192.168.15.2 (pve2) to 192.168.15.1 (pve1) and change VMID from 100 to 200: root@zfs2:~# zfs send rpool/backup/vm-100-disk-1@rep\_test100\_2015-06-12\_11:03:01 | ssh root@192.168.15.1 zfs receive vm/vm-200-disk-1 root@zfs2:~# ssh root@192.168.15.1 root@zfs1:~# cp /var/lib/pve-zsync/100.conf.rep\_test100\_2015-06-11\_14:11:01 /etc/pve/qemu-server/200.conf root@zfs1:~# nano /etc/pve/qemu-server/200.conf Now you have to change the storage path: bootdisk: virtio0 cores: 1 memory: 512 name: Debian8min net0: virtio=12:5E:F6:59:A9:BB,bridge=vmbr0 numa: 0 ostype: l26 smbios1: uuid=11fa2fba-5670-4610-aabb-534ad7edeffe sockets: 1 virtio0: zfs:vm-100-disk-1,size=10G virtio1: zfs:vm-100-disk-2,size=10G to bootdisk: virtio0 cores: 1 memory: 512 name: Debian8min net0: virtio=12:5E:F6:59:A9:BB,bridge=vmbr0 numa: 0 ostype: l26 smbios1: uuid=11fa2fba-5670-4610-aabb-534ad7edeffe sockets: 1 virtio0: vm:vm-200-disk-1,size=10G virtio1: vm:vm-200-disk-2,size=10G Troubelshooting --------------- Don't forget the command only works with IP Addresses and not hostnames. ### Job status is on error and data-set can't be erased on destination system If you have problems with a sync-job and when you try to erase the destination zvol, you get the error "zfs data-set is busy", then lvm could be the problem. This can be occur if you sync zvols with a lvm on it. In this case please insert the following line in /etc/lvm/lvm.conf filter = \[ "r|/dev/zd\*|" \] and reboot the system. tbd. Video Tutorials --------------- * [Proxmox VE Youtube channel](http://www.youtube.com/user/ProxmoxVE) tips ---- * as of 2016-11 If you migrate a vm that is used by pve-zsync edit /etc/cron,d/pve-zsync and change the IP address for vm . run 'pve-zsync enable --source \_\_\_\_ --name \_\_\_\_ ' or else there will be a warning when the job runs. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=PVE-zsync&oldid=10943](https://pve.proxmox.com/mediawiki/index.php?title=PVE-zsync&oldid=10943) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Installation](https://pve.proxmox.com/wiki/Category:Installation "Category:Installation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # User talk:Alejandra - Proxmox VE User talk:Alejandra =================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/User_talk:Alejandra#mw-head) [Jump to search](https://pve.proxmox.com/wiki/User_talk:Alejandra#searchInput) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=User\_talk:Alejandra&oldid=2672](https://pve.proxmox.com/mediawiki/index.php?title=User_talk:Alejandra&oldid=2672) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # User:Alen - Proxmox VE User:Alen ========= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/User:Alen#mw-head) [Jump to search](https://pve.proxmox.com/wiki/User:Alen#searchInput) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=User:Alen&oldid=7140](https://pve.proxmox.com/mediawiki/index.php?title=User:Alen&oldid=7140) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # LVM2 - Proxmox VE LVM2 ==== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/LVM2#mw-head) [Jump to search](https://pve.proxmox.com/wiki/LVM2#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/LVM2#Introduction) * [1.1 Configuration](https://pve.proxmox.com/wiki/LVM2#Configuration) * [1.2 Configuration Example (/etc/pve/storage.cfg)](https://pve.proxmox.com/wiki/LVM2#Configuration_Example_(/etc/pve/storage.cfg)) * [1.3 General LVM advantages](https://pve.proxmox.com/wiki/LVM2#General_LVM_advantages) * [2 Standard installation](https://pve.proxmox.com/wiki/LVM2#Standard_installation) * [3 LVM-Thin](https://pve.proxmox.com/wiki/LVM2#LVM-Thin) * [3.1 Configuration](https://pve.proxmox.com/wiki/LVM2#Configuration_2) * [3.2 Configuration Example (/etc/pve/storage.cfg)](https://pve.proxmox.com/wiki/LVM2#Configuration_Example_(/etc/pve/storage.cfg)_2) * [3.3 General LVM-Thin advantages](https://pve.proxmox.com/wiki/LVM2#General_LVM-Thin_advantages) * [3.4 Create a extra LV for /var/lib/vz](https://pve.proxmox.com/wiki/LVM2#Create_a_extra_LV_for_/var/lib/vz) * [3.5 Resize metadata pool](https://pve.proxmox.com/wiki/LVM2#Resize_metadata_pool) * [4 LVM vs LVM-Thin](https://pve.proxmox.com/wiki/LVM2#LVM_vs_LVM-Thin) * [5 Administration](https://pve.proxmox.com/wiki/LVM2#Administration) * [5.1 Create a Volume Group](https://pve.proxmox.com/wiki/LVM2#Create_a_Volume_Group) * [6 Troubleshooting and known issues](https://pve.proxmox.com/wiki/LVM2#Troubleshooting_and_known_issues) * [6.1 Thin Overprovisioning](https://pve.proxmox.com/wiki/LVM2#Thin_Overprovisioning) Introduction ------------ storage pool type: lvm LVM is a thin software layer on top of hard disks and partitions. It can be used to split available disk space into smaller logical volumes. LVM is widely used on Linux and makes managing hard drives easier. Another use case is to put LVM on top of a big iSCSI LUN. That way you can easily manage space on that iSCSI LUN, which would not be possible otherwise, because the iSCSI specification does not define a management interface for space allocation ### Configuration The LVM backend supports the common storage properties content, nodes, disable, and the following LVM specific properties: * vgname * LVM volume group name. This must point to an existing volume group. * base * Base volume. This volume is automatically activated before accessing the storage. This is mostly useful when the LVM volume group resides on a remote iSCSI server. * saferemove * Zero-out data when removing LVs. When removing a volume, this makes sure that all data gets erased. * saferemove\_throughput * Wipe throughput (cstream -t parameter value). ### Configuration Example (/etc/pve/storage.cfg) lvm: myspace vgname myspace content rootdir,images ### General LVM advantages LVM is a typical block storage, but this backend does not support snapshot and clones. Unfortunately, normal LVM snapshots are quite inefficient, because they interfere all writes on the whole volume group during snapshot time. One big advantage is that you can use it on top of a shared storage, for example an iSCSI LUN. The backend itself implement proper cluster wide locking. ℹ️ **Note**: The newer LVM-thin backend allows snapshot and clones, but does not support shared storage. Standard installation --------------------- On a default installation Proxmox VE will use lvm. The layout looks like followed. | VG | LV | Mountpoint | Note | | --- | --- | --- | --- | | pve | swap | | will used as swap partition | | pve | root | / | Example | | pve | data | /var/lib/vz/ | Proxmox VE < 4.2 | | pve | data | | Proxmox VE >= 4.2 | In Proxmox VE 4.2 we changed the LV data to a thin pool, to provide snapshots and native performance of the disk. The /var/lib/vz is now included in the LV root. LVM-Thin -------- storage pool type: lvmthin LVM normally allocates blocks when you create a volume. LVM thin pools instead allocates blocks when they are written. This behavior is called thin-provisioning, because volumes can be much larger than physically available space. You can use the normal LVM command line tools to manage and create LVM thin pools (see man lvmthin for details). Assuming you already have a LVM volume group called pve, the following commands create a new LVM thin pool (size 100G) called data: lvcreate -L 100G -n data pve lvconvert --type thin-pool pve/data Caution: Under certain circumstances, LVM does not correctly calculate the metadatapool/chunk size. Please check if the metadatapool is big enough. The formula which has to be satisfied is: PoolSize/ChunkSize \* 64b = MetadataPoolSize you can get this information via lvs -a -o name,size,chunk\_size ### Configuration The LVM thin backend supports the common storage properties content, nodes, disable, and the following LVM specific properties: * vgname * LVM volume group name. This must point to an existing volume group. * thinpool * The name of the LVM thin pool. ### Configuration Example (/etc/pve/storage.cfg) lvmthin: local-lvm thinpool data vgname pve content rootdir,images ### General LVM-Thin advantages LVM thin is a block storage, but fully supports snapshots and clones efficiently. New volumes are automatically initialized with zero. It must be mentioned that LVM thin pools cannot be shared across multiple nodes, so you can only use them as local storage. ### Create a extra LV for /var/lib/vz This can be easily done by create a new thin LV. It is thin provisioned. lvcreate -n -V / A real world example it looks like lvcreate -n vz -V 10G pve/data Now a filesystem must be create on the LV. mkfs.ext4 /dev/pve/vz And at last step this have to be mounted. ℹ️ **Note**: Be sure that /var/lib/vz is empty. On a default installation it isn’t. To make it always accessible add the following line at /etc/fstab and then **mount -a** to reload the mount point echo '/dev/pve/vz /var/lib/vz ext4 defaults 0 2' >> /etc/fstab ### Resize metadata pool ℹ️ **Note**: If the pool will extend, then it is be necessary to extent also the metadata pool. It can be achieved with the following command. lvresize --poolmetadatasize + / LVM vs LVM-Thin --------------- | Type | Content types | Image formats | Shared | Snapshots | Clones | | --- | --- | --- | --- | --- | --- | | LVM | images,rootdir | raw | possible | no | no | | LVM-Thin | images,rootdir | raw | no | yes | yes | Administration -------------- #### Create a Volume Group Let's assume we have a empty disk /dev/sdb, where we want to make a Volume Group named vmdata. First create a partition. sgdisk -N 1 /dev/sdb pvcreate --metadatasize 250k -y -ff /dev/sdb1 vgcreate vmdata /dev/sdb1 Troubleshooting and known issues -------------------------------- ### Thin Overprovisioning In a LVM\_thin pool there is no space limit when defining LVM volumes in it - regardless if these volumes are virtual disks for containers or virtual machines or just volumes for any other purpose defined by "lvcreate". If the total amount of all defined logical volume size within a thin pool exceeds the physical size of the pool it is called "overprovisioning". Attention! You can never use more space for data than physically is available! Unfortunately in case of reaching the space limit no direct warning or error message occurs. At the user interface - e.g. inside a virtual machine - it looks like all logical space can be used; but when exceeding the physical limit the data are corrupt! Therefore it is recommended \- to avoid overprovisioning; or at least, if not possible \- to check regularly via lvs the actual physical usage. See also "Automatically extend thin pool LV" in man lvmthin Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=LVM2&oldid=10016](https://pve.proxmox.com/mediawiki/index.php?title=LVM2&oldid=10016) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Serial Terminal - Proxmox VE Serial Terminal =============== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Serial_Terminal#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Serial_Terminal#searchInput) Contents -------- * [1 Why would I need a serial terminal / serial console?](https://pve.proxmox.com/wiki/Serial_Terminal#Why_would_I_need_a_serial_terminal_/_serial_console?) * [2 Some background so you get the idea](https://pve.proxmox.com/wiki/Serial_Terminal#Some_background_so_you_get_the_idea) * [2.1 How do this apply to Proxmox PVE ?](https://pve.proxmox.com/wiki/Serial_Terminal#How_do_this_apply_to_Proxmox_PVE_?) * [3 Configuration on the host](https://pve.proxmox.com/wiki/Serial_Terminal#Configuration_on_the_host) * [3.1 Add a virtual serial port to the VM](https://pve.proxmox.com/wiki/Serial_Terminal#Add_a_virtual_serial_port_to_the_VM) * [4 Configuration on the guest](https://pve.proxmox.com/wiki/Serial_Terminal#Configuration_on_the_guest) * [4.1 Configure the terminal if not present](https://pve.proxmox.com/wiki/Serial_Terminal#Configure_the_terminal_if_not_present) * [4.1.1 Reboot the VM, verify that the emulated serial port is there](https://pve.proxmox.com/wiki/Serial_Terminal#Reboot_the_VM,_verify_that_the_emulated_serial_port_is_there) * [4.1.2 Instruct grub2 to send the boot messages on the VGA display and on the serial port](https://pve.proxmox.com/wiki/Serial_Terminal#Instruct_grub2_to_send_the_boot_messages_on_the_VGA_display_and_on_the_serial_port) * [5 Connecting to the Serial Terminal](https://pve.proxmox.com/wiki/Serial_Terminal#Connecting_to_the_Serial_Terminal) * [6 Trouble shooting](https://pve.proxmox.com/wiki/Serial_Terminal#Trouble_shooting) * [7 References](https://pve.proxmox.com/wiki/Serial_Terminal#References) * [8 Going Further](https://pve.proxmox.com/wiki/Serial_Terminal#Going_Further) Why would I need a serial terminal / serial console? ---------------------------------------------------- Note: This apply to qemu/kvm virtualization. If you do a lot of work over ssh on your pve server you would maybe appreciate to connect to your running VMs like: qm status 101 status: running qm terminal 101 starting serial terminal on interface serial0 (press control-O to exit) Debian GNU/Linux 8 debian8 ttyS0 debian8 login: Other use cases: * you lost network access to the guest and VNC is either too slow for you or does not have the features you need (i.e. easy copy/paste between other terminals) * your guest freezes or kernel panics, you want to debug it, but it is impossible to capture all messages on VNC screen * your keyboard layout is borked on the guest * you are familiar with `xm console ` from Xen and you want to use a similar feature here Some background so you get the idea ----------------------------------- When you start Unix/Linux on a PC, the default input device is the attached keyboard (PS/2 or USB), and the default output device is the available VGA /HDMI / Display port of the PC. This is called in Unix-speak the **default console**, or **system console**. During boot, the kernel sends its boot messages, like device detection, to this default console, and at the end of the boot processes, fires a "login: " prompt on this console. (Actually it spawns multiple login prompts, you can switch between them with Ctrl-alt-F1, Ctrl-alt-F2, etc ... ) Now it is perfectly fine to send the boot messages and start a login prompt on something else. For instance the Linux Kernel has a **netconsole** feature, to send the boot messages over the network to another Linux computer. It is also possible to send a copy of the boot messages, and start a login prompt on the **serial port** of the PC. We get then what is called a **serial console** If you connect to this serial port any computing device with a **terminal emulation** program, it will be possible to work on the Linux PC as if you were using the PC locally in text mode. The requirements of the terminal emulation are quite low, so you could use HyperTerminal on a Windows PC, Minicom on Linux or even an [old Atari ST](http://www.tldp.org/LDP/LG/issue70/arndt.html) with the appropriate program. ### How do this apply to Proxmox PVE ? In proxmox things work exactly the same, but with emulated devices. NoVNC/ VNC Applet connects to your VM keyboard and VM VGA display and displays the stuff you would expect from a real PC on a VGA display with a locally attached keyboard. Now we can also configure our VM to have an emulated serial port, and instruct the OS, to send a copy of the boot messages / start a login prompt on the emulated serial port. Once this is configured it will be possible to connect from the host (ie the server running pve) using a **terminal emulation** program, which is handily builtin in the Proxmox Qemu Manager. Configuration on the host ------------------------- ##### Add a virtual serial port to the VM Provided your VM IS is 101 \# open /etc/pve/qemu-server/101.conf and add the following parameter at the end of file serial0: socket or use qm set 101 -serial0 socket Configuration on the guest -------------------------- #### Configure the terminal if not present As detailed in [https://help.ubuntu.com/community/SerialConsoleHowto#Server\_Setup](https://help.ubuntu.com/community/SerialConsoleHowto#Server_Setup) , check if you have the file **/etc/init/ttyS0.conf**. If not, create it: **\# ttyS0 - getty** **#** **\# This service maintains a getty on ttyS0 from the point the system is** **\# started until it is shut down again.** **start on stopped rc RUNLEVEL=\[12345\]** **stop on runlevel \[!12345\]** **respawn** **exec /sbin/getty -L 115200 ttyS0 vt102** then ask upstart to start terminal **sudo start ttyS0** You might consider creating the ttyS1.conf file as well, just as a backup in case you have a crash with ttyS0 ##### Reboot the VM, verify that the emulated serial port is there dmesg | grep ttyS \[ 0.457814\] 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A If ttyS0 is not there, type **sudo start ttyS0** from the VM shell ##### Instruct grub2 to send the boot messages on the VGA display and on the serial port \# in /etc/default/grub change the GRUB\_CMDLINE\_LINUX parameter to GRUB\_CMDLINE\_LINUX="quiet console=tty0 console=ttyS0,115200" run \# debian based update-grub # redhat based grub2-mkconfig --output=/boot/grub2/grub.cfg and do a final reboot Connecting to the Serial Terminal --------------------------------- On the Host, just enter **qm terminal ** and enter **enter** a second time you should get a login prompt **Note:** if it seems this is not working, and if you have defined ttyS1, you can connect to itwith the command **qm terminal -iface serial1** Now if you reboot your system you should see that the kernel startup messages are send to both your serial terminal and NoVNC display. Additionally (quoting from a private email, edited for clarity): Qemu also supports binding the emulated serial port to a telnet server. Look for the -chardev parameter in the qemu-kvm manual page. (With proxmox you would then use the "args:" parameter in vm.conf to specify extra args.) This would allow you to telnet to your host on a specific port to get a serial console. As with every telnet traffic remember that nothing is encrypted, so I wouldn't do this in a production setup. Trouble shooting ---------------- You can check that the virtual serial port is present, and properly bound to the unix socket that **qm terminal** uses with: qm monitor info chardev which should contains a line starting with _serial0_ like: serial0: filename=disconnected:unix:/var/run/qemu-server/101.serial0,server Remember the `qm terminal` uses Ctrl-O as shortcut, so saving a file from `nano` with Ctrl-O will log you out instead References ---------- * Systemd documentation: [http://0pointer.de/blog/projects/serial-console.html](http://0pointer.de/blog/projects/serial-console.html) Going Further ------------- It is also possible to have the grub2 and grub accessible from the serial port. See [https://help.ubuntu.com/community/Grub2#Booting\_from\_a\_serial\_console](https://help.ubuntu.com/community/Grub2#Booting_from_a_serial_console) for how to do this with Grub2. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Serial\_Terminal&oldid=10187](https://pve.proxmox.com/mediawiki/index.php?title=Serial_Terminal&oldid=10187) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # User contributions for M.frank - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:User_contributions) User contributions for M.frank ============================== Results for [M.frank](https://pve.proxmox.com/mediawiki/index.php?title=User:M.frank&action=edit&redlink=1 "User:M.frank (page does not exist)") [talk](https://pve.proxmox.com/mediawiki/index.php?title=User_talk:M.frank&action=edit&redlink=1 "User talk:M.frank (page does not exist)") [block log](https://pve.proxmox.com/mediawiki/index.php?title=Special:Log/block&page=User%3AM.frank "Special:Log/block") [uploads](https://pve.proxmox.com/wiki/Special:ListFiles/M.frank "Special:ListFiles/M.frank") [logs](https://pve.proxmox.com/wiki/Special:Log/M.frank "Special:Log/M.frank") A user with 2 edits. Account created on 3 March 2022. [Jump to navigation](https://pve.proxmox.com/wiki/Special:Contributions/M.frank#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:Contributions/M.frank#searchInput) Search for contributionsExpandCollapse ⧼contribs-top⧽ IP address or username: Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection Associated namespace [Tag](https://pve.proxmox.com/wiki/Special:Tags "Special:Tags") filter: Manual revertNew redirectRemoved redirectReplacedRevertedRollbackUndoVisual edit: Switchedwikieditor (hidden tag) Invert selection Only show edits that are latest revisions Only show edits that are page creations Hide minor edits ⧼contribs-date⧽ From date: To date: Search #### 23 March 2026 * 11:24[11:24, 23 March 2026](https://pve.proxmox.com/mediawiki/index.php?title=Stretch_Cluster&oldid=12530 "Stretch Cluster") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Stretch_Cluster&diff=prev&oldid=12530 "Stretch Cluster") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Stretch_Cluster&action=history "Stretch Cluster") +1 [Stretch Cluster](https://pve.proxmox.com/wiki/Stretch_Cluster "Stretch Cluster") [→Tie-Breaker Node](https://pve.proxmox.com/wiki/Stretch_Cluster#Tie-Breaker_Node "Stretch Cluster") : fix formatting for warning message current #### 3 March 2022 * 14:02[14:02, 3 March 2022](https://pve.proxmox.com/mediawiki/index.php?title=Nested_Virtualization&oldid=11311 "Nested Virtualization") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Nested_Virtualization&diff=prev&oldid=11311 "Nested Virtualization") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Nested_Virtualization&action=history "Nested Virtualization") +309 [Nested Virtualization](https://pve.proxmox.com/wiki/Nested_Virtualization "Nested Virtualization") No edit summary Retrieved from "[https://pve.proxmox.com/wiki/Special:Contributions/M.frank](https://pve.proxmox.com/wiki/Special:Contributions/M.frank) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # User contributions for Aasami - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:User_contributions) User contributions for Aasami ============================= Results for [Aasami](https://pve.proxmox.com/wiki/User:Aasami "User:Aasami") [talk](https://pve.proxmox.com/wiki/User_talk:Aasami "User talk:Aasami") [block log](https://pve.proxmox.com/mediawiki/index.php?title=Special:Log/block&page=User%3AAasami "Special:Log/block") [uploads](https://pve.proxmox.com/wiki/Special:ListFiles/Aasami "Special:ListFiles/Aasami") [logs](https://pve.proxmox.com/wiki/Special:Log/Aasami "Special:Log/Aasami") A user with 3 edits. Account created on 27 January 2013. [Jump to navigation](https://pve.proxmox.com/wiki/Special:Contributions/Aasami#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:Contributions/Aasami#searchInput) Search for contributionsExpandCollapse ⧼contribs-top⧽ IP address or username: Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection Associated namespace [Tag](https://pve.proxmox.com/wiki/Special:Tags "Special:Tags") filter: Manual revertNew redirectRemoved redirectReplacedRevertedRollbackUndoVisual edit: Switchedwikieditor (hidden tag) Invert selection Only show edits that are latest revisions Only show edits that are page creations Hide minor edits ⧼contribs-date⧽ From date: To date: Search #### 23 March 2016 * 07:20[07:20, 23 March 2016](https://pve.proxmox.com/mediawiki/index.php?title=DRBD&oldid=8314 "DRBD") [diff](https://pve.proxmox.com/mediawiki/index.php?title=DRBD&diff=prev&oldid=8314 "DRBD") [hist](https://pve.proxmox.com/mediawiki/index.php?title=DRBD&action=history "DRBD") +38 m [DRBD](https://pve.proxmox.com/wiki/DRBD "DRBD") [→Introduction](https://pve.proxmox.com/wiki/DRBD#Introduction "DRBD") : added meaning of DRBD * 06:52[06:52, 23 March 2016](https://pve.proxmox.com/mediawiki/index.php?title=DRBD&oldid=8313 "DRBD") [diff](https://pve.proxmox.com/mediawiki/index.php?title=DRBD&diff=prev&oldid=8313 "DRBD") [hist](https://pve.proxmox.com/mediawiki/index.php?title=DRBD&action=history "DRBD") +94 m [DRBD](https://pve.proxmox.com/wiki/DRBD "DRBD") [→System requirements](https://pve.proxmox.com/wiki/DRBD#System_requirements "DRBD") : Crossower is not needed in most cases. Retrieved from "[https://pve.proxmox.com/wiki/Special:Contributions/Aasami](https://pve.proxmox.com/wiki/Special:Contributions/Aasami) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # X11 LXDE in OpenVZ - Proxmox VE X11 LXDE in OpenVZ ================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/X11_LXDE_in_OpenVZ#mw-head) [Jump to search](https://pve.proxmox.com/wiki/X11_LXDE_in_OpenVZ#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/X11_LXDE_in_OpenVZ#Introduction) * [2 Installing the x2go server in a Debian Squeeze VM](https://pve.proxmox.com/wiki/X11_LXDE_in_OpenVZ#Installing_the_x2go_server_in_a_Debian_Squeeze_VM) * [2.1 Installing Firefox](https://pve.proxmox.com/wiki/X11_LXDE_in_OpenVZ#Installing_Firefox) * [2.2 Startup Apps](https://pve.proxmox.com/wiki/X11_LXDE_in_OpenVZ#Startup_Apps) * [2.3 Other Applications in LXDE](https://pve.proxmox.com/wiki/X11_LXDE_in_OpenVZ#Other_Applications_in_LXDE) * [2.3.1 squeeze-backports repo](https://pve.proxmox.com/wiki/X11_LXDE_in_OpenVZ#squeeze-backports_repo) * [2.3.2 Install LibreOffice](https://pve.proxmox.com/wiki/X11_LXDE_in_OpenVZ#Install_LibreOffice) * [2.3.3 Graphics Apps](https://pve.proxmox.com/wiki/X11_LXDE_in_OpenVZ#Graphics_Apps) * [2.3.4 Install Wine (32 bit only)](https://pve.proxmox.com/wiki/X11_LXDE_in_OpenVZ#Install_Wine_(32_bit_only)) * [2.3.5 Add Sys Admin Tools](https://pve.proxmox.com/wiki/X11_LXDE_in_OpenVZ#Add_Sys_Admin_Tools) * [3 Installing the x2go Client](https://pve.proxmox.com/wiki/X11_LXDE_in_OpenVZ#Installing_the_x2go_Client) * [4 Using the x2go client](https://pve.proxmox.com/wiki/X11_LXDE_in_OpenVZ#Using_the_x2go_client) * [5 lxpanel issues](https://pve.proxmox.com/wiki/X11_LXDE_in_OpenVZ#lxpanel_issues) * [5.1 Portable Client](https://pve.proxmox.com/wiki/X11_LXDE_in_OpenVZ#Portable_Client) * [5.2 Client Screenshots](https://pve.proxmox.com/wiki/X11_LXDE_in_OpenVZ#Client_Screenshots) * [6 References](https://pve.proxmox.com/wiki/X11_LXDE_in_OpenVZ#References) Introduction ------------ [x2go](http://www.x2go.org/) is available as a server for linux distributions and as a client for Windows, MacOS, Linux - Debian / Fedora and their derivatives. The x2go client in a remote instance can connect to a headless VM in an OpenVZ container running the x2go server and the specific GUI bindings (Gnome, KDE, LXDE, etc). Though this article is specific to [debian squeeze x2go server install](http://wiki.x2go.org/doku.php/doc:installation:x2goserver) , it can be a general guide with small modifications to suit any distro. Installing the x2go server in a Debian Squeeze VM ------------------------------------------------- * Create an OpenVZ container based on any debian squeeze template ([standard](https://pve.proxmox.com/mediawiki/index.php?title=Debian_6.0_Standard&action=edit&redlink=1 "Debian 6.0 Standard (page does not exist)") preferred). * SSH into it as root * Make sure the squeeze-lts repo is available (otherwise add it): grep squeeze-lts /etc/apt/sources.list **Output:** deb [http://ftp.debian.org/debian](http://ftp.debian.org/debian) squeeze-lts main contrib * Now execute the following (stopping and starting the container as directed in the comments): apt-get update && apt-get dist-upgrade apt-get clean all \# export DEBIAN\_FRONTEND=noninteractive apt-get install lxde \# During above installation, Keyboard Country and Charset will be interactively asked ( cat < /etc/apt/sources.list.d/x2go.list apt-key adv \--recv-keys \--keyserver keys.gnupg.net E1F958385BFE2B6E apt-get update apt-get install x2go-keyring && apt-get update apt-get install x2goserver x2goserver-xsession \# The following will have to be removed and installed again if the primary lxpanel gets removed in the GUI apt-get install x2golxdebindings ### Installing Firefox apt-get remove iceweasel ( cat < /etc/apt/sources.list.d/firefox.list apt-key adv \--recv-keys \--keyserver keyserver.ubuntu.com C1289A29 apt-get update apt-get install firefox-mozilla-build shutdown \-r now ### Startup Apps All the applications are in: **/usr/share/applications** cat < /etc/xdg/autostart/lxterminal.desktop \[Desktop Entry\] Type=Application Exec=lxterminal OnlyShowIn=LXDE; EOF cat <> /etc/xdg/lxsession/LXDE/autostart @/etc/xdg/autostart/lxterminal.desktop EOF ### Other Applications in LXDE To install and run applications such as LibreOffice (forked from OpenOffice.org and standard from Debian Wheezy onwards), we need to increase the RAM and Swap to atleast 1GB. Incase the RAM was not increased and the apt-get install \[package\] froze, it can be recovered on reboot after increasing the RAM by executing: dpkg --configure -a LibreOffice is available in the squeeze-backports repo which can be installed using: #### squeeze-backports repo * Increase VM memory and swap allocation to atleast 1GB * Enable **squeeze-backports** and **squeeze-backports-sloppy** repos by appending the following to **/etc/apt/sources.list** deb http://backports.debian.org/debian-backports squeeze-backports main deb http://backports.debian.org/debian-backports squeeze-backports-sloppy main This can also be done with: cat <> /etc/apt/sources.list deb http://backports.debian.org/debian-backports squeeze-backports main deb http://backports.debian.org/debian-backports squeeze-backports-sloppy main EOF apt-get update #### Install LibreOffice * LibreOffice can be installed with: apt-get install -t squeeze-backports libreoffice * openjdk 6 also gets installed * Depending on the used desktop environment, you might also have to install the libreoffice-gtk, libreoffice-gnome or libreoffice-kde packages. For LXDE, the necessary packages have already been installed now. #### Graphics Apps apt-get install gimp inkscape #### Install Wine (32 bit only) apt-get install wine ttf-mscorefonts-installer #### Add Sys Admin Tools apt-get install gnome-system-tools This package is necessary to manage Users and Groups in Debian and is quite big in size - 500 MB. Installing the x2go Client -------------------------- * In Windows XP/7/8/8.1, download and install the [x2go client](http://code.x2go.org/releases/binary-win32/x2goclient/releases/4.0.2.1+hotfix1+build6/x2goclient-4.0.2.1+hotfix1+build6-setup.exe) . * Linux and Mac clients too are [available](http://wiki.x2go.org/doku.php/doc:installation:x2goclient) . Using the x2go client --------------------- * Choose the appropriate graphic resolution and color depth to suit your monitor and bandwidth respectively. * Connect to the x2go server accepting to open what firewall requests emanate. * While inside the LXDE GUI: * Set Firefox Preferences * Set Default Browser to Firefox * Set Panel icons as desired by right-clicking the Menu icon lxpanel issues -------------- * If the lxpanel gets lost, try to logout and connect again. * If the lxpanel is still unavailable the restart it with: lxpanelctl restart * Still drastic measures can be: killall lxpanel && lxpanel -p LXDE & ### Portable Client **x2goclient on Windows** has a portable mode (and has had one for a very long time, if not even from the beginning). No need to apply any external tweaks or tools. See x2goclient.exe --help for details. ### Client Screenshots * [X11 after all installs above](https://pve.proxmox.com/mediawiki/images/4/47/X11onVZ.png "X11onVZ.png") * [X11 with Apps running](https://pve.proxmox.com/mediawiki/images/c/c6/X11onVZapps.png "X11onVZapps.png") References ---------- * [NX inside VE](https://openvz.org/NX_inside_VE) * [Portable Mode for Windows Clients](http://x2go-community.org/node/439) * [LXDE Tips](http://www.fdsd.co.uk/wiki/Tech/LxdeTips.html) * [LibreOffice on Debian](https://wiki.debian.org/LibreOffice) * [LibreOffice replaces OpenOffice.org in Debian Wheezy onwards](https://www.debian.org/News/2011/20110623) * [OpenJDK 6 JRE in Debian Packages](https://packages.debian.org/search?keywords=openjdk-6-jre) * [Wine in LXDE - Linux Guide](http://lxlinux.com/) * [LXPanel](http://wiki.lxde.org/en/LXPanel) * [Adding Menu Shortcuts in LXDE](http://lkubaski.wordpress.com/2012/06/29/adding-lxde-start-menu-and-desktop-shortcuts/) * [Ubuntu LXDE Install Guide](http://linuxftw.weebly.com/lubuntu-1110-installation-guide.html) * [LibreOffice and LXPanel Compatibility Solved](http://en.libreofficeforum.org/node/834) * [LXDE from Scratch](http://l3net.wordpress.com/2013/04/30/lightweight-debian-lxde-desktop-from-scratch/) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=X11\_LXDE\_in\_OpenVZ&oldid=10461](https://pve.proxmox.com/mediawiki/index.php?title=X11_LXDE_in_OpenVZ&oldid=10461) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Pages using deprecated source tags](https://pve.proxmox.com/mediawiki/index.php?title=Category:Pages_using_deprecated_source_tags&action=edit&redlink=1 "Category:Pages using deprecated source tags (page does not exist)") * [Archive](https://pve.proxmox.com/wiki/Category:Archive "Category:Archive") * [Proxmox VE 3.x](https://pve.proxmox.com/wiki/Category:Proxmox_VE_3.x "Category:Proxmox VE 3.x") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Service daemons - Proxmox VE Service daemons =============== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Service_daemons#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Service_daemons#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Service_daemons#Introduction) * [2 Proxmox VE Services](https://pve.proxmox.com/wiki/Service_daemons#Proxmox_VE_Services) * [2.1 pve-cluster](https://pve.proxmox.com/wiki/Service_daemons#pve-cluster) * [2.2 pve-ha-crm](https://pve.proxmox.com/wiki/Service_daemons#pve-ha-crm) * [2.3 pve-ha-lrm](https://pve.proxmox.com/wiki/Service_daemons#pve-ha-lrm) * [2.4 pvedaemon](https://pve.proxmox.com/wiki/Service_daemons#pvedaemon) * [2.5 pveproxy](https://pve.proxmox.com/wiki/Service_daemons#pveproxy) * [2.6 pvestatd](https://pve.proxmox.com/wiki/Service_daemons#pvestatd) * [2.7 pve-manager](https://pve.proxmox.com/wiki/Service_daemons#pve-manager) * [2.8 pve-firewall](https://pve.proxmox.com/wiki/Service_daemons#pve-firewall) * [2.9 pvefw-logger](https://pve.proxmox.com/wiki/Service_daemons#pvefw-logger) * [3 Cluster Services](https://pve.proxmox.com/wiki/Service_daemons#Cluster_Services) * [3.1 cman (corosync 1.x)](https://pve.proxmox.com/wiki/Service_daemons#cman_(corosync_1.x)) * [3.2 corosync 2.x](https://pve.proxmox.com/wiki/Service_daemons#corosync_2.x) * [3.3 fenced](https://pve.proxmox.com/wiki/Service_daemons#fenced) * [3.4 rgmanager](https://pve.proxmox.com/wiki/Service_daemons#rgmanager) * [4 Standard Services](https://pve.proxmox.com/wiki/Service_daemons#Standard_Services) * [4.1 cron](https://pve.proxmox.com/wiki/Service_daemons#cron) * [4.2 ntp](https://pve.proxmox.com/wiki/Service_daemons#ntp) * [4.3 rsyslog](https://pve.proxmox.com/wiki/Service_daemons#rsyslog) * [4.4 postfix](https://pve.proxmox.com/wiki/Service_daemons#postfix) Introduction ------------ A Proxmox VE node runs a couple of services for proper operation. This article provides a short overview of those services, describing their basic functionality. Proxmox VE Services ------------------- ### pve-cluster This service is the heart of any Proxmox VE installation. It provides the [Proxmox\_Cluster\_file\_system\_(pmxcfs)](https://pve.proxmox.com/wiki/Proxmox_Cluster_file_system_(pmxcfs) "Proxmox Cluster file system (pmxcfs)") , a database-driven file system for storing configuration files, replicated in real time on all nodes using corosync. The service makes the data accessible on the normal file system level, mounted at /etc/pve (using fuse). All Proxmox VE related configuration is stored there. Note: You also need this service if you do not run a cluster. This service also provides a cluster wide locking implementation, and we use it to distribute statistic data to all cluster nodes. ### pve-ha-crm This is the Proxmox VE High Availability Cluster Resource Manager, it manages the cluster which means there is only one active if a ha-resource is set, and this is the cluster master. If the one master crm is failing a new one will elected. This procedure will take a while. ### pve-ha-lrm This is the Proxmox VE High Availability Local Resource Manager, every node has an active lrm if ha is enabled. They have to execute the commands from the crm and report the crm. ### pvedaemon pvedaemon is the REST API server. All API calls which require root privileges are done using this Server. The Server runs as 'root', but only listens to a local address 127.0.0.1 port 85 for security reasons. It usually serves request from pveproxy, which listens to public ports, and run as non-root user. ### pveproxy pveproxy is the REST API proxy server, listening on port 8006 - used in PVE 3.0+ onwards. This service run as user 'www-data', and forwards request to other nodes (or pvedaemon) if required. API calls which do not require root privileges are directly answered by this server. ### pvestatd pvestatd is the PVE Status Daemon. It queries the status of all resources (VMs, Containers and Storage), and send the result to all cluster members. You can easily query the resulting data with: \# cat /etc/pve/.rrd ### pve-manager This is just a startup script (not a daemon), used to start/stop all VMs and Containers. ### pve-firewall Proxmox VE Firewall manage the Firewall(iptables) which works cluster wide. ### pvefw-logger Proxmox VE Firewall logger logs the Firewall events. Cluster Services ---------------- Those services are only required if you run a cluster. ### cman (corosync 1.x) ℹ️ **Note**: Only on the old stable Proxmox VE 3.x releases cman is a symmetric general-purpose cluster manager. It provides a service manager that handles service groups, plus a connection manager that handles cluster membership management, messaging among cluster nodes, event notification, quorum and state transitions. ### corosync 2.x The Corosync Cluster Engine is a group communication system with additional features for implementing high availability within applications. configuration a in-memory database that provide the ability to set, retrieve, and receive change notifications of information. quorum system that notifies applications when quorum is achieved or lost. ### fenced ℹ️ **Note**: Only on the old stable Proxmox VE 3.x releases The fencing daemon, fenced, fences cluster nodes that have failed. Fencing a node generally means rebooting it or otherwise preventing it from writing to storage, e.g. disabling its port on a SAN switch. Fencing involves interacting with a hardware device, e.g. network power switch, SAN switch, storage array. Different "fencing agents" are run by fenced to interact with various hardware devices. ### rgmanager ℹ️ **Note**: Only on the old stable Proxmox VE 3.x releases rgmanager is the Resource Group (Cluster Service) Manager Daemon. rgmanager handles management of user-defined cluster services (also known as resource groups). This includes handling of user requests including service start, service disable, service relocate, and service restart. The service manager daemon also handles restarting and relocating services in the event of failures. Standard Services ----------------- Almost any Linux server runs this services. I just mention them here for completeness. ### cron cron daemon execute scheduled commands. * [Crontab Defs](http://team.macnn.com/drafts/crontab_defs.html) ### ntp ntp is the Network Time Protocol (NTP) daemon. ### rsyslog rsyslogd is a system utility providing support for message logging (syslog). ### postfix Postfix is the mail server (smtp). Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Service\_daemons&oldid=9814](https://pve.proxmox.com/mediawiki/index.php?title=Service_daemons&oldid=9814) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Legacy: ZFS over iSCSI - Proxmox VE Legacy: ZFS over iSCSI ====================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Legacy:_ZFS_over_iSCSI#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Legacy:_ZFS_over_iSCSI#searchInput) ℹ️ **Note**: This article was historically maintained by users, but may still contain some possible useful info. See [Storage: ZFS over ISCSI](https://pve.proxmox.com/wiki/Storage:_ZFS_over_ISCSI "Storage: ZFS over ISCSI") for the official article from the Proxmox VE reference documentation Contents -------- * [1 Technology and features](https://pve.proxmox.com/wiki/Legacy:_ZFS_over_iSCSI#Technology_and_features) * [2 Platform notes](https://pve.proxmox.com/wiki/Legacy:_ZFS_over_iSCSI#Platform_notes) * [3 Proxmox configuration](https://pve.proxmox.com/wiki/Legacy:_ZFS_over_iSCSI#Proxmox_configuration) * [4 Extra configuration](https://pve.proxmox.com/wiki/Legacy:_ZFS_over_iSCSI#Extra_configuration) Technology and features ----------------------- As of Proxmox 3.3 the ZFS storage plugin is full supported which means the ability to use an external storage based on ZFS via iSCSI. The plugin will seamlessly integrate the ZFS storage as a viable storage backend for creating VM's using the the normal VM creation wizard in Proxmox. When Proxmox creates the raw disk image it will use the plugin to create a ZFS volume as the storage which contains the disk image. Eg. a ZFS volume will be created for every disk image like tank/vm-100-disk-1. Being a native ZFS volume also means that Proxmox will provide users live snapshots and cloning of VM's using ZFS' native snapshot and volume reference features. Since ZFS is available on several platforms using different iSCSI target implementation the plugin has a number of helper modules each providing the needed iSCSI functionality for the specific platform. For now iSCSI modules exists for the following platforms: * Solaris based platforms using Comstar. Tested on Omnios and Nexenta Store. For GUI use napp-it or Nexenta. * BSD based platforms using Istgt. Tested on FreeBSD 8.3, 9.0, 9.1. For GUI use zfsguru. * Linux based platforms with zfsonlinux using Iet. Tested on Debian Wheezy. I have no knowledge of available GUI's. Edit 2013-10-30: I have begun developing a ZFS plugin for OpenMediaVault in collaboration with the OpenMediaVault team. A beta release of the plugin is scheduled ultimo next month (November 2013). **A word of caution**. For enterprise usecases I would only recommend solaris based platforms with Comstar. Linux based platforms can IMHO be used in a non-enterprise setup which requires working HA. I will not recommend BSD based platforms for enterprise and/or HA setups due to limitations in the current iSCSI target implementation. Istgt will require a restart of the daemon every time a LUN is to be deleted or updated which means dropping all current connections. Work has begun to provide a native iSCSI target for FreeBSD 10 which hopefully will solve this inconvenience. NOTE: This is fixed in FreeBSD 10.x [URL](https://www.freebsd.org/doc/handbook/network-iscsi.html) Platform notes -------------- * On all zfs storages nodes the following should be added to /etc/ssh/sshd\_config: For old ssh from Solaris based OS LookupClientHostnames no VerifyReverseMapping no GSSAPIAuthentication no For OS which use openssh UseDNS no GSSAPIAuthentication no * For all storage platforms the distribution of root's ssh key is maintained through Proxmox's cluster wide file system which means you have to create this folder: /etc/pve/priv/zfs. In this folder you place the ssh key to use for each ZFS storage and the name of the key follows this naming scheme: \_id\_rsa. Portal is entered in the gui wizard's field portal so if a ZFS storage is referenced via the IP 192.168.1.1 then this IP is entered in the field portal and therefore the key will have this name: 192.168.1.1\_id\_rsa. Creating the key is simple. As root do the following: mkdir /etc/pve/priv/zfs ssh-keygen -f /etc/pve/priv/zfs/192.168.1.1\_id\_rsa ssh-copy-id -i /etc/pve/priv/zfs/192.168.1.1\_id\_rsa.pub root@192.168.1.1 * login once to zfs san from each proxmox node ssh -i /etc/pve/priv/zfs/192.168.1.1\_id\_rsa root@192.168.1.1 The authenticity of host '192.168.1.1 (192.168.1.1)' can't be established. RSA key fingerprint is 8c:f9:46:5e:40:65:b4:91:be:41:a0:25:ef:7f:80:5f. Are you sure you want to continue connecting (yes/no)? yes If you are logged in without errors you are ready to use your storage. * The key creation is only needed once for each portal so if the same portal provides several targets which is used for several storages in Proxmox you only create one key. * **Solaris**: Apart from performing the steps above no other things must be done. * **BSD**: Apart from performing the steps above the following is required: Since istgt must have at least one LUN before enabling a target you will have to create one LUN manually. The size is irrelevant so a LUN referencing a volume with size 1MB is sufficient but remember to name the volume with something different than the Proxmox naming scheme to avoid having it show up in the Proxmox content GUI. * **Linux**: Apart from performing the steps above no other things must be done. * **Nexenta**: Apart from performing the steps above the following is required: rm /root/.bash\_profile. To avoid to go in nmc console by default. ℹ️ **Note**: The ssh key **must not** be password protected, otherwise it will not work. Proxmox configuration --------------------- Use the GUI (Datacenter/Storage: Add ZFS) which will add configuration like below to /etc/pve/storage.cfg zfs: solaris blocksize 4k target iqn.2010-08.org.illumos:02:b00c9870-6a97-6f0b-847e-bbfb69d2e581:tank1 pool tank iscsiprovider comstar portal 192.168.3.101 content images zfs: BSD blocksize 4k target iqn.2007-09.jp.ne.peach.istgt:tank1 pool tank iscsiprovider istgt portal 192.168.3.114 content images zfs: linux blocksize 4k target iqn.2001-04.com.example:tank1 pool tank iscsiprovider iet portal 192.168.3.196 content images Then you can simply create disk with proxmox gui. Extra configuration ------------------- * **Thin provision**: When this option is checked volumes will only use actual space and grow as needed until limit is reached. * **Write cache**: When this option is unchecked the iSCSI write cache is disabled. Disabling write cache makes every write to the LUN synchronous thus reducing write performance but ensures data is persisted after each flush request made by the VM (if volumes has sync disabled data is only flushed to log!). If write cache is enabled then data persistence is left to the zfs volumes sync setting to decide when data should be flushed to disk. When iSCSI write cache is enabled your volume should have sync=standard or sync=always to ensure against data loss. Write cache is only configurable with Comstar. For istgt and iet write cache is disabled in the driver and cannot be enabled. * **Host group and target group**: If your storage node is configured to restrict access through host and target group this is where you should enter the required information. Note: iscsi multipath doesn't work yet, so it's use only the portal ip for the iscsi connection. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Legacy:\_ZFS\_over\_iSCSI&oldid=11388](https://pve.proxmox.com/mediawiki/index.php?title=Legacy:_ZFS_over_iSCSI&oldid=11388) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Convert OpenVZ to LXC" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Convert OpenVZ to LXC" ========================================== ← [Convert OpenVZ to LXC](https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC "Convert OpenVZ to LXC") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Convert_OpenVZ_to_LXC#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Convert_OpenVZ_to_LXC#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Convert OpenVZ to LXC](https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC "Convert OpenVZ to LXC") **: Displaying 4 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Convert_OpenVZ_to_LXC&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Convert_OpenVZ_to_LXC&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Convert_OpenVZ_to_LXC&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Convert_OpenVZ_to_LXC&limit=500) ) * [Roadmap](https://pve.proxmox.com/wiki/Roadmap "Roadmap") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Roadmap "Special:WhatLinksHere") ) * [Linux Container](https://pve.proxmox.com/wiki/Linux_Container "Linux Container") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Linux+Container "Special:WhatLinksHere") ) * [Upgrade from 3.x to 4.0](https://pve.proxmox.com/wiki/Upgrade_from_3.x_to_4.0 "Upgrade from 3.x to 4.0") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Upgrade+from+3.x+to+4.0 "Special:WhatLinksHere") ) * [Additional ways to migrate to Proxmox VE](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE "Additional ways to migrate to Proxmox VE") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Additional+ways+to+migrate+to+Proxmox+VE "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Convert_OpenVZ_to_LXC&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Convert_OpenVZ_to_LXC&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Convert_OpenVZ_to_LXC&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Convert_OpenVZ_to_LXC&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Convert\_OpenVZ\_to\_LXC](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Convert_OpenVZ_to_LXC) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Central Web-based Management" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Central Web-based Management" ================================================= ← [Central Web-based Management](https://pve.proxmox.com/wiki/Central_Web-based_Management "Central Web-based Management") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Central_Web-based_Management#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Central_Web-based_Management#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Central Web-based Management](https://pve.proxmox.com/wiki/Central_Web-based_Management "Central Web-based Management") **: Displaying 4 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Central_Web-based_Management&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Central_Web-based_Management&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Central_Web-based_Management&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Central_Web-based_Management&limit=500) ) * [Proxmox VE News](https://pve.proxmox.com/wiki/Proxmox_VE_News "Proxmox VE News") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Proxmox+VE+News "Special:WhatLinksHere") ) * [Proxmox VE 2.0 Cluster](https://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster "Proxmox VE 2.0 Cluster") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Proxmox+VE+2.0+Cluster "Special:WhatLinksHere") ) * [Quick installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Quick+installation "Special:WhatLinksHere") ) * [Proxmox VE 4.x Cluster](https://pve.proxmox.com/wiki/Proxmox_VE_4.x_Cluster "Proxmox VE 4.x Cluster") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Proxmox+VE+4.x+Cluster "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Central_Web-based_Management&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Central_Web-based_Management&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Central_Web-based_Management&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Central_Web-based_Management&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Central\_Web-based\_Management](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Central_Web-based_Management) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # NVIDIA vGPU on Proxmox VE - Proxmox VE NVIDIA vGPU on Proxmox VE ========================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#mw-head) [Jump to search](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Introduction) * [2 Support](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Support) * [3 Note about Full PCI Passthrough](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Note_about_Full_PCI_Passthrough) * [4 Hardware Setup](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Hardware_Setup) * [5 Software Versions](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Software_Versions) * [6 Preparation](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Preparation) * [6.1 Enable PCIe Passthrough](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Enable_PCIe_Passthrough) * [6.2 Setup Proxmox VE Repositories](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Setup_Proxmox_VE_Repositories) * [6.3 Update to Latest Package Versions](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Update_to_Latest_Package_Versions) * [6.4 Prepare using pve-nvidia-vgpu-helper](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Prepare_using_pve-nvidia-vgpu-helper) * [7 Host Driver Installation](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Host_Driver_Installation) * [7.1 Enabling SR-IOV](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Enabling_SR-IOV) * [7.2 Create a PCI Resource Mapping](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Create_a_PCI_Resource_Mapping) * [7.3 Multi-Instance GPU (MIG)](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Multi-Instance_GPU_(MIG)) * [8 Guest Configuration](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Guest_Configuration) * [8.1 General Setup](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#General_Setup) * [8.2 Remote Desktop Software](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Remote_Desktop_Software) * [8.2.1 Remote Desktop on Windows 10/11](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Remote_Desktop_on_Windows_10/11) * [8.2.2 VNC on Linux via x11vnc (Ubuntu/Rocky Linux)](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#VNC_on_Linux_via_x11vnc_(Ubuntu/Rocky_Linux)) * [8.3 vGPU Configuration](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#vGPU_Configuration) * [8.4 NVIDIA Guest Driver Installation](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#NVIDIA_Guest_Driver_Installation) * [8.4.1 Windows 10/11](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Windows_10/11) * [8.4.2 Ubuntu Desktop](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Ubuntu_Desktop) * [8.4.3 Rocky Linux](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Rocky_Linux) * [8.4.4 CUDA on Linux](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#CUDA_on_Linux) * [8.5 Guest vGPU Licensing](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Guest_vGPU_Licensing) * [8.6 Troubleshooting](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Troubleshooting) * [8.7 Known Issues](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Known_Issues) * [8.7.1 Windows 10/11 'Fast Startup'](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Windows_10/11_'Fast_Startup') * [9 Secure Boot](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Secure_Boot) * [10 Notes](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Notes) Introduction ------------ NVIDIA vGPU Software enables multiple virtual machines to use a single supported[\[1\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-supported-gpus-1) physical GPU. This article describes how to use NVIDIA vGPU software with the Proxmox Virtual Environment (Proxmox VE). The instructions were tested using an RTX A5000 and an RTX PRO 6000 Blackwell Server Edition. More information can also be found in the NVIDIA documentation[\[2\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-nvidia-docs-2) [\[3\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-3) . Support ------- Beginning with NVIDIA vGPU Software 18, Proxmox Virtual Environment is an officially supported platform. To be eligible for support tickets, you must have an **active and valid NVIDIA vGPU entitlement** as well as an active and valid Proxmox VE subscription on your cluster, with level **Basic, Standard or Premium**. See the Proxmox VE Subscription Agreement[\[4\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-4) and the Proxmox Support Offerings[\[5\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-5) for more details. For a list of supported hardware, see NVIDIA's Qualified System Catalog [\[6\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-system-catalog-6) . To get support, open a ticket on the [Proxmox Server Solutions Support Portal](https://my.proxmox.com/) . Note about Full PCI Passthrough ------------------------------- This page only covers passing through virtual GPUs ("vGPU"s) that are provided by specific data-center level cards from NVIDIA. For regular full device passthrough, please see the general documentation for that: [PCI(e)\_Passthrough](https://pve.proxmox.com/wiki/PCI(e)_Passthrough) Hardware Setup -------------- For optimal performance in production workloads, we recommend using appropriate enterprise-grade hardware. All GPUs on [NVIDIAs list of supported GPUs](https://docs.nvidia.com/vgpu/latest/grid-vgpu-release-notes-generic-linux-kvm/index.html#hardware-configuration) are supported on Proxmox VE. Please refer to NVIDIA's support page to verify server and version compatibility [\[7\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-7) [\[6\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-system-catalog-6) [\[1\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-supported-gpus-1) . Some Workstation NVIDIA GPUs do not have vGPU enabled by default, even though they support vGPU, like the RTX A5000. To enable vGPU for these models, switch the display mode using the NVIDIA Display Mode Selector Tool[\[8\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-8) . This will disable the display ports. For a list of GPUs where this is necessary check their documentation[\[9\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-9) . Note that this should be the exception and should only be necessary for workstation GPUs. Software Versions ----------------- The installation is supported on the following versions of Proxmox VE, Linux kernel, and NVIDIA drivers: | pve-manager | Kernel | vGPU Software Branch | NVIDIA Host drivers | | --- | --- | --- | --- | | 8.4.1 | 6.8.12-11-pve | 18.3 | 570.158.02 | | 8.4.1 | 6.11.11-2-pve | 18.3 | 570.158.02 | | 8.4.1 | 6.14.5-1-bpo12-pve | 18.3 | 570.158.02 | | 9.0.3 | 6.14.8-2-pve | 18.4 | 570.172.07 | | 9.1.4 | 6.17.4-1-pve | 19.4 | 580.126.08 | | 9.1.8 | 6.17.13-2-pve | 20.0 | 595.58.02 | | 9.1.8 | 7.0.0-1-rc6-pve | 20.0 | 595.58.02 | | Older, now outdated, tested versions. | | | | | --- | --- | --- | --- | | pve-manager | Kernel | vGPU Software Branch | NVIDIA Host drivers | | 7.2-7 | 5.15.39-2-pve | 14.1 | 510.73.06 | | 7.2-7 | 5.15.39-2-pve | 14.2 | 510.85.03 | | 7.4-3 | 5.15.107-2-pve | 15.2 | 525.105.14 | | 7.4-17 | 6.2.16-20-bpo11-pve | 16.0 | 535.54.06 | | 8.1.4 | 6.5.11-8-pve | 16.3 | 535.154.02 | | 8.1.4 | 6.5.13-1-pve | 16.3 | 535.154.02 | | 8.2.8 | 6.8.12-4-pve | 17.3 | 550.90.05 | | 8.2.8 | 6.11.0-1-pve | 17.3 | 550.90.05 | | 8.2.8 | 6.8.12-4-pve | 17.4 | 550.127.06 | | 8.2.8 | 6.11.0-1-pve | 17.4 | 550.127.06 | | 8.3.4 | 6.8.12-8-pve | 18.0 | 570.124.03 | | 8.3.4 | 6.11.11-1-pve | 18.0 | 570.124.03 | | 8.3.4 | 6.14.0-1-pve | 18.0 | 570.124.03 | | 8.4.1 | 6.8.12-10-pve | 18.1 | 570.133.10 | | 8.4.1 | 6.11.11-2-pve | 18.1 | 570.133.10 | | 8.4.1 | 6.14.0-2-pve | 18.1 | 570.133.10 | | 8.4.1 | 6.8.12-11-pve | 18.2 | 570.148.06 | | 8.4.1 | 6.11.11-2-pve | 18.2 | 570.148.06 | | 8.4.1 | 6.14.5-1-bpo12-pve | 18.2 | 570.148.06 | | 9.0.3 | 6.14.8-2-pve | 19.0 | 580.65.05 | | 9.0.10 | 6.14.11-2-pve | 19.1 | 580.82.02 | | 9.0.10 | 6.14.11-2-pve | 19.2 | 580.95.02 | | 9.0.11 | 6.14.11-4-pve | 19.2 | 580.95.02 | | 9.0.11 | 6.14.11-4-pve | 19.3 | 580.105.06 | ℹ️ **Note**: With 6.8+ based kernels / GRID version 17.3+, the lower level interface of the driver changed and requires `qemu-server ≥ 8.2.6` to be installed on the host. It is recommended to use the latest stable and supported version of Proxmox VE and NVIDIA drivers. However, newer versions in one vGPU Software Branch should also work for the same or older kernel version. A mapping of which NVIDIA vGPU software version corresponds to which driver version is available in the official documentation [\[10\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-driver-versions-10) . Since version 16.0, certain cards are no longer supported by the NVIDIA vGPU driver, but are supported by NVIDIA AI Enterprise [\[1\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-supported-gpus-1) [\[11\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-supported-gpus-ai-11) . The NVIDIA AI Enterprise driver behaves similarly to the vGPU driver. Therefore, the following steps should also apply. Note that vGPU and NVIDIA AI Enterprise are different products with different licenses, and **NVIDIA AI Enterprise** is currently **not officially supported** with Proxmox VE. Preparation ----------- Before actually installing the host drivers, there are a few steps that need to be done on the Proxmox VE host. ℹ️ **Note**: If you need to use a root shell, you can, open one by connecting via SSH or using the node shell on the Proxmox VE web interface. ### Enable PCIe Passthrough Make sure that your system is compatible with PCIe passthrough. See the [PCI(e) Passthrough](https://pve.proxmox.com/wiki/PCI(e)_Passthrough) documentation for details. Additionally, confirm that the following features are enabled in your firmware settings (BIOS/UEFI): * _VT-d_ for Intel, or _AMD-v_ for AMD (sometimes named IOMMU) * _SR-IOV_ (this may not be necessary for older pre-Ampere GPU generations) * Above 4G decoding * Alternative Routing ID Interpretation (ARI) (not necessary for pre-Ampere GPUs) The firmware of your host might use different naming. If you are unable to locate some of these options, refer to the documentation provided by your firmware or motherboard manufacturer. ℹ️ **Note**: It is crucial to ensure that both the IOMMU options are enabled in your firmware and the kernel. See [General Requirements for PCI(e) Passthrough](https://pve.proxmox.com/wiki/PCI(e)_Passthrough#_general_requirements) for how to do that. ### Setup Proxmox VE Repositories Proxmox VE ships with the enterprise repository set up by default, as this repository provides better tested software and is recommended for production use. The enterprise repository needs a valid subscription per node. For evaluation or non-production use cases, you can switch to the public `no-subscription` repository. Packages in the `no-subscription` repository get updated more frequently but are not as well tested. There is no difference in available features. You can use the `Repositories` management panel in the Proxmox VE web UI for managing package repositories, see the [documentation](https://pve.proxmox.com/wiki/Package_Repositories) for details. ### Update to Latest Package Versions Proxmox VE uses a rolling release model and should be updated frequently to ensure that your Proxmox VE installation has the latest bug and security fixes, and features available. You can update your Proxmox VE node using the `Updates` panel on the web UI. ### Prepare using `pve-nvidia-vgpu-helper` Since _pve-manager_ version `8.3.4` the `pve-nvidia-vgpu-helper` tool is included. If you're on an older version, please upgrade to the latest version or install it manually with apt install pve-nvidia-vgpu-helper The `pve-nvidia-vgpu-helper` tool will set up some basics, like blacklisting the `nouveau` driver, installing header packages, DKMS and so on. You can start the setup with pve-nvidia-vgpu-helper setup You will be asked if you want to install missing packages, answer 'y'. Once all the required packages have been successfully installed, you should see this message All done, you can continue with the NVIDIA vGPU driver installation. If the `nouveau` driver was loaded previously, you have to reboot after this step so it isn't loaded afterward. ℹ️ **Note**: If you install an opt-in kernel later, you have to also install the corresponding `proxmox-header-X.Y` package for DKMS to work. Host Driver Installation ------------------------ ℹ️ **Note**: The driver/file versions shown in this section are examples only; use the correct file names for the selected driver you're installing. ℹ️ **Note**: If you're using Secure boot, please refer to the Chapter [Secure Boot](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#Secure_Boot) before continuing. To get started, you will need the appropriate host and guest drivers; see the NVIDIA Virtual GPU Software Quick Start Guide[\[12\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-12) for instructions on how to obtain them. Choose `Linux KVM` as target hypervisor when downloading. In our case, we got the following host driver file: NVIDIA-Linux-x86\_64-525.105.14-vgpu-kvm.run Copy this file over to your Proxmox VE node, for example with SCP or an SSH file copy tool. If you are on Windows, [WinSCP](https://winscp.net/) can be used for this step. To start the installation, you need to make the installer executable first, and then pass the `--dkms` option when running it, to ensure that the module is rebuilt after a kernel upgrade: chmod +x NVIDIA-Linux-x86\_64-525.105.14-vgpu-kvm.run ./NVIDIA-Linux-x86\_64-525.105.14-vgpu-kvm.run --dkms Follow the steps of the installer. When you're asked if you want to register the kernel module sources with DKMS, answer 'yes'. After the installer has finished successfully, you will need to reboot your system, either using the web interface or by executing `reboot`. ### Enabling SR-IOV On newer NVIDIA GPUs (based on the Ampere architecture and beyond), you must first enable SR-IOV before being able to use vGPU. This can be done manually with the `sriov-manage` script from NVIDIA (this is lost on reboot). Alternatively, the `pve-nvidia-vgpu-helper` package comes with a systemd service template which calls it automatically on every boot. To enable it, use systemctl enable --now pve-nvidia-sriov@ALL.service You can replace `ALL` with a specific PCI ID (like `0000:01:00.0`) if you only want to enable it for a specific card. This will then run before the NVIDIA vGPU daemons and the Proxmox VE virtual guest auto start-up. Due to the `--now` parameter, it will be started immediately. Verify that there are multiple virtual functions for your device with: \# lspci -d 10de: In our case, there are now 24 virtual functions in addition to the physical card (01:00.0): 01:00.0 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) 01:00.4 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) 01:00.5 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) 01:00.6 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) 01:00.7 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) 01:01.0 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) 01:01.1 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) 01:01.2 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) 01:01.3 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) 01:01.4 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) 01:01.5 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) 01:01.6 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) 01:01.7 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) 01:02.0 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) 01:02.1 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) 01:02.2 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) 01:02.3 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) 01:02.4 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) 01:02.5 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) 01:02.6 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) 01:02.7 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) 01:03.0 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) 01:03.1 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) 01:03.2 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) 01:03.3 3D controller: NVIDIA Corporation GA102GL \[RTX A5000\] (rev a1) ### Create a PCI Resource Mapping For convenience and privilege separation, you can now create resource mappings for PCI devices. This can contain multiple PCI IDs, such as all virtual functions. The first available ID is automatically selected when the guest is started. Go to Datacenter → Resource mappings to create a new one. For details, see [Resource Mapping](https://pve.proxmox.com/wiki/QEMU/KVM_Virtual_Machines#resource_mapping "QEMU/KVM Virtual Machines") In the resource mapping you need to enable 'Use with mediated devices'[\[13\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-13) and select all relevant devices. For GPUs with SR-IOV (Ampere and later), this means the virtual functions which the card exposes. For example, using an RTX A5000 card, we want to select all virtual functions: [![](https://pve.proxmox.com/mediawiki/images/b/b3/Pve-vgpu-mapping.png)](https://pve.proxmox.com/wiki/File:Pve-vgpu-mapping.png) ### Multi-Instance GPU (MIG) Starting with the RTX PRO 6000 Blackwell Server Edition, NVIDIA vGPU enables regular time-sliced vGPUs to be created on hardware partitioned MIG instances. Note that this is an optional feature, and you can create vGPUs without MIG instances on these cards as well, but there might be different profiles available (For example, a 2GiB vWS profile on the RTX PRO 6000 Blackwell Server Edition is only available via MIG). This enables a higher density of small vGPUs and results in higher isolation between these partitions. For more in depth documentation, consult the NVIDIA vGPU Documentation[\[2\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-nvidia-docs-2) . Currently, using vGPU on MIG is supported on Proxmox VE with the following limitations: * MIG instances must be created and managed manually from the CLI * Placement of vGPUs on MIG instances is done automatically by the NVIDIA driver and cannot be changed To enable MIG for your card, do \# nvidia-smi -i -mig 1 After that, you can list the available MIG instance profiles: \# nvidia-smi mig -lgip For example on an RTX PRO 6000 Blackwell Server Edition, this looks like this: +-------------------------------------------------------------------------------+ | GPU instance profiles: | | GPU Name ID Instances Memory P2P SM DEC ENC | | Free/Total GiB CE JPEG OFA | |===============================================================================| | 0 MIG 1g.24gb 14 4/4 23.12 No 46 1 1 | | 1 1 0 | +-------------------------------------------------------------------------------+ | 0 MIG 1g.24gb+me 21 1/1 23.12 No 46 1 1 | | 1 1 1 | +-------------------------------------------------------------------------------+ | 0 MIG 1g.24gb+gfx 47 4/4 23.12 No 46 1 1 | | 1 1 0 | +-------------------------------------------------------------------------------+ | 0 MIG 1g.24gb+me.all 65 1/1 23.12 No 46 4 4 | | 1 4 1 | +-------------------------------------------------------------------------------+ | 0 MIG 1g.24gb-me 67 4/4 23.12 No 46 0 0 | | 1 0 0 | +-------------------------------------------------------------------------------+ | 0 MIG 2g.48gb 5 2/2 46.50 No 94 2 2 | | 2 2 0 | +-------------------------------------------------------------------------------+ | 0 MIG 2g.48gb+gfx 35 2/2 46.50 No 94 2 2 | | 2 2 0 | +-------------------------------------------------------------------------------+ | 0 MIG 2g.48gb+me.all 64 1/1 46.50 No 94 4 4 | | 2 4 1 | +-------------------------------------------------------------------------------+ | 0 MIG 2g.48gb-me 66 2/2 46.50 No 94 0 0 | | 2 0 0 | +-------------------------------------------------------------------------------+ | 0 MIG 4g.96gb 0 1/1 93.38 No 188 4 4 | | 4 4 1 | +-------------------------------------------------------------------------------+ | 0 MIG 4g.96gb+gfx 32 1/1 93.38 No 188 4 4 | | 4 4 1 | +-------------------------------------------------------------------------------+ To use MIG with vGPU you must use a profile with the `+gfx` postfix. You can create the instances like this: \# nvidia-smi mig -cgi 47,47,47,47 -C This creates 4 instances of profile '1g.24gb+gfx' (47) on the card with the corresponding compute instances. After that, you can use the Web UI to assign vGPU profiles to your VMs like usual. To delete the instances again you have to delete the compute instances and the gpu instances seperately: \# nvidia-smi mig -dci # nvidia-smi mig -dgi to delete all, or use the `-ci`(compute instance) / `-gi`(gpu instance) parameters to reference a specific one. To disable MIG again, use \# nvidia-smi -i -mig 0 Guest Configuration ------------------- ### General Setup First, set up a VM as you normally would, without adding a vGPU. This can be done either with the Virtual Machine wizard in the Web UI or via the CLI tool `qm`. For guest specific notes, see for example [Windows 11 guest best practices](https://pve.proxmox.com/wiki/Windows%2011%20guest%20best%20practices) . Please note that all Linux commands shown are assumed to be run as a privileged user. For example, directly as the `root` user, or prefixed with `sudo`. ### Remote Desktop Software Since the built-in VNC and SPICE console cannot display the virtual display provided by the vGPU, you need some kind of remote desktop software installed in the guest to access the guest. There are many options available, see the NVIDIA documentation[\[2\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-nvidia-docs-2) or [Wikipedia Comparison of Remote Desktop Software](https://en.wikipedia.org/wiki/Comparison_of_remote_desktop_software) for examples. We show how to enable two examples here, Remote Desktop for Windows 10/11, and VNC (via x11vnc) on Linux: #### Remote Desktop on Windows 10/11 To enable Remote Desktop on Windows 10/11, go to Settings → System → Remote Desktop and enable the Remote Desktop option. * [![](https://pve.proxmox.com/mediawiki/images/thumb/d/d3/Windows_rdp.png/240px-Windows_rdp.png)](https://pve.proxmox.com/wiki/File:Windows_rdp.png) * [![](https://pve.proxmox.com/mediawiki/images/thumb/0/00/Win11-remote-desktop.png/240px-Win11-remote-desktop.png)](https://pve.proxmox.com/wiki/File:Win11-remote-desktop.png) #### VNC on Linux via x11vnc (Ubuntu/Rocky Linux) Note that this is just an example; how you want to configure remote desktops on Linux will depend on your use case. Ubuntu 24.04 and Rocky Linux 9 ship with GDM3 + Gnome per default, which make it a bit harder to share the screen with x11vnc. So the first step is to install a different display manager. We successfully tested LightDM here, but others may work as well. Note that for Rocky linux you might need to enable the EPEL repository beforehand with: \# dnf install epel-release First, we install and activate the new display manager: Ubuntu: \# apt install lightdm Select 'LightDM' as default login manager when prompted. Rocky Linux: \# dnf install lightdm # systemctl disable --now gdm.service # systemctl enable --now lightdm.service After that install `x11vnc` with Ubuntu: \# apt install x11vnc Rocky Linux: \# dnf install x11vnc We then added a systemd service that starts the VNC server on the x.org server provided by LightDM in `/etc/systemd/system/x11vnc.service` \[Unit\] Description=Start x11vnc After=multi-user.target \[Service\] Type=simple ExecStart=/usr/bin/x11vnc -display :0 -auth /var/run/lightdm/root/:0 -forever -loop -repeat -rfbauth /etc/x11vnc.passwd -rfbport 5900 -shared -noxdamage \[Install\] WantedBy=multi-user.target You can set the password by executing: \# x11vnc -storepasswd /etc/x11vnc.passwd # chmod 0400 /etc/x11vnc.passwd On Rocky Linux, you might need to allow VNC in the firewall: \# firewall-cmd --permanent --add-port=5900/tcp After setting up LightDM and x11vnc and restarting the VM, you should now be able to connect via VNC. ### vGPU Configuration After configuring the VM to your liking, shut down the VM and add a vGPU by selecting one of the virtual functions and selecting the appropriate mediated device type. For example: Via the CLI: qm set VMID -hostpci0 01:00.4,mdev=nvidia-660 Via the web interface: [![Selecting a vGPU model](https://pve.proxmox.com/mediawiki/images/8/81/PVE_select_a_vgpu_with_mapping.png)](https://pve.proxmox.com/wiki/File:PVE_select_a_vgpu_with_mapping.png "Selecting a vGPU model") Selecting a vGPU model To find the correct mediated device type, you can use `pvesh get /nodes/NODENAME/hardware/pci/MAPPINGNAME/mdev`. This will query sysfs for all supported types that can be created. Note that, depending on the driver and kernel versions in use, not all models may be visible here, but only those that are currently available. ### NVIDIA Guest Driver Installation #### Windows 10/11 Refer to their documentation[\[10\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-driver-versions-10) to find a compatible guest driver to host driver mapping. For example: 553.24\_grid\_win10\_win11\_server2022\_dch\_64bit\_international.exe Start the installer and follow the instructions, then, after it finished, restart the guest as prompted. * [![Starting NVIDIA driver installation on Windows 10](https://pve.proxmox.com/mediawiki/images/thumb/f/f3/Windows_nv_install01.png/240px-Windows_nv_install01.png)](https://pve.proxmox.com/wiki/File:Windows_nv_install01.png "Starting NVIDIA driver installation on Windows 10") Starting NVIDIA driver installation on Windows 10 * [![Accepting the license agreement on Windows 10](https://pve.proxmox.com/mediawiki/images/thumb/5/51/Windows_nv_install02.png/240px-Windows_nv_install02.png)](https://pve.proxmox.com/wiki/File:Windows_nv_install02.png "Accepting the license agreement on Windows 10") Accepting the license agreement on Windows 10 * [![Finishing the installation on Windows 10](https://pve.proxmox.com/mediawiki/images/thumb/3/35/Windows_nv_install03.png/240px-Windows_nv_install03.png)](https://pve.proxmox.com/wiki/File:Windows_nv_install03.png "Finishing the installation on Windows 10") Finishing the installation on Windows 10 * [![Starting NVIDIA driver installation on Windows 11](https://pve.proxmox.com/mediawiki/images/thumb/3/3b/Win11-nv-install01.jpg/240px-Win11-nv-install01.jpg)](https://pve.proxmox.com/wiki/File:Win11-nv-install01.jpg "Starting NVIDIA driver installation on Windows 11") Starting NVIDIA driver installation on Windows 11 * [![Accepting the license agreement on Windows 11](https://pve.proxmox.com/mediawiki/images/thumb/e/e7/Win11-nv-install02.jpg/240px-Win11-nv-install02.jpg)](https://pve.proxmox.com/wiki/File:Win11-nv-install02.jpg "Accepting the license agreement on Windows 11") Accepting the license agreement on Windows 11 * [![Finishing the installation on Windows 11](https://pve.proxmox.com/mediawiki/images/thumb/5/53/Win11-nv-install03.jpg/240px-Win11-nv-install03.jpg)](https://pve.proxmox.com/wiki/File:Win11-nv-install03.jpg "Finishing the installation on Windows 11") Finishing the installation on Windows 11 From this point on, Proxmox VE's built-in noVNC console will no longer work, so use your desktop sharing software to connect to the Guest. Now you can use the vGPU for starting 3D applications such as Blender, 3D games, etc. * [![Unigine Valley on Windows 10](https://pve.proxmox.com/mediawiki/images/thumb/6/68/Windows_valley.png/240px-Windows_valley.png)](https://pve.proxmox.com/wiki/File:Windows_valley.png "Unigine Valley on Windows 10") Unigine Valley on Windows 10 * [![SuperTuxKart on Windows 10](https://pve.proxmox.com/mediawiki/images/thumb/9/92/Windows_supertuxkart.png/240px-Windows_supertuxkart.png)](https://pve.proxmox.com/wiki/File:Windows_supertuxkart.png "SuperTuxKart on Windows 10") SuperTuxKart on Windows 10 * [![Blender on Windows 10](https://pve.proxmox.com/mediawiki/images/thumb/5/5c/Windows_blender.png/240px-Windows_blender.png)](https://pve.proxmox.com/wiki/File:Windows_blender.png "Blender on Windows 10") Blender on Windows 10 * [![Blender on Windows 11](https://pve.proxmox.com/mediawiki/images/thumb/a/a7/Win11-blender.jpg/240px-Win11-blender.jpg)](https://pve.proxmox.com/wiki/File:Win11-blender.jpg "Blender on Windows 11") Blender on Windows 11 * [![Unigine Superposition on Windows 11](https://pve.proxmox.com/mediawiki/images/thumb/d/d8/Win11-superposition.jpg/240px-Win11-superposition.jpg)](https://pve.proxmox.com/wiki/File:Win11-superposition.jpg "Unigine Superposition on Windows 11") Unigine Superposition on Windows 11 * [![SuperTuxKart on Windows 11](https://pve.proxmox.com/mediawiki/images/thumb/1/12/Win11-supertuxkart.jpg/240px-Win11-supertuxkart.jpg)](https://pve.proxmox.com/wiki/File:Win11-supertuxkart.jpg "SuperTuxKart on Windows 11") SuperTuxKart on Windows 11 #### Ubuntu Desktop To install the NVIDIA driver on Ubuntu, use `apt` to install the .deb package that NVIDIA provides for Ubuntu. Check the NVIDIA documentation[\[10\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-driver-versions-10) for a compatible guest driver to host driver mapping. In our case, this was `nvidia-linux-grid-550_550.127.05_amd64.deb`. For that to work you must prefix the relative path, for example `./` if the `.deb` file is located in the current directory. \# apt install ./nvidia-linux-grid-550\_550.127.05\_amd64.deb * [![List NVIDIA driver files](https://pve.proxmox.com/mediawiki/images/thumb/e/e2/Ubuntu-nv-install01.jpg/240px-Ubuntu-nv-install01.jpg)](https://pve.proxmox.com/wiki/File:Ubuntu-nv-install01.jpg "List NVIDIA driver files") List NVIDIA driver files * [![Start NVIDIA driver installation](https://pve.proxmox.com/mediawiki/images/thumb/a/a4/Ubuntu-nv-install02.jpg/240px-Ubuntu-nv-install02.jpg)](https://pve.proxmox.com/wiki/File:Ubuntu-nv-install02.jpg "Start NVIDIA driver installation") Start NVIDIA driver installation * [![Finished NVIDIA driver installation](https://pve.proxmox.com/mediawiki/images/thumb/3/30/Ubuntu-nv-install03.jpg/240px-Ubuntu-nv-install03.jpg)](https://pve.proxmox.com/wiki/File:Ubuntu-nv-install03.jpg "Finished NVIDIA driver installation") Finished NVIDIA driver installation Then you must use NVIDIA's tools to configure the x.org configuration with: \# nvidia-xconfig Now you can reboot and use a VNC client to connect and use the vGPU for 3D applications. * [![Unigine Valley (Ubuntu 22.04)](https://pve.proxmox.com/mediawiki/images/thumb/4/40/Ubuntu_valley.png/240px-Ubuntu_valley.png)](https://pve.proxmox.com/wiki/File:Ubuntu_valley.png "Unigine Valley (Ubuntu 22.04)") Unigine Valley (Ubuntu 22.04) * [![SuperTuxKart (Ubuntu 22.04)](https://pve.proxmox.com/mediawiki/images/thumb/0/04/Nv_Ubuntu_supertuxkart.png/240px-Nv_Ubuntu_supertuxkart.png)](https://pve.proxmox.com/wiki/File:Nv_Ubuntu_supertuxkart.png "SuperTuxKart (Ubuntu 22.04)") SuperTuxKart (Ubuntu 22.04) * [![Blender (Ubuntu 22.04)](https://pve.proxmox.com/mediawiki/images/thumb/7/70/Ubuntu_blender.png/240px-Ubuntu_blender.png)](https://pve.proxmox.com/wiki/File:Ubuntu_blender.png "Blender (Ubuntu 22.04)") Blender (Ubuntu 22.04) * [![Unigine Superposition (Ubuntu 24.04)](https://pve.proxmox.com/mediawiki/images/thumb/e/ee/Ubuntu-24-superposition.jpg/240px-Ubuntu-24-superposition.jpg)](https://pve.proxmox.com/wiki/File:Ubuntu-24-superposition.jpg "Unigine Superposition (Ubuntu 24.04)") Unigine Superposition (Ubuntu 24.04) * [![SuperTuxKart (Ubuntu 24.04)](https://pve.proxmox.com/mediawiki/images/thumb/2/22/Ubuntu-24-supertuxkart.jpg/240px-Ubuntu-24-supertuxkart.jpg)](https://pve.proxmox.com/wiki/File:Ubuntu-24-supertuxkart.jpg "SuperTuxKart (Ubuntu 24.04)") SuperTuxKart (Ubuntu 24.04) * [![Blender Classroom (Ubuntu 24.04)](https://pve.proxmox.com/mediawiki/images/thumb/6/63/Ubuntu-24-blender.jpg/240px-Ubuntu-24-blender.jpg)](https://pve.proxmox.com/wiki/File:Ubuntu-24-blender.jpg "Blender Classroom (Ubuntu 24.04)") Blender Classroom (Ubuntu 24.04) #### Rocky Linux To install the NVIDIA driver on Rocky Linux, use `dnf` to install the .rpm package that NVIDIA provides for Red Hat based distributions. Check the NVIDIA documentation[\[10\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-driver-versions-10) for a compatible guest driver to host driver mapping. In our case, this was `nvidia-linux-grid-550-550.127.05-1.x86_64.rpm`. If the file is located in the current directory, run: \# dnf install nvidia-linux-grid-550-550.127.05-1.x86\_64.rpm * [![Start driver installation](https://pve.proxmox.com/mediawiki/images/thumb/3/32/Rocky-9-nv-install01.jpg/240px-Rocky-9-nv-install01.jpg)](https://pve.proxmox.com/wiki/File:Rocky-9-nv-install01.jpg "Start driver installation") Start driver installation * [![Finished driver installation](https://pve.proxmox.com/mediawiki/images/thumb/9/9e/Rocky-9-nv-install02.jpg/240px-Rocky-9-nv-install02.jpg)](https://pve.proxmox.com/wiki/File:Rocky-9-nv-install02.jpg "Finished driver installation") Finished driver installation Then you must use NVIDIA's tools to configure the x.org configuration with: \# nvidia-xconfig Now you can reboot and use a VNC client to connect and use the vGPU for 3D applications. * [![Blender Classroom render](https://pve.proxmox.com/mediawiki/images/thumb/c/cf/Rocky-9-blender.jpg/240px-Rocky-9-blender.jpg)](https://pve.proxmox.com/wiki/File:Rocky-9-blender.jpg "Blender Classroom render") Blender Classroom render * [![Unigine Superposition](https://pve.proxmox.com/mediawiki/images/thumb/b/bf/Rocky-9-superposition.jpg/240px-Rocky-9-superposition.jpg)](https://pve.proxmox.com/wiki/File:Rocky-9-superposition.jpg "Unigine Superposition") Unigine Superposition * [![SuperTuxKart](https://pve.proxmox.com/mediawiki/images/thumb/4/4c/Rocky-9-supertuxkart.jpg/240px-Rocky-9-supertuxkart.jpg)](https://pve.proxmox.com/wiki/File:Rocky-9-supertuxkart.jpg "SuperTuxKart") SuperTuxKart #### CUDA on Linux If you want to use CUDA on a Linux Guest, you might need to install the CUDA Toolkit manually[\[14\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-14) . Check the NVIDIA documentation which version of CUDA is supported for your vGPU drivers. ### Guest vGPU Licensing To use the vGPU without restriction, you must adhere to NVIDIA's licensing. Check the NVIDIA vGPU documentation[\[15\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-15) for instructions on how to do so. For setting up a DLS (Delegated License Service), see NVIDIAs DLS Documentation[\[16\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-16) . **Tip**: Ensure that the guest system time is properly synchronized using NTP. Otherwise, the guest will be unable to request a license for the vGPU. ### Troubleshooting A warning like the following might get logged by QEMU on VM startup. This usually only happens on consumer hardware which does not support PCIe AER[\[17\]](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_note-17) error recovery properly, it generally should not have any adverse effects on normal operation, but PCIe link errors might not be (soft-)recoverable in such cases. kvm: -device vfio-pci,host=0000:09:00.5,id=hostpci0,bus=ich9-pcie-port-1,addr=0x0: warning: vfio 0000:09:00.5: Could not enable error recovery for the device ### Known Issues #### Windows 10/11 'Fast Startup' In Windows 10/11 'fast startup' is enabled by default. When enabled, a shutdown via ACPI or the start menu will use 'hybrid shutdown'. The next boot will fail with a blue screen and the vGPU will be disabled. Disable 'fast boot' in Windows to prevent this. In the Control Panel → Power Options → Choose what the power button does → Uncheck 'fast startup'. Alternatively, disable hybrid shutdown in a command prompt with admin privileges: Powercfg -h off Secure Boot ----------- When booting the host with secure boot, kernel modules must be signed with a trusted key. We will show you how to set up your host so that the NVIDIA driver is signed and ready to load. For more details, see [Secure Boot Setup](https://pve.proxmox.com/wiki/Secure_Boot_Setup "Secure Boot Setup") . To be able to enroll the keys into the UEFI, make sure you have access to the physical display output during boot. This is necessary for confirming the key import. On servers, this can usually be achieved with IPMI/iKVM/etc. Before installing the NVIDIA Host driver, we need to install a few prerequisites to enroll the DKMS signing key into UEFI: apt install shim-signed grub-efi-amd64-signed mokutil Now you can install the NVIDIA driver, but with an additional parameter: ./NVIDIA-Linux-x86\_64-525.105.14-vgpu-kvm.run --dkms --skip-module-load When asked if the installer should sign the module, select 'no'. After the installer is finished, we now want to rebuild the kernel modules with DKMS, which will sign the kernel module for us with a generated key. First, check what module version is installed with: dkms status Which will output a line like this: nvidia/550.144.02, 6.8.12-6-pve, x86\_64: installed You need to rebuild and reinstall the listed module with (replace the version with the one on your system) dkms build -m nvidia -v 550.144.02 --force dkms install -m nvidia -v 550.144.02 --force This will ensure that the modules are signed with the DKMS key located in /var/lib/dkms/mok.pub If you have not already done so, enroll the DKMS key as described in [Using DKMS with Secure Boot](https://pve.proxmox.com/wiki/Secure_Boot_Setup#Using_DKMS_with_Secure_Boot "Secure Boot Setup") . You should then be able to load the signed NVIDIA kernel module. You can verify this by checking if the PCI devices have their driver loaded, e.g. with lspci -d 10de: -nnk It should say Kernel driver in use: nvidia You can now continue with the next step after the driver installation. Notes ----- 1. ↑ [1.0](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-supported-gpus_1-0) [1.1](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-supported-gpus_1-1) [1.2](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-supported-gpus_1-2) NVIDIA GPUs supported by vGPU [https://docs.nvidia.com/vgpu/gpus-supported-by-vgpu.html](https://docs.nvidia.com/vgpu/gpus-supported-by-vgpu.html) 2. ↑ [2.0](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-nvidia-docs_2-0) [2.1](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-nvidia-docs_2-1) [2.2](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-nvidia-docs_2-2) Latest NVIDIA vGPU Documentation [https://docs.nvidia.com/vgpu/latest/index.html](https://docs.nvidia.com/vgpu/latest/index.html) 3. [↑](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-3) NVIDIA vGPU Linux with KVM Documenation [https://docs.nvidia.com/vgpu/latest/grid-vgpu-release-notes-generic-linux-kvm/index.html](https://docs.nvidia.com/vgpu/latest/grid-vgpu-release-notes-generic-linux-kvm/index.html) 4. [↑](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-4) Proxmox VE Subscription Agreement [https://www.proxmox.com/en/downloads/proxmox-virtual-environment/agreements/proxmox-ve-subscription-agreement](https://www.proxmox.com/en/downloads/proxmox-virtual-environment/agreements/proxmox-ve-subscription-agreement) 5. [↑](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-5) Proxmox VE Subscriptions [https://www.proxmox.com/en/products/proxmox-virtual-environment/pricing](https://www.proxmox.com/en/products/proxmox-virtual-environment/pricing) 6. ↑ [6.0](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-system-catalog_6-0) [6.1](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-system-catalog_6-1) NVIDIA Qualified System Catalog [https://marketplace.nvidia.com/en-us/enterprise/qualified-system-catalog/](https://marketplace.nvidia.com/en-us/enterprise/qualified-system-catalog/) 7. [↑](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-7) NVIDIA vGPU Support Matrix [https://docs.nvidia.com/vgpu/latest/product-support-matrix/index.html](https://docs.nvidia.com/vgpu/latest/product-support-matrix/index.html) 8. [↑](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-8) NVIDIA Display Mode Selector Tool [https://developer.nvidia.com/displaymodeselector](https://developer.nvidia.com/displaymodeselector) 9. [↑](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-9) Latest NVIDIA vGPU user guide: Switching the Mode of a GPU that Supports Multiple Display Modes [https://docs.nvidia.com/vgpu/latest/grid-vgpu-user-guide/index.html#displaymodeselector](https://docs.nvidia.com/vgpu/latest/grid-vgpu-user-guide/index.html#displaymodeselector) 10. ↑ [10.0](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-driver-versions_10-0) [10.1](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-driver-versions_10-1) [10.2](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-driver-versions_10-2) [10.3](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-driver-versions_10-3) NVIDIA vGPU Driver versions [https://docs.nvidia.com/vgpu/#driver-versions](https://docs.nvidia.com/vgpu/#driver-versions) 11. [↑](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-supported-gpus-ai_11-0) NVIDIA GPUs supported by NVIDIA AI Enterprise [https://docs.nvidia.com/ai-enterprise/latest/product-support-matrix/index.html](https://docs.nvidia.com/ai-enterprise/latest/product-support-matrix/index.html) 12. [↑](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-12) Getting your NVIDIA vGPU Software: [https://docs.nvidia.com/vgpu/latest/grid-software-quick-start-guide/index.html#getting-your-nvidia-grid-software](https://docs.nvidia.com/vgpu/latest/grid-software-quick-start-guide/index.html#getting-your-nvidia-grid-software) 13. [↑](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-13) Mediated Devices [https://pve.proxmox.com/wiki/PCI(e)\_Passthrough#\_mediated\_devices\_vgpu\_gvt\_g](https://pve.proxmox.com/wiki/PCI(e)_Passthrough#_mediated_devices_vgpu_gvt_g) 14. [↑](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-14) NVIDIA CUDA Toolkit Download [https://developer.nvidia.com/cuda-downloads](https://developer.nvidia.com/cuda-downloads) 15. [↑](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-15) NVIDIA vGPU Licensing User Guide: [https://docs.nvidia.com/vgpu/latest/grid-licensing-user-guide/index.html](https://docs.nvidia.com/vgpu/latest/grid-licensing-user-guide/index.html) 16. [↑](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-16) NVIDIA DLS Documentation [https://docs.nvidia.com/license-system/latest/](https://docs.nvidia.com/license-system/latest/) 17. [↑](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE#cite_ref-17) PCI Express Advanced Error Reporting Driver Guide: [https://www.kernel.org/doc/html/v6.12-rc4/PCI/pcieaer-howto.html](https://www.kernel.org/doc/html/v6.12-rc4/PCI/pcieaer-howto.html) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=NVIDIA\_vGPU\_on\_Proxmox\_VE&oldid=12534](https://pve.proxmox.com/mediawiki/index.php?title=NVIDIA_vGPU_on_Proxmox_VE&oldid=12534) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Qemu/KVM](https://pve.proxmox.com/wiki/Category:Qemu/KVM "Category:Qemu/KVM") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Install Proxmox VE on Debian Squeeze on 32-Bit Processor - Proxmox VE Install Proxmox VE on Debian Squeeze on 32-Bit Processor ======================================================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze_on_32-Bit_Processor#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze_on_32-Bit_Processor#searchInput) This article deals with installing Proxmox VE 2.1 on 32-bit Debian Squeeze. Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze_on_32-Bit_Processor#Introduction) * [2 Installation](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze_on_32-Bit_Processor#Installation) * [2.1 Step 1: Setup a fresh Debian Squeeze 32-bit system](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze_on_32-Bit_Processor#Step_1:_Setup_a_fresh_Debian_Squeeze_32-bit_system) * [2.2 Step 2: Prepare the installed system](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze_on_32-Bit_Processor#Step_2:_Prepare_the_installed_system) * [2.3 Step 3: Install the packages](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze_on_32-Bit_Processor#Step_3:_Install_the_packages) * [2.4 Upgrade](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze_on_32-Bit_Processor#Upgrade) * [3 Notes](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze_on_32-Bit_Processor#Notes) * [4 Bugs](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze_on_32-Bit_Processor#Bugs) * [5 Build the packages yourself](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze_on_32-Bit_Processor#Build_the_packages_yourself) Introduction ------------ I started originally with Proxmox VE 1.4, installing it on my 32-bit host using these instructions: [Install Proxmox VE on Debian Lenny on 32-Bit Processor](https://pve.proxmox.com/mediawiki/index.php?title=Install_Proxmox_VE_on_Debian_Lenny_on_32-Bit_Processor&action=edit&redlink=1 "Install Proxmox VE on Debian Lenny on 32-Bit Processor (page does not exist)") . Big thanks to the author for the helpful hints in that article. I expanded upon his approach by re-building all the packages, including the custom patched kernel. The pre-built packages here are based on the sources available on September 20th, 2012 (equivalent to v2.1 with some v2.2 updates). Installation ------------ If you'd like to just get on with it and install the packages, our company, Locatrix Communications, has provided a download repository with the pre-made packages. **We make no guarantees what-so-ever about these packages. They are unofficial and completely unsupported.** ### Step 1: Setup a fresh Debian Squeeze 32-bit system Here's the CD image we used: wget http://cdimage.debian.org/cdimage/archive/6.0.8/i386/iso-cd/debian-6.0.8-i386-netinst.iso When partitioning, use LVM and you're going to want to leave 4GB of space free for snapshot backups (reference: [http://forum.proxmox.com/threads/2059-backup-issues](http://forum.proxmox.com/threads/2059-backup-issues) ). The Proxmox bare-metal installer does this automatically when installing the default setup. Snapshot backups should only use 1GB of that space regardless of the VM size. Here's how to setup your partitioning: * Guided - Use entire disk and set up LVM * Select default disk (e.g. "SCSI3 (0,0,0...") * All files in one partition * Choose "Yes" to write the changes to disks and configure LVM * On the "Partition disks" review screen * Arrow up and choose "Configure the Logical Volume Manager" * Choose "Yes" to write the changes to disks and configure LVM * Delete logical volume * Choose "root" * Create logical volume * Choose default volume group, e.g. "debian" * Enter "root" as the logical volume name * Now choose a size that is around 4GB smaller than the default to allow for that 4GB to be used for snapshot backups (e.g. if the default is "47934MB", I just entered "43934MB") * Finish * Arrow down and select the line that says "#1 XX GB" (with XX being the size you chose above), it's the line underneath "LVM VG debian, LV root...". * Choose "Use as: do not use" * Choose "Ext3 journaling file system" * Choose "Mount point: none" * Choose "/ - the root file system" * Choose "Done setting up the partition" * Choose "Finish partitioning and write changes to disk" * Choose "Yes" to write the changes to disks Proceed through the rest of the installation. ### Step 2: Prepare the installed system Add the Locatrix package repository vi /etc/apt/sources.list # Add a new line: deb http://download.locatrix.com/proxmox32/ ./ Download the updated package information aptitude update Setup the network apt-get install postfix bridge-utils vi /etc/network/interfaces # Add the below in place of your existing eth0 configuration # This assumes you have a single network interface on a local LAN on 192.168.0.x # The bridge interface below should take-over the IP you were previously using on eth0 iface eth0 inet manual auto vmbr0 iface vmbr0 inet static address 192.168.0.90 netmask 255.255.255.0 gateway 192.168.0.254 bridge\_ports eth0 bridge\_stp off bridge\_fd 0 Setup NAT forwarding \# Save vi /etc/sysctl.conf # Uncomment the line net.ipv4.ip\_forward=1 # Save/test sysctl -p Setup hosts file for pve-manager vi /etc/hosts # Set to your machine's actual vmbr0 interface IP from above instead of 127.0.1.1 192.168.0.90 somemachine.mynet.net somemachine pvelocalhost Install NTP apt-get install ntp ### Step 3: Install the packages First install the kernel apt-get install pve-firmware apt-get install pve-kernel-2.6.32-14-pve reboot uname -a should report "2.6.32-14-pve" Do not proceed with rebooting first! I've had to include a bit of hacking with LVM until I sort out the problem. It seems using the lvm2 package excludes a necessary init script to bootstrap lvm. apt-get install clvm apt-get install vzctl wget http://download.locatrix.com/proxmox32/lvmfix.sh wget http://download.locatrix.com/proxmox32/hooks-lvm2 wget http://download.locatrix.com/proxmox32/local-top-lvm2 sh ./lvmfix.sh Ensure you setup the /etc/hosts file correctly as above, or pve-manager will fail to install. Install the rest of the packages: apt-get install proxmox-ve-2.6.32 apt-get install ssh ksm-control-daemon a2ensite pve-redirect.conf /etc/init.d/apache2 reload Not required, but I recommend giving your machine another reboot at this stage to make sure everything comes up OK. Better to find out now. reboot Visit your new Proxmox install: https://:8006 * Login using your Linux password, e.g. "root" and "" If you want to get started right away adding some VMs, I recommend you do this: * Login as above * Click on Datacenter->mymachine->local (mymachine)->Content * Click Templates in that section * Click a template and download it, e.g. "Ubuntu 10.04" * After the template has been downloaded, you can now launch a VM of that type using "Create CT" in the upper-right-hand-corner ### Upgrade **UPDATE: September 2012 - Updated the repository to a later version of the source code and improved some parts of the build process.** You should be able to automatically upgrade from the previous release to the latest with these commands apt-get update apt-get upgrade apt-get install proxmox-ve-2.6.32 pve-qemu-kvm qemu-server Notes ----- One difference from the [Install\_Proxmox\_VE\_on\_Debian\_Lenny\_on\_32-Bit\_Processor](https://pve.proxmox.com/mediawiki/index.php?title=Install_Proxmox_VE_on_Debian_Lenny_on_32-Bit_Processor&action=edit&redlink=1 "Install Proxmox VE on Debian Lenny on 32-Bit Processor (page does not exist)") instructions is that I included all the qemu and KVM packages, because I understand they may be useful for some people. You can also still run VMs under QEMU in this setup even if you don't have hardware support for KVM. This isn't recommended, however, and what you really want is to just use OpenVZ for everything. * On start-up you see messages like "unable to load kvm module" * This means your processor doesn't support KVM, so just ignore it and use OpenVZ for all of your VMs * If you try to start a VM and see "No accelerator found!" * This means your hardware doesn't support KVM. * You can disable KVM under Options->KVM hardware acceleration, but in general this is a bad idea since it means the system will fall-back to QEMU-only, which will give you poor performance. Instead you should create your VMs with "Create CT" to use OpenVZ. * If you see "start failed" after doing the above, you may have selected an unsupported CPU type. * Login to your host machine and run: /usr/bin/kvm -cpu ? * This will give you a list of valid options, like "Opteron\_G3", note items in brackets are not available, like "\[pentium3\]" Bugs ---- Reports from the wild suggest that the packages seem to work fine in stand-alone servers, but clustering may have issues. If you have information to share, send it through to Andrew Eross on the [PVE users mailing list](http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user) Build the packages yourself --------------------------- If you'd like to re-build all of the packages yourself, we are happy to share the [PHP build script](http://download.locatrix.com/proxmox32/build) that automatically downloads all the sources, modifies the package files, builds, and then creates a repository for the packages. This is the same script used to create the Locatrix repository above from scratch. Notes: * Start with a clean Debian Squeeze 32-bit system. You need to be aware the build process can harm your system and so you really do this inside of a new VM that you don't mind deleting afterwards. * Run the build either as root or from an account that can use sudo. Various parts of the build process require packages to be installed as we proceed. Run the build: \# install sudo because the build script assumes you have it su root -c 'apt-get install sudo' vi /etc/group # add your current user account to the 'sudo' group if you're not running as root # save sudo apt-get install php5-cli cd ~ wget http://download.locatrix.com/proxmox32/build # output some information about the build program php ./build # now run the full build php ./build -f # hint: if you seem to get stuck on "Preconfiguring packages..." for a while .. # just press enter once.. some GUI screen in the background gets stuck every time for me | Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Install\_Proxmox\_VE\_on\_Debian\_Squeeze\_on\_32-Bit\_Processor&oldid=10458](https://pve.proxmox.com/mediawiki/index.php?title=Install_Proxmox_VE_on_Debian_Squeeze_on_32-Bit_Processor&oldid=10458) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Installation](https://pve.proxmox.com/wiki/Category:Installation "Category:Installation") * [Archive](https://pve.proxmox.com/wiki/Category:Archive "Category:Archive") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Windows VirtIO Drivers - Proxmox VE Windows VirtIO Drivers ====================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#Introduction) * [2 virtio-win Releases](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#virtio-win_Releases) * [3 Windows OS Versions](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#Windows_OS_Versions) * [4 Installation](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#Installation) * [4.1 Using the ISO](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#Using_the_ISO) * [4.1.1 Wizard Installation](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#Wizard_Installation) * [4.1.2 Manual Installation](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#Manual_Installation) * [4.2 Downloading the Wizard in the VM](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#Downloading_the_Wizard_in_the_VM) * [5 Troubleshooting](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#Troubleshooting) * [5.1 Known Issues](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#Known_Issues) * [5.1.1 0.1.285: VirtIO SCSI/VirtIO Block: Read errors and performance issues with IO-heavy Windows Server 2025 VMs](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#0.1.285:_VirtIO_SCSI/VirtIO_Block:_Read_errors_and_performance_issues_with_IO-heavy_Windows_Server_2025_VMs) * [5.1.2 0.1.215..0.1.262: VirtIO SCSI/VirtIO Block: "Reset to device was issued" events, blocked IO](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#0.1.215..0.1.262:_VirtIO_SCSI/VirtIO_Block:_%22Reset_to_device_was_issued%22_events,_blocked_IO) * [6 Further Reading](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#Further_Reading) * [7 See also](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#See_also) Introduction ------------ VirtIO Drivers are paravirtualized drivers for [kvm](https://pve.proxmox.com/mediawiki/index.php?title=KVM&action=edit&redlink=1 "KVM (page does not exist)") /Linux (see [http://www.linux-kvm.org/page/Virtio](http://www.linux-kvm.org/page/Virtio) ). In short, they enable direct (paravirtualized) access to devices and peripherals for virtual machines using them, instead of slower, emulated, ones. A quite extended explanation about VirtIO drivers can be found here: [http://www.ibm.com/developerworks/library/l-virtio](http://www.ibm.com/developerworks/library/l-virtio) . At the moment these kinds of devices are supported: * block (disk drives), see [Paravirtualized Block Drivers for Windows](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows "Paravirtualized Block Drivers for Windows") * network (ethernet cards), see [Paravirtualized Network Drivers for Windows](https://pve.proxmox.com/wiki/Paravirtualized_Network_Drivers_for_Windows "Paravirtualized Network Drivers for Windows") * balloon (dynamic memory management), see [Dynamic Memory Management](https://pve.proxmox.com/wiki/Dynamic_Memory_Management "Dynamic Memory Management") You can maximize performance by using VirtIO drivers. The availability and status of the VirtIO drivers depend on the guest OS and platform. virtio-win Releases ------------------- Windows does not have native support for VirtIO devices included. However, there is excellent external support through open-source drivers provided by the [virtio-win](https://virtio-win.github.io/) project, which are available compiled and signed for Windows. The virtio-win project periodically releases new versions of the virtio-win drivers. The following virtio-win repository provides the most recent as well as older versions of the virtio-win drivers: [https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/?C=M;O=D](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/?C=M;O=D) Currently, there are no known issues for version **virtio-win 0.1.271**. We recommend to test new versions in a testing environment with realistic workloads. Older virtio-win versions can be useful if a Windows VM shows instability or incompatibility with a newer driver version. See also [#Known Issues](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#Known_Issues) . Windows OS Versions ------------------- The virtio-win binary drivers are digitally signed by Red Hat and will work on 32-bit and 64-bit versions of Windows. Newer virtio-win versions may not contain drivers for older Windows OS versions, such as Windows 7. If you want to use VirtIO devices with older Windows versions, you may need to install an older version of the virtio-win drivers. Installation ------------ ### Using the ISO See [#virtio-win Releases](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#virtio-win_Releases) and [#Known Issues](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#Known_Issues) for download links and details on the recommended virtIO versions. You can access the ISO in a VM by mounting the ISO with a virtual CD-ROM/DVD drive on that VM. #### Wizard Installation [![](https://pve.proxmox.com/mediawiki/images/thumb/6/68/Win10-virtio-driver-wizard.png/600px-Win10-virtio-driver-wizard.png)](https://pve.proxmox.com/wiki/File:Win10-virtio-driver-wizard.png) Wizard Installation You can use an easy wizard to install all, or a selection, of VirtIO drivers. 1. Open the Windows Explorer and navigate to the CD-ROM drive. 2. Simply execute (double-click on) **virtio-win-gt-x64** 3. Follow its instructions. 4. (Optional) use the **virtio-win-guest-tools** wizard to install the [QEMU Guest Agent](https://pve.proxmox.com/wiki/Qemu-guest-agent "Qemu-guest-agent") and the [SPICE](https://pve.proxmox.com/wiki/SPICE "SPICE") agent for an improved remote-viewer experience. 5. Reboot VM #### Manual Installation 1. Open the Windows Explorer and navigate to the CD-ROM drive. There you can see that the ISO consists of several directories, each having sub-directories for supported OS versions (for example, 2k19, 2k12R2, w7, w8.1, w10, ...). * Balloon * guest-agent * NetKVM * qxl * vioscsi * ... [![](https://pve.proxmox.com/mediawiki/images/thumb/d/d3/Win10-virtio-driver-manual.png/600px-Win10-virtio-driver-manual.png)](https://pve.proxmox.com/wiki/File:Win10-virtio-driver-manual.png) Manual Installation 2. Navigate to the desired driver directories and respective Windows Version 3. Right-click on the file with type "Setup Information" 4. A context menu opens; select "Install" here. 5. Repeat that process for all desired drivers 6. Reboot VM. ### Downloading the Wizard in the VM You can also just download the `virtio-win-gt-x64.msi` or `virtio-win-gt-x86.msi` inside the VM, if you already have network access. Then just execute it and follow the installation process. Troubleshooting --------------- If you experience problems with the latest drivers, check below for reported issues or try using an older version. If that does not help, ask in one of our [support channels](https://pve.proxmox.com/wiki/Get_support "Get support") . ### Known Issues #### 0.1.285: VirtIO SCSI/VirtIO Block: Read errors and performance issues with IO-heavy Windows Server 2025 VMs Using VirtIO SCSI or VirtIO Block disks with virtio-win 0.1.285 for Windows Server 2025 VMs has been [reported](https://github.com/virtio-win/kvm-guest-drivers-windows/issues/1453) to cause read errors / performance issues when running IO-heavy workloads, particularly seen with a Microsoft SQL server. virtio-win 0.1.271 seems to be unaffected and could be used as a workaround. #### 0.1.215..0.1.262: VirtIO SCSI/VirtIO Block: "Reset to device was issued" events, blocked IO Starting from virtio-win version 0.1.215 up to 0.1.262 the following issues have been [reported](https://github.com/virtio-win/kvm-guest-drivers-windows/issues/756) when using VirtIO SCSI or VirtIO Block devices: * The Windows event viewer (run `eventvwr`) shows warnings mentioning `vioscsi`, Event ID 129, message `Reset to device, \Device\RaidPortN, was issued`. `N` corresponds to the LUN of the affected disk. After such a warning appears the first time, a warning can appear every minute. * IO on the affected disk may be blocked * In-guest rebooting the VM may get stuck (with a spinning wheel) * On the host, QEMU may log messages like `kvm: virtio: zero sized buffers are not allowed` or `kvm: Desc next is 3` Upgrading to a version 0.1.266 or later should resolve the problem. Further Reading --------------- [https://docs.fedoraproject.org/en-US/quick-docs/creating-windows-virtual-machines-using-virtio-drivers/index.html](https://docs.fedoraproject.org/en-US/quick-docs/creating-windows-virtual-machines-using-virtio-drivers/index.html) [http://www.linux-kvm.org/page/WindowsGuestDrivers](http://www.linux-kvm.org/page/WindowsGuestDrivers) The source code of those drivers can be found here: [https://github.com/virtio-win/kvm-guest-drivers-windows](https://github.com/virtio-win/kvm-guest-drivers-windows) [http://www.linux-kvm.org/page/WindowsGuestDrivers/Download\_Drivers](http://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers) See also ======== * [Paravirtualized Block Drivers for Windows](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows "Paravirtualized Block Drivers for Windows") * [Paravirtualized Network Drivers for Windows](https://pve.proxmox.com/wiki/Paravirtualized_Network_Drivers_for_Windows "Paravirtualized Network Drivers for Windows") * [Dynamic Memory Management](https://pve.proxmox.com/wiki/Dynamic_Memory_Management "Dynamic Memory Management") Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Windows\_VirtIO\_Drivers&oldid=12480](https://pve.proxmox.com/mediawiki/index.php?title=Windows_VirtIO_Drivers&oldid=12480) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Qemu/KVM](https://pve.proxmox.com/wiki/Category:Qemu/KVM "Category:Qemu/KVM") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # HTTPS Certificate Configuration (Version 4.x, 5.0 and 5.1) - Proxmox VE HTTPS Certificate Configuration (Version 4.x, 5.0 and 5.1) ========================================================== From Proxmox VE (Redirected from [HTTPS Certificate Configuration (Version 4.x and newer)](https://pve.proxmox.com/mediawiki/index.php?title=HTTPS_Certificate_Configuration_(Version_4.x_and_newer)&redirect=no "HTTPS Certificate Configuration (Version 4.x and newer)") ) [Jump to navigation](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#mw-head) [Jump to search](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#searchInput) ℹ️ **Note**: Article about old Proxmox VE 4.x, 5.0 and 5.1 releases. From Proxmox VE 5.2 this is part of the reference documentation see: [Certificate Management](https://pve.proxmox.com/wiki/Certificate_Management "Certificate Management") or [http://pve.proxmox.com/pve-docs/](http://pve.proxmox.com/pve-docs/) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#Introduction) * [2 Revert to default configuration](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#Revert_to_default_configuration) * [3 CAs other than Let's Encrypt](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#CAs_other_than_Let's_Encrypt) * [3.1 Install certificate chain and key](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#Install_certificate_chain_and_key) * [4 Let's Encrypt using acme.sh](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#Let's_Encrypt_using_acme.sh) * [4.1 Prerequisites](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#Prerequisites) * [4.2 Install certificate chain and key](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#Install_certificate_chain_and_key_2) * [4.2.1 0) Upgrade from le.sh to acme.sh](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#0)_Upgrade_from_le.sh_to_acme.sh) * [4.2.2 1) Install acme.sh](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#1)_Install_acme.sh) * [4.2.3 2) Run the install script](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#2)_Run_the_install_script) * [4.2.4 3) Check the account config](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#3)_Check_the_account_config) * [4.2.5 4) Make sure port 80 is open from the public](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#4)_Make_sure_port_80_is_open_from_the_public) * [4.2.6 5) Issue your first certificate](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#5)_Issue_your_first_certificate) * [4.2.7 6\. Check it's working](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#6._Check_it's_working) * [4.2.8 7\. Set up automatic renewal](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#7._Set_up_automatic_renewal) * [4.3 Updating acme.sh](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#Updating_acme.sh) * [4.4 Account key](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#Account_key) * [5 Let's Encrypt using eff.org's certbot](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#Let's_Encrypt_using_eff.org's_certbot) * [5.1 Installing certbot](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#Installing_certbot) * [5.2 Obtaining your certificate](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#Obtaining_your_certificate) * [5.3 Getting your certificate into Proxmox](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#Getting_your_certificate_into_Proxmox) * [5.4 Setting up renewal](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#Setting_up_renewal) * [6 Let's Encrypt using other Clients](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#Let's_Encrypt_using_other_Clients) Introduction ------------ This is a howto for changing the web server certificate used by Proxmox VE, in order to enable the usage of publicly trusted certificates issued by a CA of your choice (like Let's Encrypt or a commercial CA). It has been tested on a Proxmox VE 4.1 installation, using certificates from [https://www.letsencrypt.org](https://www.letsencrypt.org/) . _Note: the previous, outdated version of this HowTo is archived at [HTTPS Certificate Configuration (Version 3.x and earlier)](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_3.x_and_earlier) "HTTPS Certificate Configuration (Version 3.x and earlier)") _ Revert to default configuration ------------------------------- If you have used the previous HowTo and replaced any of the certificate or key files generated by PVE, you need to revert to the default state before proceeding. Delete or move the following files: * /etc/pve/pve-root-ca.pem * /etc/pve/priv/pve-root-ca.key * /etc/pve/nodes//pve-ssl.pem * /etc/pve/nodes//pve-ssl.key The latter two need to be repeated for all nodes if you have a cluster. Afterwards, run the following command on each node of the cluster to re-generate the certificates and keys: pvecm updatecerts -f CAs other than Let's Encrypt ---------------------------- ### Install certificate chain and key Since pve-manager 4.1-20, it is possible to provide alternative SSL files for each node's web interface. The following steps need to be repeated for each node where you want to use alternative certificate files. First check your version of pve-manager and upgrade if necessary: pveversion You will need the following two files provided by your CA: * fullchain.pem (your certificate and all intermediate certificates, excluding the root certificate, in PEM format) * private-key.pem (your private key, in PEM format, without a password) Now copy those files to the override locations in /etc/pve/nodes/ (make sure to use the correct certificate files and node!): cp fullchain.pem /etc/pve/nodes//pveproxy-ssl.pem cp private-key.pem /etc/pve/nodes//pveproxy-ssl.key and restart the web interface: systemctl restart pveproxy The system log should inform you about the usage of the alternative SSL certificate ("Using '/etc/pve/local/pveproxy-ssl.pem' as certificate for the web interface."): journalctl -b -u pveproxy.service When accessing the web interface on this node, you should be presented with the new certificate. Note that the alternative certificate is only used by the web interface (including noVNC), but not by the Spice Console/Shell. Let's Encrypt using acme.sh --------------------------- ### Prerequisites Let's Encrypt enables everyone with a publicly resolvable domain name to be issued SSL certificates for free. Your domain name needs to be publicly resolvable both ways. (Check with \`$ drill -x Your.Ip.Address\` or \`$ dig -x Your.Ip.Address\`) The following steps show how to achieve this using the acme.sh bash script and standalone HTTP authentication. These steps need to be repeated on each node where you want to use Let's Encrypt certificates. You need at least pve-manager >= 4.1-20 (see \`$ pveversion\`), so upgrade if necesasry. For some discussions and resolving non-mentioned problems see [https://forum.proxmox.com/threads/let%E2%80%99s-encrypt-with-proxmox-ve.26842/](https://forum.proxmox.com/threads/let%E2%80%99s-encrypt-with-proxmox-ve.26842/) ### Install certificate chain and key #### 0) Upgrade from le.sh to acme.sh If you followed a previous version of this HowTo using le.sh, please uninstall le.sh and proceed with "Install acme.sh": le.sh uninstall acme.sh is the 2.X release of le.sh, the existing configuration should be migrated automatically when installing acme.sh. #### 1) Install acme.sh Install the acme.sh script from [https://github.com/Neilpang/acme.sh](https://github.com/Neilpang/acme.sh) (this howto was tested with commit 2d39b3df8893cd256257fe1f32ca6b0485a90dcf): Via git: git clone [https://github.com/Neilpang/acme.sh.git](https://github.com/Neilpang/acme.sh.git) acme.sh-master Or direct download: wget '[https://github.com/Neilpang/acme.sh/archive/master.zip'](https://github.com/Neilpang/acme.sh/archive/master.zip') unzip master.zip #### 2) Run the install script You must do this from within the script's directory, otherwise it won't find acme.sh! Take care to replace $EMAIL with the address that you want to register with at Let's Encrypt. Let's Encrypt will send automatic expiration reminders to this address! mkdir /etc/pve/.le cd /root/acme.sh-master ./acme.sh --install --accountconf /etc/pve/.le/account.conf --accountkey /etc/pve/.le/account.key --accountemail "$EMAIL" After the installation, you need to close and reopen your shell (acme.sh is installed to ~/.acme.sh and sets up your shell's $PATH accordingly). #### 3) Check the account config Check the config file in /etc/pve/.le/account.conf and verify: * the ACCOUNT\_EMAIL variable should be set to your email address * the ACCOUNT\_KEY\_PATH variable should be set to "/etc/pve/.le/account.key" You can edit this file with your favourite text editor if either of those is incorrect. #### 4) Make sure port 80 is open from the public As part of the certificate creation process, acme.sh will listen for a confirmation from LetsEncrypt's servers on port 80. Check that this port is therefore not blocked by any firewall between the machine you are certifying and the public internet. You can close the port once you're done issuing all certificates for your cluster. However, be aware that as part of the certificate renewal process (managed with a cron job that acme.sh installs), port 80 must also be open. You may therefore need to work out an automated way (not covered in this guide) of opening up port 80 for the renewal process. #### 5) Issue your first certificate Now you can issue your first certificate, replacing $DOMAIN with your node's fully qualified domain: acme.sh --issue --standalone --keypath /etc/pve/local/pveproxy-ssl.key --fullchainpath /etc/pve/local/pveproxy-ssl.pem --reloadcmd "systemctl restart pveproxy" -d $DOMAIN Warnings like "cp: preserving permissions for ‘/etc/pve/local/pveproxy-ssl.pem.bak’: Function not implemented" can be safely ignored. By appending the previous command with \--test you can issue a certificate using the staging (i.e., testing) CA instead of the production CA: acme.sh --issue --standalone --keypath /etc/pve/local/pveproxy-ssl.key --fullchainpath /etc/pve/local/pveproxy-ssl.pem --reloadcmd "systemctl restart pveproxy" -d $DOMAIN --test To "upgrade" to a production certificate, you need to rerun the issue command with an appended \--force instead of \--test, in order to replace the existing (test) certificate even though it is not yet expired. This can also be used to force a premature renewal in case the node's domain name has changed: acme.sh --issue --standalone --keypath /etc/pve/local/pveproxy-ssl.key --fullchainpath /etc/pve/local/pveproxy-ssl.pem --reloadcmd "systemctl restart pveproxy" -d $DOMAIN --force #### 6\. Check it's working If necessary, close the firewall port again. The system log should inform you about the usage of the alternative SSL certificate ("Using '/etc/pve/local/pveproxy-ssl.pem' as certificate for the web interface."): journalctl -b -u pveproxy.service When accessing the web interface on this node, you should be presented with the new certificate. Note that the alternative certificate is only used by the web interface (including noVNC), but not by the Spice Console/Shell. #### 7\. Set up automatic renewal acme.sh installs a cron job that checks the installed certificate(s) and automatically renews them before they expire. The crontab entry should look like this (crontab -l): 0 0 \* \* \* "/root/.acme.sh"/acme.sh --cron --home "/root/.acme.sh" > /dev/null It's a good idea to test the cron entry by running it manually from the command line, just copy the following command (including the quotes): "/root/.acme.sh"/acme.sh --cron --home "/root/.acme.sh" NOTE: The requirements for issuing certificates apply for renewals as well: the configured domain name **must be resolvable and reachable on port 80 from the public internet when the renewal cron job runs**. ### Updating acme.sh acme.sh can be updated with the following commands when installed from the git repository: cd /root/acme.sh-master git pull ./acme.sh --install --accountconf /etc/pve/.le/account.conf --accountkey /etc/pve/.le/account.key --accountemail "YOUR@EMAIL.ADDRESS" ### Account key It is recommended to do an off-site/offline backup of the account key file in /etc/pve/.le/account.key, in case one of your certificate private key files is lost or compromised, it can be used to revoke the associated certificate. Let's Encrypt using eff.org's certbot ------------------------------------- ### Installing certbot certbot is packaged in Debian (the building base of Proxmox VE), so you may just install it with apt: apt install certbot If you run PVE 4.X (Debian Jessie) or run into any problems which are fixed by a newer version, you may enable the backports repository ( [http://backports.debian.org/Instructions/](http://backports.debian.org/Instructions/) ) and run: apt -t stretch-backports install certbot or respectively: apt -t jessie-backports install certbot ### Obtaining your certificate Just run the following command and follow the on screen output to obtain your certificate. certbot certonly ### Getting your certificate into Proxmox You need to copy the certificate from the LE directory to the PVE directory: cp /etc/letsencrypt/live//fullchain.pem /etc/pve/local/pveproxy-ssl.pem cp /etc/letsencrypt/live//privkey.pem /etc/pve/local/pveproxy-ssl.key Than restart the PVE proxy: systemctl restart pveproxy ### Setting up renewal Create a new bash script with the commands used to copy the certificate and restart the proxy from the previous step and make it executable, lets assume that you put it into /usr/local/bin/renew-pve-certs.sh Than edit your /etc/crontab with the editor your like and add the following line: 30 6 1,15 \* \* root /usr/bin/certbot renew --quiet --post-hook /usr/local/bin/renew-pve-certs.sh This will check two times each month (on the first and the 15th) at 06:30 AM if it needs to issue a new certificate. As certificates are valid for three months, this frequency should be high enough to ensure a certificate gets always renewed on time. Let's Encrypt using other Clients --------------------------------- It should also be possible to use other Let's Encrypt clients, as long as care is taken that the issued as well as renewed certificates and the associated keys are copied to the correct locations, and the pveproxy service is restarted afterwards. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=HTTPS\_Certificate\_Configuration\_(Version\_4.x,\_5.0\_and\_5.1)&oldid=10500](https://pve.proxmox.com/mediawiki/index.php?title=HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)&oldid=10500) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Proxmox VE 4.x](https://pve.proxmox.com/mediawiki/index.php?title=Category:Proxmox_VE_4.x&action=edit&redlink=1 "Category:Proxmox VE 4.x (page does not exist)") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Introduction - Proxmox VE Introduction ============ From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Introduction#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Introduction#searchInput) Proxmox VE is a platform to run virtual machines and containers. It is based on Debian Linux, and completely open source. For maximum flexibility, we implemented two virtualization technologies - Kernel-based Virtual Machine (KVM) and container-based virtualization (LXC). One main design goal was to make administration as easy as possible. You can use Proxmox VE on a single node, or assemble a cluster of many nodes. All management tasks can be done using our web-based management interface, and even a novice user can setup and install Proxmox VE within minutes. ![Proxmox Software Stack]() Central Management ------------------ While many people start with a single node, Proxmox VE can scale out to a large set of clustered nodes. The cluster stack is fully integrated and ships with the default installation. Unique Multi-Master Design The integrated web-based management interface gives you a clean overview of all your KVM guests and Linux containers and even of your whole cluster. You can easily manage your VMs and containers, storage or cluster from the GUI. There is no need to install a separate, complex, and pricey management server. Proxmox Cluster File System (pmxcfs) Proxmox VE uses the unique Proxmox Cluster file system (pmxcfs), a database-driven file system for storing configuration files. This enables you to store the configuration of thousands of virtual machines. By using corosync, these files are replicated in real time on all cluster nodes. The file system stores all data inside a persistent database on disk, nonetheless, a copy of the data resides in RAM which provides a maximum storage size of 30MB - more than enough for thousands of VMs. Proxmox VE is the only virtualization platform using this unique cluster file system. Web-based Management Interface Proxmox VE is simple to use. Management tasks can be done via the included web based management interface - there is no need to install a separate management tool or any additional management node with huge databases. The multi-master tool allows you to manage your whole cluster from any node of your cluster. The central web-based management - based on the JavaScript Framework (ExtJS) - empowers you to control all functionalities from the GUI and overview history and syslogs of each single node. This includes running backup or restore jobs, live-migration or HA triggered activities. Command Line For advanced users who are used to the comfort of the Unix shell or Windows Powershell, Proxmox VE provides a command-line interface to manage all the components of your virtual environment. This command-line interface has intelligent tab completion and full documentation in the form of UNIX man pages. REST API Proxmox VE uses a RESTful API. We choose JSON as primary data format, and the whole API is formally defined using JSON Schema. This enables fast and easy integration for third party management tools like custom hosting environments. Role-based Administration You can define granular access for all objects (like VMs, storages, nodes, etc.) by using the role based user- and permission management. This allows you to define privileges and helps you to control access to objects. This concept is also known as access control lists: Each permission specifies a subject (a user or group) and a role (set of privileges) on a specific path. Authentication Realms Proxmox VE supports multiple authentication sources like Microsoft Active Directory, LDAP, Linux PAM standard authentication or the built-in Proxmox VE authentication server. Flexible Storage ---------------- The Proxmox VE storage model is very flexible. Virtual machine images can either be stored on one or several local storages or on shared storage like NFS and on SAN. There are no limits, you may configure as many storage definitions as you like. You can use all storage technologies available for Debian Linux. One major benefit of storing VMs on shared storage is the ability to live-migrate running machines without any downtime, as all nodes in the cluster have direct access to VM disk images. We currently support the following Network storage types: * LVM Group (network backing with iSCSI targets) * iSCSI target * NFS Share * CIFS Share * Ceph RBD * CephFS * Directly use iSCSI LUNs or Fibre Attached SANs. Local storage types supported are: * LVM Group (local backing devices like block devices, FC devices, DRBD, etc.) * Directory (storage on existing filesystem) * ZFS Integrated Backup and Restore ----------------------------- The integrated backup tool (vzdump) creates consistent snapshots of running Containers and KVM guests. It basically creates an archive of the VM or CT data which includes the VM/CT configuration files. Additionally, the [Proxmox Backup Server integration](https://pve.proxmox.com/wiki/Storage:_Proxmox_Backup_Server#storage_pbs) provides advanced features, including the ability to combine full backups and data deduplication, perform client-side encryption, back up to tape or S3 object storage, and sync with other offsite Proxmox Backup Server installations. QEMU/KVM live backup works for all storage types including VM images on NFS, CIFS, iSCSI LUN, Ceph RBD. The new backup format is optimized for storing VM backups fast and effective (sparse files, out of order data, minimized I/O). High Availability Cluster ------------------------- A multi-node Proxmox VE HA Cluster enables the definition of highly available virtual servers. The Proxmox VE HA Cluster is based on proven Linux HA technologies, providing stable and reliable HA services. Flexible Networking ------------------- Proxmox VE uses a bridged networking model. All VMs can share one bridge as if virtual network cables from each guest were all plugged into the same switch. For connecting VMs to the outside world, bridges are attached to physical network cards and assigned a TCP/IP configuration. For further flexibility, VLANs (IEEE 802.1q) and network bonding/aggregation are possible. In this way it is possible to build complex, flexible virtual networks for the Proxmox VE hosts, leveraging the full power of the Linux network stack. Integrated Firewall ------------------- The integrated firewall allows you to filter network packets on any VM or Container interface. Common sets of firewall rules can be grouped into “security groups”. Hyper-converged Infrastructure ------------------------------ Proxmox VE is a virtualization platform that tightly integrates compute, storage and networking resources, manages highly available clusters, backup/restore as well as disaster recovery. All components are software-defined and compatible with one another. Therefore it is possible to administrate them like a single system via the centralized web management interface. These capabilities make Proxmox VE an ideal choice to deploy and manage an open source [hyper-converged infrastructure](https://en.wikipedia.org/wiki/Hyper-converged_infrastructure) . ### Benefits of a Hyper-Converged Infrastructure (HCI) with Proxmox VE A hyper-converged infrastructure (HCI) is especially useful for deployments in which a high infrastructure demand meets a low administration budget, for distributed setups such as remote and branch office environments or for virtual private and public clouds. HCI provides the following advantages: * Scalability: seamless expansion of compute, network and storage devices (i.e. scale up servers and storage quickly and independently from each other). * Low cost: Proxmox VE is open source and integrates all components you need such as compute, storage, networking, backup, and management center. It can replace an expensive compute/storage infrastructure. * Data protection and efficiency: services such as backup and disaster recovery are integrated. * Simplicity: easy configuration and centralized administration. * Open Source: No vendor lock-in. ### Hyper-Converged Infrastructure: Storage Proxmox VE has tightly integrated support for deploying a hyper-converged storage infrastructure. You can, for example, deploy and manage the following two storage technologies by using the web interface only: * **Ceph**: a both self-healing and self-managing shared, reliable and highly scalable storage system. Checkout [how to manage Ceph services on Proxmox VE nodes](https://pve.proxmox.com/wiki/Deploy_Hyper-Converged_Ceph_Cluster#chapter_pveceph) * **ZFS**: a combined file system and logical volume manager with extensive protection against data corruption, various RAID modes, fast and cheap snapshots - among other features. Find out [how to leverage the power of ZFS on Proxmox VE nodes](https://pve.proxmox.com/wiki/ZFS_on_Linux#chapter_zfs) . Besides above, Proxmox VE has support to integrate a wide range of additional storage technologies. You can find out about them in the [Storage Manager chapter](https://pve.proxmox.com/wiki/Storage#chapter_storage) . ### See Also * [pveceph - Manage Ceph Services on Proxmox VE Nodes](https://pve.proxmox.com/wiki/Deploy_Hyper-Converged_Ceph_Cluster#chapter_pveceph) Why Open Source --------------- Proxmox VE uses a Linux kernel and is based on the Debian GNU/Linux Distribution. The source code of Proxmox VE is released under the [GNU Affero General Public License, version 3](https://www.gnu.org/licenses/agpl-3.0.html) . This means that you are free to inspect the source code at any time or contribute to the project yourself. At Proxmox we are committed to use open source software whenever possible. Using open source software guarantees full access to all functionalities - as well as high security and reliability. We think that everybody should have the right to access the source code of a software to run it, build on it, or submit changes back to the project. Everybody is encouraged to contribute while Proxmox ensures the product always meets professional quality criteria. Open source software also helps to keep your costs low and makes your core infrastructure independent from a single vendor. Your benefits with Proxmox VE ----------------------------- * Open source software * No vendor lock-in * Linux kernel * Fast installation and easy-to-use * Web-based management interface * REST API * Huge active community * Low administration costs and simple deployment Getting Help ------------ ### Proxmox VE Wiki The primary source of information is the [Proxmox VE Wiki](https://pve.proxmox.com/wiki/) . It combines the reference documentation with user contributed content. ### Community Support Forum Proxmox VE itself is fully open source, so we always encourage our users to discuss and share their knowledge using the [Proxmox VE Community Forum](https://forum.proxmox.com/) . The forum is moderated by the Proxmox support team, and has a large user base from all around the world. Needless to say, such a large forum is a great place to get information. ### Mailing Lists This is a fast way to communicate with the Proxmox VE community via email. * Mailing list for users: [Proxmox VE User List](http://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user) Proxmox VE is fully open source and contributions are welcome! The primary communication channel for developers is the: * Mailing list for developers: [Proxmox VE development discussion](http://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel) ### Commercial Support Proxmox Server Solutions GmbH also offers enterprise support available as [Proxmox VE Subscription Service Plans](https://proxmox.com/en/proxmox-virtual-environment/pricing) . All users with a subscription get access to the Proxmox VE [Enterprise Repository](https://pve.proxmox.com/wiki/Package_Repositories#sysadmin_enterprise_repo) , and—with a Basic, Standard or Premium subscription—also to the Proxmox Customer Portal. The customer portal provides help and support with guaranteed response times from the Proxmox VE developers. For volume discounts, or more information in general, please contact [sales@proxmox.com](mailto:sales@proxmox.com) . ### Bug Tracker Proxmox runs a public bug tracker at [https://bugzilla.proxmox.com](https://bugzilla.proxmox.com/) . If an issue appears, file your report there. An issue can be a bug as well as a request for a new feature or enhancement. The bug tracker helps to keep track of the issue and will send a notification once it has been solved. Project History --------------- The project started in 2007, followed by a first stable version in 2008. At the time we used OpenVZ for containers, and QEMU with KVM for virtual machines. The clustering features were limited, and the user interface was simple (server generated web page). But we quickly developed new features using the [Corosync](https://corosync.github.io/corosync/) cluster stack, and the introduction of the new Proxmox cluster file system (pmxcfs) was a big step forward, because it completely hides the cluster complexity from the user. Managing a cluster of 16 nodes is as simple as managing a single node. The introduction of our new REST API, with a complete declarative specification written in JSON-Schema, enabled other people to integrate Proxmox VE into their infrastructure, and made it easy to provide additional services. Also, the new REST API made it possible to replace the original user interface with a modern client side single-page application using JavaScript. We also replaced the old Java based VNC console code with [noVNC](https://novnc.com/info.html) . So you only need a web browser to manage your VMs. The support for various storage types is another big task. Notably, Proxmox VE was the first distribution to ship [ZFS on Linux](https://zfsonlinux.org/) by default in 2014. Another milestone was the ability to run and manage [Ceph](https://ceph.com/) storage on the hypervisor nodes. Such setups are extremely cost effective. When our project started we were among the first companies providing commercial support for KVM. The KVM project itself continuously evolved, and is now a widely used hypervisor. New features arrive with each release. We developed the KVM live backup feature, which makes it possible to create snapshot backups on any storage type. The most notable change with version 4.0 was the move from OpenVZ to [LXC](https://linuxcontainers.org/) . Containers are now deeply integrated, and they can use the same storage and network features as virtual machines. At the same time we introduced the easy-to-use [High Availability (HA) manager](https://pve.proxmox.com/wiki/High_Availability#chapter_ha_manager) , simplifying the configuration and management of highly available setups. During the development of Proxmox VE 5 the asynchronous [storage replication](https://pve.proxmox.com/wiki/Storage_Replication#chapter_pvesr) as well as automated [certificate management](https://pve.proxmox.com/wiki/Certificate_Management#sysadmin_certificate_management) using ACME/Let’s Encrypt were introduced, among many other features. The [Software Defined Network (SDN)](https://pve.proxmox.com/wiki/Software-Defined_Network#chapter_pvesdn) stack was developed in cooperation with our community. It was integrated into the web interface as an experimental feature in version 6.2, simplifying the management of sophisticated network configurations. Since version 8.1, the SDN integration is fully supported and installed by default. 2020 marked the release of a new project, the [Proxmox Backup Server](https://www.proxmox.com/en/products/proxmox-backup-server/overview) , written in the Rust programming language. Proxmox Backup Server is deeply integrated with Proxmox VE and significantly improves backup capabilities by implementing incremental backups, deduplication, and much more. Another new tool, the [Proxmox Offline Mirror](https://pom.proxmox.com/) , was released in 2022, enabling subscriptions for systems which have no connection to the public internet. The highly requested dark theme for the web interface was introduced in 2023. Later that year, version 8.0 integrated access to the Ceph enterprise repository. Now access to the most stable Ceph repository comes with any Proxmox VE subscription. Automated and unattended installation for the official [ISO installer](https://pve.proxmox.com/wiki/Installation#installation_installer) was introduced in version 8.2, significantly simplifying large deployments of Proxmox VE. With the [import wizard](https://pve.proxmox.com/wiki/QEMU/KVM_Virtual_Machines#qm_import_virtual_machines) , equally introduced in version 8.2, users can easily and efficiently migrate guests directly from other hypervisors like VMware ESXi \[Migrate to Proxmox VE [https://pve.proxmox.com/wiki/Migrate\_to\_Proxmox\_VE](https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE)\ \] . Additionally, archives in Open Virtualization Format (OVF/OVA) can now be directly imported from file-based storages in the web interface. Improving the Proxmox VE Documentation -------------------------------------- Contributions and improvements to the Proxmox VE documentation are always welcome. There are several ways to contribute. If you find errors or other room for improvement in this documentation, please file a bug at the [Proxmox bug tracker](https://bugzilla.proxmox.com/) to propose a correction. If you want to propose new content, choose one of the following options: * The wiki: For specific setups, how-to guides, or tutorials the wiki is the right option to contribute. * The reference documentation: For general content that will be helpful to all users please propose your contribution for the reference documentation. This includes all information about how to install, configure, use, and troubleshoot Proxmox VE features. The reference documentation is written in the [asciidoc format](https://en.wikipedia.org/wiki/AsciiDoc) . To edit the documentation you need to clone the git repository at git://git.proxmox.com/git/pve-docs.git; then follow the [README.adoc](https://git.proxmox.com/?p=pve-docs.git;a=blob_plain;f=README.adoc;hb=HEAD) document. | | | | --- | --- | | ![Note]() | If you are interested in working on the Proxmox VE codebase, the [Developer Documentation](https://pve.proxmox.com/wiki/Developer_Documentation)
wiki article will show you where to start. | Translating Proxmox VE ---------------------- The Proxmox VE user interface is in English by default. However, thanks to the contributions of the community, translations to other languages are also available. We welcome any support in adding new languages, translating the latest features, and improving incomplete or inconsistent translations. We use [gettext](https://www.gnu.org/software/gettext/) for the management of the translation files. Tools like [Poedit](https://poedit.net/) offer a nice user interface to edit the translation files, but you can use whatever editor you’re comfortable with. No programming knowledge is required for translating. ### Translating with git The language files are available as a [git repository](https://git.proxmox.com/?p=proxmox-i18n.git) . If you are familiar with git, please contribute according to our [Developer Documentation](https://pve.proxmox.com/wiki/Developer_Documentation) . You can create a new translation by doing the following (replace with the language ID): \# git clone git://git.proxmox.com/git/proxmox-i18n.git # cd proxmox-i18n # make init-.po Or you can edit an existing translation, using the editor of your choice: \# poedit .po ### Translating without git Even if you are not familiar with git, you can help translate Proxmox VE. To start, you can download the language files [here](https://git.proxmox.com/?p=proxmox-i18n.git;a=tree) . Find the language you want to improve, then right click on the "raw" link of this language file and select _Save Link As…_. Make your changes to the file, and then send your final translation directly to office(at)proxmox.com, together with a signed [contributor license agreement](https://pve.proxmox.com/wiki/Developer_Documentation#Software_License_and_Copyright) . ### Testing the Translation In order for the translation to be used in Proxmox VE, you must first translate the .po file into a .js file. You can do this by invoking the following script, which is located in the same repository: \# ./po2js.pl -t pve xx.po >pve-lang-xx.js The resulting file pve-lang-xx.js can then be copied to the directory /usr/share/pve-i18n, on your proxmox server, in order to test it out. Alternatively, you can build a deb package by running the following command from the root of the repository: \# make deb | | | | --- | --- | | ![Important]() | For either of these methods to work, you need to have the following perl packages installed on your system. For Debian/Ubuntu: | \# apt-get install perl liblocale-po-perl libjson-perl ### Sending the Translation You can send the finished translation (.po file) to the Proxmox team at the address office(at)proxmox.com, along with a signed contributor license agreement. Alternatively, if you have some developer experience, you can send it as a patch to the Proxmox VE development mailing list. See [Developer Documentation](https://pve.proxmox.com/wiki/Developer_Documentation) . Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Introduction&oldid=12301](https://pve.proxmox.com/mediawiki/index.php?title=Introduction&oldid=12301) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Reference Documentation](https://pve.proxmox.com/wiki/Category:Reference_Documentation "Category:Reference Documentation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Install Proxmox VE on Debian Squeeze - Proxmox VE Install Proxmox VE on Debian Squeeze ==================================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze#searchInput) ℹ️ **Note**: Article about the old stable Proxmox VE 2.x releases Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze#Introduction) * [2 Install a standard Debian Squeeze(amd64)](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze#Install_a_standard_Debian_Squeeze(amd64)) * [3 Install Proxmox VE](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze#Install_Proxmox_VE) * [3.1 Adapt your sources.list](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze#Adapt_your_sources.list) * [3.2 Install Proxmox VE Kernel](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze#Install_Proxmox_VE_Kernel) * [3.3 Install Proxmox VE packages](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze#Install_Proxmox_VE_packages) * [4 Connect to the Proxmox VE web interface](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze#Connect_to_the_Proxmox_VE_web_interface) * [5 Optional: Developer Workstations with Proxmox VE and X11](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze#Optional:_Developer_Workstations_with_Proxmox_VE_and_X11) Introduction ------------ The installation of a supported Proxmox VE server should be done via [Bare-metal\_ISO\_Installer](https://pve.proxmox.com/mediawiki/index.php?title=Bare-metal_ISO_Installer&action=edit&redlink=1 "Bare-metal ISO Installer (page does not exist)") . In some case it makes sense to install Proxmox VE on top of a running Debian Squeeze 64-bit, especially if you want a custom partition layout. For this HowTO the following Debian Squeeze ISO was used: [PC Network Installer v6.0.7](http://cdimage.debian.org/debian-cd/6.0.7/amd64/iso-cd/debian-6.0.7-amd64-netinst.iso) . Suggested partition layout with LVM: Device Boot Start End Blocks Id System /dev/sda1 1 122 975872 83 Linux /dev/sda2 122 5222 40965120 8e Linux LVM LVM: LV VG Attr LSize Origin Snap% Move Log Copy% Convert data pve -wi-ao 30.69g root pve -wi-ao 3.72g swap pve -wi-ao 1.86g We recommend to use ext3 filesystem for best performance. Install a standard Debian Squeeze(amd64) ---------------------------------------- Install a standard Debian Squeeze (amd64), for details see [Debian](http://www.debian.org/) . Go for a LVM based partitioning and a fixed IP and take care that you have enough free space for snapshots (needed for online backup with vzdump) Please make sure that your hostname is resolvable via /etc/hosts, i.e you need an entry in /etc/hosts which assigns an IP address to that hostname. Install Proxmox VE ------------------ ### Adapt your sources.list Adapt your sources.list and add the Proxmox VE repository: nano /etc/apt/sources.list deb http://ftp.at.debian.org/debian squeeze main contrib # PVE packages provided by proxmox.com deb http://download.proxmox.com/debian squeeze pve # security updates deb http://security.debian.org/ squeeze/updates main contrib a. Add the Proxmox VE repository key b. Update your repository and system wget -O- "http://download.proxmox.com/debian/key.asc" | apt-key add - aptitude update aptitude full-upgrade ### Install Proxmox VE Kernel aptitude install pve-firmware aptitude install pve-kernel-2.6.32-19-pve Reboot and make sure to select Proxmox VE Kernel on the boot loader (grub2). reboot Optional - install Kernel headers: aptitude install pve-headers-2.6.32-19-pve ### Install Proxmox VE packages Make sure you are running the Proxmox VE Kernel, otherwise the installation will fail. Check the currently active Kernel: uname -a Linux 2.6.32-19-pve ... a. Install the Proxmox VE packages b. Configure pve-redirect for apache2 c. And restart apache aptitude install proxmox-ve-2.6.32 a2ensite pve-redirect.conf /etc/init.d/apache2 restart Install the rest of needed packages: aptitude install ntp ssh lvm2 postfix ksm-control-daemon vzprocps open-iscsi Accept the suggestion to remove Exim and configure postfix according to your network. Connect to the Proxmox VE web interface --------------------------------------- Connect to the admin web interface (https://youripaddress:8006) and configure the vmbr0 and review all other settings, finally reboot to check if everything is running as expected. [![Adapt vmbr0 settings](https://pve.proxmox.com/mediawiki/images/b/ba/Screen-vmbr0-setup-for-pve2.png)](https://pve.proxmox.com/wiki/File:Screen-vmbr0-setup-for-pve2.png "Adapt vmbr0 settings") Optional: Developer Workstations with Proxmox VE and X11 -------------------------------------------------------- Proxmox VE is primarily used as virtualization platform with NO additional software installed. In some case it makes sense to have a full desktop running on Proxmox VE, for example for developers using Proxmox VE as their primary workstation/desktop. For example, just install lxde desktop: aptitude install lxde libcurl3 Make sure network-manager is not used, else pve-cluster will not start aptitude purge network-manager To get a modern browser, Google Chrome is a good idea - download the 64-bit Chrome from Google, also install Oracle (Sun) Java, see [Java\_Console\_(Ubuntu)](https://pve.proxmox.com/wiki/Java_Console_(Ubuntu) "Java Console (Ubuntu)") Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Install\_Proxmox\_VE\_on\_Debian\_Squeeze&oldid=10542](https://pve.proxmox.com/mediawiki/index.php?title=Install_Proxmox_VE_on_Debian_Squeeze&oldid=10542) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Archive](https://pve.proxmox.com/wiki/Category:Archive "Category:Archive") * [Installation](https://pve.proxmox.com/wiki/Category:Installation "Category:Installation") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Migrate to Proxmox VE" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Migrate to Proxmox VE" ========================================== ← [Migrate to Proxmox VE](https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE "Migrate to Proxmox VE") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Migrate_to_Proxmox_VE#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Migrate_to_Proxmox_VE#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Migrate to Proxmox VE](https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE "Migrate to Proxmox VE") **: Displaying 5 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Migrate_to_Proxmox_VE&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Migrate_to_Proxmox_VE&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Migrate_to_Proxmox_VE&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Migrate_to_Proxmox_VE&limit=500) ) * [Main Page](https://pve.proxmox.com/wiki/Main_Page "Main Page") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Main+Page "Special:WhatLinksHere") ) * [Migration of servers to Proxmox VE](https://pve.proxmox.com/mediawiki/index.php?title=Migration_of_servers_to_Proxmox_VE&redirect=no "Migration of servers to Proxmox VE") (redirect page) ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Migration+of+servers+to+Proxmox+VE "Special:WhatLinksHere") ) * [Advanced Migration Techniques to Proxmox VE](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE "Advanced Migration Techniques to Proxmox VE") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Advanced+Migration+Techniques+to+Proxmox+VE "Special:WhatLinksHere") ) * [Additional ways to migrate to Proxmox VE](https://pve.proxmox.com/wiki/Additional_ways_to_migrate_to_Proxmox_VE "Additional ways to migrate to Proxmox VE") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Additional+ways+to+migrate+to+Proxmox+VE "Special:WhatLinksHere") ) * [Migrate to Proxmox VE](https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE "Migrate to Proxmox VE") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Migrate+to+Proxmox+VE "Special:WhatLinksHere") ) * [Advanced Migration Techniques to Proxmox VE](https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE "Advanced Migration Techniques to Proxmox VE") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Advanced+Migration+Techniques+to+Proxmox+VE "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Migrate_to_Proxmox_VE&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Migrate_to_Proxmox_VE&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Migrate_to_Proxmox_VE&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Migrate_to_Proxmox_VE&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Migrate\_to\_Proxmox\_VE](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Migrate_to_Proxmox_VE) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Cluster Manager" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Cluster Manager" ==================================== ← [Cluster Manager](https://pve.proxmox.com/wiki/Cluster_Manager "Cluster Manager") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Cluster_Manager#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Cluster_Manager#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go The following pages link to **[Cluster Manager](https://pve.proxmox.com/wiki/Cluster_Manager "Cluster Manager") **: Displaying 5 items. View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Cluster_Manager&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Cluster_Manager&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Cluster_Manager&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Cluster_Manager&limit=500) ) * [Main Page](https://pve.proxmox.com/wiki/Main_Page "Main Page") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Main+Page "Special:WhatLinksHere") ) * [Quick installation](https://pve.proxmox.com/wiki/Quick_installation "Quick installation") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Quick+installation "Special:WhatLinksHere") ) * [Proxmox VE Cluster](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_VE_Cluster&redirect=no "Proxmox VE Cluster") (redirect page) ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Proxmox+VE+Cluster "Special:WhatLinksHere") ) * [User:Grin/Debian](https://pve.proxmox.com/wiki/User:Grin/Debian "User:Grin/Debian") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=User%3AGrin%2FDebian "Special:WhatLinksHere") ) * [Proxmox VE 4.x Cluster](https://pve.proxmox.com/wiki/Proxmox_VE_4.x_Cluster "Proxmox VE 4.x Cluster") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Proxmox+VE+4.x+Cluster "Special:WhatLinksHere") ) * [Full Mesh Network for Ceph Server](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server "Full Mesh Network for Ceph Server") ([← links](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere&target=Full+Mesh+Network+for+Ceph+Server "Special:WhatLinksHere") ) View (previous 50 | next 50) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Cluster_Manager&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Cluster_Manager&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Cluster_Manager&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:WhatLinksHere/Cluster_Manager&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Cluster\_Manager](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Cluster_Manager) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Windows 2012 guest best practices - Proxmox VE Windows 2012 guest best practices ================================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices#Introduction) * [2 Install](https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices#Install) * [2.1 Prepare](https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices#Prepare) * [2.2 Launch Windows install](https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices#Launch_Windows_install) * [3 Install Guest Agent and Services](https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices#Install_Guest_Agent_and_Services) * [3.1 Guest Agent](https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices#Guest_Agent) * [3.2 Drivers and Services](https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices#Drivers_and_Services) * [3.3 Check for missing drivers](https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices#Check_for_missing_drivers) * [3.4 Installing WSL(g)](https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices#Installing_WSL(g)) * [4 Further Information](https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices#Further_Information) * [4.1 RAW vs QCOW2](https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices#RAW_vs_QCOW2) * [4.2 VirtIO Drivers](https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices#VirtIO_Drivers) * [5 See also](https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices#See_also) Introduction ------------ This is a set of best practices to follow when installing a Windows Server 2012(R2) guest on a Proxmox VE server 6.x. Install ------- ### Prepare To obtain a good level of performance, we will install the [Windows VirtIO Drivers](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers "Windows VirtIO Drivers") during the Windows installation. * Create a new VM, select "Microsoft Windows 8.x/2012/2012r2" as Guest OS and enable the "Qemu Agent" in the System tab. Continue and mount your Windows Server 2012 ISO in the CDROM drive * For your virtual hard disk select "SCSI" as bus with "VirtIO SCSI single" as controller. Set "Write back" as cache option for best performance (the "No cache" default [is safer, but slower](https://pve.proxmox.com/wiki/Performance_Tweaks#Disk_Cache "Performance Tweaks") ) and tick "Discard" to optimally use disk space (TRIM). For the best performance, also make sure that IO Thread is enabled. * Configure your memory settings as needed, continue and set "VirtIO (paravirtualized)" as network device, finish your VM creation. * For the VirtIO drivers, upload the driver ISO (see [Windows VirtIO Drivers#virtio-win Releases](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#virtio-win_Releases "Windows VirtIO Drivers") for information on how to download it) to your storage, create a new CDROM drive (use "Add -> CD/DVD drive" in the hardware tab) **with Bus "IDE" and number 0**. Load the Virtio Drivers ISO in the new virtual CDROM drive. * Now your ready to start the VM, just follow the Windows installer. * Note for Older Version of Windows like Windows-2012 (use the stable older version of VirtIO ISO - virtio-win-0.1.189.iso, [download it from here](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.189-1/virtio-win-0.1.189.iso) ) ### Launch Windows install * After starting your VM launch the noVNC console * Follow the installer steps until you reach the installation type selection where you need to select "Custom (advanced)" * Now click "Load driver" to install the VirtIO drivers for hard disk and the network. * Hard disk: Browse to the CD drive where you mounted the VirtIO driver and select folder "vioscsi\\2k12\\amd64" and confirm. Select the "Red Hat VirtIO SCSI pass-through controller" and click next to install it. Now you should see your drive. * Network: Repeat the steps from above (click again "Load driver", etc.) and select the folder "NetKVM\\2k12\\amd64", confirm it and select "Redhat VirtIO Ethernet Adapter" and click next. * Memory Ballooning: Again, repeat the steps but this time select the "Balloon\\2k12\\amd64" folder, then the "VirtIO Balloon Driver" and install it by clicking next. With these three drivers you should be good covered to run a fast virtualized Windows Server 2012 system. * Choose the drive and continue the Windows installer steps. **HINT:** There is a [video showing the process](https://www.proxmox.com/en/services/training-courses/videos/proxmox-virtual-environment/install-windows-2016-server-on-proxmox-ve) for a Windows Server 2016 installation which is the same as for Windows Server 2012. Install Guest Agent and Services -------------------------------- ### Guest Agent If you enabled the Qemu Agent option for the VM the mouse pointer will probably be off after the first boot. To remedy this install the "Qemu Guest Agent". The installer is located on the driver CD under guest-agent\\qemu-ga-x86\_64.msi. ### Drivers and Services [![](https://pve.proxmox.com/mediawiki/images/thumb/f/fd/Win10_virtio_guest_tool_installer.png/400px-Win10_virtio_guest_tool_installer.png)](https://pve.proxmox.com/wiki/File:Win10_virtio_guest_tool_installer.png) VirtIO guest tools installer The easiest way to install missing drivers and services is to use the provided MSI installer. It is available on the driver CD since version 0.1.173-2. Run the "virtio-win-gt-x64.msi" file located directly on the CD. If you do not plan to use [SPICE](https://pve.proxmox.com/wiki/SPICE "SPICE") you can deselect the "Qxl" and "Spice" features. Restart the VM after the installer is done. After all this the RAM usage and IP configuration should be shown correctly in the summary page of the VM. For more information and configuration about ballooning, see [Dynamic Memory Management](https://pve.proxmox.com/wiki/Dynamic_Memory_Management "Dynamic Memory Management") ### Check for missing drivers _See also: [Paravirtualized Block Drivers for Windows](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows "Paravirtualized Block Drivers for Windows") _ [![](https://pve.proxmox.com/mediawiki/images/thumb/9/9c/Win10_unknown_dev.png/400px-Win10_unknown_dev.png)](https://pve.proxmox.com/wiki/File:Win10_unknown_dev.png) Unknown device in device manager [![](https://pve.proxmox.com/mediawiki/images/thumb/5/5e/Win10_update_driver_cd_selection.png/400px-Win10_update_driver_cd_selection.png)](https://pve.proxmox.com/wiki/File:Win10_update_driver_cd_selection.png) Make sure to include subfolders Go to the Device Manager to see if there are any drivers missing. For any unknown device: * Right click an select "Update driver". * Select "Browse my computer for driver software". * Select the Driver CD. Make sure that "Include subfolders" is checked. * Once a driver has been found you might be prompted with a security warning asking if you "Would like to install this device software". Click "Install". ### Installing WSL(g) To run WSL (Windows Subsystem for Linux) you need to enable [Nested Virtualization](https://pve.proxmox.com/wiki/Nested_Virtualization "Nested Virtualization") . Make sure to set your processor to 'host'; if you already set up your VM and did not select 'host' as processor, you can change it in the 'Hardware' section of your VM in the web interface. Follow the [official instructions](https://learn.microsoft.com/en-us/windows/wsl/install) . If you are using a GPU via PCI(e) passthrough, you might need to add args: -cpu host,kvm=off to your config file at _/etc/pve/qemu-server/.conf_, see [the vfio blog](http://vfio.blogspot.com/2014/08/vfiovga-faq.html) Further Information ------------------- ### RAW vs QCOW2 The RAW file format provides slightly better performance WHILE qcow2 offers advanced features such as copy on write and [Live\_Snapshots](https://pve.proxmox.com/wiki/Live_Snapshots "Live Snapshots") independent of the backing storage. Since Proxmox VE version 2.3, qcow2 is the default format. ### VirtIO Drivers Make it really easy:Build your ISO with drivers already included: [Windows guests - build ISOs including VirtIO drivers](https://pve.proxmox.com/wiki/Windows_guests_-_build_ISOs_including_VirtIO_drivers "Windows guests - build ISOs including VirtIO drivers") See also -------- [Windows 2003 guest best practices](https://pve.proxmox.com/wiki/Windows_2003_guest_best_practices "Windows 2003 guest best practices") [Windows 2008 guest best practices](https://pve.proxmox.com/wiki/Windows_2008_guest_best_practices "Windows 2008 guest best practices") Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Windows\_2012\_guest\_best\_practices&oldid=12487](https://pve.proxmox.com/mediawiki/index.php?title=Windows_2012_guest_best_practices&oldid=12487) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Qemu/KVM](https://pve.proxmox.com/wiki/Category:Qemu/KVM "Category:Qemu/KVM") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Windows 2019 guest best practices - Proxmox VE Windows 2019 guest best practices ================================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Windows_2019_guest_best_practices#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Windows_2019_guest_best_practices#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Windows_2019_guest_best_practices#Introduction) * [2 Install](https://pve.proxmox.com/wiki/Windows_2019_guest_best_practices#Install) * [2.1 Prepare](https://pve.proxmox.com/wiki/Windows_2019_guest_best_practices#Prepare) * [2.2 Launch Windows install](https://pve.proxmox.com/wiki/Windows_2019_guest_best_practices#Launch_Windows_install) * [3 Install Guest Agent and Services](https://pve.proxmox.com/wiki/Windows_2019_guest_best_practices#Install_Guest_Agent_and_Services) * [3.1 Guest Agent](https://pve.proxmox.com/wiki/Windows_2019_guest_best_practices#Guest_Agent) * [3.2 Drivers and Services](https://pve.proxmox.com/wiki/Windows_2019_guest_best_practices#Drivers_and_Services) * [3.3 Check for missing drivers](https://pve.proxmox.com/wiki/Windows_2019_guest_best_practices#Check_for_missing_drivers) * [3.4 Installing WSL(g)](https://pve.proxmox.com/wiki/Windows_2019_guest_best_practices#Installing_WSL(g)) * [4 Further information](https://pve.proxmox.com/wiki/Windows_2019_guest_best_practices#Further_information) * [4.1 Disk-Image Format: raw vs qcow2](https://pve.proxmox.com/wiki/Windows_2019_guest_best_practices#Disk-Image_Format:_raw_vs_qcow2) * [4.2 VirtIO drivers](https://pve.proxmox.com/wiki/Windows_2019_guest_best_practices#VirtIO_drivers) * [5 See also](https://pve.proxmox.com/wiki/Windows_2019_guest_best_practices#See_also) Introduction ------------ This is a set of best practices to follow when installing a Windows Server 2019 guest on a Proxmox VE server 6.x. Install ------- ### Prepare To obtain a good level of performance, we will install the [Windows VirtIO Drivers](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers "Windows VirtIO Drivers") during the Windows installation. * Create a new VM, select "Microsoft Windows 10/2016/2019" as Guest OS and enable the "Qemu Agent" in the System tab. Continue and mount your Windows Server 2019 ISO in the CDROM drive * For your virtual hard disk select "SCSI" as bus with "VirtIO SCSI single" as controller. Set "Write back" as cache option for best performance (the "No cache" default [is safer, but slower](https://pve.proxmox.com/wiki/Performance_Tweaks#Disk_Cache "Performance Tweaks") ) and tick "Discard" to optimally use disk space (TRIM). For the best performance, also make sure that IO Thread is enabled. * Configure your memory settings as needed, continue and set "VirtIO (paravirtualized)" as network device, finish your VM creation. * For the VirtIO drivers, upload the driver ISO (see [Windows VirtIO Drivers#virtio-win Releases](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#virtio-win_Releases "Windows VirtIO Drivers") for information on how to download it) to your storage, create a new CDROM drive (use "Add -> CD/DVD drive" in the hardware tab) **with Bus "IDE" and number 0**. Load the Virtio Drivers ISO in the new virtual CDROM drive. * Now your ready to start the VM, just follow the Windows installer. * Note for Older Version of Windows like Windows-2012 (use the stable older version of VirtIO ISO - virtio-win-0.1.189.iso, [download it from here](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.189-1/virtio-win-0.1.189.iso) ) ### Launch Windows install * After starting your VM launch the noVNC console * Follow the installer steps until you reach the installation type selection where you need to select "Custom (advanced)" * Now click "Load driver" to install the VirtIO drivers for hard disk and the network. * Hard disk: Browse to the CD drive where you mounted the VirtIO driver and select folder "vioscsi\\2k19\\amd64" and confirm. Select the "Red Hat VirtIO SCSI pass-through controller" and click next to install it. Now you should see your drive. * Network: Repeat the steps from above (click again "Load driver", etc.) and select the folder "NetKVM\\2k19\\amd64", confirm it and select "Redhat VirtIO Ethernet Adapter" and click next. * Memory Ballooning: Again, repeat the steps but this time select the "Balloon\\2k19\\amd64" folder, then the "VirtIO Balloon Driver" and install it by clicking next. With these three drivers you should be good covered to run a fast virtualized Windows Server 2019 system. * Choose the drive and continue the Windows installer steps. **HINT:** There is a [video showing the process](https://www.proxmox.com/en/services/training-courses/videos/proxmox-virtual-environment/install-windows-2016-server-on-proxmox-ve) for a Windows Server 2016 installation which is the same as for Windows Server 2019. Install Guest Agent and Services -------------------------------- ### Guest Agent If you enabled the Qemu Agent option for the VM the mouse pointer will probably be off after the first boot. To remedy this install the "Qemu Guest Agent". The installer is located on the driver CD under guest-agent\\qemu-ga-x86\_64.msi. ### Drivers and Services [![](https://pve.proxmox.com/mediawiki/images/thumb/f/fd/Win10_virtio_guest_tool_installer.png/400px-Win10_virtio_guest_tool_installer.png)](https://pve.proxmox.com/wiki/File:Win10_virtio_guest_tool_installer.png) VirtIO guest tools installer The easiest way to install missing drivers and services is to use the provided MSI installer. It is available on the driver CD since version 0.1.173-2. Run the "virtio-win-gt-x64.msi" file located directly on the CD. If you do not plan to use [SPICE](https://pve.proxmox.com/wiki/SPICE "SPICE") you can deselect the "Qxl" and "Spice" features. Restart the VM after the installer is done. After all this the RAM usage and IP configuration should be shown correctly in the summary page of the VM. For more information and configuration about ballooning, see [Dynamic Memory Management](https://pve.proxmox.com/wiki/Dynamic_Memory_Management "Dynamic Memory Management") ### Check for missing drivers _See also: [Paravirtualized Block Drivers for Windows](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows "Paravirtualized Block Drivers for Windows") _ [![](https://pve.proxmox.com/mediawiki/images/thumb/9/9c/Win10_unknown_dev.png/400px-Win10_unknown_dev.png)](https://pve.proxmox.com/wiki/File:Win10_unknown_dev.png) Unknown device in device manager [![](https://pve.proxmox.com/mediawiki/images/thumb/5/5e/Win10_update_driver_cd_selection.png/400px-Win10_update_driver_cd_selection.png)](https://pve.proxmox.com/wiki/File:Win10_update_driver_cd_selection.png) Make sure to include subfolders Go to the Device Manager to see if there are any drivers missing. For any unknown device: * Right click an select "Update driver". * Select "Browse my computer for driver software". * Select the Driver CD. Make sure that "Include subfolders" is checked. * Once a driver has been found you might be prompted with a security warning asking if you "Would like to install this device software". Click "Install". ### Installing WSL(g) To run WSL (Windows Subsystem for Linux) you need to enable [Nested Virtualization](https://pve.proxmox.com/wiki/Nested_Virtualization "Nested Virtualization") . Make sure to set your processor to 'host'; if you already set up your VM and did not select 'host' as processor, you can change it in the 'Hardware' section of your VM in the web interface. Follow the [official instructions](https://learn.microsoft.com/en-us/windows/wsl/install) . If you are using a GPU via PCI(e) passthrough, you might need to add args: -cpu host,kvm=off to your config file at _/etc/pve/qemu-server/.conf_, see [the vfio blog](http://vfio.blogspot.com/2014/08/vfiovga-faq.html) Further information ------------------- ### Disk-Image Format: raw vs qcow2 Raw file format provides slightly better performance while qcow2 offers advanced features such as copy on write and [Live\_Snapshots](https://pve.proxmox.com/wiki/Live_Snapshots "Live Snapshots") . Since V2.3, qcow2 is the default format. ### VirtIO drivers Make it really easy: Build your ISO with drivers already included: [Windows guests - build ISOs including VirtIO drivers](https://pve.proxmox.com/wiki/Windows_guests_-_build_ISOs_including_VirtIO_drivers "Windows guests - build ISOs including VirtIO drivers") See also -------- [Windows 2016 guest best practices](https://pve.proxmox.com/wiki/Windows_2016_guest_best_practices "Windows 2016 guest best practices") [Windows 10 guest best practices](https://pve.proxmox.com/wiki/Windows_10_guest_best_practices "Windows 10 guest best practices") Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Windows\_2019\_guest\_best\_practices&oldid=12483](https://pve.proxmox.com/mediawiki/index.php?title=Windows_2019_guest_best_practices&oldid=12483) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # PCI Passthrough - Proxmox VE PCI Passthrough =============== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/PCI_Passthrough#mw-head) [Jump to search](https://pve.proxmox.com/wiki/PCI_Passthrough#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/PCI_Passthrough#Introduction) * [2 Requirements](https://pve.proxmox.com/wiki/PCI_Passthrough#Requirements) * [3 Verifying IOMMU parameters](https://pve.proxmox.com/wiki/PCI_Passthrough#Verifying_IOMMU_parameters) * [3.1 Verify IOMMU is enabled](https://pve.proxmox.com/wiki/PCI_Passthrough#Verify_IOMMU_is_enabled) * [3.2 Verify IOMMU interrupt remapping is enabled](https://pve.proxmox.com/wiki/PCI_Passthrough#Verify_IOMMU_interrupt_remapping_is_enabled) * [3.3 Verify IOMMU isolation](https://pve.proxmox.com/wiki/PCI_Passthrough#Verify_IOMMU_isolation) * [4 GPU passthrough](https://pve.proxmox.com/wiki/PCI_Passthrough#GPU_passthrough) * [4.1 Blacklisting drivers](https://pve.proxmox.com/wiki/PCI_Passthrough#Blacklisting_drivers) * [4.2 How to know if a graphics card is UEFI (OVMF) compatible](https://pve.proxmox.com/wiki/PCI_Passthrough#How_to_know_if_a_graphics_card_is_UEFI_(OVMF)_compatible) * [4.3 The 'romfile' option](https://pve.proxmox.com/wiki/PCI_Passthrough#The_'romfile'_option) * [4.4 Tips](https://pve.proxmox.com/wiki/PCI_Passthrough#Tips) * [4.4.1 Nvidia Tips](https://pve.proxmox.com/wiki/PCI_Passthrough#Nvidia_Tips) * [5 Troubleshooting](https://pve.proxmox.com/wiki/PCI_Passthrough#Troubleshooting) * [5.1 "BAR 3: can't reserve \[mem\]" error](https://pve.proxmox.com/wiki/PCI_Passthrough#%22BAR_3:_can't_reserve_[mem]%22_error) * [5.2 "BAR0 is 0M" error or Windows Code 12 Error](https://pve.proxmox.com/wiki/PCI_Passthrough#%22BAR0_is_0M%22_error_or_Windows_Code_12_Error) * [5.3 WSLg (Windows Subsystem for Linux GUI)](https://pve.proxmox.com/wiki/PCI_Passthrough#WSLg_(Windows_Subsystem_for_Linux_GUI)) * [5.4 Black display in NoVNC/Spice](https://pve.proxmox.com/wiki/PCI_Passthrough#Black_display_in_NoVNC/Spice) * [5.5 Spice](https://pve.proxmox.com/wiki/PCI_Passthrough#Spice) * [5.6 HDMI audio crackling/broken](https://pve.proxmox.com/wiki/PCI_Passthrough#HDMI_audio_crackling/broken) * [5.7 BIOS options](https://pve.proxmox.com/wiki/PCI_Passthrough#BIOS_options) * [5.8 Error 43](https://pve.proxmox.com/wiki/PCI_Passthrough#Error_43) * [5.8.1 Finding out if the PCI device has a hardware fault](https://pve.proxmox.com/wiki/PCI_Passthrough#Finding_out_if_the_PCI_device_has_a_hardware_fault) * [5.8.2 Finding software issues](https://pve.proxmox.com/wiki/PCI_Passthrough#Finding_software_issues) * [5.8.3 Nvidia specific issues](https://pve.proxmox.com/wiki/PCI_Passthrough#Nvidia_specific_issues) * [5.8.4 AMD specific issues](https://pve.proxmox.com/wiki/PCI_Passthrough#AMD_specific_issues) * [6 USB passthrough](https://pve.proxmox.com/wiki/PCI_Passthrough#USB_passthrough) * [7 vGPU](https://pve.proxmox.com/wiki/PCI_Passthrough#vGPU) Introduction ------------ ℹ️ **Note**: This is a collection of examples, workarounds, hacks, and specific issues for PCI(e) passthrough. For a step-by-step guide on how and what to do to pass through PCI(e) devices, see [the docs](https://pve.proxmox.com/pve-docs/pve-admin-guide.html#qm_pci_passthrough) or [the wiki page generated from the docs](https://pve.proxmox.com/wiki/PCI(e)_Passthrough "PCI(e) Passthrough") PCI passthrough allows you to use a physical PCI device (graphics card, network card) inside a VM (KVM virtualization only). If you "PCI passthrough" a device, the device is not available to the host anymore. Note that VMs with passed-through devices cannot be migrated. Requirements ------------ This is a list of basic requirements adapted from [the Arch wiki](https://wiki.archlinux.org/title/PCI_passthrough_via_OVMF#Prerequisites) CPU requirements Your CPU has to support hardware virtualization and IOMMU. Most new CPUs support this. * AMD: CPUs from the Bulldozer generation and newer, CPUs from the K10 generation need a 890FX or 990FX motherboard. * Intel: [list of VT-d capable Intel CPUs](https://ark.intel.com/content/www/us/en/ark/search/featurefilter.html?productType=873&0_VTD=True) Motherboard requirements Your motherboard needs to support IOMMU. Lists can be found on [the Xen wiki](https://wiki.xenproject.org/wiki/VTd_HowTo) and [Wikipedia](https://en.wikipedia.org/wiki/List_of_IOMMU-supporting_hardware) . Note that, as of writing, both these lists are incomplete and very out-of-date and most newer motherboards support IOMMU. GPU requirements The ROM of your GPU does not necessarily need to support UEFI, however, most modern GPUs do. If you GPU ROM supports UEFI, it is recommended to use OVMF (UEFI) instead of SeaBIOS. For a list of GPU ROMs, see [Techpowerup's collection of GPU ROMs](https://www.techpowerup.com/vgabios/?architecture=&manufacturer=&model=&version=&interface=&memType=&memSize=&since=) Verifying IOMMU parameters -------------------------- ### Verify IOMMU is enabled Reboot, then run: dmesg | grep -e DMAR -e IOMMU There should be a line that looks like "DMAR: IOMMU enabled". If there is no output, something is wrong. ### Verify IOMMU interrupt remapping is enabled It is not possible to use PCI passthrough without interrupt remapping. Device assignment will fail with 'Failed to assign device "\[device name\]": Operation not permitted' or 'Interrupt Remapping hardware not found, passing devices to unprivileged domains is insecure.'. All systems using an Intel processor and chipset that have support for Intel Virtualization Technology for Directed I/O (VT-d), but do not have support for interrupt remapping will see such an error. Interrupt remapping support is provided in newer processors and chipsets (both AMD and Intel). To identify if your system has support for interrupt remapping: dmesg | grep 'remapping' If you see one of the following lines: * `AMD-Vi: Interrupt remapping enabled` * `DMAR-IR: Enabled IRQ remapping in x2apic mode` ('x2apic' can be different on old CPUs, but should still work) then remapping is supported. If your system doesn't support interrupt remapping, you can allow unsafe interrupts with: echo "options vfio\_iommu\_type1 allow\_unsafe\_interrupts=1" > /etc/modprobe.d/iommu\_unsafe\_interrupts.conf ### Verify IOMMU isolation For working PCI passthrough, you need a dedicated IOMMU group for all PCI devices you want to assign to a VM. When executing \# pvesh get /nodes/{nodename}/hardware/pci --pci-class-blacklist "" replacing {nodename} with the name of your node. You should get a list similar to: ┌──────────┬────────┬──────────────┬────────────┬────────┬───────────────────────────────────────────────────────────────────┬... │ class │ device │ id │ iommugroup │ vendor │ device\_name │ ╞══════════╪════════╪══════════════╪════════════╪════════╪═══════════════════════════════════════════════════════════════════╪ │ 0x010601 │ 0xa282 │ 0000:00:17.0 │ 5 │ 0x8086 │ 200 Series PCH SATA controller \[AHCI mode\] │ ├──────────┼────────┼──────────────┼────────────┼────────┼───────────────────────────────────────────────────────────────────┼ │ 0x010802 │ 0xa808 │ 0000:02:00.0 │ 12 │ 0x144d │ NVMe SSD Controller SM981/PM981/PM983 │ ├──────────┼────────┼──────────────┼────────────┼────────┼───────────────────────────────────────────────────────────────────┼ │ 0x020000 │ 0x15b8 │ 0000:00:1f.6 │ 11 │ 0x8086 │ Ethernet Connection (2) I219-V │ ├──────────┼────────┼──────────────┼────────────┼────────┼───────────────────────────────────────────────────────────────────┼ │ 0x030000 │ 0x5912 │ 0000:00:02.0 │ 2 │ 0x8086 │ HD Graphics 630 │ ├──────────┼────────┼──────────────┼────────────┼────────┼───────────────────────────────────────────────────────────────────┼ │ 0x030000 │ 0x1d01 │ 0000:01:00.0 │ 1 │ 0x10de │ GP108 \[GeForce GT 1030\] │ ├──────────┼────────┼──────────────┼────────────┼────────┼───────────────────────────────────────────────────────────────────┼ . . . To have separate IOMMU groups, your processor needs to have support for a feature called ACS (Access Control Services). Make sure you enable the corresponding setting in your BIOS for this. If you don't have dedicated IOMMU groups, you can try moving the card to another PCI slot. Should that not work, you can try using [Alex Williamson's ACS override patch](https://lkml.org/lkml/2013/5/30/513) . However, this should be seen as a last option and is [not without risks](http://vfio.blogspot.be/2014/08/iommu-groups-inside-and-out.html) . As of writing, the ACS patch is part of the Proxmox VE kernel and can be invoked via [Editing the kernel command line](https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysboot_edit_kernel_cmdline) . Add pcie\_acs\_override=downstream to the kernel boot command line (grub or systemd-boot) options. More information can be found at [Alex Williamson's blog](http://vfio.blogspot.com/) . GPU passthrough --------------- ℹ️ **Note**: See [http://blog.quindorian.org/2018/03/building-a-2u-amd-ryzen-server-proxmox-gpu-passthrough.html/](http://blog.quindorian.org/2018/03/building-a-2u-amd-ryzen-server-proxmox-gpu-passthrough.html/) if you like an article with a How-To approach. (NOTE: you usually do not need the ROM-file dumping mentioned at the end!) * AMD RADEON 5xxx, 6xxx, 7xxx, NVIDIA GeForce 7, 8, GTX 4xx, 5xx, 6xx, 7xx, 9xx, 10xx, 15xx, 16xx, and RTX 20xx have been reported working. Anything newer should work as well. * AMD Navi (5xxx(XT)/6xxx(XT)) suffer from the reset bug (see [https://github.com/gnif/vendor-reset](https://github.com/gnif/vendor-reset) ), and while dedicated users have managed to get them to run, they require a lot more effort and will probably not work entirely stable (see the [AMD specific issues](https://pve.proxmox.com/wiki/PCI_Passthrough#AMD_specific_issues) for workarounds). * You might need to load some specific options in grub.cfg or other tuning values to get your configuration specifically working/stable * Here's a good forum thread of Arch Linux: [https://bbs.archlinux.org/viewtopic.php?id=162768](https://bbs.archlinux.org/viewtopic.php?id=162768) For starters, it's often helpful if the host doesn't try to use the GPU, which avoids issues with the host driver unbinding and re-binding to the device. Sometimes making sure the host BIOS POST messages are displayed on a different GPU is helpful too. This can sometimes be acomplished via BIOS settings, moving the card to a different slot or enabling/disabling legacy boot support. ### Blacklisting drivers The following is a list of common drivers and how to blacklist them: * AMD GPUs echo "blacklist amdgpu" >> /etc/modprobe.d/blacklist.conf echo "blacklist radeon" >> /etc/modprobe.d/blacklist.conf * NVIDIA GPUs echo "blacklist nouveau" >> /etc/modprobe.d/blacklist.conf echo "blacklist nvidia\*" >> /etc/modprobe.d/blacklist.conf * Intel GPUs echo "blacklist i915" >> /etc/modprobe.d/blacklist.conf ℹ️ **Note**: If you are using an Intel iGPU and an Intel discrete GPU, blacklisting the Intel 'i915' drivers that the discrete GPU uses means the iGPU won't be able to use those drivers either. After blacklisting, you will need to reboot. ### How to know if a graphics card is UEFI (OVMF) compatible Have a look at [the requirements section](https://pve.proxmox.com/mediawiki/index.php?title=PCI_passthrough&action=edit&redlink=1 "PCI passthrough (page does not exist)") . Chances are you are using the BIOS listed for your device on the Techpowerup GPU ROM list, which will say if it is UEFI compatible or not. Alternatively, you can dump your ROM and use Alex Williams rom-parser tool: ℹ️ **Note**: You will want to run the following commands logged in as root user (by running `su -`) or by wrapping them with `sudo sh -c ""`, otherwise the bash-redirects in the code-snippets below won't work Get and compile the software "rom-parser": git clone [https://github.com/awilliam/rom-parser](https://github.com/awilliam/rom-parser) cd rom-parser make Then dump the rom of you vga card: cd /sys/bus/pci/devices/0000:01:00.0/ echo 1 > rom cat rom > /tmp/image.rom echo 0 > rom and test it with: ./rom-parser /tmp/image.rom The output should look like this: Valid ROM signature found @0h, PCIR offset 190h PCIR: type 0, vendor: 10de, device: 1280, class: 030000 PCIR: revision 0, vendor revision: 1 Valid ROM signature found @f400h, PCIR offset 1ch PCIR: type 3, vendor: 10de, device: 1280, class: 030000 PCIR: revision 3, vendor revision: 0 EFI: Signature Valid Last image To be UEFI compatible, you need a "type 3" in the result. ### The 'romfile' option Some motherboards can't pass through GPUs on the first PCI(e) slot by default, because its vBIOS is shadowed during boot up. You need to capture its vBIOS when it is working "normally" (i.e. installed in a different slot), then you can move the card to slot 1 and start the vm using the dumped vBIOS. To dump the bios: cd /sys/bus/pci/devices/0000:01:00.0/ echo 1 > rom cat rom > /usr/share/kvm/vbios.bin echo 0 > rom Then you can pass the vbios file (must be located in /usr/share/kvm/) with: hostpci0: 01:00,x-vga=on,romfile=vbios.bin ### Tips Some Windows applications like GeForce Experience, Passmark Performance Test and SiSoftware Sandra can crash the VM. You need to add: echo "options kvm ignore\_msrs=1" > /etc/modprobe.d/kvm.conf If you see a lot of warning messages in your 'dmesg' system log, add the following instead: echo "options kvm ignore\_msrs=1 report\_ignored\_msrs=0" > /etc/modprobe.d/kvm.conf #### Nvidia Tips User have reported that NVIDIA Kepler K80 GPUs need this in vmid.conf: args: -machine pc,max-ram-below-4g=1G Troubleshooting --------------- ### "BAR 3: can't reserve \[mem\]" error If you have this error when you try to use the card for a VM: vfio-pci 0000:04:00.0: BAR 3: can't reserve \[mem 0xca000000-0xcbffffff 64bit\] you can try to add the following kernel command line option: video=efifb:off Check out the documentation about [editing the kernel command line](https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysboot_edit_kernel_cmdline) . ### "BAR0 is 0M" error or Windows Code 12 Error In case you see such an error in the journal of the guest VM: kernel: nvidia 0000:01:00.0: enabling device (0000 -> 0002) kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: NVRM: BAR0 is 0M @ 0x0 (PCI:0000:01:00.0) kernel: nvidia: probe of 0000:01:00.0 failed with error -1 kernel: NVRM: The NVIDIA probe routine failed for 1 device(s). Or the Windows Device Manager complains with This device cannot find enough free resources that it can use. (Code 12) This happens when passing the GPU with a large amount of VRAM to a VM that uses OVMF. By default, OVMF uses 32GB of address space for the 64-bit PCI MMIO window (see [edk2 docs](https://github.com/tianocore/edk2/blob/master/OvmfPkg/RUNTIME_CONFIG.md#platform-optovmfx-pcimmio64mb) ), which is not enough for GPUs with 24GB VRAM or more. There are four possible solutions to this: * Use `host` CPU type. This changes the MMIO size calculation for OVMF with info from the host CPU. * If you can't or don't want to use `host` type CPU, you can set `phys-bits` to `host`. You also possibly need to enable the flag `pdpe1gb`. This can be done with (we use x86-64-v2-AES as an example CPU type): qm set VMID --cpu x86-64-v2-AES,phys-bits=host,flags=+pdpe1gb * Should neither of that work, you can manually set the MMIO window size, e.g. to 64 GB: qm set VMID --args '-fw\_cfg name=opt/ovmf/X-PciMmio64Mb,string=65536' Set it to larger values if necessary, e.g. 131072 for 128GB or 262144 for 256GB. * Alternatively, SeaBIOS can be used instead of OVMF, which should not cause such issues. ### WSLg (Windows Subsystem for Linux GUI) If GUI apps don't open in WSLg, see [Windows 2022 guest best practices](https://pve.proxmox.com/wiki/Windows_2022_guest_best_practices#Installing_WSL.28g.29) . ### Black display in NoVNC/Spice If you are passing through a GPU and are getting a black screen, you might need to change your display settings in the Guest OS. On Windows, this can be done by pressing the "Super/Windows" and "P" key. Alternatively, if you are using the GPU for hardware accelerated computing and need no graphical output from it, you can deselect the "primary GPU" option and physically disconnect your GPU. ### Spice Spice may give trouble when passing through a GPU as it presents a "virtual" PCI graphic card to the guest and some drivers have problems with that, even when both cards show up. It's always worth a try to disable SPICE and check again if something fails. ### HDMI audio crackling/broken Some digital audio devices (usually added via GPU functions) may require MSI (Message Signaled Interrupts) to be enabled to function correctly. If you experience any issues, try changing MSI settings in the guest and rebooting the guest. Linux guests usually enable MSI by themselves. To force use of MSI for GPU audio devices, use the following command and reboot: echo "options snd-hda-intel enable\_msi=1" >> /etc/modprobe.d/snd-hda-intel.conf Use 'lspci -vv' and check for the following line on your device to see if MSI is enabled: Capabilities: \[a0\] MSI: Enable+ Count=1/1 Maskable- 64bit+ If it says 'Enable+', MSI is working, 'Enable-' means it is supported but disabled, and if the line is missing, MSI is not supported by the PCIe hardware. This can potentially also improve performance for other passthrough devices, including GPUs, but that depends on the hardware being used. ### BIOS options Make sure you are using the most recent BIOS version for your motherboard. Often IOMMU groupings or passthrough support in general is improved in later versions. Some general BIOS options that might need changing to allow passthrough to work: * IOMMU or VT-d: Set to 'Enabled' or equivalent, often 'Auto' is not the same * 'Legacy boot' or CSM: For GPU passthrough it can help to disable this, but keep in mind that PVE has to be installed in UEFI mode, as it will not boot in BIOS mode without this enabled. The reason for disabling this is that it avoids legacy VGA initialization of installed GPUs, making them able to be re-initialized later, as required for passthrough. Most useful when trying to use passthrough in single GPU systems. * 'Resizable BAR'/'Smart Access Memory': Some AMD GPUs (Vega and up) experience 'Code 43' in Windows guests if this is enabled on the host. It's not supported in VMs either way (yet), so the recommended setting is 'off'. ### Error 43 [Error code 43](https://support.microsoft.com/en-us/windows/fix-graphics-device-problems-with-error-code-43-6f6ae1ec-0bbe-a848-142e-0c6190502842) is a generic Windows driver error and can occur for a wide number of reasons. Things you can try troubleshooting include: #### Finding out if the PCI device has a hardware fault * Try passing the PCI device to a Linux VM * Try plugging the PCI device into a different PCI slot or into a different machine #### Finding software issues * Check the security event logs of your Windows VM * Check the dmesg logs of your host machine * [Dump your vBIOS](https://pve.proxmox.com/wiki/PCI_Passthrough#How_to_know_if_a_Graphics_Card_is_UEFI_.28OVMF.29_compatible) and check if it is working correctly. * Try a different vbios (see [the GPU requirements section](https://pve.proxmox.com/mediawiki/index.php?title=PCI_passthrough&action=edit&redlink=1 "PCI passthrough (page does not exist)") ) * If your GPU supports resizable BAR/SAM and you have this option set in your BIOS, you might need to deactivate it or manually tweak your BAR using an udev rule (see [Code 43 while Resizable Bar is turned on in the bios](https://wiki.archlinux.org/title/PCI_passthrough_via_OVMF#Code_43_while_Resizable_Bar_is_turned_on_in_the_bios) in the Arch wiki) * Sometimes the issue is very hardware-dependent. You might find someone else who found a solution who has the same hardware. Try searching the internet with keywords containing your hardware, together with keywords like "Proxmox", "KVM", or "Qemu". #### Nvidia specific issues When passing through mobile- or vGPUs, it might be necessary to spoof the Vendor ID and Hardware ID as if the passed-through GPU were the desktop variant. Changing the IDs might also be needed to remove manufacturer-specific vendor ID variants that are not recognized otherwise. The Vendor and Device ID can be added in the web interface under "Hardware" -> "PCI Device (hostpciX)" and then clicking on the "Advanced" checkbox. Some software will also refuse to run when it detects that it is running in a VM. This should no longer be an issue with Nvidia drivers 465 and newer. To find the Vendor ID and Device ID of the card installed on your host, run: lspci -nn which will give you something similar to 01:00.0 VGA compatible controller \[0300\]: NVIDIA Corporation GP108 \[GeForce GT 1030\] \[10de:1d01\] (rev a1) Here, `0x10de` is the Vendor ID and `0x1d01` the Device ID. #### AMD specific issues Some AMD cards suffer from the "AMD reset bug" where the GPU does not correctly reset after power cycling. This can be remedied with the [vendor-reset patch](https://github.com/gnif/vendor-reset/) . See also [Nick Sherlock's writeup](https://www.nicksherlock.com/2020/11/working-around-the-amd-gpu-reset-bug-on-proxmox/) on the issue. USB passthrough --------------- If you need to pass through USB devices (keyboard, mouse), please follow the [USB Physical Port Mapping](https://pve.proxmox.com/wiki/USB_Physical_Port_Mapping "USB Physical Port Mapping") wiki article. vGPU ---- If you want to split up one GPU into multiple vGPUs, see: * [MxGPU with AMD S7150](https://pve.proxmox.com/wiki/MxGPU_with_AMD_S7150_under_Proxmox_VE_5.x) * [NVIDIA vGPU](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE_7.x) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=PCI\_Passthrough&oldid=12459](https://pve.proxmox.com/mediawiki/index.php?title=PCI_Passthrough&oldid=12459) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Staging](https://pve.proxmox.com/mediawiki/index.php?title=Category:Staging&action=edit&redlink=1 "Category:Staging (page does not exist)") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Dynamic Memory Management - Proxmox VE Dynamic Memory Management ========================= From Proxmox VE (Redirected from [KSM](https://pve.proxmox.com/mediawiki/index.php?title=KSM&redirect=no "KSM") ) [Jump to navigation](https://pve.proxmox.com/wiki/KSM#mw-head) [Jump to search](https://pve.proxmox.com/wiki/KSM#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/KSM#Introduction) * [2 KSM](https://pve.proxmox.com/wiki/KSM#KSM) * [2.1 KSM in action](https://pve.proxmox.com/wiki/KSM#KSM_in_action) * [2.2 Disable KSM](https://pve.proxmox.com/wiki/KSM#Disable_KSM) * [3 Ballooning](https://pve.proxmox.com/wiki/KSM#Ballooning) * [3.1 Manually ballooning (testing)](https://pve.proxmox.com/wiki/KSM#Manually_ballooning_(testing)) * [3.2 Requirements for Windows VM](https://pve.proxmox.com/wiki/KSM#Requirements_for_Windows_VM) * [3.2.1 Installation](https://pve.proxmox.com/wiki/KSM#Installation) * [3.2.2 Download](https://pve.proxmox.com/wiki/KSM#Download) * [3.2.3 Choose the right driver](https://pve.proxmox.com/wiki/KSM#Choose_the_right_driver) * [3.2.4 Enable Auto-Ballooning on Windows Server 2012 / Windows 8.1 or newer](https://pve.proxmox.com/wiki/KSM#Enable_Auto-Ballooning_on_Windows_Server_2012_/_Windows_8.1_or_newer) * [3.2.5 Enable Auto-Ballooning on Windows 2008r2](https://pve.proxmox.com/wiki/KSM#Enable_Auto-Ballooning_on_Windows_2008r2) * [3.2.6 Enable Auto-Ballooning on Windows 2003 / Windows Xp](https://pve.proxmox.com/wiki/KSM#Enable_Auto-Ballooning_on_Windows_2003_/_Windows_Xp) * [3.3 See also](https://pve.proxmox.com/wiki/KSM#See_also) * [3.4 Requirements for Linux VM](https://pve.proxmox.com/wiki/KSM#Requirements_for_Linux_VM) * [4 External Links](https://pve.proxmox.com/wiki/KSM#External_Links) * [5 Video Tutorials](https://pve.proxmox.com/wiki/KSM#Video_Tutorials) Introduction ------------ Optimized and effective memory management is a key factor in virtualization environments. KSM and Auto-Ballooning enables sophisticated and economic configurations for physical RAM utilization. KSM --- KSM (Kernel Samepage Merging) is running in the Linux kernel and scans the memory of all the virtual machines running on a single host, looking for duplication and consolidating. With KSM we're able to improve virtual machine density by as much as 300% without impacting performance. One of the great benefits of using Linux as the hypervisor means KSM is not limited to KVM and virtual machines, but can also reduce memory pressure with normal Linux applications. It was integrated in PVE since version 1.5, and is implemented with the package "ksm-control-daemon" (check your version with the cli command "pveversion -v"). ### KSM in action Just install several KVM virtual machines with the same OS (using at least 80% of your physical memory on the host) and wait a few minutes. You will notice higher CPU activities on the host (ksm daemon) and the used memory on the host will be lowered significantly (see start page showing the overall memory usage). Howto verify that KSM is working (how many pages are being shared between your KVM guests): watch cat /sys/kernel/mm/ksm/pages\_sharing Note: a page is 4096 bytes The file /etc/ksmtuned.conf allows for some customization of its behaviour. See also * [http://www.linux-kvm.org/page/KSM](http://www.linux-kvm.org/page/KSM) * [http://www.linux-kvm.com/content/using-ksm-kernel-samepage-merging-kvm](http://www.linux-kvm.com/content/using-ksm-kernel-samepage-merging-kvm) * [http://en.wikipedia.org/wiki/Kernel\_SamePage\_Merging\_%28KSM%29](http://en.wikipedia.org/wiki/Kernel_SamePage_Merging_%28KSM%29) ### Disable KSM If you don't care about memory optimization but care about save CPU overhead produced by KSM, in Proxmox >= 4.x you can disable it with: systemctl disable ksmtuned and reboot Ballooning ---------- Memory ballooning (KVM only) allows you to have your guest dynamically change it’s memory usage by evicting unused memory during run time. It reduces the impact your guest can have on memory usage of your host by giving up unused memory back to the host. The Proxmox VE host can loan ballooned memory to a busy VM. The VM decides which processes or cache pages to swap out to free up memory for the balloon. The VM (Windows or Linux) knows best which memory regions it can give up without impacting performance of the VM. Note that the Guest cannot ask for the memory back until the host has 'deflated' this balloon. If set too aggressively, some applications in the guest may run out of memory as a result and your guest's OOM killer may activate, killing important processes - [https://www.kernel.org/doc/gorman/html/understand/understand016.html](https://www.kernel.org/doc/gorman/html/understand/understand016.html) Note that if you are passing through a physical PCI(e) device or a Virtual Function I/O (VFIO) Mediated device (MDEV) such as a vGPU, then ballooning will not work since these devices are mapped to fixed memory addresses in the host and in the guest. If you do enable ballooning, the KVM process will not release the memory back to the host but the guest may report a reduced memory availability which can be manually recovered using the KVM monitor using the balloon command. ### Manually ballooning (testing) In the monitor tab of your guest, type balloon - so balloon 16384 will instruct your guest to target 16GB of memory. This is a 'target' which the driver on the VM side will try to reach by trying to free available memory. ### Requirements for Windows VM #### Installation * You need to install the VirtIO Balloon Driver and the management service (blnsvr.exe -i). * Notice: there is a small blnsvr.exe bug on 32bit systems with RAM more than 2GB: [https://github.com/YanVugenfirer/kvm-guest-drivers-windows/issues/11](https://github.com/YanVugenfirer/kvm-guest-drivers-windows/issues/11) See [Windows VirtIO Drivers](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers "Windows VirtIO Drivers") to get info about * downloading VirtIO drivers * changelog and guest OS compatibility * other kind of guest devices supported #### Download Download the latest drivers (ISO) as suggested by the page [Windows\_VirtIO\_Drivers](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers "Windows VirtIO Drivers") to your desktop. Then upload the ISO to your Proxmox VE server: * logon to the Proxmox VE web interface * select a ISO-enabled storage (see [Storage\_Model#Storage\_type\_Content](https://pve.proxmox.com/mediawiki/index.php?title=Storage_Model&action=edit&redlink=1 "Storage Model (page does not exist)") ) * switch to "content" tab * just use the "upload" button on the menu bar. #### Choose the right driver * Follow the link: [Windows\_VirtIO\_Drivers#Choose\_the\_right\_driver](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#Choose_the_right_driver "Windows VirtIO Drivers") #### Enable Auto-Ballooning on Windows Server 2012 / Windows 8.1 or newer Starting with [virtio-win-0.1.173-2](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/) the driver ISO provides an installer located at ":\\virtio-win-gt-x64.msi" that can, besides other things, install the ballooning service. If it does not work you can follow the manual way which is described below for Windows 2008r2. #### Enable Auto-Ballooning on Windows 2008r2 1. Set the VM memory to "Automatically allocate memory within this range" - I choose 4096/2048 as example (see screenshot) 2. Start the VM and install all virtio drivers, including the balloon driver (see screenshot) 3. Copy and rename as Administrator the WIN7\\AMD64 directory from the virtio.iso to "c:/Program files/Balloon" 4. Open a CMD as Administrator and cd into "c:/Program Files/Balloon" 5. Install the BLNSVR with "BLNSVR.exe -i" As soon as the service is started, also the memory information displayed on the Proxmox VE GUI is identical to the value shown in the windows task manager (see screenshot). If you need details about ballooning stats for this VM, go to the KVM monitor and enter 'info balloon' VirtIO drivers: [KVM project wiki downloads](http://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers) * [![Set Memory to Dynamic](https://pve.proxmox.com/mediawiki/images/thumb/2/2b/Screen-Win2008r2-Set-Memory-Dynamically.png/240px-Screen-Win2008r2-Set-Memory-Dynamically.png)](https://pve.proxmox.com/wiki/File:Screen-Win2008r2-Set-Memory-Dynamically.png "Set Memory to Dynamic") Set Memory to Dynamic * [![VirtIO Balloon Driver](https://pve.proxmox.com/mediawiki/images/thumb/b/b5/Screen-Win2008r2-VirtIO-Balloon-Driver.png/240px-Screen-Win2008r2-VirtIO-Balloon-Driver.png)](https://pve.proxmox.com/wiki/File:Screen-Win2008r2-VirtIO-Balloon-Driver.png "VirtIO Balloon Driver") VirtIO Balloon Driver * [![BLNSVR Service](https://pve.proxmox.com/mediawiki/images/thumb/e/eb/Screen-2008r2-BLNSVR.png/240px-Screen-2008r2-BLNSVR.png)](https://pve.proxmox.com/wiki/File:Screen-2008r2-BLNSVR.png "BLNSVR Service") BLNSVR Service * [![Memory Usage](https://pve.proxmox.com/mediawiki/images/thumb/5/52/Screen-Win2008r2-Memory-Usage.png/240px-Screen-Win2008r2-Memory-Usage.png)](https://pve.proxmox.com/wiki/File:Screen-Win2008r2-Memory-Usage.png "Memory Usage") Memory Usage #### Enable Auto-Ballooning on Windows 2003 / Windows Xp You need to install the balloon service with BLNSVR, like for win2008. You also need to install the driver manually Download the "devcon" software on microsoft website [http://support.microsoft.com/kb/311272](http://support.microsoft.com/kb/311272) Then install the balloon driver with devcon install BALLOON.inf "PCI\\VEN\_1AF4&DEV\_1002&SUBSYS\_00051AF4&REV\_00" ### See also * [Windows\_VirtIO\_Drivers](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers "Windows VirtIO Drivers") * [Paravirtualized Block Drivers for Windows](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows "Paravirtualized Block Drivers for Windows") * [Paravirtualized Network Drivers for Windows](https://pve.proxmox.com/wiki/Paravirtualized_Network_Drivers_for_Windows "Paravirtualized Network Drivers for Windows") ### Requirements for Linux VM Modern Linux Kernels does include the Balloon drivers by default. It works out of the box, and you only need to set the VM to "Automatically allocate memory within this range" External Links -------------- tbd. Video Tutorials --------------- tbd: [Proxmox VE Youtube channel](http://www.youtube.com/user/ProxmoxVE) Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Dynamic\_Memory\_Management&oldid=11794](https://pve.proxmox.com/mediawiki/index.php?title=Dynamic_Memory_Management&oldid=11794) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Windows 10 guest best practices - Proxmox VE Windows 10 guest best practices =============================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Windows_10_guest_best_practices#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Windows_10_guest_best_practices#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Windows_10_guest_best_practices#Introduction) * [2 Install](https://pve.proxmox.com/wiki/Windows_10_guest_best_practices#Install) * [2.1 Prepare](https://pve.proxmox.com/wiki/Windows_10_guest_best_practices#Prepare) * [2.2 Launch Windows install](https://pve.proxmox.com/wiki/Windows_10_guest_best_practices#Launch_Windows_install) * [3 Install Guest Agent and Services](https://pve.proxmox.com/wiki/Windows_10_guest_best_practices#Install_Guest_Agent_and_Services) * [3.1 Guest Agent](https://pve.proxmox.com/wiki/Windows_10_guest_best_practices#Guest_Agent) * [3.2 Drivers and Services](https://pve.proxmox.com/wiki/Windows_10_guest_best_practices#Drivers_and_Services) * [3.3 Check for missing drivers](https://pve.proxmox.com/wiki/Windows_10_guest_best_practices#Check_for_missing_drivers) * [3.4 Installing WSL(g)](https://pve.proxmox.com/wiki/Windows_10_guest_best_practices#Installing_WSL(g)) * [4 Further information](https://pve.proxmox.com/wiki/Windows_10_guest_best_practices#Further_information) * [4.1 Disk-Image Format: raw vs qcow2](https://pve.proxmox.com/wiki/Windows_10_guest_best_practices#Disk-Image_Format:_raw_vs_qcow2) * [4.2 VirtIO drivers](https://pve.proxmox.com/wiki/Windows_10_guest_best_practices#VirtIO_drivers) * [5 See also](https://pve.proxmox.com/wiki/Windows_10_guest_best_practices#See_also) Introduction ------------ This is a set of best practices to follow when installing a Windows 10 guest on a Proxmox VE server 6.x. Right now it's a work in progress. Install ------- ### Prepare To obtain a good level of performance, we will install the [Windows VirtIO Drivers](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers "Windows VirtIO Drivers") during the Windows installation. * Create a new VM, select "Microsoft Windows 10/2016/2019" as Guest OS and enable the "Qemu Agent" in the System tab. Continue and mount your Windows 10 ISO in the CDROM drive * For your virtual hard disk select "SCSI" as bus with "VirtIO SCSI single" as controller. Set "Write back" as cache option for best performance (the "No cache" default [is safer, but slower](https://pve.proxmox.com/wiki/Performance_Tweaks#Disk_Cache "Performance Tweaks") ) and tick "Discard" to optimally use disk space (TRIM). For the best performance, also make sure that IO Thread is enabled. * Configure your memory settings as needed, continue and set "VirtIO (paravirtualized)" as network device, finish your VM creation. * For the VirtIO drivers, upload the driver ISO (see [Windows VirtIO Drivers#virtio-win Releases](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#virtio-win_Releases "Windows VirtIO Drivers") for information on how to download it) to your storage, create a new CDROM drive (use "Add -> CD/DVD drive" in the hardware tab) **with Bus "IDE" and number 0**. Load the Virtio Drivers ISO in the new virtual CDROM drive. * Now your ready to start the VM, just follow the Windows installer. * Note for Older Version of Windows like Windows-2012 (use the stable older version of VirtIO ISO - virtio-win-0.1.189.iso, [download it from here](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.189-1/virtio-win-0.1.189.iso) ) ### Launch Windows install * After starting your VM launch the noVNC console * Follow the installer steps until you reach the installation type selection where you need to select "Custom (advanced)" * Now click "Load driver" to install the VirtIO drivers for hard disk and the network. * Hard disk: Browse to the CD drive where you mounted the VirtIO driver and select folder "vioscsi\\w10\\amd64" and confirm. Select the "Red Hat VirtIO SCSI pass-through controller" and click next to install it. Now you should see your drive. * Network: Repeat the steps from above (click again "Load driver", etc.) and select the folder "NetKVM\\w10\\amd64", confirm it and select "Redhat VirtIO Ethernet Adapter" and click next. * Memory Ballooning: Again, repeat the steps but this time select the "Balloon\\w10\\amd64" folder, then the "VirtIO Balloon Driver" and install it by clicking next. With these three drivers you should be good covered to run a fast virtualized Windows 10 system. * Choose the drive and continue the Windows installer steps. **HINT:** There is a [video showing the process](https://www.proxmox.com/en/services/training-courses/videos/proxmox-virtual-environment/install-windows-2016-server-on-proxmox-ve) for a Windows Server 2016 installation which is the same as for Windows 10. Install Guest Agent and Services -------------------------------- ### Guest Agent If you enabled the Qemu Agent option for the VM the mouse pointer will probably be off after the first boot. To remedy this install the "Qemu Guest Agent". The installer is located on the driver CD under guest-agent\\qemu-ga-x86\_64.msi. ### Drivers and Services [![](https://pve.proxmox.com/mediawiki/images/thumb/f/fd/Win10_virtio_guest_tool_installer.png/400px-Win10_virtio_guest_tool_installer.png)](https://pve.proxmox.com/wiki/File:Win10_virtio_guest_tool_installer.png) VirtIO guest tools installer The easiest way to install missing drivers and services is to use the provided MSI installer. It is available on the driver CD since version 0.1.173-2. Run the "virtio-win-gt-x64.msi" file located directly on the CD. If you do not plan to use [SPICE](https://pve.proxmox.com/wiki/SPICE "SPICE") you can deselect the "Qxl" and "Spice" features. Restart the VM after the installer is done. After all this the RAM usage and IP configuration should be shown correctly in the summary page of the VM. For more information and configuration about ballooning, see [Dynamic Memory Management](https://pve.proxmox.com/wiki/Dynamic_Memory_Management "Dynamic Memory Management") ### Check for missing drivers _See also: [Paravirtualized Block Drivers for Windows](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows "Paravirtualized Block Drivers for Windows") _ [![](https://pve.proxmox.com/mediawiki/images/thumb/9/9c/Win10_unknown_dev.png/400px-Win10_unknown_dev.png)](https://pve.proxmox.com/wiki/File:Win10_unknown_dev.png) Unknown device in device manager [![](https://pve.proxmox.com/mediawiki/images/thumb/5/5e/Win10_update_driver_cd_selection.png/400px-Win10_update_driver_cd_selection.png)](https://pve.proxmox.com/wiki/File:Win10_update_driver_cd_selection.png) Make sure to include subfolders Go to the Device Manager to see if there are any drivers missing. For any unknown device: * Right click an select "Update driver". * Select "Browse my computer for driver software". * Select the Driver CD. Make sure that "Include subfolders" is checked. * Once a driver has been found you might be prompted with a security warning asking if you "Would like to install this device software". Click "Install". ### Installing WSL(g) To run WSL (Windows Subsystem for Linux) you need to enable [Nested Virtualization](https://pve.proxmox.com/wiki/Nested_Virtualization "Nested Virtualization") . Make sure to set your processor to 'host'; if you already set up your VM and did not select 'host' as processor, you can change it in the 'Hardware' section of your VM in the web interface. Follow the [official instructions](https://learn.microsoft.com/en-us/windows/wsl/install) . If you are using a GPU via PCI(e) passthrough, you might need to add args: -cpu host,kvm=off to your config file at _/etc/pve/qemu-server/.conf_, see [the vfio blog](http://vfio.blogspot.com/2014/08/vfiovga-faq.html) Further information ------------------- ### Disk-Image Format: raw vs qcow2 Raw file format provides slightly better performance while qcow2 offers advanced features such as copy on write and [Live\_Snapshots](https://pve.proxmox.com/wiki/Live_Snapshots "Live Snapshots") . Since V2.3, qcow2 is the default format. ### VirtIO drivers Make it really easy: Build your ISO with drivers already included: [Windows guests - build ISOs including VirtIO drivers](https://pve.proxmox.com/wiki/Windows_guests_-_build_ISOs_including_VirtIO_drivers "Windows guests - build ISOs including VirtIO drivers") See also -------- [Windows 2012 guest best practices](https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices "Windows 2012 guest best practices") [Windows 8 guest best practices](https://pve.proxmox.com/wiki/Windows_8_guest_best_practices "Windows 8 guest best practices") Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Windows\_10\_guest\_best\_practices&oldid=12482](https://pve.proxmox.com/mediawiki/index.php?title=Windows_10_guest_best_practices&oldid=12482) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Windows 7 guest best practices - Proxmox VE Windows 7 guest best practices ============================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Windows_7_guest_best_practices#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Windows_7_guest_best_practices#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Windows_7_guest_best_practices#Introduction) * [2 Install](https://pve.proxmox.com/wiki/Windows_7_guest_best_practices#Install) * [2.1 Prepare](https://pve.proxmox.com/wiki/Windows_7_guest_best_practices#Prepare) * [2.2 Launch Windows install](https://pve.proxmox.com/wiki/Windows_7_guest_best_practices#Launch_Windows_install) * [3 Install additional VirtIO drivers on running System](https://pve.proxmox.com/wiki/Windows_7_guest_best_practices#Install_additional_VirtIO_drivers_on_running_System) * [4 Further information](https://pve.proxmox.com/wiki/Windows_7_guest_best_practices#Further_information) * [4.1 Disk-Image Format: raw vs qcow2](https://pve.proxmox.com/wiki/Windows_7_guest_best_practices#Disk-Image_Format:_raw_vs_qcow2) * [4.2 VirtIO drivers](https://pve.proxmox.com/wiki/Windows_7_guest_best_practices#VirtIO_drivers) * [5 See also](https://pve.proxmox.com/wiki/Windows_7_guest_best_practices#See_also) Introduction ------------ This is a set of best practices to follow when installing a Windows 7 guest on a Proxmox VE server 4.x. Right now it's a work in progress. Install ------- ### Prepare To obtain a good level of performance, we will install the [Windows VirtIO Drivers](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers "Windows VirtIO Drivers") during the Windows installation. * Create a new VM, select "Microsoft Windows 7/2008" continue and mount your Windows 7 ISO in the CDROM drive * For your virtual hard disk select "VirtIO" as bus and "Write back" as cache option for best performance (the No cache default is safer, but slower) * Configure your memory settings as needed, continue and set "VirtIO (paravirtualized)" as network device, finish your VM creation. * For the VirtIO drivers, upload the driver ISO (use the stable VirtIO iso, [get it from here](https://fedoraproject.org/wiki/Windows_Virtio_Drivers#Direct_download) ) to your storage, create a new CDROM drive (use "Add -> CD/DVD drive" in the hardware tab), and load the Virtio Drivers ISO in the new virtual CDROM drive * Now your ready to start the VM, just follow the Windows installer. ### Launch Windows install * After starting your VM launch the console * Follow the installer steps until you reach the installation type selection where you need to select "Custom (advanced)" * Now click "Load driver" to install the VirtIO drivers for hard disk and the network. (successfully tested with "virtio-win-0.1.105.iso") * hard disk: Browse to the CD drive where you mounted the VirtIO driver and select folder "viostor\\w7\\amd64" and confirm. Select the "Red Hat VirtIO SCSI controller" and click next to install it. Now you should see your drive. * Network: Repeat the steps from above (click again "Load driver", etc.) and select the folder "NetKVM\\w7\\amd64", confirm it and select "Redhat VirtIO Ethernet Adapter" and click next. * Memory Ballooning: Again, repeat the steps but this time select the "Balloon\\w7\\amd64" folder, then the "VirtIO Balloon Driver" and install it by clicking next. With these three drivers you should be good covered to run a fast virtualized Windows 10 system. * Choose the drive and continue the Windows installer steps. Install additional VirtIO drivers on running System --------------------------------------------------- _See also: [Paravirtualized Block Drivers for Windows](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows "Paravirtualized Block Drivers for Windows") _ [![](https://pve.proxmox.com/mediawiki/images/thumb/a/a4/Install_virtio_driver.png/400px-Install_virtio_driver.png)](https://pve.proxmox.com/wiki/File:Install_virtio_driver.png) VirtIO Ethernet Installation If you miss some VirtIO drivers, you may install them as follows on a running system. To do so, start the file explorer, select the CDROM drive with the VirtIO iso image mounted and browse to the folder folder of the desired component. Some often needed, using the virtio-win-0.1.105 version, are: * Ethernet Adapter: NetKVM\\w7\\amd64 here right-click the setup information file "netkvm" and select install. * Virtual Memory Balloon Driver: Balloon\\w7\\amd64 here right-click the setup information file "balloon" and select install. * Hard disk: viostor\\w7\\amd64 here right-click the setup information file "viostor" and select install. After the installation process the device should work as expected. For more information and configuration about ballooning, see [Dynamic Memory Management](https://pve.proxmox.com/wiki/Dynamic_Memory_Management "Dynamic Memory Management") Further information ------------------- ### Disk-Image Format: raw vs qcow2 Raw file format provides slightly better performance while qcow2 offers advanced features such as copy on write and [Live\_Snapshots](https://pve.proxmox.com/wiki/Live_Snapshots "Live Snapshots") . Since V2.3, qcow2 is the default format. ### VirtIO drivers Make it really easy: Build your ISO with drivers already included: [Windows guests - build ISOs including VirtIO drivers](https://pve.proxmox.com/wiki/Windows_guests_-_build_ISOs_including_VirtIO_drivers "Windows guests - build ISOs including VirtIO drivers") See also -------- [Windows 2012 guest best practices](https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices "Windows 2012 guest best practices") [Windows 10 guest best practices](https://pve.proxmox.com/wiki/Windows_10_guest_best_practices "Windows 10 guest best practices") Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Windows\_7\_guest\_best\_practices&oldid=9140](https://pve.proxmox.com/mediawiki/index.php?title=Windows_7_guest_best_practices&oldid=9140) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") * [Qemu/KVM](https://pve.proxmox.com/wiki/Category:Qemu/KVM "Category:Qemu/KVM") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Windows 2016 guest best practices - Proxmox VE Windows 2016 guest best practices ================================= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Windows_2016_guest_best_practices#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Windows_2016_guest_best_practices#searchInput) Contents -------- * [1 Introduction](https://pve.proxmox.com/wiki/Windows_2016_guest_best_practices#Introduction) * [2 Install](https://pve.proxmox.com/wiki/Windows_2016_guest_best_practices#Install) * [2.1 Prepare](https://pve.proxmox.com/wiki/Windows_2016_guest_best_practices#Prepare) * [2.2 Launch Windows install](https://pve.proxmox.com/wiki/Windows_2016_guest_best_practices#Launch_Windows_install) * [3 Install Guest Agent and Services](https://pve.proxmox.com/wiki/Windows_2016_guest_best_practices#Install_Guest_Agent_and_Services) * [3.1 Guest Agent](https://pve.proxmox.com/wiki/Windows_2016_guest_best_practices#Guest_Agent) * [3.2 Drivers and Services](https://pve.proxmox.com/wiki/Windows_2016_guest_best_practices#Drivers_and_Services) * [3.3 Check for missing drivers](https://pve.proxmox.com/wiki/Windows_2016_guest_best_practices#Check_for_missing_drivers) * [3.4 Installing WSL(g)](https://pve.proxmox.com/wiki/Windows_2016_guest_best_practices#Installing_WSL(g)) * [4 Further information](https://pve.proxmox.com/wiki/Windows_2016_guest_best_practices#Further_information) * [4.1 Disk-Image Format: raw vs qcow2](https://pve.proxmox.com/wiki/Windows_2016_guest_best_practices#Disk-Image_Format:_raw_vs_qcow2) * [4.2 VirtIO drivers](https://pve.proxmox.com/wiki/Windows_2016_guest_best_practices#VirtIO_drivers) * [5 See also](https://pve.proxmox.com/wiki/Windows_2016_guest_best_practices#See_also) Introduction ------------ This is a set of best practices to follow when installing a Windows Server 2016 guest on a Proxmox VE server 6.x. Install ------- ### Prepare To obtain a good level of performance, we will install the [Windows VirtIO Drivers](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers "Windows VirtIO Drivers") during the Windows installation. * Create a new VM, select "Microsoft Windows 10/2016/2019" as Guest OS and enable the "Qemu Agent" in the System tab. Continue and mount your Windows Server 2016 ISO in the CDROM drive * For your virtual hard disk select "SCSI" as bus with "VirtIO SCSI single" as controller. Set "Write back" as cache option for best performance (the "No cache" default [is safer, but slower](https://pve.proxmox.com/wiki/Performance_Tweaks#Disk_Cache "Performance Tweaks") ) and tick "Discard" to optimally use disk space (TRIM). For the best performance, also make sure that IO Thread is enabled. * Configure your memory settings as needed, continue and set "VirtIO (paravirtualized)" as network device, finish your VM creation. * For the VirtIO drivers, upload the driver ISO (see [Windows VirtIO Drivers#virtio-win Releases](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers#virtio-win_Releases "Windows VirtIO Drivers") for information on how to download it) to your storage, create a new CDROM drive (use "Add -> CD/DVD drive" in the hardware tab) **with Bus "IDE" and number 0**. Load the Virtio Drivers ISO in the new virtual CDROM drive. * Now your ready to start the VM, just follow the Windows installer. * Note for Older Version of Windows like Windows-2012 (use the stable older version of VirtIO ISO - virtio-win-0.1.189.iso, [download it from here](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.189-1/virtio-win-0.1.189.iso) ) ### Launch Windows install * After starting your VM launch the noVNC console * Follow the installer steps until you reach the installation type selection where you need to select "Custom (advanced)" * Now click "Load driver" to install the VirtIO drivers for hard disk and the network. * Hard disk: Browse to the CD drive where you mounted the VirtIO driver and select folder "vioscsi\\2k16\\amd64" and confirm. Select the "Red Hat VirtIO SCSI pass-through controller" and click next to install it. Now you should see your drive. * Network: Repeat the steps from above (click again "Load driver", etc.) and select the folder "NetKVM\\2k16\\amd64", confirm it and select "Redhat VirtIO Ethernet Adapter" and click next. * Memory Ballooning: Again, repeat the steps but this time select the "Balloon\\2k16\\amd64" folder, then the "VirtIO Balloon Driver" and install it by clicking next. With these three drivers you should be good covered to run a fast virtualized Windows Server 2016 system. * Choose the drive and continue the Windows installer steps. **HINT:** There is a [video showing the process](https://www.proxmox.com/en/services/training-courses/videos/proxmox-virtual-environment/install-windows-2016-server-on-proxmox-ve) for a Windows Server 2016 installation which is the same as for Windows Server 2016. Install Guest Agent and Services -------------------------------- ### Guest Agent If you enabled the Qemu Agent option for the VM the mouse pointer will probably be off after the first boot. To remedy this install the "Qemu Guest Agent". The installer is located on the driver CD under guest-agent\\qemu-ga-x86\_64.msi. ### Drivers and Services [![](https://pve.proxmox.com/mediawiki/images/thumb/f/fd/Win10_virtio_guest_tool_installer.png/400px-Win10_virtio_guest_tool_installer.png)](https://pve.proxmox.com/wiki/File:Win10_virtio_guest_tool_installer.png) VirtIO guest tools installer The easiest way to install missing drivers and services is to use the provided MSI installer. It is available on the driver CD since version 0.1.173-2. Run the "virtio-win-gt-x64.msi" file located directly on the CD. If you do not plan to use [SPICE](https://pve.proxmox.com/wiki/SPICE "SPICE") you can deselect the "Qxl" and "Spice" features. Restart the VM after the installer is done. After all this the RAM usage and IP configuration should be shown correctly in the summary page of the VM. For more information and configuration about ballooning, see [Dynamic Memory Management](https://pve.proxmox.com/wiki/Dynamic_Memory_Management "Dynamic Memory Management") ### Check for missing drivers _See also: [Paravirtualized Block Drivers for Windows](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows "Paravirtualized Block Drivers for Windows") _ [![](https://pve.proxmox.com/mediawiki/images/thumb/9/9c/Win10_unknown_dev.png/400px-Win10_unknown_dev.png)](https://pve.proxmox.com/wiki/File:Win10_unknown_dev.png) Unknown device in device manager [![](https://pve.proxmox.com/mediawiki/images/thumb/5/5e/Win10_update_driver_cd_selection.png/400px-Win10_update_driver_cd_selection.png)](https://pve.proxmox.com/wiki/File:Win10_update_driver_cd_selection.png) Make sure to include subfolders Go to the Device Manager to see if there are any drivers missing. For any unknown device: * Right click an select "Update driver". * Select "Browse my computer for driver software". * Select the Driver CD. Make sure that "Include subfolders" is checked. * Once a driver has been found you might be prompted with a security warning asking if you "Would like to install this device software". Click "Install". ### Installing WSL(g) To run WSL (Windows Subsystem for Linux) you need to enable [Nested Virtualization](https://pve.proxmox.com/wiki/Nested_Virtualization "Nested Virtualization") . Make sure to set your processor to 'host'; if you already set up your VM and did not select 'host' as processor, you can change it in the 'Hardware' section of your VM in the web interface. Follow the [official instructions](https://learn.microsoft.com/en-us/windows/wsl/install) . If you are using a GPU via PCI(e) passthrough, you might need to add args: -cpu host,kvm=off to your config file at _/etc/pve/qemu-server/.conf_, see [the vfio blog](http://vfio.blogspot.com/2014/08/vfiovga-faq.html) Further information ------------------- ### Disk-Image Format: raw vs qcow2 Raw file format provides slightly better performance while qcow2 offers advanced features such as copy on write and [Live\_Snapshots](https://pve.proxmox.com/wiki/Live_Snapshots "Live Snapshots") . Since V2.3, qcow2 is the default format. ### VirtIO drivers Make it really easy: Build your ISO with drivers already included: [Windows guests - build ISOs including VirtIO drivers](https://pve.proxmox.com/wiki/Windows_guests_-_build_ISOs_including_VirtIO_drivers "Windows guests - build ISOs including VirtIO drivers") See also -------- [Windows 2012 guest best practices](https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices "Windows 2012 guest best practices") [Windows 10 guest best practices](https://pve.proxmox.com/wiki/Windows_10_guest_best_practices "Windows 10 guest best practices") Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Windows\_2016\_guest\_best\_practices&oldid=12488](https://pve.proxmox.com/mediawiki/index.php?title=Windows_2016_guest_best_practices&oldid=12488) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # User contributions for A.zeidler - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:User_contributions) User contributions for A.zeidler ================================ Results for [A.zeidler](https://pve.proxmox.com/mediawiki/index.php?title=User:A.zeidler&action=edit&redlink=1 "User:A.zeidler (page does not exist)") [talk](https://pve.proxmox.com/mediawiki/index.php?title=User_talk:A.zeidler&action=edit&redlink=1 "User talk:A.zeidler (page does not exist)") [block log](https://pve.proxmox.com/mediawiki/index.php?title=Special:Log/block&page=User%3AA.zeidler "Special:Log/block") [uploads](https://pve.proxmox.com/wiki/Special:ListFiles/A.zeidler "Special:ListFiles/A.zeidler") [logs](https://pve.proxmox.com/wiki/Special:Log/A.zeidler "Special:Log/A.zeidler") A user with 10 edits. Account created on 24 July 2023. [Jump to navigation](https://pve.proxmox.com/wiki/Special:Contributions/A.zeidler#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:Contributions/A.zeidler#searchInput) Search for contributionsExpandCollapse ⧼contribs-top⧽ IP address or username: Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection Associated namespace [Tag](https://pve.proxmox.com/wiki/Special:Tags "Special:Tags") filter: Manual revertNew redirectRemoved redirectReplacedRevertedRollbackUndoVisual edit: Switchedwikieditor (hidden tag) Invert selection Only show edits that are latest revisions Only show edits that are page creations Hide minor edits ⧼contribs-date⧽ From date: To date: Search #### 26 February 2025 * 11:27[11:27, 26 February 2025](https://pve.proxmox.com/mediawiki/index.php?title=Automated_Installation&oldid=12179 "Automated Installation") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Automated_Installation&diff=prev&oldid=12179 "Automated Installation") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Automated_Installation&action=history "Automated Installation") +8 m [Automated Installation](https://pve.proxmox.com/wiki/Automated_Installation "Automated Installation") Extend the sample passwords to meet the new minimum requirement of 8 characters. #### 18 September 2024 * 09:42[09:42, 18 September 2024](https://pve.proxmox.com/mediawiki/index.php?title=Tape_Drives&oldid=12023 "Tape Drives") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Tape_Drives&diff=prev&oldid=12023 "Tape Drives") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Tape_Drives&action=history "Tape Drives") −120 m [Tape Drives](https://pve.proxmox.com/wiki/Tape_Drives "Tape Drives") update and reorder notes current #### 18 December 2023 * 18:56[18:56, 18 December 2023](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Workstations_with_Proxmox_VE_and_X11&oldid=11902 "Developer Workstations with Proxmox VE and X11") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Workstations_with_Proxmox_VE_and_X11&diff=prev&oldid=11902 "Developer Workstations with Proxmox VE and X11") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Workstations_with_Proxmox_VE_and_X11&action=history "Developer Workstations with Proxmox VE and X11") +141 m [Developer Workstations with Proxmox VE and X11](https://pve.proxmox.com/wiki/Developer_Workstations_with_Proxmox_VE_and_X11 "Developer Workstations with Proxmox VE and X11") update sources.list * 18:37[18:37, 18 December 2023](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Workstations_with_Proxmox_VE_and_X11&oldid=11901 "Developer Workstations with Proxmox VE and X11") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Workstations_with_Proxmox_VE_and_X11&diff=prev&oldid=11901 "Developer Workstations with Proxmox VE and X11") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Workstations_with_Proxmox_VE_and_X11&action=history "Developer Workstations with Proxmox VE and X11") −32 m [Developer Workstations with Proxmox VE and X11](https://pve.proxmox.com/wiki/Developer_Workstations_with_Proxmox_VE_and_X11 "Developer Workstations with Proxmox VE and X11") apt-get -> apt #### 27 November 2023 * 17:36[17:36, 27 November 2023](https://pve.proxmox.com/mediawiki/index.php?title=Secure_Boot_Setup&oldid=11881 "Secure Boot Setup") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Secure_Boot_Setup&diff=prev&oldid=11881 "Secure Boot Setup") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Secure_Boot_Setup&action=history "Secure Boot Setup") +54 m [Secure Boot Setup](https://pve.proxmox.com/wiki/Secure_Boot_Setup "Secure Boot Setup") mention Backup Server #### 4 October 2023 * 16:30[16:30, 4 October 2023](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_7_to_8&oldid=11793 "Upgrade from 7 to 8") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_7_to_8&diff=prev&oldid=11793 "Upgrade from 7 to 8") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_7_to_8&action=history "Upgrade from 7 to 8") 0 m [Upgrade from 7 to 8](https://pve.proxmox.com/wiki/Upgrade_from_7_to_8 "Upgrade from 7 to 8") fix link #### 11 September 2023 * 12:05[12:05, 11 September 2023](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=11777 "Developer Documentation") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&diff=prev&oldid=11777 "Developer Documentation") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&action=history "Developer Documentation") +119 m [Developer Documentation](https://pve.proxmox.com/wiki/Developer_Documentation "Developer Documentation") add PVE 8 bookworm repo #### 28 August 2023 * 11:19[11:19, 28 August 2023](https://pve.proxmox.com/mediawiki/index.php?title=Windows_VirtIO_Drivers&oldid=11771 "Windows VirtIO Drivers") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Windows_VirtIO_Drivers&diff=prev&oldid=11771 "Windows VirtIO Drivers") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Windows_VirtIO_Drivers&action=history "Windows VirtIO Drivers") −5 m [Windows VirtIO Drivers](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers "Windows VirtIO Drivers") fix spelling * 10:26[10:26, 28 August 2023](https://pve.proxmox.com/mediawiki/index.php?title=Windows_VirtIO_Drivers&oldid=11770 "Windows VirtIO Drivers") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Windows_VirtIO_Drivers&diff=prev&oldid=11770 "Windows VirtIO Drivers") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Windows_VirtIO_Drivers&action=history "Windows VirtIO Drivers") −14 m [Windows VirtIO Drivers](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers "Windows VirtIO Drivers") fix link #### 24 July 2023 * 14:55[14:55, 24 July 2023](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=11759 "Developer Documentation") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&diff=prev&oldid=11759 "Developer Documentation") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&action=history "Developer Documentation") −15 m [Developer Documentation](https://pve.proxmox.com/wiki/Developer_Documentation "Developer Documentation") fix link Retrieved from "[https://pve.proxmox.com/wiki/Special:Contributions/A.zeidler](https://pve.proxmox.com/wiki/Special:Contributions/A.zeidler) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # User contributions for S.sterz - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:User_contributions) User contributions for S.sterz ============================== Results for [S.sterz](https://pve.proxmox.com/mediawiki/index.php?title=User:S.sterz&action=edit&redlink=1 "User:S.sterz (page does not exist)") [talk](https://pve.proxmox.com/mediawiki/index.php?title=User_talk:S.sterz&action=edit&redlink=1 "User talk:S.sterz (page does not exist)") [block log](https://pve.proxmox.com/mediawiki/index.php?title=Special:Log/block&page=User%3AS.sterz "Special:Log/block") [uploads](https://pve.proxmox.com/wiki/Special:ListFiles/S.sterz "Special:ListFiles/S.sterz") [logs](https://pve.proxmox.com/wiki/Special:Log/S.sterz "Special:Log/S.sterz") A user with 14 edits. Account created on 5 June 2025. [Jump to navigation](https://pve.proxmox.com/wiki/Special:Contributions/S.sterz#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:Contributions/S.sterz#searchInput) Search for contributionsExpandCollapse ⧼contribs-top⧽ IP address or username: Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection Associated namespace [Tag](https://pve.proxmox.com/wiki/Special:Tags "Special:Tags") filter: Manual revertNew redirectRemoved redirectReplacedRevertedRollbackUndoVisual edit: Switchedwikieditor (hidden tag) Invert selection Only show edits that are latest revisions Only show edits that are page creations Hide minor edits ⧼contribs-date⧽ From date: To date: Search #### 25 March 2026 * 11:20[11:20, 25 March 2026](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&oldid=12531 "Upgrade from 8 to 9") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&diff=prev&oldid=12531 "Upgrade from 8 to 9") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&action=history "Upgrade from 8 to 9") **+1,095** [Upgrade from 8 to 9](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9 "Upgrade from 8 to 9") [→Host PCI passthrough with kernel 6.14 for virtual machines sometimes broken](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Host_PCI_passthrough_with_kernel_6.14_for_virtual_machines_sometimes_broken "Upgrade from 8 to 9") : add section on /etc/sysctl.conf no longer being read current #### 19 March 2026 * 10:20[10:20, 19 March 2026](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_Datacenter_Manager_Roadmap&oldid=12523 "Proxmox Datacenter Manager Roadmap") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_Datacenter_Manager_Roadmap&diff=prev&oldid=12523 "Proxmox Datacenter Manager Roadmap") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_Datacenter_Manager_Roadmap&action=history "Proxmox Datacenter Manager Roadmap") −1 m [Proxmox Datacenter Manager Roadmap](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap "Proxmox Datacenter Manager Roadmap") fix typo current * 10:19[10:19, 19 March 2026](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_Datacenter_Manager_Roadmap&oldid=12522 "Proxmox Datacenter Manager Roadmap") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_Datacenter_Manager_Roadmap&diff=prev&oldid=12522 "Proxmox Datacenter Manager Roadmap") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_Datacenter_Manager_Roadmap&action=history "Proxmox Datacenter Manager Roadmap") +227 [Proxmox Datacenter Manager Roadmap](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap "Proxmox Datacenter Manager Roadmap") add note that the current roadmap is part of pdm's documentation #### 11 September 2025 * 12:23[12:23, 11 September 2025](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1&oldid=12358 "Proxmox Datacenter Manager Upgrade from Alpha to 1") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1&diff=prev&oldid=12358 "Proxmox Datacenter Manager Upgrade from Alpha to 1") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1&action=history "Proxmox Datacenter Manager Upgrade from Alpha to 1") +226 [Proxmox Datacenter Manager Upgrade from Alpha to 1](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1 "Proxmox Datacenter Manager Upgrade from Alpha to 1") add back missing beta sticky note * 12:18[12:18, 11 September 2025](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1&oldid=12357 "Proxmox Datacenter Manager Upgrade from Alpha to 1") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1&diff=prev&oldid=12357 "Proxmox Datacenter Manager Upgrade from Alpha to 1") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1&action=history "Proxmox Datacenter Manager Upgrade from Alpha to 1") +40 [Proxmox Datacenter Manager Upgrade from Alpha to 1](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1 "Proxmox Datacenter Manager Upgrade from Alpha to 1") add back missing category * 12:17[12:17, 11 September 2025](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1&oldid=12356 "Proxmox Datacenter Manager Upgrade from Alpha to 1") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1&diff=prev&oldid=12356 "Proxmox Datacenter Manager Upgrade from Alpha to 1") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1&action=history "Proxmox Datacenter Manager Upgrade from Alpha to 1") **+14,461** [Proxmox Datacenter Manager Upgrade from Alpha to 1](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_1 "Proxmox Datacenter Manager Upgrade from Alpha to 1") No edit summary #### 25 August 2025 * 15:10[15:10, 25 August 2025](https://pve.proxmox.com/mediawiki/index.php?title=Install_Proxmox_VE_on_Debian_13_Trixie&oldid=12339 "Install Proxmox VE on Debian 13 Trixie") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Install_Proxmox_VE_on_Debian_13_Trixie&diff=prev&oldid=12339 "Install Proxmox VE on Debian 13 Trixie") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Install_Proxmox_VE_on_Debian_13_Trixie&action=history "Install Proxmox VE on Debian 13 Trixie") −23 [Install Proxmox VE on Debian 13 Trixie](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie "Install Proxmox VE on Debian 13 Trixie") [→Add Proxmox VE Repository](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie#Add_Proxmox_VE_Repository "Install Proxmox VE on Debian 13 Trixie") : remove the mispellect "Archtechtures" as we don't use it anywhere else either current #### 5 August 2025 * 07:47[07:47, 5 August 2025](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&oldid=12278 "Upgrade from 8 to 9") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&diff=prev&oldid=12278 "Upgrade from 8 to 9") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&action=history "Upgrade from 8 to 9") 0 m [Upgrade from 8 to 9](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9 "Upgrade from 8 to 9") [→Update Debian Base Repositories to Trixie](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Update_Debian_Base_Repositories_to_Trixie "Upgrade from 8 to 9") : fix displayed package repository link, media wiki replaces spaces with underscores anyway * 07:43[07:43, 5 August 2025](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&oldid=12277 "Upgrade from 8 to 9") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&diff=prev&oldid=12277 "Upgrade from 8 to 9") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&action=history "Upgrade from 8 to 9") +1 m [Upgrade from 8 to 9](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9 "Upgrade from 8 to 9") [→Update the configured APT repositories](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Update_the_configured_APT_repositories "Upgrade from 8 to 9") : fix typo Suid -> Squid #### 1 August 2025 * 13:16[13:16, 1 August 2025](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&oldid=12274 "Developer Documentation") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&diff=prev&oldid=12274 "Developer Documentation") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Developer_Documentation&action=history "Developer Documentation") +294 [Developer Documentation](https://pve.proxmox.com/wiki/Developer_Documentation "Developer Documentation") [→Preparing Patches](https://pve.proxmox.com/wiki/Developer_Documentation#Preparing_Patches "Developer Documentation") : add an explainer as to why a cover letter is useful * 12:43[12:43, 1 August 2025](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&oldid=12273 "Upgrade from 8 to 9") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&diff=prev&oldid=12273 "Upgrade from 8 to 9") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&action=history "Upgrade from 8 to 9") +394 [Upgrade from 8 to 9](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9 "Upgrade from 8 to 9") [→Update the configured APT repositories](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Update_the_configured_APT_repositories "Upgrade from 8 to 9") : add note about updating to ceph squid before editing apt repos * 12:31[12:31, 1 August 2025](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&oldid=12272 "Upgrade from 8 to 9") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&diff=prev&oldid=12272 "Upgrade from 8 to 9") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&action=history "Upgrade from 8 to 9") **+592** [Upgrade from 8 to 9](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9 "Upgrade from 8 to 9") [→Update the Ceph Package Repository](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Update_the_Ceph_Package_Repository "Upgrade from 8 to 9") : update on how to use apt policy correctly * 12:25[12:25, 1 August 2025](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&oldid=12271 "Upgrade from 8 to 9") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&diff=prev&oldid=12271 "Upgrade from 8 to 9") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&action=history "Upgrade from 8 to 9") **+501** [Upgrade from 8 to 9](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9 "Upgrade from 8 to 9") [→Add the Proxmox VE 9 Package Repository](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Add_the_Proxmox_VE_9_Package_Repository "Upgrade from 8 to 9") #### 5 June 2025 * 12:47[12:47, 5 June 2025](https://pve.proxmox.com/mediawiki/index.php?title=Javascript_Style_Guide&oldid=12234 "Javascript Style Guide") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Javascript_Style_Guide&diff=prev&oldid=12234 "Javascript Style Guide") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Javascript_Style_Guide&action=history "Javascript Style Guide") +497 [Javascript Style Guide](https://pve.proxmox.com/wiki/Javascript_Style_Guide "Javascript Style Guide") add a note about the introduction of biome Retrieved from "[https://pve.proxmox.com/wiki/Special:Contributions/S.sterz](https://pve.proxmox.com/wiki/Special:Contributions/S.sterz) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # User contributions for L.Leahu-Vladucu - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:User_contributions) User contributions for L.Leahu-Vladucu ====================================== Results for [L.Leahu-Vladucu](https://pve.proxmox.com/mediawiki/index.php?title=User:L.Leahu-Vladucu&action=edit&redlink=1 "User:L.Leahu-Vladucu (page does not exist)") [talk](https://pve.proxmox.com/mediawiki/index.php?title=User_talk:L.Leahu-Vladucu&action=edit&redlink=1 "User talk:L.Leahu-Vladucu (page does not exist)") [block log](https://pve.proxmox.com/mediawiki/index.php?title=Special:Log/block&page=User%3AL.Leahu-Vladucu "Special:Log/block") [uploads](https://pve.proxmox.com/wiki/Special:ListFiles/L.Leahu-Vladucu "Special:ListFiles/L.Leahu-Vladucu") [logs](https://pve.proxmox.com/wiki/Special:Log/L.Leahu-Vladucu "Special:Log/L.Leahu-Vladucu") A user with 16 edits. Account created on 16 December 2024. [Jump to navigation](https://pve.proxmox.com/wiki/Special:Contributions/L.Leahu-Vladucu#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:Contributions/L.Leahu-Vladucu#searchInput) Search for contributionsExpandCollapse ⧼contribs-top⧽ IP address or username: Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection Associated namespace [Tag](https://pve.proxmox.com/wiki/Special:Tags "Special:Tags") filter: Manual revertNew redirectRemoved redirectReplacedRevertedRollbackUndoVisual edit: Switchedwikieditor (hidden tag) Invert selection Only show edits that are latest revisions Only show edits that are page creations Hide minor edits ⧼contribs-date⧽ From date: To date: Search #### 27 March 2026 * 07:33[07:33, 27 March 2026](https://pve.proxmox.com/mediawiki/index.php?title=Full_Mesh_Network_for_Ceph_Server&oldid=12533 "Full Mesh Network for Ceph Server") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Full_Mesh_Network_for_Ceph_Server&diff=prev&oldid=12533 "Full Mesh Network for Ceph Server") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Full_Mesh_Network_for_Ceph_Server&action=history "Full Mesh Network for Ceph Server") −1 m [Full Mesh Network for Ceph Server](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server "Full Mesh Network for Ceph Server") Fixed typo (protocoll) current #### 16 December 2025 * 10:29[10:29, 16 December 2025](https://pve.proxmox.com/mediawiki/index.php?title=PCI_Passthrough&oldid=12451 "PCI Passthrough") [diff](https://pve.proxmox.com/mediawiki/index.php?title=PCI_Passthrough&diff=prev&oldid=12451 "PCI Passthrough") [hist](https://pve.proxmox.com/mediawiki/index.php?title=PCI_Passthrough&action=history "PCI Passthrough") **+1,053** [PCI Passthrough](https://pve.proxmox.com/wiki/PCI_Passthrough "PCI Passthrough") Added info on workaround for "BAR0 is 0M" errors #### 3 September 2025 * 12:44[12:44, 3 September 2025](https://pve.proxmox.com/mediawiki/index.php?title=PCI_Passthrough&oldid=12341 "PCI Passthrough") [diff](https://pve.proxmox.com/mediawiki/index.php?title=PCI_Passthrough&diff=prev&oldid=12341 "PCI Passthrough") [hist](https://pve.proxmox.com/mediawiki/index.php?title=PCI_Passthrough&action=history "PCI Passthrough") +1 m [PCI Passthrough](https://pve.proxmox.com/wiki/PCI_Passthrough "PCI Passthrough") No edit summary #### 28 July 2025 * 07:50[07:50, 28 July 2025](https://pve.proxmox.com/mediawiki/index.php?title=Paravirtualized_Block_Drivers_for_Windows&oldid=12269 "Paravirtualized Block Drivers for Windows") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Paravirtualized_Block_Drivers_for_Windows&diff=prev&oldid=12269 "Paravirtualized Block Drivers for Windows") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Paravirtualized_Block_Drivers_for_Windows&action=history "Paravirtualized Block Drivers for Windows") +1 [Paravirtualized Block Drivers for Windows](https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows "Paravirtualized Block Drivers for Windows") No edit summary #### 25 July 2025 * 09:56[09:56, 25 July 2025](https://pve.proxmox.com/mediawiki/index.php?title=Template:WinX-install-steps&oldid=12267 "Template:WinX-install-steps") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Template:WinX-install-steps&diff=prev&oldid=12267 "Template:WinX-install-steps") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Template:WinX-install-steps&action=history "Template:WinX-install-steps") +75 [Template:WinX-install-steps](https://pve.proxmox.com/wiki/Template:WinX-install-steps "Template:WinX-install-steps") No edit summary #### 24 June 2025 * 09:45[09:45, 24 June 2025](https://pve.proxmox.com/mediawiki/index.php?title=Performance_Tweaks&oldid=12235 "Performance Tweaks") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Performance_Tweaks&diff=prev&oldid=12235 "Performance Tweaks") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Performance_Tweaks&action=history "Performance Tweaks") −1 [Performance Tweaks](https://pve.proxmox.com/wiki/Performance_Tweaks "Performance Tweaks") No edit summary current #### 10 March 2025 * 10:46[10:46, 10 March 2025](https://pve.proxmox.com/mediawiki/index.php?title=Template:WinX-install-steps&oldid=12189 "Template:WinX-install-steps") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Template:WinX-install-steps&diff=prev&oldid=12189 "Template:WinX-install-steps") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Template:WinX-install-steps&action=history "Template:WinX-install-steps") +34 [Template:WinX-install-steps](https://pve.proxmox.com/wiki/Template:WinX-install-steps "Template:WinX-install-steps") No edit summary #### 4 February 2025 * 14:07[14:07, 4 February 2025](https://pve.proxmox.com/mediawiki/index.php?title=Template:WinX-install-steps&oldid=12136 "Template:WinX-install-steps") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Template:WinX-install-steps&diff=prev&oldid=12136 "Template:WinX-install-steps") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Template:WinX-install-steps&action=history "Template:WinX-install-steps") +31 [Template:WinX-install-steps](https://pve.proxmox.com/wiki/Template:WinX-install-steps "Template:WinX-install-steps") No edit summary #### 30 January 2025 * 08:42[08:42, 30 January 2025](https://pve.proxmox.com/mediawiki/index.php?title=Javascript_Style_Guide&oldid=12127 "Javascript Style Guide") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Javascript_Style_Guide&diff=prev&oldid=12127 "Javascript Style Guide") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Javascript_Style_Guide&action=history "Javascript Style Guide") +12 [Javascript Style Guide](https://pve.proxmox.com/wiki/Javascript_Style_Guide "Javascript Style Guide") No edit summary #### 16 December 2024 * 09:28[09:28, 16 December 2024](https://pve.proxmox.com/mediawiki/index.php?title=Windows_2022_guest_best_practices&oldid=12105 "Windows 2022 guest best practices") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Windows_2022_guest_best_practices&diff=prev&oldid=12105 "Windows 2022 guest best practices") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Windows_2022_guest_best_practices&action=history "Windows 2022 guest best practices") +37 m [Windows 2022 guest best practices](https://pve.proxmox.com/wiki/Windows_2022_guest_best_practices "Windows 2022 guest best practices") No edit summary * 09:26[09:26, 16 December 2024](https://pve.proxmox.com/mediawiki/index.php?title=Windows_2025_guest_best_practices&oldid=12104 "Windows 2025 guest best practices") diff [hist](https://pve.proxmox.com/mediawiki/index.php?title=Windows_2025_guest_best_practices&action=history "Windows 2025 guest best practices") **+940** N [Windows 2025 guest best practices](https://pve.proxmox.com/wiki/Windows_2025_guest_best_practices "Windows 2025 guest best practices") Created page with " ==Introduction== This is a set of best practices to follow when installing a Windows Server 2025 guest on a Proxmox VE server 8.x. {{WinX-install-steps|osversion=Server 2025|osgroup=11/2022/2025|driverdir=2k25}} ==Further information== ===Disk-Image Format: raw vs qcow2=== Raw file format provides slightly better performance while qcow2 offers advanced features such as copy on write and [Live\_Snapshots](https://pve.proxmox.com/wiki/Live_Snapshots "Live Snapshots") . Since V2.3, qcow2 is the default format. ===VirtIO drivers===..." * 09:24[09:24, 16 December 2024](https://pve.proxmox.com/mediawiki/index.php?title=Windows_11_guest_best_practices&oldid=12103 "Windows 11 guest best practices") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Windows_11_guest_best_practices&diff=prev&oldid=12103 "Windows 11 guest best practices") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Windows_11_guest_best_practices&action=history "Windows 11 guest best practices") 0 m [Windows 11 guest best practices](https://pve.proxmox.com/wiki/Windows_11_guest_best_practices "Windows 11 guest best practices") No edit summary * 09:19[09:19, 16 December 2024](https://pve.proxmox.com/mediawiki/index.php?title=Windows_11_guest_best_practices&oldid=12102 "Windows 11 guest best practices") diff [hist](https://pve.proxmox.com/mediawiki/index.php?title=Windows_11_guest_best_practices&action=history "Windows 11 guest best practices") **+884** N [Windows 11 guest best practices](https://pve.proxmox.com/wiki/Windows_11_guest_best_practices "Windows 11 guest best practices") Created page with " ==Introduction== This is a set of best practices to follow when installing a Windows 10 guest on a Proxmox VE server 8.x. {{WinX-install-steps|osversion=11|osgroup=11/2022/2025|driverdir=w11}} ==Further information== ===Disk-Image Format: raw vs qcow2=== Raw file format provides slightly better performance while qcow2 offers advanced features such as copy on write and [Live\_Snapshots](https://pve.proxmox.com/wiki/Live_Snapshots "Live Snapshots") . Since V2.3, qcow2 is the default format. ===VirtIO drivers=== Make it really ea..." * 09:17[09:17, 16 December 2024](https://pve.proxmox.com/mediawiki/index.php?title=Windows_2022_guest_best_practices&oldid=12101 "Windows 2022 guest best practices") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Windows_2022_guest_best_practices&diff=prev&oldid=12101 "Windows 2022 guest best practices") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Windows_2022_guest_best_practices&action=history "Windows 2022 guest best practices") 0 m [Windows 2022 guest best practices](https://pve.proxmox.com/wiki/Windows_2022_guest_best_practices "Windows 2022 guest best practices") No edit summary * 09:16[09:16, 16 December 2024](https://pve.proxmox.com/mediawiki/index.php?title=Windows_2022_guest_best_practices&oldid=12100 "Windows 2022 guest best practices") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Windows_2022_guest_best_practices&diff=prev&oldid=12100 "Windows 2022 guest best practices") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Windows_2022_guest_best_practices&action=history "Windows 2022 guest best practices") +5 m [Windows 2022 guest best practices](https://pve.proxmox.com/wiki/Windows_2022_guest_best_practices "Windows 2022 guest best practices") No edit summary * 09:13[09:13, 16 December 2024](https://pve.proxmox.com/mediawiki/index.php?title=Windows_2022_guest_best_practices&oldid=12099 "Windows 2022 guest best practices") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Windows_2022_guest_best_practices&diff=prev&oldid=12099 "Windows 2022 guest best practices") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Windows_2022_guest_best_practices&action=history "Windows 2022 guest best practices") 0 [Windows 2022 guest best practices](https://pve.proxmox.com/wiki/Windows_2022_guest_best_practices "Windows 2022 guest best practices") No edit summary Retrieved from "[https://pve.proxmox.com/wiki/Special:Contributions/L.Leahu-Vladucu](https://pve.proxmox.com/wiki/Special:Contributions/L.Leahu-Vladucu) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # User contributions for A.lauterer - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:User_contributions) User contributions for A.lauterer ================================= Results for [A.lauterer](https://pve.proxmox.com/mediawiki/index.php?title=User:A.lauterer&action=edit&redlink=1 "User:A.lauterer (page does not exist)") [talk](https://pve.proxmox.com/mediawiki/index.php?title=User_talk:A.lauterer&action=edit&redlink=1 "User talk:A.lauterer (page does not exist)") [block log](https://pve.proxmox.com/mediawiki/index.php?title=Special:Log/block&page=User%3AA.lauterer "Special:Log/block") [uploads](https://pve.proxmox.com/wiki/Special:ListFiles/A.lauterer "Special:ListFiles/A.lauterer") [logs](https://pve.proxmox.com/wiki/Special:Log/A.lauterer "Special:Log/A.lauterer") A user with 133 edits. Account created on 21 August 2019. [Jump to navigation](https://pve.proxmox.com/wiki/Special:Contributions/A.lauterer#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:Contributions/A.lauterer#searchInput) Search for contributionsExpandCollapse ⧼contribs-top⧽ IP address or username: Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk Invert selection Associated namespace [Tag](https://pve.proxmox.com/wiki/Special:Tags "Special:Tags") filter: Manual revertNew redirectRemoved redirectReplacedRevertedRollbackUndoVisual edit: Switchedwikieditor (hidden tag) Invert selection Only show edits that are latest revisions Only show edits that are page creations Hide minor edits ⧼contribs-date⧽ From date: To date: Search (newest | [oldest](https://pve.proxmox.com/mediawiki/index.php?title=Special:Contributions/A.lauterer&target=A.lauterer&dir=prev) ) View (newer 50 | [older 50](https://pve.proxmox.com/mediawiki/index.php?title=Special:Contributions/A.lauterer&target=A.lauterer&offset=20240503132024) ) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:Contributions/A.lauterer&target=A.lauterer&offset=&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:Contributions/A.lauterer&target=A.lauterer&offset=&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:Contributions/A.lauterer&target=A.lauterer&offset=&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:Contributions/A.lauterer&target=A.lauterer&offset=&limit=500) ) #### 18 February 2026 * 11:44[11:44, 18 February 2026](https://pve.proxmox.com/mediawiki/index.php?title=Stretch_Cluster&oldid=12518 "Stretch Cluster") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Stretch_Cluster&diff=prev&oldid=12518 "Stretch Cluster") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Stretch_Cluster&action=history "Stretch Cluster") **+1,482** [Stretch Cluster](https://pve.proxmox.com/wiki/Stretch_Cluster "Stretch Cluster") add scope and network redundancy requirements, smaller grammer and phrasing fixes #### 26 January 2026 * 10:25[10:25, 26 January 2026](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Reef_to_Squid&oldid=12479 "Ceph Reef to Squid") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Reef_to_Squid&diff=prev&oldid=12479 "Ceph Reef to Squid") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Reef_to_Squid&action=history "Ceph Reef to Squid") +1 m [Ceph Reef to Squid](https://pve.proxmox.com/wiki/Ceph_Reef_to_Squid "Ceph Reef to Squid") [→Disallow pre-Reef OSDs and enable all new Squid-only functionality](https://pve.proxmox.com/wiki/Ceph_Reef_to_Squid#Disallow_pre-Reef_OSDs_and_enable_all_new_Squid-only_functionality "Ceph Reef to Squid") : fix headline current #### 12 January 2026 * 10:56[10:56, 12 January 2026](https://pve.proxmox.com/mediawiki/index.php?title=Split_lock_detection&oldid=12457 "Split lock detection") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Split_lock_detection&diff=prev&oldid=12457 "Split lock detection") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Split_lock_detection&action=history "Split lock detection") +134 [Split lock detection](https://pve.proxmox.com/wiki/Split_lock_detection "Split lock detection") add example on how to search for split\_lock in journal current * 10:55[10:55, 12 January 2026](https://pve.proxmox.com/mediawiki/index.php?title=Split_lock_detection&oldid=12456 "Split lock detection") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Split_lock_detection&diff=prev&oldid=12456 "Split lock detection") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Split_lock_detection&action=history "Split lock detection") +10 m [Split lock detection](https://pve.proxmox.com/wiki/Split_lock_detection "Split lock detection") indent pre blocks as elements of the list #### 12 December 2025 * 17:48[17:48, 12 December 2025](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Reef_to_Squid&oldid=12450 "Ceph Reef to Squid") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Reef_to_Squid&diff=prev&oldid=12450 "Ceph Reef to Squid") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Reef_to_Squid&action=history "Ceph Reef to Squid") +375 [Ceph Reef to Squid](https://pve.proxmox.com/wiki/Ceph_Reef_to_Squid "Ceph Reef to Squid") Undo revision 12449 by [A.lauterer](https://pve.proxmox.com/wiki/Special:Contributions/A.lauterer "Special:Contributions/A.lauterer") ([talk](https://pve.proxmox.com/mediawiki/index.php?title=User_talk:A.lauterer&action=edit&redlink=1 "User talk:A.lauterer (page does not exist)") ) [Tag](https://pve.proxmox.com/wiki/Special:Tags "Special:Tags") : Undo * 17:48[17:48, 12 December 2025](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Reef_to_Squid&oldid=12449 "Ceph Reef to Squid") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Reef_to_Squid&diff=prev&oldid=12449 "Ceph Reef to Squid") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Reef_to_Squid&action=history "Ceph Reef to Squid") −375 [Ceph Reef to Squid](https://pve.proxmox.com/wiki/Ceph_Reef_to_Squid "Ceph Reef to Squid") [→Upgrade all CephFS MDS daemons](https://pve.proxmox.com/wiki/Ceph_Reef_to_Squid#Upgrade_all_CephFS_MDS_daemons "Ceph Reef to Squid") : mention to restore allow\_standby\_replay [Tags](https://pve.proxmox.com/wiki/Special:Tags "Special:Tags") : Manual revert Reverted #### 2 December 2025 * 13:30[13:30, 2 December 2025](https://pve.proxmox.com/mediawiki/index.php?title=Stretch_Cluster&oldid=12438 "Stretch Cluster") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Stretch_Cluster&diff=prev&oldid=12438 "Stretch Cluster") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Stretch_Cluster&action=history "Stretch Cluster") +181 [Stretch Cluster](https://pve.proxmox.com/wiki/Stretch_Cluster "Stretch Cluster") add note about different physical paths for network interconnect for better redundancy * 12:54[12:54, 2 December 2025](https://pve.proxmox.com/mediawiki/index.php?title=Stretch_Cluster&oldid=12437 "Stretch Cluster") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Stretch_Cluster&diff=prev&oldid=12437 "Stretch Cluster") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Stretch_Cluster&action=history "Stretch Cluster") +6 m [Stretch Cluster](https://pve.proxmox.com/wiki/Stretch_Cluster "Stretch Cluster") [→Tie-Breaker Node](https://pve.proxmox.com/wiki/Stretch_Cluster#Tie-Breaker_Node "Stretch Cluster") : fix internal anchor link * 12:53[12:53, 2 December 2025](https://pve.proxmox.com/mediawiki/index.php?title=Stretch_Cluster&oldid=12436 "Stretch Cluster") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Stretch_Cluster&diff=prev&oldid=12436 "Stretch Cluster") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Stretch_Cluster&action=history "Stretch Cluster") −16 [Stretch Cluster](https://pve.proxmox.com/wiki/Stretch_Cluster "Stretch Cluster") [→Tie-Breaker Node](https://pve.proxmox.com/wiki/Stretch_Cluster#Tie-Breaker_Node "Stretch Cluster") * 09:40[09:40, 2 December 2025](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Quincy_to_Reef&oldid=12435 "Ceph Quincy to Reef") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Quincy_to_Reef&diff=prev&oldid=12435 "Ceph Quincy to Reef") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Quincy_to_Reef&action=history "Ceph Quincy to Reef") +220 [Ceph Quincy to Reef](https://pve.proxmox.com/wiki/Ceph_Quincy_to_Reef "Ceph Quincy to Reef") [→Restart the monitor daemon](https://pve.proxmox.com/wiki/Ceph_Quincy_to_Reef#Restart_the_monitor_daemon "Ceph Quincy to Reef") : add note about mgrs becoming unresponsive * 09:35[09:35, 2 December 2025](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Quincy_to_Reef&oldid=12434 "Ceph Quincy to Reef") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Quincy_to_Reef&diff=prev&oldid=12434 "Ceph Quincy to Reef") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Quincy_to_Reef&action=history "Ceph Quincy to Reef") +283 [Ceph Quincy to Reef](https://pve.proxmox.com/wiki/Ceph_Quincy_to_Reef "Ceph Quincy to Reef") [→Upgrade all CephFS MDS daemons](https://pve.proxmox.com/wiki/Ceph_Quincy_to_Reef#Upgrade_all_CephFS_MDS_daemons "Ceph Quincy to Reef") : mention to re-enable allow\_standby\_replay * 09:31[09:31, 2 December 2025](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Reef_to_Squid&oldid=12433 "Ceph Reef to Squid") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Reef_to_Squid&diff=prev&oldid=12433 "Ceph Reef to Squid") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Reef_to_Squid&action=history "Ceph Reef to Squid") +375 [Ceph Reef to Squid](https://pve.proxmox.com/wiki/Ceph_Reef_to_Squid "Ceph Reef to Squid") mention to re-enable allow\_standby\_replay [Tag](https://pve.proxmox.com/wiki/Special:Tags "Special:Tags") : Reverted #### 28 November 2025 * 12:15[12:15, 28 November 2025](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&oldid=12432 "Migrate to Proxmox VE") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&diff=prev&oldid=12432 "Migrate to Proxmox VE") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&action=history "Migrate to Proxmox VE") +162 [Migrate to Proxmox VE](https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE "Migrate to Proxmox VE") update with additional infos regarding TPM snapshots with qcow2 current #### 25 November 2025 * 17:33[17:33, 25 November 2025](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&oldid=12429 "Migrate to Proxmox VE") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&diff=prev&oldid=12429 "Migrate to Proxmox VE") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&action=history "Migrate to Proxmox VE") +291 [Migrate to Proxmox VE](https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE "Migrate to Proxmox VE") update to document the current snapshot situation as of Proxmox VE 9.1 * 17:32[17:32, 25 November 2025](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&oldid=12428 "Migrate to Proxmox VE") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&diff=prev&oldid=12428 "Migrate to Proxmox VE") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&action=history "Migrate to Proxmox VE") **+586** [Migrate to Proxmox VE](https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE "Migrate to Proxmox VE") [→Attach Disk & Move Disk (minimal downtime)](https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE#Attach_Disk_&_Move_Disk_(minimal_downtime) "Migrate to Proxmox VE") : update with diagrams and explicit step to power down source VM * 17:24[17:24, 25 November 2025](https://pve.proxmox.com/mediawiki/index.php?title=File:Vmware-adv-final.png&oldid=12427 "File:Vmware-adv-final.png") diff [hist](https://pve.proxmox.com/mediawiki/index.php?title=File:Vmware-adv-final.png&action=history "File:Vmware-adv-final.png") +59 N [File:Vmware-adv-final.png](https://pve.proxmox.com/wiki/File:Vmware-adv-final.png "File:Vmware-adv-final.png") VMware Migration to Proxmox VE via NFS, step4 current * 17:24[17:24, 25 November 2025](https://pve.proxmox.com/mediawiki/index.php?title=File:Vmware-adv-cp.png&oldid=12426 "File:Vmware-adv-cp.png") diff [hist](https://pve.proxmox.com/mediawiki/index.php?title=File:Vmware-adv-cp.png&action=history "File:Vmware-adv-cp.png") +59 N [File:Vmware-adv-cp.png](https://pve.proxmox.com/wiki/File:Vmware-adv-cp.png "File:Vmware-adv-cp.png") VMware Migration to Proxmox VE via NFS, step3 current * 17:24[17:24, 25 November 2025](https://pve.proxmox.com/mediawiki/index.php?title=File:Vmware-adv-create-vm.png&oldid=12425 "File:Vmware-adv-create-vm.png") diff [hist](https://pve.proxmox.com/mediawiki/index.php?title=File:Vmware-adv-create-vm.png&action=history "File:Vmware-adv-create-vm.png") +59 N [File:Vmware-adv-create-vm.png](https://pve.proxmox.com/wiki/File:Vmware-adv-create-vm.png "File:Vmware-adv-create-vm.png") VMware Migration to Proxmox VE via NFS, step2 current * 17:23[17:23, 25 November 2025](https://pve.proxmox.com/mediawiki/index.php?title=File:Vmware-adv-start.png&oldid=12424 "File:Vmware-adv-start.png") diff [hist](https://pve.proxmox.com/mediawiki/index.php?title=File:Vmware-adv-start.png&action=history "File:Vmware-adv-start.png") +59 N [File:Vmware-adv-start.png](https://pve.proxmox.com/wiki/File:Vmware-adv-start.png "File:Vmware-adv-start.png") VMware Migration to Proxmox VE via NFS, step1 current #### 10 November 2025 * 13:58[13:58, 10 November 2025](https://pve.proxmox.com/mediawiki/index.php?title=Stretch_Cluster&oldid=12396 "Stretch Cluster") diff [hist](https://pve.proxmox.com/mediawiki/index.php?title=Stretch_Cluster&action=history "Stretch Cluster") **+15,731** N [Stretch Cluster](https://pve.proxmox.com/wiki/Stretch_Cluster "Stretch Cluster") moved to public with some small tiny changes #### 21 August 2025 * 07:46[07:46, 21 August 2025](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&oldid=12338 "Migrate to Proxmox VE") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&diff=prev&oldid=12338 "Migrate to Proxmox VE") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&action=history "Migrate to Proxmox VE") **+951** [Migrate to Proxmox VE](https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE "Migrate to Proxmox VE") expand on snapshots on shared block storage, mention snapshot chains #### 12 August 2025 * 08:44[08:44, 12 August 2025](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&oldid=12336 "Upgrade from 8 to 9") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&diff=prev&oldid=12336 "Upgrade from 8 to 9") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&action=history "Upgrade from 8 to 9") +2 m [Upgrade from 8 to 9](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9 "Upgrade from 8 to 9") [→Existing Ceph Full Mesh Setups fail to boot](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Existing_Ceph_Full_Mesh_Setups_fail_to_boot "Upgrade from 8 to 9") : link to full mesh guide * 08:43[08:43, 12 August 2025](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&oldid=12335 "Upgrade from 8 to 9") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&diff=prev&oldid=12335 "Upgrade from 8 to 9") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&action=history "Upgrade from 8 to 9") **+572** [Upgrade from 8 to 9](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9 "Upgrade from 8 to 9") [→Network](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Network "Upgrade from 8 to 9") : add note regarding full-mesh FRR setups * 08:41[08:41, 12 August 2025](https://pve.proxmox.com/mediawiki/index.php?title=Full_Mesh_Network_for_Ceph_Server&oldid=12334 "Full Mesh Network for Ceph Server") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Full_Mesh_Network_for_Ceph_Server&diff=prev&oldid=12334 "Full Mesh Network for Ceph Server") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Full_Mesh_Network_for_Ceph_Server&action=history "Full Mesh Network for Ceph Server") +92 [Full Mesh Network for Ceph Server](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server "Full Mesh Network for Ceph Server") add hints regarding pve8 - pve9 differences for network config with FRR * 08:32[08:32, 12 August 2025](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&oldid=12333 "Upgrade from 8 to 9") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&diff=prev&oldid=12333 "Upgrade from 8 to 9") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&action=history "Upgrade from 8 to 9") +44 m [Upgrade from 8 to 9](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9 "Upgrade from 8 to 9") [→VM Memory Consumption Shown is Higher](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#VM_Memory_Consumption_Shown_is_Higher "Upgrade from 8 to 9") #### 8 August 2025 * 13:31[13:31, 8 August 2025](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&oldid=12331 "Upgrade from 8 to 9") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&diff=prev&oldid=12331 "Upgrade from 8 to 9") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&action=history "Upgrade from 8 to 9") −2 m [Upgrade from 8 to 9](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9 "Upgrade from 8 to 9") [→VM Memory Consumption Shown is Higher](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#VM_Memory_Consumption_Shown_is_Higher "Upgrade from 8 to 9") : fix name of BalloonService as it is shown in window' Services * 09:46[09:46, 8 August 2025](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&oldid=12329 "Upgrade from 8 to 9") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&diff=prev&oldid=12329 "Upgrade from 8 to 9") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&action=history "Upgrade from 8 to 9") +5 m [Upgrade from 8 to 9](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9 "Upgrade from 8 to 9") [→Known Upgrade Issues](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Known_Upgrade_Issues "Upgrade from 8 to 9") * 09:45[09:45, 8 August 2025](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&oldid=12328 "Upgrade from 8 to 9") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&diff=prev&oldid=12328 "Upgrade from 8 to 9") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Upgrade_from_8_to_9&action=history "Upgrade from 8 to 9") **+1,210** [Upgrade from 8 to 9](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9 "Upgrade from 8 to 9") [→Known Upgrade Issues](https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Known_Upgrade_Issues "Upgrade from 8 to 9") : add section why mem usage might be higher and over 100% after the upgrade #### 8 July 2025 * 14:19[14:19, 8 July 2025](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&oldid=12245 "Migrate to Proxmox VE") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&diff=prev&oldid=12245 "Migrate to Proxmox VE") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&action=history "Migrate to Proxmox VE") +359 [Migrate to Proxmox VE](https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE "Migrate to Proxmox VE") [→VirtIO Guest Drivers](https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE#VirtIO_Guest_Drivers "Migrate to Proxmox VE") : reword and mention Virtio for initramfs and rescue boot mode for dracut * 14:12[14:12, 8 July 2025](https://pve.proxmox.com/mediawiki/index.php?title=Paravirtualized_Drivers_for_Linux&oldid=12244 "Paravirtualized Drivers for Linux") diff [hist](https://pve.proxmox.com/mediawiki/index.php?title=Paravirtualized_Drivers_for_Linux&action=history "Paravirtualized Drivers for Linux") **+2,634** N [Paravirtualized Drivers for Linux](https://pve.proxmox.com/wiki/Paravirtualized_Drivers_for_Linux "Paravirtualized Drivers for Linux") Created page with "= Introduction = The Linux kernel has \[https://docs.kernel.org/driver-api/virtio/virtio.html Virtio\] support since version 2.6.x. However, the drivers are not necessarily compiled directly into the kernel but must sometimes be loaded as a kernel module. This sometimes leads to problems if the VM configuration wants to use Virtio components but the guest operating system has not loaded any drivers for them. = Adding the Virtio drivers to the initramfs = First check whet..." current #### 4 July 2025 * 09:00[09:00, 4 July 2025](https://pve.proxmox.com/mediawiki/index.php?title=Shrink_Qcow2_Disk_Files&oldid=12241 "Shrink Qcow2 Disk Files") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Shrink_Qcow2_Disk_Files&diff=prev&oldid=12241 "Shrink Qcow2 Disk Files") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Shrink_Qcow2_Disk_Files&action=history "Shrink Qcow2 Disk Files") +141 [Shrink Qcow2 Disk Files](https://pve.proxmox.com/wiki/Shrink_Qcow2_Disk_Files "Shrink Qcow2 Disk Files") [→Windows Guest Configuration](https://pve.proxmox.com/wiki/Shrink_Qcow2_Disk_Files#Windows_Guest_Configuration "Shrink Qcow2 Disk Files") : mention how to manually trim in windows current * 08:59[08:59, 4 July 2025](https://pve.proxmox.com/mediawiki/index.php?title=Shrink_Qcow2_Disk_Files&oldid=12240 "Shrink Qcow2 Disk Files") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Shrink_Qcow2_Disk_Files&diff=prev&oldid=12240 "Shrink Qcow2 Disk Files") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Shrink_Qcow2_Disk_Files&action=history "Shrink Qcow2 Disk Files") +417 [Shrink Qcow2 Disk Files](https://pve.proxmox.com/wiki/Shrink_Qcow2_Disk_Files "Shrink Qcow2 Disk Files") [→PVE Configuration](https://pve.proxmox.com/wiki/Shrink_Qcow2_Disk_Files#PVE_Configuration "Shrink Qcow2 Disk Files") : mention automatic shrinking on NFS will only work with recent NFS versions #### 30 June 2025 * 09:53[09:53, 30 June 2025](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Reef_to_Squid&oldid=12238 "Ceph Reef to Squid") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Reef_to_Squid&diff=prev&oldid=12238 "Ceph Reef to Squid") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Reef_to_Squid&action=history "Ceph Reef to Squid") −2 m [Ceph Reef to Squid](https://pve.proxmox.com/wiki/Ceph_Reef_to_Squid "Ceph Reef to Squid") [→Upgrade on each Ceph cluster node](https://pve.proxmox.com/wiki/Ceph_Reef_to_Squid#Upgrade_on_each_Ceph_cluster_node "Ceph Reef to Squid") : change leftover Quincy to Reef * 09:52[09:52, 30 June 2025](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Reef_to_Squid&oldid=12237 "Ceph Reef to Squid") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Reef_to_Squid&diff=prev&oldid=12237 "Ceph Reef to Squid") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Reef_to_Squid&action=history "Ceph Reef to Squid") +244 [Ceph Reef to Squid](https://pve.proxmox.com/wiki/Ceph_Reef_to_Squid "Ceph Reef to Squid") [→Upgrade on each Ceph cluster node](https://pve.proxmox.com/wiki/Ceph_Reef_to_Squid#Upgrade_on_each_Ceph_cluster_node "Ceph Reef to Squid") : add note about enterprise repositories and pvesubscription update #### 5 May 2025 * 09:04[09:04, 5 May 2025](https://pve.proxmox.com/mediawiki/index.php?title=Roadmap&oldid=12228 "Roadmap") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Roadmap&diff=prev&oldid=12228 "Roadmap") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Roadmap&action=history "Roadmap") +268 [Roadmap](https://pve.proxmox.com/wiki/Roadmap "Roadmap") add known issue for iGPU passthrough in legacy mode #### 24 April 2025 * 12:05[12:05, 24 April 2025](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&oldid=12226 "Migrate to Proxmox VE") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&diff=prev&oldid=12226 "Migrate to Proxmox VE") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&action=history "Migrate to Proxmox VE") **+1,893** [Migrate to Proxmox VE](https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE "Migrate to Proxmox VE") expand description of options for shared storage #### 10 April 2025 * 08:11[08:11, 10 April 2025](https://pve.proxmox.com/mediawiki/index.php?title=VM_Backup_Consistency&oldid=12222 "VM Backup Consistency") [diff](https://pve.proxmox.com/mediawiki/index.php?title=VM_Backup_Consistency&diff=prev&oldid=12222 "VM Backup Consistency") [hist](https://pve.proxmox.com/mediawiki/index.php?title=VM_Backup_Consistency&action=history "VM Backup Consistency") +278 [VM Backup Consistency](https://pve.proxmox.com/wiki/VM_Backup_Consistency "VM Backup Consistency") [→Windows](https://pve.proxmox.com/wiki/VM_Backup_Consistency#Windows "VM Backup Consistency") : add note about QGA update overwriting existing registry value current #### 18 March 2025 * 14:21[14:21, 18 March 2025](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_RBD_Mirroring&oldid=12191 "Ceph RBD Mirroring") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_RBD_Mirroring&diff=prev&oldid=12191 "Ceph RBD Mirroring") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_RBD_Mirroring&action=history "Ceph RBD Mirroring") +144 [Ceph RBD Mirroring](https://pve.proxmox.com/wiki/Ceph_RBD_Mirroring "Ceph RBD Mirroring") mention that TPM disks also rely on KRBD only and therefore cannot be used with journal based snapshots current #### 3 March 2025 * 12:34[12:34, 3 March 2025](https://pve.proxmox.com/mediawiki/index.php?title=Solaris_guest_best_practices&oldid=12186 "Solaris guest best practices") diff [hist](https://pve.proxmox.com/mediawiki/index.php?title=Solaris_guest_best_practices&action=history "Solaris guest best practices") **+1,306** N [Solaris guest best practices](https://pve.proxmox.com/wiki/Solaris_guest_best_practices "Solaris guest best practices") Created page with "== Introduction == This is a set of best practices when using Solaris in a VM. == Solaris 10 up to 11.3 == These versions don't come with support for VirtIO out of the box. Use the following VM settings: \* '''Guest OS:''' Solaris \* '''Disk:''' SATA or IDE \* '''Network:''' e1000 \* '''Machine-Type:''' i440 === Known Issues === CPUs and cores are not detected properly. If you run psrinfo -pv or mpstat, it will detect sockets, but not all core..." current #### 23 January 2025 * 13:48[13:48, 23 January 2025](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&oldid=12126 "Migrate to Proxmox VE") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&diff=prev&oldid=12126 "Migrate to Proxmox VE") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&action=history "Migrate to Proxmox VE") −49 m [Migrate to Proxmox VE](https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE "Migrate to Proxmox VE") [→Shared storage](https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE#Shared_storage "Migrate to Proxmox VE") : link to new multipath page #### 20 January 2025 * 14:23[14:23, 20 January 2025](https://pve.proxmox.com/mediawiki/index.php?title=VM_Backup_Consistency&oldid=12119 "VM Backup Consistency") diff [hist](https://pve.proxmox.com/mediawiki/index.php?title=VM_Backup_Consistency&action=history "VM Backup Consistency") **+3,933** N [VM Backup Consistency](https://pve.proxmox.com/wiki/VM_Backup_Consistency "VM Backup Consistency") Created page with "When backups (or snapshots) are triggered for VMs in Proxmox VE, it is necessary to make sure that the guest has written the latest changes to the disk image before the backup starts (or the snapshot is created). This is handled by the Qemu-Guest-Agent inside the guest OS. The trigger that can be observed in the backup task log: 
 INFO: issuing guest-agent 'fs-freeze' command INFO: issuing guest-agent 'fs-thaw' command
This will cause the guest OS to ensure t..." #### 15 January 2025 * 15:57[15:57, 15 January 2025](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_RBD_Mirroring&oldid=12118 "Ceph RBD Mirroring") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_RBD_Mirroring&diff=prev&oldid=12118 "Ceph RBD Mirroring") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_RBD_Mirroring&action=history "Ceph RBD Mirroring") +222 m [Ceph RBD Mirroring](https://pve.proxmox.com/wiki/Ceph_RBD_Mirroring "Ceph RBD Mirroring") [→Promote images on site B](https://pve.proxmox.com/wiki/Ceph_RBD_Mirroring#Promote_images_on_site_B "Ceph RBD Mirroring") : mention how to demote regularly for a normal switch and not a DR situation * 15:26[15:26, 15 January 2025](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_RBD_Mirroring&oldid=12117 "Ceph RBD Mirroring") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_RBD_Mirroring&diff=prev&oldid=12117 "Ceph RBD Mirroring") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_RBD_Mirroring&action=history "Ceph RBD Mirroring") +56 m [Ceph RBD Mirroring](https://pve.proxmox.com/wiki/Ceph_RBD_Mirroring "Ceph RBD Mirroring") [→Enable mirroring on pools](https://pve.proxmox.com/wiki/Ceph_RBD_Mirroring#Enable_mirroring_on_pools "Ceph RBD Mirroring") #### 4 November 2024 * 16:18[16:18, 4 November 2024](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&oldid=12057 "Migrate to Proxmox VE") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&diff=prev&oldid=12057 "Migrate to Proxmox VE") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&action=history "Migrate to Proxmox VE") +139 [Migrate to Proxmox VE](https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE "Migrate to Proxmox VE") [→Supported Import Sources](https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE#Supported_Import_Sources "Migrate to Proxmox VE") : mention that encrypted disks cannot be imported #### 31 October 2024 * 08:47[08:47, 31 October 2024](https://pve.proxmox.com/mediawiki/index.php?title=NVIDIA_vGPU_on_Proxmox_VE&oldid=12055 "NVIDIA vGPU on Proxmox VE") [diff](https://pve.proxmox.com/mediawiki/index.php?title=NVIDIA_vGPU_on_Proxmox_VE&diff=prev&oldid=12055 "NVIDIA vGPU on Proxmox VE") [hist](https://pve.proxmox.com/mediawiki/index.php?title=NVIDIA_vGPU_on_Proxmox_VE&action=history "NVIDIA vGPU on Proxmox VE") −5 [NVIDIA vGPU on Proxmox VE](https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE "NVIDIA vGPU on Proxmox VE") make notes stand out more #### 28 October 2024 * 12:56[12:56, 28 October 2024](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Reef_to_Squid&oldid=12054 "Ceph Reef to Squid") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Reef_to_Squid&diff=prev&oldid=12054 "Ceph Reef to Squid") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Ceph_Reef_to_Squid&action=history "Ceph Reef to Squid") +189 m [Ceph Reef to Squid](https://pve.proxmox.com/wiki/Ceph_Reef_to_Squid "Ceph Reef to Squid") [→Consider Enabling Telemetry](https://pve.proxmox.com/wiki/Ceph_Reef_to_Squid#Consider_Enabling_Telemetry "Ceph Reef to Squid") : adapt telemetry command to run through #### 30 August 2024 * 15:47[15:47, 30 August 2024](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&oldid=12021 "Migrate to Proxmox VE") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&diff=prev&oldid=12021 "Migrate to Proxmox VE") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Migrate_to_Proxmox_VE&action=history "Migrate to Proxmox VE") **+919** [Migrate to Proxmox VE](https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE "Migrate to Proxmox VE") add section for alternatives to snapshots when exisiting iSCSI or FC storages need to be repurposed for PVE #### 25 July 2024 * 09:58[09:58, 25 July 2024](https://pve.proxmox.com/mediawiki/index.php?title=Automated_Installation&oldid=12018 "Automated Installation") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Automated_Installation&diff=prev&oldid=12018 "Automated Installation") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Automated_Installation&action=history "Automated Installation") −19 m [Automated Installation](https://pve.proxmox.com/wiki/Automated_Installation "Automated Installation") [→Useful Properties](https://pve.proxmox.com/wiki/Automated_Installation#Useful_Properties "Automated Installation") : fix property, device serial smuggled in #### 15 July 2024 * 11:15[11:15, 15 July 2024](https://pve.proxmox.com/mediawiki/index.php?title=Full_Mesh_Network_for_Ceph_Server&oldid=12009 "Full Mesh Network for Ceph Server") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Full_Mesh_Network_for_Ceph_Server&diff=prev&oldid=12009 "Full Mesh Network for Ceph Server") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Full_Mesh_Network_for_Ceph_Server&action=history "Full Mesh Network for Ceph Server") +11 m [Full Mesh Network for Ceph Server](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server "Full Mesh Network for Ceph Server") [→Example](https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Example "Full Mesh Network for Ceph Server") #### 3 May 2024 * 13:20[13:20, 3 May 2024](https://pve.proxmox.com/mediawiki/index.php?title=Automated_Installation&oldid=12000 "Automated Installation") [diff](https://pve.proxmox.com/mediawiki/index.php?title=Automated_Installation&diff=prev&oldid=12000 "Automated Installation") [hist](https://pve.proxmox.com/mediawiki/index.php?title=Automated_Installation&action=history "Automated Installation") **+9,804** [Automated Installation](https://pve.proxmox.com/wiki/Automated_Installation "Automated Installation") add example server and third party tools sections - now carefully merged (newest | [oldest](https://pve.proxmox.com/mediawiki/index.php?title=Special:Contributions/A.lauterer&target=A.lauterer&dir=prev) ) View (newer 50 | [older 50](https://pve.proxmox.com/mediawiki/index.php?title=Special:Contributions/A.lauterer&target=A.lauterer&offset=20240503132024) ) ([20](https://pve.proxmox.com/mediawiki/index.php?title=Special:Contributions/A.lauterer&target=A.lauterer&offset=&limit=20) | 50 | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:Contributions/A.lauterer&target=A.lauterer&offset=&limit=100) | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:Contributions/A.lauterer&target=A.lauterer&offset=&limit=250) | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:Contributions/A.lauterer&target=A.lauterer&offset=&limit=500) ) Retrieved from "[https://pve.proxmox.com/wiki/Special:Contributions/A.lauterer](https://pve.proxmox.com/wiki/Special:Contributions/A.lauterer) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Proxmox Datacenter Manager Roadmap - Proxmox VE Proxmox Datacenter Manager Roadmap ================================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap#searchInput) This roadmap is outdated. With the release of Proxmox Datacenter Manager 1.0 the roadmap and release notes are now available as part of its documentation: [https://pdm.proxmox.com/docs/roadmap.html](https://pdm.proxmox.com/docs/roadmap.html) Contents -------- * [1 Overview](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap#Overview) * [2 Roadmap](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap#Roadmap) * [3 Proxmox Datacenter Manager 0.9 BETA](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap#Proxmox_Datacenter_Manager_0.9_BETA) * [3.1 Features (Highlights)](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap#Features_(Highlights)) * [3.2 Changelog Overview](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap#Changelog_Overview) * [3.2.1 Enhancements in the Web Interface (GUI)](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap#Enhancements_in_the_Web_Interface_(GUI)) * [3.2.2 Remotes Management](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap#Remotes_Management) * [3.2.3 Backend Improvements](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap#Backend_Improvements) * [3.2.4 Command Line Interface Enhancements](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap#Command_Line_Interface_Enhancements) * [3.2.5 Miscellaneous Improvements](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap#Miscellaneous_Improvements) * [3.3 Known Issues & Breaking Changes](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap#Known_Issues_&_Breaking_Changes) * [4 Proxmox Datacenter Manager 0.1 ALPHA](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap#Proxmox_Datacenter_Manager_0.1_ALPHA) * [4.1 Features (Highlights)](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap#Features_(Highlights)_2) * [4.2 Changelog Overview](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap#Changelog_Overview_2) * [4.3 Known Issues & Breaking Changes](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap#Known_Issues_&_Breaking_Changes_2) Overview -------- This article provides release notes and a high-level roadmap overview for Proxmox Datacenter Manager. [![](https://pve.proxmox.com/mediawiki/images/thumb/7/76/Pdm-alpha-0.1.7-ui.png/600px-Pdm-alpha-0.1.7-ui.png)](https://pve.proxmox.com/wiki/File:Pdm-alpha-0.1.7-ui.png) The Proxmox Datacenter Manager project has been developed with the objective of providing a centralized overview of all your individual nodes and clusters. It also enables basic management like migrations of virtual guests without any cluster network requirements. Due to the current beta in-development status of the Proxmox Datacenter Manager, the specific feature list planned for the first stable 1.0 release is not yet final. This roadmap includes points that quite probably will only make it in after the first 1.0 release. Further, the roadmap consists not only of specific features that are planned. It includes more general concepts we want to evaluate and pain points that one currently faces when managing big and/or physically distributed Proxmox VE and Proxmox Backup Server setups. Roadmap ------- * Improve the overview of the health state (subscription, valid APT repositories, pending updates, backups done …) of all nodes and resources. * Better organization of resources, including over multiple remotes, for example with (hierarchical) groups or resource pools. Finding a specific set of virtual machines, nodes, … is key on large setups, and this will be an important area of work for the final 1.0. * Simplify adding remotes by implementing a remote-join information endpoint where key information can be copied from to give the PDM all initial information required for connecting to a remote while upholding high guarantees for trust and safety. Somewhat similar in principle to how the "Join Information" API and UI simplified the process for Proxmox VE clusters, but independent of that as PDM doesn't interface with cluster communication and works on single nodes too. * Management of some core configurations. * Node updates. * Backup jobs and their status. * Firewall (potentially only done later with SDN integration). * Very basic management of the most important virtual guest resources and settings. Proxmox Datacenter Manager provides a link to the target resource, allowing one to quickly open the fully featured user interface for any complex configurations. * First-class SDN integration, for example for setting up EVPN between different clusters. Probably the most important feature in the long run. * stretching EVPN VNets across clusters * support for multiple VRFs across clusters * automatic configuration of RT Import / Export * Off-site replication copies of guest for manual recovery on DC failure (not HA!) * Evaluate if an active-standby like architecture for the Proxmox Datacenter Manager makes sense, to have a native method to avoid a single point of failure. User can just use two Proxmox Datacenter Manager instances for now, metrics collection is doubled, but besides that, it's not much extra overhead. * Integration of other projects like Proxmox Backup Server and Proxmox Mail Gateway. * Caching/Tracking of remote tasks. * Bulk actions like start/stop/(remote-)migrations of virtual guests. * More complex search/filter syntax. * Improve ACL schema/handling. * Improve and polish error messages and handling. * Add notification system * Standard system, updates, ... notifications. * Evaluate if PDM can act as notification target for remotes. * Improvements on the UI side * Show more information and make things like RRD time frames configurable * Show/allow more options for migrations * Console for remote resources (nodes/guests) * Handling MFA for the initial "Probe Remote" connection. * Evaluate a Pool-View where the hierarchical resource pools from all remotes are merged. * Evaluate a way for limited views that certain users can be assigned too, for example showing only details of the virtual guests but not their nodes. * Implement different views for remotes like pool or tag. * Add a 'Quick Add' Copy-/Pasteable text (like PVE cluster-join) Proxmox Datacenter Manager 0.9 BETA ----------------------------------- Released 11. September 2025: [ISO Download](https://enterprise.proxmox.com/iso) . * Based on Debian Trixie (13) * Latest 6.14.11-1 Kernel as stable default * ZFS 2.3.4 ### Features (Highlights) * New release based on the great Debian Trixie. * Seamless upgrade from Proxmox Datacenter Manager Alpha, see [Proxmox Datacenter Manager Upgrade from Alpha to Beta](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta "Proxmox Datacenter Manager Upgrade from Alpha to Beta") . * EVPN configuration for Software-Defined Networking between clusters. A new panel provides an overview of the state of all EVPN zones across all remotes. Create EVPN Zones and VNets across multiple remotes from a single interface. A more detailed explanation of Proxmox Datacenter Manager's SDN capabilities can be found in the [documentation](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Beta_Documentation#SDN_Integration "Proxmox Datacenter Manager Beta Documentation") . * Improved search functionality to find resources quicker. Allows filtering by resource type (remote, virtual machine, container…), status (stopped, running…) and much more. The query syntax is inspired by Elasticsearch and GitHub's query language. Please refer to the [documentation](https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Beta_Documentation#Search_Syntax "Proxmox Datacenter Manager Beta Documentation") for a more thorough explanation of the syntax. * More efficient metric collection logic. Metrics are now collected concurrently. * Integrate privilege management in the access control UI. Allow managing the permissions of Proxmox Datacenter Manager users. ### Changelog Overview #### Enhancements in the Web Interface (GUI) * Add a time frame selector for RRD graphs to allow users to select the displayed time frame. * Display new metrics such as Pressure Stall Information (PSI) for Proxmox VE 9 hosts. * Improve the remote URL list of a remote by adding a placeholder, clear trigger and clearer column headers. * Enhancements to the Proxmox VE remote setup wizard. Probe hosts for fingerprint settings, to verify a provided fingerprint or to enable trust on first use (TOFU). Try matching the provided host against the host list that was queried from the remote to avoid duplicates. Reset later pages when previous pages have been changed, as they need to be revisited. * Make the “remote loading” icon nicer. * Correctly show a “cube” icon for container guests. * Add a panel that allows adding and editing permissions. * Move the node overview to a tab and add a tab that displays available updates. * Add a button linking the user to a remote's upgrade page. * Add descriptions for Software Defined Networking tasks. * Provide an EVPN overview panel for displaying EVPN Zones and Vnets. * Add a view for showing EVPN VRF instances across all remotes. * Allow creating EVPN VNets. * Open the search panel when clicking different panels in the dashboard and pre-fill it with appropriate filters. * Add a clear trigger to the search bar. * Provide a search icon in the guest panel for better discoverability of the search function. * Include a summary of all tasks in the dashboard. * Render status icons with a shadow instead of a solid background for a cleaner look. * Enhance the reloading logic for the dashboard. * Show tasks from the last 48 hours in the dashboard's task summary. * Close the search box if a user navigated to an entry. * Display a list of storages and their status in the resource tree of a Proxmox VE remote. * Change the warning and critical thresholds to 90% and 97.5% respectively. * Don't show a start or shutdown button for templates ([issue 6782](https://bugzilla.proxmox.com/show_bug.cgi?id=6782) ). * The dashboard now includes a panel showing the SDN status report. * Show an overview of all SDN zones and their status as a tree. The EVPN section is now moved below the SDN menu to mimic Proxmox VE's menu structure. * Route to correct panels when navigating between components. * Allow filtering tasks in the task list by remote. * Show the remote tasks when selecting the root node of the resource tree for a Proxmox VE remote. * Allow navigating to an SDN zone and SDN panel of a remote from the zone tree overview. * Show failed tasks only in task summary. * Add support for initial translations: * Arabic * Bulgarian * Catalan * Chinese (Simplified) * Chinese (Traditional) * Croatian * Czech * Danish * Dutch * Euskera (Basque) * French * Georgian * German * Hebrew * Italian * Japanese * Korean * Norwegian (Bokmal) * Norwegian (Nynorsk) * Persian (Farsi) * Polish * Portuguese (Brazil) * Russian * Slovenian * Spanish * Swedish * Turkish * Ukrainian #### Remotes Management * Enable Proxmox Backup Server Integration, CLI only for now. * Enable connection tracking when live migrating VMs on remotes. Whether connection tracking actually persists after migration also depends on the environment and especially on whether third party firewalls are used. * Enable trust on first use (TOFU) prompts when adding remotes. * Include templates in status counts. * Add an API endpoint that allows querying updates and changelogs from remotes. * Add the API infrastructure for the initial Software Defined Networking integration. #### Backend Improvements * Improve robustness of incoming connection handling. * Improve size requirements and performance for remote tasks cache. * More intelligently query remote tasks. * Fix an issue where the ACME configuration would not be constructed properly for the default account. * Collect metrics from remotes concurrently to improve performance. * Persist metric collection state after a run to allow reusing it after a daemon restart. This should allow more efficient metric collection runs after restarts. * Metrics that should have been collected already, but were not due to collection timing changes, will now be collected. * Keep track of the time it took to collect metrics from each single remote and all remotes together. This provides better insights into the performance of metric collection runs. * Add an API endpoint to trigger metric collection. * Trigger immediate metric collection when a remote is added. * When a metric collection task is delayed skip it instead of triggering it quicker. * Add a more complex filter and search syntax inspired by Elasticsearch and GitHub query language. * When querying the remote task list treat a limit of “0” as unbounded and return the entire list. * Allow filtering remote tasks by remote. * Add an API endpoint that allows querying remote task statistics. * Add API endpoints for querying Proxmox VE storage's RRD data and status. * Add a `resource-type` parameter to the resources API endpoints. This allows more efficient filtering when querying the API for tasks and resource statuses. * Don't match templates when searching by remote. * Improve search when searching by remotes. For example, searching for all VMs of a specific remote is now possible. * When encountering an error, return the root cause not the top level error when fetching remotes. This makes the reported error messages more specific. #### Command Line Interface Enhancements * Allow query the status and RRD data from remotes via `proxmox-datacenter-manager-client`. * Add an upgrade checking script (`pdmAtoB`) to make upgrades more seamless. * The utility `proxmox-datacenter-manager-admin` can now display the currently running version. #### Miscellaneous Improvements * Log an error when a task to query remote tasks fails instead of cancelling all tasks. * Fix the order filters are applied when requesting a filtered task list. * Use the new deb822 format for package repositories. * Add a CLI command to allow querying the metric collection status and triggering a metric collection run. * Handle a missing journal file error more gracefully when querying the task list. ### Known Issues & Breaking Changes * The API endpoint for listing realms was changed from a `POST` to a `GET` request. Proxmox Datacenter Manager 0.1 ALPHA ------------------------------------ Released 19. December 2024: [ISO Download](https://enterprise.proxmox.com/iso) , [Forum Announcement](https://forum.proxmox.com/threads/proxmox-datacenter-manager-first-alpha-release.159323/) . * Based on Debian Bookworm (12.8) * Latest 6.8.12-5 Kernel as stable default * Newer 6.11 Kernel as opt-in * ZFS: 2.2.6 (with compatibility patches for Kernel 6.11) ### Features (Highlights) * Connect to and view any number of independent nodes or clusters ("Datacenters") * View the basic resource usage of all nodes and their guests. Saves and caches the list of resources (mainly guests and storage) and their usage metrics to provide a quick overview of all resources and the last-seen state for offline/unresponsive ones. * Basic management of the resources: shutdown, reboot, start, … For more complex management tasks, it provides a direct link to the full web interface of Proxmox VE/Proxmox Backup Server/… * Remote migration of virtual guests between different datacenters. * Support for the standard Proxmox feature set including complex Multi-Factor Authentication or ACME/Let's Encrypt from the beginning. ### Changelog Overview Not applicable for the first alpha release. ### Known Issues & Breaking Changes This is an alpha release, there might be lots of stuff that is broken, gets reworked and fixed somewhat frequently. Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=Proxmox\_Datacenter\_Manager\_Roadmap&oldid=12523](https://pve.proxmox.com/mediawiki/index.php?title=Proxmox_Datacenter_Manager_Roadmap&oldid=12523) " [Category](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Proxmox Datacenter Manager](https://pve.proxmox.com/wiki/Category:Proxmox_Datacenter_Manager "Category:Proxmox Datacenter Manager") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # YubiKey - Proxmox VE YubiKey ======= From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/YubiKey#mw-head) [Jump to search](https://pve.proxmox.com/wiki/YubiKey#searchInput) Contents -------- * [1 YubiKeys](https://pve.proxmox.com/wiki/YubiKey#YubiKeys) * [1.1 Demo: Hosting your own Verification Servers](https://pve.proxmox.com/wiki/YubiKey#Demo:_Hosting_your_own_Verification_Servers) * [1.1.1 The Key Server](https://pve.proxmox.com/wiki/YubiKey#The_Key_Server) * [1.1.2 The Validation Server](https://pve.proxmox.com/wiki/YubiKey#The_Validation_Server) * [1.1.3 Connecting PVE to the Validation Server](https://pve.proxmox.com/wiki/YubiKey#Connecting_PVE_to_the_Validation_Server) * [1.2 Securing a realm with Yubico Two-Factor Authentication](https://pve.proxmox.com/wiki/YubiKey#Securing_a_realm_with_Yubico_Two-Factor_Authentication) * [1.3 Preparing YubiKeys](https://pve.proxmox.com/wiki/YubiKey#Preparing_YubiKeys) * [1.3.1 Generating a Key as a User](https://pve.proxmox.com/wiki/YubiKey#Generating_a_Key_as_a_User) * [1.3.2 Generating a Key on the Server](https://pve.proxmox.com/wiki/YubiKey#Generating_a_Key_on_the_Server) YubiKeys ======== In order to use YubiKeys in Proxmox VE you need access to a YubiKey validation server. You can either use the [YubiCloud](https://www.yubico.com/products/services-software/yubicloud/) or host your own validation server. Below is a short introduction to setting up such a server for demonstration purposes. If you've setup your server and simply wish to start using the YubiKeys, skip the server setup and go straight to your preferred method of managing keys below. Demo: Hosting your own Verification Servers ------------------------------------------- When using Yubikey OTP there are two servers involved: a validation server and a key storage server. For security reasons it is recommended to separate the two and restrict access to the key servers. The validation servers need to access the key server via a REST API. And PVE needs access to the validation server's API. For demonstration purposes the Debian provided \`yubikey-ksm\` and \`yubkey-val\` packages can be installed on a single local host - for simplicity this can be a fresh Debian or PVE machine - to test the functionality. For a complete setup it is recommended to read through the whole documentation of both packages found here: * [https://github.com/Yubico/yubikey-ksm/blob/master/doc/](https://github.com/Yubico/yubikey-ksm/blob/master/doc/) * [https://github.com/Yubico/yubikey-val/blob/master/doc/](https://github.com/Yubico/yubikey-val/blob/master/doc/) ### The Key Server Install the \`yubikey-ksm\` package. Note that it'll pull in mysql as a dependency, and for demonstration purposes we'll choose the simplest setup and let APT perform default setups of mysql as well as the \`yubikey-ksm\` package via \`dbconfig-common\`. In other words: tell apt the mysql root password as well as the KSM password you want to use. You then have * a mysql database with a db named \`ykksm\` up and running * apache2 providing the YubiKey KSM API at [http://localhost/wsapi/decrypt](http://localhost/wsapi/decrypt) For manual deployment refer to: [https://github.com/Yubico/yubikey-ksm/blob/master/doc/Installation.adoc](https://github.com/Yubico/yubikey-ksm/blob/master/doc/Installation.adoc) ### The Validation Server Install the \`yubikey-val\` package. If you follow the instructions the same way as with the key server above, you'll have * a mysql database named \`ykval\` * an apache2 configured to provide the validation API at [http://localhost/wsapi/verify](http://localhost/wsapi/verify) ### Connecting PVE to the Validation Server You can now use \`ykval-gen-clients\` to create an API key to be added to Proxmox: root@yubitest # ykval-gen-clients 1 2,6Xlxb5iNALPKN7Rf9jqTYPisqXo= The above output is your API ID and Key separated by a comma. This means after selecting 'Yubico' in the \`TFA\` combo box in the dialog used to add an authentication realm, you write \`2\` in the ID field, and \`6Xlxb5iNALPKN7Rf9jqTYPisqXo=\` in the Key field. As URL, assuming you performed the above steps on the PVE host itself, you write: \`[http://localhost/wsapi/2.0/verify\`](http://localhost/wsapi/2.0/verify%60) . (Otherwise replace \`localhost\` with the IP address of your validation server. If you've gone through the manual setup and the recommended steps to secure the server with HTTPS you'll obviously want to replace the \`http\` part by \`https\`.) Securing a realm with Yubico Two-Factor Authentication ------------------------------------------------------ [![](https://pve.proxmox.com/mediawiki/images/thumb/7/7e/Screen-Prepare-Realm-for-Yubico.png/600px-Screen-Prepare-Realm-for-Yubico.png)](https://pve.proxmox.com/wiki/File:Screen-Prepare-Realm-for-Yubico.png) Make sure that are logged into the GUI as \`root@pam\`. In the Datacenter section select Authentication, select a realm you want to secure and click Edit (or double-click the realm). Select \`Yubico\` as in the \`TFA\` dropdown box. Three more fields will appear. In our example you'll fill in the following values: * Yubico API Id: 2 as API Id * Yubico API Key: 6Xlxb5iNALPKN7Rf9jqTYPisqXo= * Yubico URL: [http://localhost/wsapi/2.0/verify](http://localhost/wsapi/2.0/verify) Preparing YubiKeys ------------------ In order to use YubiKeys you need to be able to either get a server generated key to the client to configure their YubiKey with, or get a user-generated key to the server to import. Either way you'll want to secure the key while it is travelling instead of sending it plaintext or obscured. The import utilities provided by the \`yubikey-ksm\` package will want to decrypt and verify files before importing the contained keys into the database. To get started read through the following documentation links (you can skip the first one if you already have a GPG key setup for use on the key server): * [https://github.com/Yubico/yubikey-ksm/blob/master/doc/Generate\_KSM\_Key.adoc](https://github.com/Yubico/yubikey-ksm/blob/master/doc/Generate_KSM_Key.adoc) * [https://github.com/Yubico/yubikey-ksm/blob/master/doc/Key\_Provisioning\_Format.adoc](https://github.com/Yubico/yubikey-ksm/blob/master/doc/Key_Provisioning_Format.adoc) The rest of this howto will assume you created a GPG key with the name 'YK-KSM Importer'. #### Generating a Key as a User [![](https://pve.proxmox.com/mediawiki/images/thumb/a/ad/Screen-YubicoOTP-Generated.png/600px-Screen-YubicoOTP-Generated.png)](https://pve.proxmox.com/wiki/File:Screen-YubicoOTP-Generated.png) First read through: * [https://github.com/Yubico/yubikey-ksm/blob/master/doc/Import\_Keys\_To\_KSM.adoc](https://github.com/Yubico/yubikey-ksm/blob/master/doc/Import_Keys_To_KSM.adoc) * [https://github.com/Yubico/yubikey-ksm/blob/master/doc/Key\_Provisioning\_Format.adoc](https://github.com/Yubico/yubikey-ksm/blob/master/doc/Key_Provisioning_Format.adoc) To create a key as a user, simply connect your YubiKey and fireup the \`yubikey-personalization-gui\` program. Select \`Yubico OTP\`, click \`Advanced\` and hit the three \`Generate\` buttons while leaving the default settings. Also make sure you hit the \`Write Configuration\` button in order to write this key onto the YubiKey. Now it the GUI should look similar to the screenshot on the right. You need to copy the 3 values (Public Identity, Private Identity and Secret Key) and get them to onto the server over a secure channel. Since this is just a demonstration we'll prepare the file to be imported via \`ykksm-import\` right away. (Make sure you read through the link about the [Key Provisioning Format](https://github.com/Yubico/yubikey-ksm/blob/master/doc/Key_Provisioning_Format.adoc) above). The following is a working example file containing the data from the screenshot on the right. Make sure you fill in the data in the right order. We'll leave the lockpw field blank here. Create the file 'keys-plain.txt': \# ykksm 1 # serialnr,identity,internaluid,aeskey,lockpw,created,accessed\[,progflags\] 1,hegrtfdufiki,e43254bdfda2,f5dca0ea8e169cb797d87671c0431e1c,000000000000,2016-10-13T09:30:25, # the end We now sign and encryt this file with the ykksm server administrator as a recipient. \# gpg -a --encrypt -r 'YK-KSM Importer' -s < keys-plain.txt > keys.gpg Now we transfer this file to the server and import it: \# ykksm-import --verbose --database='dbi:mysql:ykksm' --db-user=pv-yubi --creator='YK-KSM Importer' < keys.gpg [![](https://pve.proxmox.com/mediawiki/images/5/5e/Screen-Yubico-UserConfig.png)](https://pve.proxmox.com/wiki/File:Screen-Yubico-UserConfig.png) The next step is to associate the PVE user with the Public Identity of this key. In our example the Public Identity is \`hegrtfdufiki\`. We add this to the user's Key IDs field via the PVE GUI. #### Generating a Key on the Server First read through: * [https://github.com/Yubico/yubikey-ksm/blob/master/doc/Generate\_Keys.adoc](https://github.com/Yubico/yubikey-ksm/blob/master/doc/Generate_Keys.adoc) * [https://github.com/Yubico/yubikey-ksm/blob/master/doc/Import\_Keys\_To\_KSM.adoc](https://github.com/Yubico/yubikey-ksm/blob/master/doc/Import_Keys_To_KSM.adoc) We start by creating a single key. The following command will show the key via stderr on the terminal, and a second later ask you for the GPG passphraze to sign and encrypt the file into \`keys.txt\`. bash # ykksm-gen-keys --urandom 1 1 | tee /dev/stderr | (sleep 1 && gpg -a --encrypt -r 'YK-KSM Importer' -s > keys.txt) # ykksm 1 # serialnr,identity,internaluid,aeskey,lockpw,created,accessed\[,progflags\] 1,cccccccccccb,6f966145cd8e,0ef19f49b1bb52e5bfcd11ad3d50d1ec,86aad678e350,2016-10-21T12:33:43, # the end You need a passphrase to unlock the secret key for user: "YK-KSM pv-yubi Import Key" 2048-bit RSA key, ID 40FC7068, created 2016-10-13 bash # Here you see that the Public Identity (\`cccccccccccb\`) in this case depends on the serial number which is passed via command line parameters. In this case '1'. As you can gather from the second link, importing works like in the previous example where we generated the key file manually: \# ykksm-import --verbose --database='dbi:mysql:ykksm' --db-user=pv-yubi < keys.txt We now have to upload the key onto a YubiKey. We can do this with the \`yubikey-personalization-gui\`. Similarly to when generating the keys via this UI, select Yubikey OTP, hit Advanced, leave the default settings, but this time instead of hitting the \`Generate\` buttons, copy the three fields after the serial number from the \`ykksm-gen-keys\` output into the fields in the YubiKey UI. The order is Public Identity, Private Identity, then Secret Key. Then press the \`Write Configuration\` button. Now add the Public Identity (in this case \`cccccccccccb\`) into the user' Retrieved from "[https://pve.proxmox.com/mediawiki/index.php?title=YubiKey&oldid=9824](https://pve.proxmox.com/mediawiki/index.php?title=YubiKey&oldid=9824) " [Categories](https://pve.proxmox.com/wiki/Special:Categories "Special:Categories") : * [Pages using deprecated source tags](https://pve.proxmox.com/mediawiki/index.php?title=Category:Pages_using_deprecated_source_tags&action=edit&redlink=1 "Category:Pages using deprecated source tags (page does not exist)") * [HOWTO](https://pve.proxmox.com/wiki/Category:HOWTO "Category:HOWTO") Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Template:Languages" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Template:Languages" ======================================= ← [Template:Languages](https://pve.proxmox.com/wiki/Template:Languages "Template:Languages") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Template:Languages#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Template:Languages#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk all HelpInvert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go No pages link to **[Template:Languages](https://pve.proxmox.com/wiki/Template:Languages "Template:Languages") **. Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Template:Languages](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Template:Languages) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") Check this box to hide links from pages within the selected namespace. all (Main) Talk User User talk Proxmox VE Proxmox VE talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Module Module talk --- # Related changes - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Related_changes) Related changes =============== ← [Upgrade from 5.x to 6.0](https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0 "Upgrade from 5.x to 6.0") [Jump to navigation](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Upgrade_from_5.x_to_6.0#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Upgrade_from_5.x_to_6.0#searchInput) Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category). Changes to pages on [your Watchlist](https://pve.proxmox.com/wiki/Special:Watchlist "Special:Watchlist") are in **bold**. Recent changes optionsShow last [**50**](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&limit=50&target=Upgrade_from_5.x_to_6.0 "Special:RecentChangesLinked") | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&limit=100&target=Upgrade_from_5.x_to_6.0 "Special:RecentChangesLinked") | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&limit=250&target=Upgrade_from_5.x_to_6.0 "Special:RecentChangesLinked") | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&limit=500&target=Upgrade_from_5.x_to_6.0 "Special:RecentChangesLinked") changes in last [1](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&days=1&from=&target=Upgrade_from_5.x_to_6.0 "Special:RecentChangesLinked") | [3](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&days=3&from=&target=Upgrade_from_5.x_to_6.0 "Special:RecentChangesLinked") | [**7**](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&days=7&from=&target=Upgrade_from_5.x_to_6.0 "Special:RecentChangesLinked") | [14](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&days=14&from=&target=Upgrade_from_5.x_to_6.0 "Special:RecentChangesLinked") | [30](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&days=30&from=&target=Upgrade_from_5.x_to_6.0 "Special:RecentChangesLinked") days [Hide](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&hideliu=1&target=Upgrade_from_5.x_to_6.0 "Special:RecentChangesLinked") registered users | [Hide](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&hideanons=1&target=Upgrade_from_5.x_to_6.0 "Special:RecentChangesLinked") anonymous users | [Hide](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&hidemyself=1&target=Upgrade_from_5.x_to_6.0 "Special:RecentChangesLinked") my edits | [Show](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&hidebots=0&target=Upgrade_from_5.x_to_6.0 "Special:RecentChangesLinked") bots | [Hide](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&hideminor=1&target=Upgrade_from_5.x_to_6.0 "Special:RecentChangesLinked") minor edits [Show new changes starting from 08:23, 14 April 2026](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&from=20260414082305&fromFormatted=08%3A23%2C+14+April+2026&target=Upgrade_from_5.x_to_6.0 "Special:RecentChangesLinked") * * * | | | | --- | --- | | Namespace: | all (Main) Talk User User talk Proxmox VE Proxmox VE talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Module Module talk  Invert selection  Associated namespace | | [Tag](https://pve.proxmox.com/wiki/Special:Tags "Special:Tags")
filter: | Manual revert New redirect Removed redirect Replaced Reverted Rollback Undo Visual edit: Switched wikieditor (hidden tag)  Invert selection | | Page name: | Show changes to pages linked to the given page instead | No changes during the given period match these criteria. Retrieved from "[https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Upgrade\_from\_5.x\_to\_6.0](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Upgrade_from_5.x_to_6.0) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Proxmox VE:Language policy - Proxmox VE Proxmox VE:Language policy ========================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Proxmox_VE:Language_policy#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Proxmox_VE:Language_policy#searchInput) There is currently no text in this page. You can [search for this page title](https://pve.proxmox.com/wiki/Special:Search/Proxmox_VE:Language_policy "Special:Search/Proxmox VE:Language policy") in other pages, or [search the related logs](https://pve.proxmox.com/mediawiki/index.php?title=Special:Log&page=Proxmox_VE:Language_policy) , but you do not have permission to create this page. Retrieved from "[https://pve.proxmox.com/wiki/Proxmox\_VE:Language\_policy](https://pve.proxmox.com/wiki/Proxmox_VE:Language_policy) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Related changes - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Related_changes) Related changes =============== ← [Windows 2003 guest best practices](https://pve.proxmox.com/wiki/Windows_2003_guest_best_practices "Windows 2003 guest best practices") [Jump to navigation](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Windows_2003_guest_best_practices#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Windows_2003_guest_best_practices#searchInput) Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category). Changes to pages on [your Watchlist](https://pve.proxmox.com/wiki/Special:Watchlist "Special:Watchlist") are in **bold**. Recent changes optionsShow last [**50**](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&limit=50&target=Windows_2003_guest_best_practices "Special:RecentChangesLinked") | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&limit=100&target=Windows_2003_guest_best_practices "Special:RecentChangesLinked") | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&limit=250&target=Windows_2003_guest_best_practices "Special:RecentChangesLinked") | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&limit=500&target=Windows_2003_guest_best_practices "Special:RecentChangesLinked") changes in last [1](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&days=1&from=&target=Windows_2003_guest_best_practices "Special:RecentChangesLinked") | [3](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&days=3&from=&target=Windows_2003_guest_best_practices "Special:RecentChangesLinked") | [**7**](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&days=7&from=&target=Windows_2003_guest_best_practices "Special:RecentChangesLinked") | [14](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&days=14&from=&target=Windows_2003_guest_best_practices "Special:RecentChangesLinked") | [30](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&days=30&from=&target=Windows_2003_guest_best_practices "Special:RecentChangesLinked") days [Hide](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&hideliu=1&target=Windows_2003_guest_best_practices "Special:RecentChangesLinked") registered users | [Hide](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&hideanons=1&target=Windows_2003_guest_best_practices "Special:RecentChangesLinked") anonymous users | [Hide](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&hidemyself=1&target=Windows_2003_guest_best_practices "Special:RecentChangesLinked") my edits | [Show](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&hidebots=0&target=Windows_2003_guest_best_practices "Special:RecentChangesLinked") bots | [Hide](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&hideminor=1&target=Windows_2003_guest_best_practices "Special:RecentChangesLinked") minor edits [Show new changes starting from 08:23, 14 April 2026](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&from=20260414082305&fromFormatted=08%3A23%2C+14+April+2026&target=Windows_2003_guest_best_practices "Special:RecentChangesLinked") * * * | | | | --- | --- | | Namespace: | all (Main) Talk User User talk Proxmox VE Proxmox VE talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Module Module talk  Invert selection  Associated namespace | | [Tag](https://pve.proxmox.com/wiki/Special:Tags "Special:Tags")
filter: | Manual revert New redirect Removed redirect Replaced Reverted Rollback Undo Visual edit: Switched wikieditor (hidden tag)  Invert selection | | Page name: | Show changes to pages linked to the given page instead | No changes during the given period match these criteria. Retrieved from "[https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Windows\_2003\_guest\_best\_practices](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Windows_2003_guest_best_practices) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Related changes - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Related_changes) Related changes =============== ← [Ceph Server](https://pve.proxmox.com/wiki/Ceph_Server "Ceph Server") [Jump to navigation](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Ceph_Server#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Ceph_Server#searchInput) Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category). Changes to pages on [your Watchlist](https://pve.proxmox.com/wiki/Special:Watchlist "Special:Watchlist") are in **bold**. Recent changes optionsShow last [**50**](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&limit=50&target=Ceph_Server "Special:RecentChangesLinked") | [100](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&limit=100&target=Ceph_Server "Special:RecentChangesLinked") | [250](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&limit=250&target=Ceph_Server "Special:RecentChangesLinked") | [500](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&limit=500&target=Ceph_Server "Special:RecentChangesLinked") changes in last [1](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&days=1&from=&target=Ceph_Server "Special:RecentChangesLinked") | [3](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&days=3&from=&target=Ceph_Server "Special:RecentChangesLinked") | [**7**](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&days=7&from=&target=Ceph_Server "Special:RecentChangesLinked") | [14](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&days=14&from=&target=Ceph_Server "Special:RecentChangesLinked") | [30](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&days=30&from=&target=Ceph_Server "Special:RecentChangesLinked") days [Hide](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&hideliu=1&target=Ceph_Server "Special:RecentChangesLinked") registered users | [Hide](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&hideanons=1&target=Ceph_Server "Special:RecentChangesLinked") anonymous users | [Hide](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&hidemyself=1&target=Ceph_Server "Special:RecentChangesLinked") my edits | [Show](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&hidebots=0&target=Ceph_Server "Special:RecentChangesLinked") bots | [Hide](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&hideminor=1&target=Ceph_Server "Special:RecentChangesLinked") minor edits [Show new changes starting from 08:23, 14 April 2026](https://pve.proxmox.com/mediawiki/index.php?title=Special:RecentChangesLinked&from=20260414082306&fromFormatted=08%3A23%2C+14+April+2026&target=Ceph_Server "Special:RecentChangesLinked") * * * | | | | --- | --- | | Namespace: | all (Main) Talk User User talk Proxmox VE Proxmox VE talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Module Module talk  Invert selection  Associated namespace | | [Tag](https://pve.proxmox.com/wiki/Special:Tags "Special:Tags")
filter: | Manual revert New redirect Removed redirect Replaced Reverted Rollback Undo Visual edit: Switched wikieditor (hidden tag)  Invert selection | | Page name: | Show changes to pages linked to the given page instead | No changes during the given period match these criteria. Retrieved from "[https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Ceph\_Server](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Ceph_Server) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Related changes - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit_review) Related changes =============== ← [Upgrade from 3.x to 4.0](https://pve.proxmox.com/wiki/Upgrade_from_3.x_to_4.0 "Upgrade from 3.x to 4.0") [Jump to navigation](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Upgrade_from_3.x_to_4.0#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Upgrade_from_3.x_to_4.0#searchInput) Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category). Changes to pages on [your Watchlist](https://pve.proxmox.com/wiki/Special:Watchlist "Special:Watchlist") are in **bold**. Show changes on pages linked from **Pages linked from** the selected page **Pages linking to** the selected page Active filters Hide Human (not bot) No active filters. All contributions are shown. NamespacesTags Live updates 50 changes, 7 days No changes during the given period match these criteria. Retrieved from "[https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Upgrade\_from\_3.x\_to\_4.0](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Upgrade_from_3.x_to_4.0) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") No filters saved yet To save your filter settings and reuse them later, click the bookmark icon in the Active filters area, below. Filters [](https://pve.proxmox.com/wiki/Special:Tags "Learn more about Tagged edits") Exclude selected Exclude selected Highlight results No filters found Advanced filters NamespacesTagged edits Results to show 50 100 250 500 Group results by page Time period to search Recent hours 1 2 6 12 Recent days 1 3 7 14 30 --- # Pages that link to "Category:Proxmox VE 3" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Category:Proxmox VE 3" ========================================== ← [Category:Proxmox VE 3](https://pve.proxmox.com/wiki/Category:Proxmox_VE_3 "Category:Proxmox VE 3") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Category:Proxmox_VE_3#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Category:Proxmox_VE_3#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk all HelpInvert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go No pages link to **[Category:Proxmox VE 3](https://pve.proxmox.com/wiki/Category:Proxmox_VE_3 "Category:Proxmox VE 3") **. Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Category:Proxmox\_VE\_3](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Category:Proxmox_VE_3) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") Check this box to hide links from pages within the selected namespace. all (Main) Talk User User talk Proxmox VE Proxmox VE talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Module Module talk --- # Related changes - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit_review) Related changes =============== ← [Translations](https://pve.proxmox.com/wiki/Translations "Translations") [Jump to navigation](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Translations#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Translations#searchInput) Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category). Changes to pages on [your Watchlist](https://pve.proxmox.com/wiki/Special:Watchlist "Special:Watchlist") are in **bold**. Show changes on pages linked from **Pages linked from** the selected page **Pages linking to** the selected page Active filters Hide Human (not bot) No active filters. All contributions are shown. NamespacesTags Live updates 50 changes, 7 days No changes during the given period match these criteria. Retrieved from "[https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Translations](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Translations) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") No filters saved yet To save your filter settings and reuse them later, click the bookmark icon in the Active filters area, below. Filters [](https://pve.proxmox.com/wiki/Special:Tags "Learn more about Tagged edits") Exclude selected Exclude selected Highlight results User registration and experience Unregistered Editors who aren't logged-in. Excluded Registered Logged-in editors. Excluded Newcomers Registered editors who have fewer than 10 edits or 4 days of activity. Excluded Learners Registered editors whose experience falls between "Newcomers" and "Experienced users." Excluded Experienced users Registered editors with more than 500 edits and 30 days of activity. Excluded Contribution authorship Changes by you Your own contributions. Excluded Changes by others All changes except your own. Excluded Automated contributions Bot Edits made by automated tools. Excluded Human (not bot) Edits made by human editors. Excluded Significance Minor edits Edits the author labeled as minor. Excluded Non-minor edits Edits not labeled as minor. Excluded Latest revisions Latest revision Only the most recent change to a page. Excluded Not the latest revision All changes that are not the "latest revision". Excluded Type of change Page edits Edits to wiki content, discussions, category descriptions… Excluded Page creations Edits that make new pages. Excluded Logged actions Administrative actions, page deletions, uploads… Excluded Account creations Log entries for account creation. Logged actions must be selected. Excluded All contents Excluded All discussions Excluded (Main) Excluded Talk Excluded User Excluded User talk Excluded Proxmox VE Excluded Proxmox VE talk Excluded File Excluded File talk Excluded MediaWiki Excluded MediaWiki talk Excluded Template Excluded Template talk Excluded Help Excluded Help talk Excluded Category Excluded Category talk Excluded Module Excluded Module talk Excluded Special Excluded Manual revert Edits that manually restore the page to an exact previous state Excluded New redirect Edits that create a new redirect or change a page to a redirect Excluded Removed redirect Edits that change an existing redirect to a non-redirect Excluded Replaced Edits that remove more than 90% of the content of a page Excluded Reverted Edits that were later reverted by a different edit Excluded Rollback Edits that roll back previous edits using the rollback link Excluded Undo Edits that undo previous edits using the undo link Excluded Visual edit: Switched User started to edit using the visual editor, then changed to the wikitext editor. Excluded wikieditor (hidden tag) Edit made using WikiEditor (2010 wikitext editor) Excluded No filters found Advanced filters NamespacesTagged edits Results to show 50 100 250 500 Group results by page Time period to search Recent hours 1 2 6 12 Recent days 1 3 7 14 30 Select a color --- # Related changes - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit_review) Related changes =============== ← [High Availability](https://pve.proxmox.com/wiki/High_Availability "High Availability") [Jump to navigation](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/High_Availability#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/High_Availability#searchInput) Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category). Changes to pages on [your Watchlist](https://pve.proxmox.com/wiki/Special:Watchlist "Special:Watchlist") are in **bold**. Show changes on pages linked from **Pages linked from** the selected page **Pages linking to** the selected page Active filters Hide Human (not bot) No active filters. All contributions are shown. NamespacesTags Live updates 50 changes, 7 days No changes during the given period match these criteria. Retrieved from "[https://pve.proxmox.com/wiki/Special:RecentChangesLinked/High\_Availability](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/High_Availability) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") No filters saved yet To save your filter settings and reuse them later, click the bookmark icon in the Active filters area, below. Filters [](https://pve.proxmox.com/wiki/Special:Tags "Learn more about Tagged edits") Exclude selected Exclude selected Highlight results User registration and experience Unregistered Editors who aren't logged-in. Excluded Registered Logged-in editors. Excluded Newcomers Registered editors who have fewer than 10 edits or 4 days of activity. Excluded Learners Registered editors whose experience falls between "Newcomers" and "Experienced users." Excluded Experienced users Registered editors with more than 500 edits and 30 days of activity. Excluded Contribution authorship Changes by you Your own contributions. Excluded Changes by others All changes except your own. Excluded Automated contributions Bot Edits made by automated tools. Excluded Human (not bot) Edits made by human editors. Excluded Significance Minor edits Edits the author labeled as minor. Excluded Non-minor edits Edits not labeled as minor. Excluded Latest revisions Latest revision Only the most recent change to a page. Excluded Not the latest revision All changes that are not the "latest revision". Excluded Type of change Page edits Edits to wiki content, discussions, category descriptions… Excluded Page creations Edits that make new pages. Excluded Logged actions Administrative actions, page deletions, uploads… Excluded Account creations Log entries for account creation. Logged actions must be selected. Excluded All contents Excluded All discussions Excluded (Main) Excluded Talk Excluded User Excluded User talk Excluded Proxmox VE Excluded Proxmox VE talk Excluded File Excluded File talk Excluded MediaWiki Excluded MediaWiki talk Excluded Template Excluded Template talk Excluded Help Excluded Help talk Excluded Category Excluded Category talk Excluded Module Excluded Module talk Excluded Special Excluded Manual revert Edits that manually restore the page to an exact previous state Excluded New redirect Edits that create a new redirect or change a page to a redirect Excluded Removed redirect Edits that change an existing redirect to a non-redirect Excluded Replaced Edits that remove more than 90% of the content of a page Excluded Reverted Edits that were later reverted by a different edit Excluded Rollback Edits that roll back previous edits using the rollback link Excluded Undo Edits that undo previous edits using the undo link Excluded Visual edit: Switched User started to edit using the visual editor, then changed to the wikitext editor. Excluded wikieditor (hidden tag) Edit made using WikiEditor (2010 wikitext editor) Excluded No filters found Advanced filters NamespacesTagged edits Results to show 50 100 250 500 Group results by page Time period to search Recent hours 1 2 6 12 Recent days 1 3 7 14 30 Select a color --- # Related changes - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit_review) Related changes =============== ← [Legacy: ZFS over iSCSI](https://pve.proxmox.com/wiki/Legacy:_ZFS_over_iSCSI "Legacy: ZFS over iSCSI") [Jump to navigation](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Legacy:_ZFS_over_iSCSI#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Legacy:_ZFS_over_iSCSI#searchInput) Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category). Changes to pages on [your Watchlist](https://pve.proxmox.com/wiki/Special:Watchlist "Special:Watchlist") are in **bold**. Show changes on pages linked from **Pages linked from** the selected page **Pages linking to** the selected page Active filters Hide Human (not bot) No active filters. All contributions are shown. NamespacesTags Live updates 50 changes, 7 days No changes during the given period match these criteria. Retrieved from "[https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Legacy:\_ZFS\_over\_iSCSI](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Legacy:_ZFS_over_iSCSI) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") No filters saved yet To save your filter settings and reuse them later, click the bookmark icon in the Active filters area, below. Filters [](https://pve.proxmox.com/wiki/Special:Tags "Learn more about Tagged edits") Exclude selected Exclude selected Highlight results No filters found Advanced filters NamespacesTagged edits Results to show 50 100 250 500 Group results by page Time period to search Recent hours 1 2 6 12 Recent days 1 3 7 14 30 --- # Related changes - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit_review) Related changes =============== ← [Hotplug (qemu disk,nic,cpu,memory)](https://pve.proxmox.com/wiki/Hotplug_(qemu_disk,nic,cpu,memory) "Hotplug (qemu disk,nic,cpu,memory)") [Jump to navigation](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Hotplug_(qemu_disk,nic,cpu,memory)#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Hotplug_(qemu_disk,nic,cpu,memory)#searchInput) Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category). Changes to pages on [your Watchlist](https://pve.proxmox.com/wiki/Special:Watchlist "Special:Watchlist") are in **bold**. Show changes on pages linked from **Pages linked from** the selected page **Pages linking to** the selected page Active filters Hide Human (not bot) No active filters. All contributions are shown. NamespacesTags Live updates 50 changes, 7 days No changes during the given period match these criteria. Retrieved from "[https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Hotplug\_(qemu\_disk,nic,cpu,memory)](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Hotplug_(qemu_disk,nic,cpu,memory)) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") No filters saved yet To save your filter settings and reuse them later, click the bookmark icon in the Active filters area, below. Filters [](https://pve.proxmox.com/wiki/Special:Tags "Learn more about Tagged edits") Exclude selected Exclude selected Highlight results User registration and experience Unregistered Editors who aren't logged-in. Excluded Registered Logged-in editors. Excluded Newcomers Registered editors who have fewer than 10 edits or 4 days of activity. Excluded Learners Registered editors whose experience falls between "Newcomers" and "Experienced users." Excluded Experienced users Registered editors with more than 500 edits and 30 days of activity. Excluded Contribution authorship Changes by you Your own contributions. Excluded Changes by others All changes except your own. Excluded Automated contributions Bot Edits made by automated tools. Excluded Human (not bot) Edits made by human editors. Excluded Significance Minor edits Edits the author labeled as minor. Excluded Non-minor edits Edits not labeled as minor. Excluded Latest revisions Latest revision Only the most recent change to a page. Excluded Not the latest revision All changes that are not the "latest revision". Excluded Type of change Page edits Edits to wiki content, discussions, category descriptions… Excluded Page creations Edits that make new pages. Excluded Logged actions Administrative actions, page deletions, uploads… Excluded Account creations Log entries for account creation. Logged actions must be selected. Excluded All contents Excluded All discussions Excluded (Main) Excluded Talk Excluded User Excluded User talk Excluded Proxmox VE Excluded Proxmox VE talk Excluded File Excluded File talk Excluded MediaWiki Excluded MediaWiki talk Excluded Template Excluded Template talk Excluded Help Excluded Help talk Excluded Category Excluded Category talk Excluded Module Excluded Module talk Excluded Special Excluded Manual revert Edits that manually restore the page to an exact previous state Excluded New redirect Edits that create a new redirect or change a page to a redirect Excluded Removed redirect Edits that change an existing redirect to a non-redirect Excluded Replaced Edits that remove more than 90% of the content of a page Excluded Reverted Edits that were later reverted by a different edit Excluded Rollback Edits that roll back previous edits using the rollback link Excluded Undo Edits that undo previous edits using the undo link Excluded Visual edit: Switched User started to edit using the visual editor, then changed to the wikitext editor. Excluded wikieditor (hidden tag) Edit made using WikiEditor (2010 wikitext editor) Excluded No filters found Advanced filters NamespacesTagged edits Results to show 50 100 250 500 Group results by page Time period to search Recent hours 1 2 6 12 Recent days 1 3 7 14 30 Select a color --- # Related changes - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit_review) Related changes =============== ← [Debugging Installation](https://pve.proxmox.com/wiki/Debugging_Installation "Debugging Installation") [Jump to navigation](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Debugging_Installation#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Debugging_Installation#searchInput) Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category). Changes to pages on [your Watchlist](https://pve.proxmox.com/wiki/Special:Watchlist "Special:Watchlist") are in **bold**. Show changes on pages linked from **Pages linked from** the selected page **Pages linking to** the selected page Active filters Hide Human (not bot) No active filters. All contributions are shown. NamespacesTags Live updates 50 changes, 7 days No changes during the given period match these criteria. Retrieved from "[https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Debugging\_Installation](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Debugging_Installation) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") No filters saved yet To save your filter settings and reuse them later, click the bookmark icon in the Active filters area, below. Filters [](https://pve.proxmox.com/wiki/Special:Tags "Learn more about Tagged edits") Exclude selected Exclude selected Highlight results User registration and experience Unregistered Editors who aren't logged-in. Excluded Registered Logged-in editors. Excluded Newcomers Registered editors who have fewer than 10 edits or 4 days of activity. Excluded Learners Registered editors whose experience falls between "Newcomers" and "Experienced users." Excluded Experienced users Registered editors with more than 500 edits and 30 days of activity. Excluded Contribution authorship Changes by you Your own contributions. Excluded Changes by others All changes except your own. Excluded Automated contributions Bot Edits made by automated tools. Excluded Human (not bot) Edits made by human editors. Excluded Significance Minor edits Edits the author labeled as minor. Excluded Non-minor edits Edits not labeled as minor. Excluded Latest revisions Latest revision Only the most recent change to a page. Excluded Not the latest revision All changes that are not the "latest revision". Excluded Type of change Page edits Edits to wiki content, discussions, category descriptions… Excluded Page creations Edits that make new pages. Excluded Logged actions Administrative actions, page deletions, uploads… Excluded Account creations Log entries for account creation. Logged actions must be selected. Excluded All contents Excluded All discussions Excluded (Main) Excluded Talk Excluded User Excluded User talk Excluded Proxmox VE Excluded Proxmox VE talk Excluded File Excluded File talk Excluded MediaWiki Excluded MediaWiki talk Excluded Template Excluded Template talk Excluded Help Excluded Help talk Excluded Category Excluded Category talk Excluded Module Excluded Module talk Excluded Special Excluded Manual revert Edits that manually restore the page to an exact previous state Excluded New redirect Edits that create a new redirect or change a page to a redirect Excluded Removed redirect Edits that change an existing redirect to a non-redirect Excluded Replaced Edits that remove more than 90% of the content of a page Excluded Reverted Edits that were later reverted by a different edit Excluded Rollback Edits that roll back previous edits using the rollback link Excluded Undo Edits that undo previous edits using the undo link Excluded Visual edit: Switched User started to edit using the visual editor, then changed to the wikitext editor. Excluded wikieditor (hidden tag) Edit made using WikiEditor (2010 wikitext editor) Excluded No filters found Advanced filters NamespacesTagged edits Results to show 50 100 250 500 Group results by page Time period to search Recent hours 1 2 6 12 Recent days 1 3 7 14 30 Select a color --- # Proxmox VE:Terms of Service - Proxmox VE Proxmox VE:Terms of Service =========================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Proxmox_VE:Terms_of_Service#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Proxmox_VE:Terms_of_Service#searchInput) There is currently no text in this page. You can [search for this page title](https://pve.proxmox.com/wiki/Special:Search/Proxmox_VE:Terms_of_Service "Special:Search/Proxmox VE:Terms of Service") in other pages, or [search the related logs](https://pve.proxmox.com/mediawiki/index.php?title=Special:Log&page=Proxmox_VE:Terms_of_Service) , but you do not have permission to create this page. Retrieved from "[https://pve.proxmox.com/wiki/Proxmox\_VE:Terms\_of\_Service](https://pve.proxmox.com/wiki/Proxmox_VE:Terms_of_Service) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Pages that link to "Category:HA" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Category:HA" ================================ ← [Category:HA](https://pve.proxmox.com/wiki/Category:HA "Category:HA") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Category:HA#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Category:HA#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk all HelpInvert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go No pages link to **[Category:HA](https://pve.proxmox.com/wiki/Category:HA "Category:HA") **. Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Category:HA](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Category:HA) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") Check this box to hide links from pages within the selected namespace. all (Main) Talk User User talk Proxmox VE Proxmox VE talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Module Module talk --- # Pages that link to "Category:High Availability" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Category:High Availability" =============================================== ← [Category:High Availability](https://pve.proxmox.com/wiki/Category:High_Availability "Category:High Availability") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Category:High_Availability#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Category:High_Availability#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk all HelpInvert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go No pages link to **[Category:High Availability](https://pve.proxmox.com/wiki/Category:High_Availability "Category:High Availability") **. Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Category:High\_Availability](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Category:High_Availability) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") Check this box to hide links from pages within the selected namespace. all (Main) Talk User User talk Proxmox VE Proxmox VE talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Module Module talk --- # Pages that link to "Category:Proxmox VE 3.x" - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:What_links_here) Pages that link to "Category:Proxmox VE 3.x" ============================================ ← [Category:Proxmox VE 3.x](https://pve.proxmox.com/wiki/Category:Proxmox_VE_3.x "Category:Proxmox VE 3.x") [Jump to navigation](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Category:Proxmox_VE_3.x#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Category:Proxmox_VE_3.x#searchInput) What links here ⧼whatlinkshere-whatlinkshere-target⧽ Page: ⧼whatlinkshere-whatlinkshere-ns⧽ Namespace: all(Main)TalkUserUser talkProxmox VEProxmox VE talkFileFile talkMediaWikiMediaWiki talkTemplateTemplate talkHelpHelp talkCategoryCategory talkModuleModule talk all HelpInvert selection ⧼whatlinkshere-whatlinkshere-filter⧽ Hide transclusions Hide links Hide redirects Go No pages link to **[Category:Proxmox VE 3.x](https://pve.proxmox.com/wiki/Category:Proxmox_VE_3.x "Category:Proxmox VE 3.x") **. Retrieved from "[https://pve.proxmox.com/wiki/Special:WhatLinksHere/Category:Proxmox\_VE\_3.x](https://pve.proxmox.com/wiki/Special:WhatLinksHere/Category:Proxmox_VE_3.x) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") Check this box to hide links from pages within the selected namespace. all (Main) Talk User User talk Proxmox VE Proxmox VE talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Module Module talk --- # Related changes - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit_review) Related changes =============== ← [Upgrade from 7 to 8](https://pve.proxmox.com/wiki/Upgrade_from_7_to_8 "Upgrade from 7 to 8") [Jump to navigation](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Upgrade_from_7_to_8#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Upgrade_from_7_to_8#searchInput) Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category). Changes to pages on [your Watchlist](https://pve.proxmox.com/wiki/Special:Watchlist "Special:Watchlist") are in **bold**. Show changes on pages linked from **Pages linked from** the selected page **Pages linking to** the selected page Active filters Hide Human (not bot) No active filters. All contributions are shown. NamespacesTags Live updates 50 changes, 7 days No changes during the given period match these criteria. Retrieved from "[https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Upgrade\_from\_7\_to\_8](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Upgrade_from_7_to_8) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") No filters saved yet To save your filter settings and reuse them later, click the bookmark icon in the Active filters area, below. Filters [](https://pve.proxmox.com/wiki/Special:Tags "Learn more about Tagged edits") Exclude selected Exclude selected Highlight results User registration and experience Unregistered Editors who aren't logged-in. Excluded Registered Logged-in editors. Excluded Newcomers Registered editors who have fewer than 10 edits or 4 days of activity. Excluded Learners Registered editors whose experience falls between "Newcomers" and "Experienced users." Excluded Experienced users Registered editors with more than 500 edits and 30 days of activity. Excluded Contribution authorship Changes by you Your own contributions. Excluded Changes by others All changes except your own. Excluded Automated contributions Bot Edits made by automated tools. Excluded Human (not bot) Edits made by human editors. Excluded Significance Minor edits Edits the author labeled as minor. Excluded Non-minor edits Edits not labeled as minor. Excluded Latest revisions Latest revision Only the most recent change to a page. Excluded Not the latest revision All changes that are not the "latest revision". Excluded Type of change Page edits Edits to wiki content, discussions, category descriptions… Excluded Page creations Edits that make new pages. Excluded Logged actions Administrative actions, page deletions, uploads… Excluded Account creations Log entries for account creation. Logged actions must be selected. Excluded All contents Excluded All discussions Excluded (Main) Excluded Talk Excluded User Excluded User talk Excluded Proxmox VE Excluded Proxmox VE talk Excluded File Excluded File talk Excluded MediaWiki Excluded MediaWiki talk Excluded Template Excluded Template talk Excluded Help Excluded Help talk Excluded Category Excluded Category talk Excluded Module Excluded Module talk Excluded Special Excluded Manual revert Edits that manually restore the page to an exact previous state Excluded New redirect Edits that create a new redirect or change a page to a redirect Excluded Removed redirect Edits that change an existing redirect to a non-redirect Excluded Replaced Edits that remove more than 90% of the content of a page Excluded Reverted Edits that were later reverted by a different edit Excluded Rollback Edits that roll back previous edits using the rollback link Excluded Undo Edits that undo previous edits using the undo link Excluded Visual edit: Switched User started to edit using the visual editor, then changed to the wikitext editor. Excluded wikieditor (hidden tag) Edit made using WikiEditor (2010 wikitext editor) Excluded No filters found Advanced filters NamespacesTagged edits Results to show 50 100 250 500 Group results by page Time period to search Recent hours 1 2 6 12 Recent days 1 3 7 14 30 Select a color --- # Related changes - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit_review) Related changes =============== ← [Debian Appliance Builder](https://pve.proxmox.com/wiki/Debian_Appliance_Builder "Debian Appliance Builder") [Jump to navigation](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Debian_Appliance_Builder#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Debian_Appliance_Builder#searchInput) Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category). Changes to pages on [your Watchlist](https://pve.proxmox.com/wiki/Special:Watchlist "Special:Watchlist") are in **bold**. Show changes on pages linked from **Pages linked from** the selected page **Pages linking to** the selected page Active filters Hide Human (not bot) No active filters. All contributions are shown. NamespacesTags Live updates 50 changes, 7 days No changes during the given period match these criteria. Retrieved from "[https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Debian\_Appliance\_Builder](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Debian_Appliance_Builder) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") No filters saved yet To save your filter settings and reuse them later, click the bookmark icon in the Active filters area, below. Filters [](https://pve.proxmox.com/wiki/Special:Tags "Learn more about Tagged edits") Exclude selected Exclude selected Highlight results User registration and experience Unregistered Editors who aren't logged-in. Excluded Registered Logged-in editors. Excluded Newcomers Registered editors who have fewer than 10 edits or 4 days of activity. Excluded Learners Registered editors whose experience falls between "Newcomers" and "Experienced users." Excluded Experienced users Registered editors with more than 500 edits and 30 days of activity. Excluded Contribution authorship Changes by you Your own contributions. Excluded Changes by others All changes except your own. Excluded Automated contributions Bot Edits made by automated tools. Excluded Human (not bot) Edits made by human editors. Excluded Significance Minor edits Edits the author labeled as minor. Excluded Non-minor edits Edits not labeled as minor. Excluded Latest revisions Latest revision Only the most recent change to a page. Excluded Not the latest revision All changes that are not the "latest revision". Excluded Type of change Page edits Edits to wiki content, discussions, category descriptions… Excluded Page creations Edits that make new pages. Excluded Logged actions Administrative actions, page deletions, uploads… Excluded Account creations Log entries for account creation. Logged actions must be selected. Excluded All contents Excluded All discussions Excluded (Main) Excluded Talk Excluded User Excluded User talk Excluded Proxmox VE Excluded Proxmox VE talk Excluded File Excluded File talk Excluded MediaWiki Excluded MediaWiki talk Excluded Template Excluded Template talk Excluded Help Excluded Help talk Excluded Category Excluded Category talk Excluded Module Excluded Module talk Excluded Special Excluded Manual revert Edits that manually restore the page to an exact previous state Excluded New redirect Edits that create a new redirect or change a page to a redirect Excluded Removed redirect Edits that change an existing redirect to a non-redirect Excluded Replaced Edits that remove more than 90% of the content of a page Excluded Reverted Edits that were later reverted by a different edit Excluded Rollback Edits that roll back previous edits using the rollback link Excluded Undo Edits that undo previous edits using the undo link Excluded Visual edit: Switched User started to edit using the visual editor, then changed to the wikitext editor. Excluded wikieditor (hidden tag) Edit made using WikiEditor (2010 wikitext editor) Excluded No filters found Advanced filters NamespacesTagged edits Results to show 50 100 250 500 Group results by page Time period to search Recent hours 1 2 6 12 Recent days 1 3 7 14 30 Select a color --- # Related changes - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit_review) Related changes =============== ← [Storage](https://pve.proxmox.com/wiki/Storage "Storage") [Jump to navigation](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Storage#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Storage#searchInput) Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category). Changes to pages on [your Watchlist](https://pve.proxmox.com/wiki/Special:Watchlist "Special:Watchlist") are in **bold**. Show changes on pages linked from **Pages linked from** the selected page **Pages linking to** the selected page Active filters Hide Human (not bot) No active filters. All contributions are shown. NamespacesTags Live updates 50 changes, 7 days No changes during the given period match these criteria. Retrieved from "[https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Storage](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Storage) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") No filters saved yet To save your filter settings and reuse them later, click the bookmark icon in the Active filters area, below. Filters [](https://pve.proxmox.com/wiki/Special:Tags "Learn more about Tagged edits") Exclude selected Exclude selected Highlight results User registration and experience Unregistered Editors who aren't logged-in. Excluded Registered Logged-in editors. Excluded Newcomers Registered editors who have fewer than 10 edits or 4 days of activity. Excluded Learners Registered editors whose experience falls between "Newcomers" and "Experienced users." Excluded Experienced users Registered editors with more than 500 edits and 30 days of activity. Excluded Contribution authorship Changes by you Your own contributions. Excluded Changes by others All changes except your own. Excluded Automated contributions Bot Edits made by automated tools. Excluded Human (not bot) Edits made by human editors. Excluded Significance Minor edits Edits the author labeled as minor. Excluded Non-minor edits Edits not labeled as minor. Excluded Latest revisions Latest revision Only the most recent change to a page. Excluded Not the latest revision All changes that are not the "latest revision". Excluded Type of change Page edits Edits to wiki content, discussions, category descriptions… Excluded Page creations Edits that make new pages. Excluded Logged actions Administrative actions, page deletions, uploads… Excluded Account creations Log entries for account creation. Logged actions must be selected. Excluded All contents Excluded All discussions Excluded (Main) Excluded Talk Excluded User Excluded User talk Excluded Proxmox VE Excluded Proxmox VE talk Excluded File Excluded File talk Excluded MediaWiki Excluded MediaWiki talk Excluded Template Excluded Template talk Excluded Help Excluded Help talk Excluded Category Excluded Category talk Excluded Module Excluded Module talk Excluded Special Excluded Manual revert Edits that manually restore the page to an exact previous state Excluded New redirect Edits that create a new redirect or change a page to a redirect Excluded Removed redirect Edits that change an existing redirect to a non-redirect Excluded Replaced Edits that remove more than 90% of the content of a page Excluded Reverted Edits that were later reverted by a different edit Excluded Rollback Edits that roll back previous edits using the rollback link Excluded Undo Edits that undo previous edits using the undo link Excluded Visual edit: Switched User started to edit using the visual editor, then changed to the wikitext editor. Excluded wikieditor (hidden tag) Edit made using WikiEditor (2010 wikitext editor) Excluded No filters found Advanced filters NamespacesTagged edits Results to show 50 100 250 500 Group results by page Time period to search Recent hours 1 2 6 12 Recent days 1 3 7 14 30 Select a color --- # Related changes - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit_review) Related changes =============== ← [Category:Upgrade](https://pve.proxmox.com/wiki/Category:Upgrade "Category:Upgrade") [Jump to navigation](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Category:Upgrade#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Category:Upgrade#searchInput) Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category). Changes to pages on [your Watchlist](https://pve.proxmox.com/wiki/Special:Watchlist "Special:Watchlist") are in **bold**. Show changes on pages linked from **Pages linked from** the selected page **Pages linking to** the selected page Active filters Hide Human (not bot) No active filters. All contributions are shown. NamespacesTags Live updates 50 changes, 7 days No changes during the given period match these criteria. Retrieved from "[https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Category:Upgrade](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Category:Upgrade) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") No filters saved yet To save your filter settings and reuse them later, click the bookmark icon in the Active filters area, below. Filters [](https://pve.proxmox.com/wiki/Special:Tags "Learn more about Tagged edits") Exclude selected Exclude selected Highlight results User registration and experience Unregistered Editors who aren't logged-in. Excluded Registered Logged-in editors. Excluded Newcomers Registered editors who have fewer than 10 edits or 4 days of activity. Excluded Learners Registered editors whose experience falls between "Newcomers" and "Experienced users." Excluded Experienced users Registered editors with more than 500 edits and 30 days of activity. Excluded Contribution authorship Changes by you Your own contributions. Excluded Changes by others All changes except your own. Excluded Automated contributions Bot Edits made by automated tools. Excluded Human (not bot) Edits made by human editors. Excluded Significance Minor edits Edits the author labeled as minor. Excluded Non-minor edits Edits not labeled as minor. Excluded Latest revisions Latest revision Only the most recent change to a page. Excluded Not the latest revision All changes that are not the "latest revision". Excluded Type of change Page edits Edits to wiki content, discussions, category descriptions… Excluded Page creations Edits that make new pages. Excluded Logged actions Administrative actions, page deletions, uploads… Excluded Account creations Log entries for account creation. Logged actions must be selected. Excluded All contents Excluded All discussions Excluded (Main) Excluded Talk Excluded User Excluded User talk Excluded Proxmox VE Excluded Proxmox VE talk Excluded File Excluded File talk Excluded MediaWiki Excluded MediaWiki talk Excluded Template Excluded Template talk Excluded Help Excluded Help talk Excluded Category Excluded Category talk Excluded Module Excluded Module talk Excluded Special Excluded Manual revert Edits that manually restore the page to an exact previous state Excluded New redirect Edits that create a new redirect or change a page to a redirect Excluded Removed redirect Edits that change an existing redirect to a non-redirect Excluded Replaced Edits that remove more than 90% of the content of a page Excluded Reverted Edits that were later reverted by a different edit Excluded Rollback Edits that roll back previous edits using the rollback link Excluded Undo Edits that undo previous edits using the undo link Excluded Visual edit: Switched User started to edit using the visual editor, then changed to the wikitext editor. Excluded wikieditor (hidden tag) Edit made using WikiEditor (2010 wikitext editor) Excluded No filters found Advanced filters NamespacesTagged edits Results to show 50 100 250 500 Group results by page Time period to search Recent hours 1 2 6 12 Recent days 1 3 7 14 30 Select a color --- # Storage: GlusterFS - Proxmox VE Storage: GlusterFS ================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/Storage:_GlusterFS#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Storage:_GlusterFS#searchInput) There is currently no text in this page. You can [search for this page title](https://pve.proxmox.com/wiki/Special:Search/Storage:_GlusterFS "Special:Search/Storage: GlusterFS") in other pages, or [search the related logs](https://pve.proxmox.com/mediawiki/index.php?title=Special:Log&page=Storage:_GlusterFS) , but you do not have permission to create this page. Retrieved from "[https://pve.proxmox.com/wiki/Storage:\_GlusterFS](https://pve.proxmox.com/wiki/Storage:_GlusterFS) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Api-viewer/index.html - Proxmox VE Api-viewer/index.html ===================== From Proxmox VE [Jump to navigation](https://pve.proxmox.com/wiki/api-viewer/index.html#mw-head) [Jump to search](https://pve.proxmox.com/wiki/api-viewer/index.html#searchInput) There is currently no text in this page. You can [search for this page title](https://pve.proxmox.com/wiki/Special:Search/Api-viewer/index.html "Special:Search/Api-viewer/index.html") in other pages, or [search the related logs](https://pve.proxmox.com/mediawiki/index.php?title=Special:Log&page=Api-viewer/index.html) , but you do not have permission to create this page. Retrieved from "[https://pve.proxmox.com/wiki/Api-viewer/index.html](https://pve.proxmox.com/wiki/Api-viewer/index.html) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") --- # Related changes - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit_review) Related changes =============== ← [Category:Troubleshooting](https://pve.proxmox.com/wiki/Category:Troubleshooting "Category:Troubleshooting") [Jump to navigation](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Category:Troubleshooting#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Category:Troubleshooting#searchInput) Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category). Changes to pages on [your Watchlist](https://pve.proxmox.com/wiki/Special:Watchlist "Special:Watchlist") are in **bold**. Show changes on pages linked from **Pages linked from** the selected page **Pages linking to** the selected page Active filters Hide Human (not bot) No active filters. All contributions are shown. NamespacesTags Live updates 50 changes, 7 days No changes during the given period match these criteria. Retrieved from "[https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Category:Troubleshooting](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Category:Troubleshooting) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") No filters saved yet To save your filter settings and reuse them later, click the bookmark icon in the Active filters area, below. Filters [](https://pve.proxmox.com/wiki/Special:Tags "Learn more about Tagged edits") Exclude selected Exclude selected Highlight results User registration and experience Unregistered Editors who aren't logged-in. Excluded Registered Logged-in editors. Excluded Newcomers Registered editors who have fewer than 10 edits or 4 days of activity. Excluded Learners Registered editors whose experience falls between "Newcomers" and "Experienced users." Excluded Experienced users Registered editors with more than 500 edits and 30 days of activity. Excluded Contribution authorship Changes by you Your own contributions. Excluded Changes by others All changes except your own. Excluded Automated contributions Bot Edits made by automated tools. Excluded Human (not bot) Edits made by human editors. Excluded Significance Minor edits Edits the author labeled as minor. Excluded Non-minor edits Edits not labeled as minor. Excluded Latest revisions Latest revision Only the most recent change to a page. Excluded Not the latest revision All changes that are not the "latest revision". Excluded Type of change Page edits Edits to wiki content, discussions, category descriptions… Excluded Page creations Edits that make new pages. Excluded Logged actions Administrative actions, page deletions, uploads… Excluded Account creations Log entries for account creation. Logged actions must be selected. Excluded All contents Excluded All discussions Excluded (Main) Excluded Talk Excluded User Excluded User talk Excluded Proxmox VE Excluded Proxmox VE talk Excluded File Excluded File talk Excluded MediaWiki Excluded MediaWiki talk Excluded Template Excluded Template talk Excluded Help Excluded Help talk Excluded Category Excluded Category talk Excluded Module Excluded Module talk Excluded Special Excluded Manual revert Edits that manually restore the page to an exact previous state Excluded New redirect Edits that create a new redirect or change a page to a redirect Excluded Removed redirect Edits that change an existing redirect to a non-redirect Excluded Replaced Edits that remove more than 90% of the content of a page Excluded Reverted Edits that were later reverted by a different edit Excluded Rollback Edits that roll back previous edits using the rollback link Excluded Undo Edits that undo previous edits using the undo link Excluded Visual edit: Switched User started to edit using the visual editor, then changed to the wikitext editor. Excluded wikieditor (hidden tag) Edit made using WikiEditor (2010 wikitext editor) Excluded No filters found Advanced filters NamespacesTagged edits Results to show 50 100 250 500 Group results by page Time period to search Recent hours 1 2 6 12 Recent days 1 3 7 14 30 Select a color --- # Related changes - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit_review) Related changes =============== ← [Category:Proxmox VE 3.x](https://pve.proxmox.com/wiki/Category:Proxmox_VE_3.x "Category:Proxmox VE 3.x") [Jump to navigation](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Category:Proxmox_VE_3.x#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Category:Proxmox_VE_3.x#searchInput) Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category). Changes to pages on [your Watchlist](https://pve.proxmox.com/wiki/Special:Watchlist "Special:Watchlist") are in **bold**. Show changes on pages linked from **Pages linked from** the selected page **Pages linking to** the selected page Active filters Hide Human (not bot) No active filters. All contributions are shown. NamespacesTags Live updates 50 changes, 7 days No changes during the given period match these criteria. Retrieved from "[https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Category:Proxmox\_VE\_3.x](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Category:Proxmox_VE_3.x) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") No filters saved yet To save your filter settings and reuse them later, click the bookmark icon in the Active filters area, below. Filters [](https://pve.proxmox.com/wiki/Special:Tags "Learn more about Tagged edits") Exclude selected Exclude selected Highlight results User registration and experience Unregistered Editors who aren't logged-in. Excluded Registered Logged-in editors. Excluded Newcomers Registered editors who have fewer than 10 edits or 4 days of activity. Excluded Learners Registered editors whose experience falls between "Newcomers" and "Experienced users." Excluded Experienced users Registered editors with more than 500 edits and 30 days of activity. Excluded Contribution authorship Changes by you Your own contributions. Excluded Changes by others All changes except your own. Excluded Automated contributions Bot Edits made by automated tools. Excluded Human (not bot) Edits made by human editors. Excluded Significance Minor edits Edits the author labeled as minor. Excluded Non-minor edits Edits not labeled as minor. Excluded Latest revisions Latest revision Only the most recent change to a page. Excluded Not the latest revision All changes that are not the "latest revision". Excluded Type of change Page edits Edits to wiki content, discussions, category descriptions… Excluded Page creations Edits that make new pages. Excluded Logged actions Administrative actions, page deletions, uploads… Excluded Account creations Log entries for account creation. Logged actions must be selected. Excluded All contents Excluded All discussions Excluded (Main) Excluded Talk Excluded User Excluded User talk Excluded Proxmox VE Excluded Proxmox VE talk Excluded File Excluded File talk Excluded MediaWiki Excluded MediaWiki talk Excluded Template Excluded Template talk Excluded Help Excluded Help talk Excluded Category Excluded Category talk Excluded Module Excluded Module talk Excluded Special Excluded Manual revert Edits that manually restore the page to an exact previous state Excluded New redirect Edits that create a new redirect or change a page to a redirect Excluded Removed redirect Edits that change an existing redirect to a non-redirect Excluded Replaced Edits that remove more than 90% of the content of a page Excluded Reverted Edits that were later reverted by a different edit Excluded Rollback Edits that roll back previous edits using the rollback link Excluded Undo Edits that undo previous edits using the undo link Excluded Visual edit: Switched User started to edit using the visual editor, then changed to the wikitext editor. Excluded wikieditor (hidden tag) Edit made using WikiEditor (2010 wikitext editor) Excluded No filters found Advanced filters NamespacesTagged edits Results to show 50 100 250 500 Group results by page Time period to search Recent hours 1 2 6 12 Recent days 1 3 7 14 30 Select a color --- # Related changes - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit_review) Related changes =============== ← [Backup and Restore](https://pve.proxmox.com/wiki/Backup_and_Restore "Backup and Restore") [Jump to navigation](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Backup_and_Restore#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Backup_and_Restore#searchInput) Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category). Changes to pages on [your Watchlist](https://pve.proxmox.com/wiki/Special:Watchlist "Special:Watchlist") are in **bold**. Show changes on pages linked from **Pages linked from** the selected page **Pages linking to** the selected page Active filters Hide Human (not bot) No active filters. All contributions are shown. NamespacesTags Live updates 50 changes, 7 days No changes during the given period match these criteria. Retrieved from "[https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Backup\_and\_Restore](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Backup_and_Restore) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") No filters saved yet To save your filter settings and reuse them later, click the bookmark icon in the Active filters area, below. Filters [](https://pve.proxmox.com/wiki/Special:Tags "Learn more about Tagged edits") Exclude selected Exclude selected Highlight results User registration and experience Unregistered Editors who aren't logged-in. Excluded Registered Logged-in editors. Excluded Newcomers Registered editors who have fewer than 10 edits or 4 days of activity. Excluded Learners Registered editors whose experience falls between "Newcomers" and "Experienced users." Excluded Experienced users Registered editors with more than 500 edits and 30 days of activity. Excluded Contribution authorship Changes by you Your own contributions. Excluded Changes by others All changes except your own. Excluded Automated contributions Bot Edits made by automated tools. Excluded Human (not bot) Edits made by human editors. Excluded Significance Minor edits Edits the author labeled as minor. Excluded Non-minor edits Edits not labeled as minor. Excluded Latest revisions Latest revision Only the most recent change to a page. Excluded Not the latest revision All changes that are not the "latest revision". Excluded Type of change Page edits Edits to wiki content, discussions, category descriptions… Excluded Page creations Edits that make new pages. Excluded Logged actions Administrative actions, page deletions, uploads… Excluded Account creations Log entries for account creation. Logged actions must be selected. Excluded All contents Excluded All discussions Excluded (Main) Excluded Talk Excluded User Excluded User talk Excluded Proxmox VE Excluded Proxmox VE talk Excluded File Excluded File talk Excluded MediaWiki Excluded MediaWiki talk Excluded Template Excluded Template talk Excluded Help Excluded Help talk Excluded Category Excluded Category talk Excluded Module Excluded Module talk Excluded Special Excluded Manual revert Edits that manually restore the page to an exact previous state Excluded New redirect Edits that create a new redirect or change a page to a redirect Excluded Removed redirect Edits that change an existing redirect to a non-redirect Excluded Replaced Edits that remove more than 90% of the content of a page Excluded Reverted Edits that were later reverted by a different edit Excluded Rollback Edits that roll back previous edits using the rollback link Excluded Undo Edits that undo previous edits using the undo link Excluded Visual edit: Switched User started to edit using the visual editor, then changed to the wikitext editor. Excluded wikieditor (hidden tag) Edit made using WikiEditor (2010 wikitext editor) Excluded No filters found Advanced filters NamespacesTagged edits Results to show 50 100 250 500 Group results by page Time period to search Recent hours 1 2 6 12 Recent days 1 3 7 14 30 Select a color --- # Related changes - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit_review) Related changes =============== ← [Convert OpenVZ to LXC](https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC "Convert OpenVZ to LXC") [Jump to navigation](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Convert_OpenVZ_to_LXC#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Convert_OpenVZ_to_LXC#searchInput) Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category). Changes to pages on [your Watchlist](https://pve.proxmox.com/wiki/Special:Watchlist "Special:Watchlist") are in **bold**. Show changes on pages linked from **Pages linked from** the selected page **Pages linking to** the selected page Active filters Hide Human (not bot) No active filters. All contributions are shown. NamespacesTags Live updates 50 changes, 7 days No changes during the given period match these criteria. Retrieved from "[https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Convert\_OpenVZ\_to\_LXC](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Convert_OpenVZ_to_LXC) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") No filters saved yet To save your filter settings and reuse them later, click the bookmark icon in the Active filters area, below. Filters [](https://pve.proxmox.com/wiki/Special:Tags "Learn more about Tagged edits") Exclude selected Exclude selected Highlight results User registration and experience Unregistered Editors who aren't logged-in. Excluded Registered Logged-in editors. Excluded Newcomers Registered editors who have fewer than 10 edits or 4 days of activity. Excluded Learners Registered editors whose experience falls between "Newcomers" and "Experienced users." Excluded Experienced users Registered editors with more than 500 edits and 30 days of activity. Excluded Contribution authorship Changes by you Your own contributions. Excluded Changes by others All changes except your own. Excluded Automated contributions Bot Edits made by automated tools. Excluded Human (not bot) Edits made by human editors. Excluded Significance Minor edits Edits the author labeled as minor. Excluded Non-minor edits Edits not labeled as minor. Excluded Latest revisions Latest revision Only the most recent change to a page. Excluded Not the latest revision All changes that are not the "latest revision". Excluded Type of change Page edits Edits to wiki content, discussions, category descriptions… Excluded Page creations Edits that make new pages. Excluded Logged actions Administrative actions, page deletions, uploads… Excluded Account creations Log entries for account creation. Logged actions must be selected. Excluded All contents Excluded All discussions Excluded (Main) Excluded Talk Excluded User Excluded User talk Excluded Proxmox VE Excluded Proxmox VE talk Excluded File Excluded File talk Excluded MediaWiki Excluded MediaWiki talk Excluded Template Excluded Template talk Excluded Help Excluded Help talk Excluded Category Excluded Category talk Excluded Module Excluded Module talk Excluded Special Excluded Manual revert Edits that manually restore the page to an exact previous state Excluded New redirect Edits that create a new redirect or change a page to a redirect Excluded Removed redirect Edits that change an existing redirect to a non-redirect Excluded Replaced Edits that remove more than 90% of the content of a page Excluded Reverted Edits that were later reverted by a different edit Excluded Rollback Edits that roll back previous edits using the rollback link Excluded Undo Edits that undo previous edits using the undo link Excluded Visual edit: Switched User started to edit using the visual editor, then changed to the wikitext editor. Excluded wikieditor (hidden tag) Edit made using WikiEditor (2010 wikitext editor) Excluded No filters found Advanced filters NamespacesTagged edits Results to show 50 100 250 500 Group results by page Time period to search Recent hours 1 2 6 12 Recent days 1 3 7 14 30 Select a color --- # Related changes - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit_review) Related changes =============== ← [Cluster Manager](https://pve.proxmox.com/wiki/Cluster_Manager "Cluster Manager") [Jump to navigation](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Cluster_Manager#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Cluster_Manager#searchInput) Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category). Changes to pages on [your Watchlist](https://pve.proxmox.com/wiki/Special:Watchlist "Special:Watchlist") are in **bold**. Show changes on pages linked from **Pages linked from** the selected page **Pages linking to** the selected page Active filters Hide Human (not bot) No active filters. All contributions are shown. NamespacesTags Live updates 50 changes, 7 days No changes during the given period match these criteria. Retrieved from "[https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Cluster\_Manager](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Cluster_Manager) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") No filters saved yet To save your filter settings and reuse them later, click the bookmark icon in the Active filters area, below. Filters [](https://pve.proxmox.com/wiki/Special:Tags "Learn more about Tagged edits") Exclude selected Exclude selected Highlight results User registration and experience Unregistered Editors who aren't logged-in. Excluded Registered Logged-in editors. Excluded Newcomers Registered editors who have fewer than 10 edits or 4 days of activity. Excluded Learners Registered editors whose experience falls between "Newcomers" and "Experienced users." Excluded Experienced users Registered editors with more than 500 edits and 30 days of activity. Excluded Contribution authorship Changes by you Your own contributions. Excluded Changes by others All changes except your own. Excluded Automated contributions Bot Edits made by automated tools. Excluded Human (not bot) Edits made by human editors. Excluded Significance Minor edits Edits the author labeled as minor. Excluded Non-minor edits Edits not labeled as minor. Excluded Latest revisions Latest revision Only the most recent change to a page. Excluded Not the latest revision All changes that are not the "latest revision". Excluded Type of change Page edits Edits to wiki content, discussions, category descriptions… Excluded Page creations Edits that make new pages. Excluded Logged actions Administrative actions, page deletions, uploads… Excluded Account creations Log entries for account creation. Logged actions must be selected. Excluded All contents Excluded All discussions Excluded (Main) Excluded Talk Excluded User Excluded User talk Excluded Proxmox VE Excluded Proxmox VE talk Excluded File Excluded File talk Excluded MediaWiki Excluded MediaWiki talk Excluded Template Excluded Template talk Excluded Help Excluded Help talk Excluded Category Excluded Category talk Excluded Module Excluded Module talk Excluded Special Excluded Manual revert Edits that manually restore the page to an exact previous state Excluded New redirect Edits that create a new redirect or change a page to a redirect Excluded Removed redirect Edits that change an existing redirect to a non-redirect Excluded Replaced Edits that remove more than 90% of the content of a page Excluded Reverted Edits that were later reverted by a different edit Excluded Rollback Edits that roll back previous edits using the rollback link Excluded Undo Edits that undo previous edits using the undo link Excluded Visual edit: Switched User started to edit using the visual editor, then changed to the wikitext editor. Excluded wikieditor (hidden tag) Edit made using WikiEditor (2010 wikitext editor) Excluded No filters found Advanced filters NamespacesTagged edits Results to show 50 100 250 500 Group results by page Time period to search Recent hours 1 2 6 12 Recent days 1 3 7 14 30 Select a color --- # Related changes - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit_review) Related changes =============== ← [Upgrade from 6.x to 7.0](https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0 "Upgrade from 6.x to 7.0") [Jump to navigation](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Upgrade_from_6.x_to_7.0#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Upgrade_from_6.x_to_7.0#searchInput) Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category). Changes to pages on [your Watchlist](https://pve.proxmox.com/wiki/Special:Watchlist "Special:Watchlist") are in **bold**. Show changes on pages linked from **Pages linked from** the selected page **Pages linking to** the selected page Active filters Hide Human (not bot) No active filters. All contributions are shown. NamespacesTags Live updates 50 changes, 7 days No changes during the given period match these criteria. Retrieved from "[https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Upgrade\_from\_6.x\_to\_7.0](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/Upgrade_from_6.x_to_7.0) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") No filters saved yet To save your filter settings and reuse them later, click the bookmark icon in the Active filters area, below. Filters [](https://pve.proxmox.com/wiki/Special:Tags "Learn more about Tagged edits") Exclude selected Exclude selected Highlight results User registration and experience Unregistered Editors who aren't logged-in. Excluded Registered Logged-in editors. Excluded Newcomers Registered editors who have fewer than 10 edits or 4 days of activity. Excluded Learners Registered editors whose experience falls between "Newcomers" and "Experienced users." Excluded Experienced users Registered editors with more than 500 edits and 30 days of activity. Excluded Contribution authorship Changes by you Your own contributions. Excluded Changes by others All changes except your own. Excluded Automated contributions Bot Edits made by automated tools. Excluded Human (not bot) Edits made by human editors. Excluded Significance Minor edits Edits the author labeled as minor. Excluded Non-minor edits Edits not labeled as minor. Excluded Latest revisions Latest revision Only the most recent change to a page. Excluded Not the latest revision All changes that are not the "latest revision". Excluded Type of change Page edits Edits to wiki content, discussions, category descriptions… Excluded Page creations Edits that make new pages. Excluded Logged actions Administrative actions, page deletions, uploads… Excluded Account creations Log entries for account creation. Logged actions must be selected. Excluded All contents Excluded All discussions Excluded (Main) Excluded Talk Excluded User Excluded User talk Excluded Proxmox VE Excluded Proxmox VE talk Excluded File Excluded File talk Excluded MediaWiki Excluded MediaWiki talk Excluded Template Excluded Template talk Excluded Help Excluded Help talk Excluded Category Excluded Category talk Excluded Module Excluded Module talk Excluded Special Excluded Manual revert Edits that manually restore the page to an exact previous state Excluded New redirect Edits that create a new redirect or change a page to a redirect Excluded Removed redirect Edits that change an existing redirect to a non-redirect Excluded Replaced Edits that remove more than 90% of the content of a page Excluded Reverted Edits that were later reverted by a different edit Excluded Rollback Edits that roll back previous edits using the rollback link Excluded Undo Edits that undo previous edits using the undo link Excluded Visual edit: Switched User started to edit using the visual editor, then changed to the wikitext editor. Excluded wikieditor (hidden tag) Edit made using WikiEditor (2010 wikitext editor) Excluded No filters found Advanced filters NamespacesTagged edits Results to show 50 100 250 500 Group results by page Time period to search Recent hours 1 2 6 12 Recent days 1 3 7 14 30 Select a color --- # Related changes - Proxmox VE [Help](https://www.mediawiki.org/wiki/Special:MyLanguage/Help:New_filters_for_edit_review) Related changes =============== ← [User Management](https://pve.proxmox.com/wiki/User_Management "User Management") [Jump to navigation](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/User_Management#mw-head) [Jump to search](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/User_Management#searchInput) Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category). Changes to pages on [your Watchlist](https://pve.proxmox.com/wiki/Special:Watchlist "Special:Watchlist") are in **bold**. Show changes on pages linked from **Pages linked from** the selected page **Pages linking to** the selected page Active filters Hide Human (not bot) No active filters. All contributions are shown. NamespacesTags Live updates 50 changes, 7 days No changes during the given period match these criteria. Retrieved from "[https://pve.proxmox.com/wiki/Special:RecentChangesLinked/User\_Management](https://pve.proxmox.com/wiki/Special:RecentChangesLinked/User_Management) " Cookies help us deliver our services. By using our services, you agree to our use of cookies. [More information](https://www.proxmox.com/en/privacy-policy) OK Navigation menu --------------- ### Search [](https://pve.proxmox.com/wiki/Main_Page "Visit the main page") No filters saved yet To save your filter settings and reuse them later, click the bookmark icon in the Active filters area, below. Filters [](https://pve.proxmox.com/wiki/Special:Tags "Learn more about Tagged edits") Exclude selected Exclude selected Highlight results User registration and experience Unregistered Editors who aren't logged-in. Excluded Registered Logged-in editors. Excluded Newcomers Registered editors who have fewer than 10 edits or 4 days of activity. Excluded Learners Registered editors whose experience falls between "Newcomers" and "Experienced users." Excluded Experienced users Registered editors with more than 500 edits and 30 days of activity. Excluded Contribution authorship Changes by you Your own contributions. Excluded Changes by others All changes except your own. Excluded Automated contributions Bot Edits made by automated tools. Excluded Human (not bot) Edits made by human editors. Excluded Significance Minor edits Edits the author labeled as minor. Excluded Non-minor edits Edits not labeled as minor. Excluded Latest revisions Latest revision Only the most recent change to a page. Excluded Not the latest revision All changes that are not the "latest revision". Excluded Type of change Page edits Edits to wiki content, discussions, category descriptions… Excluded Page creations Edits that make new pages. Excluded Logged actions Administrative actions, page deletions, uploads… Excluded Account creations Log entries for account creation. Logged actions must be selected. Excluded All contents Excluded All discussions Excluded (Main) Excluded Talk Excluded User Excluded User talk Excluded Proxmox VE Excluded Proxmox VE talk Excluded File Excluded File talk Excluded MediaWiki Excluded MediaWiki talk Excluded Template Excluded Template talk Excluded Help Excluded Help talk Excluded Category Excluded Category talk Excluded Module Excluded Module talk Excluded Special Excluded Manual revert Edits that manually restore the page to an exact previous state Excluded New redirect Edits that create a new redirect or change a page to a redirect Excluded Removed redirect Edits that change an existing redirect to a non-redirect Excluded Replaced Edits that remove more than 90% of the content of a page Excluded Reverted Edits that were later reverted by a different edit Excluded Rollback Edits that roll back previous edits using the rollback link Excluded Undo Edits that undo previous edits using the undo link Excluded Visual edit: Switched User started to edit using the visual editor, then changed to the wikitext editor. Excluded wikieditor (hidden tag) Edit made using WikiEditor (2010 wikitext editor) Excluded No filters found Advanced filters NamespacesTagged edits Results to show 50 100 250 500 Group results by page Time period to search Recent hours 1 2 6 12 Recent days 1 3 7 14 30 Select a color ---