Cloud computer startup method and device

Abstract

The present application discloses a cloud computer startup method and device, including: obtaining a startup request, and triggering a preset number of cloud computers to start up according to the startup request until the cloud computers stop starting when they are in a preset startup phase, thereby obtaining a corresponding preset number of cloud computers to be started; wherein, the preset startup phase is the phase from the start of the cloud computer startup to the completion of the startup; based on the resource scheduling request of the terminal, determining the target cloud computer from the cloud computers to be started, and triggering the target cloud computer to continue starting up, so as to use the successfully started target cloud computer to respond to the resource scheduling request. In this application, when the user has not yet requested a cloud computer environment, the cloud computer is pre-started and paused in the preset startup phase. When the user issues a resource scheduling request, the paused cloud computer is started again to achieve network connection. The above-mentioned method of pre-starting the cloud computer can greatly shorten the user's streaming scheduling speed and startup waiting time, thereby improving scheduling and connection efficiency.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a cloud computer startup method and device. Background Art

[0002] Cloud diskless and cloud computing technologies typically don't use a physical hard drive as a boot disk (drive C). Instead, they use a network drive as the boot disk. This creates a problem: diskless boot speeds can be slower than SSDs. In cloud computing environments, user wait times can be as long as 40 to 90 seconds, or even longer. Users can't quickly connect to cloud computing and enjoy cloud services, resulting in a poor user experience.

[0003] Therefore, how to shorten the boot waiting time of a cloud computer to improve the user experience is a technical problem that needs to be solved urgently by those skilled in the art. Summary of the Invention

[0004] In view of this, the purpose of the present invention is to provide a cloud computer startup method, device, equipment and storage medium, which can shorten the cloud computer startup waiting time and improve the user experience. The specific solution is as follows:

[0005] A first aspect of the present application provides a cloud computer startup method, comprising:

[0006] Obtaining a startup request, and triggering a preset number of cloud computers to start according to the startup request until the cloud computers stop starting when they are in a preset startup phase, thereby obtaining a corresponding preset number of cloud computers to be started; wherein the preset startup phase is the phase from the start of cloud computer startup to the completion of startup;

[0007] Based on the resource scheduling request of the terminal, a target cloud computer is determined from the cloud computers to be started, and the target cloud computer is triggered to continue to start, so as to respond to the resource scheduling request by using the successfully started target cloud computer.

[0008] Optionally, the cloud computer startup method further includes:

[0009] Determine the time required for the cloud computer to enter the desktop after startup and / or determine the number of processes running in the cloud computer after startup;

[0010] It is determined whether the required time is less than the preset time and / or whether the number of processes is less than the preset number. If so, the current stage of the cloud host is determined to be the preset startup stage.

[0011] Optionally, after obtaining the power-on request, the method further includes:

[0012] Determine the current time period, and dynamically determine a preset number of cloud computers corresponding to the current time period from all cloud computers according to preset rules.

[0013] Optionally, the cloud computer startup method further includes:

[0014] Determining cloud computers with a pre-start function as candidate cloud computers, and determining a preset number of cloud computers from the candidate cloud computers;

[0015] The cloud computer without the pre-start function is determined as an ordinary cloud computer, and the ordinary cloud computer is started up in a diskless startup manner.

[0016] Optionally, the cloud computer startup method further includes:

[0017] Determining, based on a preset field in a data packet transmitted by the Dynamic Host Configuration Protocol, whether the cloud computer has a pre-open switch and whether the pre-open switch is in a closed state;

[0018] If so, it is determined that the cloud computer has a pre-start function.

[0019] Optionally, before triggering the target cloud computer to continue booting, the method further includes:

[0020] The IP address, subnet mask, gateway, and host name of the target cloud computer are modified and the VLAN network is re-divided so that the network between the modified target cloud computer and the corresponding terminal can be interconnected.

[0021] Optionally, the cloud computer startup method further includes:

[0022] Determining whether the target host is successfully started by determining whether the target host has detected the reporting information of entering the desktop;

[0023] If the reporting information is not detected, the startup fails, and the target host that fails to start is recycled.

[0024] Optionally, the cloud computer startup method further includes:

