Latest activity
-
Ssteve-dg reacted to Alwin's post in the thread [SOLVED] command 'apt-get update' failed: exit code 100 with
Like.
No gpg key, see the link. https://pve.proxmox.com/wiki/Package_Repositories -
SteveITS reacted to devaux's post in the thread Feature Request: Show VLAN tag in VM Summary "IPs" section with Like.
Hi everyone, it would be a great to see the configured VLAN tag directly in the "IPs" section of the VM/CT Summary page. Currently, one has to click into the "Hardware" or "Network" tab to verify which VLAN a NIC is assigned to. Having this... -
RRoxyProxy replied to the thread Storage for small clusters, any good solutions?.Thanks again everyone for your detailed answers. So far Blockbridge still sounds very interesting and when the time comes I or someone from my team might reach out to the Blockbridge Team for more information. For some of our customers who dont...
-
Dd.konyayev replied to the thread ceph-osd crashes with kernel 6.17.2-1-pve on Dell system.Has anyone performed testing on kernel version 6.17.13?
-
Wwoma replied to the thread Should I set CT Swap to 0 to prevent PVE host crashes during high memory usage?.Hi, from my experience you could run into issues as soon as sum of used LXC swap space grows beyond available swap space on that specific PVE node. Then LXCs could restart or processes inside LXC get killed as soon as they try to use even more...
-
BBu66as replied to the thread OCFS2(unsupported): Frage zu Belegung.Das ist besorgniserregend — die Allocated Pages sind nicht gesunken sondern gestiegen: von 1.673.851 auf 1.727.919, das sind +54.068 Pages ≈ +211 GiB. Die fstrim-UNMAPs werden vom Controller offensichtlich nicht in freigegebene Pages umgesetzt...
-
Mmicneu reacted to Bu66as's post in the thread Dateien im Netzwerk verschicken sich nur sehr langsam obwohl das Netzwerk ordentlich Leistung hat - Woran kann das liegen? with Like.
Hallo @3n0x, so lässt sich das leider nicht eingrenzen — da brauchen wir deutlich mehr Infos: Proxmox VE Version (pveversion -v) Netzwerk-Konfiguration (cat /etc/network/interfaces) Zwischen welchen Endpunkten ist es langsam? (VM↔VM, VM↔Host...
-
JJohannes S reacted to Onslow's post in the thread Replication of a VM between two independent Proxmox clusters (LVM storage) with Like.
@katti Depending on your requirements on a how long the services can be unavailable and on how much fresh data can be lost, a workaround could be frequent backups to PBS. And restoring to the other cluster when needed). Thanks to "dirty bitmaps"...
-
JJohannes S reacted to alexskysilk's post in the thread HA configuration for node migration/restart only with Like.
yes. For your test vms (and other non critical) just set the HA request state to ignored. you can still live migrate them just fine.
-
JJohannes S reacted to alexskysilk's post in the thread HA configuration for node migration/restart only with Like.
You realize that HA request state of started means, you know, that it should be started. If you dont want that, set a different request state.
-
JJohannes S reacted to BobhWasatch's post in the thread HA configuration for node migration/restart only with Like.
No, it still doesn't make sense. Proxmox is somehow supposed to know if this was an "intended" shutdown rather than a VM crash, and do something different in that case. And you want "on demand" machines to have high availability? What the heck...
-
JJohannes S reacted to BobhWasatch's post in the thread HA configuration for node migration/restart only with Like.
What is the point of HA if you're going to be shutting the VM down for extended periods and it should not run on a cluster restart? On the face of it this does not make any sense.
-
JJohannes S reacted to Impact's post in the thread Defining where container templates and ISOs are stored with Like.
@despens Note that the ZFS storage type cannot store files such as ISOs. Create a Directory storage and point it to a dataset's mount point. Check zfs list to see it. Only enable the content types you need. Don't store guest disks on Directory if...
-
JJohannes S reacted to boisbleu's post in the thread Dateien im Netzwerk verschicken sich nur sehr langsam obwohl das Netzwerk ordentlich Leistung hat - Woran kann das liegen? with Like.
Er will damit sagen, dass hier so ziemlich alles an Informationen und Details fehl, um die Frage sinnvoll zu beantworten.
-
JJohannes S reacted to Bu66as's post in the thread Dateien im Netzwerk verschicken sich nur sehr langsam obwohl das Netzwerk ordentlich Leistung hat - Woran kann das liegen? with Like.
Hallo @3n0x, so lässt sich das leider nicht eingrenzen — da brauchen wir deutlich mehr Infos: Proxmox VE Version (pveversion -v) Netzwerk-Konfiguration (cat /etc/network/interfaces) Zwischen welchen Endpunkten ist es langsam? (VM↔VM, VM↔Host...
-
JJohannes S reacted to dcsapak's post in the thread PDM 1.0.1 highest usage bars are bad readable with Like.
i get what you mean, but it's hard to auto generate proper colors when the actual metric is a gradient, so we go from green to yellow to red, but since cpu and memory are on a scale, we have to fade between the colors to have some kind of...
-
JGuest agent on OS & set in PVE VM. You should use a more descriptive thread-title than "problem" to help others seeking help - just like you are looking for now,
-
JJohannes S reacted to alexskysilk's post in the thread Recommendation for software-defined storage for Proxmox on OVH (with Veeam snapshot integration) with Like.
devil's in the details. What is "good" in this context? numbers under load would be a good start. kinda hard to hit a target that isnt visible/understood. This is most likely the way.
-
JJohannes S reacted to bbgeek17's post in the thread Recommendation for software-defined storage for Proxmox on OVH (with Veeam snapshot integration) with Like.
There is no storage level snapshot integration in a Veeam+PVE combination for any storage type. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
-
Hallo @sgw, die Diskrepanz zwischen MSA-Belegung (92%) und OCFS2-Sicht (55%) ist ein klassisches Thin-Provisioning-Problem. OCFS2 gibt gelöschte Blöcke nicht automatisch an den MSA zurück. 1. TRIM/Discard — vermutlich die Hauptursache: #...