Tech Blog

everyWAN Blog

Technology, cybersecurity and IT trends that matter

Deep Analysis
Cybersecurity
IT Trends
Filter by:
Sala de servidores con bastidores abiertos medio poblados y paneles de parcheo
13 min read

The API for declaring your VMs is now neutral; the provider that fulfils it is not

On 9 November Broadcom took VM API into the CNCF Sandbox: Kubernetes CRDs for declaring a virtual machine the same way anywhere. The next day, on the same blog, the sentence that qualifies it. Inside: the two readings of the same document, the contract field that still carries no netmask, the Proxmox VE 9.2 provider that already exists and has gone thirty-five days without a reply, the KubeVirt question that is also unanswered, and the five questions to ask before this goes into a contract.

Campo de conexión de fibra óptica en un armario de distribución: bandejas con latiguillos azules y amarillos ordenados
6 min read

Everpure supports Proxmox VE; the plugin is still being written

On 5 November 2026 Proxmox announced that Proxmox VE "is supported across the full Everpure FlashArray™ family". The words snapshot, clone, provisioning and plugin never appear in the release: those are on Everpure's blog, in the present continuous ("we're already working on it") and with no date. Inside: the two sentences the release does make, what you actually get today from a shared LUN, why the snapshot-as-volume-chain flag is a technology preview that only applies to newly created disks, the four storage announcements of 2026 and the title that changes, why Pure Storage is now called Everpure, and the three questions we ask before signing off a design.

Sala de servidores pequeña de oficina: dos armarios rack a medio poblar y una bandeja de cableado en el techo
7 min read

Broadcom extends vSphere 8 in Europe only, and support ends with your subscription

On 4 November 2026, inside a blog post about a different product, Broadcom wrote a paragraph that only applies in the European Economic Area: vSphere Standard 8 and Enterprise Plus 8 stay on sale until 31 October 2027, and Extended Support runs "until the earlier of the applicable subscription end date or October 31, 2028". Inside: the three dates that actually count, why 2028 is not your date, the 20 days in which a product is sold after its general support has ended, why the European Economic Area is not Europe, and what really fits into the 357 days left.

Bahías de discos de una cabina de almacenamiento en un armario de rack
9 min read

They dumped the domain controller without entering Windows

On 19 October Unit 42 updated its CVE-2026-0257 report with one sentence that changes where you should be looking: in one intrusion the attackers pivoted from the VPN gateway to vCenter, disabled execInstalledOnly on the ESXi hosts and dumped credentials against the domain controller's virtual disk, outside the guest operating system. Inside: why "they disabled the protection" is generous when the vendor publishes the command, the two execInstalledOnly options almost nobody tells apart and why yours is the weak one, why even switched on it won't stop a Python script, the warning your vCenter was already showing you, the coverage map layer by layer, and six questions answerable with yes, no or a number.

Placa base de servidor con dos sockets de procesador, disipadores y bancos de memoria
9 min read

vSphere Express: a fixed 128 cores, one year, one order per customer

The replacement for vSphere Standard now has a SKU code, a distributor price and an availability date. What it does not have, as of 4 November 2026, is a Broadcom announcement — even though Broadcom's own techdocs document it. We work through the arithmetic of a fixed 128-core package against the 16-core-per-socket minimum, with a five-row table, and go through the three lines of small print that decide whether the package exists for you at all: one order per customer, a one-year term and net-new eligibility. And we say when we would NOT buy it, even where that cuts against what we sell.

Pasillo de un centro de datos con bastidores llenos de servidores de 1U y algunas posiciones ya vacías
8 min read

They pulled the VDDK, and your VMware-to-Proxmox exit never ran through it

Around 25 August the public VDDK downloads vanished without notice and it was read as VMware's exit door being shut. Some migration routes read disks through that library and some never touch it; the Proxmox importer is one of the latter. We check it three ways and explain why the most obvious one — opening the package dependencies — proves nothing: the VDDK cannot be redistributed, so no Debian package can declare it, not even the ones that do use it. Also here: the six things the importer does NOT do, and the wall both routes share, vSAN.

Sala de servidores con racks de bastidor abierto parcialmente poblados y suelo técnico perforado
6 min read

They will pay for your VMware exit. You sign the term: 36 months

