Hi guys,
Here's a suggestion how to stop the spam logging and reduce the SNMP Daemon's logging level.
We can achieve this by adding the following line:
LogLevelMax=notice
to the /lib/systemd/system/snmpd.service file.
The entire file should then...
understandable, the only mitigation I can currently think of is by utilizing a hook script, but that won't catch every case in the guest lifecycle.
I'll look into creating patches that resolve this problem by making the guest wait for a firewall...
Doesn't boot either with EPYC-Rome-v4,-hypervisor where EPYC-Rome-v4 alone works.
Works with args: -cpu EPYC,-hypervisor
Waiting the next month if Microsoft fixes the fix, like the Stop Code UNSUPPORTED_PROCESSOR BSOD.
Just to report : even local restore is boosted.
PBS alongside PVE , Restore to Datacenter SATA SSD from Datacenter SATA SSD
170G used data of 400G virtual disk
Speeds are over SATA speeds because writing zeroes seems accounted/
PVE 8.4.0 restore...
no.
There is almost NEVER a use case for nested hypervisors except for development/lab use. Even if we assume there are no cpu/ram performance degradation that occurs with modern VT extensions (hint: there are) the consequences of cascading...
GC job must be set on each PBS.
Prune should be set on each PBS,
Snapshot sync deletions called "Remove vanished" isn't safe from my point of view.
See ...
I had exactly the same problem,
In Windows 11
The QEMU agent service in Windows was running
The qm agent <id> ping returned: QEMU guest agent is not running
After some checking, the issue happend to be that the PCI Simple Communications...
another way, with nowadays systemd versions, shipped with pve 9 , is to use MAC based altname,
like enx123456789012 where 123456789012 is the MAC address.
After looking into the device tree, I think the proper naming scheme should be as follows:
[root@pvez ~]# udevadm info -t | grep -E 'ID_NET_NAME_PATH='
│ ┆ E: ID_NET_NAME_PATH=wlp0s20f3
│ │ │ ┆ E: ID_NET_NAME_PATH=enp1s0 # eth1
│ │ │ ┆ E...
just to clarify, MDF files as SQL backups by PVE/PBS are valid, because rely on SQL VSS agent within Windows guest.
Only granular restore is missing. Full MDF need to be downloaded/restored, attached as temporary to recovery specific DB.
edit : myself test with a PBS v3. 2
grant user permission is required to allow API token Read Datastore for Sync job.
(perhaps fixed in newer version)
https://pbs.proxmox.com/docs/user-management.html#api-tokens
You should create seperate API tokens on PBS for every PVE server and give every API token only access to it's own namespace.
Set the permission for the API tokens to "Datastore Access" (hope that's the right one) for their respective namespace...