Recent content by nhand42

Google suggested this polling error might be due to the netconsole service. As an experiment I've disabled netconsole and rebooted. After the reboot the containers have all started correctly. Your intuition it was a timing error seems correct. I suspect a race between netconsole and...

I've been looking through logs and might have found something useful. After a reboot the dmesg shows eth0 and eth1 being renamed at T+3, vmbr0 being created and entering forwarding state at T+19, then three containers trying to start from T+37 but all three failling. After the reboot the fault...

I do not want a bond. This worked on PVE8 and it is a regression in PVE9. If you have nothing of value to contribute please refrain from commenting.

This has worked fine for several years. I use a bridge so I don't have to remember which port is which on the back. I plug a single cable into any port and then use vmbr0. I already said this worked on PVE8 and works on PVE9 after ifdown/ifup and I also pointed out eno2 being down is normal...

The PCT containers do start after "ifdown vmbr0; ifup vmbr0". However this workaround is not persistent across reboots. I would not think the PCT configuration is changed by "ifdown vmbr0; ifup vmbr0" on the proxmox host.

I upgraded from PVE8 to PVE9 and everything went smoothly. However afterwards all the PCT were in the stopped state. Manually starting PCT shows the error # pct start 100 run_buffer: 571 Script exited with status 2 lxc_create_network_priv: 3466 Success - Failed to create network device...

This issue has been solved. This thread is for anybody having slow I/O performance and searching for keywords. The cause might be ZFS trimming the rpool. I’m running proxmox version 7.3-1 on a Supermicro A2SDi-8C+-HLN4F with HP SSD EX920 1TB for the rpool. My proxmox node was unresponsive. VMs...

Same issue here with a Debian container. I could reliably get I/O errors when building a development project inside the container. This caused the root partition to remount read-only. Was also using virtio block over ZFS storage. Upgraded the pve-qemu-kvm_6.1.0-3 package linked by Tom and the...

This has been solved - this thread is for anybody else who has the same problem and is searching for keywords. An upgrade to Proxmox 7.0 has tanked the performance of virtualized pfSense 2.5.2. Pre-upgrade a download of 100Mbps used about 20% VCPU and now can't reach that bandwidth even 50Mbps...

Recurring theme. Thanks for the workaround.

Could be memory fragmentation. KVM needs a contiguous piece of memory. If it's fragmented then you'll need to defrag. You could try "sysctl vm.compact_memory=1".

Unfortunately my cluster has failed again even with pve2-test1. The cluster split into two subsets this time. First subset, two nodes. root@hera:~# pvecm status Quorum information ------------------ Date: Wed Aug 7 00:49:29 2019 Quorum provider: corosync_votequorum Nodes...

I'm also seeing a much more stable PVE cluster with http://download.proxmox.com/temp/libknet1_1.10-pve2~test1_amd64.deb installed. I've got a 5 node cluster in a single VLAN and corosync was frequently "splitting" into subsets of nodes, e.g. root@maia# pvecm status Quorum information...

Yes, you can do this. I have VM and container images on Ceph RBD and shared network filesystems on CephFS. Here's how I configured mine: enabled metadata servers on three nodes created new pools "fs_data" on HDD (2-repl) and "fs_meta" on SSD (3-repl) created new cephfs using the two pools...