Tech Blog

everyWAN Blog

Technology, cybersecurity and IT trends that matter

Deep Analysis
Cybersecurity
IT Trends
Filter by:
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.

Servidores retirados apilados sobre un palé de madera junto a sus guías de rack
8 min read

650 servers became 400: where the savings from leaving VMware actually come from

Topgolf says it avoided or eliminated more than $11.3 million in combined infrastructure costs after moving 12,000 virtual machines off VMware. The headline will end up on a slide this week. What will not is in the same report and in the vendor's own documentation: they went from 650 servers to roughly 400, each venue cluster dropped from six nodes with 35 TB to three with 5 TB, and an entire third-party backup product left the invoice along the way. Inside those $11.3 million there are at least four different bills and only one of them is the hypervisor. We separate the sums, say which part does not transfer to your company, and leave you the list of line items that cost about the same with 40 machines as with 12,000.

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.

Parte trasera de un armario de servidores con los latiguillos de red saliendo de cada nodo hacia los de al lado
10 min read

The switchless Ceph mesh has four variants. Two of them break on one cable

Three nodes wired directly to each other at 25 GbE, with no switch to buy, is one of the best decisions you can make on a small budget. Proxmox documents four ways to wire it and only two survive a single link going down: in the other two, its own wiki says, "the nodes now have a different view" and Ceph reports services as down that are perfectly alive. Since Proxmox VE 9 that mesh is configured from the web interface, with four fabric protocols. And the official documentation still labels that layer tech preview.

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 en penumbra de una sala de servidores, con dos filas de armarios cerrados y sus pilotos encendidos
9 min read

Your VMware provider expires before your contract does

On 8 October 2026 IBM handed "hundreds" of its VMware cloud customers over to another company. None of them signed that deal. The date that governs a hosted VMware cloud is not in your contract: it is in the partner agreement your provider holds with Broadcom. Inside: the January FAQ sentence that describes what just happened nine months in advance, the seven dates with their owner in one table, the two days between 31 March and 2 April 2027, why "VCF 7" does not exist in Broadcom's documentation, and four questions that fit in one email.

Pasillo de un centro de datos con un rack abierto, un carro de consola con monitor y teclado, y una silla vacía
9 min read

A VM escape with no CVE and no patch: what root on a Proxmox node reaches

On Tuesday 6 October 2026 The Register reported that a researcher claims a guest-to-host escape in KVM, that Vercel's CEO confirmed it inside their bounty programme, and named Proxmox among those relying on KVM. There is no CVE, no patch and no technical detail. Since there is nothing to patch, what is measurable today is the radius: Proxmox VE's documentation says QEMU runs as a root process, so it is one hop and not two; and root on one node reads /etc/pve/priv, which pmxcfs replicates in real time to every node. Inside: the table of ten files with their official descriptions, why the backup password sits there "in plain text" next to the encryption key, and the rotation list, line by line, with what each one costs.

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.

Parte trasera de un rack con servidores de 1U, sus puertos de consola a la vista y los mazos de cables recogidos
10 min read

Moving to Proxmox: permissions do not travel, and the role that sounds like "user" opens the console

The migration brings the disks, the configuration and the networks. It brings not one line of the permissions table, and because the two tables look alike in shape, almost nobody rebuilds theirs: they copy it from memory, going by the names of the roles. Inside: the mapping between a vCenter permission and a Proxmox ACL, with its three gaps; the literal definition of the PVEVMUser role —"view, backup, configure CD-ROM, VM console, VM power management"— and why console, CD-ROM and power together do not describe a reader; the question only your installation can answer; the inheritance rule that subtracts instead of adding and bites everyone arriving from Active Directory; the family of privileges that reads and writes files inside the guest, has no mental equivalent in vCenter and is a virtue of the model that nobody uses; root@pam, the unconfined account that cannot be deleted; and the four commands that tell you, the following Monday, who can do what on your cluster.

Aula de informática con filas de equipos de sobremesa idénticos y pantallas apagadas
8 min read

