Tech News
← Home  ·  All topics

Hypervisor

4 GoKawiil briefs on this topic

Survey: 60% of VMware customers weigh multi-hypervisor strategies to cut costs

A Rimini Street survey of 300 VMware-using organizations found 60% are considering a multi-hypervisor approach, while 47% favor combining hypervisors and containers to choose where workloads run. Respondents cited operational complexity (40%), multi-vendor management (38%), expanded attack surface and staff skills gaps (each 37%) as the main barriers to making such changes.

Developer boots early Linux on Apple's M4 Mac mini

A hobbyist developer documented progress toward running Linux on Apple's M4 Mac mini, building on work by the Asahi Linux project. The effort required disabling macOS boot security, loading the m1n1 bootloader, and working around the new SPTM hardware security layer that blocks the usual MMIO-tracing approach used for earlier Apple Silicon chips.

postmarketOS developer traces ARM64 hypervisor crash to NX bit page permissions, not security bug

A developer building a bare-metal ARM64 hypervisor for postmarketOS ran into random system lockups whenever the CTR_EL0 register trap was enabled, forcing a watchdog reset within seconds. After ruling out register corruption in the exception handler and stack setup, the investigation eventually traced the fault to how executable-page protections (the NX bit) interacted with the trap handling, rather than any obvious logic error in the emulated instruction handling.

Multikernel Technologies releases mklinux v7.0-mk2, running several Linux kernels on one server

Multikernel Technologies has published the first public version of its multikernel Linux tree, mklinux v7.0-mk2, which lets one physical machine run multiple independent Linux kernels simultaneously, each with dedicated CPU and memory allocations. A host kernel manages hardware assignment via device tree overlays and boots new kernel instances directly onto hardware using kexec, bypassing any hypervisor layer. The initial release supports only x86_64 systems, though the company says the architecture-specific code is built to allow future ports.