IBM Director Virtual Machine Manager 1.0 Installation and User s Guide

IBM Director 4.20 Virtual Machine Manager 1.0 Installation and User s Guide

Note Before using this information and the product it supports, read the general information in Appendix D, Notices, on page 59. First Edition (September 2004) Copyright International Business Machines Corporation 2004. All rights resered. US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents Figures........................... ii Tables............................ ix About this book........................ xi How this book is organized..................... xi Notices that are used in this document................ xii VMM documentation....................... xii VMM resources on the World Wide Web............... xii Chapter 1. Introducing Virtual Machine Manager............ 1 VMM enironment and terminology.................. 1 Oeriew of VMM integration with IBM Director............. 3 VMM Serer......................... 3 VMM Console......................... 4 VMM Agent.......................... 4 VMM Agent for VMware VirtualCenter................ 4 VMM Agent for Microsoft Virtual Serer............... 4 Virtual Machine Manager task.................... 5 Help............................ 5 Start Vendor Software...................... 6 IBM Director features that are releant to VMM objects.......... 7 Groups for use with VMM objects................. 7 Associations for use with VMM objects............... 7 Scheduler tasks for use with VMM objects.............. 7 Eent filters and actions for use with VMM objects........... 10 Chapter 2. Installing Virtual Machine Manager............ 11 System requirements....................... 11 Supported irtualization applications................ 11 Hardware requirements..................... 11 Supported operating systems.................... 11 VMM Serer......................... 11 VMM Console........................ 12 VMM Agent......................... 12 Downloading VMM....................... 12 Installing VMM......................... 12 Installing IBM Director Agent on guest operating systems......... 14 Uninstalling VMM........................ 14 Chapter 3. VMM objects and their discoery............. 15 Coordinator objects....................... 15 Operations for coordinator objects................. 15 Icons for coordinator objects................... 16 Farm objects.......................... 16 Operations for farm objects................... 17 Icons for farm objects..................... 17 Host objects.......................... 17 Icons for host objects..................... 18 Hosts that are running VMware ESX Serer............. 18 Hosts that are running Microsoft Virtual Serer............ 19 Virtual machine objects...................... 19 Icons for irtual machine objects................. 19 Copyright IBM Corp. 2004 iii

Virtual machines in VMware VirtualCenter.............. 20 Virtual machines in Microsoft Virtual Serer............. 20 Undoable disks........................ 21 Guest-operating-system objects................... 21 Manually discoering VMM objects................. 21 Manually discoering farms................... 22 Manually discoering irtual machines............... 22 Chapter 4. Working with credentials and configuring hosts....... 23 Credentials for coordinators.................... 23 Entering credentials for a coordinator................ 23 Reoking credentials for a coordinator............... 24 Configuring hosts in IBM Director.................. 24 Configuring hosts that are running VMware ESX Serer......... 24 Configuring hosts that are running Microsoft Virtual Serer........ 26 Deleting a VMM object from IBM Director............... 27 Chapter 5. Running power operations on irtual machines....... 29 Power operations for all irtual machines on a host........... 30 Powering-on all stopped irtual machines.............. 30 Suspending all running irtual machines.............. 30 Resuming all suspended irtual machines.............. 31 Powering-off all running irtual machines.............. 31 Power operations for a single irtual machine............. 31 Chapter 6. Viewing VMM object attributes.............. 33 Displaying coordinator object attributes................ 33 Displaying farm object attributes.................. 34 Displaying host object attributes.................. 34 Hosts in VMware VirtualCenter.................. 35 Hosts in Microsoft Virtual Serer................. 36 Displaying irtual machine object attributes.............. 36 Virtual machines in VMware VirtualCenter.............. 37 Virtual machines in Microsoft Virtual Serer............. 38 Chapter 7. Soling Virtual Machine Manager problems......... 39 Any supported irtualization enironment............... 39 VMware VirtualCenter enironment................. 39 Microsoft Virtual Serer enironment................. 41 Appendix A. Virtual Machine Manager eent filters and actions..... 43 Eents proided by VMM..................... 43 Virtual machine eents..................... 44 Coordinator, farm, and host eents................ 46 Eent actions proided by VMM.................. 48 Eent actions for adding hosts to or remoing hosts from farms...... 48 Eent actions for performing power operations on irtual machines..... 49 Eent actions for migrating irtual machines............. 51 Virtual machine task failures.................... 51 Command codes for irtual machine task failures........... 52 Failure codes for irtual machine task failures............ 52 Appendix B. Terminology summary and abbreiation list........ 55 VMM terminology summary.................... 55 Abbreiation list........................ 56 i IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

Appendix C. Getting help and technical assistance.......... 57 Before you call......................... 57 Using the documentation..................... 57 Getting help and information from the World Wide Web.......... 58 Software serice and support................... 58 Hardware serice and support................... 58 Appendix D. Notices...................... 59 Edition notice......................... 60 Trademarks.......................... 60 Glossary........................... 61 Index............................ 63 Contents

i IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

Figures 1. Oeriew of VMM enironment.......................... 3 2. VMM tasks that are displayed in IBM Director Console................. 5 3. Scheduler tasks for host management....................... 8 4. Scheduler tasks for power management...................... 10 5. Setup Type window............................. 13 6. Destination Folder window........................... 13 7. Question window.............................. 14 8. Enter Credentials window........................... 23 9. Add Host window.............................. 25 10. Migrate window............................... 26 11. VMM object attributes for a coordinator...................... 33 12. VMM object attributes for a farm......................... 34 13. VMM object attributes for a host in a VMware VirtualCenter enironment.......... 35 14. VMM object attributes for a host in a Microsoft Virtual Serer enironment.......... 36 15. VMM object attributes for a irtual machine in a VMware VirtualCenter enironment...... 37 16. VMM object attributes for a irtual machine in a Microsoft Virtual Serer enironment..... 38 17. Virtual machine eents in the Simple Eent Filter Builder window............ 44 18. Coordinator, farm, and host eents in the Simple Eent Filter Builder window........ 46 Copyright IBM Corp. 2004 ii

iii IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

Tables 1. IBM Director groups that are used only with VMM objects................ 7 2. Scheduler tasks for host objects.......................... 8 3. Status icons for coordinator objects........................ 16 4. Status icons for farm objects.......................... 17 5. Status icons for host objects.......................... 18 6. Status icons for irtual machine objects...................... 20 7. Power Management menu options for irtual machines................. 31 8. VMM object attributes for a coordinator...................... 33 9. VMM object attributes for a farm......................... 34 10. VMM object attributes for a host in a VMware VirtualCenter enironment.......... 35 11. VMM object attributes for a host in a Microsoft Virtual Serer enironment.......... 36 12. VMM object attributes for a irtual machine in a VMware VirtualCenter enironment...... 37 13. VMM object attributes for a irtual machine in a Microsoft Virtual Serer enironment..... 38 14. VMM problems in any supported irtualization enironment............... 39 15. VMM problems in a VMware VirtualCenter enironment................ 39 16. VMM problems in a Microsoft Virtual Serer enironment................ 41 17. Virtual machine eents............................. 44 18. Coordinator, farm, and host eents........................ 47 19. Actions aailable for Manage a Host eent action................... 49 20. Actions aailable for Manage a Virtual Machine eent action............... 50 21. Command codes that are returned by Virtual Machine, Task Failed eents......... 52 22. Failure codes that are returned by Virtual Machine, Task Failed eents........... 52 Copyright IBM Corp. 2004 ix

x IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

About this book How this book is organized This book describes IBM Virtual Machine Manager 1.0 and how to use VMware VirtualCenter and Microsoft Virtual Serer in an IBM Director enironment. Chapter 1, Introducing Virtual Machine Manager, on page 1 contains an oeriew of Virtual Machine Manager (VMM), including its components and features, and its integration with IBM Director. This chapter also describes the features of IBM Director that are releant to VMM objects. Chapter 2, Installing Virtual Machine Manager, on page 11 details the system requirements for VMM and how to install and uninstall VMM. Chapter 3, VMM objects and their discoery, on page 15 describes the arious objects in VMM, explains their state icons, and describes discoery of these objects. Chapter 4, Working with credentials and configuring hosts, on page 23 proides information about entering and reoking credentials for coordinators and how to use IBM Director Console to configure hosts that define irtual machines. This chapter also explains how to delete VMM objects from IBM Director Console. Chapter 5, Running power operations on irtual machines, on page 29 describes the power operations that you can perform on irtual machines. Chapter 6, Viewing VMM object attributes, on page 33 describes the VMM object attributes that VMM displays for coordinators, farms, hosts, and irtual machines. Chapter 7, Soling Virtual Machine Manager problems, on page 39 lists some of the problem symptoms and suggested solutions for VMM. Appendix A, Virtual Machine Manager eent filters and actions, on page 43 describes the eent filters and actions that are proided by VMM that you can use with IBM Director eent action plans. This chapter also describes the irtual machine task failures that can occur. Appendix B, Terminology summary and abbreiation list, on page 55 contains a summary of VMM terminology and a list of abbreiations that are used in VMM documentation. Appendix C, Getting help and technical assistance, on page 57 contains information about accessing IBM Support Web sites for help and technical assistance. Appendix D, Notices, on page 59 contains product notices and trademarks. The Glossary on page 61 proides definitions for terms that are used in VMM documentation. Copyright IBM Corp. 2004 xi