Red Hat waives the first year on a 3-year agreement, Nutanix discounts by deal size with a 36-month minimum, HPE gives up to twelve months of licences and a one-dollar Zerto, and Mirantis pays for the whole migration. Four offers, four brochures and one column almost nobody reads: the term. What each one subsidises, what none of them pays for, what Nutanix's own terms say about renewal pricing, why both published deadlines land before end of support, and the five questions worth asking in writing before you sign.

Pasillo entre racks de una sala de servidores a oscuras, iluminado solo por los pilotos verdes y azules de los equipos
9 min read

ESXi: the 2.7 we ranked fifth was a zero-day

On 30 July we put CVE-2026-41709 last on a list of five: 2.7 out of 10, "insufficient logging" in VMware ESX. Ninety days later CISA adds it to the Known Exploited Vulnerabilities catalog because an adversary had been using it as a zero-day. We go back over that post and correct two things: the doubtful window does not start on the advisory date, and shipping logs off the box does not fix a non-write.

Armario de comunicaciones mural de una sede con panel de parcheo, switch y router
9 min read

Proxmox across a thousand sites is not one cluster: it is a thousand clusters

On 26 October 2026 it was reported that Tesco is replacing VMware with Proxmox in its stores. The headline is the hypervisor; the real detail is in the job ad, which does not ask anyone to build a cluster but an "Edge Management Platform" to provision, manage, monitor and maintain the store estate throughout its lifecycle. The reason is a number from Proxmox's own documentation: corosync needs latencies under 5 milliseconds between all nodes, which rules out anything that is not a LAN. With the per-socket arithmetic that flips sign at the edge, the minutes of data loss that ZFS replication brings with it, what the Datacenter Manager still does not do according to its own roadmap, and the three-bucket inventory for deciding what stays in the site and what should never have been there.

Bastidor con varios servidores apilados y sus bahías de disco SAS a la vista, en penumbra
9 min read

VMFS alternatives on Proxmox: no release has been verified on a storage array

This week two clustered filesystems started circulating that do on a shared LUN what VMFS does for vSphere: CetraFS and MeshXFS. It is the missing piece in every migration away from VMware where the array still has life in it. Both are free software, both package for Debian, and both write in their own README why they do not yet belong underneath your machines. The deciding sentence is MeshXFS's: "no release has been verified on a storage array". With the arithmetic of the 120-second stale window against multipath's stock 90, who kills the partitioned host once vSphere HA is gone, why Proxmox's own option has spent 446 days in technology preview, and seven checks before letting any of this near production.

Centro de operaciones de red real: puestos curvos con monitores y técnicos atendiendo, iluminación tenue
9 min read

Three of the seven lines DOCOMO signed with VMware are not software

On 20 October 2026 Broadcom announced its first comprehensive ten-year agreement in Japan: NTT DOCOMO keeps its private cloud on VMware Cloud Foundation. The reading that will circulate in this week's renewal meetings — "not everyone is leaving" — is the wrong one, and the reason sits in the release itself: of the seven lines listed in the product annex, three cannot be installed. They are a Support Account Manager, a Technical Account Manager and VCF Forte Support; people with your name on their list. We explain why that column is not in your catalogue, why the product list read backwards is the dependency inventory that decides how long a migration takes, when we DO tell clients to stay, and we leave you the seven-line exercise to run against your own contract.

Frontales de servidores montados en un chasis de rack, con latiguillos etiquetados a mano y pilotos verdes encendidos
9 min read

HyperArmor does not patch ESX: it buys you time

Broadcom introduced VMware HyperArmor today: a separately sold layer that mitigates ESX hypervisor flaws with "no host reboots or software upgrades". The most honest sentence of the launch came from one of its own engineers: "this basically buys you time". The free route to avoiding the reboot has existed since vSphere 8.0 Update 3, and it ships with a written exclusion list: TPMs, DPUs and virtual machines without Fast Suspend and Resume. Of the three pieces HyperArmor sells, one is already sitting on your host, switched off.

Frontal de un rack de servidores con varias generaciones de equipos apiladas, iluminadas por sus propios pilotos
8 min read

Multi-hypervisor is not a phase: it is what you will maintain twice

Sixty percent of the VMware customers surveyed by Unisphere Research are considering a multi-hypervisor strategy, and the four barriers they cite most — operational complexity 40%, multi-vendor management 38%, and tied at 37% securing the increased attack surface and team skills — are precisely what running two platforms at once installs in your shop. The list of what you end up maintaining twice, what genuinely does get halved, and when the dual state is the right call.

