Frequently Asked Questions about KVM MCP Server

Q: What is a KVM MCP Server?

A: The KVM MCP Server is a JSON-RPC server that simplifies the management of KVM virtual machines. It provides a centralized and intuitive interface for controlling and monitoring your VMs.

Q: Why should I use a KVM MCP Server?

A: It simplifies VM management by providing a unified interface, enables remote control, automates VM operations, standardizes VM configuration, and optimizes performance.

Q: What are the key features of the KVM MCP Server?

A: Key features include VM lifecycle management, network management, storage management, display management, installation support, and performance optimizations like connection pooling and caching.

Q: What is JSON-RPC?

A: JSON-RPC is a simple remote procedure call protocol encoded in JSON. It allows you to execute functions on a remote server by sending JSON requests.

Q: What performance benefits does the KVM MCP Server offer?

A: It offers performance benefits such as reduced latency, resource efficiency, improved concurrency, and better resource utilization through connection pooling, caching, and asynchronous processing.

Q: How do I configure the KVM MCP Server?

A: The server uses a JSON configuration file (config.json) to store default values and paths. You can modify this file to match your environment’s requirements.

Q: What are the prerequisites for installing the KVM MCP Server?

A: Prerequisites include Python 3.6 or higher, KVM and libvirt installed on the host system, a configured network bridge (default: brforvms), a VM storage directory (default: /vm/), and sufficient system resources for your VM workload.

Q: How do I install the KVM MCP Server?

A: To install the server, clone the repository, create and activate a virtual environment, and install the dependencies using pip install -r requirements.txt.

Q: How do I start the KVM MCP Server?

A: Start the server by running the command python3 kvm_mcp_server.py in your terminal.

Q: How do I send commands to the KVM MCP Server?

A: You can send commands to the server using JSON-RPC. Example scripts are provided for creating VMs and finding VNC ports.

Q: What are the default login details for Fedora CoreOS VMs?

A: By default, the KVM MCP Server configures Fedora CoreOS VMs with the username core and no password. An SSH key can be added by configuring the VM_IGNITION_DEFAULT_SSH_KEY environment variable to the path of the SSH public key you want to use for the user. Ensure SSH key is present in your system, before you configuring it. You can also set a password by configuring the VM_IGNITION_DEFAULT_PASSWORD_HASH environment variable.

Q: How do I monitor and troubleshoot the KVM MCP Server?

A: You can monitor the server using log files, performance metrics, and by tracking common issues and solutions.

Q: Where are the log files located?

A: The log files are located at kvm_mcp.log (current log file) and kvm_mcp.log.1 (previous log file).

Q: What should I do if I encounter connection pool exhaustion?

A: If you experience slow response times or connection errors, increase the max_connections in the connection pool configuration.

Q: What should I do if I encounter cache invalidation issues?

A: If you encounter stale VM information, use the no_cache parameter or reduce the cache TTL.

Q: How does the KVM MCP Server support Fedora CoreOS?

A: The KVM MCP Server supports Fedora CoreOS through Ignition configuration, allowing you to customize hostname, user, SSH key, timezone, and locale.

Q: What is UBOS, and how does it relate to the KVM MCP Server?

A: UBOS is a full-stack AI Agent Development Platform. The KVM MCP Server integrates with UBOS, enabling you to orchestrate AI Agents, connect them with enterprise data, build custom AI Agents, and create Multi-Agent Systems.

Q: How can I contribute to the KVM MCP Server project?

A: Contributions are welcome! Please feel free to submit a Pull Request on the project’s GitHub repository.