Notices that are used in this document VMM documentation This document contains the following notices designed to highlight key information: Note: These notices proide important tips, guidance, or adice. Important: These notices proide information or adice that might help you aoid inconenient or difficult situations. Attention: These notices indicate possible damage to programs, deices, or data. An attention notice is placed just before the instruction or situation in which damage could occur. The Web site for VMM proides the following document in Adobe Acrobat Portable Document Format (PDF): Virtual Machine Manager 1.0 Installation and User s Guide You can also obtain this document from the IBM Support Web site at http://www.ibm.com/pc/support/. VMM resources on the World Wide Web The following Web pages proide resources for understanding, using, and troubleshooting IBM Director and systems-management tools. IBM Support page http://www.ibm.com/pc/support/ This is the IBM Support Web site for IBM hardware and systems-management software. For systems-management software support, click Systems management. IBM Systems Management Software: Download/Registration page http://www.ibm.com/pc/us/eserer/xseries/systems_management/dwnl.html Use this Web page to download IBM systems-management software, including IBM Director. IBM xseries Systems Management page http://www.ibm.com/pc/ww/eserer/xseries/systems_management/index.html This Web page presents an oeriew of IBM systems management and IBM Director. Click IBM Director 4.2 for the latest information and documentation. IBM SererProen page http://www.ibm.com/pc/us/compat/index.html This Web page proides information about IBM hardware compatibility with IBM systems-management software. xii IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

Chapter 1. Introducing Virtual Machine Manager IBM Virtual Machine Manager (VMM) enables the use of the following irtualization applications in an IBM Director enironment: VMware VirtualCenter Microsoft Virtual Serer When VMM and these irtualization applications are installed, you can perform the following tasks from IBM Director Console: Correlate relationships between physical platforms and irtualization components Report status of physical platforms and their corresponding irtualization components Log in to the management interface of the irtualization application Discoer irtualization components Perform migration and power operations on irtual machines Create eent action plans that inole irtualization components When VMM is installed, IBM Director can recognize systems that contain irtualization components. Next, VMM can create VMM objects to represent the irtualization components that were recognized. VMM uses the application programming interface (API) of the irtualization application to perform VMM operations on the irtualization component itself. Both IBM Director Console and the irtualization application then are updated. All VMM Console operations, such as powering on a irtual machine, are run as background processes. Therefore, IBM Director Console can be used for other operations while VMM performs its operations. VMM enironment and terminology The hardware in a VMM enironment is referred to in the following ways: A management serer is a serer on which both IBM Director Serer and VMM Serer are installed. A management console is a system on which both IBM Director Console and VMM Console are installed. In a VMware VirtualCenter enironment, this system must also be installed with VMware VirtualCenter client, which proides a graphical user interface (GUI) to an instance of VMware VirtualCenter serer. A managed system is a system on which IBM Director Agent and a irtualization application are installed. A system is a serer, workstation, desktop computer, or mobile computer. The software and its components in a VMM enironment are referred to in the following ways: A irtualization application is one of the following applications: VMware VirtualCenter serer VMware ESX Serer Microsoft Virtual Serer A irtualization component is a software element that is created by a irtualization application. Copyright IBM Corp. 2004 1

A VMM object is an IBM Director managed object that represents the irtualization components in a VMware VirtualCenter enironment or in a Microsoft Virtual Serer enironment. VMM objects include coordinators, farms, hosts, irtual machines, and guest operating systems. The following VMM objects are used by VMM: A coordinator is a managed object that represents a system on which all of the following software is running: VMware VirtualCenter serer VMware VirtualCenter Web serice IBM Director Agent VMM Agent A farm is a managed object that represents a collection of hosts and their associated irtual machines as defined by a farm configured on a VMware VirtualCenter serer. A host is a managed object that represents a system on which one of the following combinations of software are running: VMware ESX Serer and IBM Director Agent Microsoft Virtual Serer, IBM Director Agent, and VMM Agent. A irtual machine is a managed object that represents a irtual machine that is associated with a system that is running VMware ESX Serer or Microsoft Virtual Serer. A guest operating system is a managed object that represents an operating system that is running in a irtual machine and on which IBM Director Agent is installed. In a VMware VirtualCenter enironment, VMM uses coordinators, farms, hosts, irtual machines, and guest operating systems. In a Microsoft Virtual Serer enironment, VMM uses hosts, irtual machines, and guest operating systems. For detailed explanations of VMM objects and how they are used, see Chapter 3, VMM objects and their discoery, on page 15. 2 IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

Oeriew of VMM integration with IBM Director VMM includes the following software components: VMM Serer VMM Console VMM Agent Figure 1 shows how VMM is integrated with IBM Director, VMware VirtualCenter, and Microsoft Virtual Serer. Management serer IBM Director Serer installed VMM Serer installed No irtualization software necessary Management console IBM Director Console installed VMM Console installed (VMware only) VMware VirtualCenter client installed Managed system running Microsoft Virtual Serer Microsoft Virtual Serer installed IBM Director Agent installed VMM Agent installed Managed system running VMware ESX Serer IBM Director Agent installed No VMM component necessary Managed system running VMware VirtualCenter VMware VirtualCenter serer installed VMware VirtualCenter Web serice installed IBM Director Agent installed VMM Agent installed Figure 1. Oeriew of VMM enironment VMM Serer VMM Serer is the main component of Virtual Machine Manager because it maintains the VMM enironment and manages all VMM operations. VMM Serer communicates with VMM Agent and VMM Console to display status and perform operations for VMM objects. VMM Serer communicates with IBM Director Serer to proide eent filtering and eent actions that support IBM Director eent action plans that inole VMM objects. VMM Serer must be installed on the management serer. When you install VMM Serer, VMM Console is installed automatically also. Chapter 1. Introducing Virtual Machine Manager 3

VMM Console VMM Console is the graphical user interface (GUI) component of VMM. VMM Console must be installed on any management console from which a system administrator will remotely access the management serer and perform VMM tasks. Note: If you are using VMware VirtualCenter with IBM Director, the VMware VirtualCenter client must be installed on the system where IBM Director Console and VMM Console are installed. Otherwise, you cannot start the VMware VirtualCenter client with the Start Vendor Software subtask of VMM. Microsoft Virtual Serer does not hae the same requirement, because it has a Web interface. VMM Agent VMM proides a different ersion of VMM Agent for each irtualization application that it supports. The installation program for VMM automatically detects which irtualization application is installed and displays the correct installation choice for the applicable ersion of VMM Agent. Note: VMM Agent can proide support only for features that are proided by the irtualization application. For example, when VMM Agent is installed on a system that is running VMware VirtualCenter, you can migrate irtual machines from one host to another. When VMM Agent is installed on a system that is running Microsoft Virtual Serer, this support is not proided. VMM Agent performs the following functions: Discoers irtualization application and creates VMM objects Relays communication between VMM Serer and the irtualization application Translates eents that are proided by the irtualization application into eents that can be used in IBM Director eent action plans VMM Agent for VMware VirtualCenter Install VMM Agent on a system that is running IBM Director Agent, VMware VirtualCenter serer, and VMware VirtualCenter Web serice. These software components enable VMM and IBM Director to recognize this managed system as a coordinator object, which you can iew and manage from IBM Director Console. For more information, see Coordinator objects on page 15. VMM Agent for Microsoft Virtual Serer Install VMM Agent on the system that is running Microsoft Virtual Serer. You also must install IBM Director Agent on this system. These software components enable VMM and IBM Director to recognize this managed system as a host object, which you can iew and manage from IBM Director Console. For more information, see Host objects on page 17. 4 IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

Virtual Machine Manager task When you add VMM Console to your IBM Director enironment, the Virtual Machine Manager task is added to IBM Director Console. The Virtual Machine Manager task has the following two subtasks: Help Start Vendor Software Figure 2 shows the IBM Director Console window with VMM and its tasks in the Tasks pane. Figure 2. VMM tasks that are displayed in IBM Director Console The icon is used to identify the following VMM features: The Virtual Machine Manager task The VMM Systems group Windows, eent actions, scheduler tasks, and help topics that are proided by VMM Additionally, VMM adds arious state icons to the VMM objects that are displayed in the Group Contents pane of IBM Director Console. For information, see the descriptions of the state icons for the arious VMM object types in Chapter 3, VMM objects and their discoery, on page 15. Help You can use the Help subtask to access and iew the help pages that are proided with VMM. To start the Help subtask, double-click the subtask. Use the links at the bottom of each help page to naigate the help that is proided for VMM and its subtasks. Chapter 1. Introducing Virtual Machine Manager 5

Start Vendor Software You can use the Start Vendor Software subtask to start the irtualization application for the targeted VMM object. To start the Start Vendor Software subtask, drag it onto any VMM object in the Group Contents Pane. You must run this subtask on a VMM object. When you start this subtask, VMM determines whether the VMM object exists in VMware VirtualCenter or Microsoft Virtual Serer. Then, the applicable irtualization application is started. VMware VirtualCenter When you drag the Start Vendor Software subtask onto a VMM object that is in a VMware VirtualCenter enironment, VMM starts the VMware VirtualCenter client interface. Log in to the VMware VirtualCenter serer for the VMM object that you want to manage. After you hae successfully logged in, you can access and use the features of VMware VirtualCenter client, which enables administration of multiple irtual machines and VMware ESX Serer instances that are associated with one VMware VirtualCenter serer. Use the VMware VirtualCenter client only when VMM does not proide equialent functionality, for example, creation of irtual machines. Otherwise, use the features that are proided by VMM. For information about VMware VirtualCenter and its client interface, see the documentation that comes with that product. Microsoft Virtual Serer When you drag the Start Vendor Software subtask onto a VMM object that is in a Microsoft Virtual Serer enironment, VMM starts the Administration Web site, which is the user interface to Microsoft Virtual Serer. Log in to the Microsoft Virtual Serer that you want to manage. After you hae successfully logged in, you can access and use the features of Microsoft Virtual Serer, which enables administration of multiple irtual machines that are hosted on a single system. Use the Microsoft Virtual Serer user interface only when VMM does not proide equialent functionality, for example, creation of irtual machines. Otherwise, use the features that are proided by VMM. For information about Microsoft Virtual Serer and its Administration Web site, see the documentation that comes with that product. 6 IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

