The pve-container project and its tooling (e.g., pct = Proxmox Container Toolkit) is already doing all that and more. We're using LXC similarly as LXD does: as low level toolkit which we control with higher level management, things like a syscall...
These really aren't containers, but rather LXD spins up a regular virtual machine.
All which Proxmox VE can also already do fine.
(On a techical level, containerization of Windows on e.g. Linux isn't even possible, as containers share the host...
OP mentioned TRIM… in ZFS it’s only enabled for nvme disks by default. See here and the later posts that links to the reasons.
https://forum.proxmox.com/threads/server-disk-i-o-delay-100-during-cloning-and-backup.173051/post-835149
ZFS has a...
It helps, but it is not the main culprit with PVE. PVE writes constantly in it sqlite3 database that is the storage behind /etc/pve and also stores metrics into rrdtool.
Most of the time, those are very small writes that gets write amplified a...
Hello,
Thank you for wounderful software, it fit very well in place where zimbra would be (with extra steps and only as a cog in bigger machine).
I move message based on user mailbox interaction with /Spam folder. If he mark mail as spam the...
Was? Das prunen geht eigentlich recht schnell. Die garbage-collection oder verify-Job werden bei hdds aber immer lange dauern, weil beim PBS der Datenbestand in zig kleine Dateien ( Chunks ) aufgeteilt wird und jeder (!) chunk dafür eingelesen...
OP mentioned TRIM… in ZFS it’s only enabled for nvme disks by default. See here and the later posts that links to the reasons.
https://forum.proxmox.com/threads/server-disk-i-o-delay-100-during-cloning-and-backup.173051/post-835149
ZFS has a...
Some notes on this:
You don't need "host" CPU type.
Memory Isolation uses Hyper-V to run critical processes inside a virtualized environment. Basically, right now it requires nested virtualization.
As you may know, nested virtualization can be...
how come such bugs happen BEFORE releasing the new version? bloody hell, testing in proxmox seems to be nowhere ;-(
no, I am not complaing - just stating the fact
anyway, thanks to all who posted the workaround
Although his examples isn't good (due to being a non-supported setup or (like pci-passtrough) something of an edgecase) his basic assumption is sound: If you use the enterprise repository it's more likely that you will only get updates after bugs...
Running stuff in an unsupported setup does not count. You also cannot sink your car in the river and complain to the manufacturer, that the car did not float.
How would having a subscription solve the problems you faced?
smem is great for that stuff, dstat does it too.
I normally don't monitor hosts by myself, I use telegraf and there is also swap in / out measurements available.
It helps, but it is not the main culprit with PVE. PVE writes constantly in it sqlite3 database that is the storage behind /etc/pve and also stores metrics into rrdtool.
Most of the time, those are very small writes that gets write amplified a...
smem is great for that stuff, dstat does it too.
I normally don't monitor hosts by myself, I use telegraf and there is also swap in / out measurements available.
Was? Das prunen geht eigentlich recht schnell. Die garbage-collection oder verify-Job werden bei hdds aber immer lange dauern, weil beim PBS der Datenbestand in zig kleine Dateien ( Chunks ) aufgeteilt wird und jeder (!) chunk dafür eingelesen...
Hello, the error arrives at the end of the download in the action "make system bootable"
For the installation support, I used a bit of everything, but in this one, I use a DVD with the proxmox ISO to burn on it.
I downgraded to API 9.0.3 and the problem was solved.
There's something wrong with API 9.0.4.
------
apt install pmg-api=9.0.3
DOWNGRADING:
pmg-api
Summary:
Upgrading: 0, Installing: 0, Downgrading: 1, Removing: 0, Not Upgrading: 7...