7cd7022f6e
- Added lock file exclusions for pnpm in .gitignore. - Removed obsolete package-lock.json from the api and portal directories. - Enhanced Cloudflare adapter with additional interfaces for zones and tunnels. - Improved Proxmox adapter error handling and logging for API requests. - Updated Proxmox VM parameters with validation rules in the API schema. - Enhanced documentation for Proxmox VM specifications and examples.
129 lines
3.2 KiB
Markdown
129 lines
3.2 KiB
Markdown
# VM 100 Current Status
|
|
|
|
**Date**: 2025-12-11
|
|
**Node**: ml110-01 (192.168.11.10)
|
|
|
|
---
|
|
|
|
## Current Status
|
|
|
|
### ✅ Working
|
|
- **VM Status**: Running
|
|
- **Guest Agent (Proxmox)**: Enabled (`agent: 1`)
|
|
- **CPU**: 2 cores
|
|
- **Memory**: 4096 MB (4 GiB)
|
|
|
|
### ❌ Issues
|
|
- **Guest Agent (OS)**: NOT installed/running inside VM
|
|
- **Network Access**: Cannot determine IP (not in ARP table)
|
|
- **Guest Commands**: Cannot execute via `qm guest exec` (requires working guest agent)
|
|
|
|
---
|
|
|
|
## Problem
|
|
|
|
The guest agent is **configured in Proxmox** (`agent: 1`), but the **package and service are not installed/running inside the VM**. This means:
|
|
|
|
1. ✅ Proxmox can attempt to communicate with the VM
|
|
2. ❌ The VM cannot respond because `qemu-guest-agent` package is missing
|
|
3. ❌ `qm guest exec` commands fail with "No QEMU guest agent configured"
|
|
|
|
---
|
|
|
|
## Solution Options
|
|
|
|
### Option 1: Install via Proxmox Web Console (Recommended)
|
|
|
|
1. **Access Proxmox Web UI**: `https://192.168.11.10:8006`
|
|
2. **Navigate to**: VM 100 → Console
|
|
3. **Login** to the VM (use admin user or root)
|
|
4. **Run installation commands**:
|
|
```bash
|
|
sudo apt-get update
|
|
sudo apt-get install -y qemu-guest-agent
|
|
sudo systemctl enable qemu-guest-agent
|
|
sudo systemctl start qemu-guest-agent
|
|
sudo systemctl status qemu-guest-agent
|
|
```
|
|
|
|
### Option 2: Install via SSH (if network access available)
|
|
|
|
1. **Find VM IP** (if possible):
|
|
```bash
|
|
# On Proxmox node
|
|
qm config 100 | grep net0
|
|
# Or check ARP table for VM MAC address
|
|
```
|
|
|
|
2. **SSH to VM**:
|
|
```bash
|
|
ssh admin@<VM_IP>
|
|
```
|
|
|
|
3. **Run installation commands** (same as Option 1)
|
|
|
|
### Option 3: Restart VM (if cloud-init should install it)
|
|
|
|
If VM 100 was created with a template that includes `qemu-guest-agent` in cloud-init, a restart might trigger installation:
|
|
|
|
```bash
|
|
# On Proxmox node
|
|
qm shutdown 100 # Graceful shutdown (may fail without guest agent)
|
|
# OR
|
|
qm stop 100 # Force stop
|
|
qm start 100 # Start VM
|
|
```
|
|
|
|
**Note**: This only works if the VM was created with cloud-init that includes the guest agent package.
|
|
|
|
---
|
|
|
|
## Verification
|
|
|
|
After installation, verify the guest agent is working:
|
|
|
|
```bash
|
|
# On Proxmox node
|
|
qm guest exec 100 -- systemctl status qemu-guest-agent
|
|
```
|
|
|
|
Or run the comprehensive check script:
|
|
|
|
```bash
|
|
# On Proxmox node
|
|
/usr/local/bin/complete-vm-100-guest-agent-check.sh
|
|
```
|
|
|
|
---
|
|
|
|
## Expected Results After Fix
|
|
|
|
- ✅ `qm guest exec 100 -- <command>` should work
|
|
- ✅ `qm guest exec 100 -- systemctl status qemu-guest-agent` should show running
|
|
- ✅ `qm guest exec 100 -- dpkg -l | grep qemu-guest-agent` should show installed package
|
|
- ✅ Graceful shutdown (`qm shutdown 100`) should work
|
|
|
|
---
|
|
|
|
## Root Cause
|
|
|
|
VM 100 was likely created:
|
|
1. **Before** the enhanced templates with guest agent were available, OR
|
|
2. **Without** cloud-init configuration that includes `qemu-guest-agent`, OR
|
|
3. **Cloud-init** didn't complete successfully during initial boot
|
|
|
|
---
|
|
|
|
## Prevention
|
|
|
|
For future VMs:
|
|
- ✅ Use templates from `examples/production/` which include guest agent
|
|
- ✅ Verify cloud-init completes successfully
|
|
- ✅ Check guest agent status after VM creation
|
|
|
|
---
|
|
|
|
**Last Updated**: 2025-12-11
|
|
**Status**: ⚠️ **GUEST AGENT NEEDS INSTALLATION IN VM**
|
|
|