Native protocol I / O device network access method and system in virtualization environment

Abstract

The invention relates to the technical field of virtualized network communication, in particular to a native protocol I / O device network access method and system in a virtualized environment, and the method comprises the following steps: S1, deploying an I / O virtualization service on a physical server, and enabling the I / O virtualization service to be connected with a physical I / O device; s2, a virtual machine I / O client is installed in the virtual machine and used for providing a standard I / O equipment interface for an upper-layer application and establishing network connection with the I / O virtualization service; s3, establishing a native I / O protocol pipeline between the I / O virtualization service and the virtual machine I / O client; s4, transmitting I / O equipment data through a native I / O protocol pipeline; s5, in the migration process of the virtual machine, the I / O session state is kept, and network connection is reestablished; through an innovative session persistence and state synchronization mechanism, I / O connection can be seamlessly kept in the migration process of the virtual machine, it is ensured that service operation is not perceptually interrupted, and the reliability of the system and the user experience are greatly improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of virtualized network communication, in particular to a native protocol I / O device network access method and system in a virtualized environment. BACKGROUND

[0002] With the development of virtualization technology, more and more business applications run in a virtual machine environment. However, the access of the virtualization platform to the local I / O hardware (such as serial ports, USB interfaces, etc.) usually depends on the direct mapping mode of the physical machine. This mode will cause the original I / O mapping to fail when the virtual machine migrates or drifts (VM MigratI / On), thereby causing the I / O connection to be interrupted, which adversely affects the continuity and reliability of the upper layer application.

[0003] The prior art mainly has the following solutions: Some existing solutions use a general network transmission method for remote I / O access after I / O data analysis, and some present in a compromised way, that is, not the original native device, but through a certain compatible way to obtain data. Although it can solve the problem of local I / O mapping failure to a certain extent, it often needs to encapsulate or convert I / O data, which cannot maintain the characteristics of the original I / O protocol, and may cause the following problems: 1. Application layer compatibility is limited: some applications that depend on specific I / O protocol features cannot work normally; 2. Data transmission efficiency is reduced: protocol conversion and additional encapsulation cause performance loss; 3. Special control commands are lost: some device-specific control commands cannot be preserved during protocol conversion; 4. Timing requirements cannot be met: I / O devices sensitive to timing cannot maintain the original precise timing requirements; 5. Migration process session interruption: lack of perfect session maintenance mechanism, causing I / O operation interruption during migration. SUMMARY

[0004] (I) Technical problems solved In view of the deficiencies of the prior art, the present application provides a native protocol I / O device network access method and system in a virtualized environment, which solves the technical problems of I / O device connection interruption during virtual machine migration and loss of native I / O protocol characteristics in existing solutions.

[0005] (II) Technical solutions To achieve the above purpose, the present application provides the following technical solutions: a network I / O device access method based on a native protocol in a virtualized environment, comprising the following steps: S1: Deploy I / O virtualization service on physical server, which connects physical I / O devices and provides device registration, session management and protocol adaptation services; S2: Install virtual machine I / O client in virtual machine, which provides standard I / O device interface to upper layer application and establishes network connection with I / O virtualization service; S3: Establish native I / O protocol pipe between I / O virtualization service and virtual machine I / O client, which keeps the complete characteristics of original I / O protocol; S4: Transmit I / O device data through the native I / O protocol pipe to realize transparent access of virtual machine to physical I / O device; S5: Keep I / O session state and rebuild network connection during virtual machine migration to ensure business continuity; The I / O virtualization service provides multiplexing access capability for the same physical I / O device, supporting multiple virtual machines to access the same physical I / O device simultaneously.

[0006] Further, in step S3, the method of establishing a native I / O protocol pipe includes: Identify the protocol characteristics of physical I / O device, including command set, timing requirements and data format; Encapsulate the original I / O protocol into network transmission protocol to keep the complete characteristics of the original protocol; Decapsulate the encapsulated data at the receiving end to restore the original I / O protocol data; Perform corresponding I / O operations or return operation results according to the protocol data after decapsulation.

[0007] Further, in step S5, the method of keeping I / O connection during virtual machine migration includes: Before virtual machine migration, send current session state information to I / O virtualization service and save it persistently; During virtual machine migration, suspend I / O operation and freeze current session; After virtual machine migration is completed, virtual machine I / O client initiates a reconnection request to I / O virtualization service; I / O virtualization service verifies session information and restores session state; Client and server perform state synchronization to ensure I / O device state consistency; Restore normal I / O operation to ensure business continuity.

[0008] Further, the I / O virtualization service implements the following functions: Automatic discovery, registration and state monitoring of physical I / O devices; Adaptation of multiple I / O protocols and preservation of native characteristics; Establishment and maintenance of connection sessions between virtual machines and I / O devices; Persistent storage and state synchronization of session information; Security control and identity authentication for device access.

[0009] Further, the virtual machine I / O client implements the following functions: Provides a standard I / O device interface to the upper layer application; Converts the I / O request of the application into a network transmission format; Establishes and maintains network connections with the I / O virtualization service; Reduces network access through local caching and improves response speed; Detects network connection failures and implements an automatic reconnection mechanism.

[0010] A network I / O device access system based on native protocols in a virtualized environment, characterized by comprising: I / O virtualization service, deployed on a physical server, for connecting physical I / O devices and providing networked I / O services; Virtual machine I / O client, deployed in a virtual machine, for providing a standard I / O interface to the application and communicating with the I / O virtualization service; Native I / O protocol pipeline, a network transmission channel established between the server and the client that preserves the original I / O protocol characteristics; Session management module, for maintaining device connection status and supporting connection recovery after virtual machine migration.

[0011] Further, the I / O virtualization service includes: Device management module, responsible for discovery, registration, and state monitoring of physical I / O devices; Protocol adaptation engine, responsible for identifying and processing the protocol characteristics of different types of I / O devices; Session manager, responsible for establishing and maintaining connection sessions between virtual machines and I / O devices; Network transmission module, responsible for reliable data transmission over the network; Security control module, responsible for connection authentication and access control; Device resource scheduling module, responsible for reasonably allocating device resources in a multi-virtual machine environment; Cluster management module, responsible for implementing node collaborative work and state synchronization in a multi-server environment.

[0012] Further, the virtual machine I / O client includes: Device interface layer, providing a standard I / O device interface to the upper layer application; Protocol conversion layer, responsible for network format conversion of I / O requests; Session connection manager, responsible for establishing and maintaining network connections; Local cache module, reducing network access through caching; Fault detection and recovery module, responsible for detecting connection failures and implementing recovery mechanisms; Performance optimization module, improving system efficiency through request batching and operation merging; Monitoring and diagnostic module, collecting I / O operation statistics and performance indicators.