IBM Director features that are releant to VMM objects IBM Director includes seeral features that are releant to VMM objects. Groups for use with VMM objects IBM Director proides seeral default groups of managed objects in the Groups pane for easier management of objects. Some of these groups, like the Logical Platforms group and the Platforms group, will display some VMM objects. VMM has additional groups just for VMM objects. Table 1 lists the groups that apply only to VMM objects. Table 1. IBM Director groups that are used only with VMM objects Group name Farms VMM Systems Includes these VMM objects Only farms Only VMM objects, which includes coordinators, farms, hosts, irtual machines, and guest operating systems Associations for use with VMM objects You can use IBM Director associations to display the VMM objects of a group in the Group Contents pane in a logical ordering, and if applicable, in a tree structure. Both IBM Director and VMM proide associations that are releant to VMM objects. Use the VMM Systems group with these associations to list just the VMM objects on IBM Director Serer. VMM proides one association, the VMM Systems Membership association, that applies only to VMM objects. This association alphabetically orders the objects in a group by coordinator and then all remaining hosts. For coordinators, each object is shown in a tree structure that lists the farms, hosts, irtual machines, and guest operating systems that are associated with the coordinator. For each remaining host, each object is shown with a tree structure that lists the irtual machines and guest operating systems that are associated with that host. Scheduler tasks for use with VMM objects You can use IBM Director Scheduler to create jobs that perform tasks on a single host or on a single irtual machine. For detailed procedures for creating and monitoring scheduled jobs, see the IBM Director 4.20 Systems Management Guide. Note: The execution history proides details only about the start and completion of the job. It does not proide details about the success or failure of the VMM operations that are performed by the job. For that information, use the IBM Director Eent Log task to iew details about all operations that hae been receied and logged by IBM Director Serer. For information about irtual machine operations that fail, see Virtual machine task failures on page 51. For information about the Eent Log task, see the IBM Director 4.20 Systems Management Guide. Chapter 1. Introducing Virtual Machine Manager 7

Tasks for a single host You can use the Scheduler in IBM Director Console to create scheduled jobs that perform operations on a specific host. You can perform operations that affect a host directly or affect all irtual machines on a host. These Scheduler tasks for use with hosts are under Host Management on the Tasks page of the New Scheduled Job window. Notes: 1. The Targets page of the New Scheduled Job window lists all managed objects that are shown in the Group Contents pane of IBM Director Console. Howeer, you must target host tasks to only host managed objects; otherwise, the task will fail. 2. Status icons for VMM objects are not shown on the Targets page of the New Scheduled Job window. Figure 3 shows the New Scheduled Job window with the host management operations that you can schedule. Figure 3. Scheduler tasks for host management Table 2 describes each of these host management tasks. Important: The power operations for the irtual machines on a single host apply to all irtual machines that are associated with a single VMware ESX Serer or a single Microsoft Virtual Serer, een those irtual machines that are not represented in IBM Director Console. Table 2. Scheduler tasks for host objects Scheduler task Force Power Off All Running Virtual Machines Description Powers-off all running irtual machines that are associated with a host without an orderly shut down of any guest operating systems. 8 IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

Table 2. Scheduler tasks for host objects (continued) Scheduler task Power On All Stopped Virtual Machines Remoe Host From Farm Resume All Suspended Virtual Machines Start Stop Suspend All Running Virtual Machines Description Powers-on all stopped irtual machines that are associated with a host. (Hosts that are running VMware ESX Serer only) Remoes the managed object for the host from the farm managed object in IBM Director Console. Resumes all suspended irtual machines that are associated with a host. (Hosts that are running Microsoft Virtual Serer only) Starts the host that is represented by the managed object. You can only create scheduled jobs that use this task for hosts that are currently stopped. (Hosts that are running Microsoft Virtual Serer only) Stops the host that is represented by the managed object. You can create scheduled jobs that use this task only for hosts that are currently started. Suspends all running irtual machines that are associated with a host. If you use a task that applies to all irtual machines on a host, VMM generates a Virtual Machine, Task Failed eent for each irtual machine that cannot perform the task. For example, if you use Power On All Stopped Virtual Machines and two irtual machines are already powered-on, VMM will generate two Virtual Machine, Task Failed eents because those two irtual machines could not be powered-on. For more information about irtual machine operations that fail, see Virtual machine task failures on page 51. Tasks for a single irtual machine You can use the Scheduler in IBM Director Console to create scheduled jobs that perform operations on a specific irtual machine. These Scheduler tasks for use with irtual machines are under Power Management on the Tasks page of the New Scheduled Job window. Notes: 1. You only can use some of these power management operations with irtual machine objects. For information about which ones are supported, see Table 7 on page 31 in the section Power operations for a single irtual machine. 2. The Targets page of the New Scheduled Job window lists all managed objects that are shown in the Group Contents pane of IBM Director Console. Howeer, you must target power operation tasks to only irtual machine objects; otherwise, the task will fail. 3. Status icons for VMM objects are not shown on the Targets page of the New Scheduled Job window. Chapter 1. Introducing Virtual Machine Manager 9

Figure 4 shows the New Scheduled Job window with the power management operations that you can schedule. Figure 4. Scheduler tasks for power management Eent filters and actions for use with VMM objects VMM proides seeral eents and eent actions for use with VMM objects. For more information about using eents and eent actions with VMM objects, see Appendix A, Virtual Machine Manager eent filters and actions, on page 43. 10 IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

Chapter 2. Installing Virtual Machine Manager System requirements This chapter proides information about system requirements, supported systems, and instructions for installing and uninstalling VMM 1.0 In addition to the requirements that are applicable to IBM Director 4.20, VMM has further requirements regarding the hardware and software with which it can be used. Supported irtualization applications VMM 1.0 supports the following irtualization applications: VMware VirtualCenter 1.1.x Microsoft Virtual Serer 2005 (VMware enironment only) Notes: 1. Only VMware ESX Serer hosts are supported with VMware VirtualCenter in IBM Director. 2. The VMware VirtualCenter client must be installed on the system where IBM Director Console and VMM Console are installed. Hardware requirements This section describes the hardware requirements for VMM. Supported operating systems Management serers and management consoles VMM has these additional hardware requirements beyond those of IBM Director 4.20: VMM Serer needs 10 MB of additional disk space VMM Console needs 10 MB of additional disk space Managed systems You can install VMM Agent on any platform that supports IBM Director 4.20 Agent and the irtualization application that you plan to use. Howeer, depending on the irtualization application that you are using, VMM has these additional hardware requirements beyond those of IBM Director 4.20: Managed systems running VMware VirtualCenter need 10 MB of additional disk space Managed systems running Microsoft Virtual Serer need 10 MB of additional disk space. This section lists the operating systems upon which the components of VMM 1.0 are supported. VMM Serer VMM Serer is supported for use with IBM Director 4.20 management serers that are running any supported Windows operating system. Copyright IBM Corp. 2004 11

VMM Console VMM Agent VMM Console is supported for use with IBM Director 4.20 management consoles that are running any supported Windows operating system. VMM Agent is supported for use on Windows operating systems that are supported by both IBM Director 4.20 managed systems and irtualization applications on that managed system. Downloading VMM Installing VMM Complete the following steps to download VMM from the IBM Web site: 1. Go to http://www.ibm.com. 2. Click Support & Downloads. 3. Click Downloads & driers. 4. In the Enter search terms field, type Virtual Machine Manager 1.0 and click Submit. 5. Click Systems Management - Virtual Machine Manager 1.0. 6. Click the file link for the executable file to download the file. You also can download the VMM readme text file and the Virtual Machine Manager 1.0 Installation and User s Guide from this Web page. 7. Copy the downloaded file to a local drie on each management serer, management console, and managed system on which you want to install VMM. The VMM installation program detects whether IBM Director Serer or IBM Director Console are installed on a system and automatically displays installation choices for the corresponding VMM components. If IBM Director Agent is installed on a system that contains a supported irtualization application, the VMM installation program detects which irtualization application is installed and automatically displays an installation choice for the applicable ersion of VMM Agent. Notes: 1. (VMware enironment only) Before you use VMM, you must also install the VMware VirtualCenter Web serice on the managed system that is running VMware VirtualCenter. 2. Do not install VMM Agent on any managed system that is running VMware ESX Serer. Complete the following steps to install VMM: 1. If IBM Director Console is running, close it. 2. From the system on which you want to install VMM, run the executable file that you downloaded. Note: The operating-system account that is used to install VMM has at least local Administrator authority. The VMM Setup program starts, and the Welcome to the InstallShield Wizard for IBM Virtual Machine Manager window opens. 3. Click Next. The License Agreement window opens. 12 IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

