# US 2013/0254523 A1 · System and Method for Supporting Full Volume Encryption Devices in a Client Hosted Virtualization System

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2013/0254523 A1
- Document ID: US20130254523A1
- Status: Published application
- Kind: A1
- Application number: 13/895,925
- Filed: 2013-05-16
- Published: 2013-09-26
- Earliest claimed: 2010-05-28
- Assignees: Dell Products L.P.
- Applicants: Dell Products, LP
- Inventors: David Konetski; Kenneth W. Stufflebeam; Shree Dandekar
- Web page: https://patentgrep.com/patent/US20130254523A1

## CPC

- G06F 21/572: {Secure firmware programming, e.g. of basic input output system [BIOS]}
- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 21/53: by executing in a restricted environment, e.g. sandbox or secure virtual machine
- G06F 21/575: {Secure boot}
- G06F 2009/45587: {Isolation or security of virtual machine instances}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A client hosted virtualization system includes a full volume encryption (FVE) storage device, a processor, and non-volatile memory with BIOS code and virtualization manager code. The virtualization manager initializes the client hosted virtualization system, authenticates a virtual machine image, launches the virtual machine based on the image, receives a transaction from the virtual machine targeted to the FVE storage device, sends the transaction to the FVE storage device, receives a response from the FVE storage device, and sends the first response to the first virtual machine. The client hosted virtualization system is configurable to execute the BIOS or the virtualization manager.

## Claims

### Claim 1

A client hosted virtualization system (CHVS) comprising:
a full volume encryption (FVE) storage device;
a processor operable to execute code; and
a non-volatile memory including first code to implement a basic input/output system to initialize the CHVS, and second code to implement a virtualization manager operable to:
initialize the CHVS;
receive a first transaction from a first virtual machine, a target of the first transaction being the FVE storage device;
send the first transaction to the FVE storage device;
receive a first response to the first transaction from the FVE storage device; and
send the first response to the first virtual machine;
wherein the CHVS is configurable in a first configuration to execute the first code and not the second code, and is configurable in a second configuration to execute the second code and not the first code.

### Claim 2 (depends on 1)

The CHVS of claim 1, further comprising a mass storage device, and wherein the first virtual machine image:
is stored on the mass storage device; and
includes an operating system and an application.

### Claim 3 (depends on 1)

The CHVS of claim 1, further comprising:
a general purpose encryption (GPE) engine;
wherein in sending the first transaction to the FVE storage device, the virtualization manager is further operable to send the first transaction to the GPE engine.

### Claim 4 (depends on 3)

The CHVS of claim 3, wherein:
the first transaction is a write transaction; and
in sending the first transaction to the GPE engine, the virtualization manager is further operable to direct the GPE engine to encrypt information associated with the first transaction, and to store the information on the FVE storage device.

### Claim 5 (depends on 3)

The CHVS of claim 3, wherein:
the first transaction is a read transaction;
in sending the first transaction to the GPE engine, the virtualization manager is further operable to direct the GPE retrieve information associated with the first transaction from the FVE storage device; and
in receiving the first response to the first transaction from the FVE storage device engine, the virtualization manager is further operable to direct the GPE engine to decrypt the information.

### Claim 6 (depends on 1)

The CHVS of claim 1, wherein the virtualization manager is further operable to:
receive a second transaction from a second virtual machine, a target of the second transaction being the FVE storage device;
send the second transaction to the FVE storage device;
receive a second response to the first transaction from the FVE storage device; and
send the second response to the second virtual machine.

### Claim 7 (depends on 6)

The CHVS of claim 6, further comprising:
an unencrypted storage device;
wherein the virtualization manager is further operable to:
receive a third transaction from the first virtual machine, a target of the third transaction being the unencrypted storage device;
send the third transaction to the unencrypted storage device;
receive a third response to the third transaction from the unencrypted storage device; and
send the third response to the first virtual machine.

### Claim 8 (depends on 7)

The CHVS of claim 7, wherein the virtualization manager is further operable to:
receive a fourth transaction from the second virtual machine, a target of the fourth transaction being the unencrypted storage device;
send the fourth transaction to the unencrypted storage device;
receive a fourth response to the fourth transaction from the unencrypted storage device; and
send the fourth response to the second virtual machine.

### Claim 9

