virtui-manager 1.1.5__tar.gz → 1.1.6__tar.gz

{virtui_manager-1.1.5/src/virtui_manager.egg-info → virtui_manager-1.1.6}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: virtui-manager
-Version: 1.1.5
+Version: 1.1.6
 Summary: Terminal-based interface to manage virtual machines using libvirt
 Home-page: https://aginies.github.io/virtui-manager/
 Author: Antoine Ginies

{virtui_manager-1.1.5 → virtui_manager-1.1.6}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "virtui-manager"
-version = "1.1.5"
+version = "1.1.6"
 description = "Terminal-based interface to manage virtual machines using libvirt"
 readme = "README.md"
 authors = [

{virtui_manager-1.1.5 → virtui_manager-1.1.6}/setup.cfg

@@ -1,6 +1,6 @@
 [metadata]
 name = virtui-manager
-version = 1.1.5
+version = 1.1.6
 description = Terminal-based interface to manage virtual machines using libvirt
 long_description = file: README.md
 long_description_content_type = text/markdown

{virtui_manager-1.1.5 → virtui_manager-1.1.6/src/virtui_manager.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: virtui-manager
-Version: 1.1.5
+Version: 1.1.6
 Summary: Terminal-based interface to manage virtual machines using libvirt
 Home-page: https://aginies.github.io/virtui-manager/
 Author: Antoine Ginies

{virtui_manager-1.1.5 → virtui_manager-1.1.6}/src/virtui_manager.egg-info/SOURCES.txt

@@ -1,4 +1,3 @@
-FEATURES.md
 LICENSE
 MANIFEST.in
 README.md

{virtui_manager-1.1.5 → virtui_manager-1.1.6}/src/vmanager/constants.py

@@ -37,7 +37,7 @@ class AppInfo:
     """Define app data"""
     name = "virtui-manager"
     namecase = "VirtUI Manager"
-    version = "1.1.5"
+    version = "1.1.6"
 
 class VmAction:
     """Defines constants for VM action types."""

virtui_manager-1.1.6/src/vmanager/modals/howto_disk_modal.py

@@ -0,0 +1,33 @@
+"""
+Modal to show how to manage VM disks.
+"""
+import os
+from pathlib import Path
+from textual.app import ComposeResult
+from textual.containers import Vertical, Horizontal, ScrollableContainer
+from textual.widgets import Button, Markdown
+from textual import on
+from .base_modals import BaseModal
+
+class HowToDiskModal(BaseModal[None]):
+    """A modal to display instructions for managing VM disks."""
+
+    def compose(self) -> ComposeResult:
+        # Load markdown from external file
+        docs_path = Path(__file__).parent.parent / "appdocs" / "howto_disk.md"
+        try:
+            with open(docs_path, "r") as f:
+                content = f.read()
+        except FileNotFoundError:
+            content = "# Error: Documentation file not found."
+
+        with Vertical(id="howto-disk-dialog"):
+            with ScrollableContainer(id="howto-disk-content"):
+                yield Markdown(content, id="howto-disk-markdown")
+        with Horizontal(id="dialog-buttons"):
+            yield Button("Close", id="close-btn", variant="primary")
+
+    @on(Button.Pressed)
+    def on_button_pressed(self, event: Button.Pressed) -> None:
+        """Handle button presses."""
+        self.dismiss()

virtui_manager-1.1.6/src/vmanager/modals/howto_network_modal.py

@@ -0,0 +1,33 @@
+"""
+Modal to show how to configure networks.
+"""
+import os
+from pathlib import Path
+from textual.app import ComposeResult
+from textual.containers import Vertical, Horizontal, ScrollableContainer
+from textual.widgets import Button, Markdown
+from textual import on
+from .base_modals import BaseModal
+
+class HowToNetworkModal(BaseModal[None]):
+    """A modal to display instructions for network configuration."""
+
+    def compose(self) -> ComposeResult:
+        # Load markdown from external file
+        docs_path = Path(__file__).parent.parent / "appdocs" / "howto_network.md"
+        try:
+            with open(docs_path, "r") as f:
+                content = f.read()
+        except FileNotFoundError:
+            content = "# Error: Documentation file not found."
+
+        with Vertical(id="howto-network-dialog"):
+            with ScrollableContainer(id="howto-network-content"):
+                yield Markdown(content, id="howto-network-markdown")
+        with Horizontal(id="dialog-buttons"):
+            yield Button("Close", id="close-btn", variant="primary")
+
+    @on(Button.Pressed)
+    def on_button_pressed(self, event: Button.Pressed) -> None:
+        """Handle button presses."""
+        self.dismiss()

virtui_manager-1.1.6/src/vmanager/modals/howto_overlay_modal.py

@@ -0,0 +1,33 @@
+"""
+Modal to show how overlay disks work.
+"""
+import os
+from pathlib import Path
+from textual.app import ComposeResult
+from textual.containers import Vertical, Horizontal, ScrollableContainer
+from textual.widgets import Button, Markdown
+from textual import on
+from .base_modals import BaseModal
+
+class HowToOverlayModal(BaseModal[None]):
+    """A modal to display instructions for disk overlays."""
+
+    def compose(self) -> ComposeResult:
+        # Load markdown from external file
+        docs_path = Path(__file__).parent.parent / "appdocs" / "howto_overlay.md"
+        try:
+            with open(docs_path, "r") as f:
+                content = f.read()
+        except FileNotFoundError:
+            content = "# Error: Documentation file not found."
+
+        with Vertical(id="howto-overlay-dialog", classes="howto-dialog"):
+            with ScrollableContainer(id="howto-overlay-content"):
+                yield Markdown(content, id="howto-overlay-markdown")
+        with Horizontal(id="dialog-buttons"):
+            yield Button("Close", id="close-btn", variant="primary")
+
+    @on(Button.Pressed)
+    def on_button_pressed(self, event: Button.Pressed) -> None:
+        """Handle button presses."""
+        self.dismiss()

virtui_manager-1.1.6/src/vmanager/modals/howto_ssh_modal.py

@@ -0,0 +1,32 @@
+"""
+Modal to show how to use ssh-agent.
+"""
+from pathlib import Path
+from textual.app import ComposeResult
+from textual.containers import Vertical, Horizontal, ScrollableContainer
+from textual.widgets import Button, Markdown
+from textual import on
+from .base_modals import BaseModal
+
+class HowToSSHModal(BaseModal[None]):
+    """A modal to display instructions for using an ssh-agent."""
+
+    def compose(self) -> ComposeResult:
+        # Load markdown from external file
+        docs_path = Path(__file__).parent.parent / "appdocs" / "howto_ssh.md"
+        try:
+            with open(docs_path, "r") as f:
+                content = f.read()
+        except FileNotFoundError:
+            content = "# Error: Documentation file not found."
+
+        with Vertical(id="howto-ssh-dialog"):
+            with ScrollableContainer(id="howto-ssh-content"):
+                yield Markdown(content, id="howto-ssh-markdown")
+        with Horizontal(id="dialog-buttons"):
+            yield Button("Close", id="close-btn", variant="primary")
+
+    @on(Button.Pressed)
+    def on_button_pressed(self, event: Button.Pressed) -> None:
+        """Handle button presses."""
+        self.dismiss()

virtui_manager-1.1.6/src/vmanager/modals/howto_virtiofs_modal.py

@@ -0,0 +1,33 @@
+"""
+Modal to show how to use VirtIO-FS.
+"""
+import os
+from pathlib import Path
+from textual.app import ComposeResult
+from textual.containers import Vertical, Horizontal, ScrollableContainer
+from textual.widgets import Button, Markdown
+from textual import on
+from .base_modals import BaseModal
+
+class HowToVirtIOFSModal(BaseModal[None]):
+    """A modal to display instructions for using VirtIO-FS."""
+
+    def compose(self) -> ComposeResult:
+        # Load markdown from external file
+        docs_path = Path(__file__).parent.parent / "appdocs" / "howto_virtiofs.md"
+        try:
+            with open(docs_path, "r") as f:
+                content = f.read()
+        except FileNotFoundError:
+            content = "# Error: Documentation file not found."
+
+        with Vertical(id="howto-virtiofs-dialog"):
+            with ScrollableContainer(id="howto-virtiofs-content"):
+                yield Markdown(content, id="howto-virtiofs-markdown")
+        with Horizontal(id="dialog-buttons"):
+            yield Button("Close", id="close-btn", variant="primary")
+
+    @on(Button.Pressed)
+    def on_button_pressed(self, event: Button.Pressed) -> None:
+        """Handle button presses."""
+        self.dismiss()

{virtui_manager-1.1.5 → virtui_manager-1.1.6}/src/vmanager/modals/server_prefs_modals.py

@@ -248,20 +248,28 @@ class ServerPrefModal(BaseModal[None]):
         pools = storage_manager.list_storage_pools(self.conn)
         node_to_select = None
         for pool_data in pools:
-            pool_name = pool_data['name']
-            status = pool_data['status']
-            autostart = "autostart" if pool_data['autostart'] else "no autostart"
-            label = f"{pool_name} [{status}, {autostart}]"
-            pool_node = tree.root.add(label, data=pool_data)
-            pool_node.data["type"] = "pool"
-            # Add a dummy node to make the pool node expandable
-            pool_node.add_leaf("Loading volumes...")
-
-            if expand_pools and pool_name in expand_pools:
-                self.app.call_later(pool_node.expand)
-
-            if select_pool and pool_name == select_pool:
-                node_to_select = pool_node
+            try:
+                pool_name = pool_data['name']
+                status = pool_data['status']
+                autostart = "autostart" if pool_data['autostart'] else "no autostart"
+                label = f"{pool_name} [{status}, {autostart}]"
+                pool_node = tree.root.add(label, data=pool_data)
+                pool_node.data["type"] = "pool"
+                # Add a dummy node to make the pool node expandable
+                pool_node.add_leaf("Loading volumes...")
+
+                if expand_pools and pool_name in expand_pools:
+                    self.app.call_later(pool_node.expand)
+
+                if select_pool and pool_name == select_pool:
+                    node_to_select = pool_node
+            except libvirt.libvirtError:
+                # Handle cases where pool might be listed but inaccessible (e.g. NFS down)
+                pool_name = pool_data.get('name', 'Unknown')
+                label = f"{pool_name} [unavailable]"
+                pool_node = tree.root.add(label, data=pool_data)
+                pool_node.data["type"] = "pool"
+                pool_node.add_leaf("Pool unavailable")
 
         if node_to_select:
             self.app.call_later(tree.select_node, node_to_select)
@@ -308,7 +316,8 @@ class ServerPrefModal(BaseModal[None]):
         if len(node.children) == 1 and node.children[0].data is None:
             node.remove_children()
             pool = node_data.get('pool')
-            if pool and pool.isActive():
+            # Check cached status instead of calling pool.isActive() to avoid blocking
+            if pool and node_data.get('status') == 'active':
                 volumes = storage_manager.list_storage_volumes(pool)
                 for vol_data in volumes:
                     vol_name = vol_data['name']
@@ -404,7 +413,7 @@ class ServerPrefModal(BaseModal[None]):
             self.app.show_error_message("Could not find pool object to edit.")
             return
 
-        if pool.isActive():
+        if node_data.get('status') == 'active':
             self.app.show_error_message("Pool must be inactive to edit its XML definition.")
             return
 

{virtui_manager-1.1.5 → virtui_manager-1.1.6}/src/vmanager/storage_manager.py

@@ -29,18 +29,40 @@ def list_storage_pools(conn: libvirt.virConnect) -> List[Dict[str, Any]]:
         pools = conn.listAllStoragePools(0)
         for pool in pools:
             try:
+                # Try to get basic info
+                try:
+                    name = pool.name()
+                except libvirt.libvirtError:
+                    name = "Unknown Pool"
+
                 is_active = pool.isActive()
                 info = pool.info()
                 pools_info.append({
-                    'name': pool.name(),
+                    'name': name,
                     'pool': pool,
                     'status': 'active' if is_active else 'inactive',
                     'autostart': pool.autostart() == 1,
                     'capacity': info[1],
                     'allocation': info[2],
                 })
-            except libvirt.libvirtError:
-                continue
+            except libvirt.libvirtError as e:
+                # If we fail to get details (e.g. NFS down), still list the pool but as unavailable
+                if 'name' not in locals():
+                     try:
+                        name = pool.name()
+                     except:
+                        name = "Unknown Pool"
+
+                logging.warning(f"Failed to get details for pool '{name}': {e}")
+                pools_info.append({
+                    'name': name,
+                    'pool': pool,
+                    'status': 'unavailable',
+                    'autostart': False,
+                    'capacity': 0,
+                    'allocation': 0,
+                    'error': str(e)
+                })
     except libvirt.libvirtError:
         return []
 

virtui_manager-1.1.5/FEATURES.md

@@ -1,256 +0,0 @@
-# Virtui Manager - Features
-
-## Overview
-A Textual-based TUI (Terminal User Interface) application for managing QEMU/KVM virtual machines using the libvirt Python API. It provides a comprehensive interface for VM management with features that go beyond basic management.
-
-## Main Interface Features
-
-### Multi-server Management
-- Connect to multiple libvirt servers simultaneously
-- Transhypervisor view showing VMs from different servers
-- Server selection and management interface
-
-### VM Grid Display
-- VMs displayed in a responsive grid layout (up to 5x3 = 15 VM)
-- Color-coded status indicators (Running, Paused, Stopped)
-- CPU, Memory, Disk, Net usage sparklines for running VMs
-- Pagination controls for large VM lists
-
-### VM Management Actions
-- Start, Shutdown, Force Off (destroy), Pause, Resume
-- Delete VM with optional storage cleanup: Now more robust, always using libvirt API for managed storage volumes, preventing permission errors. Automatically deletes VM snapshot metadata.
-- Hide restore snapshot if the VM is running or loading
-- Clone VM functionality: Clone VMs with advanced options, including specifying a custom suffix, cloning multiple instances at once, and automatic creation of storage for the new clones.
-- Rename VM with snapshot handling
-- Take, restore, and delete VM snapshots
-- View/Edit XML configuration
-- Connect to VM via virt-viewer
-- Web console access via novnc (when available)
-  - **Multi-session Support**: Support for multiple concurrent remote web console sessions via automatic port allocation/checking on the remote server.
-  - When connecting to a remote libvirt server via SSH, the web console can be configured to run either locally (default) or directly on the remote server.
-  - To enable running the web console on the remote server, set `REMOTE_WEBCONSOLE: True` in your `config.yaml`.
-  - When `REMOTE_WEBCONSOLE` is enabled, `websockify` and `novnc` assets must be installed on the remote server at the paths specified in `config.yaml` (default: `/usr/bin/websockify` and `/usr/share/novnc/`).
-  - For secure (HTTPS) remote web console access, `cert.pem` and `key.pem` files must also be present on the remote server in `~/.config/virtui-manager/`.
-- Bulk actions on selected VMs (start, stop, force off, pause, delete)
-- Edit Configuration Bulk action available
-- VM Migration (Live and Offline) with pre-checking server and VM configuration
-- Custom migration: migrate offline VMs with their volumes, snapshots, and overlays, allowing users to select where to place volumes on the destination server pool.
-- Always copy storage in custom migration by default
-
-### Disk Overlay Management (External Snapshots)
-- **Create Overlay**: Create a new QCOW2 overlay on top of the current disk (freezes base image).
-- **Discard Overlay**: Revert to the backing file and delete the overlay (discard changes).
-- **Commit Disk**: Merge changes from the overlay back into the base image (make changes permanent).
-- Visual management of overlay state.
-- Comparison guide between Internal Snapshots and External Overlays included in the UI.
-
-### Advanced Features
-- Filter VMs by status (All, Running, Paused, Stopped) and search by name
-- Filter VMs to show only VMs from a specific hypervisor
-- Server preferences configuration
-- Virsh shell access
-- Detailed VM information view
-- Web console management with automatic port allocation
-- Configuration file management for server lists
-- Create new VMs (with single server connection)
-- Bulk operations on multiple VMs
-- VMs sorted in human-readable order
-- Select which server to autoconnect at startup
-
-## Configure VM Features
-
-### CPU Configuration
-- Edit CPU count
-- Select CPU model from available models (including host-passthrough and default options)
-- CPU model selection is disabled when VM is running
-
-### Memory Configuration
-- Edit memory size in MB
-- Enable/disable shared memory (disabled when VM is running)
-
-### Firmware Configuration
-- Select firmware type (BIOS or UEFI)
-- For UEFI firmware:
-  - Enable/disable Secure Boot
-  - Enable/disable AMD-SEV and AMD-SEV-ES (when supported)
-  - Select UEFI file from available options
-- Machine type selection (disabled when VM is running)
-
-### Boot Configuration
-- Enable/disable boot menu
-- Boot device management
-- Set boot order for devices
-
-### Disk Management
-- View all disks in a table format
-- Add new disk (create new or attach existing)
-- Create new disk in specific storage pool
-- Attach existing volume to VM
-- Attach existing disk from storage pools
-- Remove disk
-- Disable disk
-- Enable disk
-- Edit disk properties (cache mode and discard mode)
-- Disk status indicators (enabled/disabled)
-- Set disk cache and discard modes
-- Display disk bus information
-
-### Network Configuration
-- View network interfaces with MAC addresses and IP addresses
-- Change network interface to a different network
-- View network DNS and gateway information
-- Add new network interface
-- Remove network interface
-- Change network interface model
-
-### VirtIO-FS Configuration
-- View existing VirtIO-FS mounts
-- Add new VirtIO-FS mount
-- Edit existing VirtIO-FS mount
-- Delete VirtIO-FS mount
-- Requires shared memory to be enabled
-
-### Video Configuration
-- Select video model (virtio, qxl, vga, cirrus, bochs, ramfb, none, default)
-- Enable/disable 3D acceleration (virtio only)
-- Video model selection is disabled when VM is running
-
-### Graphics Configuration
-- Select graphics type (VNC, Spice, or None)
-- Configure listen type (Address or None)
-- Set address (Hypervisor default, Localhost only, All interfaces)
-- Enable/disable auto port allocation
-- Set port number (when auto port is disabled)
-- Enable/disable password protection
-- Set password for graphics access
-- Apply graphics settings (disabled when VM is running)
-- When switching from Spice to VNC: If other SPICE-related devices (channels, audio, QXL video) are detected, the user is prompted to remove them for a clean switch. This process automatically removes SPICE channels and USB redirection, changes SPICE audio to 'none', and converts QXL video to 'virtio'. A default VNC graphics device is added if no other graphics device exists after removal.
-
-### TPM Configuration
-- Select TPM model (tpm-crb, tpm-tis, or none)
-- Select TPM type (emulated or passthrough)
-- Configure device path for passthrough TPM
-- Configure backend type and path for passthrough TPM
-- Apply TPM settings (disabled when VM is running)
-
-### RNG Configuration
-- Configure Random Number Generator (RNG) host device.
-- Apply RNG settings (disabled when VM is running).
-
-### Sound Configuration
-- Select sound model (ac97, ich6, sb16, pcspk, es1370, hda, default)
-- Sound model selection is disabled when VM is running
-
-### Watchdog Configuration
-- Configure Watchdog device for VM
-- Set watchdog model and action (reset, shutdown, poweroff)
-- Watchdog configuration is disabled when VM is running
-
-### Input Configuration
-- Configure input devices (keyboard, mouse, tablet)
-- Set input device type and bus (usb, ps2, virtio)
-- Input configuration is disabled when VM is running
-
-### USB Host Configuration
-- Add/Remove USB host devices
-- Configure vendor ID, product ID, and address
-
-### PCI Passthrough Configuration
-- View available PCI host devices
-- Attach PCI devices to VM (experimental)
-- Detach PCI devices from VM (experimental)
-- PCI device status indicators (attached/disconnected)
-
-### Serial Configuration
-- Add/Remove serial devices
-- Configure serial device type (Pty)
-
-### Additional Features
-- Tabbed interface for organized configuration
-- Toggle between main and extended configuration tabs
-- Real-time status indicators
-- Confirmation dialogs for destructive actions
-- Error handling and user feedback
-- VM status validation (prevents configuration changes when VM is running)
-
-## Server Management Features
-
-### Network Management
-- View all networks in a table format
-- Create new network with NAT or routed type
-- Edit network properties including DHCP settings
-- Delete network with confirmation
-- Toggle network active state
-- Toggle network autostart state
-- View network XML details
-- Get list of VMs using a specific network
-
-### Storage Management
-- View storage pools in a tree format
-- Create new storage pool (directory or network file system)
-- Edit storage pool properties (path)
-- Delete storage pool with confirmation
-- Create new storage volume
-- Delete storage volume with confirmation
-- Toggle storage pool active state
-- Toggle storage pool autostart state
-- List unused storage volumes
-- Get all storage volumes across all pools
-- Move storage volume between pools
-
-## User Interface Features
-
-### Keyboard Shortcuts
-- `v` - View Log
-- `f` - Filter VM
-- `p` - Pattern Selection of VM
-- `m` - Servers List
-- `s` - Select Servers
-- `ctrl+a` - Select/Deselect All VMs on current page
-- `ctrl+u` - Unselect all VMs
-- `c` - User Application Configuration
-- `ctrl+v` - Virsh Shell
-- `q` - Quit
-
-For Debugging the app:
-- `ctrl+l` - Start/Stop Log Stats
-- `ctrl+s` - Show Cache Stats
-
-
-### Visual Elements
-- Color-coded server identification
-- Status indicators with color coding (Running, Paused, Stopped)
-- Sparkline graphs for CPU, Memory, Disk, Network usage
-- Responsive layout that adapts to terminal size
-- Tabbed interface for organized information display
-- Selection indicators for multiple VMs
-
-## Technical Capabilities
-
-### Connection Management
-- Support for multiple libvirt connection types (local, SSH)
-- Automatic detection of virt-viewer, websockify, and novnc availability
-- Error handling and logging
-- Responsive UI that adapts to terminal size
-- Command-line mode support (--cmd flag)
-- Improved cache invalidation mechanism using UUID@URI for better accuracy
-
-## User Experience
-- Visual feedback through notifications
-- Confirmation dialogs for destructive actions
-- Loading indicators for long-running operations
-- Detailed error messages
-- Command-line mode for advanced users
-- Bulk operations
-- Real-time VM status updates
-
-## Extra Command-Line Tool (vmanager_cmd.py)
-
-In addition to the main TUI application, `vmanager` also provides a command-line interface (`vmanager_cmd.py`) for managing virtual machines and storage. This tool offers the following key features:
-
-*   **Multi-server Management**: Connect to and manage multiple `libvirt` servers simultaneously from a single shell.
-*   **Bulk VM Operations**: Execute commands like `start`, `stop`, `status`, `pause`, `resume`, `force_off`, and `delete` on multiple VMs across different connected servers at once.
-*   **Advanced VM Selection**: Select VMs for operations using direct names or powerful regular expression patterns.
-*   **Interactive VM Deletion**: Delete VMs with interactive confirmation, including an option to also remove associated storage volumes.
-*   **Storage Management**: List storage pools and identify unused storage volumes across all connected servers.
-*   **Tab Autocompletion**: Enjoy context-aware autocompletion for server names, VM names, and storage pool names, enhancing usability and speed.

virtui_manager-1.1.5/src/vmanager/modals/howto_disk_modal.py

@@ -1,93 +0,0 @@
-"""
-Modal to show how to manage VM disks.
-"""
-from textual.app import ComposeResult
-from textual.containers import Vertical, Horizontal, ScrollableContainer
-from textual.widgets import Button, Markdown
-from textual import on
-from .base_modals import BaseModal
-
-HOW_TO_DISK_TEXT = """
-# Managing VM Disks
-
-This guide explains the functions of the buttons available in the "Disks" tab.
-
----
-
-### Add Disk
-
-This button allows you to create a **brand new virtual disk** and attach it to the VM.
-
-- You will be prompted to select a **Storage Pool** where the new disk image file will be created.
-- You must provide a **Volume Name** for the new disk (e.g., `new-data-disk.qcow2`).
-- You must specify its **Size** and **Format** (`qcow2` or `raw`).
-- The VM does **not** need to be stopped to add a new disk.
-
----
-
-### Attach Existing Disk
-
-This attaches a **pre-existing disk image** to your VM. This is useful if you have an existing `.qcow2`, `.raw`, or `.iso` file you want to use.
-
-- The system will first ask you to select a **Storage Pool** that contains the disk volume you want to attach.
-- If the disk file is not part of a libvirt storage pool yet, you should first use the "Attach" button in the **Server Preferences -> Storage** tab to make it known to libvirt. This might involve creating a new storage pool for the directory containing your disk file.
-
----
-
-### Edit Disk
-
-*(This button is enabled only when a disk is selected in the table)*
-
-Allows you to modify properties of an attached disk, such as:
-- **Bus Type:** `virtio`, `sata`, `scsi`, etc.
-- **Cache Mode:** `none`, `writeback`, etc.
-- **Discard Mode:** `unmap`, `ignore`.
-
-> **Important:** The VM must be **stopped** to edit disk properties.
-
----
-
-### Remove Disk
-
-*(This button is enabled only when a disk is selected)*
-
-This **detaches** the selected disk from the virtual machine.
-
-- **This action does NOT delete the disk image file.** The file remains in its storage pool or on your filesystem.
-- It only removes the disk from this specific VM's configuration.
-- The VM must be **stopped** to remove most types of disks.
-
----
-
-### Disable Disk
-
-*(This button is enabled for active disks)*
-
-This temporarily "unplugs" the disk from the VM **without removing its configuration**.
-
-- The disk will become invisible to the guest operating system but remains in the disk list with a `(disabled)` status.
-- This is useful for troubleshooting or temporarily preventing access to a disk without fully removing it.
-
----
-
-### Enable Disk
-
-*(This button is enabled for disabled disks)*
-
-This "re-plugs" a disabled disk back into the VM, making it available to the guest operating system again.
-"""
-
-class HowToDiskModal(BaseModal[None]):
-    """A modal to display instructions for managing VM disks."""
-
-    def compose(self) -> ComposeResult:
-        with Vertical(id="howto-disk-dialog"):
-            with ScrollableContainer(id="howto-disk-content"):
-                yield Markdown(HOW_TO_DISK_TEXT, id="howto-disk-markdown")
-        with Horizontal(id="dialog-buttons"):
-            yield Button("Close", id="close-btn", variant="primary")
-
-    @on(Button.Pressed)
-    def on_button_pressed(self, event: Button.Pressed) -> None:
-        """Handle button presses."""
-        self.dismiss()

virtui_manager-1.1.5/src/vmanager/modals/howto_network_modal.py

@@ -1,60 +0,0 @@
-"""
-Modal to show how to configure networks.
-"""
-from textual.app import ComposeResult
-from textual.containers import Vertical, Horizontal, ScrollableContainer
-from textual.widgets import Button, Markdown
-from textual import on
-from .base_modals import BaseModal
-
-HOW_TO_NETWORK_TEXT = """
-# Understanding Network Configuration in libvirt
-
-libvirt provides flexible networking capabilities for virtual machines, allowing them to communicate with each other, the host, and external networks.
-
-### Types of Networks
-
-1.  **NAT (Network Address Translation) Network:**
-    *   **Purpose:** Allows VMs to access the external network (internet) but prevents external machines from directly initiating connections to the VMs.
-    *   **Mechanism:** libvirt creates a virtual bridge (e.g., `virbr0`) on the host, and VMs connect to this bridge. The host acts as a router, performing NAT for outgoing connections from VMs. VMs get IP addresses from a DHCP server managed by libvirt.
-    *   **Use Cases:** Most common setup for general VM usage where VMs just need internet access.
-
-2.  **Routed Network:**
-    *   **Purpose:** VMs can communicate with other machines on the host's physical network, and potentially external networks, with proper routing configured on the host and potentially external routers. VMs will have IP addresses on the same subnet as the host's physical network, or a dedicated routed subnet.
-    *   **Mechanism:** Similar to NAT, a virtual bridge is used, but without NAT. The host needs to be configured to route traffic between the virtual bridge and the physical interface. VMs typically get IP addresses from a DHCP server on the physical network or static IPs.
-    *   **Use Cases:** When VMs need to be directly accessible from the physical network, or participate as full members of an existing network.
-
-3.  **Isolated Network:**
-    *   **Purpose:** VMs on this network can only communicate with each other and the host, but not with external networks.
-    *   **Mechanism:** A virtual bridge is created, but no routing or NAT is configured to connect it to physical interfaces.
-    *   **Use Cases:** Testing environments, isolated services, or when you need a private network segment for VMs.
-
-### Key Concepts
-
-*   **Bridge:** A software-based network device that connects multiple network segments at the data link layer. VMs connect to a virtual bridge, which then connects to a physical interface (for NAT/routed) or remains isolated.
-*   **DHCP:** Dynamic Host Configuration Protocol. Automatically assigns IP addresses to VMs within a network.
-*   **Forward Device:** The physical network interface on the host through which the virtual network's traffic is forwarded (for NAT or routed modes).
-*   **MAC Address:** Media Access Control address. A unique identifier assigned to network interfaces. For KVM/QEMU, MAC addresses often start with `52:54:00:`.
-
-### Common Tasks
-
-*   **Create/Edit Network:** Define network parameters like name, IP range, DHCP settings, and forward mode.
-*   **Activate/Deactivate Network:** Start or stop a virtual network.
-*   **Autostart Network:** Configure a network to start automatically when the libvirt daemon starts.
-*   **View XML:** Examine the underlying libvirt XML definition of a network, which provides full details of its configuration.
-"""
-
-class HowToNetworkModal(BaseModal[None]):
-    """A modal to display instructions for network configuration."""
-
-    def compose(self) -> ComposeResult:
-        with Vertical(id="howto-network-dialog"):
-            with ScrollableContainer(id="howto-network-content"):
-                yield Markdown(HOW_TO_NETWORK_TEXT, id="howto-network-markdown")
-        with Horizontal(id="dialog-buttons"):
-            yield Button("Close", id="close-btn", variant="primary")
-
-    @on(Button.Pressed)
-    def on_button_pressed(self, event: Button.Pressed) -> None:
-        """Handle button presses."""
-        self.dismiss()

virtui_manager-1.1.5/src/vmanager/modals/howto_overlay_modal.py

@@ -1,73 +0,0 @@
-"""
-Modal to show how overlay disks work.
-"""
-from textual.app import ComposeResult
-from textual.containers import Vertical, Horizontal, ScrollableContainer
-from textual.widgets import Button, Markdown
-from textual import on
-from .base_modals import BaseModal
-
-HOW_TO_OVERLAY_TEXT = """
-# Understanding Snapshots and Disk Overlays
-
-Virtual machines in this manager support two ways to preserve states and manage changes: **Snapshots** and **Disk Overlays**. While they share similar goals, they work differently and are suited for different use cases.
-
----
-
-### 1. Snapshots (Internal)
-Snapshots are managed directly by libvirt and are typically stored **inside** the disk image (if using QCOW2 format).
-
-*   **How they work:** When you take a snapshot, libvirt records the current state of the VM's disks and, if the VM is running, its memory (RAM). You can have many snapshots for a single VM, creating a timeline you can jump back and forth in.
-*   **Operations:**
-    *   **Take Snapshot:** Creates a new restore point.
-    *   **Restore Snapshot:** Reverts the VM to a previous state.
-    *   **Delete Snapshot:** Removes the restore point from the timeline.
-*   **Best for:** Quick restore points before risky operations, and preserving the full "live" state of a running VM.
-
-### 2. Disk Overlays (External)
-Overlays are **new files** created on top of a base disk image. This is also known as "External Snapshots" or "Backing Files".
-
-*   **Key Concepts:**
-    *   **Base Image (Backing File):** The original disk image that becomes read-only.
-    *   **Overlay Image:** A new QCOW2 file that records only the changes made *after* its creation.
-    *   **Backing Chain:** The relationship between layers (e.g., Base -> Overlay 1 -> Overlay 2).
-*   **Operations:**
-    *   **New Overlay:** Freezes the current disk and starts a new layer.
-    *   **Discard Overlay (Revert):** Deletes the overlay file and reverts to the base image.
-    *   **Commit Disk (Merge):** Merges changes from the overlay into the base image, making them permanent.
-*   **Best for:** Maintaining "Golden Images", branching multiple VMs from a single base, and isolating large changes in separate files.
-
----
-
-### Comparison: Snapshot vs. Overlay
-
-| Feature | Snapshots (Internal) | Disk Overlays (External) |
-| :--- | :--- | :--- |
-| **Storage** | Inside the existing disk file | In a new, separate file |
-| **VM State** | Can include RAM (Live state) | Disk only (requires VM stop) |
-| **Management** | Timeline (multiple points) | Layered (Base + Changes) |
-| **Primary Use** | Quick restore points | Permanent branching / Golden images |
-
----
-
-### How Overlays Work (Technical)
-
-1.  **Creation:** When you create a "New Overlay", the current disk image is set as the backing file for a newly created QCOW2 file. The VM is then updated to point to this new overlay file instead of the original disk.
-2.  **Read Operations:** When the VM needs to read data, it first checks the overlay. If the data has been modified, it reads from the overlay. If not, it transparently reads from the backing file.
-3.  **Write Operations:** All writes are directed to the overlay file. The backing file remains untouched and pristine.
-"""
-
-class HowToOverlayModal(BaseModal[None]):
-    """A modal to display instructions for disk overlays."""
-
-    def compose(self) -> ComposeResult:
-        with Vertical(id="howto-overlay-dialog", classes="howto-dialog"):
-            with ScrollableContainer(id="howto-overlay-content"):
-                yield Markdown(HOW_TO_OVERLAY_TEXT, id="howto-overlay-markdown")
-        with Horizontal(id="dialog-buttons"):
-            yield Button("Close", id="close-btn", variant="primary")
-
-    @on(Button.Pressed)
-    def on_button_pressed(self, event: Button.Pressed) -> None:
-        """Handle button presses."""
-        self.dismiss()

virtui_manager-1.1.5/src/vmanager/modals/howto_ssh_modal.py

@@ -1,88 +0,0 @@
-"""
-Modal to show how to use ssh-agent.
-"""
-from textual.app import ComposeResult
-from textual.containers import Vertical, Horizontal, ScrollableContainer
-from textual.widgets import Button, Markdown
-from textual import on
-from .base_modals import BaseModal
-
-HOW_TO_SSH_TEXT = """
-# Using an SSH Agent for Passwordless Connections
-
-Using an `ssh-agent` is the standard and most secure way to handle passphrase-protected SSH keys, allowing you to connect without repeatedly entering your passphrase.
-
-### What is an SSH Agent?
-
-An `ssh-agent` is a background program that securely stores your private SSH keys in memory. When you try to connect to a remote server, SSH can ask the agent for the key, and the agent provides it. You only need to "unlock" your key once.
-
----
-
-### Step 1: Start the `ssh-agent`
-
-On most modern desktop environments, an agent is often started automatically. If not, run this in your terminal:
-
-```bash
-eval "$(ssh-agent -s)"
-```
-
-> To make this permanent, add the command to your shell's startup file (e.g., `~/.bashrc` or `~/.zshrc`).
-
----
-
-### Step 2: Add Your SSH Key to the Agent
-
-Use the `ssh-add` command. If your key is in a default location (`~/.ssh/id_rsa`, etc.), you can just run:
-
-```bash
-ssh-add
-```
-
-If your key is elsewhere, specify the path to the **private key**:
-
-```bash
-ssh-add /path/to/your/private_key
-```
-
-You will be prompted for your key's passphrase **one time**.
-
-To verify the key was added, list the agent's keys:
-```bash
-ssh-add -l
-```
----
-
-### Step 3: Connect
-
-That's it! `Virtui Manager` will now use the agent to authenticate for any `qemu+ssh://` connections without any more prompts.
-
----
-
-### SSH Compression for Performance
-
-For connections over slower networks, enabling SSH compression can significantly improve performance. This is configured in your SSH client's configuration file.
-
-To enable compression for a specific host, add the following to your `~/.ssh/config` file:
-
-```
-Host your_remote_host_name
-  Compression yes
-```
-
-Replace `your_remote_host_name` with the actual hostname or IP address you use in your `qemu+ssh://` URI. If you want to enable compression for all SSH connections, you can use `Host *`.
-"""
-
-class HowToSSHModal(BaseModal[None]):
-    """A modal to display instructions for using an ssh-agent."""
-
-    def compose(self) -> ComposeResult:
-        with Vertical(id="howto-ssh-dialog"):
-            with ScrollableContainer(id="howto-ssh-content"):
-                yield Markdown(HOW_TO_SSH_TEXT, id="howto-ssh-markdown")
-        with Horizontal(id="dialog-buttons"):
-            yield Button("Close", id="close-btn", variant="primary")
-
-    @on(Button.Pressed)
-    def on_button_pressed(self, event: Button.Pressed) -> None:
-        """Handle button presses."""
-        self.dismiss()

virtui_manager-1.1.5/src/vmanager/modals/howto_virtiofs_modal.py

@@ -1,85 +0,0 @@
-"""
-Modal to show how to use VirtIO-FS.
-"""
-from textual.app import ComposeResult
-from textual.containers import Vertical, Horizontal, ScrollableContainer
-from textual.widgets import Button, Markdown
-from textual import on
-from .base_modals import BaseModal
-
-HOW_TO_VIRTIOFS_TEXT = """
-# Using VirtIO-FS for Host-Guest File Sharing
-
-VirtIO-FS is a high-performance shared filesystem that lets you share a directory from your host machine directly with a guest VM.
-
----
-
-### Host Prerequisites
-
-1.  **Shared Memory:** VirtIO-FS requires shared memory to be enabled for the VM. You can enable this in the **"Mem"** tab.
-2.  **Permissions:** The user running QEMU/libvirt on the host must have the necessary permissions to read (and write, if needed) the source directory you want to share.
-
----
-
-### Adding a VirtIO-FS Mount
-
-- **Source Path:** The absolute path to the directory on your **host machine** that you want to share.
-- **Target Path:** This is a "mount tag" or a label that the guest VM will use to identify the shared directory. It is **not** a path inside the guest. For example, you could use `shared-data`.
-
----
-
-### Mounting in a Linux Guest
-
-Most modern Linux distributions include the necessary VirtIO-FS drivers.
-
-**1. Create a Mount Point:**
-This is the directory inside your VM where the shared files will appear.
-
-```bash
-sudo mkdir /mnt/my_host_share
-```
-
-**2. Mount the Share:**
-Use the `mount` command with the filesystem type `virtiofs` and the **Target Path (mount tag)** you defined.
-
-```bash
-sudo mount -t virtiofs 'your-target-path' /mnt/my_host_share
-```
-*(Replace `'your-target-path'` with the actual tag you set)*
-
-**3. Automount on Boot (Optional):**
-To make the share available automatically every time the VM boots, add an entry to `/etc/fstab`:
-
-```
-your-target-path /mnt/my_host_share virtiofs defaults,nofail 0 0
-```
-> The `nofail` option is recommended to prevent boot issues if the share is not available.
-
----
-
-### Mounting in a Windows Guest
-
-**1. Install Drivers:**
-You must install the VirtIO-FS drivers in the Windows guest. These are included in the **"VirtIO-Win Guest Tools"** package, which you can typically download as an ISO file.
-- Download the latest stable `virtio-win.iso` from the [Fedora VirtIO-Win project](https://github.com/virtio-win/virtio-win-pkg-scripts/blob/master/README.md).
-- Attach the ISO to your VM as a CD-ROM.
-- Open the CD-ROM in Windows and run the `virtio-win-guest-tools.exe` installer, ensuring the **"VirtIO-FS"** feature is selected.
-
-**2. Access the Share:**
-After installation and a reboot, the VirtIO-FS service will start. The shared folder will automatically appear as a network drive in **This PC** (or My Computer). The drive will be named after the **Target Path (mount tag)** you set.
-"""
-
-class HowToVirtIOFSModal(BaseModal[None]):
-    """A modal to display instructions for using VirtIO-FS."""
-
-    def compose(self) -> ComposeResult:
-        with Vertical(id="howto-virtiofs-dialog"):
-            with ScrollableContainer(id="howto-virtiofs-content"):
-                yield Markdown(HOW_TO_VIRTIOFS_TEXT, id="howto-virtiofs-markdown")
-        with Horizontal(id="dialog-buttons"):
-            yield Button("Close", id="close-btn", variant="primary")
-
-    @on(Button.Pressed)
-    def on_button_pressed(self, event: Button.Pressed) -> None:
-        """Handle button presses."""
-        self.dismiss()