Source: https://patents.google.com/patent/US20110072429A1/en
Timestamp: 2020-07-03 11:34:04
Document Index: 340714846

Matched Legal Cases: ['art 24', 'art 36', 'art 44', 'art 52', 'art 60', 'art 68']

US20110072429A1 - Virtual machine relocation system and associated methods - Google Patents
Virtual machine relocation system and associated methods Download PDF
US20110072429A1
US20110072429A1 US12/565,830 US56583009A US2011072429A1 US 20110072429 A1 US20110072429 A1 US 20110072429A1 US 56583009 A US56583009 A US 56583009A US 2011072429 A1 US2011072429 A1 US 2011072429A1
US12/565,830
US8495629B2 (en
Cathy C. Hupman
Selina Lok
2009-09-24 Priority to US12/565,830 priority Critical patent/US8495629B2/en
2009-09-24 Assigned to INTERNATIONAL BUSINESS MACHINES CORPORATION reassignment INTERNATIONAL BUSINESS MACHINES CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: LOK, SELINA, CELESKEY, EMILY K., GREER, TIMOTHY D., HUPMAN, CATHY C.
2011-03-24 Publication of US20110072429A1 publication Critical patent/US20110072429A1/en
2013-07-23 Publication of US8495629B2 publication Critical patent/US8495629B2/en
A system to address virtual machine relocation may include a computer system and a host operating system executing on the computer system. The system may also include a second computer system and a second host operating system executing on the second computer system. The system may further include a virtual machine executing on the host operating system. The system may additionally include a tool to relocate the virtual machine to the second host operating system based upon the host operating system's needs, the second host operating system's availability, and/or the virtual machine's relocation eligibility.
The invention relates to the field of computer systems, and, more particularly, to the relocation of virtual machines in such.
In general, a virtual machine is a software application that executes programs like a real computer system. For example, a virtual machine is a logical sharing or partition of CPU, memory, or the like that appears to programs executing in the virtual machine to be a real computer with dedicated CPU, memory, and the like.
According to one embodiment of the invention, a system to address virtual machine relocation may include a computer system and a host operating system executing on the computer system. The system may also include a second computer system and a second host operating system executing on the second computer system. The system may further include a virtual machine executing on the host operating system. The system may additionally include a tool to relocate the virtual machine to the second host operating system based upon the host operating system's needs, the second host operating system's availability, and/or the virtual machine's relocation eligibility.
The tool may control timing of the relocation between the host operating system and the second host operating system. The tool may control the relocation timing based upon configuration parameters, user input information, statistical data, historical averages, and/or historical trends of the virtual machine's operation.
The tool may determine a success level of the virtual machine's relocation. The tool may match a below average success level to the virtual machine's configuration profile. The tool may generate a possible code errors report based upon any mismatches. The host operating system's needs may comprise planned system outages.
Another aspect of the invention is a method to address virtual machine relocation. The method may include executing a host operating system on a computer system and a second host operating system on a second computer system. The method may also include executing a virtual machine on the host operating system. The method may further include using a tool to relocate the virtual machine to the second host operating system based upon the host operating system's needs, the second host operating system's availability, and/or the virtual machine's relocation eligibility.
The method may also include controlling relocation timing between the host operating system and the second host operating system. The method may further include controlling the relocation timing based upon configuration parameters, user input information, statistical data, historical averages, and/or historical trends of the virtual machine's operation.
The method may also include determining a success level of the virtual machine's relocation. The method may further include matching a below average success level to the virtual machine's configuration profile. The method may additionally include generating a possible code errors report based upon any mismatches.
Another aspect of the invention is a computer program product that may address virtual machine relocation. The computer program product may include a computer readable storage medium having computer readable program code embodied therewith. The computer readable program code may include computer readable program code configured to execute a host operating system on a computer system and a second host operating system on a second computer system. The computer readable program code may also include computer readable program code configured to execute a virtual machine on the host operating system. The computer readable program code may further include computer readable program code configured to use a tool to relocate the virtual machine to the second host operating system based upon at least one of the host operating system's needs, the second host operating system's availability, and the virtual machine's relocation eligibility.
Another aspect of the invention is a system that may include a plurality of computer systems and a plurality of host operating systems executing on the plurality of computer systems. The system may also include a plurality of virtual machines each executing via a respective one of the plurality of host operating systems. The system may further include a tool to relocate any of the plurality of virtual machines to a different one of the plurality of host operating systems based upon the respective needs of the plurality of host operating systems, availability of a different one of the plurality of host operating systems, and/or the relocation eligibility of each of the plurality of virtual machines.
The tool may determine each of the plurality of virtual machines' configurations. The tool may determine which of the plurality of virtual machines is expected to pass or fail the relocation. The tool may review each of the plurality of virtual machines' configurations for potential relocation errors.
The tool may order at least one of when and where each of said plurality of virtual machines is relocated. The tool uses the order to address at least one of the plurality of host operating systems' respective needs and the different one of the plurality of host operating systems availability.
FIG. 1 is a schematic block diagram of a system to relocate virtual machines in accordance with the invention.
FIG. 4 is a flowchart illustrating method aspects according to the method of FIG. 3.
FIG. 6 is a flowchart illustrating method aspects according to the method of FIG. 5.
FIG. 7 is a flowchart illustrating method aspects according to the method of FIG. 6.
With reference now to FIG. 1, a system 10 to address virtual machine relocation is initially described. The system 10 is a programmable apparatus that stores and manipulates data according to an instruction set as will be appreciated by those of skill in the art.
According to one embodiment of the invention, the system 10 includes a computer system 12 a and a host operating system 14 a executing on the computer system. In another embodiment, the system 10 includes a second computer system 12 b and a second host operating system 14 b executing on the second computer system. In one embodiment, the system 10 includes a virtual machine 16 a executing on the host operating system. In another embodiment, the system 10 includes a tool 18 to relocate the virtual machine 16 a to the second host operating system 14 b based upon the host operating system's 14 a needs, the second host operating system's availability, and/or the virtual machine's relocation eligibility.
In one embodiment, the tool 18 controls timing of the relocation between the host operating system 14 a and the second host operating system 14 b. In another embodiment, the tool 18 controls the relocation timing and which users are relocated based upon scenarios determined by configuration parameters, user input information, statistical data, historical averages, and/or historical trends of the virtual machine's operation.
In one embodiment, the tool 18 determines a success level of the virtual machine's 16 a relocation. In another embodiment, the tool 18 matches a below average success level to the virtual machine's 16 a configuration profile. In one embodiment, the tool 18 generates a possible code errors report based upon any mismatches. In another embodiment, the host operating system's 14 a needs may comprise planned system outages.
In one embodiment, the system 10 includes a communications network 20, which enables a signal to travel anywhere within system 10 and/or to any other system connected to system 10. The communications network 20 is wired and/or wireless, for example. The communications network 20 is local and/or global with respect to system 10, for instance. The communications network 20 includes communications links 22 a-22 n as will be appreciated by those of skill in the art.
Another aspect of the invention is a method to address virtual machine relocation, which is now described with reference to flowchart 24 of FIG. 2. The method begins at Block 26 and may include executing a host operating system on a computer system and a second host operating system on a second computer system at Block 28. The method may also include executing a virtual machine on the host operating system at Block 30. The method may further include using a tool to relocate the virtual machine to the second host operating system based upon the host operating system's needs, the second host operating system's availability, and/or the virtual machine's relocation eligibility at Block 32. The method ends at Block 34.
In another method embodiment, which is now described with reference to flowchart 36 of FIG. 3, the method begins at Block 38. The method may include the steps of FIG. 2 at Blocks 28, 30, and 32. The method may additionally include controlling relocation timing between the host operating system and the second host operating system at Block 40. The method ends at Block 42.
In another method embodiment, which is now described with reference to flowchart 44 of FIG. 4, the method begins at Block 46. The method may include the steps of FIG. 3 at Blocks 28, 30, 32, and 40. The method may additionally include controlling the relocation timing based upon configuration parameters, user input information, statistical data, historical averages, and/or historical trends of the virtual machine's operation at Block 48. The method ends at Block 50.
In another method embodiment, which is now described with reference to flowchart 52 of FIG. 5, the method begins at Block 54. The method may include the steps of FIG. 2 at Blocks 28, 30, and 32. The method may additionally include determining a success level of the virtual machine's relocation at Block 56. The method ends at Block 58.
In another method embodiment, which is now described with reference to flowchart 60 of FIG. 6, the method begins at Block 62. The method may include the steps of FIG. 5 at Blocks 28, 30, 32, and 56. The method may additionally include matching a below average success level to the virtual machine's configuration profile at Block 64. The method ends at Block 66.
In another method embodiment, which is now described with reference to flowchart 68 of FIG. 7, the method begins at Block 70. The method may include the steps of FIG. 6 at Blocks 28, 30, 32, 56, and 64. The method may additionally include generating a possible code errors report based upon any mismatches at Block 72. The method ends at Block 74.
Another aspect of the invention is a set of computer readable program codes coupled to tangible media that may address virtual machine relocation. In one embodiment, the computer readable program codes are configured to cause the program to execute a host operating system 14 a on a computer system 12 a and a second host operating system 14 b on a second computer system 12 b. In another embodiment, the computer readable program codes execute a virtual machine 16 a on the host operating system. In one embodiment, the computer readable program codes use a tool 18 to relocate the virtual machine 16 a to the second host operating system 14 b based upon the host operating system's 14 a needs, the second host operating system's availability, and/or the virtual machine's relocation eligibility.
Referring back to FIG. 1, another aspect of the invention is a system 10 that includes a plurality of computer systems 12 a-12 n and a plurality of host operating systems 14 a-14 n executing on the plurality of computer systems. In one embodiment, the system 10 includes a plurality of virtual machines 16 a-16 n each executing via a respective one of the plurality of host operating systems 14 a-14 n. In another embodiment, the system 10 includes a tool 18 to relocate any of the plurality of virtual machines 16 a-16 n to a different one of the plurality of host operating systems 14 a-14 n based upon the plurality of host operating systems' respective needs, the different one of the plurality of host operating systems availability, and/or each of the plurality of virtual machines' relocation eligibility.
In one embodiment, the tool 18 determines each of the plurality of virtual machines' 16 a-16 n configurations. In another embodiment, the tool 18 determines which of the plurality of virtual machines 16 a-16 n is expected to pass or fail the relocation. In one embodiment, the tool 18 reviews each of the plurality of virtual machines' 16 a-16 n configurations for potential relocation errors.
In one embodiment, the tool 18 orders when and/or where each of said plurality of virtual machines 16 a-16 n is relocated. In another embodiment, the tool 18 uses the order to address the plurality of host operating systems' 14 a-14 n respective needs and/or the different one of the plurality of host operating systems availability.
In view of the foregoing, the system 10 addresses virtual machine relocation, for example. In one embodiment, the tool 18 takes in the user directory to determine which users may be running on the system 10 and their possible problems. From there it looks for active users (inactive users may not be relocatable) and queries their active configurations to determine any additional restrictions. In another embodiment, then from the active users, the tool 18 determines which guests to move where based on a testing profile (e.g., maximizing data throughput) and kicks off the relocations.
In one embodiment, the tool 18 then determines if relocations were successful and if the guests continued to run. In another embodiment, if the relocations were not successful, the tool 18 tries to match the problems encountered with the guests' configurations. Any mismatches are highlighted as possible code errors, for instance.
In one embodiment, the system 10 involves the automated test generation and checking of Live Guest Relocation (“LGR”) eligibility errors. In another embodiment, a new LGR code on IBM's z/VM system runs on only a small subset of all possible guests, therefore there are a number of things a relocating guest is not allowed to do.
In one embodiment, each of these eligibility restrictions generates its own error, and to do this eligibility checking by hand would be time/cost prohibitive and highly error prone. Similarly, kicking off the relocations and verifying that the errors received match what the guest is doing would be very difficult to do manually for an entire z/VM system, for example.
In one embodiment, the input comes in the form of a user directory, containing initial user information; various query input, a list of possible error messages and the way to tell if a guest should encounter these errors. In another embodiment, the tool 18 checks the user directory to see which users have static configurations that will cause errors.
In one embodiment, the tool 18 creates a master file with all the users and whether they are expected to pass or fail. For each user expected to fail, the tool 18 creates a restrictions file containing the expected error messages, for example.
In one embodiment, the tool 18 then queries which users are active on the system 10. In another embodiment, for each active user, the tool 18 goes through all the possible queries to see if the user's active configuration will cause an error.
In one embodiment, for each active configuration error expected, the tool 18 updates/creates the user's restriction file and updates the master file, if necessary. Then for all the active users, the tool 18 issues the relocation command, for instance.
In one embodiment, to determine the order of users to be relocated, the system 10 looks at the system and guest configurations. For instance, the guest's memory usage and number of links between the system could give system 10 an estimate of how quickly the guest would relocate. Based on this information the tool 18 will then have various “relocation use cases”.
In one embodiment, one use case could be to keep the links as busy as possible, while another could focus on relocating small and large guests alternately. In another embodiment, each use case should stress the code and system in different ways.
In one embodiment, the tool 18 then checks the command output against the master file and restrictions file and highlights any differences (by creating a differences file). If the command was successful (the relocation could take awhile), the tool 18 then checks the test case running on the user to ensure it continued running while the command was being executed, for example. Of course the tool 18 cannot assume that the guest has been running a test case (for instance the guest could be a service machine for the system), so instead the tool 18 will keep a historical comparison to help tell if the guest has relocated successfully, for instance.
In one embodiment, each user will have a profile of sorts with average time to relocate and guest “behavior” (again, memory usage, commands it usually issues, average time for relocation). For example, the most recent statistics should be in line with the usual.
In one embodiment, if the relocation failed but was expected to pass, several steps are taken. First, the active configuration queries are re-run to see if the guest has changed its configuration since we last looked. If the difference still exists (i.e., the current configuration doesn't seem to match the problems the tool 18 saw) the tool 18 further classifies the difference.
For instance, there are two basic types of differences: more problems than expected, or fewer problems than expected. In the case of more problems than expected, the tool can see if the additional problems were caused by temporary active configuration changes (for example a guest “rebooting”), in which case it could still pass the relocation, although flagging it as “yellow”. If there were fewer problems received than expected, or the mismatches were not related to temporary changes, then the tool would fail the relocation because it likely signals a code error (or at least a documentation problem in the relocation restrictions), for example. The tool can also check the guest's console to see if it issued any commands that caused these changes and also look historically at which problems the guest has.
For instance, if the tool sees the guest reboot several times a week, we may stop counting this problem against this guest. This would mean that some mismatches would not fail the test case. In the rare case where a user logs off before its configuration has been checked and there is a mismatch, the errors can be flagged as “orange”, for example.
In one embodiment, the tool 18 compiles a list of all the relocations it has issued and whether the expected output was received. In another embodiment, this is formatted in a human readable way, e.g. HTML file.
In one embodiment, this output should also be compared to the historical data. In another embodiment, average time of all relocations and average system performance should be in line with previous instances of the use case. For example, if the tool is running the “keep all links busy” use case and it can usually relocate 30 large users, the current statistics should be in line with that.
In one embodiment, the tool 18 concerns itself with the effects of its actions upon the underlying host systems 14 a-14 n. In other words, the tool 18 selects guests to relocate based on the expected effect on the host systems 14 a-14 n.
In one embodiment, the system 10 manipulates the timing of relocation requests to affect the host systems 14 a-14 n and/or the connections between them. In another embodiment, the tool collects statistical data and uses historical averages or trends to predict the host systems' 14 a-14 n responses to patterns of relocation requests. For example, these responses do affect guests being relocated—as the amount of time required to relocate—so there is some applicability to the problem of maximizing guest performance (or avoiding dropping below some minimum). But even here, the focus is on the host systems 14 a-14 n rather than the guests.
In one embodiment, the system 10 is about handling the relocations themselves to drive various functions in the hypervisor layer. In another embodiment, the system 10 assumes that relocations have to happen because of planned system outages. (That sentence doesn't seem to make sense there.)
a host operating system executing on said computer system;
a second host operating system executing on said second computer system;
a virtual machine executing on said host operating system; and
a tool to relocate said virtual machine to said second host operating system based upon at least one of said host operating system's needs, said second host operating system's availability, and said virtual machine's relocation eligibility.
2. The system of claim 1 wherein said tool controls timing of the relocation between said host operating system and said second host operating system.
3. The system of claim 2 wherein said tool controls the relocation timing based upon at least one of configuration parameters, user input information, statistical data, historical averages, and historical trends of said virtual machine's operation.
4. The system of claim 1 wherein said tool determines a success level of said virtual machine's relocation.
5. The system of claim 4 wherein said tool matches a below average success level to said virtual machine's configuration profile.
6. The system of claim 5 wherein said tool generates a possible code errors report based upon any mismatches.
7. The system of claim 1 wherein said host operating system's needs comprise planned system outages.
executing a host operating system on a computer system and a second host operating system on a second computer system;
executing a virtual machine on the host operating system; and
using a tool to relocate the virtual machine to the second host operating system based upon at least one of the host operating system's needs, the second host operating system's availability, and the virtual machine's relocation eligibility.
9. The method of claim 8 further comprising controlling timing of the relocation between the host operating system and the second host operating system.
10. The method of claim 9 further comprising controlling the relocation timing based upon at least one of configuration parameters, user input information, statistical data, historical averages, and historical trends of the virtual machine's operation.
11. The method of claim 8 further comprising determining a success level of the virtual machine's relocation.
12. The method of claim 11 further comprising matching a below average success level to the virtual machine's configuration profile.
13. The method of claim 12 further comprising generating a possible code errors report based upon any mismatches.
14. A computer program product to address virtual machine relocation, the computer program product comprising: a computer readable storage medium having computer readable program code embodied therewith, the computer readable program code comprising:
computer readable program code configured to execute a host operating system on a computer system and a second host operating system on a second computer system;
computer readable program code configured to execute a virtual machine on the host operating system; and
computer readable program code configured to use a tool to relocate the virtual machine to the second host operating system based upon at least one of the host operating system's needs, the second host operating system's availability, and the virtual machine's relocation eligibility.
15. The computer program product of claim 14 further comprising: computer readable program code configured to control timing of the relocation between the host operating system and the second host operating system.
16. The computer program product of claim 15 further comprising: computer readable program code configured to control the relocation timing based upon at least one of configuration parameters, user input information, statistical data, historical averages, and historical trends of the virtual machine's operation.
17. The computer program product of claim 14 further comprising: computer readable program code configured to determine a success level of the virtual machine's relocation.
18. The computer program product of claim 17 further comprising: computer readable program code configured to match a below average success level to the virtual machine's configuration profile.
19. The computer program product of claim 18 further comprising: computer readable program code configured to generate a possible code errors report based upon any mismatches.
a plurality of host operating systems executing on said plurality of computer systems;
a plurality of virtual machines each executing via a respective one of said plurality of host operating systems; and
a tool to relocate any of said plurality of virtual machines to a different one of said plurality of host operating systems based upon the respective needs of at least one of said plurality of host operating systems, availability of a different one of said plurality of host operating systems, and the relocation eligibility of each of said plurality of virtual machines.
21. The system of claim 20 wherein said tool determines each of said plurality of virtual machines' configurations.
22. The system of claim 20 wherein said tool determines which of said plurality of virtual machines is expected to pass or fail the relocation.
23. The system of claim 21 wherein said tool reviews each of said plurality of virtual machines' configurations for potential relocation errors.
24. The system of claim 20 wherein said tool orders at least one of when and where each of said plurality of virtual machines is relocated.
25. The system of claim 24 wherein said tool uses the order to address at least one of the respective needs of said plurality of host operating systems and the availability of said different one of said plurality of host operating systems.
US12/565,830 2009-09-24 2009-09-24 Virtual machine relocation system and associated methods Active 2031-08-17 US8495629B2 (en)
US12/565,830 US8495629B2 (en) 2009-09-24 2009-09-24 Virtual machine relocation system and associated methods
US20110072429A1 true US20110072429A1 (en) 2011-03-24
US8495629B2 US8495629B2 (en) 2013-07-23
ID=43757739
US12/565,830 Active 2031-08-17 US8495629B2 (en) 2009-09-24 2009-09-24 Virtual machine relocation system and associated methods
US (1) US8495629B2 (en)
WO2013062715A1 (en) * 2011-10-27 2013-05-02 Intel Corporation Controlling operating frequency of a core domain via a non-core domain of a multi-domain processor
2009-09-24 US US12/565,830 patent/US8495629B2/en active Active
US8495629B2 (en) 2013-07-23
Leesatapornwongsa et al. 2014 {SAMC}: Semantic-Aware Model Checking for Fast Discovery of Deep Bugs in Cloud Systems
US20160004606A1 (en) 2016-01-07 Method, system and device for validating repair files and repairing corrupt software
US9389810B2 (en) 2016-07-12 Performance-based grouping of storage devices in a storage system
US9716612B2 (en) 2017-07-25 Evaluation of field replaceable unit dependencies and connections
US10592325B2 (en) 2020-03-17 Enabling symptom verification
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CELESKEY, EMILY K.;GREER, TIMOTHY D.;HUPMAN, CATHY C.;AND OTHERS;SIGNING DATES FROM 20090921 TO 20090923;REEL/FRAME:023276/0130