[0025] The cloud computer to be started is connected to the server by a heartbeat connection, and the cloud host to be started with abnormal heartbeat connection is recycled.

[0026] Optionally, the cloud computer startup method further includes:

[0027] Monitor the cloud host after startup;

[0028] When it is detected that the cloud host is running the wininit process, this stage is determined as the preset startup stage and the cloud host is stopped from starting.

[0029] A second aspect of the present application provides a cloud computer startup device, comprising:

[0030] A pre-startup module is configured to obtain a startup request and trigger a preset number of cloud computers to start starting according to the startup request until the cloud computers stop starting when they are in a preset startup phase, thereby obtaining a corresponding preset number of cloud computers to be started; wherein the preset startup phase is the phase from the start of cloud computer startup to the completion of startup;

[0031] The scheduling response module is used to determine the target cloud computer from the cloud computers to be started based on the terminal's resource scheduling request, and trigger the target cloud computer to continue starting, so as to use the successfully started target cloud computer to respond to the resource scheduling request.

[0032] A third aspect of the present application provides an electronic device, comprising a processor and a memory; wherein the memory is used to store a computer program, and the computer program is loaded and executed by the processor to implement the aforementioned cloud computer startup method.

[0033] The fourth aspect of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are loaded and executed by a processor, the aforementioned cloud computer startup method is implemented.

[0034] In this application, a startup request is first obtained, and a preset number of cloud computers are triggered to start according to the startup request until the cloud computers are in the preset startup phase and stop starting, thereby obtaining a corresponding preset number of cloud computers to be started; wherein, the preset startup phase is the phase from the start of the cloud computer startup to the completion of the startup; then, based on the resource scheduling request of the terminal, a target cloud computer is determined from the cloud computers to be started, and the target cloud computer is triggered to continue starting, so as to use the successfully started target cloud computer to respond to the resource scheduling request. It can be seen that this application pre-starts the cloud computer and pauses it in the preset startup phase before the user requests the cloud computer environment. When the user issues a resource scheduling request, the paused cloud computer is started again to achieve network connection. The above-mentioned method of pre-starting the cloud computer can greatly shorten the user's streaming scheduling speed and boot waiting time, thereby improving the scheduling and connection efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are merely embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0036] Figure 1 A flow chart of a cloud computer startup method provided in this application;

[0037] Figure 2 A schematic diagram of the structure of a cloud computer startup device provided in this application;

[0038] Figure 3 This is a structural diagram of a cloud computer startup electronic device provided in this application. DETAILED DESCRIPTION

[0039] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0040] In existing technologies, diskless boot speeds can be slower than SSDs. In cloud computing environments, users can wait for 40 to 90 seconds, or even longer. Users cannot quickly connect to cloud computing and enjoy cloud services, resulting in a very poor user experience. To address these technical deficiencies, this application provides a cloud computing startup solution that significantly reduces user streaming scheduling speed and startup waiting time by pre-starting the cloud computing, thereby improving scheduling and connectivity efficiency.

[0041] Figure 1 This is a flow chart of a cloud computer startup method provided by an embodiment of the present application. Figure 1 As shown, the cloud computer startup method includes:

[0042] S11: Obtain a startup request, and trigger a preset number of cloud computers to start according to the startup request until the cloud computers stop starting when they are in a preset startup phase, thereby obtaining a corresponding preset number of cloud computers to be started; wherein, the preset startup phase is the phase from the start of cloud computer startup to the completion of startup.

[0043] In this embodiment, a startup request is obtained, and based on the startup request, a preset number of cloud computers are triggered to start up until the cloud computers reach a preset startup phase, thereby stopping startup and obtaining a corresponding preset number of cloud computers to be started. The preset startup phase is the period from the start of cloud computer startup to its completion. To balance energy consumption and user access expectations, this embodiment enables dynamic pre-startup, dynamically adjusting the number of pre-started cloud computers based on different time periods. Specifically, after receiving the startup request, the current time period is further determined, and a preset number of cloud computers corresponding to the current time period is dynamically determined from all cloud computers based on preset rules. This avoids the situation of pre-starting too many machines, which wastes energy and ultimately leads to significant cost increases. It also avoids the situation of pre-starting too few machines, which could result in some users having a good experience with the pre-started system, while others, due to a lack of available pre-started machines, are forced to use traditional diskless startup methods, resulting in a poor user experience.