[0013] Further, the I / O device types supported by the native I / O protocol pipeline include but are not limited to: USB devices, serial devices, parallel devices, cryptographic card devices, special instrument devices, SCSI devices, industrial bus devices.

[0014] Further, the native I / O protocol pipeline implements the following functions: Maintain the timing characteristics and control commands of the original I / O protocol; Provide reliability guarantees required for network transmission; Support data compression and optimization to improve transmission efficiency; Implement data encryption and integrity verification to ensure security; Support unified packaging and transmission of multiple I / O protocol types.

[0015] Further, the system also includes a device resource scheduling module for allocating device resources according to pre-set policies or priority rules when multiple virtual machines request access to the same I / O device.

[0016] Further, the system also includes a device simulation module that, when a physical I / O device is temporarily unavailable, maintains the normal operation of the application program by simulating device behavior.

[0017] Further, the system supports multi-path transmission at the network transmission layer, improving system reliability by establishing redundant network connections.

[0018] Further, the following steps are included: Audit records of operations on physical I / O devices, including operation time, operation type, operation content and operation result; Implement operation playback function according to audit records for fault analysis and system debugging.

[0019] Further, the I / O virtualization service also has load balancing function, when the load of a single server is too high, it can automatically transfer part of the I / O device access task to other I / O virtualization services.

[0020] Further, the system also includes a cluster management mechanism, which realizes the following functions in a multi-server deployment environment: Automatic discovery and registration of server nodes; State synchronization and consistency maintenance between cluster nodes; Dynamic task distribution based on load conditions; Node fault detection and automatic failover; Centralized management and distribution of cluster configuration.

[0021] Further, the system also includes a multi-tenant support mechanism, which realizes resource isolation and security boundaries between different tenants.

[0022] Further, the system also includes a multi-tenant support mechanism, which realizes resource quota and priority management at the tenant level.

[0023] Further, the system also includes a multi-tenant support mechanism, which realizes tenant-specific device allocation and sharing mode.

[0024] Further, the system also includes a multi-tenant support mechanism, which realizes performance monitoring and reporting at the tenant level.

[0025] Further, the encapsulation format of the original I / O protocol into the network transmission protocol includes: Header identification, used to identify the beginning of the data packet; Protocol type, identifying the type of the original I / O protocol; Session ID, uniquely identifying the session between the virtual machine and the I / O device; Sequence number, identifying the order of the data packet; Timestamp, used to maintain timing characteristics; Flag bit, containing various control flags; Data length, identifying the length of the valid data; Raw data, containing the complete content of the original I / O protocol; Check code, used for data integrity check.

[0026] Further, the method also includes the following steps: Collecting performance indicators of the system, including delay, throughput, resource utilization, etc. Analyzing system bottlenecks according to performance indicators; Dynamically adjusting system parameters to optimize system performance; Providing targeted optimization strategies according to different application scenarios and device characteristics.

[0027] Further, the system supports the following application scenarios: Remote access of financial industry secure encryption card devices; Medical device data collection and analysis Remote monitoring of industrial control equipment Remote sharing of scientific research equipment Virtualization access and sharing of special peripherals.

[0028] Advantages Compared with the prior art, the present application provides a network access method and system for native protocol I / O equipment in a virtualization environment, which has the following advantages: 1. The present application can seamlessly maintain I / O connection during virtual machine migration through the innovative session persistence and state synchronization mechanism, ensures the business operation without perceptual interruption, provides continuity guarantee for the core business of enterprises, and greatly improves the reliability and user experience of the system.

[0029] 2. The present application realizes the protocol encapsulation technology of complete preservation of native protocol fields, so that the application program depending on the specific I / O protocol characteristics can normally run in the virtualization environment, ensures the accurate operation of time-sensitive I / O equipment, makes the networked I / O equipment functionally equivalent to the local equipment, and improves the compatibility and stability of the application.

[0030] 3. The present application is not only suitable for common USB, serial port, parallel port and other equipment, but also can support industrial bus equipment, encryption card equipment and other special equipment, adapt to the needs of different industries, and enhance its versatility.

[0031] 4. The present application is not only suitable for common USB, serial port, parallel port and other equipment, but also can support industrial bus equipment, encryption card equipment and other special equipment, adapt to the needs of different industries. In addition, the plug-in mechanism provided by the system facilitates the extension of new protocol types in the future, and enhances its flexibility.

[0032] 5. The present application is divided into multiple modules, each module is responsible for independent function, easy to manage and maintain, adopts layered design, reduces the system complexity and maintenance cost. BRIEF DESCRIPTION OF DRAWINGS

[0033] The drawings described herein are used to provide further understanding of the present application, constitute a part of the present application, the schematic embodiments of the present application and the description thereof are used to explain the present application, and do not constitute improper limitation on the present application. In the drawings: Figure 1 Network I / O equipment access method flow chart based on native protocol in virtualization environment. DETAILED DESCRIPTION

[0034] With reference to the drawings of the embodiments of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described, obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments of the present application, all the other embodiments obtained by those skilled in the art without creative work are within the protection scope of the present application.

[0035] The specific embodiments are given below.

[0036] Embodiment 1 Please refer to Figure 1 The present application provides a native protocol I / O device network access system in a virtualization environment, which comprises an I / O virtualization service, a virtual machine I / O client, a native I / O protocol pipe and a session management module.

[0037] The I / O virtualization service is deployed on a physical server and is responsible for the connection and management of physical I / O devices. The physical I / O devices can be various types of external devices, such as serial port devices, USB devices, parallel port devices, etc. The I / O virtualization service communicates directly with the physical I / O devices through device drivers to obtain device information and data.

[0038] The virtual machine I / O client is deployed inside a virtual machine and provides a standard I / O device interface to the application running in the virtual machine. The application does not need to be aware of the actual location of the physical device and can access the remote I / O device as if it were accessing a local device.

[0039] The native I / O protocol pipe is a network transmission channel established between the I / O virtualization service and the virtual machine I / O client. The channel uses a special encapsulation method to maintain the complete characteristics of the original I / O protocol, including timing requirements, control commands, etc., while providing the reliability and security required for network transmission.

[0040] The session management module is responsible for maintaining the device connection state, recording session information, and supporting quick recovery of the connection after virtual machine migration. The session information includes device identification, connection parameters, state records, etc.

