a simple 3 node, 2 x86 (alderlake n100 and n305) and 1 arm64 (amlogic s905x3), earlier i had just the 2 nodes + qdevice for qorum now deprecated the qdevice and added the third node, works great so far i've rebuild the arm kernel adding also zfs...
VMware hasn't exposed VT-x/EPT to the Proxmox VM. Proxmox's boot process is failing to get hardware accelerated CPU access.
- Enable "Virtualize Intel VT-x/EPT or AMD-V/RVI" or "Expose hardware assisted virtualization to the guest OS" on the...
The deduplication will continue to work in any case since it's cross-namespaces as long as you have them all on the same datastore. To get the backup snapshots to another namespace I would use a sync-job, for moving retention rules you will...
Here’s another problem we hit bringing PVE arm64 up on the GX10. The first was the black screen after initrd (thread here). Posting this one since the symptom is a show stopper.
Hardware
ASUS Ascent GX10
NVIDIA GB10, 20 cores, 3.9 GHz
128 GB...
So this 192.168.255.16 is a pve node nfs client. I assume you have 1 switch or 2 ?
On switch I would first just cross-exchange the used cable port plugin's from pve-cluster1-node1 and pve-cluster1-node2 so your problem should be seen on nfs...
To be honest the only thing which wonders me is, why some people have downplayed the issue when many others showed enough evidence. And that includes also Proxmox stuff. If you do not know what I mean, read the whole thread.
Reg key works fine :-) ( yellow area) , tested to remove it as well and cpu usage went high again, no change when setting cpu to Host ( pink area)
Down from 3.5% -> under 1% on fresh install .
Sure but I think we can agree, that the situation get's much worse (due to a larger scale) as soon as script kiddies gets envolved ;) And at least that impact would be avoided by actually not running EOL systems and not exposing hypervisors to...
Purely theoretically, we don't know how long this bug has been exploited since it was possible to do anything, including clearing logs. Only now have script kiddies gotten their hands on it.
Here’s another problem we hit bringing PVE arm64 up on the GX10. The first was the black screen after initrd (thread here). Posting this one since the symptom is a show stopper.
Hardware
ASUS Ascent GX10
NVIDIA GB10, 20 cores, 3.9 GHz
128 GB...
I'm looking at moving our backup targets around on PBS to make better use of namespace specific pruning jobs, and I'm curious before I make any changes if there's a best practice for moving the files so that when the backup jobs are retargetted...
In my case, setting up AppArmor inside containers helped.
pct enter <id>
echo "/run/systemd/journal/dev-log rw," >> /etc/apparmor.d/local/usr.sbin.rsyslogd
apparmor_parser -r /etc/apparmor.d/usr.sbin.rsyslogd
reboot
This is probably what fiona...
Thanks for the feedback. bpftrace would not work on 6.17 as possible_nx_huge_pages structure is different. On 6.19+ it's an array of per-MMU-type structs. On 6.17 its a list of pointers.
Interesting that you are seeing the thread spikes on...