JP2011221831A - Terminal switching system of virtual computer - Google Patents

Abstract

PROBLEM TO BE SOLVED: To utilize a job terminal used by a job virtual computer manager as a serial terminal for operating a guest OS.SOLUTION: In order for the serial port input and output of the guest OS to come and go on a job network, a virtual NIC provided in the job virtual computer is reused, and a serial information communication route inside a virtual computer firmware is changed.

Description

  The present invention relates to a virtual machine system, and more particularly to provision of a guest OS operation means by a serial terminal when a video terminal cannot be displayed due to a guest OS failure executed on the virtual machine.

  The operation of the OS includes a graphical screen operation using a GUI and a text screen operation using a character string. Here, the terminal that displays the former is called a video terminal, and the terminal that displays the latter is called a serial terminal. In a commercial OS for servers, it is common to use a video terminal for normal work and a serial terminal for emergency work such as OS failure recovery.

  In a virtual machine system that does not assume an OS failure, only a guest OS operation by a video terminal via a business network is provided. However, when a video terminal cannot be used due to a failure of the guest OS running on the business virtual machine, there is a drawback that the business virtual machine administrator has no means of operating the guest OS.

  As a measure for improvement, a guest OS operating means was provided via a management network by a serial terminal emulator provided in the management terminal. However, since the business virtual machine administrator does not have authority to use the management network, the physical computer I had to ask the administrator to operate the guest OS. Since this method exceeds the control range of the physical computer administrator, there are problems such as risk of erroneous operation and difficulty in emergency operation.

Hitachi Blade Symphony BS2000 User's Guide

  The problem to be solved is that a business virtual machine administrator who operates a guest OS running on a virtual machine has only a video terminal that can be used by a business virtual machine administrator. There is no means for the virtual machine administrator to operate the guest OS.

  The present invention reuses a virtual NIC, which is a network interface card emulated by a virtual machine system, provided in a business virtual machine so that serial port input / output information of a guest OS can be transferred over the business network. The serial information communication path in the firmware is changed. The communication path has a theoretical line length longer than that of the conventional path due to the addition of processing for converting the input / output information of the serial port to the input / output information of the network and the detour to the existing path for connection to the business network. Since the serial port communication speed is sufficiently lower than the network communication speed, the delay in information transmission due to the theoretical increase in line length can be ignored.

  The business terminal used by the business virtual machine administrator can be used as a serial terminal for operating the guest OS.

