Search results

This is the default behavior in Proxmox and this thread is about disabling this behavior so I'm not sure how your comment adds to the discussion at all. Am I missing something ?

I find this ghost lock happens most often because of stale devicemapper handles. Not sure why it happens but it only seems to ever happen with Proxmox, so I suspect some cleanup from GUI operations not happening when it should. If you get this error, check the device mapper table for ghost...

I doubt there is anyway to “force” the p_state driver if the default kernel doesn’t enable it directly. I can’t seem to get it enabled on my old T110 ii with “supported” E31230 Sandybridge. I suspect it is due to the ancient Dell firmware not fully supporting them, even though the proc does.

From reviewing the docker ZFS driver detail documentation (https://docs.docker.com/storage/storagedriver/zfs-driver/) it seemed clear from the error that docker was not using the ZFS driver for /var/lib/docker when being nested on a ZFS-backed LXC as it should be. As a work around we force...

Just found same... So sad... okay, back to the dark ages of LVM from ZFS *sigh* -=dave

If by "let the CPU do the rest" you mean, let the CPU do nothing but run at it's lowest supported frequency, sure, but you're neutering performance, especially if you have a higher-end CPU that supports large CPU scaling factors...

Update: In addition to procedure to disable IPV6 on host, any LXC containers set to use DHCP for IPV6 on their network interface must be changed to STATIC and CIDR of default "NONE", else the LXC will continue to use IPV6. This seems like a bug to me, since there is no IPV6 DHCP server to...

FYI: Unfortunately, disabling via the proscribed method doesn't disable it in LXC containers that existed prior to when ipv6 was disabled via sysctl on the proxmox host... -Proxmox host set to static IPV4 address via netplan -Moved Proxmox host from network that supported DHCP ipv6 to network...

A standard stand-alone computer. Your problem is either 1) issues with the OS configuration (which might be better served at a forum dedicated to the distro you're using, or 2) networking issues within Proxmox (which would be prime to ask about here). Assuming your issue isn't #1, first...

yes, it should work as if they are normal systems

Same problem on Dell R420 w/192GB RAM… so flakey

https://bugzilla.proxmox.com/show_bug.cgi?id=3493

New information: if you restart the LXC, the mounted file systems are once again inaccessible. Umount/mount once again restores access but "mount -o remount <mount path>" does not. Can anyone confirm this does not occur with 5.4 kernel ? I will have to forego wireguard functionality if I...

I've found what appears to be a bug on PVE 6.4. I am running 5.11 kernel but have not tested on 5.4 kernel. Linux richie 5.11.17-1-pve #1 SMP PVE 5.11.17-1~bpo10 (Wed, 12 May 2021 12:45:37 +0200) x86_64 GNU/Linux Containers that have a configured bind mount point will restore correctly, but...

for posterity, please remember to provide the solutions when you find them :) So what resolved the non-starting error ??? Jan 07 10:24:35 orion systemd-udevd[8273]: Could not generate persistent MAC address for fwbr100i0: No such file or directory Jan 07 10:24:36 orion systemd-udevd[8267]...

yes, worked like a charm - thanks for the effort !

Came here looking for the same. We have a production cluster of new efficienct lean machines, but our Proxmox Backup Server is running on quite old/inefficient repurposed hardware with 4x fully populated 16-bay JBOD SAS trays added running ZFS on PBS (these are also repurposed relatively small...

same here

same e1000e driver Fail++ Proxmox 6.3 with all latest non-enterprise updates as of 20dec22 Circa 2010 Dell Optiplex 960 generic box w/o any 3rd party HW additions other than HDs Dell BIOS A18 (2019 Spectre/Meltdown mc updates) Q9550 2.83Ghz Intel 82567LM-3 NIC chip Single VM consisting of...