Thin Agent Virtual Machine Event Monitoring

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In virtual machine systems, updating and managing anti-virus software and virus signature databases across multiple guest operating systems is inefficient, leading to discrepancies in anti-virus protection and requiring separate updates for each system.

Innovation Solution

A thin agent installed within each virtual machine monitors system events and communicates selectively with service applications, using a multiplexer and services manager to facilitate communication and access to system resources, allowing for centralized management and updates without interrupting VM operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If separate virus signature database copies are maintained in each guest OS, then each system can operate independently, but updating and managing anti-virus software becomes inefficient and leads to discrepancies in protection

Engineering Contradiction:
ImproveIndependent operation of guest OSVSAvoidAnti-virus software management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A service appliance is introduced as an intermediary component between the guest OS and the virus signature database. The service appliance maintains a centralized virus signature database and communicates with guest OS through a service interface, eliminating the need for each guest OS to maintain its own copy while preserving independent operation capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The service appliance provides universal anti-virus protection across multiple guest OS by implementing a single centralized virus signature database that serves all connected systems. This multi-functional approach allows one service appliance to manage security for numerous guest OS, replacing the traditional one-per-system model.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Productivity

If anti-virus software is updated separately in each guest OS, then updates can be applied individually, but the process becomes time-consuming and resource-intensive

Engineering Contradiction:
ImproveAnti-virus update speedVSAvoidTime required for separate updates
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

Multiple separate anti-virus update operations are merged into a single centralized update process. The service appliance receives updated virus signatures once and distributes them to all connected guest OS simultaneously, transforming numerous sequential update operations into one efficient batch process.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

Virus signature updates are prepared and validated in advance at the service appliance before distribution to guest OS. This preliminary action ensures that updates are ready for immediate deployment, reducing the overall time required and eliminating the need for repeated update cycles across individual systems.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If service applications are added to VMs, then new functions can be provided, but the operation of existing VMs may be interrupted

Engineering Contradiction:
ImproveFunctionality of VMVSAvoidVM operation continuity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The service application architecture is segmented into modular components that can be independently added, removed, or updated without affecting the core VM operation. The service interface is designed as a separate layer, allowing new services to be introduced while maintaining the operational continuity of existing VM through isolation of service changes.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9195518B1System and method for communicating production virtual machine access events to a service appliance in a virtualized environment
Publication Date: 2015.11.24 VMWARE INC
  • US9195518B1 patent drawing
  • US9195518B1 patent drawing
  • US9195518B1 patent drawing

AI summary

A thin agent installed within a guest virtual machine (GVM) enables a service application to monitor events within the GVM and to perform certain system functions within the GVM. The thin agent maintains a distinct set of rules for selectively reporting system events to each different service application connected to the thin agent. A multiplexer executing within a virtualization software is configured to facilitate communication between a plurality of thin agents and a plurality of service applications. A services manager facilitates communication between new service applications and the thin agents. Each service application is able to advantageously add new functions to production GVMs without interrupting proper operation of the GVMs.