--- Begin Message ---
hello,
nice to see some progress here, but keep in mind that memory calculation
is completely wrong on zfs based systems,
where arcsize is not taken into account
https://bugzilla.proxmox.com/show_bug.cgi?id=3859
regards
roland
Am 08.04.24 um 15:25 schrieb Stefan Lendl:
P
--- Begin Message ---
FWIW, depending on how the sum is used it might actually make even more
sense to use PSS, i.e., the proportional set size which better accounts
for shared memory by dividing that part between all its users, as if
e.g. 10 QEMU processes have 100 MB of shared code and what not
--- Begin Message ---
oh, and shouldn't we also add that to total and free_memory calculation,
even chances are less that the limit is hit there ?
total=`awk '/^MemTotal:/ {print $2}' /proc/meminfo`
free_memory () {
awk '/^(MemFree|Buffers|Cached):/ {free += $2}; END {print free}' \
--- Begin Message ---
Hi Stefan,
looks good for me so far and indeed, on very large system when VMs eat
up >2TB this could hit the limit very soon.
but shouldn't we add some newline , as the original "print sum" prints one ?
root@s740:/usr/sbin# seq 1 10 | awk '{ sum += $1 }; END { print su
--- Begin Message ---
hi,
any reason why this did not get a response ? (i do not see rejection of
this ,nor did it appear in
https://git.proxmox.com/?p=ksm-control-daemon.git;a=summary )
and, while we are at ksmtuned, i think it's is broken, especially when
run on ZFS based installations, as i
--- Begin Message ---
what about adding zfs datasets as a general type of storage?
currently, you need to create a dataset manually and add that as type
"dir" to proxmox, to be able to use file backed instead of zvol backed VMs
that feels ugly.
Am 10.05.23 um 02:08 schrieb Konstantin Filippov:
--- Begin Message ---
good evening,
in https://github.com/proxmox/pve-installer/blob/master/proxinstall
there is
syscmd("zpool set bootfs=$zfspoolname/ROOT/$zfsrootvolname
$zfspoolname") == 0 ||
die "zfs set bootfs failed\n";
that should have been:
die "zpool set boofs failed\n";
regards
rol
--- Begin Message ---
+storage controller, rather than handling all I/O in the main event loop or vCPU
+threads. This can increase performance, because of improved work distribution.
not only that, it evidently avoids vm locking / cpu stuck/freeze
conditions and vm timing hiccups
see https://bu
--- Begin Message ---
ah ok, thanks for letting me know. i did not expect that it's difficult
to handle...but that explains a lot.
Am 17.11.22 um 11:38 schrieb Wolfgang Bumiller:
On Thu, Nov 17, 2022 at 11:23:19AM +0100, Roland wrote:
nice!
btw, what about this one ?
https://bugzilla.proxmox.
--- Begin Message ---
nice!
btw, what about this one ?
https://bugzilla.proxmox.com/show_bug.cgi?id=3909#c3
actually, the firewall stuff is getting blindly executed every 10
seconds, that's causing a lot of noise.
couldn't/shouldn't this be handled more intelligenty ?
roland
Am 17.11.22 um 1
--- Begin Message ---
Hello,
i'm using this script with great success for a while . it doesn't have
dependency to xs utility
https://github.com/guestisp/xen-to-pve/blob/master/xva-conv.sh
It's mentioned at https://pve.proxmox.com/wiki/Xenmigrate
All i need to do is to create pve vm with raw vi
--- Begin Message ---
hello,
has there been done a patch?
there is nothing attached to your mail
roland
Am 16.03.22 um 23:27 schrieb Bruce Wainer via pve-devel:
___
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin
12 matches
Mail list logo
