Search results

[Not a hijack, just wanted to thank @t.lamprecht for this valuable info] I found this post after thinking this fresh PVE install I did was broken. I <3 the idea of an efficient unified index of of events rather than the age-old practice of storing massive amounts of free-form text to wade...

Just to be clear, the snapshot taken prior to initiating a move of a detached VD does not contain the detached VD entries. Once the move completes, the move operation goes and updates only the primary section of the VM, regardless, which it would still do after the move completes, even if the VD...

The move will either succeed, or not succeed, depending on the move results, and the move process will either update the config if the move succeeds, or not, if it fails. In neither case does the result affect any active state of the VM (or CT for that matter) nor the activity of it's attached...

I am testing a production workflow we are attempting to build using PVE and am a bit confused... Part of the workflow is to take advantage of PVE to manage migration of virtual disks between storage tiers. However, it appears our workflow is dead in the water because PVE will not allow us to...

Came here searching for same... glad a fix is imminent -=dave

I'm here literally because I have given up on PBS. The Push datastore sync feature is apparently not quite as solid as I'd have hoped, as my local Debian/PBS LXC (installed 2022, upgraded continually to current Deb12/PBS 3.3.2) which has nearly 3yrs of backups over 5TB on it, all the while with...

For live VMs/LXCs, that's not possible, but it should definitely be an option for offline CTs/VMs. I have a separate volume for each docker image that I'm running within a single LXC and currently have to manually take a zfs snapshot of the specific docker image's virtual disk volume prior to...

Added my $0.02 on the ticket too. Bummer.

I think it's clear what we are looking for. How would we as a community effectively communicate this desire to the Proxmox team? Nodes have very specific changes from base installation for many HW configs so rather than having to continually update/test an Ansible playbook, a simple...

Ah, that’s a great test feature I haven’t seen before (and searching seems to back up that it’s not super common knowledge). Thanks. When I was testing HW NVMe RAID0 on a single-cpu Bronze X11 system, we had to drop a second cpu in just to saturate the card (9460-16i) with 12x P4500 4TB on the...

It's a wonder what either of you is talking about, because the ARC is integral to ZFS and cannot be "removed", only adjusted in size.

Can you please explain how the change helps to make Proxmox not run the processor at max frequency ? @spirit stated the change is to "force max frequencies" (which is exactly opposite of what this thread is about).

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...