text/microsoft-resx 2.0 System.Resources.ResXResourceReader, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 An activation key can only be applied when the edition is set to 'free'. The specified IP address violates the VIF locking configuration. External authentication for this server is already enabled. External authentication has been disabled with errors: Your AD machine account was not disabled successfully on the AD server. 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. Could not enable external authentication. The server was unable to contact your domain server to enable external authentication. Check that your settings are correct and a route to the server exists. The host failed to enable external authentication. The host failed to enable external authentication. Failed to enable external authentication, permission on the AD server was denied. Failed to enable external authentication, the AD server was unavailable. Failed to enable external authentication, the supplied credentials were invalid. 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. Timeout trying to balloon down memory before VM migration. If the error occurs repeatedly, consider increasing the memory-dynamic-min value. The bootloader for this VM returned an error -- did the VM installation succeed? {1} The specified bridge already exists. Could not find bridge required by VM. This PIF is a bond slave and cannot have a tunnel on it. This PIF is a bond slave and cannot have a VLAN on it. This properties of this PIF cannot be changed. Only the properties of non-bonded physical PIFs, or bond masters can be changed. Cannot forward messages because the server cannot be contacted. The server may be switched off or there may be network connectivity problems. 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 master. The backup partition to stream the update to cannot be found The requested update could not be found. This can occur when you designate a new master. Please upload it again The restore could not be performed because the state partition could not be found The requested update could not be found. Please upload the update again. This can occur when you run xe update-pool-clean before xe update-apply. This PIF is a bond slave and cannot be plugged. This VM cannot be started because its network interfaces could not be connected. One of the NICs is in use elsewhere. The power-state of a control domain cannot be reset. 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. Change password rejected An SR is using clustered local storage. It is not safe to reboot a host at the moment. 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. Table: {0}, Field: {1}, Value: {2} No default SR found The device {0} is already attached to a VM The device {0} is not currently attached There is already a disk at position {0} on the selected VM A timeout happened while attempting to attach a device {1} of type {0} to a VM The VM rejected the attempt to detach the device {1} of type {0}. {2} A timeout happened while attempting to detach a device {1} of type {0} 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 No other server available to nominate as master. Please add or enable some other servers. Some events have been lost from the queue and cannot be retrieved. The event.from token could not be parsed. Valid values include: '', and a value returned from a previous event.from call. The server failed to parse your event subscription. Valid values include: *, class-name, class-name/object-reference. 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. One of the fields you supplied was of the wrong type. The GPU group does not contain any GPUs. The GPU group contains active GPUs and cannot be deleted. The GPU group contains active virtual GPUs and cannot be deleted. Object has been deleted.{0}:{1} This server cannot accept the proposed new master 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. In order to do that, disable HA, create or delete the bond then re-enable HA. This operation cannot be performed because the referenced network is not properly shared. The network must either be entirely virtual or must be physically present via a currently attached PIF on every server. This operation cannot be performed because the referenced SR is not properly shared. The SR must both be marked as shared and a currently attached PBD must exist for each server. 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. Check your network connectivity. 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. 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. Cannot find a plan for placement of VMs as there are no other servers available. This operation cannot be performed because HA would no longer be guaranteed for this pool. To perform this operation anyway, you must disable or reconfigure HA. 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 master's partition) HA can only be enabled for 2 servers or more. Note that 2 servers requires a pre-configured quorum tiebreak script. The hosts in this pool are not compatible. The servers in this pool are not homogeneous. {0} 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). Cannot attach network This server cannot destroy itself. The metrics of this server could not be read. The VM could not start because the CD drive is empty. The specified server is disabled. 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 master. This server can not be forgotten because there are some user VMs still running This server is in emergency mode The backup could not be performed because the server is in recovery mode This operation cannot be completed because the server is in use. This operation cannot be completed because the server is still live. The server that you are talking to is a slave The host is its own slave. Please use pool-emergency-transition-to-master or pool-emergency-reset-master. The master reports that it cannot talk back to the slave on the supplied management IP address. The server name is invalid. This server cannot be enabled as it is not disabled. Not enough server memory is available to perform this operation Not enough free memory The restore could not be performed because the server is not in recovery mode This operation cannot be completed as the server is not live. Unreachable Server could not be contacted This operation cannot be completed because the server power on mode is disabled. The server is still booting. The master says the server is not known to it. Perhaps the server was deleted from the master's database? The specified VBD device is not recognized: please use a non-negative integer This file 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. Cannot import on this server because it was saved on an incompatible version This operation cannot be performed, because it is incompatible with the currently active HA cluster stack. These PIFs can not 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 Internal error: {0} A required parameter contained an invalid CIDR address (<addr>/<prefix length>) The device name {0} is invalid The license type you supplied is invalid. The given feature string is not valid. A required parameter contained an invalid IP address The uploaded update file is invalid The uploaded update file is invalid. The uploaded update package is invalid. The value '{1}' is invalid for field '{0}'. You tried to 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 master 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. Joining server cannot have VMs with any current operations The connection to the joining server failed There was an error connecting to the server. the service contacted didn't reply properly. This operation is not allowed with your current license Cannot downgrade license while in pool. Please disband the pool first, then downgrade licenses on servers separately. The license type 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. Please upgrade to the new licensing system. Host and pool have incompatible licenses. There was an error processing your license. Please contact your support representative The server was unable to contact your domain server. Check your settings are correct and that a route to the server exists. A VDI with the specified location already exists within the SR The MAC address specified doesn't exist on this server. The MAC address specified is not valid. The MAC address specified still exists on this server. INTERNAL ERROR: Attempted to set '{0}'.'{1}':'{3}'='{2}', but the key '{3}' was already present in map '{1}'. The dynamic memory range does not satisfy the following constraint. You have reached the maximum amount of memory allowed for this virtual machine. Maximum amount of memory allowed This message has been deprecated. You tried to call a method that does not exist. The method name that you used is {0}. You tried to call the method {0} with the incorrect number of parameters {2}. The method expect {1} parameter(s). This function is no longer available. The VDI mirroring cannot be performed The license-server connection details (address or port) were missing or incomplete. You tried to create a PIF, but the network {0} you tried to attach it to is already attached to some other PIF {1}, and so the creation failed. The network contains active PIFs ({0}) and cannot be deleted. The network contains active VIFs ({0}) and cannot be deleted. 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 not managed by xapi. This command is not allowed on the OEM edition. The function {0} 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. This operation can only be performed on a registered system domain. There were no servers available to complete the specified operation. The upper limit of active redo log instances was reached. Nvidia tools error. Please ensure that the latest Nvidia tools are installed 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. You attempted an operation that was explicitly blocked (see the blocked_operations field of the given object). The administrator provided the following message: {1}. You attempted an operation that was not allowed. {0} 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 The passthrough_enabled must be true before passthrough usb to vm. The update {0} has already been applied The uploaded update already exists The update failed to apply. View logs for more details. The patch apply failed: backup files were created while applying the patch. Please remove these backup files before applying the patch again. The specified patch is applied and cannot be destroyed. The Tools ISO must be ejected from all running VMs in the pool. The patch precheck stage failed: the server does not have enough space. The update precheck stage failed: prerequisite updates are missing. The update precheck stage failed with an unknown error. The update precheck stage failed: there are one or more VMs still running on the server. All VMs must be shut down or suspended before the update can be applied. The current build number ({1}) is incompatible with the update build number ({2}). The current version number ({1}) is incompatible with the update version number regular expression ({2}). A PBD already exists connecting the SR to the server Caller not allowed to perform this operation. There is insufficient capacity on this GPU to run the virtual GPU. This GPU is currently in use by running VMs. GPU type not compatible with destination group. You cannot create a bond of an interface which is a member of an existing bond. 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. PIF has no network configuration PIF has no IPv6 configuration (mode currently set to 'none') The primary address types are not compatible PIF is the management interface. You tried to destroy the PIF {0}, but it represents an aspect of the physical server configuration, and so cannot be destroyed. You tried to create a VLAN on top of another VLAN - use the underlying physical PIF/bond instead This host has no PIF on the given network. 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. VLAN tag already in use Operation cannot proceed while a VLAN exists on this interface. External authentication is already enabled for at least one server in this pool. External authentication has been disabled with errors: Some AD machine accounts were not disabled successfully on the AD server. 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: Some AD machine accounts were 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. Could not enable external authentication: {1} The server was unable to contact your domain server to enable external authentication. Check that your settings are correct and a route to the server exists. Failed to enable external authentication, a duplicate hostname was detected. Failed to enable external authentication, the supplied account was invalid. The pool failed to enable external authentication. Failed to enable external authentication, permission on the AD server was denied. Failed to enable external authentication, the AD server was unavailable. Failed to enable external authentication, the supplied credentials were invalid. The external authentication configuration of the server joining the pool must match the pool's own external authentication configuration. The host joining the pool must not have any bonds. 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 management NIC must not be on a VLAN or bonded PIF). The host joining the pool must have the same API version as the pool master. The host joining the pool must have the same database schema as the pool master. The server joining the pool must have the same product version as the pool master. 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. Your current role is not authorized to perform this action. Action: {0} Your current role is not authorized to perform this action. Current Role: {0} Authorized Roles: {1} Your current role is not authorized to perform this action on {2}. Current Role: {0} Authorized Roles: {1} The operation could not be performed because a redo log is enabled on the Pool. Cannot restore on this server because it was saved on an incompatible version The restore could not be performed because the restore script failed. Your backup file may be corrupt. See the logs for more information. The restore could not be performed because the server's current management interface is not in the backup. The interfaces mentioned in the backup are: The restore could not be performed because a network interface is missing Role already exists. Role cannot be found. Could not authenticate session. Check your access credentials and try again. The connection to the server has been lost. This session {0} is not registered to receive events. You must call event.register before event.next. The session handle you are using is echoed. The management interface on a slave cannot be disabled because the slave would enter emergency mode. The SM plugin did not respond to a query. Attaching this SR failed. The SR failed to complete the operation Invalid argument Cannot find volume The request is missing the server path parameter The request is missing the server parameter The server path argument is not valid Unable to open the refcount file Root system device, cannot be used for VM storage The IQN provided is an invalid format The SCSIid parameter is missing or incorrect Unable to detect an NFS service on this target. The snapshot chain is too long VDI resize failed SMB mount error SMB unmount error SMB mount point already attached Failed to remove SMB mount point Not all required parameters specified. Failed to create SMB SR. Netapp Target parameter missing in Dconf string SM has thrown a generic python exception Netapp Username parameter missing in Dconf string Netapp Password parameter missing in Dconf string Netapp Aggregate parameter missing in Dconf string Failed to connect to Netapp target Authentication credentials incorrect Auth credentials have insufficient access privileges Max number of flexvols reached on target. Unable to allocate requested resource. Max number of Snapshots reached on target Volume. Unable to create snapshot. Insufficient space, unable to create snapshot. Netapp Target version unsupported Unable to retrieve target IQN iSCSI service not running on the Netapp target. Failed to enable A-SIS for the SR. Requires valid license on the filer. The filer will not support A-SIS on this aggregate. The license is valid however on some filers A-SIS is limited to smaller aggregates, e.g. FAS3020 max supported aggregate is 1TB. See filer support documentation for details on your model. You must either disable A-SIS support, or re-configure your aggregate to the max supported size. Failed to acquire an exclusive lock on the LUN. DNS lookup failed: the given servername could not be resolved. Unable to connect to iSCSI service on target Incorrect value for iSCSI port, must be a number between 1 and 65535 Failed to parse the request VDI could not be found Failed to initialize XMLRPC connection Failed to query Local Control Domain A Failure occurred querying the PBD entries A Failure occurred accessing an API object The specified storage repository is currently in use Equallogic Target parameter missing in Dconf string Equallogic Username parameter missing in Dconf string Equallogic Password parameter missing in Dconf string Equallogic StoragePool parameter missing in Dconf string Failed to connect to Equallogic Array; maximum SSH CLI sessions reached Invalid snap-reserver-percentage value, must be an integer indicating the amount of space, as a percentage of the VDI size, to reserve for snapshots. Invalid snap-depletion value, must be one of 'delete-oldest' or 'volume-offline' Volume out of space, probably due to insufficient snapshot reserve allocation. Cannot create Snapshot of a Snapshot VDI, operation unsupported Failed to connect to Equallogic Array. Check your user name and password. Equallogic Target version unsupported Unable to logon to Array. Check IP settings. Equallogic StoragePool parameter specified in Dconf string is Invalid Equallogic Target parameter specified in Dconf string is Invalid, please specify the correct Group IPaddress Invalid SNMP response received for a CLI command Volume metadata stored in the 'Description' field is invalid, this field contains encoded data and is not user editable Invalid EOF response received for a CLI command Volume Group out of space. The SR is over-provisioned, and out of space. Unable to grow the underlying volume to accommodate the virtual size of the disk. Error in Metadata volume operation for SR. No such device A bad character was detected in the dconf string No such secret. General IO error Currently unavailable, try again General backend error An active FIST point was reached that causes the process to exit abnormally The device configuration request is missing the Location parameter ISO name must have .iso extension Unable to mount the directory specified in device configuration request Unable to unmount the directory specified in device configuration request Could not locate the ISO sharename on the target, or the access permissions may be incorrect. Incorrect Location string format. String must be in the format SERVER:PATH for NFS targets, or \\SERVER\PATH for CIFS targets Invalid local path Given SMB version is not allowed. Choose either 1.0 or 3.0 Require "-o" along with xe-mount-isosr The specified VDI is currently in use The request to lock/unlock the storage repository or VDI failed The method you have requested is not currently supported The specified storage repository contains data The specified storage repository scan failed The target server name or IP address is missing The Storage System ID is missing The Storage Pool ID is missing The storage repository log operation failed The gssi operation to the CSLG server failed The SR loading operation failed An invalid storage protocol was specified Unable to parse XML Failed to probe SR Snapshot/Clone failed Storage assignment failed Storage un-assignment failed Storage allocation failed The specified storage repository already exists Storage deallocation failed HBA Query failed IQN/iSCSI initialization failed SCSI device scan failed Failed to connect to target: please check the hostname or IP address The Storage Node ID is missing The VDI failed to be introduced to the database The CSLG software doesn't seem to be installed Failed to create multiple sub-pools from parent pool Current XML definition is newer version The specified VDI already exists Failed to communicate with the multipath daemon Error in storage adapter communication The adapter id is missing The user name is missing The password is missing An invalid storage system ID was specified Failed to collect storage system information Failed to collect storage pool information Failed to delete storage pool Failed to collect storage volume information The specified storage repository has insufficient space Failed to list storage volume Failed to resize storage volume Failed to list storage target ports Failed to list storage pool The tapdisk failed The tapdisk is already running Extended characters are not supported in SMB paths, user names, and passwords. Illegal XML character. Unsupported kernel: neither 2.6 nor 3.x. Only 1 LUN may be used with shared OCFS OCFS mount error OCFS unmount error OCFS filesystem creation error tapdisk experienced an error SMB SR is not licensed on this host VG Registration failure Unable to attach empty optical drive to VM. Unable to activate changed block tracking. Unable to deactivate changed block tracking. Changed block tracking log is in an inconsistent state. The VDI is not available Failed to calculate changed blocks for given VDIs. The storage repository is not available The storage repository you are attempting to access is an unknown type The xml string is malformed There was an error while attempting to create the specified logical volume There was an error while attempting to delete the specified logical volume Logical Volume mount/activate error The attempt to umount/deactivate the specified logical volume failed There was an error while attempting to write to the specified logical volume There was an error while attempting to create a partition on the specified logical volume The partition on the logical volume is currently in use There was an error while attempting to create the filesystem on the specified logical volume There was an error while attempting to make a request from the logical volume. The request must come from the master. The attempt to resize the logical volume failed The size specified for the logical volume is invalid. There was an error while attempting create the file storage repository There was an error while attempting to remove the directory on the file storage repository. There was an error while attempting to delete the file storage repository The attempt to remove the VDI failed The attempt to load the VDI failed The VDI type is invalid Unable to add the iSCSI device Logging in to the iSCSI target failed. Check your user name and password. Logging out of the iSCSI target failed Unable to set the iSCSI initiator The iSCSI daemon failed to start The NFS server version is unsupported There was an error while attempting to mount the NFS share There was an error while attempting to unmount the NFS share The NFS share has already been added The attempt to remove the NFS share failed The attempt to create a logical volume group failed The attempt to create a VDI failed The size specified for the VDI is invalid The attempt to mark the VDI as hidden failed The attempt to clone the VDI failed The attempt to snapshot the VDI failed The attempt to discover the iSCSI target/device failed The iScsi target and received IQNs do not match The attempt to detach the iSCSI failed The attempt to query the iSCSi daemon failed Either LUNid or LUNserial value must be provided There was an error while attempting to create the NFS storage repository The request is missing the LUNid parameter The request is missing the device parameter The device is not a valid path The volume cannot be found The pvs utility returns an error The request is missing the location parameter The request is missing the target parameter The request is missing the target IQN parameter The request is missing the server configuration iSCSI IQN parameter The request is missing the LUN serial number Only 1 LUN may be used with shared LVM The SR operation cannot be performed because a device underlying the SR is in use by the server. You attempted to migrate a VDI to or from an SR that doesn't support migration The SR is full. Requested size {0} exceeds the maximum size {1} 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 {0} is still connected to a server by a PBD. It cannot be destroyed. 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. SR is not sharable This SR does not support this operation The operation cannot be performed until the SR has been upgraded The SR could not be connected because the driver {0} was not recognized. 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 You must use tar output to retrieve system status from an OEM server. Retrieving system status from the server failed. The request was asynchronously cancelled. 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 {1} for VM {0} 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. View logs for more details. The specified update has been applied and cannot be destroyed. The update cannot be applied for the following host(s). The update precheck stage failed: conflicting update(s) are present. The update precheck stage failed: RPM package validation requires a GPG key that is not present on the host. The update precheck stage failed: the server does not have enough space. The update precheck stage failed: prerequisite update(s) are missing. The update precheck stage failed with an unknown error. The update precheck stage failed: the server is of an incorrect version. 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 value {1} for field {0} that is not supported. {2} You have reached the maximum number of virtual disks allowed for this virtual machine. Maximum number of virtual disks allowed Read/write CDs are not supported VBD {0} - Operation could not be performed because the drive is empty VBD {0} - Operation could not be performed because the drive is not empty VBD {0} - 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 You have reached the maximum number of virtual CPUs allowed for this virtual machine. Maximum number of virtual CPUs allowed 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 virtual disk is of an incompatible type (e.g., an HA statefile cannot be attached to a VM) This operation cannot be performed because a VDI is in use by some other operation. The operation cannot be performed on physical device This operation can only be performed on CD VDIs (iso files or CDROM drives). VDI {0} is of type {1}. This operation cannot be performed because the specified virtual disk could not be found in the specified SR This operation cannot be performed because the specified virtual disk could not be found You attempted to migrate a VDI which is not attached to a running VM. This operation cannot be performed because VDI {0} 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. It is not possible to query and manipulate only the changed blocks (or 'block differences' or 'disk deltas') between two VDIs. Please select a VDI which uses a sparse-aware technology such as VHD. The requested operation is not allowed because the specified VDI does not have changed block tracking metadata. 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 VDI {0} is read-only The VDI is too small. Please resize it to at least the minimum size. The VGPU is not compatible with any PGPU in the destination. The VM cannot start because all GPUs are fully used or are running other types of virtual GPU Virtual GPU type is not one of the GPU's enabled types. Virtual GPU type is not one of the GPU's supported types. You have reached the maximum number of virtual network interfaces allowed for this virtual machine. Maximum number of virtual network interfaces allowed Network has active VIFs This VIF was not mapped to a destination network Operation cannot be performed because this VLAN is already in use. Please check your network configuration. You tried to create a VLAN, but the tag you gave ({0}) was invalid -- it must be between 0 and 4094. Archive more frequent than backup. There is at least on VM assigned to this protection policy. There is at least one VM assigned to snapshot schedule. The given VMs failed to release memory when instructed to do so 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 needed it to be in state '{1}' but was in state '{2}'. The BIOS strings for this VM have already been set and cannot be changed. There is a minimal interval required between consecutive plugin calls made on the same VM, please wait before retry. You cannot delete the specified default template. An error occurred while restoring the memory image of the specified virtual machine An error occurred 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 shut down. The VM unexpectedly halted You attempted to 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. You attempted to 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. You attempted to migrate a VM to a destination host which is older than the source host. The VM's Virtual Hardware Platform version is incompatible with this host. HVM is required for this operation HVM not supported The host does not have some of the CPU features that the VM is currently using The VM is configured in a way that prevents it from being mobile. The VM cannot be recovered on its own as it is part of a VM appliance. This operation cannot be performed because the specified VM is protected by HA The operation attempted is not valid for templates This operation is illegal because the VM is using nested virtualisation. 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. VM migration failed: {3} You attempted an operation on a VM which requires PV drivers to be installed but the drivers were not detected. The specified VM is not currently resident on the specified server. This VM does not have a crashdump SR specified. The VM has no empty CD drive (VBD). This VM does not have a suspend SR specified. 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. Please upgrade your PV drivers. VM PV drivers still in use The VM unexpectedly rebooted You attempted to run a VM on a host which doesn't have a GPU available in the GPU group needed by the VM. The VM has a virtual GPU attached to this GPU group. GPU not available 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. This VM needs a network that cannot be seen from that server Cannot see required network This VM needs storage that cannot be seen from that server Cannot see required storage VM cannot be started because it requires a VDI which cannot be attached The VM cannot start because no GPU is available 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 occurred while reverting the specified virtual machine to the specified snapshot The shutdown of this VM timed out 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 Too many VCPUs to start this VM The VM cannot be imported unforced because it is either the same version or an older version of an existing VM. You attempted an operation on VM {0} that was judged to be unsafe by the server. This can happen if the VM would run on a CPU that has a potentially incompatible set of feature flags to those the VM requires. If you want to override this warning then use the 'force' option. 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. The WLB server 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. Ensure it is in format: <ipaddress>:<port>. The configured/given URL is returned. 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 The requested plugin could not be found. There was a failure communicating with the plugin. 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 An error occurred while performing the XMLRPC request. The server failed to unmarshal the XMLRPC message; it was expecting one element and received something else.