VMware

Validation Test Matrix

Goals:

  • Ensure compliance with virtual appliance best practices
  • Ensure compatibility across VMware product line
  • Ensure ease-of-use for initial customer experience with appliance
Test Matrix Legend:
must match Interpret base requirement exactly as written
must not match Interpret base requirement exactly the opposite as written (MUST vs. MUST NOT, SHOULD vs. SHOULD NOT)
not applicable This test case is not applicable to this target

Test Cases which have been modified or added since VMR 1.0 rev. 2008.09.15 are marked in bold. Test Case numbering is broken down into major categories (Test Case Series). Individual test case numbers (such as Test Case 0152 through Test Case 0158) may currently be skipped in order to be available for expansion of the test matrix in a future revision.

Test Matrix:

Test Case Series 01xx [Platforms]
TC
ID 		TC Title TC Summary Hv.
Class 		OVA OVF Only
0109 Indirect Satisfaction of Criteria Platform criteria as described in Test Cases 0110 through 0139. not applicable must match must match
0110 Required platform targets. The following platforms MUST be targeted:

Hypervisor vHW 6 -- ESXi 4.x+;
Hypervisor vHW 6 -- ESX 4.x+;		 must match must match must match
0130 Highly-portable platform targets. For additional portability options, the following platforms MAY be targeted:

OVF Revision 0.9, 1.0, 1.1
not applicable must match must match
Test Case Series 05xx [Packaging]
TC
ID 		TC Title TC Summary Hv.
Class 		OVA OVF Only
0505 No Extraneous Files. The virtual appliance archive SHOULD NOT contain extraneous files. An example of such files would be vmware.log (or equivalent) outputs. must match not applicable must match
0510 Packaging Complexity. The use of multiple archives to encapsulate a single virtual appliance may be confusing to the end user. If multiple archives are used, extraction expectations MUST be included to explain that the net result is a single directory with the contents of all archives in it (net-count ~"N" files). Some archive extraction tools may balk at performing an overlay-extraction, the Microsoft Windows XP built-in "Extraction Wizard" being a good example when handling .ZIP archives. must match not applicable must match
0511 Packaging with .tar (Tape ARchive). Use of the .tar archive format for packaging MAY be implemented at the vendor's discretion, and so-stipulated in the Documentation (see Test Cases 1001 through 1099). Note that certain limitations exist in the in the .tar archive format regarding original file sizes. must match not applicable must match
0512 Packaging with .tar.gz/.tgz (Tape ARchive GZipped). Use of the .tar.gz/.tgz archive and compression format for packaging MAY be implemented at the vendor's discretion, and so-stipulated in the Documentation (see Test Cases 1001 through 1099). Note that certain limitations exist in the in the .tar archive format regarding original file sizes. must match not applicable must match
0513 Packaging with .tar.bz2/.tbz2 (Tape ARchive BZip2ed). Use of the .tar.bz2/.tbz2 archive and compression format for packaging MAY be implemented at the vendor's discretion, and so-stipulated in the Documentation (see Test Cases 1001 through 1099). Note that certain limitations exist in the in the .tar archive format regarding original file sizes. must match not applicable must match
0514 Packaging with .tar.7z/.t7z (Tape ARchive 7Zipped). Use of the .tar.7z/.t7z archive and compression format for packaging MAY be implemented at the vendor's discretion, and so-stipulated in the Documentation (see Test Cases 1001 through 1099). Note that certain limitations exist in the in the .tar archive format regarding original file sizes. must match not applicable must match
0515 Packaging with .zip (Zipped). Use of the .zip archive and compression format for packaging MAY be implemented at the vendor's discretion, and so-stipulated in the Documentation (see Test Cases 1001 through 1099). must match not applicable must match
0520 Message Digest Hashes for Integrity Validation. In order to allow for integrity validation of archives, message digesting algorithms such as MD5 and SHA1 SHOULD be used. must match not applicable must match
Test Case Series 06xx [OVF Packaging]
TC
ID 		TC Title TC Summary Hv.
Class 		OVA OVF Only
0610 Delivery Formats At least one primary delivery format MUST be implemented from Test Cases 0611 through 0614. not applicable must match must match
0611 Offline Package The virtual appliance MAY be delivered as an offline package, whereby all OVF objects are local to the client performing an import operation. not applicable must match must match
0612 Online Streaming The virtual appliance MAY be delivered as an online package, whereby all OVF objects are served via HTTP to the client performing an import operation. not applicable must match must match
0615 Single-VM OVF The virtual appliance MUST be delivered as a single-VM OVF bundle (folder or directory of files). not applicable must match must match
0616 Multi-VM OVF The virtual appliance MUST NOT be delivered as a multi-VM OVF bundle. not applicable must match must match
0618 Manifest File A manifest file (.mf file) MAY be delivered as part of the virtual appliance. not applicable not applicable must match
0620 Product Compatibility -- General. Due to the evolutionary nature of draft standards, compatibility with existing products on the market MUST take precedence over strict adherence to the specification as finally published (DMTF OVF Specification -- DSP0243 revision 1.0.0e). Therefore, certain features or functionality present in the final specification may be excluded. not applicable must match must match
0621 Product Compatibility -- Export The specific method in which the OVF bundle is created is not prescribed. not applicable must match must match
0623 Product Compatibility -- Import Unless otherwise stipulated in the Documentation (see Test Cases 1001 through 1099), Hypervisor platforms MUST be supported as run-time targets. The specifics of OVF Import are covered in Test Cases 8801 through 8899 as constrained by the following: 
  
  Required and evaluated paths:

  Single-VM OVF to...

  VI Client 4.x+ to ESX/ESXi 4.x+


  Optional non-evaluated paths:

  Single-VM OVF to...
  
    VMware Converter 4.x+ to ESX/ESXi 4.x+

    VMware Converter 4.x+

    VMware OVF Tool 2.x:

    VMware Workstation 6.5.0+