[0041] Embodiment 2 The I / O virtualization service comprises the following functional modules: (i) Device Management Module: responsible for the discovery, registration and state monitoring of physical I / O devices. When a new device is connected, this module automatically identifies the device type and characteristics and registers the device in the system. Meanwhile, this module also supports hot plug recognition and dynamic resource allocation. In terms of implementation, the device management module includes the following sub-modules: 1. Device Discovery Sub-module: discovers newly connected I / O devices in real time through polling physical interfaces or listening to system events; 2. Device Identification Sub-module: identifies device type and function by reading device descriptors or feature codes; 3. Driver Loading Sub-module: automatically loads the corresponding device driver according to the device type; 4. Resource Allocation Sub-module: allocates system resources such as memory space and interrupt numbers for devices; 5. State Monitoring Sub-module: periodically checks device status to detect device abnormalities in a timely manner; (ii) Protocol Adaptation Engine: responsible for identifying and processing the protocol characteristics of different types of I / O devices. This engine implements an adaptation layer for multiple I / O protocols, which can preserve the complete characteristics of the original protocol while providing the necessary encapsulation for network transmission. Key technical implementations of the protocol adaptation engine include: 1. Protocol Identification Mechanism: identifies the specific protocol type and version used by the device through feature matching; 2. Protocol Adaptation Layer: implements a dedicated adaptation layer for each I / O protocol to maintain protocol semantics; 3. Protocol Conversion Engine: implements lossless conversion between different protocols for special application scenarios; 4. Protocol Extension Interface: supports the addition of new protocol types through a plug-in mechanism; 5. Protocol Optimization Processing: implements performance optimization strategies for specific protocols; (iii) Session Manager: responsible for establishing and maintaining connection sessions between virtual machines and I / O devices. Session information is stored persistently to support connection recovery after virtual machine migration. The session manager also implements a session state synchronization mechanism to ensure consistency of connection states. The implementation of the session manager includes: 1. Session Establishment Module: handles connection requests from virtual machines and establishes new sessions; 2. Session State Machine: manages the life cycle and state transitions of sessions; 3. Session Persistence Module: saves session information to persistent storage to support recovery after system restart; 4. State Synchronization Module: implements consistency of session states in multi-server deployment environments; 5. Session Recovery Module: supports fast session recovery after virtual machine migration or network interruption; (IV) Network Transmission Module: responsible for data transmission over the network, achieving reliable data delivery, this module uses low-latency network protocols, supports QoS guarantee, and implements data compression and optimization algorithms to improve transmission efficiency, specific implementation techniques include: 1. Multi-protocol support: supports multiple transmission protocols such as TCP, UDP, and RDMA; 2. Adaptive selection algorithm: automatically selects the optimal transmission protocol based on network conditions and data characteristics; 3. QoS implementation: implements differentiated services through traffic marking and priority queues; 4. Congestion control: implements adaptive congestion control algorithms to avoid network congestion; 5. Multi-path transmission: supports simultaneous use of multiple network paths to improve throughput and reliability; 6. Bandwidth management: implements dynamic bandwidth allocation to ensure the performance of critical I / O operations; (V) Security Control Module: responsible for connection authentication and access control, ensuring that only authorized virtual machines can access specified I / O devices, this module implements end-to-end encrypted communication and provides integrity verification mechanisms to prevent data tampering, the technical implementation of the security control module includes: 1. Identity authentication: supports multi-factor authentication mechanisms to confirm the legitimacy of connection requests; 2. Access control: fine-grained access control system based on roles and policies; 3. Data encryption: uses TLS 1.3 or higher to implement data transmission encryption; 4. Integrity protection: ensures data integrity through algorithms such as HMAC; 5. Security audit: records all security-related events to support post-auditing; (VI) Device Resource Scheduling Module: responsible for allocating device resources when multiple virtual machines simultaneously request access to the same I / O device, this module implements resource scheduling algorithms based on priority and fairness to ensure efficient use of system resources, specific implementation includes: 1. Resource pool management: maintains a pool of available I / O device resources and tracks resource usage status; 2. Scheduling algorithm: implements various scheduling algorithms such as priority scheduling, time slice rotation, and fair sharing; 3. QoS guarantee: ensures that critical services obtain the required device resources; 4. Load balancing: achieves balanced distribution of device loads in a multi-server environment; 5. Resource isolation: ensures that resource usage between different tenants is isolated; (vii) Cluster management module: In a multi-server deployment environment, it realizes the cooperation and state synchronization between servers. This module supports load balancing, fault switching and centralized management functions. The technical implementation includes: 1. Service discovery: automatically discover other server nodes in the cluster; 2. State synchronization: realize the state consistency between cluster nodes; 3. Task distribution: distribute I / O processing tasks according to the load situation; 4. Fault detection: real-time monitoring of node state, detection of node failure; 5. Automatic switching: automatically switch to standby node when node failure occurs.

