Search results

I have a proxmox 6.4 and it does not show names of vm's. But they are all up and running. Here is a screenshoot. How can I fix this?

My oracle linux 8 uses XFS and I have only one ZFS disk. And I checked it again, as soon as I move the oracle disk to ZFS io-delay goes up to 80%. NFS and local dir do not show this behavior.

There is nothing fancy. The VM writes every 1-2 seconds about 10-20k. May be there are some ZFS parameters to set.

I run a proxmox 7 server with a ZFS storage. I recently installed oracle linux as a VM on it and since then I have problems with io-delay. As soon as I start this VM io-delay goes up to 80-90%. The server is neatly slow. I moved the disk to another storage (NFS) and io-delay went down to 1%...

In the meantime I created a little bash script <kill-vm> #!/bin/bash # if [ $# -lt 1 ] ; then echo "Usage: kill-vm <vmid>" exit fi VMID=${1} EXIST=`qm list | awk '{print $1}' | grep -c ${VMID}$` if [ ${EXIST} -eq 1 ]; then PID=`ps waux | grep "/usr/bin/kvm" | grep "id ${VMID}" | awk...

I tried both options. But mostly I want to enable it.

You can use haproxy with a frontend IP and redirect in backend to all your nodes in cluster. For detailed information read haproxy doku. http://www.haproxy.org/

After fresh installation of a VM where it does not have installed qemu-guest-agent it is mostly not possible to shutdown or stop the vm from outside the VM. What is the recommended action for this situation? Thanks

Oh sorry, I use it as a proxmox storage, where VM's have their "harddisk". Thank you for the hint.

I could not find where to increase increase timeout, or hard mount. Where does this configuration happen?

Hi, I run a Proxmox Cluster with 3 nodes and a Pacemaker Cluster with NFS on 2 nodes. I use the NFS Cluster as a HA storage. All that worked fine for a while. I could switch from NFS node1 to node2 without problems. Running VM's on Proxmox did not recocnize the change. But since 2 or 3...

The mainboard is a supermicro 2 years old with latest firmware. The default password was changed but may be was brute force hacked. Fortunately we do have a full backup and do not need to pay ransom of 0.4 BTC. In the future we wont expose IPMI to the internet any more.

Jungle_Sec They want 0.4 Bitcoin to

I discovered a file-encrypting Trojan that encrypted a hole proxmox 6.4 server. I have no idea how this can happen since nobody does ever physical work on the proxmox console.

Ok I messed it up. Anyway after I installed the new Backup Server 2.04 it's working again now.

I just installed another new backup server 2.x and there you also find the pve-no-subscribtion with buster entry. I think the update as described here (https://pbs.proxmox.com/wiki/index.php/Upgrade_from_1.1_to_2.x) does not work. I am going to do a fresh install now.

Just a backup server I did not change /etc/apt/sources.list.d/pve-no-subscription.list There was still buster.

==> /etc/apt/sources.list <== deb http://ftp.at.debian.org/debian bullseye main contrib deb http://ftp.at.debian.org/debian bullseye-updates main contrib # security updates deb http://security.debian.org bullseye-security main contrib ==> /etc/apt/sources.list.d/pbs-enterprise.list <== deb...

This solved it: cd /usr/lib/x86_64-linux-gnu/ ln -s libsgutils2-1.45.so.2.0.0 libsgutils2.so.2

What is this lib (libsgutils2.so.2) good for? Oct 27 15:23:47 pbs systemd[1]: Starting Proxmox Backup API Server... Oct 27 15:23:47 pbs rpc.mountd[949]: Version 1.3.3 starting Oct 27 15:23:47 pbs proxmox-backup-api[948]: /usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-api: error while...