not applicable must match must match
0625 Schema Compliance. At this time, validation-by, and compliance-with a specific final OVF Schema version (such as DMTF OVF Envelope and Environment Schemas -- DSP8023 rev. 1.0.0e and DSP8027 rev. 1.0.0e respectively) is NOT REQUIRED. not applicable must match must match
0630 OVF Descriptor Content Elements Pursuant to Test Case 0620, the presence or omission of specific elements within the Content section of the OVF descriptor file MUST match those described in Test Cases 0631 through 0639. The EULA element MUST be present in the OVF descriptor file and MUST display properly. not applicable must match must match
0631 EULA Element The EULA element MUST be present in the OVF descriptor file and MUST display properly. 
The EULA typically occurs as the
last Section element at:

Envelope
  ..References/
  ..Section/
  .
  .
  .
  ..Content
      ..Info/
      ..Section/
      ..Section/
      .
      .
      .
      ..Section  (ovf:EulaSection_Type)
          ..Info/
          ..License/
      ../Section
  ../Content
/Envelope
not applicable not applicable must match
0632 Annotation Element The annotation element MUST be present in the OVF descriptor file and MUST display properly. 
The Annotation typically occurs as the
first Section element at:

Envelope
  ..References/
  ..Section/
  .
  .
  .
  ..Content
      ..Info/
      ..Section  (ovf:AnnotationSection_Type)
          ..Info/
          ..Annotation/
      ../Section
      ..Section/
      ..Section/
      .
      .
      .
  ../Content
/Envelope
not applicable not applicable must match
0633 Operating System Element The operating system element MUST be present in the OVF descriptor file and MUST display properly. not applicable not applicable must match
0634 Virtual Hardware Element The virtual hardware element MUST be present in the OVF descriptor file and MUST display properly. not applicable not applicable must match
0638 Product Element The Product element MAY be present in the OVF descriptor file. 
The Product typically occurs as the
second-to-last Section element at:

Envelope
  ..References/
  ..Section/
  .
  .
  .
  ..Content
      ..Info/
      ..Section/
      ..Section/
      .
      .
      .
      ..Section  (ovf:ProductSection_Type)
          ..Info/
          ..Product/
          ..Vendor/
          ..Version/
          ..Full-version/
          ..ProductUrl/
          ..VendorUrl/
      ../Section
      ..Section/  (ovf:EulaSection_Type)
  ../Content