[0042] Embodiment 3: The virtual machine I / O client includes the following functional modules: (i) Device interface layer: provides a standard I / O device interface to the upper layer application. The application accesses the I / O device through this interface without needing to perceive the actual location of the device. The device interface layer simulates the behavior of the local device to ensure the compatibility of the application program. The specific implementation includes: 1. Standard device interface implementation: support various general device interfaces, such as Windows device driver interface, Linux device file interface, etc.; 2. Device characteristic simulation: completely simulate the behavior characteristics of physical devices, including interrupt, DMA, etc. mechanism; 3. Interface adaptation conversion: provide an adaptation layer for different operating systems to ensure cross-platform compatibility; 4. Transparent access mechanism: makes the application program use remote devices without modification; 5. Device state management: maintain device state information and feedback to the application program in a timely manner; (ii) Protocol conversion layer: responsible for converting the I / O request of the application program into network transmission format, and restoring it into the I / O response recognizable by the application program after receiving the network data. This layer maintains the characteristics of the original I / O protocol to ensure that the protocol semantics remain unchanged. The technical implementation includes: 1. Request analysis module: analyze the I / O request initiated by the application program; 2. Protocol mapping module: map the I / O request to the native I / O protocol format; 3. Protocol encapsulation module: encapsulate the native I / O protocol into network transmission format; 4. Response processing module: process the I / O operation results returned from the server; 5. Asynchronous processing mechanism: support asynchronous I / O operation to improve system concurrency performance; (Three) Session Connection Manager: responsible for establishing and maintaining network connections with I / O virtualization services, when detecting network interruption or virtual machine migration, the session connection manager is responsible for automatic reconnection and recovery of session state, the specific implementation includes: 1. Connection establishment module: establish secure connection with I / O virtualization service; 2. Session authentication module: complete identity authentication and permission verification; 3. Connection monitoring module: monitor network connection state, and find connection exception in time; 4. Automatic reconnection module: automatically try to reconnect after connection interruption; 5. Session recovery module: rebuild session state after connection recovery; 6. Multi-path management: support multiple network paths and realize path selection and switching; (Four) Local cache module: reduce network access through local cache, improve I / O operation response speed, for frequently accessed data or configuration information, the local cache module saves its copy, reduces network transmission delay, the technical implementation includes: 1. Cache strategy management: realize various cache strategies, such as LRU, LFU, etc; 2. Cache consistency maintenance: ensure the consistency of cache data and server side data; 3. Prefetch mechanism: according to access mode, preacquire data that may be needed; 4. Write back strategy: support different write operation strategies, such as direct write, write back, etc; 5. Cache space management: dynamically adjust cache size, optimize memory usage; (Five) Fault detection and recovery module: responsible for detecting network connection fault and I / O operation exception, and realizing fault recovery mechanism, the module realizes operation retry, breakpoint resume and other functions, improves the reliability of the system, the specific implementation includes: 1. Fault monitoring mechanism: real-time monitoring of I / O operation state and network connection; 2. Fault classification and identification: distinguish different types of faults and take corresponding measures; 3. Operation retry strategy: implement intelligent retry for failed I / O operation; 4. Breakpoint resume mechanism: support breakpoint recovery for large data transmission; 5. Degraded service strategy: provide degraded service in case of serious fault; 6. State recovery mechanism: restore normal operation state after fault is solved; (Six) Performance optimization module: improve the performance and efficiency of I / O operation through various optimization technologies, the module realizes request batch processing, operation merging and other functions, reduces network interaction times, improves throughput, the key technologies include: 1. Request batching: Combining multiple small I / O requests into one batch request; 2. Operation merging: Merging consecutive read-write operations to reduce network interactions; 3. I / O priority management: Setting different processing priorities according to operation importance; 4. Asynchronous parallel processing: Supporting multiple I / O operations to be executed in parallel; 5. Resource usage optimization: Optimizing the usage efficiency of CPU, memory, and network resources; (Seven) Monitoring and diagnosis module: Collecting I / O operation statistics and performance indicators to provide data support for performance tuning and fault diagnosis, this module implements functions such as log recording, performance analysis, etc., the specific implementation includes: 1. Performance indicator collection: Recording key performance indicators such as response time, throughput, etc.; 2. Operation log recording: Detailed recording of I / O operation process and results; 3. Abnormal event reporting: Recording and reporting abnormal events and error conditions; 4. Performance bottleneck analysis: Identifying performance bottlenecks in the system; 5. Diagnosis tool support: Providing diagnostic interfaces to support fault analysis tools.

[0043] Embodiment 4: The workflow of the native I / O protocol pipeline includes the following steps: (I) Protocol feature identification: The I / O virtualization service analyzes the protocol features of physical I / O devices, including command sets, timing requirements, data formats, etc. Specifically, the system maintains a protocol feature library containing the feature descriptions of common I / O device protocols. When a new device is connected, the system automatically matches with the feature library to identify the protocol type and characteristics of the device.

[0044] (II) Protocol encapsulation: Encapsulating the original I / O protocol into a network transmission protocol, using a special encapsulation format to maintain the complete characteristics of the original protocol. The encapsulation process does not change the semantics and timing characteristics of the original protocol. The encapsulation format includes the following fields: 1. Header identification (4 bytes): Identifies the start of the encapsulated data packet; 2. Protocol type (2 bytes): Identifies the type of the original I / O protocol; 3. Timestamp (8 bytes): Records the encapsulation time, used to maintain timing characteristics; 4. Data length (4 bytes): Identifies the length of the valid data; 5. Original data: Maintains the complete content of the original I / O protocol; 6. Check code (4 bytes): Used for data integrity check; (Three) Network Transmission: The encapsulated protocol data is transmitted from the I / O virtualization service to the virtual machine I / O client or from the client to the server through the network, and the transmission process ensures the integrity and security of the data. The network transmission adopts the following optimization strategies: 1. For time-sensitive I / O operations, use UDP protocol combined with reliability guarantee mechanism; 2. For large data transmission, use TCP protocol and implement data compression; 3. Support multi-path transmission to improve network utilization and reliability; 4. Implement network QoS to ensure priority transmission of critical I / O operations; (Four) Protocol Unpacking: The receiver unpacks the received data to restore the original I / O protocol data. The unpacking process maintains the timing and semantic characteristics of the original protocol. The unpacking steps include: 1. Verify data packet integrity; 2. Extract timestamp information for controlling the timing of I / O operations; 3. Analyze protocol type and select corresponding processing logic; 4. Restore the original I / O protocol data; (Five) Protocol Processing: Based on the unpacked protocol data, perform corresponding I / O operations or return operation results. The processing process includes: 1. For input operations, pass data to upper-layer applications or devices; 2. For output operations, collect operation results and prepare return data; 3. Handle special control commands and state queries; 4. Record operation logs for troubleshooting and performance analysis; The native I / O protocol pipeline supports multiple I / O protocol types, including but not limited to: 1. USB protocol: Supports USB 1.0 / 2.0 / 3.0 specifications, including control transfer, bulk transfer, interrupt transfer, and isochronous transfer; 2. Serial port protocol: Supports RS-232 / 422 / 485 standards, including baud rate setting, parity check, flow control, etc.; 3. Parallel port protocol: Supports IEEE 1284 standard, including SPP, EPP and ECP modes; 4. SCSI protocol: Supports SCSI-2 / 3 standards for storage device access; 5. Special instrument protocol: Supports GPIB / IEEE-488 and other instrument control protocols; 6. Encryption card protocol: Supports PKCS#11 and other security device access standards; For different types of protocols, the system adopts different encapsulation methods to ensure the preservation of protocol characteristics, while the system provides a plug-in mechanism to support the extension of new protocol types, improving the versatility and scalability of the system.

