Hi all, how can we set a Limit of Proxmox Snapshots, Problem is, many Users make every Day Snapshots without delete old, and Storage is full after many Weeks. We need a Option to set a Limit of Snapshots or a seperate Space what can uyed max. for...
So the big question is
Can QEMU recognize when the VM actually resets it's processor ?
I feel like that is a really special and easy to distinguish moment for the hypervisor, and it should be possible for the hypervisor orchestrator to detect...
Ok, I test
Without guest agent, nothing but a full shutdown with the VM stopping worked
With guest agent, the VM rebooting itsef, like below, doesn't work
Rebooting the VM using the external control (which require the Guest agent), that works...
I can see some work has been done close/related to this bug in the latest Proxmox kernel commit.
https://github.com/proxmox/pve-kernel/compare/d22f95460b32713c49c587baca651b36dc603085...3ffb6d0af76b836a578bf05baf6f3593a5c821a5
But to me it looks...
That's awesome to hear! Glad we could help!
@fabian pinging you here, It may be worth for PVE team to look at including this fix sooner than later!
Cheers
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
Setup a real monitoring system like zabbix, prometheus, checkmk or icinga in a dedicated vm or lxc and put the agent of your chosen monitoring tool inside your guests. Proxmox dashboards will never have the same features set and reliability.
We have been running the TrueNAS storage plugin for Proxmox VE (github.com/truenas/truenas-proxmox-plugin) in production for months: three nodes on PVE 9.2.4, NVMe/TCP against TrueNAS SCALE 25.10, plus iSCSI for testing. Two of the things we hit...
A common issue is that third-party driver are not compatible with newer kernel versions. Maybe look at /var/lib/dkms/synosnap/0.12.10/build/make.log as the message suggest? This will not tell you much but it might help the third-party driver...
You can do it in two ways:
zpool replace pool1 1200958216758885009 <new disk>
Or, ou would just use the new disk and attach it to the mirror-0 vdev like this:
zpool attach pool1 ata-WDC_WD80EMAZ-00M9AA0_VAGDUWBL <new disk>
zpool detach pool1...
I realize that, but I'm hopeful that the PVE VM dashboards will eventually expose more of the RAM data that QEMU Guest Agent already provides.
I don't think it's unreasonable to want to be able to glance at the guest's dashboard to get an idea...
Looks like already reported bugs for this, or things along these lines:
https://bugzilla.proxmox.com/show_bug.cgi?id=7204
https://bugzilla.proxmox.com/show_bug.cgi?id=7275
Just linking for posterity. For now I'm going to work around the problem...
@pchr Bitte versteh die Frage nicht falsch: Wurde ein solches Vorhaben vorher mit dem Softwarehersteller abgestimmt? In meiner früheren Firma hatten wir einen ähnlichen Fall und haben das im Vorfeld mit dem Hersteller geklärt.
Außerdem wäre es...
Setup a real monitoring system like zabbix, prometheus, checkmk or icinga in a dedicated vm or lxc and put the agent of your chosen monitoring tool inside your guests. Proxmox dashboards will never have the same features set and reliability.
Recent reports are that FreeBSD does not report memory usage details: https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#VM_Memory_Consumption_Shown_is_Higher
Just adding a +1 for this issue.
I ran into this issue today after trying to clone a VM from a template that gets built with Packer weekly.
Took some serious debugging, but eventually I checked the image with hexdump and seen lots of weird...