IP Library Granted Patent US 10,102,020
Granted Patent B2
US 10,102,020 · App. 14/598,188 · Granted Oct 16, 2018

Methods, systems, and computer readable media for virtual machine (VM) deployment using read-only memory

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,102,020
App. No.
14/598,188
Granted
Oct 16, 2018
Kind
B2
Abstract

Methods, systems, and computer readable media for deploying a virtual machine (VM) are disclosed. According to one exemplary method, the method includes receiving a request for creating a VM. The method also includes creating the VM using a VM operating system (OS) stored in a read-only memory, wherein the read-only memory is shared among a plurality of VMs.

Claims (31)

1. A method for deploying a virtual machine, the method comprising:

at a computing platform comprising a hypervisor:

receiving a request for creating a virtual machine (VM) from a hypervisor controller;

creating the VM using a VM operating system (OS) stored in a read-only memory, wherein the read-only memory is shared among a plurality of VMs;

receiving a request for updating the plurality of VMs from the hypervisor controller; and

updating the plurality of VMs without the hypervisor controller communicating with the plurality of VMs directly by overwriting or replacing the VM OS in the read-only memory with a different VM OS via the hypervisor, wherein connectivity with the plurality of VMs is not required during the updating, wherein each of the plurality of VMs is restarted after the updating by the hypervisor and wherein each of the plurality of VMs uses the different VM OS after the updating.

2. The method of claim 1 wherein the VM is configured to use a read-write memory for storing user information, logs, user scripts, or persistent information.

3. The method of claim 2 wherein the VM is configured to use a union mount or other technique for presenting the read-only memory and the read-write memory as one logical disk or one file system to a user.

4. The method of claim 2 wherein memory write operations are redirected to the read-write memory.

5. The method of claim 1 wherein the read-only memory includes a non-transitory computer readable medium configured for allowing memory read operations but not memory write operations.

6. The method of claim 2 wherein the read-write memory includes a non-transitory computer readable medium configured for allowing memory read operations and memory write operations.

7. The method of claim 2 wherein the read-write memory or the read-only memory includes a persistent memory.

8. The method of claim 2 wherein the read-write memory is thin provisioned such that storage space is allocated on an as-needed basis.

9. A system for deploying a virtual machine, the system comprising:

a read-only memory;

a hypervisor; and

a computing platform comprising the hypervisor, the computing platform configured to receive a request for creating a VM from a hypervisor controller, to create the VM using a VM OS stored in the read-only memory, wherein the read-only memory is shared among a plurality of VMs; to receive a request for updating the plurality of VMs from the hypervisor controller; and to update the plurality of VMs without the hypervisor controller communicating with the plurality of VMs directly by overwriting or replacing the VM OS in the read-only memory with a different VM OS via the hypervisor, wherein connectivity with the plurality of VMs is not required during the updating, wherein each of the plurality of VMs is restarted after the updating by the hypervisor and wherein each of the plurality of VMs uses the different VM OS after the updating.

10. The system of claim 9 wherein the VM is configured to use a read-write memory for storing user information, logs, user scripts, or persistent information.

11. The system of claim 10 wherein the VM is configured to use a union mount or other technique for presenting the read-only memory and the read-write memory as one logical disk or one file system to a user.

12. The system of claim 10 wherein the VM is configured to redirect memory write operations to the read-write memory.

13. The system of claim 9 wherein the read-only memory includes a non-transitory computer readable medium configured for allowing memory read operations but not memory write operations.

14. The system of claim 10 wherein the read-write memory includes a non-transitory computer readable medium configured for allowing memory read operations and memory write operations.

15. The system of claim 10 wherein the read-write memory includes a persistent memory.

16. The system of claim 10 wherein the read-write memory is thin provisioned such that storage space is allocated on an as-needed basis.

17. A non-transitory computer readable medium comprising computer executable instructions embodied in the non-transitory computer readable medium that when executed by a processor of a computer perform steps comprising:

at a computing platform comprising a hypervisor:

receiving a request for creating a virtual machine (VM) from a hypervisor controller;

creating the VM using a VM operating system (OS) stored in a read-only memory, wherein the read-only memory is shared among a plurality of VMs;

receiving a request for updating the plurality of VMs from the hypervisor controller; and

updating the plurality of VMs without the hypervisor controller communicating with the plurality of VMs directly by overwriting or replacing the VM OS in the read-only memory with a different VM OS via the hypervisor, wherein connectivity with the plurality of VMs is not required during the updating, wherein each of the plurality of VMs is restarted after the updating by the hypervisor and wherein each of the plurality of VMs uses the different VM OS after the updating.

18. The non-transitory computer readable medium of claim 17 wherein the VM is configured to use a read-write memory for storing user information, logs, user scripts, or persistent information.

Assignments (5)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 19, 2018
From: KEYSIGHT TECHNOLOGIES SINGAPORE (HOLDINGS) PTE. LTD.
To: KEYSIGHT TECHNOLOGIES SINGAPORE (SALES) PTE. LTD.
Reel/Frame 048225/0065 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 18, 2017
From: IXIA
To: KEYSIGHT TECHNOLOGIES SINGAPORE (HOLDINGS) PTE. LTD.
Reel/Frame 044222/0695 →
RELEASE OF SECURITY INTEREST Recorded Apr 26, 2017
From: SILICON VALLEY BANK, AS SUCCESSOR ADMINISTRATIVE AGENT
To: IXIA
Reel/Frame 042335/0465 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 9, 2015
From: CORNEA, TUDOR; COMANESCU, GEORGE; STANCIU, ADRIAN; BELOV, KONSTANTIN
To: IXIA
Reel/Frame 035116/0661 →
SECURITY INTEREST Recorded Mar 3, 2015
From: IXIA; ANUE SYSTEMS, INC.; BREAKINGPOINT SYSTEMS, INC.
To: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
Reel/Frame 035121/0860 →
Cited By (1)
US 12,348,404