[0045] Embodiment 5: The I / O connection maintenance method during virtual machine migration includes the following steps: (I) Migration preparation: When it is detected that the virtual machine is about to be migrated, the virtual machine I / O client sends the current session state information to the I / O virtualization service, and the server persists the session information, the specific implementation includes: 1. Migration event detection: Identify the start of migration by listening to virtualization platform events or system signals; 2. Session state collection: Collect detailed state information of all active I / O connections; 3. State persistence: The server receives the state information and saves it to the persistent storage system; 4. Session marking: Mark the session to be migrated for subsequent recovery; 5. Resource reservation: Reserve necessary resources on the target server to prepare for session recovery after migration; (II) Connection freezing: During the actual migration of the virtual machine, the virtual machine I / O client suspends I / O operations and notifies the server to freeze the current session, and the server maintains device connection but suspends data transmission, the technical implementation includes: 1. Operation queuing: Put new I / O requests into the waiting queue and do not execute them; 2. In-process operation processing: Properly handle I / O operations in progress to ensure data consistency; 3. Safe point determination: Determine the safe pause point of I / O operations to avoid data corruption; 4. Session freezing notification: Send a freeze command to the server, which suspends the related session; 5. Device state maintenance: The server maintains device connection and state, waiting for the completion of virtual machine migration; (III) Migration completion detection: After the virtual machine migration is completed, the virtual machine I / O client restarts on the new physical host and detects the change in the network environment, the specific implementation includes: 1. System environment detection: Identify the network environment and system configuration on the new physical host; 2. Service discovery: Re-discover the network location of the I / O virtualization service; 3. Network path analysis: Analyze the network path and performance characteristics between the server and the client; 4. Migration state confirmation: Confirm that the virtual machine migration has been completed and the system is in a stable state; 5. Preparation for reconnection: Prepare for reconnection by loading necessary state information; (IV) Connection reestablishment: The virtual machine I / O client initiates a reconnection request to the I / O virtualization service using the saved session information, the server verifies the session information and restores the session state, the technical implementation includes: 1. Reconnection request sending: The client sends a reconnection request to the server, containing session identification and authentication information; 2. Session verification: The server verifies the legality of the request and the validity of the session information; 3. Resource allocation: The server reallocates necessary system resources for session recovery; 4. Connection parameter negotiation: The client and the server negotiate connection parameters such as transmission protocol, security options, etc; 5. Session recovery: The server loads session state from persistent storage and rebuilds session environment; (V) State synchronization: After successful reconnection, the client and the server perform state synchronization to ensure consistency of I / O device state, the specific implementation includes: 1. Device state query: The client obtains the current device state of the server; 2. State comparison: Compare the obtained state with the locally cached state; 3. Difference resolution: Handle state differences to ensure consistency; 4. Cache update: Update device state information in local cache; 5. Confirmation mechanism: The client confirms to the server that state synchronization is complete; (VI) Resume I / O operation: After completing state synchronization, resume normal I / O operation, the application can continue to access I / O devices, the technical implementation includes: 1. Queue processing: Process queued I / O requests during migration; 2. Operation priority adjustment: Adjust the execution order of I / O operations according to importance; 3. Application notification: Notify the application of I / O connection recovery if necessary; 4. Performance monitoring: Closely monitor the performance of I / O operations after recovery; 5. Exception handling: Handle exceptions that may occur during recovery; Key technical features of the entire migration process: 1. Transparency: Completely transparent to the upper layer application, the application does not need to be aware of the virtual machine migration event; 2. Data consistency: Ensure that data is not lost, duplicated or disordered during migration; 3. Fast recovery: Minimize I / O interruption time through state pre-saving and parallel processing; 4. Automation: The entire process is completed automatically without human intervention; 5. Reliability: With perfect exception handling mechanism, it ensures correct recovery under various abnormal situations; In addition, the system also implements the following advanced features: 1. Delayed migration: For critical I / O operations, the virtual machine migration time can be delayed to ensure operation completion; 2. Hierarchical recovery: Prioritize the connection of key devices to ensure rapid recovery of core business; 3. Batch migration support: Support I / O connection maintenance when multiple virtual machines are migrated simultaneously; 4. Cross-network domain migration: Support I / O connection recovery when virtual machines are migrated between different network domains.

[0046] Embodiment 6: Optimization techniques for data transmission in native I / O protocol pipeline: The encapsulation format of native I / O protocol data contains the following fields: 1. Magic Number: 4 bytes, fixed value 0x4E494F50 ("NI / OP" ASCII code), used to identify the start of the data packet; 2. Version number: 2 bytes, indicating the protocol version, currently 0x0100 (representing version 1.0); 3. Protocol type: 2 bytes, indicating the type of original I / O protocol, such as: 0x0001: USB protocol; 0x0002: Serial port protocol; 0x0003: Parallel port protocol; 0x0004: SCSI protocol; 0x0005: Encryption card protocol; 4. Session ID: 8 bytes, uniquely identifying the session between the virtual machine and the I / O device; 5. Sequence number: 4 bytes, unique sequence number for each data packet, used for sorting and deduplication; 6. Timestamp: 8 bytes, recording the time when the data packet is generated, used for timing control and timeout processing; 7. Flag bits: 4 bytes, containing various control flags: Bit 0: Whether to require confirmation (ACK); Bit 1: Whether it is a control packet; Bit 2: Whether it is the last fragment; Bit 3: Whether to use compression; Bit 4: Whether it is a retransmission packet; Other bits are reserved; 8. Data Length: 4 bytes, identifies the length of the valid data; 9. Raw Data: variable length, contains the complete content of the original I / O protocol; 10. Checksum: 4 bytes, calculated using CRC32 algorithm for the entire data packet.

[0047] This encapsulation format takes the following factors into consideration: 1. Integrity: Ensures the integrity and correctness of the data packet through magic number and checksum; 2. Protocol Identification: Identifies different types of I / O protocols through the protocol type field; 3. Session Management: Associates the connection between the virtual machine and the I / O device through the session ID; 4. Timing Control: Maintains the timing characteristics of the original I / O protocol through the timestamp and sequence number; 5. Extensibility: Reserves enough fields to support future functional extensions.

[0048] Multi-path Network Transmission: To improve transmission reliability and performance, the system implements a multi-path network transmission mechanism: 1. Path Discovery: The system automatically discovers multiple network paths between the client and the server, including different network interfaces and different routing paths; 2. Path Evaluation: Each path is evaluated for performance, measuring key indicators such as delay, bandwidth, and packet loss rate, and the evaluation results are used for path selection and load distribution; 3. Transmission Strategy: Based on data characteristics and path performance, the system supports multiple transmission strategies: a. Single-path mode: Only the best-performing path is used for transmission; b. Replication mode: Important data is transmitted simultaneously through multiple paths to improve reliability; c. Split mode: Data is transmitted on multiple paths to improve overall throughput; d. Backup mode: Mainly uses one path, and automatically switches to the backup path when the main path fails; 4. Adaptive Adjustment: The system continuously monitors the performance of each path and dynamically adjusts the transmission strategy and load distribution: a. When network congestion is detected, automatically reduce the usage proportion of that path; b. When path performance fluctuates, adjust the weight of each path; c. When the path is completely interrupted, immediately switch traffic to the available path; 5. Data Reassembly: The receiving end collects data fragments from different paths, reassembles them into a complete data stream according to the sequence number, and handles possible duplicate packets and out-of-order packets; This multi-path transmission mechanism has the following advantages: 1. Improves system reliability, even if part of the network path fails, the system can still work normally; 2. Improves overall throughput, fully utilizes the bandwidth resources of multiple network paths; 3. Reduces end-to-end delay, can choose the lowest delay path for time-sensitive I / O operations; 4. Enhances the adaptability of the system, able to cope with changes and fluctuations in the network environment.