A method of providing a client hosted virtualization system (CHVS) comprising:
storing first code in a non-volatile memory of the CHVS to implement a basic input/output system for the CHVS;
storing second code in the non-volatile memory, the second code being operable to:
initialize the CHVS;
receive a first transaction from a first virtual machine, a target of the first transaction being a full volume encryption (FVE) storage device of the CHVS;
send the first transaction to the FVE storage device;
receive a first response to the first transaction from the FVE storage device; and
send the first response to the first virtual machine;
determining to execute the second code to the exclusion of the first code; and
in response to determining to execute the second code, executing the second code.

### Claim 10 (depends on 9)

The method of claim 9, wherein the first virtual machine image includes an operating system and an application.

### Claim 11 (depends on 9)

The method of claim 9, wherein in sending the first transaction to the FVE storage device, the second code is further operable to send the first transaction to a general purpose encryption (GPE) engine of the CHVS.

### Claim 12 (depends on 11)

The method of claim 11, wherein:
the first transaction is a write transaction; and
in sending the first transaction to the GPE engine, the second code is further operable to:
direct the GPE engine to encrypt information associated with the first transaction; and
store the information on the FVE storage device.

### Claim 13 (depends on 11)

The method of claim 11, wherein:
the first transaction is a read transaction;
in sending the first transaction to the GPE engine, the second code is further operable to direct the GPE retrieve information associated with the first transaction from the FVE storage device; and
in receiving the first response to the first transaction from the FVE storage device engine, the second code is further operable to direct the GPE engine to decrypt the information.

### Claim 14 (depends on 9)

The method of claim 9, the second code being further operable to:
receive a second transaction from a second virtual machine, a target of the second transaction being the FVE storage device;
send the second transaction to the FVE storage device;
receive a second response to the second transaction from the FVE storage device; and
send the second response to the second virtual machine.

### Claim 15 (depends on 14)

The method of claim 14, the second code being further operable to:
receive a third transaction from the first virtual machine, a target of the third transaction being an unencrypted storage device of the CHVS;
send the third transaction to the unencrypted storage device;
receive a third response to the third transaction from the unencrypted storage device; and
send the third response to the first virtual machine.

### Claim 16 (depends on 15)

The method of claim 15, the second code being further operable to:
receive a fourth transaction from the second virtual machine, a target of the fourth transaction being an unencrypted storage device of the CHV S;
send the fourth transaction to the unencrypted storage device;
receive a fourth response to the fourth transaction from the unencrypted storage device; and
send the fourth response to the second virtual machine.

### Claim 17

Machine-executable code for an information handling system (IHS), wherein the machine-executable code is embedded within a non-transitory medium and includes instructions for carrying out a method, the method comprising:
storing first code in a non-volatile memory of the IHS to implement a basic input/output system for the IHS;
storing second code in the non-volatile memory, the second code being operable to:
initialize the IHS;
receive a first transaction from a first virtual machine, a target of the first transaction being a full volume encryption (FVE) storage device of the client hosted virtualization system;
send the first transaction to the FVE storage device;
receive a first response to the first transaction from the FVE storage device; and
send the first response to the first virtual machine;
determining to execute the second code to the exclusion of the first code; and
in response to determining to execute the second code, executing the second code.

### Claim 18 (depends on 17)

The machine-executable code of claim 17, wherein:
the first transaction is a write transaction;
in sending the first transaction to the FVE storage device, the second code is further operable to send the first transaction to a GPE engine of the client hosted virtualization system; and
in sending the first transaction to the GPE engine, the second code is further operable to:
direct the GPE engine to encrypt information associated with the first transaction; and
store the information on the FVE storage device.

### Claim 19 (depends on 17)

The machine-executable code of claim 17, wherein:
the first transaction is a read transaction;
in sending the first transaction to the FVE storage device, the second code is further operable to:
send the first transaction to a GPE engine of the client hosted virtualization system; and
direct the GPE retrieve information associated with the first transaction from the FVE storage device; and
in receiving the first response to the first transaction from the FVE storage device engine, the second code is further operable to direct the GPE engine to decrypt the information.

### Claim 20 (depends on 17)

The machine-executable code of claim 17, the second code being further operable to:
receive a second transaction from a second virtual machine, a target of the second transaction being the FVE storage device;
send the second transaction to the FVE storage device;
receive a second response to the second transaction from the FVE storage device; and
send the second response to the second virtual machine.
