We will now take a look at the networking components of Proxmox, which allow virtual machines to communicate with or be segmented from other internal machines as well as the internet.
- Preface
- Understanding Proxmox VE and Advanced Installation
- Creating a Cluster and Exploring the Proxmox GUI
- Creating a Proxmox cluster
- Exploring the Proxmox GUI
- The GUI menu system
- Cluster tree view
- Server View
- Folder View
- Storage View
- Pool View
- The Datacenter menu
- Node-specific menus
- KVM menu
- LXC container menu
- Pool menu
- Summary
- Proxmox under the Hood
- The Proxmox cluster file system
- Proxmox directory structure
- Dissecting the configuration files
- The cluster configuration file
- Storage configuration file
- User configuration files
- The password configuration file
- KVM virtual machine configuration file
- Arguments in the KVM configuration file
- LXC container configuration file
- Version configuration file
- Member nodes
- Virtual machine list file
- The cluster log file
- Ceph configuration files
- Firewall configuration file
- Summary
- Storage Systems
- Installing and Configuring Ceph
- KVM Virtual Machines
- LXC Virtual Machines
- Network of Virtual Networks
- Exploring virtual networks
- Physical networks versus virtual networks
- Networking components in Proxmox
- Open vSwitch
- Sample virtual networks
- A multi-tenant virtual environment
- Summary
- The Proxmox VE Firewall
- Proxmox High Availability
- Monitoring the Proxmox Cluster
- Proxmox Production-Level Setup
- Defining the production level
- Sizing CPU and memory
- Ceph cluster production
- Liquid cooling
- Real-world Proxmox scenarios
- Scenario 1 – an academic institution
- Scenario 2 – multi-tier storage cluster with a Proxmox cluster
- Scenario 3 - Virtual infrastructure for a multi-tenant cloud service provider
- Scenario 4 – nested virtual environment for a software development company
- Scenario 5 – virtual infrastructure for a public library
- Scenario 6 – multi-floor office virtual infrastructure with virtual desktops
- Scenario 7 – virtual infrastructure for the hotel industry
- Scenario 8 – virtual infrastructure for geological survey organization
- Summary
- Back Up and Restore Virtual Machines
- Updating/Upgrading Proxmox
- Proxmox Troubleshooting
- Proxmox node issues
- Issue – fresh Proxmox install stuck with /dev to be a fully populated error during node reboot
- Issue – rejoining a node to a Proxmox node with the same old IP address
- Issue – Proxmox installation completed but grub is in an endless loop after reboot
- Issue – LSI MegaRAID 9240-8i/9240-4i causes an error during booting of the Proxmox node
- Issue – the Upgrade button is disabled on the Proxmox GUI, which prevents the node upgrade
- Issue – Proxmox cannot start due to the getpwnam error
- Issue – cannot log in to the GUI as root after reinstalling Proxmox on the same node
- The main cluster issues
- Issue – Proxmox virtual machines are running, but the Proxmox GUI shows that everything is offline
- Issue – kernel panic when disconnecting USB devices, such as a keyboard, mouse, or UPS
- Issue – virtual machines on Proxmox will not shut down if shutdown is initiated from the Proxmox GUI
- Issue – kernel panic with HP NC360T (Intel 82571EB chipset) only in Proxmox VE 3.2
- Issue – the Proxmox cluster is out of quorum and cluster filesystem is in read-only mode
- Issue – VM will not respond to shutdown or restart
- Issue – Proxmox GUI not responding after Firefox update
- Issue – the Proxmox GUI is not showing RRD graphs
- Storage issues
- Issue – deleting a damaged LVM from Proxmox with the error read failed from 0 to 4096
- Issue – Proxmox cannot mount NFS share due to the timing out error
- Issue – how to delete leftover NFS shares in Proxmox or what to do when the NFS stale file handle error occurs?
- Issue – Proxmox issues --mode session exit code 21 errors while trying to access the iSCSI target
- Issue – cannot read an iSCSI target even after it has been deleted from Proxmox storage
- Issue – a Ceph node is removed from the Proxmox cluster, but OSDs still show up in PVE
- Issue – the no such block device error during creation of an OSD through the Proxmox GUI
- Issue – the fstrim command does not trim unused blocks for the Ceph storage
- Issue – the RBD couldn't connect to cluster (500) error when connecting Ceph with Proxmox
- Issue – changing the storage type from IDE to VirtIO after the VM has been set up and the OS has been installed
- Issue – the pveceph configuration not initialized (500) error when you click on the Ceph tab in the Proxmox GUI
- Issue – the CephFS storage disappears after a Proxmox node reboots
- Issue – VM cloning does not parse in the Ceph storage
- Issue – VM disk images stored on ZFS is extremely slow
- Network connectivity issues
- Issue – no connectivity on Realtek RTL8111/8411 rev. 06 network interfaces
- Issue – network performance is slower with the E1000 virtual network interfaces
- Issue – patch port for Open vSwitch in Proxmox not working
- Issue – trying to add a node to a newly created Proxmox cluster when nodes do not form quorum
- Issue – implemented IPv6 but firewall rules do not get applied
- KVM virtual machine issues
- Issue – Windows 7/XP machine converted to Proxmox KVM hangs during boot
- Issue – Windows 7 VM does not reboot, instead it shuts down, requiring a manual boot from Proxmox
- Issue – the qemu-img command does not convert the .vmdk image files created with the .ova template in Proxmox VE 5.0
- Issue – online migration of a virtual machine fails with a failed to sync data error
- Issue – no audio in Windows KVM
- Issue – the VirtIO virtual disk is not available during the Windows Server installation
- LXC container issues
- Backup/restore issues
- Issue – a Proxmox VM is locked after backup crashes unexpectedly
- Issue – how can Proxmox back up only the primary OS virtual disk instead of all the virtual disks for a VM?
- Issue – backup of virtual machines stops prematurely with an operation not permitted error
- Issue – a backup task takes a very long time to complete, or it crashes when multiple nodes are backing up to the same backup storage
- Issue – backup of virtual machines aborts a backup task prematurely
- Issue – backup storage has a lot of .dat files and .tmp folders using the storage space
- VNC/SPICE console issues
- Firewall issues
- Summary
- Proxmox node issues
- Rescuing Proxmox
Networking components in Proxmox
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.