View source for Intel corporation (20240211297). METHOD FOR A PRIMARY VIRTUAL MACHINE TO SCHEDULE A TASK OF SIBLING VIRTUAL MACHINES simplified abstract

=METHOD FOR A PRIMARY VIRTUAL MACHINE TO SCHEDULE A TASK OF SIBLING VIRTUAL MACHINES=


==Organization Name==

[[:Category:intel corporation|intel corporation]]


[[Category:intel corporation]]

==Inventor(s)==

[[:Category:Zhao Liu of Shanghai (CN)|Zhao Liu of Shanghai (CN)]][[Category:Zhao Liu of Shanghai (CN)]]

[[:Category:Zhenyu Wang of Shanghai CA (US)|Zhenyu Wang of Shanghai CA (US)]][[Category:Zhenyu Wang of Shanghai CA (US)]]

==METHOD FOR A PRIMARY VIRTUAL MACHINE TO SCHEDULE A TASK OF SIBLING VIRTUAL MACHINES - A simplified explanation of the abstract==


This abstract first appeared for US patent application 20240211297 titled 'METHOD FOR A PRIMARY VIRTUAL MACHINE TO SCHEDULE A TASK OF SIBLING VIRTUAL MACHINES

'''Simplified Explanation''': 

The patent application describes a method for a primary virtual machine (VM) to schedule a task for a sibling VM executed by a hypervisor. The primary VM communicates with the hypervisor to create a sibling task and a broker task, which are then executed based on instructions from the scheduler.

* The primary VM schedules a task for a sibling VM executed by a hypervisor.
* The hypervisor creates a sibling task with a unique ID and communicates it to the primary VM.
* The primary VM creates a broker task based on the received sibling task ID.
* The primary VM communicates a mapping of the broker ID to the corresponding hypervisor ID to the hypervisor.
* The primary VM executes the broker task when instructed by the scheduler, triggering the hypervisor to run the sibling task based on the mapping.

'''Key Features and Innovation''':

* Efficient task scheduling between primary and sibling VMs.
* Clear communication and coordination between the primary VM, hypervisor, and scheduler.
* Streamlined process for executing tasks based on unique IDs.

'''Potential Applications''':

This technology can be applied in cloud computing environments, virtualization systems, and distributed computing platforms where efficient task scheduling is crucial.

'''Problems Solved''':

This technology addresses the challenge of coordinating tasks between primary and sibling VMs in a virtualized environment, ensuring smooth execution and optimal resource utilization.

'''Benefits''':

* Improved performance and resource management in virtualized environments.
* Enhanced scalability and flexibility in task scheduling.
* Streamlined communication and coordination between VMs and hypervisors.

'''Commercial Applications''''':

Potential commercial applications include cloud service providers, data centers, and enterprises utilizing virtualization technologies for efficient task management and resource allocation.

'''Prior Art''':

Readers can explore prior research on virtual machine task scheduling, hypervisor communication, and task coordination in virtualized environments to understand the background of this technology.

'''Frequently Updated Research''':

Researchers are constantly exploring new methods and technologies to enhance task scheduling and resource management in virtualized environments. Stay updated on the latest advancements in cloud computing and virtualization technologies for more insights.

'''Questions about Virtual Machine Task Scheduling''':

1. What are the key challenges in coordinating tasks between primary and sibling VMs in virtualized environments?
2. How does this technology improve resource utilization and performance in cloud computing environments?


==Original Abstract Submitted==

a method for a primary virtual machine (vm) to schedule a sibling vm task executed by a hypervisor. upon request of the sibling vm, the hypervisor creates a sibling task which includes a hypervisor id. the hypervisor id is then communicated to the primary vm. subsequently, the primary vm creates a broker task, identified by its broker id, and based on the received hypervisor id for the sibling vm task. the primary vm then communicates to the hypervisor a mapping of the broker id to the corresponding hypervisor id. finally, the primary vm executes the broker task when instructed by a scheduler of the primary vm. the broker task then triggers the hypervisor to run the corresponding sibling task based on the mapping.



[[Category:G06F9/455]]
[[Category:CPC_G06F9/45558]]