# US 12,001,870 B2 · Injection and execution of workloads into virtual machines > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,001,870 B2 - Document ID: US12001870B2 - Status: Granted - Kind: B2 - Application number: 17/214,108 - Filed: 2021-03-26 - Published: 2022-09-29 - Granted: 2024-06-04 - Earliest claimed: 2021-03-26 - Assignees: Red Hat, Inc. - Applicants: Red Hat, Inc. - Inventors: Cleber Rosa Junior - Web page: https://patentgrep.com/patent/US12001870B2 ## CPC - G06F 9/45558: {Hypervisor-specific management and integration aspects} - G06F 9/5027: {the resource being a machine, e.g. CPUs, Servers, Terminals} - G06F 9/505: {considering the load} - G06F 9/5077: {Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455)} - G06F 2009/4557: {Distribution of virtual machine instances; Migration and load balancing} - G06F 2009/45575: {Starting, stopping, suspending or resuming virtual machine instances} - G06F 2009/45595: {Network integration; Enabling network access in virtual machine instances} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A system includes a processor in communication with a memory, a virtual machine running on the processor, and a hypervisor. The hypervisor is configured to receive a workload definition file (“WDF”). The WDF is associated with a workload, and the WDF is packaged such that the WDF is configured to generate a workload definition device (“WDD”). Additionally, the hypervisor is configured to receive a request to deploy the WDD within the virtual machine. The request includes the WDF. The hypervisor is also configured to deploy the WDD within the virtual machine. The WDD is configured to automatically execute the workload responsive to meeting at least one execution criteria. ## Claims ### Claim 1 A system comprising: a processor in communication with a memory; a virtual machine running on the processor; and a hypervisor configured to: receive a workload definition file (“WDF”), wherein the WDF is associated with a workload, and the WDF is packaged such that the WDF is configured to generate a workload definition device (“WDD”); receive a request to deploy the WDD within the virtual machine, wherein the request includes the WDF, wherein the virtual machine is a pre-existing virtual machine that is running at a time the request is received, and wherein the virtual machine is in an initial state at the time the request is received; and deploy the WDD within the virtual machine, wherein the WDD is configured to automatically execute the workload responsive to meeting at least one execution criteria wherein the hypervisor is configured to deploy the WDD within the virtual machine by: locating the virtual machine according to the request, and attaching the WDD to the virtual machine, wherein the virtual machine is in a workload execution state after the WDD is attached. ### Claim 2 (depends on 1) The system of claim 1, wherein the WDD is configured to automatically execute without further interaction between an agent and the WDD. ### Claim 3 (depends on 2) The system of claim 2, wherein the agent is at least one of the hypervisor, an owner of the virtual machine, and a proxy representing a client or customer. ### Claim 4 (depends on 1) The system of claim 1, wherein the WDD is an output device. ### Claim 5 (depends on 4) The system of claim 4, wherein the WDD is configured to: record an output generated by the workload; and send the output to a receiver. ### Claim 6 (depends on 1) The system of claim 1, wherein the WDD is a block device with a file system containing at least one executable and at least one supporting file. ### Claim 7 (depends on 1) The system of claim 1, wherein the at least one execution criteria includes at least one of (i) the WDD is a first type, (ii) the WDD includes a predetermined identifier marking the WDD as a workload candidate, (iii) the WDD includes a file system having authentication data that binds the WDD to the virtual machine, and (iv) the WDD includes a workload executable entry point. ### Claim 8 (depends on 1) The system of claim 1, wherein the WDD is configured to close responsive to the workload completing execution. ### Claim 9 A method comprising: receiving, by a hypervisor, a workload definition file (“WDF”), wherein the WDF is associated with a workload, and the WDF is packaged such that the WDF is configured to generate a workload definition device (“WDD”); receiving, by the hypervisor, a request to deploy the WDD within a virtual machine, wherein the request includes the WDF, wherein the virtual machine is a pre-existing virtual machine that is running at a time the request is received, and wherein the virtual machine is in an initial state at the time the request is received; and deploying, by the hypervisor, the WDD within the virtual machine, wherein the WDD is configured to automatically execute the workload responsive to meeting at least one execution criteria, wherein deploying, by the hypervisor, the WDD within the virtual machine includes: locating, by the hypervisor, the virtual machine, according to the request, and attaching, by the hypervisor, the WDD to the virtual machine, wherein the virtual machine is in a workload execution state after the WDD is attached. ### Claim 10 (depends on 9) The method of claim 9, wherein deploying the WDD within the virtual machine includes: creating, by the hypervisor, the virtual machine according to the request, and attaching, by the hypervisor, the WDD to the virtual machine. ### Claim 11 (depends on 10) The method of claim 10, further comprising: responsive to the workload completing execution, closing the WDD; and shutting down, by the hypervisor, the virtual machine after the WDD closes. ### Claim 12 (depends on 9) The method of claim 9, further comprising: responsive to the workload completing execution, closing the WDD; and restoring the virtual machine back to the initial state. ### Claim 13 (depends on 12) The method of claim 12, further comprising: receiving, by the hypervisor, a second request to deploy a second WDD within the virtual machine; confirming, by the hypervisor, the virtual machine is in the initial state; and deploying, by the hypervisor, the second WDD within the virtual machine. ### Claim 14 (depends on 9) The method of claim 9, wherein the hypervisor deploys the WDD and the WDD automatically executes without further interaction between an agent and the WDD. ### Claim 15 (depends on 14) The method of claim 14, wherein the agent is at least one of the hypervisor, an owner of the virtual machine, and a proxy representing a client or customer. ### Claim 16 (depends on 9) The method of claim 9, further comprising: recording, by the WDD, an output generated by the workload; and sending, by the WDD, the output to a receiver. ### Claim 17 (depends on 9) The method of claim 9, wherein the at least one execution criteria includes at least one of (i) the WDD is a first type, (ii) the WDD includes a predetermined identifier marking the WDD as a workload candidate, (iii) the WDD includes a file system having authentication data that binds the WDD to the virtual machine, and (iv) the WDD includes a workload executable entry point. ### Claim 18 (depends on 9) The method of claim 9, further comprising: responsive to the workload completing execution, closing the WDD; and shutting down, by the hypervisor, the virtual machine after the WDD closes. ### Claim 19 A non-transitory machine-readable medium storing code, which when executed by a processor is configured to: receive a workload definition file (“WDF”), wherein the WDF is associated with a workload, and the WDF is packaged such that the WDF is configured to generate a workload definition device (“WDD”); receive a request to deploy the WDD within a virtual machine, wherein the request includes the WDF, wherein the virtual machine is a pre-existing virtual machine that is running at a time the request is received, and wherein the virtual machine is in an initial state at the time the request is received; and deploy the WDD within the virtual machine, wherein the WDD is configured to automatically execute the workload responsive to meeting at least one execution criteria, wherein deploy the WDD within the virtual machine includes: locate the virtual machine, according to the request, and attach the WDD to the virtual machine, wherein the virtual machine is in a workload execution state after the WDD is attached.