SD Virtualization
This tab allows you to create new virtual guests, apply images on a traditionally managed host system, or change the status of virtual guests. You can also list and manage the storage pools that are used for the virtual machines.

The Virtualization
tab has one subtab, Guests
.
For traditional systems that have Virtualization entitlements, you will also see two additional subtabs for Provisioning
, and Deployment
.
For Salt clients, you will also see a Storage
subtab.
These tabs appear only for systems having the Virtualization entitlement.
It is not possible to create a guest system that runs on another guest system.
Guests
Guests
is the default virtualization tab.
It presents a table of the host system’s virtual guests.
For each guest system, the following information is provided:
Status
-
This field indicates whether the virtual system is running, paused, stopped, or has crashed.
Updates
-
This field indicates whether patches (errata) applicable to the guest have yet to be applied.
Base Software Channel
-
This field indicates the Base Channel to which the guest is subscribed.
If a guest system has not registered with Uyuni, this information appears as plain text in the table. |
Actions
-
This field contains the possible actions for the guest. These are depending on the virtual guest status, they may not refresh instantaneously when running a Start, Stop, Suspend, Resume action. The Edit button allows changing virtual guest properties, including the amount of allocated memory and virtual CPUs.
The Graphical Console button opens the Spice or VNC display in a new tab.
If you have System Group Administrator responsibilities assigned for your guest systems, a user might see the message You do not have permission to access this system
in the table.
This is because it is possible to assign virtual guests on a single host to multiple System Group Administrators.
Only users that have System Group Administrator privileges on the host system may create new virtual guests.
For Salt systems, the Create Guest button shows a dialog to configure and create a new virtual machine.
Editing a Virtual Machine
Traditional systems can only edit CPU and memory allocation. |
The fields in this dialog are grouped into several panels.
The General
panel contains the CPU
and memory
fields.
The Disks
and Network Interfaces
panels list the fields corresponding to the matching devices of the virtal machine.
The Graphics
panel allows configuring the display of the virtual machine.
The Schedule
panel helps configuring when the edit should take place by choosing either an earliest time or an action chain to append to.
If a guest contains one or more disks or network interfaces not recognized by SUSE Manager, you will not be able to edit the configuration. This prevents any possibility of SUSE Manager destroying the setup because of an unhandled type. |
The order of the disks is important: the disk naming will be computed from it. This means that the first virtio disk will be named 'vda', the second will be named 'vdb' and so on.
When clicking the + in the Disks
(or Network Interfaces
) panel header, a new disk (or network interface) will be appended to the list.
Likewise, clicking the - button next to a disk or interface will remove it.
The default size for a new disk is 8[nbsp]GB.
The Source image template URL
field contains the URL to a disk image to be copied and used for the virtual machine.
Click the Update button to apply the changes.
Creating a virtual machine [Salt]
To create a new virtual machine, the process is similar to editing, but there are some additional fields:
The Name
field defining the name of the virtual machine to create.
The Hypervisor
field to allow choosing among the available hypervisors of the host.
The Virtual Machine Type
to choose between fully virtualized and para-virtualized virtual machines if applicable.
The Architecture
to select the emulated CPU architecture, the default being the virtual host one.
By default a disk and a network interfaces are added. The only required value to set is the disk Source template image URL
or the virtual machine will only have an empty disk.
The new virtual machine will start immediately after it has been defined.
Display a virtual machine graphical console [Salt]
The virtual machine graphical console might prompt you for a password. This password is the Spice or VNC one.
For the Spice display to be adjusted to the window, the Spice VD agent needs to be installed within the virtual machine.
Deployment [Management]
In the qcow2
type of image and some other parameters allowing the user to schedule the deployment of that image.

