User Tools

Site Tools


virtualization:proxmox

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
virtualization:proxmox [2013/03/04 16:45]
gcooper
virtualization:proxmox [2019/08/05 14:35]
gcooper
Line 3: Line 3:
 {{:virtualization:proxmox_logo.png?nolink&|}} {{:virtualization:proxmox_logo.png?nolink&|}}
  
-**Main**: http://www.proxmox.com/products/proxmox-ve+**Main**: https://www.proxmox.com/en/proxmox-ve
  
-**Wiki**: http://pve.proxmox.com/wiki/Documentation+**Wiki**: http://pve.proxmox.com/wiki/
  
-**Forums**: http://forum.proxmox.com/forum.php+**Documentation**: https://pve.proxmox.com/pve-docs/
  
-Proxmox VE is a 64-bit, free, open-source, bare-metal virtualization platform (hypervisor).  While it may not have as full a feature set as some other commercial hypervisors, it is none the less very attractive and easy to use.+**Forums**: http://forum.proxmox.com/ 
 + 
 +Proxmox VE is a 64-bit, free, open-source, bare-metal virtualization platform (hypervisor).
  
 Proxmox VE provides two virtualization technologies in one platform: Proxmox VE provides two virtualization technologies in one platform:
Line 17: Line 19:
  
 KVM requires hardware (CPU+mainboard) virtualization support. KVM requires hardware (CPU+mainboard) virtualization support.
 +
 +===== Administration =====
 +
 +Proxmox VE Clusters can be managed from any of the cluster hosts.
 +
 +<file>
 +https://<ipaddress>:8006
 +</file>
 +
 +===== Installation =====
 +
 +:!: Use **[[https://www.balena.io/etcher/|Etcher]]** to write the ISO to a flash drive.
 +
 +:!: The installer is graphical and **requires a mouse**.
 +
 +**Download**: https://www.proxmox.com/en/downloads
  
 ===== Updating and Upgrading ===== ===== Updating and Upgrading =====
 +
 +
 +Proxmox VE comes pre-configured to use the 'enterprise' (paid subscription) package repository.  If you don't have a subscription, you must reconfigure the repository:
 +
 +First, comment out the 'enterprise' repo:
  
 <file> <file>
-apt-get update +vi /etc/apt/sources.list.d/pve-enterprise.list
-apt-get dist-upgrade+
 </file> </file>
 +
 +Then clone the 'enterprise' repo file and modify it:
 +
 +<file>
 +cp -a /etc/apt/sources.list.d/pve-enterprise.list /etc/apt/sources.list.d/pve-no-sub.list
 +
 +vi /etc/apt/sources.list.d/pve-no-sub.list
 +
 +deb http://download.proxmox.com/debian/pve buster pve-no-subscription
 +
 +apt update
 +apt dist-upgrade
 +reboot
 +</file>
 +----
 +
 +
 +FIXME All very old below this point!
 +
  
 ===== PVE Host Networking ===== ===== PVE Host Networking =====
Line 154: Line 195:
   * All VMs can share one bridge as if virtual network cables from each guest were all plugged into the same switch   * 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 connecting VMs to the outside world, bridges are attached to physical network cards and assigned a TCP/IP configuration
-  * VLANs (IEEE 802.1q) and network bonding/aggregation are possible +  * VLANs (IEEE 802.1q) and network bonding/aggregation are possible with KVM
-  * ''venet'' IP addresses are assgned by the OpenVZ admin (possibly more secure) +
-  * ''veth'' networking is more like regular Linux networking (IP assigned by guest 'root' admin)+
  
-==== Static IP ====+==== venet ====
  
-For a static guest IP address, choose **Virtual Network (venet)** when creating the VM.+  Networking configuration is assigned by OpenVZ admin 
 +  Possibly more secure since VM owners can't set the IP addresses 
 +  Possibly faster than ''veth''
  
-==== Bridged ====+==== veth ====
  
-Choose **Bridged Network** to get an IP address from your **DHCP** server.+  More like regular Linux networking 
 +  Networking configuration is assigned by VM owner 
 +  Has MAC address to support more networking configurations 
 +  Used to get an IP address from your DHCP server 
 +  Works with a pair of interfaces connected together 
 +    One in the host OS (host node, container zero, HN, CT0) and the other in the CT (container) 
 +  * Packets sent to the HN interface come out in the CT
  
 ==== Multiple NICs for OpenVZ Containers ==== ==== Multiple NICs for OpenVZ Containers ====
Line 170: Line 217:
 http://forum.proxmox.com/threads/3442-Multiple-NICs-for-OpenVZ-containers http://forum.proxmox.com/threads/3442-Multiple-NICs-for-OpenVZ-containers
  
-venet:+=== venet ===
  
   * You can assign multiple IP addresses   * You can assign multiple IP addresses
   * Just add them after you created the container (separated with spaces) using the GUI   * Just add them after you created the container (separated with spaces) using the GUI
  
-veth:+=== veth ===
  
   * Use the CLI   * Use the CLI
virtualization/proxmox.txt · Last modified: 2019/08/10 21:47 by gcooper