[0049] Data transmission optimization techniques: In addition to the above packaging format and multi-path transmission, the system also implements the following data transmission optimization techniques: 1. Data compression: compresses the original I / O data to reduce network transmission volume. The system supports multiple compression algorithms and automatically selects the optimal algorithm based on data characteristics: For text data, use LZ77 or DEFLATE algorithm; For binary data, use Huffman encoding or LZO algorithm; For real-time data streams, use lightweight compression algorithms such as Snappy; 2. Flow control: implements a sliding window-based flow control mechanism to avoid the sender's data from causing the receiver's buffer to overflow: The receiver informs the sender of the current amount of data that can be received through feedback messages; The sender adjusts the sending rate dynamically based on the receiver's window size; When the network is congested, automatically reduce the window size, when the network is good, gradually increase the window size; 3. Batch processing and merging: combines multiple small I / O operations into a batch request to reduce network interaction times: For continuous small data block read-write operations, merge into a large block operation; For frequent status query operations, implement batch query mechanism; For command sequences, merge into a single composite command; 4. Prefetching and caching: based on I / O access patterns, pre-fetch data that may be needed: Sequential access prefetching: detects sequential read patterns and pre-fetches subsequent data blocks; Pattern recognition: learns the application's access patterns and predicts future I / O operations; Hot data caching: keeps frequently accessed data in local cache; 5. Priority and QoS: implements differentiated service quality guarantee mechanism: Different priorities are assigned to different types of I / O operations; Low latency and high reliability are guaranteed for high-priority operations; When network resources are limited, the performance requirements of critical services are prioritized; These optimization techniques are applied comprehensively, significantly improving the performance and efficiency of the native I / O protocol pipeline, making networked I / O device access close to local device access in terms of performance.

[0050] Embodiment 7: Security mechanisms and multi-tenant support technology of the system: Security mechanisms The system implements a comprehensive security mechanism to ensure the security of I / O device access and the confidentiality of data: 1. Identity authentication and authorization: Multi-factor authentication: Supports multiple authentication methods based on certificates, passwords, tokens, etc. Fine-grained authorization: Role-based access control (RBAC) assigns different access permissions to different users; Centralized authentication: Supports integration with existing authentication systems (such as LDAP, Active Directory) of enterprises; Session management: Implement session timeout, concurrency limit and other security measures; 2. Data transmission security: Transmission encryption: Use TLS 1.3 or higher for data transmission encryption; Integrity protection: Ensure data integrity through algorithms such as HMAC; Anti-replay attack: Use timestamps and sequence numbers to prevent data packet replay; Secure key management: Automatic key negotiation and regular key rotation; 3. Data security: Storage encryption: Encrypt sensitive data stored in persistent storage; Memory protection: Protection mechanism to prevent memory data leakage; Secure erasure: Secure erasure mechanism for sensitive data after use; Data leak prevention: Implement data leak prevention (DLP) policies to prevent sensitive data leakage; 4. Security audit and compliance: Comprehensive logging: Record all security-related events, including identity verification, authorization decisions, system configuration changes, etc. Log integrity: Ensure the integrity and non-tamperability of audit logs; Compliance report: Generate compliance reports that meet industry standards (such as PCI DSS, HIPAA); Anomaly Detection: Identifies potential security threats and abnormal access patterns; 5. Hardware Security Support: Trusted Execution Environment: Supports Intel SGX, ARM TrustZone, etc. trusted execution environment; Hardware Security Module: Supports TPM and other hardware security modules to enhance key protection; Secure Boot: Ensures the integrity and authenticity of system components; Multi-tenancy Support Technology: The system implements a perfect multi-tenancy support mechanism, allowing multiple tenants (such as different business departments or different customers) to safely share I / O virtualization infrastructure: 1. Tenant Isolation: Network Isolation: Provides independent network namespaces for different tenants; Resource Isolation: Ensures that the activities of one tenant do not affect the performance of other tenants; Data Isolation: Prevents cross-tenant data access and information leakage; Control Plane Isolation: Provides each tenant with an independent management view and control interface; 2. Resource Allocation and Scheduling: Resource Quota: Allocates explicit resource quotas to each tenant, including device quantity, bandwidth limit, etc.; Priority Policy: Supports resource priority settings between tenants to ensure that critical business is prioritized; Dynamic Resource Adjustment: Dynamically adjusts resource allocation based on actual tenant demand and system load; Resource Reservation: Supports reserving necessary resources for key tenants to ensure performance guarantees; 3. Device Sharing Model: Exclusive Mode: Certain devices are exclusively used by a specific tenant to ensure maximum performance and security; Time-sharing: Multiple tenants use the same device in time slices, suitable for low-frequency access scenarios; Concurrent Sharing: Multiple tenants access the same device simultaneously, and the system is responsible for request scheduling and isolation; Partition Sharing: Logical partitioning of device resources, with different tenants using different partitions, such as different LUNs of storage devices; 4. Tenant Management: Tenant Lifecycle: Supports full lifecycle management of tenants, including creation, configuration, suspension, and deletion; Tenant Template: Provides predefined tenant templates to simplify the creation process of new tenants; Tenant Migration: Supports migrating tenants and their resources from one physical environment to another; Tenant Monitoring: Provides performance monitoring and resource usage reporting at the tenant level; 5. Multi-Tenant Performance Guarantee: Performance Isolation: Ensures that high load of one tenant does not affect the performance of other tenants; QoS Guarantee: Provides differentiated service quality guarantee for different tenants; Performance Prediction: Predicts resource demand based on historical data and makes resource adjustments in advance; Elastic Scaling: Supports automatic expansion and contraction of tenant resources; Embodiment 8: Cluster management and high availability guarantee technology in multi-server deployment scenarios; Cluster Architecture: The system supports multi-server cluster deployment, improving the scalability and reliability of the system: 1. Cluster Topology: Central and radial type: one master node is responsible for coordination, and multiple slave nodes are responsible for specific I / O device connection and processing; Peer-to-peer network type: all nodes are equal, jointly maintain the global state, and any node can accept client requests; Hybrid type: combines the advantages of the above two modes, part of the function is centrally managed, and part of the function is distributed processing; 2. Node Role: Control node: responsible for cluster management, resource scheduling and global strategy formulation; Data node: responsible for specific I / O device connection and data processing; Storage node: responsible for persistent storage of session information, configuration data, etc.; Monitoring node: responsible for cluster monitoring, performance analysis and alarm management; 3. Cluster Scale: Support linear expansion from several nodes to hundreds of nodes; Dynamic node joining and exiting without downtime; Heterogeneous node support, can integrate servers with different hardware configurations; Cluster Management: The system implements a perfect cluster management mechanism to ensure the cooperative work of multiple nodes: 1. Node discovery and registration: Automatic discovery: new nodes automatically discover and join the existing cluster after startup; Manual registration: supports administrators to manually add new nodes; Health check: conducts comprehensive health check on new nodes to ensure compliance with the joining conditions; Resource inventory: new nodes report their available resources when joining, which are used for global resource scheduling; 2. State synchronization and consistency: State replication: Key state information is replicated across multiple nodes to ensure consistency. Consistency protocol: Use consensus algorithms such as Raft or Paxos to handle distributed state updates. Incremental synchronization: Support incremental state synchronization to reduce network transmission. Conflict resolution: When state conflicts occur, resolve them through predefined rules or arbitration mechanisms. 3. Task distribution and load balancing: Load monitoring: Real-time monitoring of node load conditions, including CPU, memory, network, etc. Task distribution: Distribute new I / O device connection requests to appropriate nodes based on node load. Dynamic adjustment: Dynamically adjust task allocation during operation to optimize overall system load. Affinity consideration: Consider the location relationship between virtual machines and I / O devices, and prefer nodes with the shortest network path. 4. Cluster configuration management: Centralized configuration: Global configuration information is centrally managed and distributed. Version control: Configuration change version control and rollback capabilities. Dynamic reconfiguration: Support updating cluster configuration without interrupting service. Differential configuration: Support node-level differential configuration to adapt to the characteristics of different nodes. High availability mechanism: The system implements multiple levels of high availability guarantee mechanisms to ensure service continuity: 1. Node-level fault handling: Heartbeat detection: Periodically detect node health status through heartbeats. Fault detection: Use multiple detection mechanisms to accurately identify node failures. Automatic recovery: For recoverable faults, the system automatically performs recovery operations. Isolation mechanism: Isolate faulty nodes to prevent affecting other nodes. 2. Service-level failover: Hot backup: Key services are kept in hot backup state on multiple nodes. Automatic switching: When the primary node fails, automatically switch to the backup node. Stateless design: Service design adopts stateless mode for easy switching. Session preservation: Maintain user session continuity during fault switching. 3. Data redundancy and protection: Multi-copy storage: Important data is kept in multiple copies across multiple nodes; Data verification: Regularly perform data consistency verification to find and repair damage; Incremental backup: Regularly perform incremental backup to ensure data recoverability; Disaster recovery: Support cross-data center disaster recovery capabilities; 4. Smooth scaling: Online scaling: Support adding new nodes without interrupting service; Safe scaling: Support safe removal of nodes, including task migration and data transfer; Automatic rebalancing: Automatically rebalance system load after node changes; Gradual migration: Large-scale data migration uses a gradual approach to reduce system impact; 5. Fault self-healing capabilities: Automatic diagnosis: System can automatically diagnose common fault types; Automatic repair: For automatically repairable faults, the system performs repair operations; Self-adjustment: Automatically adjust system parameters based on operating conditions to improve stability; Preventive maintenance: Based on predictive analysis, perform preventive maintenance before faults occur; Through these cluster management and high availability technologies, the system ensures the reliability and continuity of services while providing high-performance I / O virtualization services, meeting the needs of enterprise key business; Through these multi-tenant support technologies, the system can safely and efficiently support multiple business departments or customers' I / O device access requirements on a single physical infrastructure, significantly improving resource utilization and management efficiency.

