install-windows-3-11

Install Windows 3.11 in QEMU with VNC and noVNC remote access.

134|21|Updated Nov 12, 2025
One-click install
npx skills add https://github.com/letta-ai/skills --skill install-windows-3-11
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: install-windows-3-11
Source: https://github.com/letta-ai/skills/tree/main/ai/benchmarks/letta/terminal-bench-2/trajectory-only/install-windows-3.11
Command: npx skills add https://github.com/letta-ai/skills --skill install-windows-3-11

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides guidance for running legacy Windows 3.11 in QEMU and exposing it via a web-based remote interface (noVNC), including QMP control and nginx proxy configuration.

Core Features & Use Cases

  • Phase-based VM setup, boot verification, and QMP access
  • nginx reverse proxy configuration for noVNC
  • Websockify integration for WebSocket-based VNC
  • Keyboard/mouse input automation guidance

Quick Start

Launch Windows 3.11 in QEMU with noVNC, configure the nginx proxy, and verify remote access via a browser.

Frequently Asked Questions about install-windows-3-11

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

FAQPage Schema
How do I install Windows 3.11 in QEMU with remote web access?

Install Windows 3.11 in QEMU by configuring disk images, memory, and VGA adapters, then expose it via noVNC through a websockify bridge and nginx reverse proxy for browser-based remote access.

What's the difference between VNC and noVNC for accessing a QEMU VM?

VNC requires a dedicated client application, while noVNC runs in a web browser. Websockify converts VNC's socket protocol to WebSocket, allowing nginx to proxy noVNC through HTTP.

How do I configure nginx to proxy noVNC for a QEMU Windows 3.11 VM?

Set up an nginx reverse proxy pointing to your websockify instance, which bridges WebSocket connections to the QEMU VM's VNC socket, enabling secure web-based console access.

What QEMU parameters do I need for Windows 3.11 VNC and QMP setup?

Configure QEMU with disk image path, memory allocation, VGA adapter type, VNC socket specification, and QMP socket path for remote monitoring and control of the legacy Windows environment.

Can I use QMP to monitor and control Windows 3.11 running in QEMU?

Yes, QMP (QEMU Machine Protocol) lets you negotiate capabilities and send commands to the running VM through a socket interface for administrative monitoring and control.

How do I verify that Windows 3.11 booted correctly in QEMU with remote access?

Run process checks on QEMU and websockify, verify QMP capability negotiation, test VNC connectivity, and confirm visual boot output through the noVNC web interface.