4. Click I accept the terms in the license agreement and click Next. The Setup Type window opens. Figure 5. Setup Type window 5. Select the check box for the type of installation that you want and click Next. The Destination Folder window opens. Note: You can select only those installation types that are applicable for the system on which you are installing VMM. For example, you cannot install VMM subagent for VMware VirtualCenter unless VMware VirtualCenter is installed on the system. Figure 6. Destination Folder window 6. Click Next. The Ready to Install the Program window opens. 7. Click Install. If you are installing VMM Serer or VMM Agent, the Question window opens. Chapter 2. Installing Virtual Machine Manager 13

8. Click Yes. The Installing IBM Virtual Machine Manager window opens. The progress of the installation is displayed. When the installation is completed, the InstallShield Wizard Completed window opens. 9. Click Finish. Installing IBM Director Agent on guest operating systems Uninstalling VMM Figure 7. Question window You also must install IBM Director Agent on all guest operating systems that you want to iew through IBM Director Console. When IBM Director Agent is installed on guest operating systems, VMM can recognize these objects as guest operating systems and correlates them to their irtual machines within IBM Director. For information about installing IBM Director Agent and the operating systems that it supports, see the IBM Director 4.20 Installation and Configuration Guide. You must uninstall VMM 1.0 before you uninstall IBM Director 4.20. The IBM Director 4.20 setup program does not uninstall VMM 1.0. Complete the following steps to uninstall VMM: 1. If necessary, close IBM Director Console. 2. Click Start Settings Control Panel. The Control Panel window opens. 3. Double-click Add/Remoe Programs. The Add/Remoe Programs window opens. 4. Click IBM Virtual Machine Manager. 5. Click Remoe. 6. When prompted Are you sure you want to remoe IBM Virtual Machine Manager from your computer, click Yes. 7. (VMM Serer and VMM Agent only) When you are prompted The action you are about to perform will stop the IBM Director Serice. Do you want to continue?, click Yes. 14 IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

Chapter 3. VMM objects and their discoery Coordinator objects This chapter describes VMM objects and how they are discoered Note: You cannot create any irtualization components in IBM Director. Instead, you must create irtualization components in the irtualization application that you are using. Then, Virtual Machine Manager and IBM Director can discoer these irtualization components and create VMM objects that are based on the information that they discoer about a specific installation of a irtualization application. VMM assigns arious attributes to VMM objects. For information, see Chapter 6, Viewing VMM object attributes, on page 33. This information applies only to systems that are running VMware VirtualCenter serer. A coordinator object is a managed object that represents a physical system on which all of the following software is installed: VMware VirtualCenter serer VMware VirtualCenter Web serice IBM Director Agent VMM Agent A coordinator object is a particular type of managed system. When IBM Director Serer discoers that VMM Agent is running on a managed system, it registers serices for VMM Agent. When VMM Serer detects that VMM Agent has been registered with IBM Director Serer, it recognizes the managed system as a coordinator object. IBM Director does not recognize a managed system as a coordinator until the managed system has been unlocked from IBM Director Console. (The padlock icon beside a managed system indicates that the object is secured.) To request access to the object, right-click the managed system and click Request Access. By proiding a alid user name that has local administratie rights to that managed system and its password, you can unlock and access the system. A coordinator object can manage multiple farms, the hosts that they contain, and their irtual machines and guest operating systems. Operations for coordinator objects You can perform the following operations on coordinator objects: Discoer farms Enter credentials Reoke credentials Note: Before you can manage a coordinator object, you must enter credentials to login to VMware VirtualCenter serer. For information, see Credentials for coordinators on page 23. Copyright IBM Corp. 2004 15

Icons for coordinator objects IBM Director Console displays a system icon for a managed system object. When VMM recognizes the managed system as a coordinator, it adds a second icon to depict status information about VMware VirtualCenter serer. VMM obtains status information from the irtualization application. For example, a system that is running VMware VirtualCenter serer and that has not yet granted permission to IBM Director to perform operations on VMM objects is represented in IBM Director Console as. Note: VMM does not add a status icon to a coordinator object when VMware VirtualCenter serer is aailable for use and authenticated with IBM Director. Table 3 describes the status icons that are used for coordinator objects. Table 3. Status icons for coordinator objects Icon Description The VMware VirtualCenter serer has not granted permission to IBM Director to perform operations on VMM objects. The serer is no longer running one of the required serices, VMware VirtualCenter serer or VMware VirtualCenter Web serice. VMM requires both of these serices. The serer is powered-on but has an error condition. Generally this problem has two causes: VMM Agent or IBM Director Agent is not running. VMware VirtualCenter serer or VMware VirtualCenter Web serice is not installed. Farm objects This information applies only to systems that are running VMware VirtualCenter serer. A farm object is a managed object that represents a farm configured on an instance of VMware VirtualCenter serer. A farm is a logical grouping of hosts and their irtual machines; it does not represent a physical system. A farm object is a new managed object that is created specifically by VMM. After IBM Director creates a coordinator object for a system that is running VMware VirtualCenter serer, VMM Agent continues the discoery process to identify farms that are in a VMware VirtualCenter enironment and create farm objects for these farms. If necessary, you can request the creation of farm objects after IBM Director has discoered a coordinator object. For information, see Manually discoering farms on page 22. A farm object can manage multiple hosts and their associated irtual machines. Farm objects in VMM are not identical to farm objects in VMware VirtualCenter because VMM does not use the hierarchical model that VMware uses. VMware VirtualCenter supports collections of farms, which are referred to as farm groups. This concept enables VMware VirtualCenter to present farms in hierarchical groups within the VMware VirtualCenter client. Howeer, VMM does not hae a farm group concept and does not support this type of farm hierarchy. When VMM Agent creates a farm object for a VMware VirtualCenter farm that is a member of one or more 16 IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

farm groups, the name of the farm object is a concatenation of the names of its farm groups and the farm itself, for example, FarmGroup1/FarmSubGroup1/Farm. Note: If a farm that is contained within a farm group is discoered and later that farm group is renamed in VMware VirtualCenter, unexpected behaior can occur with the farm object in the VMM enironment. This unexpected behaior for the farm object occurs for all instances of IBM Director Serer that are tracking actiity on that farm object. After a farm group is renamed, you should reoke and enter credentials for the coordinator object that contains the farm object. Operations for farm objects You can perform the following operations for farm objects: Add a host to a farm Remoe a host from a farm For information about these operations, see Configuring hosts that are running VMware ESX Serer on page 24. Icons for farm objects IBM Director Console displays a farm icon for a farm object. VMM uses a second icon to depict status information about the farm. VMM obtains status information from the irtualization application. Note: VMM does not add a status icon to a farm object when VMware VirtualCenter serer is aailable for use and authenticated with IBM Director. For example, a farm that is aailable for use in VMware VirtualCenter is represented in IBM Director Console as. Table 4 describes the status icons that are used for farm objects. Table 4. Status icons for farm objects Icon Description A farm whose coordinator has not authenticated with VMware VirtualCenter serer. For more information, see Credentials for coordinators on page 23. VMM also displays this icon for a farm when the VMware VirtualCenter Web serice on the coordinator has been stopped. This icon is displayed when the coordinator of the farm has an error condition. Host objects A host object is a managed object that represents a physical system on which one of the following sets of software are installed: VMware ESX Serer and IBM Director Agent Microsoft Virtual Serer, IBM Director Agent, and VMM Agent A host object is a particular type of managed system. After IBM Director creates a farm object for a farm that is in a VMware VirtualCenter enironment, VMM queries the irtualization application for the hosts that the farm contains. For each host that is identified, VMM matches it with an Chapter 3. VMM objects and their discoery 17

existing IBM Director managed system. If a managed object does not already exist for the physical system, VMM will not create a managed object for it. A host object can manage multiple irtual machines and their guest operating systems. The following sections describe the icons that are used for host objects and how VMM supports hosts that are running VMware ESX Serer or running Microsoft Virtual Serer. Icons for host objects IBM Director Console displays a system icon for a managed system object. When VMM recognizes a managed system as a host, it adds a second icon to depict status information about the host. VMM obtains status information from the irtualization application. For example, a system that is running VMware ESX Serer and IBM Director Agent is represented in IBM Director Console as. Table 5 describes the status icons that are used for host objects. Table 5. Status icons for host objects Icon Description (VMware VirtualCenter) The host is powered-on and VMware ESX Serer is running. (Microsoft Virtual Serer) The host is powered-on and Microsoft Virtual Serer is started. (Microsoft Virtual Serer) Microsoft Virtual Serer is stopped on the host. A host whose status cannot be determined. This icon can occur when VMM Agent cannot communicate with either the coordinator (VMware enironment) or the host (Microsoft enironment). (Microsoft Virtual Serer only) A host that is powered-on but has an error condition. Generally this problem has two causes: VMM Agent or IBM Director Agent is not running. Microsoft Virtual Serer is not installed on the serer. Hosts that are running VMware ESX Serer When a host object represents a system that is running VMware ESX Serer, you can perform VMM operations on that host whether it is locked or unlocked. VMM communicates out-of-band with this system. You can perform the following operations for host objects that represent systems that are running VMware ESX Serer: Add a host to and remoe a host from a farm. Discoer irtual machines associated with a host Perform power operations for irtual machines associated with a host Migrate a irtual machine from one host to another For information about these operations, see Configuring hosts that are running VMware ESX Serer on page 24, Manually discoering irtual machines on page 22, and Power operations for all irtual machines on a host on page 30. 18 IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