[0051] Embodiment 9: Performance evaluation indicators: The system defines a series of key performance indicators to evaluate the performance and efficiency of the system: 1. Latency indicators: End-to-end delay: The total time from the client initiating an I / O request to receiving a response; Protocol processing delay: The time required for native I / O protocol conversion and processing; Network transmission delay: The time required for data transmission in the network; Device operation delay: The time required for physical I / O devices to perform operations; 2. Throughput indicators: Single device throughput: The data transmission rate of a single I / O device; System total throughput: The data processing capacity of the entire system; Concurrent Connections: The number of virtual machine connections that the system can handle simultaneously. Concurrent Operations: The number of I / O operations that the system can handle simultaneously. 3. Resource Utilization: CPU Utilization: The CPU resource usage of each component in the system. Memory Utilization: The memory resource usage of each component in the system. Network Bandwidth Utilization: The network resource usage of the system. I / O Device Utilization: The efficiency of physical I / O device usage. 4. Reliability Indicators: Mean Time Between Failures (MTBF): The average time that the system runs continuously without failure. Mean Time to Recover (MTTR): The average time for the system to recover from a failure state to a normal state. Failure Rate: The frequency of system failures within a specific time period. Data Integrity: The error rate and loss rate during data transmission. 5. Scalability Indicators: Linear Expansion Coefficient: The degree of performance improvement when increasing system resources. Maximum Device Support: The maximum number of physical I / O devices that the system can support. Maximum Virtual Machine Support: The maximum number of virtual machine connections that the system can support. Resource Increase Benefit: The degree of impact on system performance when increasing specific resources. Performance Optimization Techniques: The system implements multi-level performance optimization techniques to improve overall system performance: 1. Protocol Layer Optimization: Protocol Simplification: Remove unnecessary protocol fields and processing steps. Batch Processing Mechanism: Combine multiple small operations into a batch request. Asynchronous Processing: Support asynchronous I / O operations to improve concurrent processing capability. Preprocessing Techniques: Preprocess and optimize common operation sequences. 2. Data Transmission Optimization: Zero-Copy Technology: Reduce the number of data copies in memory. Vector I / O: Support scatter-gather data transmission to reduce system call frequency. Data Alignment: Ensure data alignment in memory to improve access efficiency. Buffer Management: Optimize buffer size and allocation strategy. 3. Memory Management Optimization: Memory Pool Technology: Utilize pre-allocated memory pools to reduce dynamic memory allocation overhead; NUMA Awareness: Consider NUMA architecture characteristics in multi-processor systems; Cache Optimization: Reasonably use CPU cache to improve data access speed; Memory Pre-allocation: Pre-allocate memory resources for critical operations; 4. Concurrent Processing Optimization: Multi-threaded Architecture: Adopt an efficient multi-threaded processing model; Task Scheduling: Optimize task allocation and scheduling strategies; Lock Optimization: Reduce lock contention and use lock-free data structures; Event-driven: Use an event-driven model to handle I / O events; 5. Algorithm Optimization: Fast Path: Provide optimized processing paths for common operations; Indexing Technology: Use efficient index structures to speed up searches; Heuristic Prediction: Predict future operations based on historical data; Algorithm Complexity Control: Control algorithm complexity on critical paths; Performance Tuning Methods: The system provides a complete set of performance tuning methods to optimize system performance in different deployment environments: 1. Performance Analysis Tools: Built-in Performance Monitoring: The system has built-in comprehensive performance monitoring functions; Analysis Dashboard: Visualize performance indicators of each component of the system; Bottleneck Identification: Automatically identify performance bottlenecks in the system; Historical Trend Analysis: Support historical trend analysis of performance data; 2. Adaptive Optimization: Parameter Self-adjustment: The system automatically adjusts key parameters based on operating conditions; Load Awareness: Dynamically adjust resource allocation based on system load; Behavior Learning: Learn the access patterns of the application program and optimize the processing flow; Feedback Mechanism: Continuously optimize system configuration based on performance feedback; 3. Targeted Optimization: Device Specialization: Provide specialized optimization for specific types of I / O devices; Application Scenario Optimization: Customize optimization strategies based on different application scenarios; Hardware Adaptation: Optimize system performance for different hardware platforms; Network Environment Adaptation: Adjust transmission strategies based on network environment characteristics; 4. Benchmarking and comparison: Standard test set: Define standard test scenarios and workloads; Performance baseline: Establish system performance baseline for comparison of different versions and configurations; Comparative analysis: Compare performance with direct physical connection method; Regression testing: Ensure that system optimization does not introduce new performance problems; Through these performance evaluation and optimization techniques, the system can maintain the characteristics of the native I / O protocol while providing performance experience close to direct physical connection, meeting the needs of performance-sensitive applications.

