| Local Properties | ||
Managed Object Types | Data Object Types | All Properties | All Methods |
If an alert happens twice (e.g., two network cards were configured, and a ConverterAgentInternalNoNetworkConfiguredDeviceMappingAlert is set), then two instances of ConverterAgentInternalDeviceMappingAlert are returned, one for each alert that was triggered.
Subtypes can easily be added as needed for the localization folks to use. The intent of this hierarchy of subtypes is to support easily localized messages according to the VMACORE model. This is further discussed in ConverterAgentInternalDeviceDroppedDeviceMappingAlert.
Properties
Name | Type | Description |
---|---|---|
alertMessage | xsd:string |
A printable English-language message describing what happened. This is important
for debugging and logging purposes, during development.
For end-users, this is ignored. We use a localized message, which
we handle through VMAcore's localization facilities. These localized messages
are specific to each subtype of DeviceMappingAlert.
|
device* | VirtualDevice |
What device was affected?
|
needsForcing | xsd:boolean |
Set if a CLI would normally require that a -force flag be specified
in order to permit the VM Creation to proceed in the face of this change.
If set, the consequences of this mapping are that the resulting VM
is likely to have problems booting, or is going to undergo a risky reconfiguration
procedure. The conversion from IDE disks (on the Workstation
product) to SCSI ones (on the ESX product) falls into this category. A UI is
encouraged to require some sort of explicit acknowledgement from the user
permitting this kind of change.
|
Properties inherited from DynamicData | ||
None |
Top of page | Local Properties | ||
Managed Object Types | Data Object Types | All Properties | All Methods |