VMM supports only those hosts that are connected to a system that is running VMware VirtualCenter serer. If a VMware host is disconnected, VMM remoes the host object for that system and generates a Farm, Host Remoed eent. VMM does not discoer hosts that are connecting to or are disconnected from a system that is running VMware VirtualCenter serer. Hosts that are running Microsoft Virtual Serer A managed system that is running Microsoft Virtual Serer is not recognized as a host object until the managed system has been unlocked. To request access to the object, right-click the managed system and click Request Access. By proiding a alid user name that has local administratie rights to that managed system and its password, you can access the system. You can perform the following operations on hosts that are running Microsoft Virtual Serer: Start a host Stop a host Virtual machine objects Discoer irtual machines associated with a host Perform power operations for irtual machines associated with a host For information about these operations, see Configuring hosts that are running Microsoft Virtual Serer on page 26, Manually discoering irtual machines on page 22, and Power operations for all irtual machines on a host on page 30. A irtual machine object is a managed object that represents a irtual machine that is associated with a system (host) that is running VMware ESX Serer or Microsoft Virtual Serer. A irtual machine object is a logical platform managed object. It is the logical equialent of a physical platform: it can be powered-on and powered-off through IBM Director Console. For information, see Chapter 5, Running power operations on irtual machines, on page 29. After VMM discoers a host, it continues the discoery process to create irtual machine objects for all the irtual machines that are associated with the host. If necessary, you can request discoery of irtual machines after a host has been discoered. For information, see Manually discoering irtual machines on page 22. You can use VMM with irtual machines that are configured with one or more irtual disks. Icons for irtual machine objects IBM Director Console displays the logical platform icon for a irtual machine object. VMM adds a second icon to the irtual machine object to depict status information about the irtual machine. VMM obtains the status information from the irtualization application. For example, a irtual machine that is powered-on is represented in IBM Director Console as. IBM Director updates the irtual machine icons wheneer you perform power operations on a irtual machine. IBM Director also updates the irtual machine icons for power operations initiated by the irtualization application. Chapter 3. VMM objects and their discoery 19

Table 6 describes the status icons that are used for irtual machine objects. Table 6. Status icons for irtual machine objects Icon Description A irtual machine that is powered-on. A irtual machine that is powered-off. A irtual machine that is undergoing a transition, for example, powering-on, suspending, resuming, powering-off, resetting, or migrating. Note: This icon is displayed when the irtual machine state change is initiated through VMM. This icon is not displayed when the irtualization application initiates a state change. A irtual machine that is powered-on but suspended. When a irtual machine is suspended, all actiity on the irtual machine is stopped until you explicitly resume operations on the irtual machine. A irtual machine that has not established communication. This icon means different things: VMware enironment The coordinator does not hae credentials to log in to the VMware VirtualCenter serer. For more information, see Credentials for coordinators on page 23. VMware VirtualCenter Web serice on the coordinator has been stopped. The coordinator has some other error condition. Microsoft enironment Microsoft Virtual Serer has been stopped. VMM Agent has been stopped Virtual machines in VMware VirtualCenter In addition to power operations, you can also migrate a irtual machine on a host that is running VMware ESX Serer to another host that is running VMware ESX serer. For information, see Migrating a irtual machine to a different host on page 26. VMM does not support or display irtual machine groups, which are collections of irtual machines supported by VMware VirtualCenter. When VMM Agent creates a irtual machine object for a irtual machine that is a member of one or more irtual machine groups, the name of the irtual machine group is ignored and not included in the name of the irtual machine object. Virtual machines in Microsoft Virtual Serer Microsoft Virtual Serer has a irtual machine status called sae state; VMM refers to this feature as suspending a irtual machine. For information about the sae state, see the documentation that comes with Microsoft Virtual Serer. 20 IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

Undoable disks An undoable disk is a type of irtual disk that saes changes to a temporary file instead of to the irtual disk itself. Changes can be committed when the irtual machine is powered-off. VMM displays irtual machine objects for irtual machines that contain undoable disks. You can iew these objects in IBM Director Console, and VMM object attributes are displayed for them. Howeer, VMM does not support power operations or migration for irtual machines that contain undoable disks. For detailed information about the undoable disk implementation for a irtualization application, see the documentation that comes with it. Guest-operating-system objects A guest-operating-system object is a managed system that represents an operating system that is running on a irtual machine and that is running IBM Director Agent. A guest-operating-system object is a particular type of managed system. The standard IBM Director discoery process for managed systems can discoer guest operating systems. Howeer, if a guest operating system is not running IBM Director Agent, it is not recognized as a guest-operating-system object in IBM Director. IBM Director Console displays a system icon for a guest-operating-system object. VMM does not display any status icons for guest-operating-system objects. Manually discoering VMM objects All the irtualization components on a system that is running VMware VirtualCenter serer or Microsoft Virtual Serer are automatically discoered when the systems are discoered. Howeer, you might want to force the discoery of irtualization components if they hae been newly created on those systems since other irtualization components were initially discoered by IBM Director, or if the objects for some irtualization components were deleted from IBM Director. Once the new irtualization components are discoered, IBM Director can create VMM objects for them. Because VMM objects, such as coordinators, hosts, and guest operating systems, are extensions of IBM Director managed systems, you can manually request discoery of these objects through the standard IBM Director discoery process for physical platforms. To do so, from IBM Director Console, click Tasks Discoer Systems Physical Platforms. For more information about discoering managed systems, see the IBM Director 4.20 Installation and Configuration Guide. Note: You cannot use the Discoer All Systems icon in the toolbar of IBM Director Console or Tasks Discoer Systems All Systems and Deices to discoer VMM objects. Howeer, because other VMM objects, such as those that represent farms and irtual machines, are not extensions of IBM Director managed systems, you cannot use this method. Use VMM menu options to manually discoer farms and irtual machines and create VMM objects for them. Chapter 3. VMM objects and their discoery 21

The remainder of this section describes the VMM menus that you can use to discoer farms and irtual machines. Manually discoering farms This procedure applies only to systems that are running VMware VirtualCenter serer. Complete the following steps to discoer all farms that are defined on a system that is running VMware VirtualCenter serer and create farm objects as necessary: 1. From IBM Director Console, in the Group Contents pane, right-click the managed object for the coordinator. 2. Click Coordinator Management Discoer Farms. Manually discoering irtual machines Complete the following steps to discoer all irtual machines that are associated with a system that is running VMware ESX Serer or Microsoft Virtual Serer and create irtual machine objects as necessary: 1. From IBM Director Console, in the Group Contents pane, right-click the managed object for the host. 2. Click Host Management Discoer Virtual Machines. 22 IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

Chapter 4. Working with credentials and configuring hosts Credentials for coordinators This chapter proides information about entering and reoking credentials for coordinators, how to use IBM Director Console to configure hosts that are associated with irtual machines, and how to delete VMM objects from IBM Director Console. This information applies only to systems that are running VMware VirtualCenter serer. Before you can perform operations on VMM objects, you must enter credentials for the coordinator object that represents the system on which VMware VirtualCenter serer is installed. For example, you must enter credentials before you can power on a irtual machine through IBM Director Console. Entering credentials logs you into the VMware management interface for that system. Logging off of the VMware management interface is referred to as reoking credentials. After you hae entered credentials, any instance of IBM Director Serer in the enironment can access that instance of VMware VirtualCenter serer. You can continue to enter credentials from any instance of IBM Director Serer in the enironment. You can reoke credentials only from those instances of IBM Director that originally entered credentials. After credentials are reoked from the last instance of IBM Director serer that preiously entered credentials, no instance of IBM Director Serer can access that instance of VMware VirtualCenter serer. Entering credentials for a coordinator Complete the following steps to enter credentials for a coordinator: 1. From IBM Director Console, in the Group Contents pane, right-click the managed object for the coordinator. 2. Click Coordinator Management Enter Credentials. The Enter Credentials window opens. Figure 8. Enter Credentials window Copyright IBM Corp. 2004 23

3. In the User ID field, type the user name for the VMware VirtualCenter serer. (This user name was designated when VMware VirtualCenter Serer was installed.) 4. In the Password field, type the password for the user name that you used. 5. If necessary, in the Port field, type the address of the port that VMM uses for communication with the VMware VirtualCenter Web serice. By default, VMM uses port 8443, which is the default port number used for VMware VirtualCenter Web serice. 6. Click OK. VMM Agent logs on to the management interface that is proided by VMware VirtualCenter. If the login is successful, VMM displays a confirmation message that the credentials were accepted. 7. Click OK to close the message window. VMM saes the entered credentials for the coordinator to IBM Director Serer. VMM Agent does not sae any credentials. Reoking credentials for a coordinator Complete the following steps to reoke credentials for a coordinator: 1. From IBM Director Console, in the Group Contents pane, right-click the managed object for the coordinator. 2. Click Coordinator Management Reoke Credentials. Note: The Reoke Credentials menu option appears only when you are using an instance of IBM Director Serer that preiously entered credentials. This menu option is not aailable when using any other instance of IBM Director Serer. VMM deletes the saed credentials for the coordinator from IBM Director Serer. Also, VMM Agent logs off from the management interface that is proided by VMware VirtualCenter. Configuring hosts in IBM Director VMM proides limited configuration of hosts to which irtual machines are associated. Configuration tasks differ according to the irtualization application that you are running on the host. Configuring hosts that are running VMware ESX Serer You can use VMM to perform the following configuration tasks on a host that is running VMware ESX Serer: Add a host to a farm Remoe a host from a farm Migrate a irtual machine from one host to a different host Adding a host to a farm Complete the following steps to add a host to a farm: 1. From IBM Director Console, in the Group Contents pane, right-click the managed object for the farm. 2. Click Farm Management Add a Host to a Farm. The Add Host window opens. 24 IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

