Red Hat Training
A Red Hat training course is available for Red Hat Virtualization
Introduction to the Administration Portal
Accessing and Using the Administration Portal
Abstract
Chapter 1. Using the Administration Portal
1.1. What is the Administration Portal?
The Administration Portal is the graphical administration interface of the Red Hat Virtualization Manager server. Administrators can monitor, create, and maintain all elements of the virtualized environment from web browsers. Tasks that can be performed from the Administration Portal include:
- Creation and management of virtual infrastructure (networks, storage domains)
- Installation and management of hosts
- Creation and management of logical entities (data centers, clusters)
- Creation and management of virtual machines
- Red Hat Virtualization user and permission management
1.2. Browser Requirements
The following browser versions and operating systems can be used to access the Administration Portal and the VM Portal.
Browser support is divided into tiers:
- Tier 1: Browser and operating system combinations that are fully tested and fully supported. Red Hat Engineering is committed to fixing issues with browsers on this tier.
- Tier 2: Browser and operating system combinations that are partially tested, and are likely to work. Limited support is provided for this tier. Red Hat Engineering will attempt to fix issues with browsers on this tier.
- Tier 3: Browser and operating system combinations that are not tested, but may work. Minimal support is provided for this tier. Red Hat Engineering will attempt to fix only minor issues with browsers on this tier.
Table 1.1. Browser Requirements
Support Tier | Operating System Family | Browser |
---|---|---|
Tier 1 | Red Hat Enterprise Linux | Mozilla Firefox Extended Support Release (ESR) version |
Tier 2 | Windows | Internet Explorer 11 or later |
Any | Most recent version of Google Chrome or Mozilla Firefox | |
Tier 3 | Any | Earlier versions of Google Chrome or Mozilla Firefox |
Any | Other browsers |
1.3. Client Requirements
Virtual machine consoles can only be accessed using supported Remote Viewer (virt-viewer
) clients on Red Hat Enterprise Linux and Windows. To install virt-viewer
, see Installing Supporting Components on Client Machines in the Virtual Machine Management Guide. Installing virt-viewer
requires Administrator privileges.
Virtual machine consoles are accessed through the SPICE protocol. The QXL graphical driver can be installed in the guest operating system for improved/enhanced SPICE functionalities. SPICE currently supports a maximum resolution of 2560x1600 pixels.
Supported QXL drivers are available on Red Hat Enterprise Linux, Windows XP, and Windows 7.
SPICE support is divided into tiers:
- Tier 1: Operating systems on which Remote Viewer has been fully tested and is supported.
- Tier 2: Operating systems on which Remote Viewer is partially tested and is likely to work. Limited support is provided for this tier. Red Hat Engineering will attempt to fix issues with remote-viewer on this tier.
Table 1.2. Client Operating System SPICE Support
Support Tier | Operating System |
---|---|
Tier 1 | Red Hat Enterprise Linux 7.2 and later |
Microsoft Windows 7 | |
Tier 2 | Microsoft Windows 8 |
Microsoft Windows 10 |
1.4. Graphical User Interface Elements
The Red Hat Virtualization Administration Portal consists of contextual panes and menus.
Figure 1.1. Key Graphical User Interface Elements

Key Graphical User Interface Elements
-
Header Bar
The header bar contains the Bookmarks, Tags, Tasks, Events and alerts notifications icons, the Help drop-down button, and the User drop-down button.
You can click the Help button to select Guide, a shortcut to the Red Hat Virtualization Administration Guide, or About, to view information on the version of Red Hat Virtualization. You can click the User button to select Options or Sign out.
-
Main Navigation Menu
The main navigation menu allows you to view the resources of the Red Hat Virtualization environment.
-
Search Bar
The search bar allows you to build queries for finding resources such as hosts and clusters in the Red Hat Virtualization environment. Queries can be as simple as a list of all the hosts in the system, or more complex, such as a list of resources that match certain conditions. As you type each part of the search query, you are offered choices to assist you in building the search. The star icon can be used to save the search as a bookmark.
-
Refresh Button
The Refresh button refreshes the Administration Portal. The drop-down list beside the Refresh button allows you to set the time, in seconds, between Administration Portal refreshes. To avoid a delay between performing an action and its result appearing in the portal, the portal automatically refreshes whenever you perform an action or event, regardless of the refresh interval.
-
Results List
You can perform a task on an individual item, multiple items, or all the items in the results list by selecting the items and clicking the relevant action button.
You can display or hide table columns in the results list. To do this, right-click any table heading to display the column control menu, and select or deselect the appropriate heading title. The column control menu can also be used to rearrange the order of columns by dragging and dropping the column to the required position within the menu.
Click the name of a resource to go to its details view.
-
More Actions Button
You can use the More Actions button to perform additional tasks.
1.5. Using the Guide Me Facility
When setting up resources such as data centers and clusters, a number of tasks must be completed in sequence. The context-sensitive Guide Me window prompts for actions that are appropriate to the resource being configured. The Guide Me window can be accessed at any time by clicking More Actions → Guide Me.
Figure 1.2. Data Center Guide Me Window

