Search results

Thanks for info. Ive do loops for my customer and do something nasty :) For example one customer ESTIMATED DISK USAGE OCCUPIED ON PROXMOX-BACKUP (number of chunks * 4MB) FOR NAMESPACE customer1 customer1 / customer1-hw1 692.465 GB ----------- TOTAL: ---------- 692.465 GB But du of all these...

Doesnt work on nested namespaces as described here https://forum.proxmox.com/threads/how-to-sum-up-all-occupied-space-by-backups-from-namespaces.154202/#post-702157 /mnt/datastore/internal/ └── ns ├── customer1 │ └── ns │ ├── customer1-hw1 │ ├── customer1-hw2 │...

Ive faced for problems with this mobo - but with nvme - after grub boot ive got one nvme down and message to set latency in dmesg. Probably something with ASPM. Try a shot with these kernel params. Probably not helps, but ¯\_(ツ)_/¯ pcie_port_pm=off pcie_aspm.policy=performance...

Hi, i have structure of pbs - see below. I want to know how much space ocuppied customer1,2,3 etc... by their namespaces because we group their machines there. Is my code correct or just something missing ? root@proxmox-backup:/mnt/datastore/internal/ns/customer1/ns# find -type f -name...

Is there any way how to debug that ? Because if server reboots, nothing in syslog, kern.log even ipmi ? Is this PVE kernel problem or somethin else ? Any ideas ?

Probably yes, now the server has uptime over 40weeks Try this GRUB_CMDLINE_LINUX_DEFAULT="quiet pci=assign-busses apicmaintimer idle=poll reboot=cold,hard" and update grub

Not same CPU, but latest BIOS probably fixed the issues https://www.asrockrack.com/general/productdetail.asp?Model=1U4LW-X570/2L2T#Download 1.70 11/21/2022 BIOS Instant Flash 18.33MB 1.Update ComboAm4 V2 AGESA PI to 1.2.0.7 2.Support AMD Ryzen 7 5800X3D CPU. 3.Support Re-size BAR

Tried update to pve kernel 6.2 and added parameter iommu=pt BOOT_IMAGE=/boot/vmlinuz-6.2.16-11-bpo11-pve root=UUID=2881c2c3-7f65-4453-b3ea-164947b03dd9 ro quiet iommu=pt Now all 4 devices are in same group 17 Is there a way how to merge them in proxmox or VM into one ?

Hi, im facing problem that installed GPU card nvidia A16 is divided into 4x GPUs instead of 1. Is there a way how to merge it and connect to VM as one device ? There are 2x GPU ( A10 ) thats acts like 1GPU and works like charm in VM. root@proxmox:~# lshw -short -c display H/W path...

This is nasty and really works :D

Did you fixed it when you added 1024MiB to actual setup ? for example 64GiB => 65GiB ?

Yes, i tried echo "options vhost max_mem_regions=512" > /etc/modprobe.d/vhost.conf rmmod vhost_net rmmod vhost modprobe vhost_net cat /sys/module/vhost/parameters/max_mem_regions # 512

YES root@proxmox1:~# cat /etc/modprobe.d/modprobe.conf options vhost max_mem_regions=128

Still have issues pve-manager/8.0.4/d258a813cfa6b390 (running kernel: 6.2.16-19-pve) Testing vps config agent: 1 boot: order=ide2 cores: 128 cpu: x86-64-v2-AES hotplug: disk,network,usb,memory,cpu ide2: none,media=cdrom memory: 61440 meta: creation-qemu=8.0.2,ctime=1698709821 name: bla numa: 1...

Meh, bad distro in apt file

Hi ! I have fresh debian 11 installed and dist upgraded to deb12. After that im not able to install proxmox8, there are not met dependecies here is apt file im using deb [arch=amd64 signed-by=/etc/apt/trusted.gpg.d/proxmox-release-bullseye.gpg] http://download.proxmox.com/debian/pve bullseye...

Shame on me ! It works flawlessly.

Another "bug" with ipmi https://github.com/ipmitool/ipmitool/issues/377 but everything seems fine - juts only IANA message to stderr can be "workarounded by" ipmitool lan print 2>/dev/null root@freetest-pve8:~# ipmitool lan print IANA PEN registry open failed: No such file or directory Set in...

I have this MoBo - X570D4U-2L2T https://www.asrockrack.com/general/productdetail.asp?Model=X570D4U-2L2T#Specifications in server. Tried to do memtest - OK Smart of disks + nvme looks fine Tried to switch into new hw to same server type and Reboots doing ocassionally ~3mo 2022-12-08 09:40:25...

Probably this thread related. https://forum.proxmox.com/threads/detected-hardware-unit-hang.127991/ Still not fixed there, but recommend to update intel fw