Figure 9. Add Host window 3. In the Host field, type the IP address or name of the host that is to be added to the farm. Note: Before you type a host name, make sure that the network enironment is able to determine the IP address from the host name. Otherwise, the operation to add a host will fail. If you cannot determine the IP address of a host by using the ping command, type the IP address instead of the host name. 4. In the User ID field, type the user name for the administrator of the system. Generally, this is root. This user name is used by VMware VirtualCenter serer to communicate with the host that is running VMware ESX Serer. 5. In the Password field, type the password for the user name that you used. 6. If necessary, in the Port field, type the address of the port that VMware VirtualCenter serer will use for communication with VMware ESX Serer. By default, VMM uses port 902 for this communication. If the system that is running VMware ESX Serer is configured to use a port address other than 902, type that port address in this field. 7. Click OK. Notes: 1. VMM Agent does not enable VMware VirtualCenter VMotion for the newly added host. If you want to migrate irtual machines to or from this host, you must use VMware VirtualCenter to enable VMotion for the host. For information about VMware VirtualCenter VMotion requirements, see the documentation that comes with VMware VirtualCenter. 2. This procedure will add a system that is running VMware GSX Serer to VMware VirtualCenter, but it does not result in a host object for the system that is running VMware GSX Serer. VMM does not support systems that are running VMware GSX Serer. Remoing a host from a farm Complete the following steps to remoe a host from a farm: 1. From IBM Director Console, in the Group Contents pane, right-click the managed object for the host. 2. Click Host Management Remoe Host From Farm. 3. Click Execute Now to perform the operation immediately or click Schedule to create a new scheduled job. Chapter 4. Working with credentials and configuring hosts 25

Migrating a irtual machine to a different host Notes: 1. VMware VirtualCenter VMotion must be enabled on both the source host and destination host between which you want to migrate irtual machines. Use VMware VirtualCenter client to enable VMotion for the applicable hosts. For information about VMware VirtualCenter VMotion requirements, see the documentation that comes with VMware VirtualCenter. 2. A irtual machine must be powered-on or powered-off before you can migrate it. You cannot migrate a irtual machine that is in the suspended state. 3. VMM does not support migration of a irtual machine that contains one or more undoable disks. For more information about undoable disks, see Undoable disks on page 21. Complete the following steps to migrate a irtual machine to a different host: 1. From IBM Director Console, in the Group Contents pane, right-click the managed object for the irtual machine that you want to migrate. 2. Click Virtual Machine Management Migrate. The Migrate window opens. Figure 10. Migrate window 3. In the Host field, select the host to which you want to migrate the irtual machine. 4. Click OK. Configuring hosts that are running Microsoft Virtual Serer You can use VMM to start or stop Microsoft Virtual Serer serices. These features can be useful when you want to use Microsoft Virtual Serer to preconfigure indiidual irtual machines. VMM does not proide these configuration features. For information about Microsoft Virtual Serer serices, see the documentation. Starting Microsoft Virtual Serer serices Complete the following steps to start Microsoft Virtual Serer serices on a host: 1. From IBM Director Console, in the Group Contents pane, right-click the managed object for the host where you want to start Microsoft Virtual Serer serices. 2. Click Host Management Start Host. 26 IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

Stopping Microsoft Virtual Serer serices Complete the following steps to stop Microsoft Virtual Serer serices on a host: 1. From IBM Director Console, in the Group Contents pane, right-click the managed object for the host where you want to stop Microsoft Virtual Serer serices. 2. Click Host Management Stop Host. Deleting a VMM object from IBM Director If you no longer require a VMM object, you can delete the managed object. VMM does not delete the irtualization component from VMware VirtualCenter or Microsoft Virtual Serer. Later, if you decide that you want a managed object for a irtualization component, you can rediscoer irtualization components. For more information, see Manually discoering VMM objects on page 21. Important: Do not delete managed objects for coordinators, hosts, and guest operating systems. These managed objects represent real hardware on your network. After you uninstall VMM, these VMM objects are displayed as managed systems. Complete the following steps to delete a VMM object: 1. From IBM Director Console, in the Group Contents pane, right-click a VMM object 2. Click Delete. Chapter 4. Working with credentials and configuring hosts 27

28 IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

Chapter 5. Running power operations on irtual machines Virtual Machine Manager supports a subset of the power operations that you can perform on irtual machines by using VMware VirtualCenter or Microsoft Virtual Serer. VMM does not proide any operations that specifically target guest operating systems or that run scripts. VMM cannot create or delete irtual machines that are created by VMware VirtualCenter or Microsoft Virtual Serer. See the documentation that comes with the irtualization application for information about these types of operations. Note: You cannot perform VMM power operations on irtual machines that contain undoable disks (VMware VirtualCenter) or that use the Undo Disks feature (Microsoft Virtual Serer). For more information, see Undoable disks on page 21. You can perform power operations in seeral different ways: Use the Host Management menu to perform a power operation for all irtual machines that are associated with a selected host. Use the Power Management menu to perform a power operation for a single irtual machine. When you use either of these methods, IBM Director Console prompts you to run the operation immediately or to create a scheduled job for the operation. For information about the Scheduler, see the IBM Director 4.20 Systems Management Guide. Alternatiely, you can use the Scheduler to create scheduled jobs for these power operations. For more information, see Scheduler tasks for use with VMM objects on page 7. When you run a power operation immediately, the Execution History window is displayed and shows that the job is in progress. Note: The execution history proides details only about start and completion of the job. It does not proide details about the success or failure of the VMM operations that are performed by the job. For that information, use the IBM Director Eent Log task to iew details about all operations that hae been receied and logged by IBM Director Serer. For information about the Eent Log task, see the IBM Director 4.20 Systems Management Guide. For information about irtual machine operations that fail, see Virtual machine task failures on page 51. Because VMM performs its operations in the background, IBM Director Console remains aailable for use when you perform power operations for irtual machines. You can determine that the power operation is completed by checking the job history or by watching the icons for the irtual machines. When a irtual machine is undergoing a state transition that is initiated from IBM Director Console, the icon is displayed for the irtual machine. After the state transition is completed, the applicable state icon is displayed for the irtual machine; for example, the icon is displayed for the irtual machine when the irtual machine is powered-on. For more information about the icons that are used for a irtual machine object in IBM Director Console, see Icons for irtual machine objects on page 19. Copyright IBM Corp. 2004 29

Power operations for all irtual machines on a host Use the Host Management menu to perform power operations for all irtual machines that are associated with a single host. The Host Management menu is aailable when you right-click a host object in the Group Contents pane of IBM Director Console. You can use the Host Management menu to perform the following power operations: Power-on all stopped irtual machines Suspend all running irtual machines Resume all suspended irtual machines Power-off all running irtual machines Important: The power operations on the Host Management menu apply to all irtual machines that are associated with a system that is running VMware ESX Serer or Microsoft Virtual Serer, een those irtual machines that are not represented in IBM Director Console. The selected power operation applies only to the irtual machines in the specified state. For example, a power-on operation applies only to irtual machines that are powered-off. It does not affect irtual machines that are already powered-on or suspended. This aspect is important to consider when you create IBM Director scheduled jobs for host management power operations that inole irtual machines. Further, these power operations do not affect irtual machines that contain undoable disks (VMware VirtualCenter) or that use the Undo Disks feature (Microsoft Virtual Serer). Powering-on all stopped irtual machines Complete the following steps to power-on all stopped irtual machines that are associated with a single host: 1. From IBM Director Console, in the Group Contents pane, right-click the host. 2. Click Host Management Power On All Stopped Virtual Machines. 3. Click Execute Now to perform the operation immediately or click Schedule to create a new scheduled job. Suspending all running irtual machines Complete the following steps to suspend all running irtual machines that are associated with a single host: 1. From IBM Director Console, in the Group Contents pane, right-click the host. 2. Click Host Management Suspend All Running Virtual Machines. 3. Click Execute Now to perform the operation immediately or click Schedule to create a new scheduled job. 30 IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