[0044] In this embodiment, in order to be compatible and convenient for business management, a set of startup strategies is implemented through edge dynamic configuration, which is actually compatible with traditional startup and pre-start solutions. When an abnormal situation occurs in which the pre-start interaction fails, it is possible to dynamically downgrade and fall back to the traditional solution for seamless switching. Specifically, before a preset number of cloud computers are triggered to start according to the startup request, cloud computers with a pre-start function are further determined as candidate cloud computers to determine a preset number of cloud computers from the candidate cloud computers. At the same time, cloud computers that do not have a pre-start function are determined as ordinary cloud computers, and the ordinary cloud computers are started by diskless startup. It should be noted that the pre-start function is a function that can perform steps S11 and S12 in real time. Specifically, it can be determined based on a preset field in a data packet transmitted by the dynamic host configuration protocol whether the cloud computer has a pre-start switch and whether the pre-start switch is in the off state. If so, it is determined that the cloud computer has a pre-start function. This means that the pre-boot switch is issued through the Dynamic Host Configuration Protocol (DHCP) channel. This means that when the relevant switch is off, the traditional diskless boot process will be used, while when the pre-boot switch is on, the pre-boot waiting process will be used. This also ensures compatibility with existing diskless and cloud computing models.

[0045] In this embodiment, the method for determining the preset startup phase is particularly important, requiring consideration of two key factors: the time required for the cloud computer to enter the desktop after startup and the number of processes running in the cloud computer after startup. Specifically, the time required for the cloud computer to enter the desktop after startup and / or the number of processes running in the cloud computer after startup are first determined. Then, a determination is made as to whether the required time is less than the preset time and / or the number of processes is less than the preset number. If so, the cloud host's current phase is determined to be the preset startup phase. In other words, before the user has requested a cloud computer environment, multiple cloud hosts are pre-activated and paused in the preset startup phase. During this phase, there are no applications or task business programs, ensuring a clean user environment.

[0046] For example, in an internet cafe, network monitoring, information management, and billing software are required. These software are used by network regulators to monitor and alert users of anomalies, while billing software is crucial to the cafe's bottom line. Upon accessing the desktop, dozens or even hundreds of processes will be active, including but not limited to system processes and application package processes. However, these two software processes are associated with designated seats and hosts in the internet cafe via IP addresses and host names. Once accessed, many processes, including system processes such as svchost.exe, will access the old IP and host name information from the pre-opened server room. Even after a user schedules a new host to use the new IP and host name, there's no guarantee that all processes will update their information. If information management and billing software access old information from the pre-opened server room, it can lead to significant operational disruptions and compliance risks. Therefore, it's important to minimize the number of processes running during the waiting phase.

[0047] Based on this, this embodiment chooses to wait in the wininit.exe system process startup phase, which meets the above two requirements at the same time. Therefore, it is necessary to monitor the cloud host after startup before this. When it is detected that the cloud host is running the wininit process, this phase is determined as the preset startup phase and the cloud host is stopped from starting. During the startup of the cloud computer, until the wininit.exe process is running, the pre-opened driver will actively wait in this phase until the user issues a resource scheduling request. The reason for choosing to wait at this stage is that at this stage it is very close to entering the desktop, but there are almost no processes started. Being close to the desktop means that the time to be scheduled by the user and then released to wait until the final entry into the desktop will be very short, and the shorter the better in line with expectations.

[0048] S12: Determine a target cloud computer from the cloud computers to be started based on the resource scheduling request of the terminal, and trigger the target cloud computer to continue starting, so as to use the successfully started target cloud computer to respond to the resource scheduling request.

[0049] In this embodiment, based on the resource scheduling request of the terminal, the target cloud computer is determined from the cloud computers to be started, and the target cloud computer is triggered to continue to start, so that the target cloud computer that has started successfully can respond to the resource scheduling request. After the user issues the resource scheduling request, the target cloud computer is selected to provide services. For this purpose, the network configuration of the target cloud computer needs to be modified. That is, the IP address, subnet mask, gateway, and host name of the target cloud computer are modified and the VLAN network is re-divided so that the network between the modified target cloud computer and the corresponding terminal can be interconnected. When responding, it is necessary to notify the object waiting in the wininit.exe process context to stop waiting. The system will then enter the desktop normally, start the streaming program, and finally connect to the terminal program to provide services to the user.

