VMware工作站完全指南：从入门到精通

需积分: 0 17 浏览量更新于2024-07-17 收藏 1.4MB PDF 举报

"《VMware工作站完全指南》是一本详细阐述VMware Workstation的书籍，适合于想要深入了解和使用VMware虚拟化技术的读者。本书介绍了VMware在质量保证、网络编程与测试、操作系统开发、研究及教育等领域的应用，并涵盖了VMware的其他产品线。书中深入讲解了VMware虚拟机的结构，包括处理器、总线、内存、中断以及各种虚拟设备如IDE硬盘、CD-ROM驱动器、SCSI硬盘、软驱、以太网接口、串口、并口、USB接口、图形硬件、鼠标和声卡。此外，还详细解析了PC BIOS和PC的启动过程。在安装章节中，书中指导了VMware Workstation在Windows系统的安装要求、升级步骤、启动方式、文件结构以及卸载方法。" 本书旨在为读者提供全面的VMware Workstation使用知识，从基本概念到高级功能，无论是新手还是经验丰富的用户都能从中获益。首先，"Overview"部分简要概述了VMware Workstation及其重要性，指出这本书适合所有对虚拟化技术感兴趣，特别是那些在软件测试、网络编程、系统开发以及教育领域工作的人员。第1章"Introduction"详细介绍了本书的目标读者群体、术语约定以及书本的布局结构。同时，列举了VMware的几种应用场景，包括质量保证部门用于软件测试，网络编程和测试以模拟不同网络环境，操作系统开发者进行研究和实验，以及在教育场景中的应用。此外，还提到了VMware的其他产品，例如可能与Workstation一同使用的其他虚拟化解决方案。第2章"The VMware Virtual Machine"深入探讨了VMware虚拟机的内部构造。这里详细解说了虚拟机的处理器、总线、内存和中断机制，以及虚拟化的硬件设备，如模拟的IDE和SCSI磁盘驱动器、光驱、软驱、网络适配器、串行和并行端口、USB设备、图形硬件和声音卡。通过这些内容，读者可以理解虚拟机如何模拟真实硬件环境。第3章"Installing VMware Workstation"则转向实际操作，讲述了在满足特定主机系统要求的情况下如何在Windows上安装VMware Workstation。这一章涵盖了从新安装到从旧版本升级的步骤，以及如何启动VMware，理解其文件结构和卸载程序的方法。《VMware工作站完全指南》是学习和掌握VMware Workstation的宝贵资源，它提供了从理论到实践的全面指导，帮助用户充分利用VMware虚拟化技术来提升工作效率和灵活性。

Chapter 2: The VMware Virtual Machine

Overview

VMware Workstation provides virtual hardware on top of a host computer’s real processor and memory. That

hardware is the focus of this chapter. First, we’ll take a short look at the hardware layout on a PC and show

where the line between virtual and real is on VMware. An overview of each virtual device follows. To provide

a base reference, a description of the real hardware accompanies each explanation of a virtual device.

The last two sections in this chapter are about the PC BIOS and boot process. You’ll need to know the

information there if you plan to use your disks in raw (direct) mode.

2.1 Processor, Bus, Memory, and Interrupts

A PC has three essential components: the CPU, memory, and I/O devices (which we’ll just call devices from

now on). CPU stands for central processing unit (or processor), and it is the heart of a computer. It not only

runs the instructions that comprise a program, but it also supervises the rest of the system.

Because a CPU can’t store all of the essential system data in its limited amount of storage space, the processor

needs external memory, in the form of random−access memory (RAM). Because this storage is very

important to the CPU’s operation, the CPU has nearly direct access to it. Between the CPU and its RAM is an

important layer called the memory management unit (MMU). This piece splits the RAM into many small

pieces known as pages. The MMU has a map (called a page table) of the CPU−addressed memory to pages in

real memory.

The memory that user programs see is called virtual memory (not a VMware term). When a CPU instruction

