Virtual machine system and operating method thereof

• US 7,797,507 B2
• Filed: 07/25/2007
• Issued: 09/14/2010
• Est. Priority Date: 07/26/2006
• Status: Expired due to Fees

• Current Assignee: NEC Corporation
• Original Assignee: NEC Corporation
• Inventors: Tago, Akira
• Primary Examiner(s): Chace; Christian P
• Assistant Examiner(s): Bertram; Ryan
• Application Number:
  US11/878,576
• Publication Number:
  US 20080028124A1
• Time in Patent Office: 1,147 Days
• Field of Search: 711/6
• US Class Current: 711/203
• CPC Class Codes: G06F 12/0284 Multiple user address space allocation, e.g. using different base addresses interprocessor communication G06F15/163
• CPC Class Codes: G06F 12/1009 using page tables, e.g. page table structures
• CPC Class Codes: G06F 12/109 for multiple virtual address spaces, e.g. segmentation G06F12/1036 takes precedence
• CPC Class Codes: G06F 2009/45583 Memory management, e.g. access or allocation
• CPC Class Codes: G06F 2212/656 Address space sharing
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: G06F 9/5016 the resource being the memory
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes

Abstract

A virtual machine system includes a physical memory and a virtual machine monitor (VMM). When a kernel image of one guest OS, in startup of the one guest OS, has already been loaded on the physical memory, the VMM starts up one guest OS with the kernel image.

Claims

1. A virtual machine system, comprising:

a physical memory; and

a virtual machine monitor (VMM), when a kernel image of one guest operating system (OS), in startup of said one guest OS, has already been loaded on said physical memory, said VMM starts up one guest OS with said kernel image,

said VMM includes a management table representing a state of a kernel image loaded into said physical memory, and said VMM checks whether or not said kernel image of said one guest OS has been loaded on said physical memory based on management table,

when said kernel image of said one guest OS, in startup of said one guest OS, is not loaded on said physical memory, said VMM loads said kernel image of said one guest OS on said physical memory,

wherein said VMM adds a new entry of said kernel image of said one guest OS on said management table, when said kernel image of said one guest OS is loaded on said physical memory,

wherein said VMM checks whether or not said kernel image of said new entry is the same as said kernel image of other entry based on said management table, when there is said other entry except for said new entry, and

said management table includes an entry representing a size of said kernel image loaded, said VMM checks by comparing the size of the kernel image of each entry.

2. The virtual machine system according to claim 1, wherein said management table includes an entry representing an address of said kernel image loaded, said VMM checks by reading out said kernel image of each entry based on said management table and comparing said kernel image read out.

3. A virtual machine system, comprising:

a physical memory; and

a virtual machine monitor (VMM), when a kernel image of one guest operating system (OS), in startup of said one guest OS, has already been loaded on said physical memory, said VMM starts up one guest OS with said kernel image,

said VMM includes a management table representing a state of a kernel image loaded into said physical memory, and said VMM checks whether or not said kernel image of said one guest OS has been loaded on said physical memory based on said management table,

when said kernel image of said one guest OS, in startup of said one guest OS, is not loaded on said physical memory, said VMM loads said kernel image of said one guest OS on said physical memory,

wherein said VMM adds a new entry of said kernel image of said one guest OS on said management table, when said kernel image of said one guest OS is loaded on said physical memory,

wherein said VMM checks whether or not said kernel image of said new entry is the same as said kernel image of other entry based on said management table, when there is said other entry except for said new entry,

when said other entry whose kernel image is the same as said kernel image of said new entry exists, said VMM changes mapping of the address regarding said kernel image of said one entry into mapping of the address regarding said kernel image of said other entry, and

wherein said VMM further deletes said new entry from said management table and frees up an area where said kernel image of said one guest OS is loaded when said VMM changes mapping of the address regarding said kernel image of said one entry into mapping of the address regarding said kernel image of said other entry.

4. The virtual machine system according to claim 3, wherein said VMM deletes said other entry from said management table and frees up said area where said kernel image of said other guest OS is loaded, when there is no other than guest OS using said kernel image of said other guest OS in shut-down of said other guest OS.

5. The virtual machine system according to claim 4, wherein said entry of said management table includes the number of a guest OS using a kernel image loaded on said physical memory, said VMM changes the number of said new entry and said other entry when said VMM changes mapping of the address regarding said kernel image of said one entry into mapping of the address regarding said kernel image of said other entry.

6. An operating method of a virtual machine system,

wherein said virtual machine system includes a virtual machine monitor (VMM), said method comprising:

when a kernel image of one guest operating system (OS), in startup of said one guest OS, has already been loaded on a physical memory, starting up one guest OS with said kernel image;

checking whether or not said kernel image of said one guest OS has been loaded on said physical memory based on a management table in the VMM representing a state of said kernel image loaded on said physical memory;

loading said kernel image of said one guest OS on said physical memory when said kernel image of said one guest OS is not loaded on said physical memory in startup of said one guest OS;

adding a new entry of said kernel image of said one guest OS on said management table when said kernel image of said new guest OS is loaded on said physical memory;

checking, when there is other entry except for said new entry, whether or not said kernel image of said new entry is the same as said kernel image of said other entry based on said management table; and

checking whether or not said kernel image of said new entry is the same as said kernel image of said other entry by comparing the size of the kernel image of each entry in said management table representing the size of said kernel image loaded.

7. The operating method of the virtual machine system according to claim 6, wherein said management table includes an entry representing an address of said kernel image loaded, and said checking is done by comparing said kernel image of said one guest OS with said kernel images read out based on said entry of said management table.

8. The operating method of the virtual machine system according to claim 7, said method further comprising:

deleting said new entry from said management table and freeing up said area where said kernel image of said new guest OS is loaded.

9. The operating method of the virtual machine system according to claim 8, said method further comprising:

deleting said other entry from said management table and freeing up said area where said kernel image of said other guest OS is loaded when there is no other than guest OS using said kernel image of said other guest OS in shut-down of said other guest OS.

10. The operating method of the virtual machine system according to claim 9, wherein said entry of said management table includes the number of a guest OS using a kernel image loaded, and further comprising:

changing the number of said other entry and said new entry when changing mapping of the address regarding said kernel image of said one entry into mapping of the address regarding said kernel image of said other entry.