Tech Blog

everyWAN Blog

Technology, cybersecurity and IT trends that matter

Deep Analysis
Cybersecurity
IT Trends
Filter by:
Sala de servidores de empresa de noche, con las luces apagadas, la puerta entreabierta a un pasillo iluminado, un taburete vacío junto al rack y un carro de servicio aparcado en el pasillo
5 min read

Proxmox goes 24/7 on 19 October: what those two hours actually buy you

On 2 September 2026 Proxmox announced that its enterprise support goes 24/7 on 19 October, and opened a North American subsidiary. Until now it ran Monday to Friday, 07:00–17:00 CET/CEST, on Austrian business days. What each plan includes, what it really costs per CPU socket, the three asymmetries sitting inside the announcement itself —response is not resolution, local support stays office hours, and the scope is three products rather than your system— and the six questions for reading any 24/7 support contract, your provider's included.

Omnissa Horizon certificado en Proxmox VE: dos puestos de oficina vacíos con los monitores apagados y un cliente ligero detrás de la pantalla
9 min read

Proxmox VE is now Horizon Ready, but in manual mode: you create and power off the desktops yourself

On 4 September 2026 Proxmox announced that Proxmox VE has achieved Omnissa Horizon Ready Hypervisor certification. It is real and it removes a requirement, but it lands in "Manual Provisioning Mode": the program page states that provisioning and power policy are not supported. Meanwhile, Horizon has been integrating over the API with another non-vSphere hypervisor since December. Two different regimes, what Horizon stops doing for you, the RAM and GPU arithmetic nobody runs, and which estates this is a way out for today.

Proxmox VE 7 y CVE-2023-54391: dos servidores viejos todavía encendidos en la estantería de un cuarto trastero
9 min read

Proxmox VE 7: the patch had been out for three years and nobody knew it was a patch

On 1 September 2026 Proxmox published advisory PSA-2026-00043-1: on Proxmox VE 7, sending any tfa-challenge value is enough to log in as root@pam with no password. The code that fixed it shipped on 20 July 2023 inside a refactor nobody classified as security, which is why it was never backported. What the flaw does, why a second factor saved you, what to check on your node today, and what all of this says about your inventory.

Memoria por niveles de VMware: NVMe local haciendo de RAM en un servidor ESX
9 min read

NVMe standing in for RAM: memory tiering works if half of yours is idle

VMware refines memory tiering in Cloud Foundation 9.1, available since 9.0: cold pages demoted from DRAM to a local NVMe drive so a host ends up with more memory than you bought. What almost nobody quotes is the recommendation VMware itself published on its blog on 6 August: keep active memory below 50% of physical memory. The requirements, the limits, what is known about the 25% of workloads that does not fit today, and why a memory reservation does not get you out of it.

Parte trasera de un rack abierto con servidores apilados y cables de red recogidos con bridas
8 min read

Migrating to Proxmox: the network is not held by the cluster, it is held by each node

In a VMware to Proxmox migration everybody watches the disks. Disks are the easy part: they either arrive or they do not, and you find out straight away. What gets left out of the luggage is the network configuration: in Proxmox VE it lives in a file on each node, outside the filesystem the cluster replicates. We go through the documentation sentence that says so, why the bridge is missing from the official list of live migration requirements, what the MAC change drags with it, the 10.0.2.x symptom that wastes hours, and how far SDN really takes you.

Pasillo de un centro de datos con un rack abierto a medio poblar y un carro elevador con un servidor encima
5 min read

When NOT to migrate from VMware to Proxmox

Migrating from VMware to Proxmox is part of what we do, and there are cases where our answer is: not now. Two classic objections no longer hold — the scheduler's dynamic mode arrived with Proxmox VE 9.2 on 21 May, and Veeam 13.1 has shipped replication since 29 July. The one still standing is different: Proxmox's HA documentation describes nothing equivalent to vSphere's <em>admission control</em>, which flatly refuses to power on the machine that would break your N-1. And the <code>crs</code> factory settings decide more than people think: <code>ha=basic</code> balances by counting machines. The five cases where we tell clients to stay.

Rack abierto en una sala de servidores con dos bandejas de disco a medio sacar
5 min read

10% of the VMDK is enough: the arithmetic that changes your recovery plan

The ESXi encryptor Rapid7 took apart carries a percentage parameter, and the value observed was 10: on a large VMDK it touches only a tenth of the file, and that is enough to stop it booting. Partial encryption is not new — LockFile was doing it in 2021 — but the numbers are. What it does to your response clock, why no EDR agent belongs on the hypervisor (Broadcom says in so many words that it is not supported), what the same actor does to backup services, and why swapping hypervisors is not a security control.

Servidor de almacenamiento de 4U extraído sobre sus guías en una sala de servidores, con la tapa quitada y las filas de discos a la vista
9 min read

Proxmox's "protected" flag is not a lock, it's a latch

The Pay2Key ransomware shuts down the guests on a Proxmox cluster and deletes the backups using Proxmox's own API: first a <code>--protected 0</code>, then the delete. We read the pve-storage source to see why it works, and the answer is uncomfortable: clearing the latch never costs one privilege more than deleting the backup. What does raise a real boundary, and why it costs nothing.

Chasis de servidor de rack abierto sobre un banco de taller, con la tapa retirada y dos disipadores de procesador a la vista entre los bancos de memoria
5 min read

Azure stops including the VMware licence: the core count nobody does

