Adjustment during migration to a different virtualization environment

• US 9,280,378 B2
• Filed: 11/30/2011
• Issued: 03/08/2016
• Est. Priority Date: 11/30/2011
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Shah, Amit
• Primary Examiner(s): Kim, Dong
• Application Number:
  US13/307,963
• Publication Number:
  US 20130139155A1
• Time in Patent Office: 1,560 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 2009/4557 Distribution of virtual machine instances; Migration and load balancing
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects

Abstract

An installer installing an operating system on a host computer system detects that the operating system is to be run under a hypervisor, and causes at least one configuration parameter of the operating system to be adjusted based on the hypervisor. A migration tool migrating a virtual machine from one hypervisor to another hypervisor, identifies the types of the two hypervisors, the operating system used by the virtual machine, and causes at least one configuration parameter of the operating system to be adjusted based on the target hypervisor.

Claims

1. A method comprising:

identifying, by a migration tool executed by a processor, an operating system to be migrated to a target virtual machine host computer system from a source computer system;

identifying, by the migration tool, a first hypervisor running on the target virtual machine host computer system, wherein the operating system was running under a second hypervisor prior to migration, wherein the first hypervisor comprises a first type and the second hypervisor comprises a second type;

migrating, by the migration tool, the operating system to the target virtual machine host computer system;

in response to determining the first type of the first hypervisor and determining the second type of the second hypervisor, causing, by the migration tool, a first set of configuration parameters of the operating system to be optimized by the migration tool, wherein the first set of configuration parameters are identified in view of a difference between the first type of the first hypervisor and the second type of the second hypervisor and wherein the identified first set of configuration parameters are adjusted in response to selecting two or more options from the migration tool, wherein the two or more options comprise;

a recommended option to adjust the first set of configuration parameters to default values; and

a customizable option to adjust one or more configuration parameters of the first set of configuration parameters to one or more values from a list of selectable configuration parameters comprising a default value, a recommended value, and one or more additional values;

in response to failing to determine the first type of the first hypervisor, causing, by the migration tool, a second set of configuration parameters of the operating system to be optimized, wherein the second set of configuration parameters are identified regardless of the first type of the first hypervisor; and

in response to determining the first type of the first hypervisor and failing to determine the second type of the second hypervisor, causing, by the migration tool, a third set of configuration parameters of the operating system to be optimized, wherein the third set of configuration parameters are identified independent of the second type of the second hypervisor, wherein the third set of configuration parameters are identified in view of the first type of the first hypervisor.

2. The method of claim 1, wherein causing the first set of configuration parameters to be optimized comprises:

generating for display a user interface facilitating user input as to whether the first set of configuration parameters is to be changed;

receiving user input from a user requesting that the first set of configuration parameters be changed; and

setting the first set of configuration parameters to values corresponding to the first hypervisor.

3. The method of claim 2, wherein the values are provided by the user or are obtained without user interaction.

4. The method of claim 1, wherein causing the first set of configuration parameters to be optimized comprises updating, by the migration tool, a configuration file using values for the first set of configuration parameters in view of the first hypervisor or values acceptable for multiple hypervisors.

5. The method of claim 1, wherein causing the first set of configuration parameters to be optimized comprises enabling, by the migration tool, a service to set the first set of configuration parameters to values in view of the first hypervisor.

6. The method of claim 1, wherein causing the first set of configuration parameters to be optimized comprises setting, by the migration tool, the first set of configuration parameters to values in view of the first hypervisor.

7. The method of claim 1, wherein determining the first type of the first hypervisor comprises performing at least one of:

requesting type information from the first hypervisor;

obtaining type information from a configuration store maintained by the first hypervisor;

receiving type information from a user;

or

obtaining type information from a configuration store maintained by the target virtual machine host computer system.

8. The method of claim 1, wherein the first type of the first hypervisor is a Kernel-Based Virtual Machine (KVM) type hypervisor.

9. The method of claim 1, wherein the first set of configuration parameters of the operating system are adjusted in view of the first type of the first hypervisor after the operation system is migrated to the target virtual machine host computer system.

10. An apparatus comprising:

a hardware processor to;

identify an operating system to be migrated to a target virtual machine host computer system from a source computer system;

identify a first hypervisor running on the target virtual machine host computer system, wherein the operating system was running under a second hypervisor prior to migration, wherein the first hypervisor comprises a first type and the second hypervisor comprises a second type;

migrate the operating system to the target virtual machine host computer system;

cause a first set of configuration parameters of the operating system to be optimized by a migration tool, wherein the first set of configuration parameters are identified in view of a difference between the first type of the first hypervisor and the second type of the second hypervisor in response to determining the first type of the first hypervisor and determining the second type of the second hypervisor and wherein the identified first set of configuration parameters are adjusted in response to selecting two or more options from the migration tool, wherein the two or more options comprise;

a recommended option to adjust the first set of configuration parameters to default values; and

a customizable option to adjust one or more configuration parameters of the first set of configuration parameters to one or more values from a list of selectable configuration parameters comprising a default value, a recommended value, and one or more additional values;