/Envelope
not applicable not applicable must match
0639 Extended Elements Not Otherwise Specified Extended elements not otherwise specified MUST NOT be present in the OVF descriptor file Content section. not applicable not applicable must match
Test Case Series 10xx [Documentation]
TC
ID 		TC Title TC Summary Hv.
Class 		OVA OVF Only
1001 Availability of Documentation. Documentation MUST be available as Part of the Virtual Appliance. must match must match must match
1002 Cursory Overview. A Cursory Overview SHOULD be available for review by a potential customer prior to acquisition of the appliance. This SHOULD be limited to one (1) page or less, and SHOULD include a mix of non-technical (deployment scenarios) and technical (time and resource estimates) information. must match must match must match
1003 Getting Started Guide. A Getting Started Guide MUST be available as Part of the Virtual Appliance. This document SHOULD be limited to ten (10) pages or less, and SHOULD include: Installation Procedures, Pre-Boot Configuration Procedures, and First-Boot Configuration Procedures. must match must match must match
1011 Delivery Formats. Documentation MUST be delivered in a portable and user-friendly format. Primary format options: Plaintext (.txt) -- UTF-8(?);Adobe Acrobat Portable Document Format (.pdf) -- Minimum Version(?) and Maximum Version(?);Offline XHTML or HTML (.html) -- XHTML 1.0 Transitional recommended;Online XHTML or HTML (.html) -- XHTML 1.0 Transitional recommended; Other secondary format options (RTF, LaTeX, compiled MS Help, ...) must match must match must match
1020 General Content Requirements. At this time, core documentation MUST be delivered in English. Any variance to this policy MUST be made through written arrangement. must match must match must match
1021 Editing and Proofreading. Documentation MUST be free of major editing and proofreading (spelling, grammar, punctuation) issues. must match must match must match
1031 Accuracy of Procedures. All procedural information MUST be correct. must match must match must match
1041 Branding and Terminology. All documentation MUST communicate coherent branding to the end customer. It is understood that companies and/or products undergo periodic name changes. The intent of this requirement is that such naming be consistent, either always reflecting the "new" name, or always reflecting the "old" name. must match must match must match
1051 Branding and Terminology (VMware and third party). All documentation MUST include accurate branding and terminology for both VMware and third-parties. It is understood that part of maintaining brand identity is ensuring consistent use of that brand, which includes requiring that the full name and proper capitalization/punctuation be used in references. must match must match must match
1052 Branding and Terminology (VMware and third party). All documentation MUST include registered trademark / trademark / service mark / trade dress disclaimer. Boilerplate verbiage such as the following used by VMware will suffice: All other marks and names mentioned herein may be trademarks of their respective companies. must match must match must match
1061 Resource Requirements and Prerequisites. Documentation MUST include an accurate listing of resource requirements and other prerequisites (CPU/RAM/Disk/Network) for deployment of the virtual appliance. must match must match must match
1062 External Resource Requirements and Prerequisites. Documentation MUST include an accurate listing of external resource requirements and other prerequisites for deployment of the virtual appliance, including but not limited to: A description of each virtual network interface so that mappings to the appropriate virtual switch(es) are made during deployment.;A description of other virtual appliances this virtual appliance is dependent on.;A description of other virtual appliances dependent on this virtual appliance.;A description of services (rDNS, DNS, DHCP, NAT/PAT, NTP, etc...) this virtual appliance is dependent on.;A description of static network configuration data this virtual appliance is dependent on.; must match must match must match
1063 External Resource References. Documentation SHOULD encourage the use of fully qualified hostnames rather than non-qualified "short" hostnames when accessing network resources. Use of "short" hostnames makes a potentially incorrect assumption regarding the local client's DNS stub-resolver configuration, specifically the domain-search list and other auto-completion behavior for non-qualified hostnames. must match must match must match
1064 Access and Authentication Information. Access and authentication information MUST be available as Part of the Virtual Appliance. must match must match must match
1065 Performance Expectations. Documentation SHOULD include some description of performance expectations contrasted to resource requirements, such as: Does adding more RAM help the VA?;Does adding a second vCPU help the VA?;Does adding additional spindles to the logical disk backing the VMFS3 volume help the VA?;Is there a minimum sustained storage IOPS rate required from the logical disk?; must match must match must match
Test Case Series 25xx [Virtual Resources]
TC
ID 		TC Title TC Summary Hv.
Class 		OVA OVF Only
2501 Virtual Resources -- Prohibitions. The use of the following resources are explicitly prohibited at this time: Virtual Disk, IDE Sub-Type -- MUST NOT be present; must match must match must match
2502 Virtual Resources -- Restrictions. The use of the following resources are strongly discouraged at this time, and should be removed unless explicitly necessary:

Virtual USB, USB 1.1 (original UHCI) Sub-Type -- SHOULD NOT be present;

Virtual USB, USB 2.0 (EHCI) Sub-Type -- SHOULD NOT be present;

Virtual Legacy Device, Floppy Sub-Type -- SHOULD NOT be present;

Virtual Legacy Device, IDE CD-ROM Sub-Type -- SHOULD NOT be present;

Virtual Legacy Device, Serial Port Sub-Type -- SHOULD NOT be present;

Virtual Legacy Device, Parallel Port Sub-Type -- SHOULD NOT be present;

Virtual Sound, Legacy SB16 Sub-Type -- SHOULD NOT be present;

Virtual Sound, ES1371 Sub-Type -- SHOULD NOT be present; 		must match must match must match
2508 Virtual Resources -- Configuration File Generation. Unless otherwise stipulated in the Documentation (see Test Cases 1001 through 1099), a valid configuration file generation number MUST be used if supplied. The specific set of valid values for this number is determined by the targeted platform class and generation. must match must match must match
2509 Virtual Resources -- Platform Generation. The migration to newer virtual hardware (vHW) versions is strongly encouraged by VMware, however early adoption may limit the target platforms available to the virtual appliance. For broadest applicability and unless otherwise stipulated in the Documentation (see Test Cases 1001 through 1099), a virtual hardware (vHW) version of vHW 4 (four) SHOULD be used.

