Search results

I have a node with an external JBOD enclosure connected through two SAS cables. There are ~80 disks in the enclosure, so they show up as ~160 disks on PVE. When opening the "disks" page for this node, the request to /api2/json/nodes/<node_name>/disks/list?include-partitions=1 times out after 30...

GCP has this functionality. I found this thread trying to find a way to do the same thing in proxmox. 2022 is almost over, so here's the obligatory annual request for this feature... For example, if you want your VMs to automatically mount a disk in, say, /var/log and another in...

We did a lot of tests with various parameters in corosync.conf to stabilize the cluster. We eventually got to a point where a 52 node cluster would run without crashing for a couple of days. A 50 node cluster would run for much longer, as long as we're not actively making a lot of changes to...

I'm trying to add support for NixOS LXCs to proxmox. So far I've made a patch for pve-container that adds support for detecting NixOS LXCs, and writing host-managed configs to the container, that will then get applied by a service running inside the container...

That would be very useful. Although it wouldn't solve the issue of shared storage. Since each cluster expects guest IDs to be unique, using the same shared storage across multiple clusters would be impossible.

We've spent the past 6 months trying to make a 50 node PVE cluster stable. While we managed to identify and report multiple issues with corosync that cause instabilities, at this point it is still far from stable. The issue isn't just keeping the corosync cluster alive. Whenever Corosync has one...

Can you share this error message? As for reinstalling proxmox, unless you took backups of the VMs, simply preserving the VM storage won't help. You will still lose the configs for the VMs, so proxmox won't recognize them.

Required changes look simple enough. From 44e7d5709d1ea1ae0040af1132af8e321019d25a Mon Sep 17 00:00:00 2001 From: "harikrishnan.r" <harikrishnan.r@media.net> Date: Thu, 13 Aug 2020 17:20:50 +0530 Subject: [PATCH container] lxc: Close #2938: increase upper limit of LXC core count to 512...

back when I had this issue, I had a 60-second window between node startup (and becoming reachable over the network) and the VM autostart which would cause the node to go unresponsive. I don't remember if this is because I specified an autostart delay. I wrote a shell script to ssh and disable...

The issue is likely not the GPU itself. The address that the GPU formerly used might now be used by something else (The SATA controller, USB controllers, Audio device). that other device might crash your system when attempting a reset for passthrough. Just to confirm, is this VM set to...

We recently got some shiny new 7h12 dual-socket servers. Most of those cores need to go to a large container running YARN, and the rest go to smaller containers running other services. The limit is not just for the GUI, some PCT commands fail without increasing the limit on LXC/Config.pm...

Do you have any VMs with PCIe passthrough? Are they set to autostart on boot? IOMMU groupings and PCIe addresses would have changed when you changed the motherboard. I had a similar issue post a bios update, where a VM would try to reset the wrong PCIe device after a BIOS update. making the...

There appears to be a cap of 128 cores for LXCs in proxmox. I can manually edit the confs, but not having that restriction on the web interface would be nice. Given the way AMD is going, this cap ought to be raised. I tried modifying the hardcoded limit (and restarting pveproxy/pvedaemon), but...

Did you add args: -cpu host,kvm=off,hv_vendor_id=AMD in your VM config?

Wrote a file to s_logs, deleted it, ran trim, and it did nothing. # pv --rate --bytes /dev/zero | dd of=/s_logs/zeros ^C96MiB [68.3MiB/s] 1681507+0 records in 1681507+0 records out 860931584 bytes (861 MB, 821 MiB) copied, 14.4602 s, 59.5 MB/s # fstrim -v / ; fstrim -v /s_logs /: 400.7 MiB...

I have a few VM and contianer disks on a thinpool. One of the VMs has two disks, 128 and 256 GBs in size. # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 128G 0 disk `-sda1 8:1 0 18.6G 0 part |-turnkey-root 254:0 0 17G 0...

Restarting pvestatd worked. Thanks!

Hi. I applied this patch on one server. pvestatd still throws the same error Nov 13 13:02:05 hostname pvestatd[3727]: Use of uninitialized value $avail in int at /usr/share/perl5/PVE/Storage.pm line 1057. Nov 13 13:02:05 hostname pvestatd[3727]: Use of uninitialized value $used in int at...

Ah, bad regex for scientific notation. It should be: use strict; use warnings; use Filesys::Df; use Data::Dumper; use PVE::Tools; my $df = PVE::Tools::run_fork(sub { return Filesys::Df::df("/mnt/pve/hdfs",1); }); for my $v (qw(blocks used bavail)) { if (defined($df->{$v})) {...

# perl -T test.pl blocks unknown: 2.16972088416666e+15 used unknown: 1.90906153251635e+15 bavail only numbers: 260659351650304