All Classes and Interfaces
Class
Description
Management of remote authentication services
First published in XenServer 5.5.
A placeholder for a binary blob
First published in XenServer 5.0.
Represents all the fields in a Blob
First published in XenServer 4.1.
Represents all the fields in a Bond
Description
First published in Citrix Hypervisor 8.2.
Represents all the fields in a Certificate
Cluster-wide Cluster metadata
First published in XenServer 7.6.
Represents all the fields in a Cluster
Cluster member metadata
First published in XenServer 7.6.
Represents all the fields in a ClusterHost
Represents a connection to a XenServer.
A console
First published in XenServer 4.0.
Represents all the fields in a Console
A VM crashdump
First published in XenServer 4.0.
Represents all the fields in a Crashdump
Data sources for logging in RRDs
First published in XenServer 5.0.
Represents all the fields in a DataSource
DR task
First published in XenServer 6.0.
Represents all the fields in a DRTask
Asynchronous event registration and handling
First published in XenServer 4.0.
Represents all the fields in a Event
Class used to map the output of Event.from().
A new piece of functionality
First published in XenServer 7.2.
Represents all the fields in a Feature
A group of compatible GPUs across the resource pool
First published in XenServer 6.0.
Represents all the fields in a GPUGroup
A physical host
First published in XenServer 4.0.
Represents all the fields in a Host
A physical CPU
First published in XenServer 4.0.
Represents all the fields in a HostCpu
Represents a host crash dump
First published in XenServer 4.0.
Represents all the fields in a HostCrashdump
The metrics associated with a host
First published in XenServer 4.0.
Represents all the fields in a HostMetrics
Represents a patch stored on a server
First published in XenServer 4.0.
Represents all the fields in a HostPatch
LVHD SR specific operations
First published in XenServer 7.0.
Represents all the fields in a LVHD
Marshalls Java types onto the wire.
An message for the attention of the administrator
First published in XenServer 5.0.
Represents all the fields in a Message
A virtual network
First published in XenServer 4.0.
Represents all the fields in a Network
network-sriov which connects logical pif and physical pif
First published in XenServer 7.5.
Represents all the fields in a NetworkSriov
Describes a observer which will control observability activity in the Toolstack
First published in .
Represents all the fields in a Observer
The physical block devices through which hosts access SRs
First published in XenServer 4.0.
Represents all the fields in a PBD
A PCI device
First published in XenServer 6.0.
Represents all the fields in a PCI
A physical GPU (pGPU)
First published in XenServer 6.0.
Represents all the fields in a PGPU
A physical network interface (note separate VLANs are represented as several PIFs)
First published in XenServer 4.0.
Represents all the fields in a PIF
The metrics associated with a physical network interface
First published in XenServer 4.0.
Represents all the fields in a PIFMetrics
Pool-wide information
First published in XenServer 4.0.
Represents all the fields in a Pool
Pool-wide patches
First published in XenServer 4.1.
Represents all the fields in a PoolPatch
Pool-wide updates to the host software
First published in XenServer 7.1.
Represents all the fields in a PoolUpdate
A set of properties that describe one result element of SR.probe.
Represents all the fields in a ProbeResult
A physical USB device
First published in XenServer 7.3.
Represents all the fields in a PUSB
Describes the storage that is available to a PVS site for caching purposes
First published in XenServer 7.1.
Represents all the fields in a PVSCacheStorage
a proxy connects a VM/VIF with a PVS site
First published in XenServer 7.1.
Represents all the fields in a PVSProxy
individual machine serving provisioning (block) data
First published in XenServer 7.1.
Represents all the fields in a PVSServer
machines serving blocks of data for provisioning VMs
First published in XenServer 7.1.
Represents all the fields in a PVSSite
Repository for updates
First published in 1.301.0.
Represents all the fields in a Repository
A set of permissions associated with a subject
First published in XenServer 5.6.
Represents all the fields in a Role
Describes the SDN controller that is to connect with the pool
First published in XenServer 7.2.
Represents all the fields in a SDNController
A secret
First published in XenServer 5.6.
Represents all the fields in a Secret
A session
First published in XenServer 4.0.
Represents all the fields in a Session
A storage manager plugin
First published in XenServer 4.0.
Represents all the fields in a SM
A storage repository
First published in XenServer 4.0.
Represents all the fields in a SR
A set of high-level properties associated with an SR.
Represents all the fields in a SrStat
A user or group that can log in xapi
First published in XenServer 5.5.
Represents all the fields in a Subject
A long-running asynchronous task
First published in XenServer 4.0.
Represents all the fields in a Task
A tunnel for network traffic
First published in XenServer 5.6 FP1.
Represents all the fields in a Tunnel
This class holds vital marshalling functions, enum types and exceptions.
An activation key can only be applied when the edition is set to 'free'.
The specified IP address violates the VIF locking configuration.
Failed to apply guidance on a host after updating.
Failed to apply a livepatch.
Failed to apply updates on a host.
The operation could not be performed because applying updates is in progress.
External authentication for this server is already enabled.
The host failed to disable external authentication.
The host failed to disable external authentication.
The host failed to disable external authentication.
The host failed to enable external authentication.
The host failed to enable external authentication.
The host failed to enable external authentication.
The host failed to enable external authentication.
The host failed to enable external authentication.
The host failed to enable external authentication.
The host failed to enable external authentication.
External authentication is disabled, unable to resolve subject name.
Error querying the external directory service.
Unknown type of external authentication.
The backup could not be performed because the backup script failed.
Thrown if the response from the server contains an invalid status.
Timeout trying to balloon down memory before VM migration.
The bootloader returned an error
The specified bridge already exists.
Could not find bridge required by VM.
This PIF is a bond member and cannot have a tunnel on it.
This is a network SR-IOV logical PIF and cannot have a tunnel on it.
This is a vlan PIF on network SR-IOV and cannot have a tunnel on it.
This PIF is a bond member and cannot have a VLAN on it.
The properties of this PIF cannot be changed.
Cannot forward messages because the server cannot be contacted.
An HA statefile could not be created, perhaps because no SR with the appropriate capability was found.
The disaster recovery task could not be cleanly destroyed.
You tried to destroy a system network: these cannot be destroyed.
Could not enable redo log.
This server cannot be evacuated.
The requested update could not be obtained from the coordinator.
The backup partition to stream the update to cannot be found.
The requested update could not be found.
This operation could not be performed because the state partition could not be found
The requested update could not be found.
This is a network SR-IOV logical PIF and cannot do forget on it
This PIF is a bond member and cannot be plugged.
Cannot plug VIF
The power-state of a control domain cannot be reset.
Cannot restart device models of paused VMs residing on the host.
A certificate already exists with the specified name.
The specified certificate is corrupt or unreadable.
The specified certificate does not exist.
The certificate library is corrupt or unreadable.
The specified certificate name is invalid.
The system rejected the password change request; perhaps the new password was too short?
A cluster already exists in the pool.
The operation could not be performed because cluster creation is in progress.
An operation failed as it expected the cluster to have only one node but found multiple cluster_hosts.
An SR is using clustered local storage.
Force destroy failed on a Cluster_host while force destroying the cluster.
The last cluster host cannot be destroyed.
Cluster_host operation failed as the cluster_host has not joined the cluster.
An operation was attempted while clustering was disabled on the cluster_host.
An operation was attempted while clustering was enabled on the cluster_host.
The cluster stack is still in use by at least one plugged PBD.
The operation could not be performed because other repository(ies) is(are) already being configured.
Could not find a network interface with the specified device name and MAC address.
An error occurred while attempting to import a database from a metadata VDI
The IGMP Snooping setting cannot be applied for some of the host, network(s).
The CPU does not support masking of features.
A CRL already exists with the specified name.
The specified CRL is corrupt or unreadable.
The specified CRL does not exist.
The specified CRL name is invalid.
You attempted an operation which would have resulted in duplicate keys in the database.
The default SR reference does not point to a valid SR
The device is already attached to a VM
The device is not currently attached
A device with the name given already exists on the selected VM
A timeout happened while attempting to attach a device to a VM.
The VM rejected the attempt to detach the device.
A timeout happened while attempting to detach a device from a VM.
The operation could not be performed because the VBD was not connected to the VM.
All VBDs of type 'disk' must be read/write for HVM guests
An internal error generated by the domain builder.
The operation could not be performed because a domain still exists for the specified VM.
This MAC seed is already in use by a VM in the pool
A PIF with this specified device name already exists.
Cannot restore this VM because it would create a duplicate
The event.from token could not be parsed.
Some events have been lost from the queue and cannot be retrieved.
The server failed to parse your event subscription.
An emulator required to run this VM failed to start
The VM is set up to use a feature that requires it to boot as HVM.
The use of this feature is restricted.
The value specified is of the wrong type
Failed to get available updates from a host.
Failed to get available updates from the pool.
The operation could not be performed because getting updates is in progress.
The GPU group does not contain any PGPUs.
The GPU group contains active PGPUs and cannot be deleted.
The GPU group contains active VGPUs and cannot be deleted.
This server cannot accept the proposed new coordinator setting at this time.
This operation cannot be performed because creating or deleting a bond involving the management interface is not allowed while HA is on.
This operation cannot be performed because the referenced network is not properly shared.
This operation cannot be performed because the referenced SR is not properly shared.
The operation could not be performed because HA disable is in progress
The operation could not be performed because HA enable is in progress
HA could not be enabled on the Pool because a liveset could not be formed: check storage and network heartbeat paths.
The server could not join the liveset because the HA daemon failed to start.
The server could not join the liveset because the HA daemon could not access the heartbeat disk.
The operation failed because the HA software on the specified server could not see a subset of other servers.
The operation could not be performed while the server is still armed; it must be disarmed first.
The operation could not be performed because HA is enabled on the Pool
This server lost access to the HA statefile.
You gave an invalid object reference.
Cannot find a plan for placement of VMs as there are no other servers available.
The operation could not be performed because HA is not enabled on the Pool
The operation could not be performed because the HA software is not installed on this server.
This operation cannot be performed because it would invalidate VM failover planning such that the system would be unable to guarantee to restart protected VMs after a Host failure.
This server cannot join the pool because the pool has HA enabled but this server has HA disabled.
Server cannot rejoin pool because it should have fenced (it is not in the coordinator's partition).
HA can only be enabled for 2 servers or more.
This server failed in the middle of an automatic failover operation and needs to retry the failover action.
Server cannot attach network (in the case of NIC bonding, this may be because attaching the network on this server would require other networks - that are currently active - to be taken down).
The pool coordinator host cannot be removed.
The metrics of this server could not be read.
The host CDROM drive does not contain a valid CD
The specified server is disabled.
The specified server is disabled and cannot be re-enabled until after it has rebooted.
This host is being evacuated.
The server failed to acquire an IP address on its management interface and therefore cannot contact the coordinator.
This server cannot be forgotten because there are user VMs still running.
Cannot perform operation as the host is running in emergency mode.
This operation cannot be completed as the host is in use by (at least) the object of type and ref echoed below.
This operation cannot be completed because the server is still live.
You cannot make regular API calls directly on a supporter.
The host is its own supporter.
The coordinator reports that it cannot talk back to the supporter on the supplied management IP address.
The server name is invalid.
This operation cannot be performed because the host is not disabled.
Not enough server memory is available to perform this operation.
The host does not have enough pCPUs to run the VM.
This operation cannot be completed as the server is not live.
You attempted an operation which involves a host which could not be contacted.
This operation cannot be completed because the server power on mode is disabled.
The hosts in this pool are not compatible.
The hosts in this pool are not homogeneous.
The host toolstack is still initialising.
The coordinator says the server is not known to it.
The host xapi version is higher than the one in the coordinator
The specified VBD device is not recognized: please use a non-negative integer
The VM could not be imported.
The VM could not be imported because attached disks could not be found.
Cannot import VM using chunked encoding.
The VM could not be imported because a required object could not be found.
The VM could not be imported; the end of the file was reached prematurely.
Some data checksums were incorrect; the VM may be corrupt.
The VM could not be imported because the XVA file is invalid: an unexpected file was encountered.
The import failed because this export has been created by a different (incompatible) product version
This operation cannot be performed, because it is incompatible with the currently active HA cluster stack.
These PIFs cannot be bonded, because their properties are different.
The specified SR is incompatible with the selected HA cluster stack.
The specified interface cannot be used because it has no IP address
The server failed to handle your request, due to an internal error.
The base url in the repository is invalid.
A required parameter contained an invalid CIDR address (<addr>/<prefix length>)
The cluster stack provided is not supported.
The device name is invalid
The edition you supplied is invalid.
The given feature string is not valid.
The GPG public key file name in the repository is invalid.
A required parameter contained an invalid IP address
The uploaded patch file is invalid
The uploaded patch file is invalid.
The repomd.xml is invalid.
The repository domain allowlist has some invalid domains.
The repository proxy username/password is invalid.
The repository proxy URL is invalid.
The uploaded update package is invalid.
The updateinfo.xml is invalid.
Invalid day of the week chosen for weekly update sync.
The value given is invalid
Cannot create a VLAN or tunnel on top of a tunnel access PIF - use the underlying transport PIF instead.
The server joining the pool cannot already be a coordinator of another pool.
The server joining the pool cannot contain any shared storage.
The server joining the pool cannot have any running or suspended VMs.
The server joining the pool cannot have any running VMs.
The host joining the pool cannot have any VMs with active tasks.
There was an error connecting to the host while joining it in the pool.
There was an error connecting to the server.
This operation is not allowed because your license lacks a needed feature.
Cannot downgrade license while in pool.
The license for the edition you requested is not available.
This server cannot join a pool because its license does not support pooling.
HA cannot be enabled because this server's license does not allow it.
Your license has expired.
This type of license file is for previous versions of the server.
Host and pool have incompatible licenses (editions).
There was an error processing your license.
A VDI with the specified location already exists within the SR
The MAC address specified does not exist on this server.
The MAC address specified is not valid.
The MAC address specified still exists on this server.
You tried to add a key-value pair to a map, but that key is already there.
The dynamic memory range does not satisfy the following constraint.
The dynamic memory range violates constraint static_min = dynamic_min = dynamic_max = static_max.
The dynamic memory range violates constraint static_min <= dynamic_min <= dynamic_max <= static_max.
This message has been deprecated.
You tried to call a method that does not exist.
You tried to call a method with the incorrect number of parameters.
This function is no longer available.
The VDI mirroring cannot be performed
The license-server connection details (address or port) were missing or incomplete.
There is more than one update repository being enabled.
You tried to create a PIF, but the network you tried to attach it to is already attached to some other PIF, and so the creation failed.
The network contains active PIFs and cannot be deleted.
The network contains active VIFs and cannot be deleted.
The PIF is not compatible with the selected SR-IOV network
VLAN on the PIF is not compatible with the selected SR-IOV VLAN network
You tried to add a purpose to a network but the new purpose is not compatible with an existing purpose of the network or other networks.
The network is incompatible with bond
The network is incompatible with sriov
The network is incompatible with tunnel
The network is incompatible with vlan on bridge
The network is incompatible with vlan on sriov
The PIF selected for the SR-IOV network is already enabled
Failed to disable SR-IOV on PIF
Failed to enable SR-IOV on PIF
There is insufficient capacity for VF reservation
The network is not managed by xapi.
No other cluster host was reachable when joining
Clustering is not enabled on this host or pool.
There were no servers available to complete the specified operation.
The upper limit of active redo log instances was reached.
No update repositories have been configured.
There is no repository being enabled.
This command is not allowed on the OEM edition.
The function is not implemented
This pool is not in emergency mode.
This operation is not supported during an upgrade.
The given VM is not registered as a system domain.
The NVidia GPU is not configured for SR-IOV as expected
Nvidia tools error.
The specified object no longer exists.
This command is only allowed on the OEM edition.
This operation needs the OpenVSwitch networking backend to be enabled on all hosts in the pool.
You attempted an operation that was explicitly blocked (see the blocked_operations field of the given object).
You attempted an operation that was not allowed.
Some VMs belonging to the appliance threw an exception while carrying out the specified operation
Another operation involving the object is currently in progress
There is not enough space to upload the update
This patch has already been applied
The uploaded patch file already exists
The patch apply failed.
The patch apply failed: there are backup files created while applying patch.
The specified patch is applied and cannot be destroyed.
Tools ISO must be ejected from all running VMs.
The patch pre-check stage failed: the server does not have enough space.
The patch pre-check stage failed: prerequisite patches are missing.
The patch pre-check stage failed with an unknown error.
The patch pre-check stage failed: there are one or more VMs still running on the server.
The patch pre-check stage failed: the server is of an incorrect build.
The patch pre-check stage failed: the server is of an incorrect version.
A PBD already exists connecting the SR to the server.
Caller not allowed to perform this operation.
There is insufficient capacity on this PGPU to run the VGPU.
This PGPU is currently in use by running VMs.
PGPU type not compatible with destination group.
The operation you requested cannot be performed because the specified PIF allows unplug.
This operation cannot be performed because the pif is bonded.
Only one PIF on a bond is allowed to have an IP configuration.
A bond must consist of at least two member interfaces
You cannot bond interfaces across different servers.
An unknown error occurred while attempting to configure an interface.
The specified device was not found.
The operation you requested cannot be performed because the specified PIF does not allow unplug.
The operation you requested cannot be performed because the specified PIF has FCoE SR in use.
PIF has no IP configuration (mode currently set to 'none')
PIF has no IPv6 configuration (mode currently set to 'none')
The primary address types are not compatible
The operation you requested cannot be performed because the specified PIF is the management interface.
You tried to perform an operation which is only available on physical PIF
The selected PIF is not capable of network SR-IOV
You tried to destroy a PIF, but it represents an aspect of the physical host configuration, and so cannot be destroyed.
You tried to create a bond on top of a network SR-IOV logical PIF - use the underlying physical PIF instead
You tried to create a VLAN on top of another VLAN - use the underlying physical PIF/bond instead
Cluster_host creation failed as the PIF provided is not attached to the host.
This host has no PIF on the given network.
The PIF is still related with a network SR-IOV
Operation cannot proceed while a tunnel exists on this interface.
The operation you requested cannot be performed because the specified PIF is not managed by xapi.
You tried to create a PIF, but it already exists.
Operation cannot proceed while a VLAN exists on this interface.
External authentication is already enabled for at least one server in this pool.
The pool failed to disable the external authentication of at least one host.
External authentication has been disabled with errors: Some AD machine accounts were not disabled on the AD server due to invalid account.
External authentication has been disabled with errors: Your AD machine account was not disabled on the AD server as permission was denied.
External authentication has been disabled with errors: Some AD machine accounts were not disabled on the AD server due to invalid credentials.
The pool failed to enable external authentication.
The pool failed to enable external authentication.
The pool failed to enable external authentication.
The pool failed to enable external authentication.
The pool failed to enable external authentication.
The pool failed to enable external authentication.
The pool failed to enable external authentication.
The pool failed to enable external authentication.
Cannot join pool whose external authentication configuration is different.
The host joining the pool has different CA certificates from the pool coordinator while using the same name, uninstall them and try again.
The host joining the pool must not have any bonds.
The host joining the pool must not have any network SR-IOVs.
The host joining the pool must not have any non-management vlans.
The host joining the pool must not have any tunnels.
The host joining the pool must have the same management vlan.
The server joining the pool must have a physical management NIC (i.e.
The host joining the pool must have the same API version as the pool coordinator.
The host joining the pool must have the same database schema as the pool coordinator.
The server joining the pool must have the same product version as the pool coordinator.
The host joining the pool must not have any bonds, VLANs or tunnels.
The provision call failed because it ran out of space.
The provision call can only be invoked on templates, not regular VMs.
The VDI corresponding to this PUSB has existing VBDs.
The PVS site already has cache storage configured for the host.
The PVS cache storage is in use by the site and cannot be removed.
The VIF is already associated with a PVS proxy
The address specified is already in use by an existing PVS_server object
The PVS site contains running proxies.
The PVS site contains servers and cannot be forgotten.
RBAC permission denied.
Interface for all Record classes
The operation could not be performed because a redo log is enabled on the Pool.
The repository already exists.
Failed to clean up local repository on coordinator.
The repository is in use.
Syncing with remote YUM repository failed.
The operation you requested cannot be performed because the specified PIF is currently unplugged.
The restore could not be performed because this backup has been created by a different (incompatible) product version
The restore could not be performed because the restore script failed.
The restore could not be performed because the server's current management interface is not in the backup.
The restore could not be performed because a network interface is missing
Role already exists.
Role cannot be found.
The provided intermediate certificates are not in a PEM-encoded X509.
The provided certificate has expired.
The provided certificate is not in a PEM-encoded X509.
The provided key uses an unsupported algorithm.
The provided key is not in a PEM-encoded PKCS#8 format.
The provided key does not match the provided certificate's public key.
The provided RSA key does not have a length between 2048 and 4096.
The provided RSA key is using more than 2 primes, expecting only 2.
The provided certificate is not valid yet.
The provided certificate is not using the SHA256 (SHA2) signature algorithm.
The credentials given by the user are incorrect, so access has been denied, and you have not been issued a session handle.
The credentials given by the user are correct, but the user could not be authorized, so access has been denied, and you have not been issued a session handle.
You gave an invalid session reference.
This session is not registered to receive events.
The management interface on a supporter cannot be disabled because the supporter would enter emergency mode.
The SM plug-in did not respond to a query.
Attaching this SR failed.
There was an SR backend failure.
The SR operation cannot be performed because a device underlying the SR is in use by the server.
Cannot migrate a VDI to or from an SR that doesn't support migration.
The SR is full.
The SR.shared flag cannot be set to false while the SR remains connected to multiple servers.
The SR has no attached PBDs
The SR is still connected to a host via a PBD.
The SR could not be destroyed because the 'indestructible' flag was set on it.
The SR is currently being used as a local cache SR.
The SR is not attached.
The SR operation cannot be performed because the SR is not empty.
The PBD could not be plugged because the SR is in use by another host and is not marked as sharable.
The SR backend does not support the operation (check the SR's allowed operations)
The operation cannot be performed until the SR has been upgraded
The source SR does not have sufficient temporary space available to proceed the operation.
The SR could not be connected because the driver was not recognised.
An SR with that uuid already exists.
The operation could not proceed because necessary VDIs were already locked at the storage level.
The remote system's SSL certificate failed to verify against our certificate library.
Subject already exists.
Subject cannot be resolved by the external directory service.
The suspend image of a checkpoint is not accessible from the host on which the VM is running
The operation could not be performed because syncing updates is in progress.
You must use tar output to retrieve system status from an OEM server.
Retrieving system status from the host failed.
The request was asynchronously canceled.
The next scheduled telemetry data collection is too far into the future.
Cannot contact the other host using TLS on the specified address and port
The request was rejected because the server is too busy.
The request was rejected because there are too many pending tasks on the server.
You reached the maximal number of concurrently migrating VMs.
The VM has too many VUSBs.
The tunnel transport PIF has no IP configuration set.
You have attempted a function which is not implemented
The requested bootloader is unknown
This update has already been applied.
This update has already been applied to all hosts in the pool.
The uploaded update already exists
The update failed to apply.
Guidance for the update has changed
The hash of updateinfo doesn't match with current one.
The specified update has been applied and cannot be destroyed.
The update cannot be applied for the following host(s).
The update pre-check stage failed: conflicting update(s) are present.
The update pre-check stage failed: RPM package validation requires a GPG key that is not present on the host.
The update pre-check stage failed: the server does not have enough space.
The update pre-check stage failed: prerequisite update(s) are missing.
The update pre-check stage failed with an unknown error.
The update pre-check stage failed: the server is of an incorrect version.
Requires recommended guidance after applying updates.
The USB device is currently attached to a VM.
USB_groups are currently restricted to contain no more than one VUSB.
The USB group does not contain any PUSBs.
The USB group contains active PUSBs and cannot be deleted.
The USB group contains active VUSBs and cannot be deleted.
Only the local superuser can perform this operation.
The uuid you supplied was invalid.
There was a problem with the license daemon (v6d).
You attempted to set a value that is not supported by this implementation.
Read/write CDs are not supported
Operation could not be performed because the drive is empty
Operation could not be performed because the drive is not empty
Media could not be ejected because it is not removable
Drive could not be hot-unplugged because it is not marked as unpluggable
This VM has locked the DVD drive tray, so the disk cannot be ejected
VCPUs_max must be a multiple of cores-per-socket
The requested operation is not allowed for VDIs with CBT enabled or VMs having such VDIs, and CBT is enabled for the specified VDI.
The VDI could not be opened for metadata recovery as it contains the current pool's metadata.
The VDI copy action has failed
The operation cannot be performed because this VDI has rrd stats
This operation cannot be performed because the specified VDI is of an incompatible type (eg: an HA statefile cannot be attached to a guest)
This operation cannot be performed because this VDI is in use by some other operation
The operation cannot be performed on physical device
The requested operation is not allowed because the specified VDI is encrypted.
This operation can only be performed on CD VDIs (iso files or CDROM drives)
This operation cannot be performed because the specified VDI could not be found in the specified SR
This operation cannot be performed because the specified VDI could not be found on the storage substrate
Cannot migrate a VDI which is not attached to a running VM.
The requested operation is not allowed because the specified VDI does not have changed block tracking metadata.
This operation cannot be performed because this VDI could not be properly attached to the VM.
This VDI was not mapped to a destination SR in VM.migrate_send operation
This operation cannot be performed because the system does not manage this VDI
The VDI is not stored using a sparse format.
This operation is not permitted on VDIs in the 'on-boot=reset' mode, or on VMs having such VDIs.
The operation required write access but this VDI is read-only
The VDI is too large.
The VDI is too small.
The VGPU is not compatible with any PGPU in the destination.
The guest driver does not support VGPU migration.
The VGPU configuration does not support suspension.
VGPU type is no longer supported
Cannot create a virtual GPU that is incompatible with the existing types on the VM.
The VGPU type is incompatible with one or more of the VGPU types currently running on this PGPU
VGPU type is not one of the PGPU's enabled types.
VGPU type is not one of the PGPU's supported types.
Network has active VIFs
This VIF was not mapped to a destination Network in VM.migrate_send operation
Operation cannot be performed because this VLAN is already in use.
You tried to create a VLAN, but the tag you gave was invalid -- it must be between 0 and 4094.
This VM is assigned to a protection policy.
This VM is assigned to a snapshot schedule.
You attempted to start a VM that's attached to more than one VDI with a timeoffset marked as reset-on-boot.
You attempted an operation on a VM that was not in an appropriate power state at the time; for example, you attempted to start a VM that was already running.
The BIOS strings for this VM have already been set and cannot be changed.
There is a minimal interval required between consecutive plug-in calls made on the same VM, please wait before retry.
You cannot delete the specified default template.
An error occured while restoring the memory image of the specified virtual machine
An error occured while saving the memory image of the specified virtual machine
The VM crashed
The specified VM has a duplicate VBD device and cannot be started.
VM didn't acknowledge the need to shutdown.
VM didn't acknowledge the need to suspend.
The VM unexpectedly halted
Cannot migrate a VM which has a checkpoint.
VM cannot be resumed because it has no suspend VDI
This operation could not be performed, because the VM has one or more PCI devices passed through.
This operation could not be performed, because the VM has one or more SR-IOV VIFs.
Cannot migrate a VM with more than one snapshot.
This operation could not be performed, because the VM has one or more virtual GPUs.
The operation is not allowed when the VM has VUSBs.
This VM operation cannot be performed on an older-versioned host during an upgrade.
Cannot migrate a VM to a destination host which is older than the source host.
You attempted to run a VM on a host that cannot provide the VM's required Virtual Hardware Platform version.
HVM is required for this operation
The VM is incompatible with the CPU features of this host.
The VM is configured in a way that prevents it from being mobile.
This operation is not allowed as the VM is part of an appliance.
This operation cannot be performed because the specified VM is protected by HA
The operation attempted is not valid for a template VM
This operation is illegal because the VM is using nested virtualization.
You attempted an operation on a VM which lacks the feature.
You attempted an operation which needs the cooperative shutdown feature on a VM which lacks it.
You attempted an operation which needs the VM static-ip-setting feature on a VM which lacks it.
You attempted an operation which needs the VM cooperative suspend feature on a VM which lacks it.
You attempted an operation which needs the VM hotplug-vcpu feature on a VM which lacks it.
The specified VM has too little memory to be started.
Failed to contact service on the destination host.
An error occurred during the migration process.
You attempted an operation on a VM which requires PV drivers to be installed but the drivers were not detected.
This VM does not have a crash dump SR specified.
The VM has no empty CD drive (VBD).
This VM does not have a suspend SR specified.
The specified VM is not currently resident on the specified server.
You need at least 1 VCPU to start a VM
You attempted an operation on a VM which requires a more recent version of the PV drivers.
The VM does not have any free PCI slots
Archive more frequent than backup.
There is at least one VM assigned to this protection policy.
VM PV drivers still in use
The VM unexpectedly rebooted
You attempted to run a VM on a host which doesn't have a pGPU available in the GPU group needed by the VM.
You attempted to run a VM on a host which doesn't have I/O virtualization (IOMMU/VT-d) enabled, which is needed by the VM.
You attempted to run a VM on a host which doesn't have a PIF on a Network needed by the VM.
You attempted to run a VM on a host which doesn't have access to an SR needed by the VM.
VM cannot be started because it requires a VDI which cannot be attached
You attempted to run a VM on a host on which the vGPU required by the VM cannot be allocated on any pGPUs in the GPU_group needed by the VM.
You attempted to run a VM on a host on which the VUSB required by the VM cannot be allocated on any PUSBs in the USB_group needed by the VM.
An error occured while reverting the specified virtual machine to the specified snapshot
The given VMs failed to release memory when instructed to do so
VM failed to shutdown before the timeout expired
The quiesced-snapshot operation failed for an unexpected reason
The VSS plug-in is not installed on this virtual machine
The VSS plug-in cannot be contacted
The VSS plug-in has timed out
There is at least one VM assigned to snapshot schedule.
VM failed to suspend before the timeout expired
The VM cannot be imported unforced because it is either the same version or an older version of an existing VM.
Too many VCPUs to start this VM
You attempted an operation on a VM that was judged to be unsafe by the server.
The VM cannot be associated with more VTPMs.
WLB rejected our configured authentication details.
WLB refused a connection to the server.
The connection to the WLB server was reset.
This pool has wlb-enabled set to false.
WLB reported an internal error.
WLB rejected the server's request as malformed.
WLB said something that the server wasn't expecting or didn't understand.
No WLB connection is configured.
The communication with the WLB server timed out.
The configured WLB server name failed to resolve in DNS.
The WLB URL is invalid.
WLB reported that the server rejected its configured authentication details.
WLB reported that the server refused to let it connect (even though we're connecting perfectly fine in the other direction).
WLB reported that the server said something to it that WLB wasn't expecting or didn't understand.
WLB reported that communication with the server timed out.
WLB reported that its configured server name for this server instance failed to resolve in DNS.
3rd party xapi hook failed
Base class for all XenAPI Exceptions
The requested plug-in could not be found.
There was a failure communicating with the plug-in.
The current version of Xen or its control libraries is incompatible with the Toolstack.
Some volumes to be snapshot could not be added to the VSS snapshot set
An attempt to create the snapshots failed
Could not create the XML string generated by the transportable snapshot
Initialization of the VSS requester failed
Could not find any volumes supported by the VSS Provider
An attempt to prepare VSS writers for the snapshot failed
The VSS Provider is not loaded
An attempt to start a new VSS snapshot failed
The server failed to unmarshal the XMLRPC message; it was expecting one element and received something else.
A group of compatible USBs across the resource pool
First published in XenServer 7.3.
Represents all the fields in a USBGroup
A user of the system
First published in XenServer 4.0.
Represents all the fields in a User
A virtual block device
First published in XenServer 4.0.
Represents all the fields in a VBD
The metrics associated with a virtual block device
First published in XenServer 4.0.
Represents all the fields in a VBDMetrics
A virtual disk image
First published in XenServer 4.0.
Represents all the fields in a VDI
Details for connecting to a VDI using the Network Block Device protocol
First published in XenServer 7.3.
Represents all the fields in a VdiNbdServerInfo
A virtual GPU (vGPU)
First published in XenServer 6.0.
Represents all the fields in a VGPU
A type of virtual GPU
First published in XenServer 6.2 SP1 Tech-Preview.
Represents all the fields in a VGPUType
A virtual network interface
First published in XenServer 4.0.
Represents all the fields in a VIF
The metrics associated with a virtual network device
First published in XenServer 4.0.
Represents all the fields in a VIFMetrics
A VLAN mux/demux
First published in XenServer 4.1.
Represents all the fields in a VLAN
A virtual machine (or 'guest').
Represents all the fields in a VM
VM appliance
First published in XenServer 6.0.
Represents all the fields in a VMAppliance
The metrics reported by the guest (as opposed to inferred from outside)
First published in XenServer 4.0.
Represents all the fields in a VMGuestMetrics
The metrics associated with a VM
First published in XenServer 4.0.
Represents all the fields in a VMMetrics
VM Protection Policy
First published in XenServer 5.6 FP1.
Represents all the fields in a VMPP
VM Snapshot Schedule
First published in XenServer 7.2.
Represents all the fields in a VMSS
A virtual TPM device
First published in .
Represents all the fields in a VTPM
Describes the vusb device
First published in XenServer 7.3.
Represents all the fields in a VUSB