In addition, unless otherwise stipulated in the Documentation (see Test Cases 1001 through 1099), a virtual hardware (vHW) version earlier than vHW 6 MUST NOT be present and/or required for proper operation of the virtual appliance.		 must match must match must match
2510 Virtual CPU -- General. By nature, VMware vPlatform products perform virtualization of the Intel IA-32 (aka 'x86') PC architecture, including "64 bit extensions" (aka 'x86_64'). This means that a large percentage of the OpCodes (instructions at the 'assembly' level) submitted by the Guest OS to the virtual CPU are run without modification directly on the physical CPU (aka direct execution, or 'DirectExec'). We only fully-emulate or perform binary-translation on those specific OpCodes or series of OpCodes which would present an inherent virtualization risk if run in direct execution mode. The virtual appliance MUST NOT require other hardware architectures (such as SPARC/uSPARC, PA-RISC, IA-64/Itanium, ARM, MIPS) for proper operation. This restriction does not apply to any virtualization services supplied by the Guest OS or Application layers within the virtual appliance. must match must match must match
2511 Virtual CPU -- More than Zero vCPUs. At least one vCPU MUST be present and/or required for proper operation of the virtual appliance. -- Yes, this seems logically redundant, but may be useful for machine-processing of this specification. must match must match must match
2515 Virtual CPU -- AMD NX (No-Execute) / Intel xD (Execute-Disable) Bit. Unless otherwise stipulated in the Documentation (see Test Cases 1001 through 1099), hardware support (pCPU level) for the AMD NX and/or Intel xD bit MUST NOT be required for proper operation of the virtual appliance. must match must match not applicable
2519 Virtual CPU -- Features Not Otherwise Specified. Unless otherwise stipulated in the Documentation (see Test Cases 1001 through 1099), hardware support (pCPU level) for specialty features MUST NOT be present and/or required for proper operation of the virtual appliance. -- CPUID spoofing, etc... must match must match not applicable
2520 Virtual RAM -- General. Allocated virtual RAM MUST be a multiple of 4 MB. must match must match must match
2521 Virtual RAM -- Minimum. Allocated virtual RAM MUST be a minimum of 32 MB. must match must match must match
2522 Virtual RAM -- 3.5 GB Limit. Unless otherwise stipulated in the Documentation (see Test Cases 1001 through 1099), allocated virtual RAM MUST NOT exceed 3600 MB. Note that for certain platform targets this is a hard limit, in which case allocated virtual RAM MUST NOT exceed 3600 MB. must match must match must match
2523 Virtual RAM -- 8 GB Limit. Unless otherwise stipulated in the Documentation (see Test Cases 1001 through 1099), allocated virtual RAM MUST NOT exceed 8192 MB. must match must match must match
2524 Virtual RAM -- 16 GB Limit. Unless otherwise stipulated in the Documentation (see Test Cases 1001 through 1099), allocated virtual RAM MUST NOT exceed 16384 MB. must match must match must match
2529 Virtual RAM -- Maximum Limit. Allocated virtual RAM MUST NOT exceed 65536 MB. must match must match must match
2530 Virtual Storage Controller -- General. Unless otherwise necessary, the LSI Logic virtual SCSI controller SHOULD be favored over the BusLogic virtual SCSI controller. must match must match must match
2540 Virtual Disk -- General. Unless otherwise stipulated in the Documentation (see Test Cases 1001 through 1099), all requisite virtual disks MUST be present for proper operation of the virtual appliance. must match must match must match
2541 Virtual Disk -- Types. All virtual disks MUST be SCSI. must match must match must match
2542 Virtual Disk -- Backing Types -- Plain. All virtual disks included as Part of the Virtual Appliance MUST be backed by plain virtual disks. must match must match must match
2543 Virtual Disk -- Backing Types -- Other. Unless otherwise stipulated in the Documentation (see Test Cases 1001 through 1099), all virtual disks MUST be backed by plain virtual disks. Other backing types (raw LUN, RDM, physical disk passthrough, etc...) require explicit documentation. must match must match must match
2550 Virtual Networking Controller -- General. Where possible, the vmxnet virtual NIC SHOULD be used. Certain guests may require the use of the e1000 virtual NIC or vlance virtual NIC. must match must match must match
2555 Virtual Debugging -- General. Unless otherwise stipulated in the Documentation (see Test Cases 1001 through 1099), debugging services including the debug mode VMX and related options MUST NOT be enabled and/or required for proper operation of the virtual appliance. must match must match must match
2556 Virtual Debugging -- Record and Replay Facility. Unless otherwise stipulated in the Documentation (see Test Cases 1001 through 1099), the virtual hardware level record and replay facility MUST NOT be enabled and/or required for proper operation of the virtual appliance. must match must match must match
2557 Virtual Debugging -- VMDebug and DebugStub. Unless otherwise stipulated in the Documentation (see Test Cases 1001 through 1099), the virtual hardware level debugger passthrough integration MUST NOT be enabled and/or required for proper operation of the virtual appliance. must match must match must match
2570 VMware Tools -- General. The core set of Guest OS side functionality components known as "VMware Tools" MUST be present, enabled, and operating properly. Information further defining this requirement is covered in test cases 2571 through 2579. The precise VMware Tools ABI version and build number to be used are not prescribed. must match must match must match
2571 VMware Tools -- Host-Guest Communications. The subset of Guest OS side functionality components known as the "guest daemon" MUST be present, enabled, and operating properly. must match must match must match
2572 VMware Tools -- Guest to Host Log Channel. Unless otherwise stipulated in the Documentation (see Test Cases 1001 through 1099), the subset of Guest OS side functionality components known as the "guest to host log channel" MUST be present, enabled, and operating properly. must match must match must match
2573 VMware Tools -- Memory Balloon Driver. Unless otherwise stipulated in the Documentation (see Test Cases 1001 through 1099), the subset of Guest OS side functionality components known as the "memory balloon driver" (vmmemctl) MUST be present, enabled, and operating properly. must match must match must match
2574 VMware Tools -- Host-Guest Filesystem. Unless otherwise stipulated in the Documentation (see Test Cases 1001 through 1099), the subset of Guest OS side functionality components known as "Host-Guest Filesystem" (vmhgfs) MUST NOT be implemented. [[Only change: Title of Test Case]] must match must match must match
2575 VMware Tools -- Soft-Power Operations. Unless otherwise stipulated in the Documentation (see Test Cases 1001 through 1099), the subset of Guest OS side functionality components known as "Soft-Power Operations" SHOULD be implemented; More specifically, those for power-off and reset operations where Guest OS filesystem consistency is most at risk. must match must match must match
2576 VMware Tools -- Host-Guest Timesync. Unless otherwise stipulated in the Documentation (see Test Cases 1001 through 1099), the subset of Guest OS side functionality components known as "Host-Guest Timesync" --or-- equivalent guest time synchronization functionality SHOULD be implemented. A white paper covering timekeeping in VMware virtual machines is available in PDF at http://www.vmware.com/pdf/vmware_timekeeping.pdf must match must match must match
2579 VMware Tools -- Not Otherwise Specified. The subset of Guest OS side functionality components other than those described elsewhere MAY be implemented at the vendor's discretion, and so-stipulated in the Documentation (see Test Cases 1001 through 1099). must match must match must match
2580 Virtual Legacy Devices -- General. Unless otherwise stipulated in the Documentation (see Test Cases 1001 through 1099), virtual legacy devices MUST NOT be present and/or required for proper operation of the virtual appliance. must match must match must match
2589 Virtual Resource -- Not Otherwise Specified. Unless otherwise stipulated in the Documentation (see Test Cases 1001 through 1099), resources other than those described elsewhere MUST NOT be present and/or required for proper operation of the virtual appliance. must match must match must match
Test Case Series 30xx [VMware .vmx File]
TC
ID 		TC Title TC Summary Hv.
Class 		OVA OVF Only
3001 Annotation option in .vmx file. The annotation option SHOULD be set in the .vmx file, this option shows up as a free-form single-line wrapped text field in some but not all user interfaces, typically as "Notes" in the bottom-left corner of the UI. Typically it is set as a more verbose version of the displayName option, including for example the company's URL. Annotation values can span up to a paragraph or so, but must be stored in the .vmx file as a single "long" line of text. must match not applicable not applicable
3008 Versioning Data -- Configuration File Generation. A valid configuration file generation number MUST be present.

