Management of software and operating system updates required for the process of creating a virtual machine facsimile of an existing physical or virtual machine

• US 8,245,217 B2
• Filed: 10/12/2007
• Issued: 08/14/2012
• Est. Priority Date: 10/12/2007
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Raman, Venkatasubrahmanyan, Varava, Natalya V., Royt, Sergey, Fries, Robert M.
• Primary Examiner(s): Zhen, Wei
• Assistant Examiner(s): Wu, Junchun
• Application Number:
  US11/871,628
• Publication Number:
  US 20090100418A1
• Time in Patent Office: 1,768 Days
• Field of Search: 717/170
• US Class Current: 717/170
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors

Abstract

Disclosed are techniques for using known update technologies to automatically identify the updates installed on a physical machine prior to facsimile creation, to locate the update packages from an update server, and to download them to the machine performing the facsimile creation. The use of update technologies enables precise identification of the updates that affect the defined set of files requiring replacement, and thus minimizes the number of updates that need to be downloaded. In addition, the desired set of replacement files are extracted and cached to allow for their reuse during subsequent facsimile creations using either the same or different physical or virtual machine as the source. Downloading the minimal set of updates and caching them for reuse eliminates the redundant downloads of updates and results in a shorter time for facsimile creation.

Claims

1. A method for creating a virtual facsimile of a source machine, the method comprising:

examining the source machine to ascertain a set of software characteristics associated with the source machine, wherein the set of software characteristics includes an identity of a software component installed on the source machine;

determining an installed version of the software component, wherein the installed version of the software component is currently installed on the source machine;

determining, from an update server, whether the installed version of the software component is a most current version of the software component;

forming an image of the source machine that includes the most current version of the software component;

identifying an update to the software component, wherein the update is currently installed on the source machine;

determining an installed version of the update, wherein the installed version of the update is currently installed on the source machine;

determining, from the update server, whether the installed version of the update is a most current version of the update; and

including the most current version of the update in the image of the source machine, the including the most current version of the update comprising;

examining a first set of files to determine whether any of the files in the first set is affected by the update, the first set of files forming a software profile of the source machine; and

forming a second set of files that includes at least one replacement file, the replacement file corresponding to a file from the first set that was affected by the update.

2. The method of claim 1, further comprising making the image of the source machine bootable on a physical machine.

3. The method of claim 2, further comprising creating a virtual machine on the physical machine.

4. The method of claim 3, wherein creating the virtual machine comprises assembling a plurality of virtual hard disks, wherein each of the virtual hard disks is defined by a respective set of files, and at least one of the hard disks is defined by at least one file associated with the most current version of the software component.

5. The method of claim 4, wherein assembling the hard disks comprises logically interconnecting the files that form the virtual hard disks.

6. The method of claim 3, further comprising running the virtual machine on the physical machine.

7. The method of claim 1, further comprising downloading the replacement file from an update server.

8. The method of claim 7, further comprising:

storing the downloaded replacement file in a cache;

retrieving the stored replacement file from the cache; and

forming a second image of the physical machine that includes the replacement file retrieved from the cache.

9. A computer readable storage medium having stored thereon instructions that when executed by a processor cause the processor to create a virtual facsimile of a source machine, the instructions comprising:

instructions to provide an identity of a software component installed on the source machine;

instructions to identify an update to the software component, wherein the update is currently installed on the source machine;

instructions to determine an installed version of the update by examining the source machine, wherein the installed version of the update is currently installed on the source machine;

instructions to determine, from the update server, whether the installed version of the update is a most current version of the update;

instructions to form an image of a source machine that includes the most current version of the update;

instructions to determine, from the update server, whether the installed version of the update is a most current version of the update; and

including the most current version of the update in the image of the source machine;

including the most current version of the update comprising;

examiner a first set of files to determine whether an of the files in the first set is affected by the update, the first set of files forming a software profile of the source machine; and

forming a second set of files that includes at least one replacement file, the replacement file corresponding to a file from the first set that was affected by the update.

10. The computer readable storage medium of claim 9, further comprising:

providing a first set of files that form a software profile of the source machine;

examining the first set of files to determine whether any of the files in the first set is affected by the update;

forming a second set of files that includes at least one replacement file, the replacement file corresponding to a file from the first set that was affected by the update.

11. The computer readable storage medium of claim 9, further comprising making the image of the source machine bootable on a physical machine.

12. The computer readable storage medium of claim 11, further comprising creating a virtual machine on the physical machine.

13. The computer readable storage medium method of claim 12, wherein creating the virtual machine comprises assembling a plurality of virtual hard disks, wherein each of the virtual hard disks is defined by a respective set of files, and at least one of the hard disks is defined by at least one file associated with the most current version of the software component.

14. The computer readable storage medium of claim 13, wherein assembling the hard disks comprises logically interconnecting the files that form the virtual hard disks.

15. The computer readable storage medium of claim 12, further comprising running the virtual machine on the physical machine.

16. A method for creating a virtual facsimile of a source machine, the method comprising:

downloading a from an update server a software update associated with a software component, wherein the software component is included in a software profile of the source machine;

forming a first image of the source machine, wherein the software update forms part of a first image of the source machine;

storing the software update in a cache;

retrieving the software update from the cache; and

forming a second image of the source machine, forming the second image of the source machine comprising;

examining a first set of files to determine whether any of the files in the first set is affected by the software update, the first set of files forming a software profile of the source machine; and

forming a second set of files that includes at least one replacement file, the replacement file corresponding to a file from the first set that was affected by the software update.

17. The method of claim 16, further comprising making the file retrieved from the cache bootable on a physical machine.

18. The method of claim 17, further comprising running a virtual machine on the physical machine, wherein running the virtual machine comprises executing the file retrieved from the cache.