Chapter 2. Searches
2.1. Performing Searches in Red Hat Virtualization
The Administration Portal allows you to manage thousands of resources, such as virtual machines, hosts, users, and more. To perform a search, enter the search query (free-text or syntax-based) into the search bar, available on the main page for each resource. Search queries can be saved as bookmarks for future reuse, so you do not have to reenter a search query each time the specific search results are required. Searches are not case sensitive.
2.2. Search Syntax and Examples
The syntax of the search queries for Red Hat Virtualization resources is as follows:
result type: {criteria} [sortby sort_spec]
Syntax Examples
The following examples describe how the search query is used and help you to understand how Red Hat Virtualization assists with building search queries.
Table 2.1. Example Search Queries
Example | Result |
---|---|
Hosts: Vms.status = up page 2 | Displays page 2 of a list of all hosts running virtual machines that are up. |
Vms: domain = qa.company.com | Displays a list of all virtual machines running on the specified domain. |
Vms: users.name = Mary | Displays a list of all virtual machines belonging to users with the user name Mary. |
Events: severity > normal sortby time | Displays the list of all Events whose severity is higher than Normal, sorted by time. |
2.3. Search Auto-Completion
The Administration Portal provides auto-completion to help you create valid and powerful search queries. As you type each part of a search query, a drop-down list of choices for the next part of the search opens below the Search Bar. You can either select from the list and then continue typing/selecting the next part of the search, or ignore the options and continue entering your query manually.
The following table specifies by example how the Administration Portal auto-completion assists in constructing a query:
Hosts: Vms.status = down
Table 2.2. Example Search Queries Using Auto-Completion
Input | List Items Displayed | Action |
---|---|---|
h |
|
Select |
Hosts: | All host properties | Type v |
Hosts: v |
host properties starting with a |
Select |
Hosts: Vms | All virtual machine properties | Type s |
Hosts: Vms.s |
All virtual machine properties beginning with |
Select |
Hosts: Vms.status |
| Select or type = |
Hosts: Vms.status = | All status values | Select or type down |
2.4. Search Result Type Options
The result type allows you to search for resources of any of the following types:
- Vms for a list of virtual machines
- Host for a list of hosts
- Pools for a list of pools
- Template for a list of templates
- Events for a list of events
- Users for a list of users
- Cluster for a list of clusters
- DataCenter for a list of data centers
- Storage for a list of storage domains
As each type of resource has a unique set of properties and a set of other resource types that it is associated with, each search type has a set of valid syntax combinations. You can also use the auto-complete feature to create valid queries easily.
2.5. Search Criteria
You can specify the search criteria after the colon in the query. The syntax of {criteria}
is as follows:
<prop><operator><value>
or
<obj-type><prop><operator><value>
Examples
The following table describes the parts of the syntax:
Table 2.3. Example Search Criteria
Part | Description | Values | Example | Note |
---|---|---|---|---|
prop |
The property of the searched-for resource. Can also be the property of a resource type (see | Limit your search to objects with a certain property. For example, search for objects with a status property. | Status | N/A |
obj-type | A resource type that can be associated with the searched-for resource. | These are system objects, like data centers and virtual machines. | Users | N/A |
operator | Comparison operators. | = != (not equal) > < >= <= | N/A | Value options depend on property. |
Value | What the expression is being compared to. | String Integer Ranking Date (formatted according to Regional Settings) | Jones 256 normal |
|
2.6. Search: Multiple Criteria and Wildcards
Wildcards can be used in the <value>
part of the syntax for strings. For example, to find all users beginning with m, enter m*
.
You can perform a search having two criteria by using the Boolean operators AND
and OR
. For example:
Vms: users.name = m* AND status = Up
This query returns all running virtual machines for users whose names begin with "m".
Vms: users.name = m* AND tag = "paris-loc"
This query returns all virtual machines tagged with "paris-loc" for users whose names begin with "m".
When two criteria are specified without AND
or OR
, AND
is implied. AND
precedes OR
, and OR
precedes implied AND
.
2.7. Search: Determining Search Order
You can determine the sort order of the returned information by using sortby
. Sort direction (asc
for ascending, desc
for descending) can be included.
For example:
events: severity > normal sortby time desc
This query returns all Events whose severity is higher than Normal, sorted by time (descending order).
2.8. Searching for Data Centers
The following table describes all search options for Data Centers.
Table 2.4. Searching for Data Centers
Property (of resource or resource-type) | Type | Description (Reference) |
---|---|---|
| Depends on property type | The property of the clusters associated with the data center. |
| String | The name of the data center. |
| String | A description of the data center. |
| String | The type of data center. |
| List | The availability of the data center. |
| List | Sorts the returned results by one of the resource properties. |
| Integer | The page number of results to display. |
Example
Datacenter: type = nfs and status != up
This example returns a list of data centers with a storage type of NFS and status other than up.
2.9. Searching for Clusters
The following table describes all search options for clusters.
Table 2.5. Searching Clusters
Property (of resource or resource-type) | Type | Description (Reference) |
---|---|---|
| Depends on property type | The property of the data center associated with the cluster. |
| String | The data center to which the cluster belongs. |
| String | The unique name that identifies the clusters on the network. |
| String | The description of the cluster. |
| String | True or False indicating the status of the cluster. |
| List | Sorts the returned results by one of the resource properties. |
| Integer | The page number of results to display. |
Example
Clusters: initialized = true or name = Default
This example returns a list of clusters which are initialized or named Default.
2.10. Searching for Hosts
The following table describes all search options for hosts.
Table 2.6. Searching for Hosts
Property (of resource or resource-type) | Type | Description (Reference) |
---|---|---|
| Depends on property type | The property of the virtual machines associated with the host. |
| Depends on property type | The property of the templates associated with the host. |
| Depends on property type | The property of the events associated with the host. |
| Depends on property type | The property of the users associated with the host. |
| String | The name of the host. |
| List | The availability of the host. |
| String | The health status of the host as reported by external systems and plug-ins. |
| String | The cluster to which the host belongs. |
| String | The unique name that identifies the host on the network. |
| Integer | The percent of processing power used. |
| Integer | The percentage of memory used. |
| Integer | The percentage of network usage. |
| Integer | Jobs waiting to be executed in the run-queue per processor, in a given time slice. |
| Integer | The version number of the operating system. |
| Integer | The number of CPUs on the host. |
| Integer | The amount of memory available. |
| Integer | The processing speed of the CPU. |
| String | The type of CPU. |
| Integer | The number of virtual machines currently running. |
| Integer | The number of virtual machines currently being migrated. |
| Integer | The percentage of committed memory. |
| String | The tag assigned to the host. |
| String | The type of host. |
| String | The data center to which the host belongs. |
| List | Sorts the returned results by one of the resource properties. |
| Integer | The page number of results to display. |
Example
Hosts: cluster = Default and Vms.os = rhel6
This example returns a list of hosts which are part of the Default cluster and host virtual machines running the Red Hat Enterprise Linux 6 operating system.
2.11. Searching for Networks
The following table describes all search options for networks.
Table 2.7. Searching for Networks
Property (of resource or resource-type) | Type | Description (Reference) |
---|---|---|
| Depends on property type | The property of the cluster associated with the network. |
| Depends on property type | The property of the host associated with the network. |
| String | The human readable name that identifies the network. |
| String | Keywords or text describing the network, optionally used when creating the network. |
| Integer | The VLAN ID of the network. |
| String | Whether Spanning Tree Protocol (STP) is enabled or disabled for the network. |
| Integer | The maximum transmission unit for the logical network. |
| String | Whether the network is only used for virtual machine traffic. |
| String | The data center to which the network is attached. |
| List | Sorts the returned results by one of the resource properties. |
| Integer | The page number of results to display. |
Example
Network: mtu > 1500 and vmnetwork = true
This example returns a list of networks with a maximum transmission unit greater than 1500 bytes, and which are set up for use by only virtual machines.
2.12. Searching for Storage
The following table describes all search options for storage.
Table 2.8. Searching for Storage
Property (of resource or resource-type) | Type | Description (Reference) |
---|---|---|
| Depends on property type | The property of the hosts associated with the storage. |
| Depends on property type | The property of the clusters associated with the storage. |
| String | The unique name that identifies the storage on the network. |
| String | The status of the storage domain. |
| String | The health status of the storage domain as reported by external systems and plug-ins. |
| String | The data center to which the storage belongs. |
| String | The type of the storage. |
| Integer | The size of the storage. |
| Integer | The amount of the storage that is used. |
| Integer | The amount of the storage that is committed. |
| List | Sorts the returned results by one of the resource properties. |
| Integer | The page number of results to display. |
Example
Storage: size > 200 or used < 50
This example returns a list of storage with total storage space greater than 200 GB, or used storage space less than 50 GB.
2.13. Searching for Disks
The following table describes all search options for disks.
You can use the Disk Type
and Content Type
filtering options to reduce the number of displayed virtual disks.
Table 2.9. Searching for Disks
Property (of resource or resource-type) | Type | Description (Reference) |
---|---|---|
| Depends on property type | The property of the data centers associated with the disk. |
| Depends on property type | The property of the storage associated with the disk. |
| String | The human readable name that identifies the storage on the network. |
| String | Keywords or text describing the disk, optionally used when creating the disk. |
| Integer | The virtual size of the disk. |
| Integer | The size of the disk. |
| Integer | The actual size allocated to the disk. |
| Integer | The date the disk was created. |
| String |
Whether the disk can or cannot be booted. Valid values are one of |
| String |
Whether the disk can or cannot be attached to more than one virtual machine at a time. Valid values are one of |
| String |
The format of the disk. Can be one of |
| String |
The status of the disk. Can be one of |
| String |
The type of the disk. Can be one of |
| Integer | The number of virtual machine(s) to which the disk is attached. |
| String | The name(s) of the virtual machine(s) to which the disk is attached. |
| String | The name of the quota enforced on the virtual disk. |
| List | Sorts the returned results by one of the resource properties. |
| Integer | The page number of results to display. |
Example
Disks: format = cow and provisioned_size > 8
This example returns a list of virtual disks with QCOW format and an allocated disk size greater than 8 GB.
2.14. Searching for Volumes
The following table describes all search options for volumes.
Table 2.10. Searching for Volumes
Property (of resource or resource-type) | Type | Description (Reference) |
---|---|---|
| String | The name of the cluster associated with the volume. |
| Depends on property type (examples: name, description, comment, architecture) | The property of the clusters associated with the volume. |
| String | The human readable name that identifies the volume. |
| String | Can be one of distribute, replicate, distributed_replicate, stripe, or distributed_stripe. |
| Integer | Can be one of TCP or RDMA. |
| Integer | Number of replica. |
| Integer | Number of stripes. |
| String | The status of the volume. Can be one of Up or Down. |
| List | Sorts the returned results by one of the resource properties. |
| Integer | The page number of results to display. |
Example
Volume: transport_type = rdma and stripe_count >= 2
This example returns a list of volumes with transport type set to RDMA, and with 2 or more stripes.
2.15. Searching for Virtual Machines
The following table describes all search options for virtual machines.
Currently, the Network Label, Custom Emulated Machine, and Custom CPU Type properties are not supported search parameters.
Table 2.11. Searching for Virtual Machines
Property (of resource or resource-type) | Type | Description (Reference) |
---|---|---|
| Depends on property type | The property of the hosts associated with the virtual machine. |
| Depends on property type | The property of the templates associated with the virtual machine. |
| Depends on property type | The property of the events associated with the virtual machine. |
| Depends on property type | The property of the users associated with the virtual machine. |
| Depends on the property type | The property of storage devices associated with the virtual machine. |
| Depends on the property type | The property of the VNIC associated with the virtual machine. |
| String | The name of the virtual machine. |
| List | The availability of the virtual machine. |
| Integer | The IP address of the virtual machine. |
| Integer | The number of minutes that the virtual machine has been running. |
| String | The domain (usually Active Directory domain) that groups these machines. |
| String | The operating system selected when the virtual machine was created. |
| Date | The date on which the virtual machine was created. |
| String | The unique name that identifies the virtual machine on the network. |
| Integer | The percent of processing power used. |
| Integer | The percentage of memory used. |
| Integer | The percentage of network used. |
| Integer | The maximum memory defined. |
| String | The applications currently installed on the virtual machine. |
| List | The cluster to which the virtual machine belongs. |
| List | The virtual machine pool to which the virtual machine belongs. |
| String | The name of the user currently logged in to the virtual machine. |
| List | The tags to which the virtual machine belongs. |
| String | The data center to which the virtual machine belongs. |
| List | The virtual machine type (server or desktop). |
| String | The name of the quota associated with the virtual machine. |
| String | Keywords or text describing the virtual machine, optionally used when creating the virtual machine. |
| List | Sorts the returned results by one of the resource properties. |
| Integer | The page number of results to display. |
| Boolean | The virtual machine has pending configuration changes. |
Example
Vms: template.name = Win* and user.name = ""
This example returns a list of virtual machines whose base template name begins with Win and are assigned to any user.
Example
Vms: cluster = Default and os = windows7
This example returns a list of virtual machines that belong to the Default cluster and are running Windows 7.
2.16. Searching for Pools
The following table describes all search options for Pools.
Table 2.12. Searching for Pools
Property (of resource or resource-type) | Type | Description (Reference) |
---|---|---|
| String | The name of the pool. |
| String | The description of the pool. |
| List | The type of pool. |
| List | Sorts the returned results by one of the resource properties. |
| Integer | The page number of results to display. |
Example
Pools: type = automatic
This example returns a list of pools with a type of automatic
.
2.17. Searching for Templates
The following table describes all search options for templates.
Table 2.13. Searching for Templates
Property (of resource or resource-type) | Type | Description (Reference) |
---|---|---|
| String | The property of the virtual machines associated with the template. |
| String | The property of the hosts associated with the template. |
| String | The property of the events associated with the template. |
| String | The property of the users associated with the template. |
| String | The name of the template. |
| String | The domain of the template. |
| String | The type of operating system. |
| Integer | The date on which the template was created. Date format is mm/dd/yy. |
| Integer | The number of virtual machines created from the template. |
| Integer | Defined memory. |
| String | The description of the template. |
| String | The status of the template. |
| String | The cluster associated with the template. |
| String | The data center associated with the template. |
| String | The quota associated with the template. |
| List | Sorts the returned results by one of the resource properties. |
| Integer | The page number of results to display. |
Example
Template: Events.severity >= normal and Vms.uptime > 0
This example returns a list of templates where events of normal or greater severity have occurred on virtual machines derived from the template, and the virtual machines are still running.
2.18. Searching for Users
The following table describes all search options for users.
Table 2.14. Searching for Users
Property (of resource or resource-type) | Type | Description (Reference) |
---|---|---|
| Depends on property type | The property of the virtual machines associated with the user. |
| Depends on property type | The property of the hosts associated with the user. |
| Depends on property type | The property of the templates associated with the user. |
| Depends on property type | The property of the events associated with the user. |
| String | The name of the user. |
| String | The last name of the user. |
| String | The unique name of the user. |
| String | The department to which the user belongs. |
| String | The group to which the user belongs. |
| String | The title of the user. |
| String | The status of the user. |
| String | The role of the user. |
| String | The tag to which the user belongs. |
| String | The pool to which the user belongs. |
| List | Sorts the returned results by one of the resource properties. |
| Integer | The page number of results to display. |
Example
Users: Events.severity > normal and Vms.status = up or Vms.status = pause
This example returns a list of users where events of greater than normal severity have occurred on their virtual machines AND the virtual machines are still running; or the users' virtual machines are paused.
2.19. Searching for Events
The following table describes all search options you can use to search for events. Auto-completion is offered for many options as appropriate.
Table 2.15. Searching for Events
Property (of resource or resource-type) | Type | Description (Reference) |
---|---|---|
| Depends on property type | The property of the virtual machines associated with the event. |
| Depends on property type | The property of the hosts associated with the event. |
| Depends on property type | The property of the templates associated with the event. |
| Depends on property type | The property of the users associated with the event. |
| Depends on property type | The property of the clusters associated with the event. |
| Depends on property type | The property of the volumes associated with the event. |
| List | Type of the event. |
| List | The severity of the event: Warning/Error/Normal. |
| String | Description of the event type. |
| List | Day the event occurred. |
| String | The user name associated with the event. |
| String | The host associated with the event. |
| String | The virtual machine associated with the event. |
| String | The template associated with the event. |
| String | The storage associated with the event. |
| String | The data center associated with the event. |
| String | The volume associated with the event. |
| Integer | The identification number of the event. |
| List | Sorts the returned results by one of the resource properties. |
| Integer | The page number of results to display. |
Example
Events: Vms.name = testdesktop and Hosts.name = gonzo.example.com
This example returns a list of events, where the event occurred on the virtual machine named testdesktop
while it was running on the host gonzo.example.com
.
Chapter 3. Bookmarks
3.1. Saving a Query String as a Bookmark
A bookmark can be used to remember a search query, and shared with other users.
Saving a Query String as a Bookmark
- Enter the desired search query in the search bar and perform the search.
- Click the star-shaped Bookmark button to the right of the search bar to open the New Bookmark window.
- Enter the Name of the bookmark.
- Edit the Search string field, if required.
- Click OK.
Click the Bookmarks icon (
) in the header bar to find and select the bookmark.
3.2. Editing a Bookmark
You can modify the name and search string of a bookmark.
Editing a Bookmark
-
Click the Bookmarks icon (
) in the header bar.
- Select a bookmark and click Edit.
- Change the Name and Search string fields as necessary.
- Click OK.
3.3. Deleting a Bookmark
When a bookmark is no longer needed, remove it.
Deleting a Bookmark
-
Click the Bookmarks icon (
) in the header bar.
- Select a bookmark and click Remove.
- Click OK.
Chapter 4. Tags
4.1. Using Tags to Customize Interactions with Red Hat Virtualization
After your Red Hat Virtualization platform is set up and configured to your requirements, you can customize the way you work with it using tags. Tags allow system resources to be arranged into groups or categories. This is useful when many objects exist in the virtualization environment and the administrator wants to concentrate on a specific set of them.
This section describes how to create and edit tags, assign them to hosts or virtual machines and search using the tags as criteria. Tags can be arranged in a hierarchy that matches a structure, to fit the needs of the enterprise.
To create, modify, and remove Administration Portal tags, click the Tags icon (
) in the header bar.
4.2. Creating a Tag
Create tags so you can filter search results using tags.
Creating a Tag
-
Click the Tags icon (
) in the header bar.
- Click Add to create a new tag, or select a tag and click New to create a descendant tag.
- Enter the Name and Description of the new tag.
- Click OK.
4.3. Modifying a Tag
You can edit the name and description of a tag.
Modifying a Tag
-
Click the Tags icon (
) in the header bar.
- Select the tag you want to modify and click Edit.
- Change the Name and Description fields as necessary.
- Click OK.
4.4. Deleting a Tag
When a tag is no longer needed, remove it.
Deleting a Tag
-
Click the Tags icon (
) in the header bar.
- Select the tag you want to delete and click Remove. A message warns you that removing the tag will also remove all descendants of the tag.
- Click OK.
You have removed the tag and all its descendants. The tag is also removed from all the objects that it was attached to.
4.5. Adding and Removing Tags to and from Objects
You can assign tags to and remove tags from hosts, virtual machines, and users.
Adding and Removing Tags to and from Objects
- Select the object(s) you want to tag or untag.
- Click More Actions → Assign Tags.
- Select the check box to assign a tag to the object, or clear the check box to detach the tag from the object.
- Click OK.
The specified tag is now added or removed as a custom property of the selected object(s).
4.6. Searching for Objects Using Tags
Enter a search query using tag
as the property and the desired value or set of values as criteria for the search.
The objects tagged with the specified criteria are listed in the results list.
If you search for objects using tag
as the property and the inequality operator (!=
), for example, Host: Vms.tag!=server1
, the results list does not include untagged objects.