[0050] In the Internet cafe scenario, after the user sends the resource scheduling request, the IP, gateway, subnet mask, and host name are first modified to achieve network communication with the user. The time to wait for network communication after the modification is completed is about 1 to 3 seconds. At the same time, the cloud computer is designated as the IP corresponding to the designated machine number of the designated Internet cafe. After the network communication is established, the resource package of the corresponding resources requested by the user is issued, and the pre-open driver notifies the diskless driver to obtain the specific application resources of the Internet cafe, etc., to achieve the personalization of the Internet cafe. For example, game resource packages, office resource packages, etc. Through this series of operations, user scheduling and connection can be achieved in 7 to 12 seconds, and the longest will not exceed 25 seconds. Non-pre-opening generally takes between 45 and 90 seconds, which greatly improves the user's Internet experience and shortens the waiting time for booting.

[0051] In this embodiment, in order to avoid wasting resources, cloud computers in the waiting stage can also be recycled in a timely manner. On the one hand, whether the target host has been successfully started is determined by determining whether the reporting information of the target host entering the desktop is detected. If the reporting information is not detected, the startup fails, and the target host that failed to start is recycled. On the other hand, the cloud computer to be started is connected to the server by a heartbeat connection, and the cloud host to be started with an abnormal heartbeat connection is recycled. During the waiting stage, a heartbeat packet will maintain a heartbeat connection with the upper end to avoid being mistakenly judged as a startup failure by the upper end and shutting down the host to reclaim resources.

[0052] It can be seen that the present application and this embodiment first obtains a startup request, and triggers a preset number of cloud computers to start according to the startup request until the cloud computers are in the preset startup phase and stop starting, thereby obtaining a corresponding preset number of cloud computers to be started; wherein, the preset startup phase is the phase from the start of the cloud computer startup to the completion of the startup; then, based on the resource scheduling request of the terminal, a target cloud computer is determined from the cloud computers to be started, and the target cloud computer is triggered to continue starting, so as to use the successfully started target cloud computer to respond to the resource scheduling request. In this embodiment of the application, when the user has not yet requested a cloud computer environment, the cloud computer is pre-started and paused in the preset startup phase. When the user issues a resource scheduling request, the paused cloud computer is started again to achieve network communication. The above-mentioned method of pre-starting the cloud computer can greatly shorten the user's streaming scheduling speed and boot waiting time, thereby improving the scheduling and connection efficiency.

[0053] See also Figure 2 As shown, the embodiment of the present application also discloses a cloud computer startup device, including:

[0054] The pre-startup module 11 is configured to obtain a startup request and trigger a preset number of cloud computers to start starting according to the startup request until the cloud computers stop starting when they are in a preset startup phase, thereby obtaining a corresponding preset number of cloud computers to be started; wherein the preset startup phase is the phase from the start of cloud computer startup to the completion of startup;

[0055] The scheduling response module 12 is used to determine a target cloud computer from the cloud computers to be started based on the resource scheduling request of the terminal, and trigger the target cloud computer to continue starting, so as to use the successfully started target cloud computer to respond to the resource scheduling request.

[0056] It can be seen that the present application and this embodiment first obtains a startup request, and triggers a preset number of cloud computers to start according to the startup request until the cloud computers are in the preset startup phase and stop starting, thereby obtaining a corresponding preset number of cloud computers to be started; wherein, the preset startup phase is the phase from the start of the cloud computer startup to the completion of the startup; then, based on the resource scheduling request of the terminal, a target cloud computer is determined from the cloud computers to be started, and the target cloud computer is triggered to continue starting, so as to use the successfully started target cloud computer to respond to the resource scheduling request. In this embodiment of the application, when the user has not yet requested a cloud computer environment, the cloud computer is pre-started and paused in the preset startup phase. When the user issues a resource scheduling request, the paused cloud computer is started again to achieve network communication. The above-mentioned method of pre-starting the cloud computer can greatly shorten the user's streaming scheduling speed and boot waiting time, thereby improving the scheduling and connection efficiency.

