If you just have 1 disk per node/testing/POC then you can reduce the overall disk usage during install as below: 1.) Click on "Options" on the HDD that you want to install to. 2.) Under "hdsize" Set the Maximum Size smaller than the disk size. In this example the disk is 60G and I set max size as 20G. This then........

Proxmox's documentation shows the following here. Which mainly just says change /etc/hosts and /etc/hostname with your new hostname. Here's what happens if you only do that: If you just do the above, you will find you have an inaccessible original hostname that contains those VMs and you cannot........

If you are using a hypervisor to test Proxmox (eg. Vbox) then changing the video card/display adapter can fix it. For example VboxSVGA causes the issue but switching to VMSVGA fixes it. For example VboxSVGA causes the issue but switching to VMSVGA fixes it. ........

Docker adds iptables rules that break a lot of things including MASQUERADE or anything that needs the FORWARD table. If NAT is not working after Docker installation, it is probably because it set the iptables FORWARD policy to DROP. This may also make you think that your br0 or bridge is not working, but it's likely just due to what we'll mention later on below, that, Docker probably set your FORWARD chain to default DROP all packets, so nothing on your bridge ever makes it out........

This can be used on almost anything, since Gluster is a userspace tool, based on FUSE. This means that all Gluster appears as to any application is just a directory. Applications don't need specific support for Gluster, so long as you can tell the application to use a certain directory for storage. One application can be for redundant and scaled storage, including for within Docker and Kubernetes, LXC, Proxmox, OpenStack, etc or just your image/web/video files or even da........

1. Let's work from an environment where we can install Ansible on. If you are using an older version of Linux based on Mint 18 or Ubuntu 16, you may want to get the PPA and get the latest version of Ansible that way: sudo apt install gpg sudo add-apt-repository ppa:ansible/ansible sudo apt update........

This normally happens when you interrupt the install of Ceph: pveceph install update available package list start installation Reading package lists... Done Building dependency tree... Done Reading state information... Done gdisk is already the newest version (1.0.6-1.1). ceph-common is already the newest version (15.2.15-pve1). ceph-fuse is already the newest version (15.2.15-pve1). Some package........

Are you getting this error in Proxmox while trying to apt update or install Ceph? apt update Hit:1 http://security.debian.org bullseye-security InRelease Err:2 https://enterprise.proxmox.com/debian/pve bullseye InRelease 401 Unauthorized [IP: 144.217.225.162 443] Hit:3 http://ftp.hk.debian.org/debian bullseye InRelease ........

How To Install Ceph If you stopped an install of Ceph midway you will need to manually restart it with "pveceph install" Remember that your VM needs to have working internet (gateway) and DNS in order to connect to the apt repo to download all of the packages that Ceph requires. Remember to repeat these steps for each node that you want Ceph on. ........

There are many reasons why Proxmox services may not start, but one common one, is if you have changed your /etc/hostname or /etc/hosts and don't have a valid FQDN (eg. proxmox01 instead proxmox01.com). Failed to start The Proxmox VE cluster filesystem. Failed to start Proxmox VE firewall. Failed to start PVE Status Daemon. Failed to start Proxmox VE scheduler. Failed to start PVE Cluster HA Resource Manager Daemon. Failed to star........

How To Enable HA in Proxmox Test Your HA Shutdown the node that has the HA VM. ........

Install Errors on Version 12: This error happened on QEMU emulator version 2.11.1 pve-qemu-kvm_2.11.1-5 on Proxmox/Debian but installing on QEMU.12 on Centos 6 did not produce the error. *Update it is not related to the OS or QEMU version. This happened in Centos 6 too after a second install. What really causes this even though you successfully install........

The strange thing is that usually the first install or two will work on any new machine but then it suddenly won't. I had this experience on QEMU 2.13 on a different machine. There is something finicky or buggy about the CUCM installer even when choosing the same virtual hardware specs. qemu-kvm command: /usr/libexec/qemu-kvm -version QEMU PC emulator version 0.12.1 (qemu-kvm-0.12.1.2-2.506.el6_10.1), Copyright (c) 2003-2008 Fabrice Bellard ........

The key thing is that you must use a "machine"id of "pc-1.3" or it will say your hardware is not supported. Additionally you MUST use a virtio disk or you will get a ks_pre.sh error as soon as the install starts (a look at logs will show it can't find a disk). This is funny because even though the OS finds the disk and an fdisk -l shows it, it looks like the script looks for a /dev/vda device (virtio) and nothing else, so if you didn't use Virtio as you........

Idid a systemctl restart networking and it broke Proxmox VM connectivity! #proxmox is the problem after restarting the network the tap devices go to disabled state [2230884.919905] vmbr0: port 7(tap118i0) entered disabled state [2230884.948864] vmbr0: port 8(tap122i0) entered disabled state [2230884.972748] vmbr0: port 6(tap119i0) entered disabled state [2230885.004745] vmbr0: port 5(tap117i0) entered disabled state [2230885.03673........

I tried to stop a qemu-img copy or clone and it broke everything. It was fine to "stop" it from the GUI but a process still persisted so I killed the relevant qemu-img and the kernel went crazy. It also may not have helped that I tried to lvremove a different volume (an unused disk). But either way it breaks LVM (you cannot even run lvdisplay) so a reboot is necessary. Jan 17 06:45:21 testserver kernel: [ 5680.439337] systemd-udevd D 0&nbs........

If Proxmox won't start a VM with an error like this: trying to acquire lock... TASK ERROR: can't lock file '/var/lock/qemu-server/lock-102.conf' - got timeout rm /var/lock/qemu-server/lock-102.conf Then try to restart the VM and it should be good. What we did above was find the lock file that is named lock-VMID (in our case 102) and deleted it to release the lock.........

Proxmox at the root of your storage creates and "images"and "templates/iso" folder for VM images and iso's respectively. It ignores files in any other location.........

Error 0 occurred while receiving the document root@vh1:/var/tmp# wget http://mirror.compevo.com/proxmox/proxmox-ve_5.2-1.iso --2018-08-30 16:27:37-- http://mirror.compevo.com/proxmox/proxmox-ve_5.2-1.iso Resolving mirror.compevo.com (mirror.compevo.com)... 103.25.61.44 Connecting to mirror.compevo.com (mirror.compevo.com)|103.25.61.44|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 641517568 (612M) [application/o........

Proxmox has made this free utility to backup running OpenVZ containers. It's a great program which is actually just a PERL script but gets the job done. This program is not 100% required because all it really does is cp -a from your container's path as far as I know but it is still good to have uniformity to how you backup your containers. For RPM distros such as Centos/RHEL/Fedora etc.. download and install this: wget http://www.proxmox.com/cms_proxm........