# virtual machines Published articles for virtual machines. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Security evaluations find traditional virtual machines inadequate for containing cyber-capable autonomous agents DevFeed: [Security evaluations find traditional virtual machines inadequate for containing cyber-capable autonomous agents]() Original publisher: [Read original article]() Author: Olimpiu Pop Published: 2026-09-17T07:07:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [virtual machines](), [Security](), [Vulnerabilities](), [Linux Kernel](), [qemu](), [Firecracker](), [systems]() Tags: [agent-escape-vm](), [ai-security](), [development](), [devops](), [firecracker](), [linux](), [linux-kernel](), [news](), [qemu](), [security](), [security-breach](), [virtual-machines](), [virtualization](), [vm](), [vulnerabilities]() ### AI overview Security evaluations found that a cyber-capable autonomous agent escaped standard QEMU and KVM virtual machine configurations by exploiting kernel and library vulnerabilities. Firecracker contained the agent in testing, but the agent still hardlocked the host through Linux kernel flaws. ### Source excerpt Traditional virtual machines are inadequate for isolating cyber-capable autonomous agents. Tests using GPT-5.6-Cyber indicated multiple escape attempts due to kernel flaws. While Firecracker provided some containment, vulnerabilities remained. The study underscores the need for minimal attack surface virtualisation technologies and rapid, proactive patching strategies to safeguard host systems. By Olimpiu Pop ## How vagrant-libvirt Plugin Deals with Duplicate Subnets DevFeed: [How vagrant-libvirt Plugin Deals with Duplicate Subnets]() Original publisher: [Read original article]() Published: 2026-09-16T06:27:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [Vagrant](), [virtual machines](), [Linux](), [Ubuntu]() Tags: [debugging](), [linux](), [vagrant](), [virtual-machines](), [virtualization]() ### AI overview The article explains that vagrant-libvirt can fail when an existing libvirt virtual network has the same IP subnet as the desired management network but a different name. It identifies the resulting network-name mismatch and reports that correcting the network definition in the Vagrantfile resolves the problem. ### Source excerpt TL&DR: Badly. The vagrant-libvirt plugin mysteriously crashes when an existing virtual network (with a different libvirt name) uses the same IP subnet as the desired management network. Background: netlab is using the vagrant-libvirt plugin to manage libvirt/KVM virtual machines with Vagrant. As I already have that infrastructure, I use it to start standalone virtual machines (usually to test various Ubuntu releases) on my Linux server. Things work great... until they don't. Here's how I managed to waste half a day chasing imaginary gremlins caused by a simple error. Read more ... ## AMD Preparing Linux For Enhanced SMT Protection "ESMTP" For EPYC VMs DevFeed: [AMD Preparing Linux For Enhanced SMT Protection "ESMTP" For EPYC VMs]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-14T18:03:38Z Content type: news Language: en Sources: [Phoronix]() Topics: [Linux](), [Security](), [Hardware](), [cpu](), [Server](), [Cloud]() Tags: [attacks](), [cloud](), [desktop-linux](), [hardware](), [kernel](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [performance](), [phoronix](), [phoronix-test-suite](), [processors](), [security](), [server](), [ubuntu-benchmarks](), [ubuntu-hardware](), [virtual-machines]() ### AI overview AMD engineers are preparing Linux kernel support for Enhanced SMT Protection (ESMTP), a hardware-enforced security feature for EPYC virtual machines using SEV-SNP. ESMTP restricts simultaneous multithreading sibling threads to trusted vCPUs from the same guest or idle host threads, reducing side-channel risks from untrusted host or guest workloads. Support is also needed in QEMU and OVMF, and the feature is opt-in because it has a performance cost. ### Source excerpt AMD engineers today sent out patches on the Linux kernel mailing list for beginning to enable Enhanced SMT Protection "ESMTP" for better security with virtual machines running atop EPYC server processors with SEV-SNP... ## Red Hat edge platforms: Choosing the right one for your use case DevFeed: [Red Hat edge platforms: Choosing the right one for your use case]() Original publisher: [Read original article]() Author: Daniel Froehlich Published: 2026-09-11T13:01:48Z Content type: article Language: en Sources: [Red Hat](), [Red Hat Developer]() Topics: [Edge](), [Containers](), [Kubernetes](), [Architecture & Design](), [Hardware](), [Availability](), [Microservice]() Tags: [containers](), [deployment](), [edge](), [edge-computing](), [hardware](), [high-availability](), [kubernetes](), [management-tools](), [microservices](), [red-hat](), [virtual-machines]() ### AI overview This article introduces a series about choosing Red Hat edge platforms for specific deployment needs. It compares Red Hat Enterprise Linux and Red Hat OpenShift across workload types, platform sizes, hardware requirements, Kubernetes use cases, availability, storage, and management needs. ### Source excerpt Choosing the right platform for an edge deployment is one of the most consequential decisions an organization makes--and one of the most confusing. The options range from a single-board computer running a handful of containers to a full Kubernetes cluster with high availability, software-defined storage, and centralized management. Pick too small, and you hit a wall when requirements grow. The post Red Hat edge platforms: Choosing the right one for your use case appeared first on Red Hat Developer. ## Cursor Cloud Agents can now run in Vercel Sandbox DevFeed: [Cursor Cloud Agents can now run in Vercel Sandbox]() Original publisher: [Read original article]() Author: Allen Zhou Published: 2026-09-03T15:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [cursor](), [Vercel](), [Agent Harness](), [Firecracker]() Tags: [agents](), [apis](), [architecture](), [cursor](), [enterprise](), [firecracker](), [guide](), [sandbox](), [scale](), [vercel](), [virtual-machines](), [workflows]() ### AI overview Cursor Cloud Agents can run in Vercel Sandbox, using isolated Firecracker microVMs as their execution environment. The architecture combines Cursor's agent harness and inference loop with Vercel Functions and Workflows for durable request handling, worker provisioning, monitoring, retries, cleanup, and short-lived user-scoped credentials. ### Source excerpt Cursor Cloud Agents can now run in Vercel Sandbox instead of Cursor's hosted machines. Cursor manages the agent harness and inference loop. Its Self-Hosted Machines APIs let you supply the execution environment where agents clone repositories, edit files, and run commands and tests. Self-Hosted Machines requires a Cursor Enterprise plan. Vercel Sandbox provides that execution environment as an isolated Firecracker microVM for each agent request. Vercel Functions and Vercel Workflows form a durable control plane that claims queued agent requests, provisions workers, monitors sessions, and cleans up automatically. With this architecture, you get: A scale-to-zero worker pool without long-lived virtual machines A dedicated, isolated Sandbox for every agent request Durable retries when a worker or session fails Short-lived, user-scoped credentials inside each Sandbox Follow the step-by-step guide to deploy the reference implementation to your own Vercel account, or learn more in the Vercel Sandbox documentation. Read more ## Networking Aspects of Running VMs in Containers DevFeed: [Networking Aspects of Running VMs in Containers]() Original publisher: [Read original article]() Published: 2026-09-02T05:44:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Containers](), [virtualization](), [networking](), [Linux](), [Orchestration]() Tags: [bridge](), [containers](), [docker](), [ethernet](), [linux](), [netlab](), [networking](), [podman](), [qemu](), [virtual-machines](), [virtualization]() ### AI overview The article explains how vrnetlab and a containerlab fork package virtual machines, especially network devices, as containers so container orchestration can provision network topologies. It focuses on connecting QEMU virtual network interfaces, Linux tap interfaces, bridges, and container veth pairs, including why data-plane and management interfaces require different handling. ### Source excerpt The vrnetlab project and its containerlab fork implement a wonderful idea: let's package virtual machines (primarily network devices that cannot be containerized) as containers to use reliable orchestration tools like containerlab to provision network topologies. That approach might have a few drawbacks (depending on how the container images are built), but the obvious elephant in the room is: how do you make the virtual network plumbing work? Read more ... ## UniFi ENAS vs 45Drives X15: Comparing Two Rackmount NAS Systems DevFeed: [UniFi ENAS vs 45Drives X15: Comparing Two Rackmount NAS Systems]() Original publisher: [Read original article]() Author: Rob Andrews Published: 2026-08-31T16:00:55Z Content type: comparison Language: en Sources: [NAS Compares]() Topics: [Enterprise NAS](), [Hardware](), [Self-hosted](), [Ubiquiti](), [Server](), [Containers](), [virtual machines]() Tags: [45-drives](), [45-drives-2026](), [45-drives-2027](), [45-drives-nas](), [45drives](), [45drives-2026](), [45drives-2027](), [45drives-nas](), [45drives-review](), [45drives-system](), [45drives-unraid](), [45drives-vs-cloud](), [45drives-vs-netapp](), [45drives-vs-qnap](), [45drives-vs-synology](), [45drives-vs-unifi](), [45drives-x15](), [45drives-x15-vs-unifi-enas](), [comparison](), [containers](), [enterprise-nas](), [hardware](), [nas](), [network-attached-storage-nas](), [self-hosting](), [ubiquiti](), [uncategorised](), [unifi](), [unifi-2026](), [unifi-2027](), [unifi-enas](), [unifi-enas-review](), [unifi-nas](), [unifi-nas-comparison](), [unifi-nas-review](), [unifi-review](), [unifi-unas](), [virtual-machines]() ### AI overview This comparison examines the UniFi ENAS and 45HomeLab X15 rackmount NAS systems, covering their hardware, storage architectures, connectivity, operating-system services, management models, and upgrade paths. It presents the ENAS as a centrally managed UniFi Drive and ZFS appliance, while the X15 combines a 45Drives chassis with an x86 workstation platform and a lifetime Unraid licence for broader self-hosting and homelab use. ### Source excerpt UniFi vs 45Drives NAS Servers for Business.- Which Should You Buy? The UniFi ENAS and 45HomeLab X15 sit in a relatively narrow part of the storage market, positioned above conventional desktop NAS systems but below many fully configured enterprise storage platforms. Both are sold without storage media, use rackmount steel enclosures, provide at least 15 [...] ## AAOS SDV - Secure by Design DevFeed: [AAOS SDV - Secure by Design]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-08-24T16:00:31Z Content type: article Language: en Sources: [Android Developers Blog]() Topics: [Android](), [Security](), [virtualization](), [virtual machines](), [SELinux](), [POSIX](), [Processes](), [Google]() Tags: [android](), [android-security](), [article](), [google](), [posix](), [process](), [security](), [selinux](), [virtual-machines](), [virtualization]() ### AI overview This article explains the security design of Android Automotive Operating System for Software Defined Vehicle (AAOS SDV). It describes virtualization for domain isolation, UID-based application and service sandboxing, POSIX capabilities, SELinux deny-by-default enforcement, and Android's vulnerability management and disclosure processes. ### Source excerpt Posted by Markus Vill, Software Engineer, Sean Keys, Security Engineer, and Istvan Nador, Software Engineer, Android Auto At Google, we believe our products should be secure by design, which is why we built the Android Automotive Operating System for Software Defined Vehicle (AAOS SDV) on existing, market-proven platforms, leveraging virtualization technologies like Cuttlefish. While our release announcements focused on the features, this blog post outlines some of the security concepts. Foundation: Domain IsolationVirtualization to isolate co-hosted instances The current trend of consolidating Electronic Control Units (ECUs) into a single chip reduces isolation by running multiple domains side-by-side. While AAOS SDV instances provide internal isolation mechanisms, it is often preferable to run logical domains independently. For instance, a cluster and an infotainment system have distinct requirements. We use virtual machines to run multiple instances in parallel, ensuring that sharing remains explicit and isolation is the default behavior. Inherited Android Security AAOS SDV evolved from Microdroid, a minimalistic Android version optimized for privacy virtual machines (pVM). This lineage provides Android platform engineers with established security features they already know. Process Isolation & Deny by Default AAOS SDV follows Android's User ID (UID)-based isolation model to set up a sandbox for each application. Each service runs in a dedicated process with a unique UID to manage access rights, data directories, and other restrictions. We employ Portable Operating System Interface (POSIX) capabilities to strictly limit operations and pair this with Security-Enhanced Linux (SELinux) to enforce a "deny-by-default" posture. This approach restricts each service to the absolute minimum required, meaning missing configurations block access rather than creating an over-permissive system. We apply this same strategy to our communication permission system, as explained l ## Compiling to intermediate representation: Write yourself a compiler, Part III DevFeed: [Compiling to intermediate representation: Write yourself a compiler, Part III]() Original publisher: [Read original article]() Published: 2026-08-16T22:00:00Z Content type: tutorial Language: en Sources: [Tomasz Nurkiewicz around Java and concurrency]() Topics: [Compiler](), [virtual machines](), [Code](), [WebAssembly](), [Java]() Tags: [assembly](), [bytecode](), [compilation](), [compiler](), [go](), [interpreter](), [ir](), [javascript](), [python](), [virtual-machines](), [webassembly](), [writing-compiler]() ### AI overview This tutorial explains how a small interpreter project evolves into a compiler by emitting intermediate representation (IR). It contrasts interpreted and compiled languages, describes bytecode and virtual machines, and uses Java and WebAssembly examples to show how IR instructions are executed. ### Source excerpt It's time to dive a bit deeper and abandon the naive realm of interpreters. Our tiny little project can finally call itself a compiler. In this part we'll emit so-called intermediate representation instead of just evaluating and running the source code as-is. OK, what does this all mean? ## The Pulse: Bending Spoons' Acquisition Strategy DevFeed: [The Pulse: Bending Spoons' Acquisition Strategy]() Original publisher: [Read original article]() Author: Gergely Orosz Published: 2026-08-05T11:45:13Z Content type: opinion Language: en Sources: [The Pragmatic Engineer]() Topics: [migration](), [Architecture & Design](), [Microservices](), [Java](), [virtual machines](), [Cloud](), [Google Cloud Platform (GCP)](), [legacy application]() Tags: [architecture](), [backend](), [cloud](), [google-cloud](), [java](), [legacy](), [microservices](), [migration](), [performance](), [provisioning](), [virtual-machines]() ### AI overview The article examines Bending Spoons' acquisition strategy, including its announced $1.285 billion cash purchase of Airtable and its approach to operating struggling products with smaller teams. It also describes the company's reported modernization of Evernote from a Java 11 monolith running across 750 manually provisioned virtual machines on Google Cloud to a managed-database and microservices architecture in about six months, with reported improvements in performance, reliability, operating cost, and on-call load. ### Source excerpt In only 5 years, Hopin went from zero to a $7.7B valuation, and back to zero again. Also: Bending Spoons' startup acquisition model. ## The hyperscale blueprint: Why cloud giants prioritize VMs for Kubernetes over bare metal DevFeed: [The hyperscale blueprint: Why cloud giants prioritize VMs for Kubernetes over bare metal]() Original publisher: [Read original article]() Author: Jack Wallen Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [virtualization](), [Kubernetes](), [Containers](), [Scalability](), [Security](), [Amazon Web Services](), [Nitro System](), [Multi-tenancy]() Tags: [aws](), [containers](), [kubernetes](), [multi-tenancy](), [nitro-system](), [scalability](), [security](), [virtual-machines](), [virtualization]() ### AI overview Cloud providers generally run Kubernetes and other containerized workloads on virtual machines rather than bare metal because virtualization offers security, isolation, flexibility, scalability, and near-bare-metal performance. AWS Nitro and Firecracker help reduce virtualization overhead, while bare metal remains reserved for specialized performance or hardware-access requirements. ### Source excerpt Why do cloud giants use VMs for Kubernetes? Learn why AWS, Azure, and Google prioritize Virtual Machines for containerized workloads over bare metal, focusing on security and scalability. ## How platform engineering plus VMs ease modernization DevFeed: [How platform engineering plus VMs ease modernization]() Original publisher: [Read original article]() Author: Jennifer Riggins Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [Platform Engineering](), [virtualization](), [Containers](), [Cloud Native Ecosystem](), [Security](), [Scalability](), [Provisioning]() Tags: [architecture](), [cloud](), [cloud-native](), [containers](), [engineering](), [idp](), [infrastructure](), [operational](), [platform](), [platform-engineering](), [policy](), [provisioning](), [scalability](), [security](), [virtual-machines]() ### AI overview The article explains how combining containers in virtual machines with platform engineering and internal developer platforms can ease modernization. It argues that VMs provide stronger isolation, security boundaries, resource flexibility, and performance comparable to bare metal, while a policy-driven platform layer improves provisioning, utilization, compliance, and scalability. ### Source excerpt Explore why running containers in Virtual Machines (VMs) with a platform engineering strategy is essential for modern cloud environments. Learn how VMs deliver superior security, isolation, and resource management compared to bare metal, while achieving performance parity. ## Changing Interfaces Connected to netlab Links DevFeed: [Changing Interfaces Connected to netlab Links]() Original publisher: [Read original article]() Published: 2026-03-30T05:27:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [Containers](), [virtual machines](), [Cisco]() Tags: [cisco](), [containers](), [interfaces](), [netlab](), [network](), [node](), [virtual-machines]() ### AI overview This article explains how netlab uses interface ifindex values to connect virtual lab interfaces to specific links. It examines how interface names and mappings behave across Ethernet devices, containers, KVM virtual machines, vrnetlab, and Linux processes running in containers. ### Source excerpt Some netlab users want to accurately replicate their physical network's topology in a virtual lab. Ignoring the obvious caveats for a moment, the first hiccup is usually the interface naming. All bets are off if you're using anything but Ethernet in your actual network, but even if you did standardize on Ethernet, the container/VM interface names might not match the physical ones. netlab provided a solution for a long time - you can specify interface ifindex when attaching a node to a link. For example, use the following topology to connect Ethernet3 on R1 to Ethernet6 on R2: Read more ... ## BGP Labs: Goodbye, Cumulus Linux DevFeed: [BGP Labs: Goodbye, Cumulus Linux]() Original publisher: [Read original article]() Published: 2026-03-18T05:30:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [BGP](), [Containers](), [Linux](), [virtual machines]() Tags: [bgp](), [containers](), [end-of-life](), [linux](), [netlab](), [virtual-machines]() ### AI overview The author explains why the Online BGP Labs project moved away from Cumulus Linux. Problems included abandoned containers, crashes, a less suitable user interface after the NVIDIA acquisition, and discontinued or restricted Vagrant boxes. The author has now cleaned up more than 50 lab exercises, using FRRouting and Arista cEOS as alternatives. ### Source excerpt When I started the Online BGP Labs project in mid-2023, Cumulus Linux still seemed like a good platform to use. You could run devices as virtual machines (we were still supporting VirtualBox) or in containers (containerlab was improving with every release), and it looked more polished than bare-bones FRRouting. Things only went downhill from there (from the perspective of offering a free and easy-to-use solution with a CLI resembling commonly-used devices): Read more ... ## Keeping it boring: the incident.io technology stack DevFeed: [Keeping it boring: the incident.io technology stack]() Original publisher: [Read original article]() Author: Matthew Barrington Published: 2026-02-26T15:28:47Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [Cloud](), [Kubernetes](), [Containers](), [Google](), [cloud-infrastructure](), [configuration](), [observability](), [Processes]() Tags: [cloud](), [configuration](), [containers](), [customers](), [gcp](), [google-cloud](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [kubernetes](), [observability](), [outage](), [platform](), [post-mortem](), [processes](), [slack-incident](), [software](), [technology-stack](), [virtual-machines]() ### AI overview incident.io describes an intentionally simple technology stack built around managed Google Cloud services and a small platform team. Its default compute environment is GKE Autopilot, while workloads with long-lived processes or substantial storage or resource needs run on Google Compute Engine virtual machines. The article discusses the operational trade-offs of managed Kubernetes, including limitations around node lifetimes, system namespaces, and DNS configuration, and explains the use of Cloud Init for immutable, short-lived hosts. ### Source excerpt This is the story of how incident.io keeps its technology stack intentionally boring, scaling to thousands of customers with a lean platform team by relying on managed GCP services and a small set of well-chosen tools. ## Safe Yolo Mode: Running LLM Agents in VMs with Libvirt and Virsh DevFeed: [Safe Yolo Mode: Running LLM Agents in VMs with Libvirt and Virsh]() Original publisher: [Read original article]() Author: Chris Hager Published: 2026-02-10T00:00:00Z Content type: tutorial Language: en Sources: [Chris Hager]() Topics: [LLMs](), [virtualization](), [Security](), [Linux](), [qemu](), [ssh]() Tags: [linux](), [llm-agents](), [llms](), [security](), [tool-use](), [virtual-machines]() ### AI overview A guide to isolating LLM agents in Linux virtual machines with libvirt and virsh. It explains how VM isolation can reduce risks from destructive operations and unauthorized access when agents receive broad tool-use permissions, and covers setup, cloud-image provisioning, VM creation, and SSH access. ### Source excerpt This is a guide for isolating LLM agents in virtual machines, using libvirt and virsh on Linux servers. Running LLMs in VMs isolates them from the host system, mitigating numerous security risks such as destructive operations or unauthorized file access (i.e. private keys, secrets, credentials for communication tools). This is particularly important when granting LLM agents broad permissions, like auto-approving tool use ("yolo mode"). It's also useful to keep sessions running for extended periods of time, and to interact with agents from the phone / on the go. ## OCI Containers Come to Proxmox 9.1 - A First Look DevFeed: [OCI Containers Come to Proxmox 9.1 - A First Look]() Original publisher: [Read original article]() Author: Techno Tim Published: 2025-11-20T13:00:00Z Content type: article Language: en Sources: [Techno Tim]() Topics: [Proxmox](), [container images](), [Containers](), [hosting]() Tags: [container-images](), [containers](), [homelab](), [hosting](), [preview](), [proxmox](), [virtual-machines]() ### AI overview Proxmox 9.1 adds tech-preview support for OCI container images. The article explains how Proxmox pulls images from registries, stores them as templates, and runs them inside LXC wrappers with LXC-based networking and resource allocation. A Grafana image is shown launching successfully in this setup. ### Source excerpt Proxmox 9.1 introduces support for OCI container images, bringing Docker-style workloads into the Proxmox ecosystem for the first time. It's still a tech preview, but it's a promising step toward more flexible application hosting inside Proxmox. Watch the video Why OCI Support Matters Until now, Proxmox has traditionally focused on virtual machines and LXC containers. Both are powerful, ... ## ansible-k3s-on-vms updated to Debian 13 (Trixie) DevFeed: [ansible-k3s-on-vms updated to Debian 13 (Trixie)]() Original publisher: [Read original article]() Author: Staf Wagemakers Published: 2025-11-13T04:30:00Z Content type: release Language: en Sources: [stafwag Blog]() Topics: [Ansible](), [k3s](), [Debian](), [Raspberry Pi](), [virtual machines](), [Cloud]() Tags: [ansible](), [changelog](), [cloud](), [cloudinit](), [cluster](), [debian](), [debugging](), [k3s](), [kubernetes](), [linux](), [pi](), [pi-4](), [release](), [virtual-machines]() ### AI overview The article announces updated Ansible roles for provisioning virtual machines and deploying k3s on a Raspberry Pi 4 cluster. The roles were updated for Debian 13 Trixie and include new templates, examples, and fixes across several roles. ### Source excerpt I use the lightweight Kubernetes K3s on a 3-node Raspberry Pi 4 cluster. And created a few ansible roles to provision the virtual machines with cloud image with cloud-init and deploy k3s on it. I updated the roles below to be compatible with the latest Debian release: Debian 13 Trixie. With this release comes a new movie ;-) ## Solving virtual machine puzzles: How AI is optimizing cloud computing DevFeed: [Solving virtual machine puzzles: How AI is optimizing cloud computing]() Original publisher: [Read original article]() Published: 2025-10-17T17:56:35Z Content type: article Language: en Sources: [The latest research from Google]() Topics: [Artificial Intelligence](), [cloud-computing](), [Algorithms & Theory](), [data centers](), [servers](), [Provisioning]() Tags: [2025](), [ai](), [algorithms](), [algorithms-theory](), [cloud](), [cloud-computing](), [distributed-systems-parallel-computing](), [efficiency](), [google](), [packing](), [provisioning](), [research](), [resource](), [scale](), [server](), [servers](), [software-systems-engineering](), [virtual-machines]() ### AI overview Google Research presents LAVA, a scheduling system that uses AI models to continuously predict and adapt to virtual machine lifetimes. Its NILAS, LAVA, and LARS algorithms improve VM allocation and rescheduling in large cloud data centers, reducing stranded resources and improving server efficiency. ### Source excerpt Algorithms & Theory ## Announcing per-sec billing, new Droplet plans, BYOIP, and NAT gateway to reduce scaling costs DevFeed: [Announcing per-sec billing, new Droplet plans, BYOIP, and NAT gateway to reduce scaling costs]() Original publisher: [Read original article]() Author: Nihar Namjoshi Published: 2025-10-02T08:03:13Z Content type: release Language: en Sources: [DigitalOcean]() Topics: [Digital Ocean](), [Cloud](), [cloud-infrastructure](), [virtual machines](), [VPC](), [CI/CD]() Tags: [ci-cd](), [cloud](), [cloud-infrastructure](), [digitalocean](), [droplets](), [network](), [product-updates](), [virtual-machines](), [vpc]() ### AI overview DigitalOcean announces per-second billing for Droplets, new dedicated Droplet plans, generally available BYOIP, and a VPC NAT Gateway. The updates target more precise cost control, performance upgrades, IP reputation protection, and centralized egress management. ### Source excerpt To help users cut down on cloud spending that's wasted due to over-provisioning and inflexible billing models, we're introducing tools that offer granular control without sacrificing simplicity or cost-effectiveness. We're excited to announce new product updates that offer granular cost control, improved performance, and a clear path to savings. TL;DR DigitalOcean has transitioned to per-second billing for Droplets. Starting from January 1, 2026, you only pay for the exact compute time you use, perfect for slashing costs on ephemeral tasks and CI/CD pipelines. Create Droplets for short-lived workloads. New dedicated Droplet plans are now generally available for a seamless performance upgrade. Visit your DigitalOcean console to create these new Droplets. Bring your own IP is now generally available to protect your IP reputation. Check out our documentation or visit your DigitalOcean console to bring your own ip. VPC NAT gateway is now generally available for centralized egress and static IPs. Join our webinar: Stop the manual struggle of managing NAT instances and bastion hosts or check out our documentation or visit your DigitalOcean console to set up your NAT gateway. Droplets per-second billing slashes costs for ephemeral workloads Traditional hourly billing models for virtual machines have resulted in customers paying for idle time, even for short-lived workloads. Starting from Jan 1, 2026, our billing model transitioned to a per-second basis for Droplets, with a minimum charge of 60 seconds or $0.01, whichever is higher. This new approach aims to optimize cost control by charging for exact usage over a minute, making it simple to get precise billing for your actual usage. For sustained workloads, the monthly cap of 672 hours (24 hours x 28 days) of usage remains in place, ensuring your bill never exceeds the predictable monthly price. Imagine your development team uses a CI/CD pipeline that uses $84/month CPU-Optimized Droplet to run automated tests taking 10 mi ## Arista EOS Hates a Routing Instance with No Interfaces DevFeed: [Arista EOS Hates a Routing Instance with No Interfaces]() Original publisher: [Read original article]() Published: 2025-09-18T05:20:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [BGP](), [bug](), [debug](), [Ansible](), [IP routing](), [Containers](), [virtual machines]() Tags: [ansible](), [bgp](), [bug](), [containers](), [debug](), [ip-routing](), [netlab](), [virtual-machines]() ### AI overview A debugging investigation finds that Arista EOS fails to configure BGP and enable IP routing when the default VRF has no interfaces. The issue occurs in container and virtual-machine deployments across multiple EOS releases, while the error message is misleading. ### Source excerpt I always ask engineers reporting a netlab bug to provide a minimal lab topology that would reproduce the error, sometimes resulting in "interesting" side effects. For example, I was trying to debug a BGP-related Arista EOS issue using a netlab topology similar to this one: defaults.device: eos module: [ bgp ] nodes: a: { bgp.as: 65000 } b: { bgp.as: 65001 } Imagine my astonishment when the two switches failed to configure BGP. Here's the error message I got when running the netlab's deploy device configurations Ansible playbook: Read more ... ## QEMU version 10.1.0 released DevFeed: [QEMU version 10.1.0 released]() Original publisher: [Read original article]() Published: 2025-08-26T23:25:00Z Content type: release Language: en Sources: [QEMU]() Topics: [qemu](), [version](), [virtualization](), [virtual machines](), [RISC-V](), [cpu](), [Kernel](), [Arm](), [InfiniBand](), [intel](), [GB200]() Tags: [arm](), [cxl](), [gb200](), [intel](), [ipv6](), [kernel](), [kvm](), [migration](), [qemu](), [qemu-10-1](), [rdma](), [release](), [releases](), [risc-v](), [version](), [virtual-machines](), [virtualization](), [x86]() ### AI overview QEMU 10.1.0 has been released with more than 2,700 commits from 226 authors. Highlights include confidential-guest support, live-migration improvements, Windows guest load querying, new ARM and RISC-V capabilities, and expanded KVM and x86 virtualization support. ### Source excerpt We'd like to announce the availability of the QEMU 10.1.0 release. This release contains 2700+ commits from 226 authors. ## Network Digital Twins: Between PowerPoint and Reality DevFeed: [Network Digital Twins: Between PowerPoint and Reality]() Original publisher: [Read original article]() Published: 2025-06-19T07:16:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Network](), [networking](), [virtual machines](), [virtualization](), [Hardware](), [cpu]() Tags: [automation](), [cpu](), [examples](), [hardware](), [network](), [networking](), [virtual-machines](), [virtualization]() ### AI overview The article discusses why networking digital twins have struggled to move beyond demonstrations. It identifies limitations involving supported interface technologies, interface-name mapping, chassis and line-card modeling, interface counts, resource requirements, clustered deployment, and the fidelity of virtual data-plane behavior. ### Source excerpt A Network Artist left an interesting remark on one of my blog posts: It's kind of confusing sometimes to see the digital twin (being a really good idea) never really take off. His remark prompted me to resurface a two-year-old draft listing a bunch of minor annoyances that make Networking Digital Twins more of a PowerPoint project than a reality. Read more ... ## ArubaCX VXLAN Routing Packets Have Invalid Lengths DevFeed: [ArubaCX VXLAN Routing Packets Have Invalid Lengths]() Original publisher: [Read original article]() Published: 2025-06-12T05:08:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [VXLAN](), [networking](), [Linux](), [virtual machines]() Tags: [capture](), [ethernet](), [linux](), [netlab](), [tailscale](), [virtual-machines](), [vxlan]() ### AI overview A netlab IRB test exposed that VXLAN packets generated by ArubaCX's routing process reported IP and UDP lengths four bytes larger than the actual packet. The article uses packet captures to trace the issue to a VLAN tag removed during software VXLAN encapsulation without a corresponding length adjustment. ### Source excerpt This blog post describes yet another bizarre example of how reliable digital twins are, but don't worry; they all work great in PowerPoint. After "fixing" the integration tests to deal with ArubaCX's notion of VXLAN VNI having 16 bits, the bridging test worked, but the IRB tests kept failing. In the IRB test, the lab has two layer-3 switches. Each of them should be able to bridge within a VLAN/VXLAN segment and route across the segments. Read more ... [Next page]()