close
keyboard_arrow_left
Table of Contents
- play_arrow vMX Overview
- play_arrow Installing and Deploying vMX on KVM
- play_arrow Configuring Modified and Unmodified Drivers
- play_arrow Configuring vMX Chassis-Level Features
- play_arrow Class of Service for vMX
- CoS on vMX Overview
- CoS Features and Limitations on vMX
- Configuring Four-Level Hierarchical Scheduling on vMX
- Packet Loss Priority and Drop Profiles on vMX
- Managing Congestion Using Drop Profiles and Packet Loss Priorities on vMX
- Configuring Hierarchical CoS on vMX
- Example: Configuring Hierarchical CoS on vMX
- Bypassing the Queuing Chip
list Table of Contents
Verifying Whether VMs Are Running
date_range
19-Nov-20
To verify that the VMs are running after vMX is installed, use
the virsh list command. The virsh list command
displays the name and state of the VM. The state can be: running,
idle, paused, shutdown, crashed, or dying.
You can stop and start VMs with the following virsh commands.
virsh destroy—Forcefully stop a VM while leaving its resources intact.virsh start—Start an inactive VM that was defined previously.
