Search results

AMD already confirmed this bug...

What does VMware Workstation have to do with Proxmox???

Could you please explain this? On Debian I always do "upgrade" first, and then "dist-upgrade". Never had any problem with it...

AFAIK, pve-firewall is just front-end for iptables. Set of rules for VM is created in /etc/pve/firewall/VM-id/*.fw so you can check it there if it looks similar to what you expect... But personally, I do not recommend using PVE-firewall for anything else but filtering access to PVE-host...

PVE does NOT support software-/fake-/bios-/pseudo-raid. And what you have on AMD x370 chipset is exactly that...

Except of those trying to escape VM to compromise hypervisor...

There's no way you could hide it. There was long discussion about this on VMware-forum some year or two ago, with a few proof-of-concept apps able to detect very reliably if they are running on VM, or bare metal HW. IIRC, they were not based on some strings searching in hw/bios, but used timing...

One more interesting link (some might have missed). It explains RH plans in storage, which basically is "stratis+xfs". BTW, "stratisd", "systemd"... deja-vu? I would not be surprised...

That web-site should be updated to take ZFS into account. Standard linux tools (free, top, etc) are not sorting ARC properly, they do not put it into "buffers/cache" value. So user really can see "available" value close to zero...

And do we want to have alternative to btrfs? (OT: check bcachefs, seems very promising) It is in mainstream kernel, so what you'd like to improve in its integration? Every modern OS (and filesystem) does the same, following the rule "any utilization of ram is better then not utilizing it at...

It is possible, but I do not recommend this workaround because it does not help. It does not matter if it is HW-raid5 with 5 disks or HW-raid0 with just one disk, there still will be raid-layer between ZFS and disks...

FYI, RedHat seems to be abandoning btrfs, as it was removed from the latest RHEL 7.4. This might be serious, because as we know, RedHat has quite strong voice in Linux. Remember, it came with systemd, and despite strong oppostion, it pressed it forward to became de-facto standard init system...

Using memory for ZFS-cache has low priority. So if some app (or VM) needs more memory then there is currently available, ZFS should reduce ARC-size automatically down to minimum value (can be configured too) and release it. This is similar to standard linux disk-cache. So if you have plenty of...

You have to create that file in given location (/etc/modprobe.d/zfs.conf), update initram, and reboot (not sure if this is necessary, but I think so). You can monitor ARC-size in /proc/spl/kstat/zfs/arcstats: Look for "size" (current ARC size in bytes) and "c_max" (maximum ARC-size). And you...

Filesystem is cached, of course! Without caching you'd get terrible performance. And concerning HW-raid and ZFS, I'd recommend to read wiki: Do not use ZFS on top of hardware controller which has its own cache management. ZFS needs to directly communicate with disks.

1. Then remember, ZFS can (per default) use up to half RAM you have... 2. It is VERY BAD IDEA to put ZFS on top of HW-raid...

What kind of storage do you have? You said "each has 3TB drive", so is it local on every node? Do not forget some memory is used for cache (be it "traditional" or ARC in case of ZFS)...

You must know what storage you selected during install. Is it local (some disks in this box) or networked? If local, is it zfs or lvm/ext? Anyway, 2 or 3GB is really not much for PVE. Your host might be swapping badly... BTW I still think you'd better check "top". Either log-in to your PVE...

I'd like to have your problem (host using less memory than you think it should)! Mine is mostly opposite: even taking arc into account, pve-host is using more than (I think) it should. And I can not even find why (ps, top, etc shows nothing)...

You can always try other ftp-server...