Search results

I"m also seeing the balooning error since updating for VMs... pvestatd[2339]: VM 200 qmp command failed - VM 200 qmp command 'balloon' failed - Invalid parameter type for 'value', expected: integer pvestatd[2339]: VM 200 qmp command 'balloon' failed - Invalid parameter type for 'value'...

Just trying to find out if this is an error that needs to be fixed? pct fsck 104 fsck from util-linux 2.33.1 fsck.ext2: Unable to resolve 'rbd:test/vm-104-disk-0:conf=/etc/pve/ceph.conf:id=admin:keyring=/etc/pve/priv/ceph/test.keyring' command 'fsck -a -l...

After Updating my 4 node cluster today, I can no longer start any of my CTs. Corosync Cluster and Ceph show as healthy. I created a new Unpriviledged CT after the updates and it works fine I hope there's a way to fix this and not have to rebuild this cluster... I get an error when running...

One of my nodes starting doing the same as 'proxtext' after updating the node today. Any word on this issue?

Thanks Alwin for your reply... :)

This is the method I've been using for a while :) Convert to unprivileged CT for more security 1. Console at container cd # (if not at root directory) rm /var/spool/postfix/dev/random rm /var/spool/postfix/dev/urandom touch /var/spool/postfix/dev/random touch /var/spool/postfix/dev/urandom 2...

There is a person on you tube that has made a few nice tutorials about ProxMox Ceph setup. The latest video for ProxMox 6 and Ceph Nautilus is: https://www.youtube.com/watch?v=GgliWaOfvsA The ProxMox 5.1 Ceph Luminous tutorial recommended separate pools for VMs and CTs, the current tutorial for...

I'm using this supermicro server for distributed computing with several global projects. there's 10 different types of applications running, but the LXCs are all based on Ubuntu Server 18.04. https://www.supermicro.com/en/products/chassis/2u/825/SC825TQ-R740LPB

My single server running over 100 LXCs as an example, LAN network is all 10G...

any updates for ProxMox 6?

Thanks for the info, I am currently upgrading switches supporting cluster to M4300 series...

Yes, tried cable swap and different ports. Trying a LACP Layer 3+4 capable switch next. Have seen several articles eluding to STP Layer 2 issues with supermicro X710 NICs that could possibly be fixed with the latest Intel firmware that Supermicro hasn't approved and released yet. I also...

cat /etc/network/interfaces auto lo iface lo inet loopback iface eno1 inet manual auto ens1f0 iface ens1f0 inet static address 10.10.1.40 netmask 255.255.255.0 #Prox-Cluster-R0 auto ens1f1 iface ens1f1 inet static address 10.10.2.40 netmask 255.255.255.0...

ProxMox Network Config, exact same on all 4 nodes except for IPs of course.

Seeing the following errors on Proxmox Node Terminal screen: ens1f2 and ens1f3 are LACP bonded with Layer 2 Hash policy, using XS728T smart switch. ethtool -i bond0 driver: bonding version: 3.7.1 firmware-version: 2 expansion-rom-version: bus-info: supports-statistics: no...