config.version = "...."

Refer to Test Case 2508 for further information. 		must match not applicable not applicable
3009 Versioning Data -- Platform Generation. A valid virtual hardware version number MUST be present.

virtualHW.version = "...."

Refer to Test Case 2509 for further information. 		must match not applicable not applicable
3020 Identification Data -- General. Unique identification data within the .vmx file SHOULD be limited to that which is required for proper operation, as described in Test Cases 3021 through 3029. must match not applicable not applicable
3021 Identification Data -- UUID. A universally unique identifier is maintained for each virtual appliance running on VMware vPlatform products. Unless explicitly necessary pursuant to Test Case 3020, this data SHOULD NOT be present in the .vmx file. The universally unique identifier data, if not already present, is initially calculated based on the current location of the .vmx file during the first operation requiring this information, typically a registration or power-on event.

uuid.bios = "...."
Contains to the UUID as seen by the Guest OS.

uuid.location = "...."
Contains to the UUID as calculated based on the current location of the .vmx file. 		must match not applicable not applicable
3022 Identification Data -- UUID Preservation. Should the .vmx file be relocated subsequent to the initial universally unique identifier calculation, the uuid.location value will change. Based on the absence/presence and value of the uuid.action entry in the .vmx file, the end user may be asked whether the data as seen by the Guest OS should change or remain the same. The uuid.action value SHOULD be set to either "keep" (if the virtual appliance depends on the UUID and MAC data remaining constant) or "create" (if the virtual appliance does not depend on the UUID and MAC data remaining constant) in order to minimize end user confusion.

