Verifying VMware driver and DVS mechanism driver requirements
Review the following VMware and mechanism driver requirements.
Procedure
- (VMware driver) Verify that you have the correct user permissions.
To connect to vCenter, you must have administrator permissions to the target data center. You must also have read-only and "Extension" permissions to the entire vCenter.
- (VMware driver) Verify that you are using a supported disk
type. Supported disk types include sparse, streamOptimized, thin, preallocated, thick, and eagerZeroedThick.
- (Mechanism driver) Ensure that a distributed virtual switch
exists on the managed-to data center, and the distributed virtual
switch is connected with target hosts and clusters. Note: When Neutron creates a network, either a tenant network or an external network, a port group is created on this switch accordingly by the mechanism driver.
- (Mechanism driver) Ensure that you installed the oslo-vmware package.
- (VMware driver) Ensure that you are using a supported operating
system. Supported operating systems are as follows:
asianux3_64Guest asianux3Guest asianux4_64Guest asianux4Guest centos64Guest centosGuest darwin10_64Guest darwin10Guest darwin11_64Guest darwin11Guest darwin12_64Guest darwin13_64Guest darwin64Guest darwinGuest debian4_64Guest debian4Guest debian5_64Guest debian5Guest debian6_64Guest debian6Guest debian7_64Guest debian7Guest dosGuest eComStation2Guest eComStationGuest fedora64Guest fedoraGuest freebsd64Guest freebsdGuest genericLinuxGuest mandrakeGuest mandriva64Guest mandrivaGuest netware4Guest netware5Guest netware6Guest nld9Guest oesGuest openServer5Guest openServer6Guest opensuse64Guest opensuseGuest oracleLinux64Guest oracleLinuxGuest os2Guest other24xLinux64Guest other24xLinuxGuest other26xLinux64Guest other26xLinuxGuest other3xLinux64Guest other3xLinuxGuest otherGuest otherGuest64 otherLinux64Guest otherLinuxGuest redhatGuest rhel2Guest rhel3_64Guest rhel3Guest rhel4_64Guest rhel4Guest rhel5_64Guest rhel5Guest rhel6_64Guest rhel6Guest rhel7_64Guest rhel7Guest sjdsGuest sles10_64Guest sles10Guest sles11_64Guest sles11Guest sles12_64Guest sles12Guest sles64Guest slesGuest solaris10_64Guest solaris10Guest solaris11_64Guest solaris6Guest solaris7Guest solaris8Guest solaris9Guest turboLinux64Guest turboLinuxGuest ubuntu64Guest ubuntuGuest unixWare7Guest vmkernel5Guest vmkernelGuest win2000AdvServGuest win2000ProGuest win2000ServGuest win31Guest win95Guest win98Guest windows7_64Guest windows7Guest windows7Server64Guest windows8_64Guest windows8Guest windows8Server64Guest windowsHyperVGuest winLonghorn64Guest winLonghornGuest winMeGuest winNetBusinessGuest winNetDatacenter64Guest winNetDatacenterGuest winNetEnterprise64Guest winNetEnterpriseGuest winNetStandard64Guest winNetStandardGuest winNetWebGuest winNTGuest winVista64Guest winVistaGuest winXPHomeGuest winXPPro64Guest winXPProGuest - (VMware Driver) Ensure that the name of the datastores
to be used matches the following conditions. The name can contain only uppercase letters, lowercase letters, white spaces, numbers (0-9), minus signs ( - ), or underlines ( _ ).
- (VMware Driver) Ensure that the datacenters on the managed-to vCenter are in the root folder, not in any subfolders.