asks for a certain address in memory, the MMU redirects the access through its page table to a place in real

memory. (Note that this system is not hardware only; the operating system works with the MMU to get the

job done. Some older systems, such as DOS, do not use the MMU.)

On the other hand, it’s rare for a device to have a close connection to the CPU for two reasons. One is that

devices vary so much that it would be almost impossible to create an interface inside the CPU supporting each

device. Furthermore, devices often transmit data at irregular intervals, and several devices may try to talk to

the CPU at once. It doesn’t make sense for the CPU to bother with a device until all of its data is in order and

in a format that the CPU understands, so the CPU has a common bus that connects the devices to the CPU. In

addition, there are often extra controllers and interfaces between the devices and the bus; an example of this is

the SCSI controller.

VMware has two virtual buses, resembling those in most modern PCs: PCI and an extension off the PCI bus

called the PCI−to−ISA bridge. ISA is an old standard dating back to the first IBM PC. Though it is

remarkably inferior to current technology, backward compatibility keeps ISA alive.

Although certain devices, such as serial ports, still use the ISA interface, hardware developers avoid it

whenever possible because of its limitations. Some of those limitations have to do with interrupts and I/O

ports. Devices send interrupts over the bus to the CPU when they’re ready to transmit data or when they have

something otherwise significant to say. The CPU notices this, stops its current activity, and processes the

interrupt. ISA numbers its interrupts into interrupt request (IRQ) levels to differentiate them. Unfortunately,

did far more than a PC needed—a SCSI−I or II controller, for example, can handle up to seven disks or other

devices. Because a PC rarely has more than one or two hard drives, and other components are usually in the

form of Industry−Standard Architecture, or ISA, cards, PC designers decided that they might be able to reduce

costs by removing this flexibility. They came up with IDE disks, where the controller is actually integrated

into the disk itself, leaving only an ISA interface card on the PC’s motherboard.

As PCs became popular, IDE disks quickly became the most common commodity disks, and prices dropped

far below those of other disk types. However, the shortcuts taken in the design of IDE caused problems later,

and every time a new difficulty arose, someone added a new “standard” to the specification. For example, the

IDE interface didn’t support CD−ROM drives, so hardware

engineers squeezed ATAPI into the design. (ATAPI, or AT Attached Packet Interface, connects CD−ROM

and tape drives to the IDE interface.) In modern PCs, it isn’t even strictly true that the disks sit behind an

interface anymore—it’s hard to draw a clear line between the controller and the interface.

Like most PC motherboards, VMware Workstation has two IDE controllers, called the primary and secondary

interfaces. The virtual hardware is the Intel 82371AB PIIX4 chipset. The IRQ (or interrupt request) and port

assignments are as follows:

Interface IRQ I/O Ports

Primary 14 0x01f0 to 0x01f7, 0x03f6

Secondary 15 0x0170 to 0x0177, 0x0376

Like all IDE interfaces, each of these ports can support a maximum of two devices (sometimes called master

and slave devices). Under VMware, they are limited to disk, CD−ROM/DVD−ROM, CD−R, and CD−RW

drives that you can configure in a few different ways.

VMware stores virtual and plain disks as files on your host system. These files are images of a complete disk

and are usually quite large. A raw disk is a mapping from one of your real disks to a disk under VMware.

VMware disks provide some added flexibility that you don’t have with disks on a real machine, such as the

ability to undo or make a disk appear as read−write without actually altering the data underneath. You may

also configure VMware ATAPI CD−ROM drives as mappings to a real disk, or if you have a CD−ROM

image on your host system (such as an ISO9660 file), you can point VMware to that. (See page 58 for more

information on all of these modes and section 11.4 for a discussion of CD−ROM images.)

2.2.2 SCSI Disks

The small computer system interface, or SCSI, is a peripheral bus standard for small computers, meant for