[0057] In some specific embodiments, the cloud computer startup device further includes:

[0058] A first determination module is used to determine the time required for the cloud computer to enter the desktop after starting and / or determine the number of processes running in the cloud computer after starting;

[0059] a determination module, configured to determine whether the required time is less than a preset time and / or whether the number of processes is less than a preset number; if so, determining the current stage of the cloud host as the preset startup stage;

[0060] The second determination module is used to determine the current time period and dynamically determine a preset number of cloud computers corresponding to the current time period from all cloud computers according to a preset rule;

[0061] a third determining module, configured to determine cloud computers with a pre-start function as candidate cloud computers, so as to determine a preset number of cloud computers from the candidate cloud computers;

[0062] A fourth determination module is configured to determine a cloud computer without a pre-boot function as a common cloud computer, and to boot the common cloud computer through a diskless boot method;

[0063] a determination module, configured to determine, based on a preset field in a data packet transmitted by the dynamic host configuration protocol, whether the cloud computer has a pre-start switch and whether the pre-start switch is in a closed state; if so, determining that the cloud computer has a pre-start function;

[0064] The network communication module is used to modify the IP address, subnet mask, gateway, and host name of the target cloud computer and re-divide the VLAN network so that the modified target cloud computer and the corresponding terminal can communicate with each other;

[0065] A reporting detection module is used to determine whether the target host is successfully started by determining whether the reporting information of the target host entering the desktop is detected. If no reporting information is detected, the startup fails, and the target host that failed to start is recycled;

[0066] A heartbeat connection module is used to establish a heartbeat connection between the cloud computer to be started and the server, and to recycle the cloud host to be started with abnormal heartbeat connection;

[0067] The monitoring module is used to monitor the cloud host after startup. When it is monitored that the cloud host is running the wininit process, the monitoring module determines the phase as the preset startup phase and stops starting the cloud host.

[0068] Furthermore, an embodiment of the present application also provides an electronic device. Figure 3 This is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content in the diagram should not be considered as any limitation to the scope of application of the present application.

[0069] Figure 3 This is a schematic diagram of the structure of an electronic device 20 provided in an embodiment of the present application. The electronic device 20 may include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 is used to store a computer program, which is loaded and executed by the processor 21 to implement the relevant steps of the cloud computer startup method disclosed in any of the aforementioned embodiments.

[0070] In this embodiment, the power supply 23 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and the external device. The communication protocol it follows is any communication protocol that can be applied to the technical solution of this application and is not specifically limited here; the input and output interface 25 is used to obtain external input data or output data to the outside world. Its specific interface type can be selected according to specific application needs and is not specifically limited here.

[0071] In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk or CD, etc. The resources stored thereon may include an operating system 221, a computer program 222 and data 223, etc. The storage method can be temporary storage or permanent storage.

[0072] The operating system 221 is used to manage and control the hardware devices and computer programs 222 on the electronic device 20, enabling the processor 21 to calculate and process the massive amount of data 223 in the memory 22. The operating system 221 can be Windows Server, NetWare, Unix, Linux, etc. In addition to including computer programs capable of performing the cloud computer startup method executed by the electronic device 20 as disclosed in any of the aforementioned embodiments, the computer programs 222 can further include computer programs capable of performing other specific tasks. The data 223 can include request information collected by the electronic device 20.

[0073] Furthermore, an embodiment of the present application also discloses a storage medium, in which a computer program is stored. When the computer program is loaded and executed by a processor, the steps of the cloud computer startup method disclosed in any of the aforementioned embodiments are implemented.

[0074] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from the other embodiments. Reference can be made to the descriptions of the identical or similar parts between the various embodiments. For the devices disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple, and the relevant parts can be referred to the descriptions of the methods.

[0075] Finally, it should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or device comprising the element.

[0076] The above is a detailed introduction to the cloud computer startup method, device, equipment and storage medium provided by the present invention. Specific examples are used herein to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea. At the same time, for those skilled in the art, according to the ideas of the present invention, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as limiting the present invention.

Claims