Two weeks ago we wrote that 31 October 2026 is the end of Azure VMware Solution with the licence included. Microsoft has since published its portable licensing reference, and that is where the counting rules are: how many cores each node type has, why the distributed firewall counts every host in the private cloud even the ones you are not paying for, and which date actually governs your calendar, because it is not the August 2027 one.

Un parquímetro con el indicador EXPIRED en rojo y un coche todavía aparcado detrás: la fecha ha pasado y no ha cambiado nada visible
9 min read

Proxmox VE 8 goes end of life in August: Debian will keep patching you, the hypervisor will not

Proxmox's official table says 2026-08 and does not give a day. What tends to fall outside the headline is that Debian 12's extended support runs to June 2028 through the usual channel, so apt will keep installing real patches on an unsupported node. What exactly freezes, how to check it, the order of the upgrade to 9.2, and why forcing it in August can be worse than being late.

Cronómetro deportivo: los cinco días entre el aviso VMSA-2026-0006 y las primeras conexiones de vCenter comprometidos a la infraestructura del atacante
9 min read

The vCenter advisory said there was no known exploitation. It held for five days

Broadcom published VMSA-2026-0006 on 29 July with no information suggesting exploitation, and that is how we quoted it here the next day. On 3 August the first compromised vCenters started connecting to attacker infrastructure, and on 12 August QUIRSO published the count: 361 victim IP addresses across 47 countries. What those numbers mean, what they do not, and the question that decides whether this concerns you: who can open a connection to your vCenter.

Pulsador de parada de emergencia en una pared: el nodo que se apaga a sí mismo para que el clúster pueda seguir
9 min read

Proxmox HA does not prevent downtime: it shortens it (and sometimes causes it)

Proxmox VE's own documentation sets the ceiling: about 2 minutes of error detection and failover, and no more than 99.999% availability. What really happens when a node dies (a cold start, not a live migration), why a healthy node reboots itself 60 seconds after losing quorum, the requirements everybody skips, and when we do not deploy HA at all.

Sección de un tronco con sus anillos de crecimiento: capas acumuladas durante años, como el código del kernel donde se escondían Zapscape y SCTPhantom
5 min read

Zapscape and SCTPhantom: your Proxmox does not run Debian's kernel

Two Linux kernel flaws published this week break the two boundaries we take for granted: the virtual machine (Zapscape, CVE-2026-64561) and the container (SCTPhantom, CVE-2026-64564). Understanding them is the easy part. The hard part is answering whether the kernel your node actually boots already carries the fixes, because the versions in the advisory — 6.12.101, 7.1.6 — do not exist on your server: Proxmox does not use Debian's kernel. The exact proxmox-kernel versions that do close them (and why 7.0.14-9 is not enough), how to check in four commands, and who genuinely needs to hurry.

Proxmox VE 9.2 para arm64 anunciado el 5 de agosto de 2026: paridad de funciones con x86-64, plataformas NVIDIA Grace y Vera, y sin migración en vivo entre arquitecturas
5 min read

Proxmox on Arm doesn't extend your cluster — it makes you run two

On 5 August Proxmox shipped the first officially supported edition of Proxmox VE 9.2 for arm64: same codebase, same repositories, same lifecycle and feature parity with x86-64. Buried in the announcement there is one sentence that decides how you design your infrastructure: guests only run on nodes matching their architecture, and live migration only works between nodes of the same architecture. What they actually shipped, what you give up crossing to Arm, why the Raspberry Pi is left out, and the five questions we ask before quoting an Arm node.

VMSA-2026-0006: dos vulnerabilidades CVSS 9,8 en VMware vCenter y un escape de máquina virtual en ESX
5 min read

VMSA-2026-0006: two 9.8s in vCenter, a VM escape and the flaw nobody will look at

On 29 July 2026 Broadcom published VMSA-2026-0006: five flaws in VMware ESX, vCenter, Workstation and Fusion, two of them CVSS 9.8 in vCenter and one 9.3 that allows escaping from a virtual machine to the host. There are no workarounds. What to patch first according to the advisory itself (the order is no longer the one you knew), why updating vCenter does not stop your workloads, where the patches are if you hold a perpetual licence with no support, and why the lowest-scoring flaw — ESX may not record what an administrator does — is the one that hurts afterwards.

Proxmox VE 8 llega a su fin de soporte en agosto de 2026
5 min read

Proxmox VE 8 runs out of patches in August: why we won't upgrade on the 30th

The lifecycle table in Proxmox's official documentation puts the end of life of the 8 branch in August 2026. Just over thirty days are left, and the typical reaction is to block out a weekend and jump to 9. Our stance is the opposite: there are six situations where upgrading this August is a worse idea than being late. The live-migration asymmetry that turns your rollback into a restore, why Ceph means two windows and not one, the containers with old systemd that will not start, and a realistic split of the thirty days left.

Proxmox VE entra en el ecosistema de NVIDIA Mission Control: qué cambia de verdad para tu infraestructura
9 min read

Proxmox joins NVIDIA's ecosystem: a logo will not migrate your infrastructure

Today Proxmox Server Solutions announced it is joining the NVIDIA Mission Control ecosystem: Proxmox VE as the virtualisation and high-availability layer beneath the management services of AI factories, with engineering work for the Grace and Vera CPUs. What the announcement actually says, where Proxmox sits in that picture and where it does not, and why an announcement changes the conversation in a boardroom but changes none of the things that decide your migration.

Subscribe to our newsletter

To receive IT stories, everyWAN news and exclusive subscriber offers, sign up to our mailing list

Minorisa de Sistemas Informaticos y Gestión S.L. © 2026
everyWAN
everyWAN