troubleshoot-virt

Diagnose and resolve stuck VMs, DataVolumes, and migrations in OpenShift Virtualization.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/yaacov/forklift-skills --skill troubleshoot-virt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshoot-virt
Source: https://github.com/yaacov/forklift-skills/tree/main/skills/troubleshoot-virt
Command: npx skills add https://github.com/yaacov/forklift-skills --skill troubleshoot-virt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Troubleshoot stuck VMs and migrations in OpenShift Virtualization and MTV/Forklift. Use when VMs won't start, DataVolumes are stuck, migrations fail, or cluster resources are exhausted.

Core Features & Use Cases

  • End-to-end triage covering node resources, storage/provisioning, DataVolumes, and VM/VMI status to identify root causes.
  • Guidance for diagnosing and remediating common stuck scenarios including unschedulable VMs, stalled DataVolumes, and failed migrations.
  • Cross-component checks for MT/Forklift health, CDI importer/cloner pods, and KubeVirt operator status to inform targeted fixes.

Quick Start

Begin triage by checking node resources, storage classes, DataVolumes, PVCs, VM/VMI status, and migration health, then apply the recommended fixes based on observed conditions.

Frequently Asked Questions about troubleshoot-virt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why are my OpenShift Virtualization VMs failing to start or stuck in a stalled state?

VMs stall due to insufficient node resources, storage provisioning failures, or DataVolume issues. Diagnose the problem by inspecting VM/VMI status, checking node capacity, and reviewing KubeVirt operator health to pinpoint the root cause.

How do I troubleshoot stuck DataVolumes in OpenShift Virtualization?

Troubleshoot stuck DataVolumes by examining CDI importer and cloner pods, verifying storage class configuration, and reviewing PVC status. Cross-component checks identify provisioning bottlenecks and inform targeted remediation steps.

What's the best way to diagnose failed VM migrations in MTV Forklift?

Diagnose failed migrations by checking MTV/Forklift health, inspecting per-VM migration pods, and reviewing cluster events. End-to-end triage covers node resources and VM status to resolve migration failures.

Do I need kubectl to troubleshoot KubeVirt migration issues?

Yes, kubectl is required to inspect resources, describe pods, and review logs. MTV/Forklift tooling and standard cluster diagnostics are also necessary to examine VMI status and implement remediation steps.

How do I resolve unschedulable VMs in OpenShift Virtualization?

Resolve unschedulable VMs by checking node resources, reviewing storage classes, and inspecting VM/VMI status. Cross-component checks identify scheduling constraints and inform targeted fixes for resource exhaustion.

Can I use this to troubleshoot CDI importer pods when DataVolumes are stuck?

Yes, this includes cross-component checks for CDI importer and cloner pods. Inspecting these alongside KubeVirt operator status helps identify storage provisioning issues and resolve stalled DataVolumes.