1. A cloud computer startup method, characterized in that: include: Obtaining a startup request, and triggering a preset number of cloud computers to start according to the startup request until the cloud computers stop starting when they are in a preset startup phase, thereby obtaining a corresponding preset number of cloud computers to be started; wherein the preset startup phase is the phase from the start of cloud computer startup to the completion of startup; Determine a target cloud computer from the cloud computers to be started based on the resource scheduling request of the terminal, and trigger the target cloud computer to continue starting, so as to respond to the resource scheduling request using the successfully started target cloud computer; Among them, also include: Determine the time required for the cloud computer to enter the desktop after startup and / or determine the number of processes running in the cloud computer after startup; Determine whether the required time is less than a preset time and / or whether the number of processes is less than a preset number. If so, determine the current stage of the corresponding cloud computer as the preset startup stage. Among them, also include: Determining, based on a preset field in a data packet transmitted by the Dynamic Host Configuration Protocol, whether the cloud computer has a pre-open switch and whether the pre-open switch is in a closed state; If yes, it is determined that the cloud computer has the pre-start function; The step of responding to the resource scheduling request by utilizing the successfully started target cloud computer includes: Using the successfully started target cloud computer to start a corresponding streaming program, so as to respond to the resource scheduling request of the terminal through the streaming program; After obtaining the power-on request, the method further includes: Determine the current time period, and dynamically determine a preset number of cloud computers corresponding to the current time period from all cloud computers according to preset rules.

2. The cloud computer startup method according to claim 1, characterized in that: Also includes: Determining cloud computers with a pre-start function as candidate cloud computers, and determining a preset number of cloud computers from the candidate cloud computers; The cloud computer without the pre-start function is determined as an ordinary cloud computer, and the ordinary cloud computer is started up in a diskless startup manner.

3. The cloud computer startup method according to claim 1, characterized in that: Before triggering the target cloud computer to continue to start, the method further includes: The IP address, subnet mask, gateway, and host name of the target cloud computer are modified and the VLAN network is re-divided so that the network between the modified target cloud computer and the corresponding terminal can be interconnected.

4. The cloud computer startup method according to claim 1, characterized in that: Also includes: Determine whether the target cloud computer is successfully started by determining whether the target cloud computer is detected to have reported information about entering the desktop; If the reporting information is not detected, the startup fails, and the target cloud computer that failed to start is recycled.

5. The cloud computer startup method according to claim 1, characterized in that: Also includes: A heartbeat connection is established between the cloud computer to be started and the server, and the cloud computer to be started with abnormal heartbeat connection is recycled.

6. The cloud computer startup method according to any one of claims 1 to 5, characterized in that: Also includes: Monitor the cloud computer after startup; When it is detected that the cloud computer is running the wininit process, this stage is determined as the preset startup stage and the startup of the cloud computer is stopped.

7. A cloud computer startup device, characterized in that: include: A pre-startup module is configured to obtain a startup request and trigger a preset number of cloud computers to start starting according to the startup request until the cloud computers stop starting when they are in a preset startup phase, thereby obtaining a corresponding preset number of cloud computers to be started; wherein the preset startup phase is the phase from the start of cloud computer startup to the completion of startup; a scheduling response module, configured to determine a target cloud computer from the cloud computers to be started based on the resource scheduling request of the terminal, and trigger the target cloud computer to continue starting, so as to respond to the resource scheduling request using the successfully started target cloud computer; Among them, also include: A first determination module is used to determine the time required for the cloud computer to enter the desktop after starting and / or determine the number of processes running in the cloud computer after starting; a determination module, configured to determine whether the required time is less than a preset time and / or whether the number of processes is less than a preset number; if so, determining the current stage of the corresponding cloud computer as the preset startup stage; Among them, also include: a determination module, configured to determine, based on a preset field in a data packet transmitted by the dynamic host configuration protocol, whether the cloud computer has a pre-start switch and whether the pre-start switch is in a closed state; if so, determining that the cloud computer has a pre-start function; The process of using the successfully started target cloud computer to respond to the resource scheduling request by the scheduling response module includes: using the successfully started target cloud computer to start a corresponding streaming program to respond to the resource scheduling request of the terminal through the streaming program; Among them, also include: The second determining module is used to determine the current time period and dynamically determine a preset number of cloud computers corresponding to the current time period from all cloud computers according to a preset rule.

Images