[0052] The above shows and describes the basic principles, main features and advantages of the present application. Those skilled in the art should understand that the present application is not limited to the above examples, and the above examples and descriptions in the specification are only to illustrate the principles of the present application. Without departing from the spirit and scope of the present application, various changes and improvements can be made to the present application, and these changes and improvements all fall within the scope of the claimed present application.

Claims

1. A method for accessing network I / O devices based on native protocols in a virtualized environment, characterized in that, Includes the following steps: S1: Deploy I / O virtualization services on physical servers to connect physical I / O devices and provide device registration, session management and protocol adaptation services; S2: Install a virtual machine I / O client in the virtual machine to provide standard I / O device interfaces to upper-layer applications and establish network connections with the I / O virtualization service; S3: Establish a native I / O protocol pipeline between the I / O virtualization service and the virtual machine I / O client, which maintains the complete characteristics of the original I / O protocol; S4: Transmit I / O device data through the native I / O protocol pipe to achieve transparent access of the virtual machine to the physical I / O device; S5: During virtual machine migration, maintain I / O session state and rebuild network connections to ensure business continuity.

2. The method for accessing network I / O devices based on native protocols in a virtualized environment according to claim 1, characterized in that, The method for establishing a native I / O protocol pipeline includes identifying the protocol characteristics of physical I / O devices, encapsulating the original I / O protocol into a network transmission protocol, maintaining the integrity of the original protocol, and decapsulating the encapsulated data at the receiving end to restore the original I / O protocol data.

3. The method for accessing network I / O devices based on native protocols in a virtualized environment according to claim 1, characterized in that, The method for maintaining I / O connectivity during virtual machine migration includes: Before migration, the current session state information is sent to the I / O virtualization service and persistently saved. I / O operations are paused and the current session is frozen during the migration process; After the migration is complete, the virtual machine I / O client sends a reconnection request to the I / O virtualization service; The server verifies the session information and restores the session state; The client and server synchronize their states to ensure consistency of I / O device states; Resume normal I / O operations to ensure business continuity.

4. A method for accessing network I / O devices based on native protocols in a virtualized environment according to any one of claims 1-3, characterized in that, The I / O virtualization service implements the following functions: Automatic discovery, registration, and status monitoring of physical I / O devices; Adaptation to multiple I / O protocols while preserving native features; Establishment and maintenance of connection sessions between virtual machines and I / O devices; Persistent storage of session information and state synchronization; Security control and authentication for device access.

5. A method for accessing network I / O devices based on native protocols in a virtualized environment according to any one of claims 1-3, characterized in that, The virtual machine I / O client implements the following functions: Provides standard I / O device interfaces to upper-layer applications; Convert the application's I / O requests into a network transmission format; Establish and maintain network connections with I / O virtualization services; Reduce network access and improve response speed by using local caching; Detect network connection failures and implement an automatic reconnection mechanism.

6. A network access system for native protocol I / O devices in a virtualized environment, characterized in that, include: I / O virtualization services are deployed on physical servers to connect physical I / O devices and provide networked I / O services; Virtual machine I / O client, deployed within a virtual machine, is used to provide standard I / O interfaces to applications and communicate with I / O virtualization services; Native I / O protocol pipe: A network transmission channel established between the server and the client that maintains the characteristics of the original I / O protocol; The session management module is used to maintain the device connection status and support connection recovery after virtual machine migration.

7. A network access system for network I / O devices based on native protocols in a virtualized environment according to claim 6, characterized in that, The I / O virtualization service includes a device management module, a protocol adaptation engine, a session manager, a network transmission module, a security control module, a device resource scheduling module, and a cluster management module.

8. A network access system for network I / O devices based on native protocols in a virtualized environment according to claim 7, characterized in that, The virtual machine I / O client includes a device interface layer, a protocol conversion layer, a session connection manager, a local cache module, a fault detection and recovery module, a performance optimization module, and a monitoring and diagnostic module.

9. A network access system for network I / O devices based on native protocols in a virtualized environment according to claim 8, characterized in that, The system also includes a device simulation module, which maintains the normal operation of the application by simulating device behavior when physical I / O devices are temporarily unavailable.

10. A network access system for network I / O devices based on native protocols in a virtualized environment according to claim 9, characterized in that, The system supports multipath transmission at the network transport layer and improves system reliability by establishing redundant network connections.

Images