Applying the update available for Test on 2026/02/18 will resolve the issue.
Previously, HDMI Audio was not recognized, but applying the update without changing any settings resolved the issue.
I tried playing the video and confirmed that sound...
Applying the update available for Test on 2026/02/18 will resolve the issue.
HDMI Audio was unavailable on N100 Windows 11, but applying the update confirmed improvement.
* Linux has not been tested, but it should be fixed.
Hey! Thanks for the reply.
I wanted to learn clustering if I don’t build a server. That’s one reason.
I want plenty of resources to tackle whatever projects I may have in the future. I was looking at dual epic 7532 processors. 32 core each...
In case someone in the future has the same problem with an osd being to full to boot, I was able to recover the data by copying the underlying disk to a bigger disk.
dd if=source/drive of=dest/drive bs=32M status=progress
reboot the node with...
Moving it between local storage unfortunately doesn't work due to these servers having a single drive available (hardware raid from repurposed vmware hardware)
The latter section is correct, each node in the cluster is using their own local...
Hey everyone!
Long story short...
Dell R710 with:
- ssd 1tb for boot and images
-4 x4tb nas drives
Running proxmox 7.x and have a linux ubuntu vm with all my services as well as a zfs raid for the 4 disks.
As you see...everything is getting...
Moving a disc from one storage to another should always work, for this you will need to have both storages.
Let's assume you have two discs (sda and sdb), your vms data lives on sda. Then you should be able to create a lvm/thin-pool on sdb and...
As long as your PVE box sees the drives (eg, /dev/sdb and /dev/sdc) you can do whatever you want insofar as deployment.
You can make them individual VGs, or Single VG on both, or as a zpool, btrfs mirror, or passthrough to guest if you really...
These are, generically, compliance standards to which you adhere and then engage a relevant external firm to audit your compliance. There's no reason Proxmox could not be made compliant with any of the prevailing standards in USA or elsewhere...
I'm afraid I give up ;-(.
On Saturday I asked you:
1) Just in case, execute in the PVE hosts: [ hosts in PLURAL form]
grep -rF 192.168. /etc
and search for any leftovers of the old addressing.
But you showed the result only from ONE...
just to add: if i run the backup manually via datacenter > host > vm > backup with the same parameters it works just fine as well (the vm also restarted immediately again).
all subsequent runs after the first manual backup also succeed now...
I recently determined that I should be using LVM-Thin instead of LVM for my cluster environment.
As such, I would like to drain and swap the datastores over to be LVM-Thin.
That said, I have some VM's that need minimal downtime. Is it possible...