attaching various devices to a computer. The bus is independent of the computer’s architecture, so you can,

for example, exchange SCSI devices between PC and Sun systems, assuming that you have the drivers for

those particular kinds of devices on those systems. The gateway between the SCSI bus and a computer is

called a SCSI host controller, though it’s often known as a SCSI adapter or SCSI card.

There are several types of SCSI buses: SCSI−I, SCSI−II, Fast SCSI−II, Ultra Wide SCSI, and so on. SCSI−I

and II can have up to eight devices on a bus (this number includes the host controller). Wide SCSI can handle

up to 16 devices. If you’re interested in SCSI, a good place to look is The Book of SCSI, 2nd Edition (another

No Starch Press publication; ISBN 1−886411−10−7).

VMware Workstation has virtual SCSI hardware. Its host controller is a PCI−based BusLogic BT−958 Ultra

Wide SCSI adapter. You can configure up to seven disks or CD−ROM drives from VMware’s controller,

Chapter 2: The VMware Virtual Machine

even though it shows up as wide (on real wide SCSI buses, you can have up to 15 devices). The special

VMware SCSI disk modes and features are the same as for the IDE disks mentioned in the previous section.

Because the virtual SCSI controller is a PCI device, the system dynamically configures the IRQ number and

I/O ports when it starts.

In addition to SCSI disks, VMware Workstation 3 supports arbitrary virtual SCSI devices such as CD−R

writers and SCSI scanners.

2.2.3 Floppy Drives

Probably the most primitive device that VMware supports is the PC floppy disk drive, and there isn’t much

hardware less intelligent than it. While floppy drives on other platforms have features such as automatic

media detection and eject notification, everything is manual on a PC floppy drive. Like the actual floppy disks

themselves, the hardware specification hasn’t changed in years. The floppy controller on a PC can’t even

figure out whether a drive is present or what size drive it is. It just tries to access the media based on a

predetermined configuration, and if it fails, it simply tells the operating system that it can’t cope.

However, this design is something of a blessing for VMware Workstation, because you don’t have to worry

about guest system support. You can configure one or two virtual floppy drives as mappings to real floppy

drives on your host system or as floppy image files on the host operating system, and as you work with floppy

disks under VMware, you’ll probably realize that the latter method is much more convenient. Floppy disks

not only tend to be unreliable, but they’re also slow. If you can just yank a floppy image off the disk at once

and point VMware at the file you created, you’ll get your work done quickly. You can also interact with

floppy images on the host system. (You’ll see how to do that in sections 11.2 and 11.3.)

The floppy controller resides at IRQ 6 on a PC, with I/O ports at 0x3f0 to 0x3f5 and 0x3f7.

To get around the deficiencies of the old floppy devices, vendors have started to offer USB and even IDE

floppy disk drives. In addition to VMware Workstation’s USB capability, a USB floppy drive on a Linux host

system shows up as a SCSI drive, and you can map it to a virtual SCSI drive. The benefits are somewhat

unclear though: If you’re interested in getting something off a floppy disk, it’s usually much faster to pull the

entire image off at once from your host system and throw the floppy disk away afterward.

2.2.4 Ethernet Interfaces

A network interface card (NIC) is an adapter that intercepts the signals on a network, filters them, and sends

them to the CPU for processing.

Ethernet is the most common type of local area network. Its low cost has led many PC manufacturers to

include onboard Ethernet interfaces on their machines. VMware’s virtual Ethernet interface is an AMD PCnet

II based on the AMD 79C970A chip.

You can add up to three interfaces to a virtual machine, in three kinds of configurations. A host−only network

exists only in the host operating system and is used primarily for communication between the host and guest.

In contrast, bridged networking multiplexes the host system’s real Ethernet interface in much the same way

that VMware multiplexes the host’s CPU, so a guest system can talk on the host’s network. NAT networking

is a host−only network that uses network address translation to communicate with outside networks.

