Disruption in the virtualization market has not slowed down. The fallout from industry licensing and packaging changes continues to push organizations into decisions they were not planning to make this year, and for many, the timelines are getting shorter, not longer. Over the past 12 months, we have worked with hundreds of organizations navigating exactly this situation, and at Red Hat Summit 2026 (May 11–14, Atlanta), many of them will share what they have learned.The early conversations were almost entirely about migration: how to move virtual machines (VMs) safely, how to avoid downtime,
Looking at the release notes or changelogs for QEMU upstream, you might notice that there's something new in version 11.0:SEV-SNP and TDX machines can now be reset.This is a feature we at Red Hat helped implement. The motivations and associated challenges have been explained in detail in a FOSDEM 2026 presentation. Before this feature was available, some confidential guests (AMD SEV-based guests) could be reset normally like other non-confidential guests. Other confidential guests (like TDX, SEV-ES and SEV-SNP guests) would terminate if a reset was attempted (for example, when you initiate a r
Extending confidential computing from individual workloads to the entire cluster is a new frontier in cloud-native security.Today, Red Hat is announcing the Developer Preview of confidential clusters for Red Hat OpenShift, a new feature of OpenShift that extends confidential computing to the cluster infrastructure level. Confidential clusters establish hardware-rooted trust across every node in an OpenShift cluster, creating a fully attested, encrypted, and verifiable execution environment from the ground up.This Developer Preview is available today for OpenShift on Microsoft Azure, powered by