uuid.action = "...." 		must match not applicable not applicable
3023 Identification Data -- MAC Information. A portion of the universally unique identifier as seen by the Guest OS is used for dynamic generation of ethernet MAC information. Unless explicitly necessary pursuant to Test Case 3020, statically assigned ethernet MACs SHOULD NOT be used, and this data (dynamic or static) SHOULD NOT be present in the .vmx file.

ethernet#.addressType = "...."
ethernet#.address = "...."
ethernet#.generatedAddress = "...."
ethernet#.generatedAddressOffset = "...." 		must match not applicable not applicable
3028 Identification Data -- Display Name. A reasonably descriptive display name SHOULD be used, however this originally supplied value may vary based on the individual environment in which this virtual appliance is deployed.

displayName = "...." 		must match not applicable not applicable
3050 File Paths -- General. File paths MUST be local (bar.baz), and not relative (../foo/bar.baz) or absolute (/foo/bar.baz). Automatically updated file path values (such as those for virtualization-host CDROM drives) are excluded from this requirement. must match not applicable not applicable
3051 File Paths -- NVRAM. nvram = "...." must match not applicable not applicable
3052 File Paths -- Log. log.fileName = "...." must match not applicable not applicable
3053 File Paths -- Virtual Disk (SCSI). scsi#:#.fileName = "...." must match not applicable not applicable
3054 File Paths -- Virtual Disk (IDE). ide#:#.fileName = "...." must match not applicable not applicable
3055 File Paths -- Extended Configuration. extendedConfigFile = "...." must match not applicable not applicable
3056 File Paths -- working Directory. workingDir = "." must match not applicable not applicable
Test Case Series 79xx [Guest OS Selection]
TC
ID 		TC Title TC Summary Hv.
Class 		OVa OVF Only
7901 Guest OS is Supported. The Guest Operating System selected for use in the virtual appliance MUST be one which is listed as Supported for the target platform. The current descriptions of Supported Guest OS variants can be found in HTML at http://pubs.vmware.com/guestnotes/ and in PDF at http://www.vmware.com/pdf/GuestOS_guide.pdf (revised concurrently). must match must match must match
Test Case Series 80xx [Guest OS and App. Stack]
TC
ID 		TC Title TC Summary Hv.
Class 		OVa OVF Only
8001 Filesystem consistency. All Guest OS filesystems MUST be marked "clean". No filesystem presented to the Guest OS may be in a state where consistency checking (fsck / chkdsk / etc...) is required as part of the normal deployment process of a virtual appliance. Written exceptions MAY be granted for situations where the filesystem is, by design, intended to be in an inconsistent state, for example a computer forensics training environment. must match must match must match
8002 Filesystem mount-count and age data. All Guest OS filesystems SHOULD have their mount-count and age values reset to extend the period of time before the first forcible consistency check (fsck / chkdsk / etc...) is required as part of the normal operation of a virtual appliance. must match must match must match
8003 Missing and remnant filesystems. With the exception of properly documented resources added as part of the deployment process, all Guest OS required filesystems MUST be present. Stale mount-point entries (CD-ROMs, NAS shares, etc...) and other remnants of pre-deployment work MUST NOT be present. must match must match must match
8011 Authentication and cryptography components. Authentication and cryptographic keying components SHOULD NOT be present in the Guest OS and/or application stack. Presence of these components means that every iteration of the virtual appliance in the field will have precisely the same keying (ex: SSH and/or SSL) components. The ISV is responsible for determining relevance, whether or not this is an appropriate behavior, and MUST validate that the virtual appliance is capable of properly regenerating keying components (e.g. automatically running keygen tool) should they be removed. must match must match must match
8080 Boot/Halt Test. The virtual appliance MUST be capable of completing a boot/halt test cycle without blocking errors. Typically this represents the span of first customer boot through first customer shutdown of the virtual appliance. must match must match must match
Test Case Series 88xx [OVF Integration -- Import]
TC
ID 		TC Title TC Summary Hv.
Class 		OVA OVF Only
8820 Pre-Import Fix-Ups Pre-import fix-ups as described in Test Cases 8821 through 8839 MUST be covered in the Documentation (see Test Cases 1001 through 1099). not applicable must match must match
8839 Pre-Import Fix-Ups Not Otherwise Specified Pre-import fix-ups not otherwise specified MAY be covered in the Documentation (see Test Cases 1001 through 1099) at the vendor's discretion.

