Nested virtualization: kvm panic under CentOS

Discussion in 'Linux Virtual Machine' started by Ed_18, Jan 30, 2026 at 12:38 PM.

  1. Ed_18

    Ed_18

    Messages:
    1
    MacOS: 15.7.3 Intel
    Guest: CentOS Stream 9
    Parallels: 26 Pro
    Context: I am attempting to run RedHat OpenShift (kubernetes) under CentOS guest. When I start the container is starting, the kernel panics. Here is the last message before forced restart:
    Code:
    Jan 30 00:35:52 localhost systemd[1]: Starting libvirt logging daemon...
    Jan 30 00:35:53 localhost systemd[1]: Started libvirt logging daemon.
    Jan 30 00:35:53 localhost systemd-machined[849]: New machine qemu-1-crc.
    Jan 30 00:35:53 localhost systemd[1]: Started Virtual Machine qemu-1-crc.
    Jan 30 00:35:53 localhost virtqemud[8964]: 2026-01-30 05:35:53.068+0000: 8964: info : libvirt version: 11.10.0, package: 2.el9 (builder@centos.org, 2025-12-18-15:09:54, )
    Jan 30 00:35:53 localhost virtqemud[8964]: 2026-01-30 05:35:53.068+0000: 8964: info : hostname: localhost.localdomain
    Jan 30 00:35:53 localhost virtqemud[8964]: 2026-01-30 05:35:53.068+0000: 8964: warning : virSecurityValidateTimestamp:205 : Invalid XATTR timestamp detected on /home/parallels/.crc/machines/crc/crc.qcow2 secdriver=dac
    Jan 30 00:35:53 localhost virtqemud[8964]: 2026-01-30 05:35:53.069+0000: 8964: warning : virSecurityValidateTimestamp:205 : Invalid XATTR timestamp detected on /var/lib/libvirt/qemu/nvram/crc_VARS.fd secdriver=dac
    Jan 30 00:35:53 localhost kernel: kvm: vmwrite failed: field=2018 val=0 err=12
    
    Nested virtualization is set on the CPUs, Parallels hypervisor.
    upload_2026-1-30_14-13-0.png

    CPU flags seem to get passed down from Parallels...
    Code:
    [root@localhost ~]# cat /sys/module/kvm_intel/parameters/nested
    Y
    
    [root@localhost ~]# dmesg | grep -i "Hypervisor detected"
    [    0.000000] Hypervisor detected: KVM
    
     

Share This Page