Search results

At this stage, I’m should move the discussion to btrfs mail list, addressing the following questions. From Proxmox point of view, I would need an opinion on question 3 - compiling my own proxmox kernel 1) Is there a setting at btrfs level that I’am missing ( maybe mount option) to trigger...

My use case is LXC containers on btrfs ( Btw, I should publish the patches updated for the latest kernel https://forum.proxmox.com/threads/btrfs-experimental-storage-pve-4-4-13-testing-issues-patch.33896/) For certain virtual machines, I get uncorrectable errors checksum errors scrub device...

My use case is described here https://lwn.net/Articles/442355/, for containers with checksum integrity, because I can’t use the qemu workaround cache=writethrough . Directly setting parameters like max_ratio or read_ahead_kb ( see...

Congrats for the new release! What does it mean "btrfs storage plugin (postponed)" in https://pve.proxmox.com/wiki/Roadmap#Roadmap ? 1) That is postponed from 5.3 https://pve.proxmox.com/mediawiki/index.php?title=Roadmap&type=revision&diff=10231&oldid=10160 , and will land in 6.0? 2) Will...

There will be Proxmox 5.4, or it will bump directly to 6?

For Jessie, If that mirror doesn't work, we can install the package directly "If your current package mirrors redirect by default (meaning you can’t update apt when using that flag) you’ll need to pick different mirrors or download the package directly" via original reporter...

Congrats for the new release! I am aware that not all the features on the current roadmap could make it into the next release, due to huge working volume. Do you think that "btrfs storage plugin" will land in 5.4, since it was already on roadmap for 5.3...

Are there any API Clients for Proxmox Mail Gateway? Or we have to fork from https://pve.proxmox.com/wiki/Proxmox_VE_API#Clients ? Thx!

I didn't say that there is an express security issue, regarding how WHMCS stores password. As I already wrote above, even in the situation when password security is flawless in WHMCS, the Proxmox could be abused by excessive or malicious API call ( delete for instance). There is a need for a...

For the sake of simplicity, I shall build the post, based on https://www.modulesgarden.com/products/whmcs/proxmox-vps example. Normally, this should be posted in https://www.forum.modulesgarden.com/, but the discussion is more general, regarding the security of any third party application...

Congrats for the new release. Hopefully, btrfs integration with proxmox will land on https://pve.proxmox.com/wiki/Roadmap#Roadmap ( see https://forum.proxmox.com/threads/proxmox-btrfs-support-roadmap-as-fallback-for-possible-licensing-issues-zfs-on-linux.32561/)

Here is the full output of the checking tool. If hardware is vulnerable, we don't need bios update ( maybe is not even available for certain servers), since we have software mitigation. HARDWARE CHECK Spectre and Meltdown mitigation detection tool v0.35 Checking for vulnerabilities on current...

Tested on PVE 4 & 5, so far so good!

You could manually install the latest package, according to https://forum.proxmox.com/threads/meltdown-and-spectre-for-newbie.39183/#post-194316 Depending on cpu, it could work or not. I have tried on both Jessie and Stretch, but not production servers and without performance benchmarks...

Results of https://github.com/speed47/spectre-meltdown-checker for kernel 4.4.98-3-pve #1 SMP PVE 4.4.98-103 (Mon, 8 Jan 2018 10:15:44 +0100) x86_64 GNU/Linux PROXMOX ./spectre-meltdown-checker.sh Spectre and Meltdown mitigation detection tool v0.29 Checking for vulnerabilities against running...

@BelCloud , any updates? Thx!

SHORT STORY Solution for use case with public ip address, from different subnets ( /etc/pve/firewall/cluster.fw) [RULES] IN ACCEPT -source +management -dest +management -p udp -dport 5404:5405 OUT ACCEPT -source +management -dest +management -p udp -sport 5404:5405 LONG STORY Cluster...

According to https://pve.proxmox.com/wiki/Firewall#pve_firewall_ip_aliases, user can overwrite local_network in the cluster.fw , in order for the firewall automatically sets up rules to allow everything needed for cluster communication (corosync, API, SSH) using this alias. What about...

Thanks for the argumentation. Can you point me to the proxmox code line, containing cluster algorithm formula? I didn't find floor keyword in code.

The problem Problems with "two_node" Clusters This corosync options depends on a fence race condition, and only works using reliable HW fence devices. Above 'self fencing' algorithm does not work if you use this option! Via...