I have enabled email alerts for updates in Proxmox. However, the email arrives with current/new versions, but no changelog.
What are you doing to prioritize some updates over others? Is there a way to get the changelog added to the notification...
There is a wiki which covers storage: https://pve.proxmox.com/wiki/Storage
I've tried replicating your problem without success. The API and web show the same Storage, only difference being the API returns GiB/TiB and the web shows GB/TiB as...
I have enabled email alerts for updates in Proxmox. However, the email arrives with current/new versions, but no changelog.
What are you doing to prioritize some updates over others? Is there a way to get the changelog added to the notification...
ok, I see that now. Yes, I did assume this was working in PVE 8 due to no logged failures and successful test restore. I don't know how likely a successful backup/restore is for this guest without freeze.
I will pursue resolving the issue on the...
I suspect that the upgrade changed something about the smart monitoring to reset the tracked stats, or maybe to start tracking stats that weren't tracked before. This is probably why it jumped from 0 to 12 or 0 to 16, and it's likely that you...
I am trying to install the NVidia host grid drivers on 7.0.2-7-pve and I am getting this error:
fatal error: os-interface.h: No such file or directory
I have these installed:
proxmox-headers-6.17.13-12-pve
proxmox-headers-7.0.2-7-pve
What am...
Hi,
adding the abi version like suggested in the documentation works for me:
[I] root@pve9a1 ~# head /etc/apparmor.d/usr.sbin.ntpd
# vim:syntax=apparmor
#include <tunables/global>
abi <abi/3.0>,
/usr/sbin/ntpd flags=(attach_disconnected) {...
try this version, also you didn't say what versions did you tried
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.173-4/virtio-win-0.1.173.iso
Not the person you replied too but I tested and it didn't work with 10.2.1-2 but did with 10.1.2-7, I have a realtek nic though and my problem was internal dns didn't work in my k3s node.
Hi,
I might have missed something, but I don't see a smoking gun in the logs unfortunately. Could you also try kernel 6.17? That would already help determine when the regression was introduced.
Even better if you could test mainline kernel...
I would like to confirm that I am seeing what appears to be the same issue on my system.
Hardware:
Controller: Broadcom / LSI MegaRAID SAS-3 3008 [Fury]
PCI ID: 1000:005f
Subsystem: 1000:9341
The controller is currently configured in JBOD mode...
When rolling back a VM snapshot that includes RAM/state, the guest resumes with the old in-guest clock from the snapshot time.
This is problematic for AD/Kerberos, databases, logs, monitoring, certificates, clusters, scheduled jobs, and any...
Thank you for the explanation.
Just to confirm my understanding — if we are using an OVS Bridge, it cannot be set to VLAN-aware, so there is no way to avoid this issue in an OVS-based setup, correct?
Also, I tested setting only the Linux bridge...
/etc/network/interfaces contents:
Basic gist is: two LACPs, each containing two of the ports, each nic has one port for each of the two LACPs (thus a nic card dying entirely should be ignored)
of those two bonds:
po7 / bond0 is for use by VMs...
Could you post your full network configuration? I've seen several reports now and usually they were using some BCM cards with bonds and VLANs, but I couldn't yet tie them together...
cat /etc/network/interfaces