Resuming all suspended irtual machines Complete the following steps to resume all suspended irtual machines that are associated with a single host: 1. From IBM Director Console, in the Group Contents pane, right-click the host. 2. Click Host Management Resume All Suspended Virtual Machines. 3. Click Execute Now to perform the operation immediately or click Schedule to create a new scheduled job. Powering-off all running irtual machines Complete the following steps to power-off all running irtual machines that are associated with a single host: Important: This operation forces a irtual machine to power-off without an orderly shut down of its guest operating system. This immediately stops all applications that are in use on that guest operating system. 1. From IBM Director Console, in the Group Contents pane, right-click the host. 2. Click Host Management Force Power Off All Running Virtual Machines. 3. Click Execute Now to perform the operation immediately or click Schedule to create a new scheduled job. Power operations for a single irtual machine Use the Power Management menu to perform a power operation on a single irtual machine. The Power Management menu is aailable when you right-click a irtual machine object in the Group Contents pane of IBM Director Console. For more information about the Power Management task, see the IBM Director 4.20 Systems Management Guide. You can use the Power Management menu to perform the power operations that are listed in Table 7. Table 7. Power Management menu options for irtual machines Menu option Power Off Now Power On Restart Now Resume Shutdown and Power Off Description The irtual machine is powered-off without an orderly shut down of its guest operating system. This immediately stops all applications that are in use on that guest operating system. The irtual machine is powered-on. The irtual machine is restarted immediately, which means that it is restarted without an orderly shut down of its guest operating system. This immediately stops all applications that are in use on that guest operating system. The irtual machine resumes operation and is no longer suspended. (VMware VirtualCenter only) The guest operating system on the irtual machine is shut down in an orderly way, and then the irtual machine is powered-off. (Microsoft Virtual Serer only) If the guest operating system is a Windows operating system and if Microsoft Virtual Machine Additions is installed on the guest operating system, this menu option performs an orderly shut down of the guest operating system and then powers-off the irtual machine. Suspend The irtual machine remains powered-on but is suspended from use. Chapter 5. Running power operations on irtual machines 31

Only those operations that are applicable to the selected irtual machine are aailable on the Power Management menu. For example, if a irtual machine is suspended, the Power Management menu contains only the Resume menu option. Further, none of the aailable power operations can be used with irtual machines that contain undoable disks (VMware VirtualCenter) or that use the Undo Disks feature (Microsoft Virtual Serer). Complete the following steps to perform a power-management operation for a irtual machine: 1. From IBM Director Console, in the Group Contents pane, right-click the irtual machine. 2. Click Power Management; then, click the power operation that you want to perform. For example, click Power Management Power On. 3. Click Execute Now to perform the operation immediately or click Schedule to create a new scheduled job. 32 IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

Chapter 6. Viewing VMM object attributes Virtual Machine Manager creates attributes for the following VMM objects: Coordinators Farms Hosts Virtual machines VMM does not create attributes for guest-operating-system objects. Displaying coordinator object attributes Complete the following steps to display VMM object attributes for a coordinator: 1. From IBM Director Console, in the Group Contents pane, right-click the managed object for the coordinator. 2. Click Coordinator Management VMM Object Attributes. The VMM Object Attributes window opens. Figure 11. VMM object attributes for a coordinator Table 8 describes the VMM object attributes for a coordinator. Table 8. VMM object attributes for a coordinator Attribute name Library Vendor Library Version Vendor URL TCP/IP Addresses TCP/IP Hosts Description The name of the irtualization endor that proides the API for the VMM object. For this release, the alue is always VMware. The ersion of the endor library that VMM is using. The Web address of the management interface for the coordinator as proided by the irtualization application. VMware VirtualCenter does not hae a Web address of the management interface so this field has the alue Information Not Aailable. The IP address of the serer. The name of the serer. Copyright IBM Corp. 2004 33

Displaying farm object attributes Complete the following steps to display VMM object attributes for a farm: 1. From IBM Director Console, in the Group Contents pane, right-click the managed object for the farm. 2. Click Farm Management VMM Object Attributes. The VMM Object Attributes window opens. Figure 12. VMM object attributes for a farm Table 9 describes the VMM object attributes for a farm. Table 9. VMM object attributes for a farm Attribute name Host Count Virtual Machine Count ID Description The number of hosts that are in the farm. The number of irtual machines that are associated with the hosts in the farm. The name of the farm as it is known by the irtualization application. This name can be the same as, or different from, the name that is shown for the farm object in IBM Director Console. Displaying host object attributes Complete the following steps to display VMM object attributes for a host: 1. From IBM Director Console, in the Group Contents pane, right-click the managed object for the host. 2. Click Host Management VMM Object Attributes. The VMM Object Attributes window opens. This window displays different attributes depending on whether the host object represents a serer that is running VMware ESX Serer or Microsoft Virtual Serer. 34 IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

Hosts in VMware VirtualCenter Figure 13 shows the VMM Object Attributes window when the host object represents a serer that is running VMware ESX Serer in a VMware VirtualCenter enironment. Figure 13. VMM object attributes for a host in a VMware VirtualCenter enironment Table 10 describes the VMM object attributes for a host object that represents a serer that is running VMware ESX Serer in a VMware VirtualCenter enironment. Table 10. VMM object attributes for a host in a VMware VirtualCenter enironment Attribute name System UUID TCP/IP Hosts Type of Hyperisor Virtual Machine Count Physical CPU Description The UUID of the serer. This attribute is the same as the IBM Director system attribute of the same name. The name of the serer. The type of hyperisor that is used by the serer. For serers that are running VMware ESX Serer, the type is always 1, which specifies that the hyperisor runs directly on the serer. The number of irtual machines that are associated with the host. The number of microprocessors (CPUs) that are in the serer. Chapter 6. Viewing VMM object attributes 35

Hosts in Microsoft Virtual Serer Figure 14 shows the VMM Object Attributes window when the host object represents a serer that is running Microsoft Virtual Serer. Figure 14. VMM object attributes for a host in a Microsoft Virtual Serer enironment Table 11 describes the VMM object attributes for a host object that represents a serer that is running Microsoft Virtual Serer. Table 11. VMM object attributes for a host in a Microsoft Virtual Serer enironment Attribute name Library Vendor Library Version System UUID TCP/IP Hosts Vendor URL Type of Hyperisor Description The name of the irtualization endor that proides the API for the VMM object. For this release, the alue is always Virtual Serer. The ersion of the endor library that VMM is using. The UUID of the serer. This attribute is the same as the IBM Director system attribute of the same name. The name of the serer. The Web address of the management interface for the host as proided by the irtualization application. The type of hyperisor that is used by the host object. For hosts in Microsoft Virtual Serer, the type is always 2, which means that the hyperisor runs under control of the operating system. Displaying irtual machine object attributes Complete the following steps to display VMM object attributes for a irtual machine: 1. From IBM Director Console, in the Group Contents pane, right-click the managed object for the irtual machine. 2. Click Virtual Machine Management VMM Object Attributes. The VMM Object Attributes window opens. This window displays different attributes depending on whether the irtual machine object represents a irtual machine in a VMware VirtualCenter enironment or a Microsoft Virtual Serer enironment. 36 IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

Virtual machines in VMware VirtualCenter Figure 15 shows the VMM Object Attributes window when the irtual machine object represents a irtual machine that is associated with a host in a VMware VirtualCenter enironment. Figure 15. VMM object attributes for a irtual machine in a VMware VirtualCenter enironment Table 12 describes the VMM object attributes for a irtual machine that is associated with a host in a VMware VirtualCenter enironment. Table 12. VMM object attributes for a irtual machine in a VMware VirtualCenter enironment Attribute name Virtual CPU Vendor Display Name System UUID Disk undoable behaior Description The number of CPUs that are assigned to the irtual machine. The name of the irtual machine as it is known by the irtualization application. This name can be the same as, or different from, the name that is shown for the irtual machine object in IBM Director Console. The UUID of the irtual machine. This attribute is the same as the IBM Director system attribute of the same name. The existence of undoable disks on the irtual machine. VMM indicates either that no undoable disks were found or that one or more undoable disks were found. For more information, see Undoable disks on page 21 Chapter 6. Viewing VMM object attributes 37

Virtual machines in Microsoft Virtual Serer Figure 16 shows the VMM Object Attributes window when the irtual machine object represents a irtual machine that is associated with a host in a Microsoft Virtual Serer enironment. Figure 16. VMM object attributes for a irtual machine in a Microsoft Virtual Serer enironment Table 13 describes the VMM object attributes for a irtual machine that is associated with a host in a Microsoft Virtual Serer enironment. Table 13. VMM object attributes for a irtual machine in a Microsoft Virtual Serer enironment Attribute name Virtual CPU Vendor Display Name System UUID ID Disk undoable behaior Description The number of CPUs that are assigned to the irtual machine. The name of the irtual machine as it is known by the irtualization application. This name can be the same as, or different from, the name that is shown for the irtual machine object in IBM Director Console. The UUID of the irtual machine. This attribute is the same as the IBM Director system attribute of the same name. The unique ID that identifies the irtual machine to Microsoft Virtual Serer. This ID is assigned by Microsoft Virtual Serer. You can use this ID to identify the irtual machine when you create scripts that use the Microsoft Virtual Serer COM interface. The existence of undoable disks on the irtual machine. VMM indicates either that no undoable disks were found or that one or more undoable disks were found. For more information, see Undoable disks on page 21. 38 IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

Chapter 7. Soling Virtual Machine Manager problems This chapter describes some of the problem symptoms and suggested solutions for Virtual Machine Manager. Multiple sections are used to list the problem symptoms depending on whether the symptom occurs with any supported irtualization enironment, occurs only in a VMware VirtualCenter enironment, or occurs only in a Microsoft Virtual Serer enironment. Any supported irtualization enironment Table 14 describes some of the problem symptoms and suggested solutions for VMM when used in any supported irtualization enironment. Table 14. VMM problems in any supported irtualization enironment Symptom Eent action plans An eent action in an eent action plan does not occur when an eent occurs. Suggested action Make sure that the eent action plan is targeting the correct managed object; for example, if an eent is for a irtual machine, the eent action plan must be applied to a irtual machine and not any other VMM objects. VMware VirtualCenter enironment Table 15 describes some of the problem symptoms and suggested solutions for VMM when used in a VMware VirtualCenter enironment. Table 15. VMM problems in a VMware VirtualCenter enironment Symptom Suggested action Communication with VMware VirtualCenter An application exception error, an insufficient permission error, or a connection error occurs when you use the Start Vendor Software task to run the VMware VirtualCenter client from IBM Director. A login failure occurs when you try to enter credentials for a coordinator. Make sure that VMware VirtualCenter serer is installed by a user that has administrator priileges on the installing system. If it was installed by a user that does not hae administrator priileges, you either must assign administrator priileges to that user or reinstall VMware VirtualCenter serer with a user that does hae administrator priileges. Make sure that the user that is running VMware VirtualCenter serer has administrator priileges in VMware VirtualCenter. If it does not, log in to the VMware VirtualCenter client as a user with administrator priileges. Then, add administrator priileges to the user that does not hae administrator priileges. Copyright IBM Corp. 2004 39

