Search results

Why are clones not supported when using `ZFS over iSCSI`? Refer to table in: https://pve.proxmox.com/wiki/Storage:_ZFS_over_ISCSI In contrast, NFS has support for clones via qcow2. https://pve.proxmox.com/wiki/Storage:_NFS

@hariharan go vote on https://forums.truenas.com/t/add-lio-or-iet-iscsi-target-compatibility-to-scale-so-proxmox-zfs-over-iscsi-can-work-natively/25374 asking they implement native proxmox support.

I'm seeing a ghost "eth0" interface spamming my console logs on proxmox latest. Not sure if this issue is caused by a BIOS firmware update I carried out on this new device (Minisforum MS-01)... hopefully someone can help? eth0 doesn't exist on my system as you can see below. I'm not sure what I...

Hello from the future! 2024... did you ever get around to posting and sharing your findings?

Looking for some guidance, on a fresh install when adding the new node to the cluster there is a "Link" selection box, in which configuration file is this setting stored and how do I change it? For context: - I would like to setup my cluster node using the native RJ45 NIC initially. Then...

I'm facing the same issue as this post. I was able to replicate it on multiple linux live CDs... filed a bug: https://bugzilla.proxmox.com/show_bug.cgi?id=5606

hello from the future... 2024... curious on how your proxmox btrfs journey has gone? I know proxmox has nifty backup capabilities zfssend/receiv and configuration of this with any other proxmox cluster member... hopefully that comes to btrfs as well soon. How has your performance been running...

I don't know how I ended up with the Qdevice having four votes. Where do I change that? The Qdevice is indeed not pingable from the `NV` node... all other nodes it pings. Will check my firewall (the Qdevice is an Azure VM in the cloud) corosync.conf root@pvecm-unraid:~# cat...

"NV" looks not normal in my cluster status. According to https://pve.proxmox.com/pve-docs/pvecm.1.html "NV" means # pvecm status Cluster information ------------------- Name: HOMELAB Config Version: 16 Transport: knet Secure auth: on Quorum information...

Power efficient performance is a big thing nowadays, ARM chips beat x86 in this race. There have been multiple discussions in these forums asking for ARM/AARCH64 support officially. Any recent word on this from Proxmox leadership? For context; a major windows laptop on ARM will soon be...

I'm seeing some kernel crashes with igc (intel nic driver) on the current kernel. How often is a new kernel version released? If this kernel is based off ubuntu; where can I check what version ubuntu is on? my latest crash https://pastebin.com/X1X3gbwf

anyone find a solution other than editing every single container and restarting it with that option? It feels like there must be something on the OS wide level that could be changed to avoid this hassle.

thank you! TL;DR add to 101.conf of the lxc container. I hope this feature makes it to web GUI soon.

Hi, I found the "CPU affinity" (cpu pinning) setting for VMs inside hardware panel in proxmox but I am unable to find this setting for LXC containers. How can I pin a specific LXC container to specific CPU cores in PVE 7.3.3?

Were you able to fix this? I'm seeing these "Memory cgroup out of memory" for Plex LXC container.

I am wondering if you ever figured this out? As I am seeing something similar as I implement NFS on my network.

Just to make sure I understand, there is a different RPC made by pvestatd that is waiting for response that is timing out after 10 seconds causing the `pvestatd` message in syslog? OK my script returned an instance timestamp for me to try to correlate. Run 234 + Thu 24 Nov 2022 03:33:03 AM...

thank you for help confirming :) I'll try CPU affinity settings to "12,13,14,15" and watch htop on proxmox to see if only those cores are maxed out and keep an eye on power consumption too

thanks for the pointer. I exclusively use NFS version 4.2 - taking a hint from the script you shared I wrote an endless loop script. #!/bin/bash # Basic script to run on an endless loop on a NFS client # idea is to catch failure in rpcinfo and log timestamp. counter=1 while : do echo "Run...

I'm trying to debug a condition where it seems that using NFS v4.2 there is a brief period of connection timeout between proxmox and my NFS server. Looks like `pvestatd` monitors storage mounts and prints some useful messages - can these be made more verbose? Nov 23 15:43:16 centrix...