I'm just contributor (sending patches or features to proxmox dev mailing list) and not in proxmox staff. (proxmox doesn't paid me.
But I try to help proxmox users when I have time. (Proxmox have a great community![]()
We really appreciate that

I'm just contributor (sending patches or features to proxmox dev mailing list) and not in proxmox staff. (proxmox doesn't paid me.
But I try to help proxmox users when I have time. (Proxmox have a great community![]()
So last stable update to qemu 1.3 doesn't help ?I'm sad to said that but we rolled back to 2.1 and decided to completely disable PVE system update. All of our tests given us that 2.2 even from pvetest is a bit less stable (to be clear: "give us a bit more questions to deal with") that "good-old" 2.1.
Hi,...
P.S. By the way, we'd stuck with 2.1 ever early, but when we deal with (a bit dated) servers with "only" 300 Gb of storage (but isn't 300 Gb still pretty good even nowadays?) and PVE (after clean install from CD) leaves only 170 GB to store VM images (with root of 60+ GB of free space, which looks too huge), we were urged to find a way to make some "custom" install, so we tried to install Debian and PVE over it as a .deb's - but then we got "new" .debs from repo. Deadlock: we won't use new packages due to its slowness on our hardware and we can't use old packages as we're unsure we'll be able to re-create 2.1 environment over fresh Debian install. May there ever be "custom" mode in PVE CD's? We'd rather try to install PVE on SSDs, but SSDs are also limited in size so install out-of-box PVE on 256 Gb SSD and get 100 Gb of VM storage sound non-practical (sure I can install PVE on HDD and mount SSD as VM storage but that was merely an example that 200+ Gb disks are good even today).
linux maxroot=20 swapsize=8
We use essential cookies to make this site work, and optional cookies to enhance your experience.