Pasillo entre armarios de servidores con las puertas cerradas en un centro de datos
9 min read

VCF hardening: the P0 shuts the door and the P2 leaves you the key

On 5 October 2026 VMware published its security configuration guidance for VMware Cloud Foundation. We downloaded the 9.1 spreadsheet and counted: 260 controls, 160 of them without the secure value set out of the box. Inside: why the control that shuts off host access is a P0 while the one that leaves you a recovery path is a P2, which virtual switch setting ships open on only one kind of switch, and the lines where the guide itself says what it does not do.

Técnico agachado detrás de un rack, con el portátil apoyado en el suelo técnico y un manojo de cables sueltos al lado
10 min read

Moving to Proxmox doesn't touch your licences; failover does

The Windows licensing question comes up in every migration meeting, and the short answer disappoints everyone: changing hypervisor recalculates nothing. Something else changes the bill, and Microsoft has it written in a single sentence: "License Mobility across Server Farms is not available for Windows Server, so each server must be licensed for peak capacity at all times." Each server, peak capacity, at all times. The licence does not follow the virtual machine, so the number depends on how many nodes it could ever start on: 32 core licences or 96, for exactly the same installation. What changed in SQL Server 2022, why the AVMA myth does not apply to you if you are coming from vSphere, and why a Proxmox affinity rule is a useful control but not a contractual boundary.

Frontal de varios servidores de rack apilados, con sus bandejas de disco etiquetadas y los pilotos de estado encendidos
9 min read

Piloting a VMware alternative is not migrating

Gartner has put a number on leaving VMware, and the number will be misquoted all autumn: by 2029, 55% of enterprises "will initiate proofs of concept" for alternatives, up from 25% in 2026. Initiate pilots, not migrate. Our argument is that most of those pilots will not help anyone decide anything, because they are built to succeed: install it, boot a VM, close the meeting. The six things an honest pilot has to try to break — starting with the restore, not the migration — the variable no analyst can give you (your renewal date), and the cases where we still tell people to stay.

Cabina de disco montada en rack, con dos filas de bandejas de disco y sus pilotos de actividad
10 min read

Moving to Proxmox and reusing your SAN: the snapshot is what does not travel

The array is paid for, so it stays: the cheapest-looking decision in the project and the one that changes your day-to-day the most. In Proxmox the snapshot is not taken by the hypervisor but by the storage plugin, and on a shared LUN with LVM-thick the documentation says «snapshots are not possible by default…». What fixes that has been labelled a technology preview since 9.0, and the vendor puts it in writing on its own roadmap. The seven real options and the decision tree we are willing to sign.

Parte trasera de una librería de cintas con las unidades LTO y su cableado de fibra
5 min read

Broadcom pulls the VDDK: the first thing that breaks is not your migration, it is your backup

In late August the download pages for the Virtual Disk Development Kit started returning a 404, with no announcement and no deprecation notice. The coverage has read it as "leaving VMware just got harder", and that is half true: it depends where you are going, because Proxmox VE's ESXi importer does not even use it. What almost nobody has looked at is Broadcom's exact wording — "no longer available for use or download" — or the place where that library has been working for twenty years without anyone looking at it: inside your backup.

Armarios de rack vacíos recién instalados en el pasillo de una oficina
9 min read

VMware to Proxmox: the disk arrives intact, Windows will not boot, and the mistake was made two weeks earlier

The Proxmox VE import wizard copies the machine off ESXi without a hitch. Then Windows will not boot, and it is not the wizard's fault: the official documentation says that to boot from VirtIO SCSI, Windows "needs to see a disk requiring the driver before". That before is the problem, because the only place you can do it is the machine you have already shut down. The official way out works, but it is a per-machine, sequential procedure that lives inside the maintenance window. The alternative is not to speed it up: it is to move it to another date.

Cuarto de informática de una empresa pequeña con un bastidor abierto de dos servidores, un SAI abajo, estanterías con discos de repuesto y una mesa plegable con una caja de herramientas
9 min read

VMware brings back vSphere Standard: how to read an announcement that does not exist

On 2 September 2026, two Broadcom executives told the press there will be a new vSphere Standard. No keynote, no press release, no price and no date. The last time the rules changed for this segment—the 72-core minimum of April 2025—that news also arrived through a distributor email, and the reversal through a revised price list. What was actually said, where Broadcom draws the line for "small", and six things you can do before 13 October.

  • 1
  • 2

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