Configuration diagram of a computer implementing the present invention Business virtual machine configuration diagram Management virtual machine configuration diagram The block diagram of the hypervisor 300 before implementing this invention Functional comparison diagram before and after implementing the present invention provided to a terminal The block diagram of the hypervisor 300 after implementing this invention Configuration diagram of SOL emulator 342 added in the present invention It is explanatory drawing which showed the implementation procedure of this invention. Detailed explanation of the implementation procedure 402 of the present invention Configuration diagram of NIC emulator 312 and others before route switching Configuration diagram of NIC emulator 312 and others after path switching Explanatory drawing of the first half of the SW332 switching process Explanatory drawing of the latter half of the switching process of SW332

  The purpose of using a business terminal as a serial terminal was realized only by changing the hypervisor. However, it is assumed that the business terminal is equipped with a serial terminal emulator like the management terminal.

  FIG. 1 is a configuration diagram of a computer 10 to which the present invention is applied. A CPU 14 cooperates with a hypervisor 300 to support execution of a guest OS 110 and a management OS 210. The business virtual machine manager 22 is a virtual machine manager and uses the business terminal 21 to operate the guest OS 110 running on the business virtual machine via the NIC 15 connected to the business network 20. The physical computer manager 32 is a manager of the physical resources of the computer 10, the hypervisor 300, and the management OS 210, and uses the management terminal 31 to operate the hypervisor 300 operating on the computer 10 via the NIC 16 and the BMC 17 connected to the management network 30 The management OS 210 is operated.

  FIG. 2 is a configuration diagram of the business virtual machine 100 to which the present invention is applied. The virtual NIC 104 virtualized by the hypervisor 300 via the NIC driver 114 or 115 by the remote desktop service 112 provided in the guest OS 110. , 105, a graphical guest OS operation screen is transmitted to the network, and an OS operation from a network connected to the NIC is received. The serial console service 113 transmits a text-based guest OS operation screen to the virtual serial port 106 virtualized by the hypervisor 300 via the serial port driver 116, and receives an OS operation from the serial port.

  FIG. 3 is a configuration diagram of the management virtual computer 200 to which the present invention is applied. The management service 210 receives the graphical guest OS operation screen information transmitted from the guest OS 110 from the network connected to the virtual NIC 204, and the management OS 210 has a bridge service 213. The OS operation screen information is transferred to the NIC 15 via.

  The text-based guest OS operation screen information transmitted from the guest OS 110 is received from a device connected to the virtual serial port 206, and the OS operation screen information is converted into a network interface via the SOL service 212 provided in the management OS 210, and is sent to the NIC 16. Forward.

  FIG. 4 is a configuration diagram of the hypervisor 300 before applying the present invention. The MMIO control unit 310 is a substance of the virtual MMIO 102 included in the business virtual machine 100, and the NIC emulators 311 and 312 are included in the business virtual machine. The virtual NICs 104 and 105 are entities. The MMIO control unit 320 is the entity of the virtual MMIO 202 included in the management virtual computer 200, and the NIC emulator 321 is the entity of the virtual NIC 204 included in the management virtual computer. The NIC emulators 311 and 312 are connected to the NIC emulator 321 via the virtual NIC bridge 301 to perform network communication between the business virtual machine and the management virtual machine. The I / O port control unit 313 is an entity of the virtual I / O port 103 included in the business virtual machine 100, and the serial port emulator 314 is an entity of the virtual serial port 106 included in the business virtual machine. The I / O port control unit 323 is an entity of the virtual I / O port 203 included in the management virtual computer 200, and the serial port emulator 324 is an entity of the virtual serial port 206 included in the management virtual computer. The serial port emulator 314 and the serial port emulator 324 are connected to perform serial communication between the business virtual machine and the management virtual machine.

  FIG. 5 is a functional comparison diagram before and after the present invention provided to each terminal. FIG. 5A before the present invention shows that the guest OS 110 cannot be operated on the guest OS serial screen on the business terminal 21. FIG. 5B after the implementation of the present invention shows that the guest OS 110 can be operated on the guest OS serial screen in either the business terminal 21 or the management terminal 31.

  FIG. 6A is a configuration diagram of a hypervisor 300 to which the present invention is applied. SWs 330 and 331 add a path for connecting the MMIO control unit 310 to the invalid NIC emulator 340. SW 332 adds a path for connecting one of the NIC emulators 311 and 312 to the NIC driver 341, and SW 333 adds a path for connecting the serial port emulator 324 to the serial port driver 343. The SOL emulator 342 converts the network interface output information from the NIC driver 341 and the serial interface output information from the serial port driver 343 into the other interface input information.

  In FIG. 4, the I / O port control unit 313, serial port emulator 314, serial port emulator 324, I / O port control unit 323 serial interface I / O information includes virtual serial port 206, virtual Via the I / O port 203, the serial port driver 217, the SOL service 212, the NIC driver 214, the MMIO 13, and the NIC 16, it is transferred to the management network 30 in FIG. 1 and displayed on the management terminal 31 as a guest OS serial screen. Here, when a failure occurs in the remote desktop service 112, there is a problem that the business virtual machine administrator 22 has no means for operating the guest OS 110.

  For example, the I / O port control unit 313 and the serial port emulator 314, the serial port emulator 324, the SW 333, the serial port driver 343, the SOL emulator 342, and the NIC driver 341 shown in FIG. , SW 332, NIC emulator 312, virtual NIC bridge 301, NIC emulator 321, MMIO control unit 320, and via the virtual NIC 204, virtual MMIO 202, NIC driver 216, bridge service 213, NIC driver 215, MMIO 13, and NIC 15 in FIG. Thus, the guest OS serial screen can be displayed on the business terminal 21 by transferring the information to the business network 20 of FIG.

  When the NIC driver 115 operating on the business virtual machine 100 accesses the virtual NIC 105, the virtual NIC appears to be in a broken link state by the invalid NIC emulator 340, and the NIC emulator that is the entity of the virtual NIC without causing an OS failure 312 can be reused for switched path formation.

  The invalid NIC emulator 340 responds to the inquiry about the link status register value from the MMIO control unit 310 with a link disconnection status. The link disconnection state acquired by the MMIO control unit 310 is recognized by the guest OS 110 when the NIC driver 115 accesses the virtual MMIO 102.

  The NIC driver 341 is a software part having a function equivalent to that of a device driver that is generally incorporated in an OS, and implements dedicated processing for controlling the NIC emulators 311 and 312. Since this processing depends on the specifications of the NIC emulator, details are omitted in this document.

  Similarly, the serial port driver 343 implements a dedicated process for controlling the serial port emulator 324. The emulator is assumed to have a function implemented by 16550 (R), which is a UART chip adopted in a PC / AT (R) compatible machine, and the driver is implemented according to the specifications of the chip.

  FIG. 6B shows a protocol stack constituting the SOL emulator 342, a Telnet COM port control protocol processing unit 350 for converting serial port input / output information proposed by RFC (Request For Comment) 2217 into a TELNET protocol, and a TELNET. The TCP / IP protocol processing unit 351 is a lower layer of the protocol. The protocol group is implemented based on a publicly available specification, and performs conversion result input / output processing using the serial port driver 343 and the NIC driver 341, respectively.

  FIG. 7 shows the procedure of the route switching embodiment described above. FIG. 7B is a processing flow of the hypervisor 300 in which the procedure 402 in FIG. 7A is detailed.

  FIG. 8A is a configuration diagram of the NIC emulator 312 and the NIC driver 341 before switching the SW 332 in the above embodiment, and FIG. 8B is a structural diagram of the NIC emulator and the NIC driver after switching the SW. . SW 330, 331, 332, and 333 shown in FIG. 6A are images schematically showing connection paths between internal modules of the hypervisor 300, for example, to a table that stores function pointers, that is, function call entry addresses. This function is realized by resetting the pointer.

  FIG. 9 shows an example of a processing flow for realizing SW332 switching. This shows the details of the process 411 in FIG. In this example, it is assumed that the function pointer is reset as part of the initialization process of the NIC emulator 312 and the NIC driver 341. These initialization processes are intended to be general initialization for executing software, and since they are implementation-dependent, they are not described in this document.

  10 computers, 13 MMIO, 14 CPU, 15, 16 NIC, 17 BMC, 20 business network, 21 business terminal, 22 business virtual computer administrator, 30 management network, 31 management terminal, 32 physical computer administrator, 100 business virtual computer , 102 Virtual MMIO, 103 Virtual I / O port, 104, 105 Virtual NIC, 106 Virtual serial port, 110 Guest OS, 112 Remote desktop service, 113 Serial console service, 114, 115 NIC driver, 116 Serial port driver, 200 Management Virtual machine, 202 virtual MMIO, 203 virtual I / O port, 204 virtual NIC, 206 virtual serial port, 210 management OS, 212 SOL service, 213 bridge service, 14, 215, 216 NIC driver, 217 serial port driver, 300 hypervisor, 301 virtual NIC bridge, 310, 320 MMIO control unit, 311, 312, 321 NIC emulator, 313, 323 I / O port control unit, 314, 324 serial Port emulator, 330, 331, 332, 333 SW, 340 invalid NIC emulator, 341 NIC driver, 342 SOL emulator, 343 serial port driver, 350 Telnet COM port control protocol, 351 TCP / IP protocol, 402 Part of path switching procedure 411 Part of hypervisor processing

Claims (1)

  In a virtual machine system in which a physical machine is logically divided and used as a plurality of virtual machines, a virtual NIC which is a network interface card emulated by the virtual machine system and assigned to the virtual machine is reused. Terminal switching method.

Images