Symptom Unlocking coordinator objects A coordinator object is locked, but Enter Credentials is not aailable in the right-click menu for the coordinator. Suggested action This problem occurs when VMware VirtualCenter serer has granted permission to IBM Director to perform operations on VMM objects, but later, someone changes the user ID and password of the VMware VirtualCenter serer so access to the coordinator is no longer aailable. Renaming farm groups Unexpected behaior occurs for a farm object in any instance of IBM Director Serer that is tracking actiity on that farm object. Virtual machine power operations (Windows NT 4.0 only) Virtual machines do not shut down and power-off as expected; instead, they power off without an orderly shut down of their operating system or they remain in a transition state. Complete the following steps to resole this problem: 1. From IBM Director Console, in the Group Contents pane, right-click the managed object for the coordinator; then, click Coordinator Management Reoke Credentials. 2. From IBM Director Console, in the Group Contents pane, right-click the managed object for the coordinator; then, click Coordinator Management Enter Credentials. 3. Type the new credentials for the coordinator in the Enter Credentials window. For information, see Entering credentials for a coordinator on page 23. 4. Click OK. This symptom can occur when a farm that is contained within a farm group is discoered in IBM Director and later that farm group is renamed in VMware VirtualCenter. After a farm group is renamed, you should reoke and enter credentials for the coordinator object that contains the farm object. For information, see Credentials for coordinators on page 23. Install VMware Tools in the irtual machine so that shut down and power-off operations do not immediately power off irtual machine without an orderly shut down. For information about installing VMware Tools, see the VMware VirtualCenter documentation. Howeer, een when VMware Tools are installed, shut down and power-off operations are not completed as expected from VMM. The guest operating system is shut down in an orderly way, but the irtual machine is not powered off. You must perform an additional operation to power off the irtual machine. Complete the following steps to perform a shut down and power-off of a irtual machine running Windows NT 4.0: 1. Perform a shut down and power off operation for the irtual machine. For information, see Power operations for a single irtual machine on page 31. This action shuts down the operating system in an orderly way, but does not power off the irtual machine. 2. Perform a second operation to power off the irtual machine. This second operation can be either another shut down and power off operation or a power off now operation. Note: Before performing a power off now operation, make sure that the operating system has completely shut down on the irtual machine. One way to check this from IBM Director is to use the Remote Session task on the irtual machine. 40 IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

Symptom Virtual machine migration Failure codes 66 and 67 are returned een though migration is enabled on the system that is running VMware ESX Serer. Failure code 84 is returned een though the irtual machine does not contain any undoable disks. Migration menu options are aailable for irtual machine objects een though VMotion is not enabled in VMware VirtualCenter. Suggested action These failure codes can be returned and the migration menu options can be aailable when VMM does not hae the most up-to-date information about migration or undoable disk properties from the irtualization application. This situation occurs more frequently when multiple users are making changes to the properties. For example, migration failure codes can be returned when migration properties hae been modified in VMware VirtualCenter while IBM Director Serer is running. Use one of the following methods to refresh these properties in VMM Serer: From the Group Contents pane of IBM Director Console, right-click the host object for the irtual machine and click Host Management Discoer Virtual Machines. From the Group Contents pane of IBM Director console, right-click the irtual machine object and click Virtual Machine Management VMM Object Attributes. Microsoft Virtual Serer enironment Table 16 describes some of the problem symptoms and suggested solutions for VMM when used in a Microsoft Virtual Serer enironment. Table 16. VMM problems in a Microsoft Virtual Serer enironment Symptom Creation of irtual machine objects A irtual machine is created in a Microsoft Virtual Serer enironment, but a corresponding irtual machine object is not created in IBM Director. Suggested action Use Microsoft Virtual Serer to power-on the newly-created irtual machine. Then, IBM Director and VMM will create a corresponding irtual machine object. Chapter 7. Soling Virtual Machine Manager problems 41

42 IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

Appendix A. Virtual Machine Manager eent filters and actions Eents proided by VMM Virtual Machine Manager proides seeral eents and eent actions for use with VMM objects. For more general information about eent filters, eent actions, and the Eent Filter Builder, see the IBM Director help, the IBM Director 4.20 Systems Management Guide, and the IBM Director 4.1 Eents Reference. The eents that are proided by VMM are for VMM objects. These eents are in the VMM eent type in the Eent Filter Builder. Note: Make sure that any eent action plans that use these eents are actually targeted to the applicable VMM object; otherwise, the intended actions will not occur. Use the IBM Director Eent Log task to iew details about all VMM eent types that hae been receied and logged by IBM Director Serer. Simple eent filters can be created with or without specifying extended attributes for the eent filter. The target object for an eent filter is different depending on which method was used to create the eent filter. If an eent filter is created without specifying any extended attributes, the eent action plan that contains this eent filter should be applied directly to the VMM object identified as the target object in the tables that follow. If an eent filter is created and it specifies alues for extended attributes, the eent action plan that contains this eent filter can be applied directly to the VMM object identified as the target object or to any higher-leel VMM objects that are associated with the target object. For example, if you create an eent filter with extended attributes that identifies a specific irtual machine, you can apply the eent action plan that contains this eent filter directly to the irtual machine itself or to its associated host, farm, or coordinator. In this scenario, all VMM objects that are associated with the target object listed in the following tables will receie the eent notification, which means that the IBM Director Eent Log will contain one eent for each associated VMM object, each with the same detail. To continue the example, there would be four log entries, one each for the coordinator, farm, host, and irtual machine. Copyright IBM Corp. 2004 43

Virtual machine eents The irtual machine eents are in the Virtual Machine subcategory of the VMM eent type category. Figure 17 shows the eents for a irtual machine in the Simple Eent Filter Builder window. Table 17. Virtual machine eents Eent subcategory Created Deleted Additional eent subcategory Table 17 defines the irtual machine eents that are proided by VMM. Target object for eent action plan Eent trigger Description Virtual machine Virtual machine Migration Started Virtual machine Figure 17. Virtual machine eents in the Simple Eent Filter Builder window A irtual machine object is created. A irtual machine object is deleted. A irtual machine has started migration from one host to another. IBM Director Console displays a irtual machine object for a irtual machine. IBM Director Console no longer displays a irtual machine object for a irtual machine. VMM has started the migration of a irtual machine from one host to another. 44 IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide

Table 17. Virtual machine eents (continued) Eent subcategory Additional eent subcategory Completed Target object for eent action plan Eent trigger Description Virtual machine Resource CPU Virtual machine A irtual machine has completed migration from one host to another. The alues for the CPU resource for a irtual machine hae changed. VMM has completed the migration of a irtual machine from one host to another. (VMware VirtualCenter) One of the following eents occur: The CPU count changes. The CPU shares priority changes. The CPU scheduling affinity changes. (Microsoft Virtual Serer) One of the following eents occur: The resered (minimum) or maximum capacity of CPU utilization changes. The relatie weight of the CPU changes. Memory Virtual machine The alues for the memory resource for a irtual machine hae changed. (VMware VirtualCenter) One of the following eents occur: The memory size changes. The minimum or maximum amount of memory changes. The memory shares priority changes. State Powered off Virtual machine Powered on Reset Resumed Virtual machine Virtual machine Virtual machine The state of a irtual machine has changed to powered-off. The state of a irtual machine has changed to powered-on. The state of a irtual machine has changed to restarted. The state of a irtual machine has changed from suspended to powered-on. (Microsoft Virtual Serer) One of the following eents occur: The memory size changes. A irtual machine is powered-off. A irtual machine is powered-on. A irtual machine is restarted. A irtual machine resumes operations after being in the suspended state. Appendix A. Virtual Machine Manager eent filters and actions 45

Table 17. Virtual machine eents (continued) Eent subcategory Task Failed Additional eent subcategory Suspended Target object for eent action plan Eent trigger Description Virtual machine Virtual machine The state of a irtual machine has changed to suspended. An operation on a irtual machine has failed to be completed successfully. A irtual machine is suspended. A power or migration operation failed for a irtual machine. For more information, see Virtual machine task failures on page 51. Coordinator, farm, and host eents VMM also proides eents for coordinators, farms and hosts. These eents are in the VMM eent type category. Figure 18 shows the coordinator, farm, and host eents for VMM objects in the Simple Eent Filter Builder window. Figure 18. Coordinator, farm, and host eents in the Simple Eent Filter Builder window Table 18 on page 47 defines the coordinator, farm, and host eents that are proided by VMM. 46 IBM Director 4.20: Virtual Machine Manager 1.0 Installation and User s Guide