Like the VMware SCSI controller, the virtual Ethernet interfaces are PCI devices, so the interrupts and I/O

ports are automatic at system boot.

Chapter 2: The VMware Virtual Machine

Networking support is one of VMware’s gems. After enabling it on your guest systems, you open up many

new possibilities for interaction between your host and guest systems. You aren’t limited to just sharing files;

you can use any feature that real networks offer, from SSH tunneling to remote print servers. Chapters 9 and

10 are dedicated to VMware networking and what you can achieve with it.

2.2.5 Serial Ports

An older type of peripheral interface, serial ports and lines transfer data between two devices one bit at a time.

The most common type of serial interaction is between a computer and a modem; internal modems also show

up as serial ports. The serial chip is called a UART (or universal asynchronous receiver−transmitter), and

these are now integrated into motherboard chipsets.

PC UARTs have a long history of not being up to scratch. The original 8250 and 16450 chips didn’t have

adequate buffering to store incoming characters. This wasn’t an issue with DOS, which didn’t have multiple

processes to worry about. But for real operating systems that were more than just program loaders, this

became a problem at speeds over 2400 baud, because the UART often overwrote incoming data before the

operating system kernel had a chance to pull the data out of the UART’s buffer. To fix this problem, the

16550 UART came around with a first−in, first−out (FIFO) queue buffer. Unfortunately, this chip had a bug

that rendered the FIFO buffer useless, and a replacement, the 16550A, was issued.

VMware Workstation has four serial ports with virtual 16550A UARTs. These ports are fixed at the PC

default hardware configuration, shown here:

DOS Name Linux Name IRQ I/O Ports

COM1: /dev/ttyS0 4 0x3f8 to 0x3ff

COM2: /dev/ttyS1 3 0x2f8 to 0x2ff

COM3: /dev/ttyS2 4 0x3e8 to 0x3ef

COM4: /dev/ttyS3 3 0x2e8 to 0x2ef

Under VMware, you can connect serial ports to actual devices, redirect output to files on the host system, or

even attach serial ports to pipes and pseudo−terminals on the host system.

Note Because the four ports share IRQs 3 and 4, you may run into trouble if you try to use the third or fourth

port because some operating systems (notably, older versions of Linux) don’t like to share serial port

IRQs.

2.2.6 Parallel Ports

Unlike serial ports, which send data one bit at a time to a device, parallel ports

send eight bits at a time. The design was originally intended as largely unidirectional, which made it

convenient for connecting a computer to moderate−bandwidth devices such as printers. As time went on,

though, parallel ports gained greater bidirectional capability so that a device could talk back to the computer.

Eventually, parallel ports became a sort of cheap alternative to SCSI. Though their bandwidth isn’t very high

and you can’t really effectively use more than one device on a parallel port at once, they come on practically

every PC, so parallel port Zip drives and the like popped up.

VMware Workstation supports two PC parallel ports in unidirectional and bidirectional modes:

DOS Name Linux Name IRQ I/O Ports

LPT1: /dev/lp0, /dev/parport0 7 0x3bc to 0x3be

Chapter 2: The VMware Virtual Machine

剩余213页未读，继续阅读

redepa

粉丝: 0
资源: 1

VMware工作站完全指南：从入门到精通

VMware Workstation 5.x 快照与克隆实战指南

VMware Workstation 15.5.6版本特性解析

VMware Workstation 10.0.x 安装与虚拟化技术详解

VMwareWorkstation.rar

macOS Unlocker V3.0 for VMware Workstation.zip

macOS Unlocker V3.0 for VMware Workstation.rar

VMware Workstation.v8.0.2.part07.rar (完美支持WIN8

VMware Workstation.v8.0.2.part08.rar (完美支持WIN8）

VMware Workstation.v8.0.2.part04.rar (完美支持WIN8）

VMware Workstation.v8.0.2.part05.rar (完美支持WIN8）

最新资源