Memory integrity turns itself on in October, and only where nobody decided anything

Microsoft announced on 1 September that the October 2026 quality updates will start enabling memory integrity on more eligible Windows devices. The press read the sentence «existing administrator and user choices and policies will remain in effect» as reassurance. Read it as a census: if the existing decision is respected, the change lands precisely where no decision was ever written down, and there the administrator becomes Windows Update. Inside: what actually gets switched on (HVCI on top of VBS) and why «eligible» is not a list you can query; the three Win32_DeviceGuard fields that answer where you stand today and why «configured» is not the same as «running» —the manual documents a case where they diverge—; why the symptom will not arrive as «a security failure» but as «the accounts scanner has stopped appearing», one at a time over a period Microsoft does not specify; the UEFI lock trap that turns undoing the policy into a physical trip to the machine; the counter-intuitive detail that the stricter value of RequirePlatformSecurityFeatures protects FEWER machines; the seven-day plan with a dated census, a pilot ring and a rollback prepared in advance; and the other two clocks expiring on that same 13 October, of different natures and with no shared rollback plan.

Sala de servidores con racks cableados y un módulo de gestión de potencia
9 min read

Moving to Proxmox 9.2 wasn't your call: the repository made it

Ask whoever runs your cluster who decided to go from 9.1 to 9.2, and in which meeting it was approved. In most places nobody decided: Proxmox VE ships no repository per minor version —there is nothing like a pve-9.1-security— so a routine apt dist-upgrade, the same one applying the patches you do want, leaves you on the latest published minor. The software that takes your backups does have a supported-version matrix, and it runs behind: Proxmox VE 9.2 shipped on 21 May 2026 and the Veeam plug-in covering it arrived on 29 July, 69 days later. And one detail misleads: plug-in 3.3 for the 13.0 branch shipped on 25 August, twenty-seven days AFTER 4.0, so "I am up to date" can mean up to date on the branch that does not carry the new support. Nothing turns red; what you lose is the right to open a case. The three facts that must live on the same line before you open the window, why the right order is matrix first and apt second, the ARM architecture boundary, and where this crack does not exist.

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.

Armario de servidores con cada máquina etiquetada a mano, una por una
8 min read

Your Proxmox backup skips disks and the job still turns green

The limitations page for the Veeam plug-in for Proxmox VE was updated on 15 September 2026, and two lines in it carry the word that really matters: skipped. There are two very different kinds of "not supported": the one that stops your job and the one that skips a disk and paints the job green. What falls outside the backup of a Proxmox platform, what does not come back when the machine comes back, why LXC containers are a separate inventory, and why the backup manual gets read before you choose your storage rather than on restore day.

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.

Pasillo frío de un centro de datos con una silla vacía y un carro de consola aparcado junto a un armario abierto
9 min read

The Proxmox CVE your scanner cannot evaluate

CVE-2023-54391 is a 9.8: you get in as root@pam with no password. We queried its record through the NVD API and the GitHub Advisories API, and here is what comes back: NVD publishes no CPE configuration at all and flags the record as Deferred; GitHub returns an empty list of affected packages; and the only range that exists stops at "7.4" while your nodes call themselves 7.4-17. A scanner that decides by version matching has nothing to decide with. Meanwhile a provider published its post mortem: twelve hypervisors mining from 31 August to 17 September, logs wiped and the sentence "we cannot prove it".

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.

Pasillo de un centro de datos con dos filas de armarios de rack idénticos
9 min read

The cluster picks a node by counting guests: anti-affinity in Proxmox VE 9 and the rule nobody declares

When a node goes down, the Proxmox VE scheduler decides where your HA-managed machines come back up. On a freshly installed cluster it does that by counting active guests: it has no idea that 101 is the second leg of 100. Proxmox VE 9.0 brought affinity rules so you can tell it, with an asymmetry worth knowing — the rule that pins a guest to a node is a preference, the rule that keeps two guests apart is an order — and an arithmetic that decides whether your VM comes back degraded or does not come back at all.

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.

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