Imho it's a bad idea to have your backups inside your prouction environment. Imagine something bad happens ( hardware error, ransomware) you will need your cluster to restore your cluster. Even worse: If some bad actor manages to take over your...
I checked the code in pve-sdn-commit and IPRoute2.pm.
bridge_is_vlan_aware() only considers interfaces with linkinfo.info_kind == "bridge". Since OVS bridges use "openvswitch"instead, they appear to be treated as non-vlan-aware by the current...
hi @philkunz
Thanks for the quick update and code fix release, but I still can't get to code.foss.global (chrome error: ERR_CONNECTION_CLOSED) , same for community.foss.global. Regards, Damien
Been running 8.4 for a while now, single-node homelab, nothing critical. Just a few VMs for self-hosted stuff and some LXC containers.
System's been rock solid so I haven't felt the need to touch it. You know how it is — if it ain't broke.
Not...
I actually used AI to do some research and found the underlying issue:
After investigation, this is not a cfs-lock or quorum problem (the cluster is quorate and pmxcfs is healthy throughout). The real chain is:
The VM being removed lives on a...
Since the slab size is 4 KB, Windows appears to stop defragmenting the slabs.
It does indeed seem to be 4 KB.
Optimize-Volume -DriveLetter C -SlabConsolidate -WhatIf -Verbose
I think it’s always been that way…
As far as I recall, if the size...
The more generic way e.g. used by the Debian installer is cryptsetup +LUKS
( e.g. you can follow https://reintech.io/blog/configuring-luks-encrypted-disk-debian-12 )
I would not recommend to use encryption within the VMs, you will need to handle...
After execution
Optimize-Volume -DriveLetter S - Retrim -Verbose
error:
Neither slab consolidation nor slab analysis can run if slabs less than 8 MB
in eventvwr:
Slab size too small 0x89000002D
Disk Optimizer shows "Thin Provisioned disk" and...
UPDATE
I found the solution to my problem:
it was the keyname I used, the wrong value for the zone field and the API
for some reason, the knot plugin type does not work, but the generic "nsupdate (RFC 2136)" does
So what made it all work...
Changing the domain (lan) works fine. Changing the node/host name (pve01) is more problematic (see threads on this forum about problems with renaming).
The tar: Cannot mkdir: No space left on device error during a Proxmox LXC restore means the newly allocated root disk size is smaller than the uncompressed data inside your backup file. This commonly happens if the container originally used ZFS...
Forgot to say...
Upgrading to 6.17.13-11 also completely solved the high iodelay problem when io-thread is active on a VM. Posting this in case it's useful for someone suffering from the same issue.
I have updates on my installation stability. With the upgrade to pve-qemu-kvm 11.0 from 10.2.1, proxmox 8 kernel (6.8.12) was having trouble with i/o threading.
Suddenly every vm was queueing I/o, to the point that global iodelay was greater...
I am using ZFS exclusively, so I can not (and should not) say much about the other storage solutions.
Encrypting a disk from the inside of a VM? Sounds wrong to me as it adds additional attack vectors and key management problems. From my...
This is a problematic area. While there are theoretically multiple mechanism to implement it, the only reference I know of is: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#zfs_encryption
I've also done a test using two Talos nodes with E1000 adapters and apparently that works too!
EDIT: there’s a bug registered: https://bugzilla.proxmox.com/show_bug.cgi?id=7627