[[VMR 1.9 rev. 2009.01.31 -- No pre-import fix-ups exist at this time.]] 		not applicable must match must match
8840 Post-Import Fix-Ups Post-import fix-ups as described in Test Cases 8841 through 8859 MUST be covered in the Documentation (see Test Cases 1001 through 1099). not applicable must match must match
8841 VMware Tools -- Time Sync OVF to VMware-native import leaves Host-Guest Timesync disabled.

Refer to Test Case 2576 for further information. 		not applicable must match must match
8842 VMware Tools -- Soft Power Operations OVF to VMware-native import leaves Soft Power Operations in 'default' state.

Refer to Test Case 2575 for further information. 		not applicable must match must match
8843 VMware Tools -- Run State Transition Scripts OVF to VMware-native import leaves run state transition scripts in enabled state. These must be disabled if Soft Power Operations are not supported by the virtual appliance, or errors will be reported requesting that a support request be filed with VMware.

Refer to Test Case 2575 for further information. 		not applicable must match must match
8844 Virtual Resources -- Virtual IDE CDROM (CD/DVD Drive) OVF to VMware-native import automatically (re-)adds one virtual IDE CDROM device if none were present in the OVF descriptor.

Refer to Test Case 2502 for further information. 		not applicable must match must match
8859 Post-Import Fix-Ups Not Otherwise Specified Post-import fix-ups not otherwise specified MAY be covered in the Documentation (see Test Cases 1001 through 1099) at the vendor's discretion. not applicable must match must match
Test Case Series 99xx [Records and Archiving]
TC
ID 		TC Title TC Summary Hv.
Class 		OVA OVF Only
9901 Record Keeping. A record MUST be kept of Test Case outcome with revision number for the Test Matrix. The exact method of implementation for this record keeping is not prescribed.

[[The current revision is VMR 1.9 rev. 2009.01.31]] 		must match must match must match
VMR 1.9 rev. 2009.01.31

Words or phrases with specific meaning:

"Part of the Virtual Appliance"

Material comprising the virtual appliance as delivered for distribution, and/or for deployment by the end user. This may include, but is not exclusively limited to: Documentation, Archives, EULA Information, Registration Information, Welcome Information, Authentication Information, and License Information.

EXPLICITLY EXCLUDED is material which requires a non-procedural action on the part of the end user in order to be obtained, and/or would generally be considered missing.


IETF BCP 14 Related

MAY

This word, or the adjective "OPTIONAL", mean that an item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item. An implementation which does not include a particular option MUST be prepared to interoperate with another implementation which does include the option, though perhaps with reduced functionality. In the same vein an implementation which does include a particular option MUST be prepared to interoperate with another implementation which does not include the option (except, of course, for the feature the option provides).



MUST

This word, or the terms "REQUIRED" or "SHALL", mean that the definition is an absolute requirement of the specification.



MUST NOT

This phrase, or the phrase "SHALL NOT", mean that the definition is an absolute prohibition of the specification.



SHOULD

This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.



SHOULD NOT

This phrase, or the phrase "NOT RECOMMENDED" mean that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label.



NOT APPLICABLE

This phrase means that an item is not relevant in this particular implementation. This term is not part of IETF BCP 14, but is included as an extension in order to provided context to individual items where traditional BCP 14 terminology cannot be used.

VMware Ready Program

Leverage the Benefits of the VMware Ready Virtual Appliance Program.

Learn More

List Your Appliance Today

Access thousands of interested customers!

Get Started

Get Juiced!

Run your software on juice.

Learn More