When the deploment scheduled it is listed as an action on the
.Storage for Salt Clients
The Storage
tab shows a tree list of the virtual storage pools and volumes that are defined on the virtual host.
The first level of the tree is the list of storage pools and all items contained in them are volumes.
Expand the pools to show the volumes.
Each pool shows:
Status
-
The pool is either running or stopped.
Autostart
-
The pool starts automatically when the virtual host boots.
Persistent
-
The pool will be kept after being stopped.
Location
-
The target path of the storage pool. Note that some pool types don’t have an associated path.
Usage
-
The disk usage of the pool. Shows
Unknown
if the pool is not running.
Each volume shows:
-
The name of the virtual machines using the volume. Some pool types will not provide this list.
-
The disk usage of the volume.
Refreshing a pool
The libvirt
service does not automatically update the pool usage and contents statistics.
Refresh the pool to see updated usage statistics, or to see a volume that has been created outside of Uyuni.
Click the Refresh
button to schedule a refresh of the pool.
-
Click Create Pool
-
This opens a new page with a form to define the pool.
-
In the
name
field, type a name for the new pool. -
In the
type
field, select the type of the pool. The list of available types depends on the virtual host setup. -
Check the
Start during virtual host boot
field, to start the pool automatically when the virtual host boots. -
OPTIONAL: In the
Earliest
field, you can set the earliest time the pool creation action should be scheduled. -
OPTIONAL: In the
Add to
field, you can select a new or existing action chain to add the pool creation action to. -
The
Source
section contains data about the device holding the pool. -
The
Target
section contains data about where to find the pool on the virtual host.
Source Fields
Device path
-
Path to a device containing the pool data
Partition separator
-
Use
'p'
as a partition separator in the path name. Format
-
Select the format of the pool source. The available values depend on the pool type.
Host name
-
IP or FQDN of the remote machine providing access to the pool.
Port
-
Port of the remote machine providing access to the pool.
iSCSI Qualified Name
-
Qualified name of the iSCSI target.
IQN Initiator
-
iSCSI qualified name of the initiator to connect to.
Username
-
Username to use to connect to remote storage.
Passphrase
-
Password to use to connect to remote storage. For RBD pools, this is the base64 encoded key.
Source name
-
Name of the storage pool source.
Directory
-
Path to the directory of the pool.
Subdirectory
-
Absolute path relative to the Gluster volume to use.
Adapter type
-
The controller type, either
fc_host
orscsi_host
. Adapter name
-
SCSI adapter name for
scsi_host
controller. Adapter parent PCI address
-
PCI address of the SCSI host in
0000:00:00.0
format. List options withlsscsi -v
. Adapter parent address unique ID
-
Unique ID of the SCSI host as found in
/sys/class/scsi_host/host*/unique_id
file. Adapter parent name
-
Name of the vport capable parent SCSI host of the virtual Host Bus Adapter (vHBA).
Adapter parent wwnn
-
World Wide Node Name used by the
fc_host
to identify the vHBA parent device. Adapter parent wwpn
-
World Wide Port Name used by the
fc_host
to identify the vHBA parent device. Adapter parent fabric wwn
-
Fabric WWN of the vHBA parent device.
Adapter wwnn
-
World Wide Node Name used by the
fc_host
to identify the vHBA device. Adapter wwpn
-
World Wide Port Name used by the
fc_host
to identify the vHBA device. Manage vHBA deletion
-
If checked the vHBA will be destroyed with the pool is destroyed. This property will be automatically activated if there is no existing vHBA.
Target fields
Path
-
Path to the storage pool mount or device on the virtual host.
Owner ID
-
ID of the user owning the path folder or file.
Group ID
-
ID of the group owning the path folder or file.
Permission mode
-
Octal representation of the permissions to set on the path folder or file.
SELinux label
-
SELinux label to set on the path folder or file.
Editing a pool
To edit the properties of a storage pool, locate the pool in the list and click Edit pool
.
Deleting a Pool
To delete a storage pool, locate the pool in the list and click Delete
.
By default, deleting a pool only removes the storage pool definition.
The pool data is kept on disk.
To delete the pool data as well as the storage pool definition, check the Delete the pool, including the contained volumes
box before you click Delete
.
Some pool types will not allow you to delete the volumes or the pool.
Deleting a Volume
To delete a storage volume, locate the volume in the tree and click Delete
on its row.
Some pool types will not allow you to delete volumes.