cause a second set of configuration parameters of the operating system to be optimized in response to failing to determine the first type of the first hypervisor, wherein the second set of configuration parameters are identified regardless of the first type of the first hypervisor; and

cause a third set of configuration parameters of the operating system to be optimized in response to determining the first type of the first hypervisor and failing to determine the second type of the second hypervisor, wherein the third set of configuration parameters are identified independent of the second type of the second hypervisor, wherein the third set of configuration parameters are identified in view of the first type of the first hypervisor.

11. The apparatus of claim 10, wherein to cause the first set of configuration parameters to be optimized, the hardware processor is further to:

generate for display a user interface facilitating user input as to whether the first set of configuration parameters is to be changed;

receive user input requesting that the first set of configuration parameters be changed; and

set the first set of configuration parameters to values corresponding to the first hypervisor.

12. The apparatus of claim 10, wherein to cause the first set of configuration parameters to be optimized, the hardware processor is further to:

update, by a migration tool executed by the hardware processor, a configuration file using values for the first set of configuration parameters in view of the first hypervisor or values acceptable for multiple hypervisors;

enable, by the migration tool, a service to set the first set of configuration parameters to values in view of the first hypervisor;

or

set, by the migration tool, the first set of configuration parameters to values in view of the first hypervisor.

13. The apparatus of claim 10, wherein to determine the first type of the first hypervisor, the hardware processor is further to:

request type information from the first hypervisor;

obtain type information from a configuration store maintained by the first hypervisor;

receive type information from a user;

or

obtain type information from a configuration store maintained by the target virtual machine host computer system.

14. The apparatus of claim 10, wherein the first type of the first hypervisor is a KVM type hypervisor.

15. The apparatus of claim 10, wherein the first set of configuration parameters of the operating system are to be adjusted in view of the first type of the first hypervisor after the operation system is migrated to the target virtual machine host computer system.

16. A non-transitory machine-readable storage medium including data that, when accessed by a processor, cause the processor to:

identify, by a migration tool executed by the processor, an operating system to be migrated to a target virtual machine host computer system from a source computer system;

identify, by the migration tool, a first hypervisor running on the target virtual machine host computer system, wherein the operating system was running under a second hypervisor prior to migration, wherein the first hypervisor comprises a first type and the second hypervisor comprises a second type;

migrate, by the migration tool, the operating system to the target virtual machine host computer system;

in response to determining the first type of the first hypervisor and determining the second type of the second hypervisor, cause, by the migration tool, a first set of configuration parameters of the operating system to be optimized by the migration tool, wherein the first set of configuration parameters are identified in view of a difference between the first type of the first hypervisor and second type of the second hypervisor and wherein the identified first set of configuration parameters are adjusted in response to selecting two or more options from the migration tool, wherein the two or more options comprise;

a recommended option to adjust the first set of configuration parameters to default values; and

a customizable option to adjust one or more configuration parameters of the first set of configuration parameters to one or more values from a list of selectable configuration parameters comprising a default value, a recommended value, and one or more additional values;

in response to failing to determine the first type of the first hypervisor, cause, by the migration tool, a second set of configuration parameters of the operating system to be optimized, wherein the second set of configuration parameters are identified regardless of the first type of the first hypervisor; and

in response to determining the first type of the first hypervisor and failing to determine the second type of the second hypervisor, causing, by the migration tool, a third set of configuration parameters of the operating system to be optimized, wherein the third set of configuration parameters are identified independent of the second type of the second hypervisor, wherein the third set of configuration parameters are identified in view of the first type of the first hypervisor.

17. The non-transitory machine-readable storage medium of claim 16, wherein to cause the first set of configuration parameters to be optimized, the data, when accessed by the processor, further cause the processor to:

generate for display a user interface facilitating user input as to whether the first set of configuration parameters is to be changed;

receive user input requesting that the first set of configuration parameters be changed; and

set the first set of configuration parameters to values corresponding to the first hypervisor.

18. The non-transitory machine-readable storage medium of claim 16, wherein to cause the first set of configuration parameters to be optimized, the data, when accessed by the processor, further cause the processor to:

update, by the migration tool executed by the processor, a configuration file using values for the first set of configuration parameters in view of the first hypervisor or values acceptable for multiple hypervisors;

enable, by the migration tool, a service to set the first set of configuration parameters to values in view of the first hypervisor;

or

set, by the migration tool, the first set of configuration parameters to values in view of the first hypervisor.

19. The non-transitory machine-readable storage medium of claim 16, further including data that, when accessed by the processor, cause the processor to:

identify a type of the first hypervisor by performing at least one of;

requesting type information from the first hypervisor;

obtaining type information from a configuration store maintained by the first hypervisor;

receiving type information from a user;

or

obtaining type information from a configuration store maintained by the target virtual machine host computer system.

20. The non-transitory machine-readable storage medium of claim 16, wherein the first type of the first hypervisor is a KVM type hypervisor.

21. The non-transitory machine-readable storage medium of claim 16, wherein the first set of configuration parameters of the operating system are to be adjusted in view of the first type of the first hypervisor after the operation system is migrated to the target virtual machine host computer system.