# US 2008/0307213 A1 · Device allocation changing method

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

- Number: US 2008/0307213 A1
- Document ID: US20080307213A1
- Status: Published application
- Kind: A1
- Application number: 12/132,406
- Filed: 2008-06-03
- Published: 2008-12-11
- Earliest claimed: 2007-06-06
- Assignees: Hitachi, Ltd.
- Inventors: Tomoki SEKIGUCHI; Sachie TAJIMA; Hidetoshi SATO
- Web page: https://patentgrep.com/patent/US20080307213A1

## CPC

- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 2009/45575: {Starting, stopping, suspending or resuming virtual machine instances}
- G06F 2009/45579: {I/O management, e.g. providing access to device drivers or storage}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Switching of the allocation of a device to a guest OS is implemented through transmission of a virtual suspension interrupt to a guest OS in a VMM; a power control notification process module that causes the guest OS to start a return process from a suspended state; a guest power process module that traps a suspension process of the guest OS; an I/O configuration change process module that updates a logical device definition of the VMM in the suspended state of the guest OS; a guest I/O emulation process module that emulates an I/O instruction that is issued by an I/O reconfiguration process module and that is executed when the guest OS has returned from the suspended state, thereby to provide a new logical device configuration to the guest OS.

## Claims

### Claim 1

A device allocation changing method for changing a device allocation to a guest OS (operating system) in a virtual machine wherein an I/O (input/output) operation is executable by configuring a device either to be directly operable from the guest OS or to be operable through I/O emulation, the method comprising the steps of:
reconfiguring either a device (or a “direct allocation device,” hereinbelow) as a device for being used under the I/O emulation or a device, the direct allocation device being originally configured to be directly operable from the guest OS, or a device (or a “emulated device,” hereinbelow) for being used under the I/O emulation, the emulated device being originally configured to be directly operable from the guest OS; and
transmitting a virtual suspend instruction from a VMM (virtual machine monitor) to the guest OS, the suspend instruction being for suspending execution of the guest OS by stopping a guest OS, and causing the VMM to execute a device allocation changing process that changes the allocation of the device after completion of a suspension process that suspends the guest OS.

### Claim 2 (depends on 1)

A device allocation changing method according to claim 1, wherein the virtual suspend instruction is transmitted by a power control notification process of the VMM.

### Claim 3 (depends on 2)

A device allocation changing method according to claim 2, wherein an I/O instruction related to an I/O re-configuration process of the guest OS that is executed when the guest OS has returned from a suspended state is emulated by the VMM to configure a logical device after the device allocation change process.

### Claim 4 (depends on 1)

A device allocation changing method according to claim 1, wherein
as a device allocation change request to be made to the guest OS being executing, a physical device to be correlated a logical device and whether the physical device is set to be a direct allocation device or an emulated device is specified on the basis of each logical device to be configured; and
the VMM receives the change request inclusive of data necessary for re-initialization of the correlated physical device, and executes the allocation change process.

### Claim 5 (depends on 4)

A device allocation changing method according to claim 4, wherein, in a case where a device to be set as a direct allocation device is included in the change request, when the device is allocated an other guest OS, the allocation change process is abnormally terminated.

### Claim 6 (depends on 4)

A device allocation changing method according to claim 4, wherein a physical device different from the logical device before the configuration change process is allocated to the guest OS.

### Claim 7 (depends on 4)

A device allocation changing method according to claim 4, wherein the logical device to be configured by VMM through the I/O emulation is configured to be provided to the guest OS as a device of the same type as the emulated device that is allocated for emulation.

### Claim 8 (depends on 4)

A device allocation changing method according to claim 4, wherein, in the device allocation changing process, the VMM executes initializing process that initializes the physical device specified as a target of the allocation changing process by using the re-initialization data of the correlated to the physical device.

### Claim 9 (depends on 8)

A device allocation changing method according to claim 8, wherein in a re-initialization process of the device, an address such as a MAC address or an IP address is settable for an network adapter.

### Claim 10 (depends on 8)

A device allocation changing method according to claim 8, wherein in a re-initialization process of the device, a port ID is settable for a fiber channel adapter.
