Differences

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

--- virtualization:proxmox [2013/02/28 18:08]
gcooper
+++ virtualization:proxmox [2019/08/10 21:47] (current)
gcooper
@@ Line 3: / Line 3: @@
 {{: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:
@@ Line 17: / Line 19: @@
 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 =====
+:!: **Proxmox VE comes pre-configured to use the 'enterprise' (paid subscription) package repository.**
+==== No Subscription ====
+If you don't have a subscription, you must reconfigure the repository:
+First, comment out the 'enterprise' repo:
 <file>
-apt-get update
+vi /etc/apt/sources.list.d/pve-enterprise.list
-apt-get dist-upgrade
 </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>
+==== Windows Guests ====
+**Windows 7**: https://pve.proxmox.com/wiki/Windows_7_guest_best_practices
+**Windows 8**: https://pve.proxmox.com/wiki/Windows_8_guest_best_practices
+**Windows 10**: https://pve.proxmox.com/wiki/Windows_10_guest_best_practices
+**Windows 2012**: https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices
+----
+FIXME All very old below this point!
 ===== PVE Host Networking =====
@@ Line 92: / Line 146: @@
   * Has near-zero overhead
   * Only works for Linux guests
+==== CentOS 5 Container (VM) ====
+When you first create a CentOS 5 VM, you must reconfigure a few things:
+From the PVE host CLI, we enter the VM:
+<file>
+vzctl enter CTID                                  #next steps are all now inside the VM
+</file>
+Enable Proxmox CT console so we can access it from the web management interface:
+<file>
+vim /etc/inittab
+</file>
+Add the following line and reboot:
+<file>
+:2345:respawn:/sbin/agetty tty1 38400 linux
+</file>
 ==== CentOS 6 Container (VM) ====
@@ Line 118: / Line 193: @@
 </file>
-Name resolution:
+Then reboot the VM.
-<file>
+===== Networking =====
-vim /etc/resolv.conf
-search myvirtualoffice.pro
+**Differences Between ''venet'' and ''veth''**: http://wiki.openvz.org/Differences_between_venet_and_veth
-nameserver 8.8.8.8
-nameserver 8.8.4.4
-</file>
-Host name:
+**Detailed ''veth'' Networking Info**: http://forum.openvz.org/index.php?t=msg&&th=6191&goto=36869#msg_36869
-<file>
+**''venet'' Docs**: http://openvz.org/Virtual_network_device
-vim /etc/hosts
-.168.1.30 pbx pbx.myvirtualoffice.pro
+**''veth'' Docs**: http://openvz.org/Virtual_Ethernet_device
-</file>
-===== Networking =====
-http://wiki.openvz.org/Differences_between_venet_and_veth
   * 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
-  * VLANs (IEEE 802.1q) and network bonding/aggregation are possible
+  * VLANs (IEEE 802.1q) and network bonding/aggregation are possible with KVM
-==== 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 ====
-venet:
+http://forum.proxmox.com/threads/3442-Multiple-NICs-for-OpenVZ-containers
+=== venet ===
   * You can assign multiple IP addresses
   * Just add them after you created the container (separated with spaces) using the GUI
-veth:
+=== veth ===
   * Use the CLI

Virtual Architects Support Wiki

User Tools

Site Tools

Differences

Page Tools