Has anyone had issues with ESXi 6 update 2 and Active Directory authentication?  It appears to join the domain just fine (the server object gets created in AD) but I can't log in.  I can ping the domain and all the dcs.  DNS is pointed at a DC.

: Failed to group memberships of SID=(My User SID HERE). [error code:40286]

20160324135215:INFO:lsass:LsaDmpLdapReconnectCallback():lsadm.c:3214: Clearing ldap DC connection list for domain 'Domain.com' due to a network error.

20160324135215:DEBUG:LwLdapDirectorySearchEx():lwldap.c:791: [LwLdapDirectorySearchEx() ../lwadvapi/threaded/lwldap.c:791] Ldap error code: 40286

20160324135215:DEBUG:LwLdapDirectoryExtendedDNSearch():lwldap.c:1962: [LwLdapDirectoryExtendedDNSearch() ../lwadvapi/threaded/lwldap.c:1962] Error code: 40286 (symbol: <null>)

20160324135215:DEBUG:lsass:LsaDmLdapDirectoryExtendedDNSearch():lsadm.c:3568: Error code: 40286 (symbol: LW_ERROR_LDAP_SERVER_DOWN)

20160324135215:DEBUG:lsass:ADLdap_GetAttributeValuesList():adldap.c:1366: Error code: 40286 (symbol: LW_ERROR_LDAP_SERVER_DOWN)

20160324135215:DEBUG:lsass:ADLdap_GetObjectGroupMembership():adldap.c:1688: Error code: 40286 (symbol: LW_ERROR_LDAP_SERVER_DOWN)

20160324135215:ERROR:lsass:ADLdap_GetObjectGroupMembership():adldap.c:1757: Failed to group memberships of SID=(My User SID HERE). [error code:40286]

20160324135215:DEBUG:lsass:AD_PacMembershipFilterWithLdap():online.c:1162: Error code: 40286 (symbol: LW_ERROR_LDAP_SERVER_DOWN)

20160324135215:DEBUG:lsass:AD_CacheGroupMembershipFromPac():online.c:1353: Error code: 40286 (symbol: LW_ERROR_LDAP_SERVER_DOWN)

20160324135215:DEBUG:lsass:AD_OnlineCheckUserPassword():online.c:1816: Error code: 40286 (symbol: LW_ERROR_LDAP_SERVER_DOWN)

20160324135215:DEBUG:lsass:AD_OnlineAuthenticateUserPam():online.c:1909: Error code: 40286 (symbol: LW_ERROR_LDAP_SERVER_DOWN)

20160324135215:DEBUG:lsass:LsaSrvAuthenticateUserPam():auth.c:120: Error code: 40286 (symbol: LW_ERROR_LDAP_SERVER_DOWN)

20160324135215:ERROR:lsass:LsaSrvAuthenticateUserPam():auth.c:174: Failed to authenticate user (name = 'User@Domain.com') -> error = 40286, symbol = LW_ERROR_LDAP_SERVER_DOWN, client pid = 35954

20160324135215:VERBOSE:lsass-ipc:lwmsg_peer_task_handle_assoc_error():peer-task.c:895: (assoc:0x1f1013b0) Dropping: Connection closed by peer

20160324135215:DEBUG:LwKrb5SetThreadDefaultCachePath():lwkrb5.c:410: Switched gss krb5 credentials path from <null> to FILE:/etc/likewise/lib/krb5cc_lsass.Domain.com

20160324135215:VERBOSE:lsass:AD_CheckExpiredObject():online.c:2001: Using cache entry for sid S-1-5-21-3658379808-1708799015-1379952707-83163, updated 1044 seconds ago

20160324135215:DEBUG:LwKrb5SetThreadDefaultCachePath():lwkrb5.c:410: Switched gss krb5 credentials path from <null> to FILE:/etc/likewise/lib/krb5cc_lsass.Domain.com

20160324135215:VERBOSE:lsass:AD_CheckExpiredObject():online.c:2001: Using cache entry for sid S-1-5-21-3658379808-1708799015-1379952707-83163, updated 1044 seconds ago

20160324135217:VERBOSE:lsass:LsaSrvIpcCheckPermissions():ipc_state.c:79: Permission granted for (uid = 0, gid = 0, pid = 84440) to open LsaIpcServer

20160324135217:VERBOSE:lsass-ipc:lwmsg_peer_log_accept():peer-task.c:271: (session:af426f444a751a18-231291411ab31d27) Accepted association 0x1f0f7228

20160324135217:VERBOSE:lsass-ipc:lwmsg_peer_task_handle_assoc_error():peer-task.c:895: (assoc:0x1f0f7228) Dropping: Connection closed by peer

20160324135217:VERBOSE:lsass:LsaSrvIpcCheckPermissions():ipc_state.c:79: Permission granted for (uid = 0, gid = 0, pid = 84440) to open LsaIpcServer

20160324135217:VERBOSE:lsass-ipc:lwmsg_peer_log_accept():peer-task.c:271: (session:f3984d013795f5fb-7c033ed7f8e93f5a) Accepted association 0x1f0b9e18

20160324135217:VERBOSE:lsass-ipc:lwmsg_peer_task_handle_assoc_error():peer-task.c:895: (assoc:0x1f0b9e18) Dropping: Connection closed by peer

20160324135217:VERBOSE:lsass:LsaSrvIpcCheckPermissions():ipc_state.c:79: Permission granted for (uid = 0, gid = 0, pid = 84441) to open LsaIpcServer

20160324135217:VERBOSE:lsass-ipc:lwmsg_peer_log_accept():peer-task.c:271: (session:fec44f4ec5ad69a5-a9c45595908d5eae) Accepted association 0x1f1013b0

20160324135217:VERBOSE:lsass-ipc:lwmsg_peer_task_handle_assoc_error():peer-task.c:895: (assoc:0x1f1013b0) Dropping: Connection closed by peer

20160324135217:VERBOSE:lsass:LsaSrvIpcCheckPermissions():ipc_state.c:79: Permission granted for (uid = 0, gid = 0, pid = 84441) to open LsaIpcServer

20160324135217:VERBOSE:lsass-ipc:lwmsg_peer_log_accept():peer-task.c:271: (session:734c74cc6f62b2b3-7438b01d2ca183ef) Accepted association 0x1f0f7228

20160324135217:VERBOSE:lsass-ipc:lwmsg_peer_task_handle_assoc_error():peer-task.c:895: (assoc:0x1f0f7228) Dropping: Connection closed by peer

20160324135217:DEBUG:LwKrb5SetThreadDefaultCachePath():lwkrb5.c:410: Switched gss krb5 credentials path from <null> to FILE:/etc/likewise/lib/krb5cc_lsass.Domain.com

20160324135217:DEBUG:lsass:MemCacheFindUserByName():memcache.c:937: Error code: 40017 (symbol: LW_ERROR_NOT_HANDLED)

20160324135217:DEBUG:lsass:LsaSrvFindProviderByName():state.c:128: Error code: 40040 (symbol: LW_ERROR_INVALID_AUTH_PROVIDER)

20160324135217:DEBUG:lsass:LsaSrvProviderServicesDomain():provider.c:151: Error code: 40040 (symbol: LW_ERROR_INVALID_AUTH_PROVIDER)

20160324135217:DEBUG:LwLdapDirectorySearch():lwldap.c:716: [LwLdapDirectorySearch() ../lwadvapi/threaded/lwldap.c:716] Ldap error code: 40286

20160324135217:INFO:netlogon:LWNetSrvGetDCName():dcinfo.c:97: Looking for a DC in domain 'Domain.com', site '<null>' with flags 0

20160324135217:DEBUG:lsass:LsaLdapOpenDirectoryWithReaffinity():lsaldap.c:152: Using DC 'DC.Domain.com' for domain 'Domain.com' (affinitization attempt 0)

20160324135217:DEBUG:LwKrb5CheckInitiatorCreds():lwkrb5.c:1601: GSS API error calling gss_init_sec_context(): majorStatus = 0x00000001 (The routine must be called again to complete its function), minorStatus = 0x00000000 (Unknown error)

Hi,

I found the following issue with the new  ESX 6.0.0 Update2 3073146

* I've got a device mapped by RDM like on KB1017530 to a VM (has been connected with the the c# "fat client") some time ago

* I open the new host client

* from there I open the settings of my VM (running or not running does not matter)

* when hit 'Save' even without changing anything  I get a red

Failed to reconfigure virtual machine BACKUPSERVER. Incompatible device backing specified for device '3'. end ngIf: !notification.link && !notification.state ngIf: notification.link ngIf: notification.state

Edit settings with the fat client still works as usual...

Ralf.

Thank You! That is a good hint. Indeed when you configure it that way, users cannot see every resource pool and vm. That is way better.

There is one problem left. When we give the privilege "Assign virtual machine to resource pool" to users on cluster level, even if propagate is un-checked and users therefor cannot move machines in each others resource pools, they are still able to move machines directly to the cluster resource pool. They would be able to bypass the resource restrictions we set on their resource pools.

Am I still missing out on something? Is there another trick that will do it? 

Hi,

I'm currently trying to install ESXi 5.1 on some new HP ProLiant BL460c Gen9 servers. However the install runs through what looks to be successful and then hit with a PSOD.

I have attached a image of the PSOD to the post. Any help on why this is happening would be greatly appreciated.

thanks.

Хорошо. Повторюсь третий раз.

При помощи vsphere client ЭТОТ диск добавляеться без проблем и все данные видны и целы.

Вопрос. Как точно такуюже операцию можно выполнить при помощи embedded host client?

I cleared the exam with about 7-10 days of prep. I had no prior experience with NSX so studying from the ground-up was helpful. This certification give you some direction and structure in preparing for more advanced exams. I am hoping this will help with my VCP prep.

Below are the resources I used:

[1] VMware Network Virtualization Fundamentals eLearning Course

[2] NSX HOL

[3] NSX Network Virtualization Design Guide

[4] NSX Documentation Center

[5] NSX Packet Walk [Deep Dive Blogs from routetocloud]

[6] Blogs from Scott Lowe and Brad Hedlund

Good luck !

Комрады всем привет, давно не был здесь!

Дано:

powershell скрипт, который делает некоторые манипуляции с гостем

Задача:

заставить его отработать в кастомизации, если он будет прописан в строке RunOnce

вопрос, может ли runonce как-либо поглотить powershell?

Скрипт относительно простой, добавление сервера в домен (add-computer).

Не спрашивайте, знаю что это можно делать штатными средствами, или netdom в том же runonce. Просто так надо!

На чистой машине скрипт отрабатывает на ура. В RunOnce пытаюсь его всячески прописать, но он не отрабатывает.

Знаю, что можно еще положить в шаблон скрипт и в RunOnce прописать путь, такой вариант менее интересен.

Вывод команды esxcli storage vmfs snapshot list

[root@esxi:~] esxcli storage vmfs snapshot list

5347a57d-8dc5de20-ced3-e0cb4e9b6e59

   Volume Name: HDD_1000

   VMFS UUID: 5347a57d-8dc5de20-ced3-e0cb4e9b6e59

   Can mount: true

   Reason for un-mountability:

   Can resignature: true

   Reason for non-resignaturability:

   Unresolved Extent Count: 1

Hi All

We have recently purchased two new HP ProLiant DL380p Gen8 servers and as these come with quad 1Gbe on-board I have also added Intel X710-DA2 NIC on each to benefit from faster speeds to our storage. Genuine Intel 10GBase-SR SFP+ modules have been also installed.

First as there is no i40e driver in ESXi 6.0u2 (3620759) I had to load the drivers in order to make ESXi recognize my cards. I downloaded the latest i40e version 1.4.26 available on VMware website through that link VMware Compatibility Guide - I/O Device Search and installed the vib. As reboot was required I have rebooted the system and after the reboot the adapters were now assigned a vmnic numbers and were available to claim for usage.

Just to make sure I have also downloaded the latest NVM updater from Intel website to verify I am running on the most recent firmware. So I downloaded the updater for firmware version 5.02 from Download NVM Update Utility for Intel® Ethernet Converged Network Adapter XL710 & X710 Series and using the ESX updater verified that both cards are running on the latest firmware (they were already up-to-date).

Eventually I continued on my deployment, but as I needed to reboot one of the hosts I hit a PURPLE screen with the error: "LINT1/NMI (motherboard nonmaskable interrupt), undiagnosed. This may be a hardware problem; please contact your hardware vendor." (check attached file esxi-crash.JPG)

To further-troubleshoot I have verified that I am running on the latest BIOS version on the DL380p Gen8 servers (P70), and I also had the latest iLO4 version (2.30). I have tried also the following:

1) Adjusting the power options for the server to full performance

2) Using different Intel driver for VMware (I tried with all available versions: 1.4.26, 1.3.45, 1.3.38, 1.2.48, 1.2.22, 1.1.1)

Neither one of these helped and each time I would reboot any of the hosts I would hit the same Purple screen with the same error.

Eventually in BIOS I noticed that even-though the X710 NIC is recognized as Ethernet adapter in IRQ settings, in the PCI enable/disable list the NIC is shown as unknown PCI device. (check attached files: dl380p-gen8-01.PNG & dl380p-gen8-02.PNG)

I am also attaching the output of /usr/lib/vmware/vm-support/bin/swfw.sh (attached file output-swfw.txt). In that file is clearly visible that I am running 1.4.26 and my firmware version is 5.02.

It is good mentioning that network traffic is just fine, the only time I get that purple screen is when I reboot either one of the hosts. Also NIC ports are not teamed.

Any ideas or suggestions are highly appreciated!

Best,

KG

For an CSV you can use the Export-Csv cmdlet.

For an XLSX there is my Export-Xlsx, the sequel, and ordered data, and more recent Doug's excellent PowerShell Import-Excel

сообщения в vmkernel логе при прохождении rescan.

2016-03-25T09:36:18.548Z cpu1:33117)NMP: nmp_ResetDeviceLogThrottling:3349: last error status from device mpx.vmhba32:C0:T0:L0 repeated 11 times

2016-03-25T09:37:32.880Z cpu2:32926)ScsiUid: 273: Path 'vmhba0:C0:T0:L0' does not support VPD Device Id page.

2016-03-25T09:37:32.883Z cpu2:32926)VMWARE SCSI Id: Could not get disk id for vmhba0:C0:T0:L0

2016-03-25T09:37:32.897Z cpu1:33132)usb-storage: detected SCSI revision number 0 on vmhba32

2016-03-25T09:37:32.897Z cpu1:33132)usb-storage: patching inquiry data to change SCSI revision number from 0 to 2 on vmhba32

2016-03-25T09:37:32.898Z cpu0:32924)ScsiUid: 273: Path 'vmhba32:C0:T0:L0' does not support VPD Device Id page.

2016-03-25T09:37:32.898Z cpu0:32924)VMWARE SCSI Id: Could not get disk id for vmhba32:C0:T0:L0

2016-03-25T09:37:32.910Z cpu1:34102 opID=5678c057)World: 15516: VC opID 06E7F66B-0000004C-b97e maps to vmkernel opID 5678c057

2016-03-25T09:37:32.910Z cpu1:34102 opID=5678c057)ScsiScan: 836: Path vmhba35:C0:T0:L0 supports REPORT LUNS 0x11

2016-03-25T09:37:32.924Z cpu1:32787)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x12 (0x439d8025df00, 0) to dev "mpx.vmhba32:C0:T0:L0" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0. Act:NONE

2016-03-25T09:37:32.930Z cpu0:32786)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x12 (0x439d8025df00, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0. Act:NONE

2016-03-25T09:37:33.125Z cpu1:32787)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x439d802901c0, 0) to dev "mpx.vmhba32:C0:T0:L0" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-03-25T09:37:33.130Z cpu0:34102 opID=e32c1fc1)World: 15516: VC opID 06E7F66B-0000004E-b98b maps to vmkernel opID e32c1fc1

2016-03-25T09:37:33.130Z cpu0:34102 opID=e32c1fc1)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12

2016-03-25T09:37:33.130Z cpu1:32787)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x439d802901c0, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-03-25T09:37:33.142Z cpu0:34102 opID=e32c1fc1)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12

2016-03-25T09:37:33.142Z cpu1:32787)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x439d802901c0, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-03-25T09:37:33.154Z cpu0:34102 opID=e32c1fc1)LVM: 10080: Device t10.ATA_____WDC_WD1001FALS2D00J7B1________________________WD2DWMATV1883224:1 detected to be a snapshot:

2016-03-25T09:37:33.154Z cpu0:34102 opID=e32c1fc1)LVM: 10087:   queried disk ID: <type 1, len 26, lun 0, devType 0, scsi 0, h(id) 17948703437476516516>

2016-03-25T09:37:33.154Z cpu0:34102 opID=e32c1fc1)LVM: 10094:   on-disk disk ID: <type 1, len 14, lun 0, devType 0, scsi 0, h(id) 7322232454884392162>

2016-03-25T09:37:33.155Z cpu0:34102 opID=e32c1fc1)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12

2016-03-25T09:37:33.155Z cpu1:32787)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x439d802961c0, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-03-25T09:37:33.157Z cpu0:34102 opID=e32c1fc1)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12

2016-03-25T09:37:33.157Z cpu1:32787)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x439d802961c0, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-03-25T09:37:33.159Z cpu0:34102 opID=e32c1fc1)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12

2016-03-25T09:37:33.159Z cpu1:32787)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x439d802961c0, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-03-25T09:37:33.162Z cpu0:34102 opID=e32c1fc1)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12

2016-03-25T09:37:33.162Z cpu1:32787)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x439d802961c0, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-03-25T09:37:33.167Z cpu0:34102 opID=e32c1fc1)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12

2016-03-25T09:37:33.167Z cpu1:32787)NMP: nmp_ThrottleLogForDevice:3248: last error status from device mpx.vmhba0:C0:T0:L0 repeated 1 times

2016-03-25T09:37:33.167Z cpu1:32787)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x439d80294cc0, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-03-25T09:37:33.169Z cpu0:34102 opID=e32c1fc1)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12

2016-03-25T09:37:33.169Z cpu1:32787)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x439d80294cc0, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-03-25T09:37:33.174Z cpu0:34102 opID=e32c1fc1)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12

2016-03-25T09:37:33.174Z cpu1:32787)NMP: nmp_ThrottleLogForDevice:3248: last error status from device mpx.vmhba0:C0:T0:L0 repeated 1 times

2016-03-25T09:37:33.174Z cpu1:32787)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x439d80299b80, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-03-25T09:37:33.176Z cpu0:34102 opID=e32c1fc1)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12

2016-03-25T09:37:33.176Z cpu1:32787)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x439d80299b80, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-03-25T09:37:33.178Z cpu0:34102 opID=e32c1fc1)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12

2016-03-25T09:37:33.178Z cpu1:32787)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x439d80299b80, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-03-25T09:37:33.181Z cpu0:34102 opID=e32c1fc1)FSS: 5334: No FS driver claimed device 'mpx.vmhba0:C0:T0:L0': No filesystem on the device

2016-03-25T09:37:33.190Z cpu1:32787)NMP: nmp_ThrottleLogForDevice:3231: last error status from device mpx.vmhba32:C0:T0:L0 repeated 10 times

2016-03-25T09:37:33.324Z cpu1:34102 opID=e32c1fc1)VC: 3551: Device rescan time 31 msec (total number of devices 4)

2016-03-25T09:37:33.324Z cpu1:34102 opID=e32c1fc1)VC: 3554: Filesystem probe time 169 msec (devices probed 4 of 4)

2016-03-25T09:37:33.324Z cpu1:34102 opID=e32c1fc1)VC: 3556: Refresh open volume time 0 msec

Hello All,

Slowly coming up to speed with the VMware certification tracks.

I am starting to prep for the VCA6-DCV exam and had a few questions on the below:

[1] Is there a VMware Hands On Lab course I can look at for the DCV track ?

[2] There seems to be a VMware Press DCV Cert Guide. Is it helpful or should the Data Center Virtualization Fundamentals track be sufficient ?

Appreciate your input. Thank you !

I have seen mentions where the VM you are trying to export was configured with a static IP.

Once the VM was reconfigured to use DHCP, the export worked.

A wild guess, but perhaps worth a try.

Also check the vpxd log.

Or did you already do that, and saw the same message that was mentioned ?

Thanks LucD.You are always the best:)

I will try this out.

How about Step#2 wherein I need to map the disks to VM using Powercli with exact same configurations as that info pulled from Step#1?

Hi,

That is related to new feature on VMware Tools 10 and don't remove that.

Common Agent Framework: Common Agent Framework (CAF) provides the basic services necessary to simplify secure and efficient management of agents inside the guest virtual machines.

BR

Can you please try full path to the vib rather than relative path

esxcli software vib install -v < full path to the vib>

Друзья подскажите.

Имеется:

MB - P5E3 Deluxe > линк на Никс

Биос последний > 1502

Vanderpool Technology в биосе включено.

Проц - Intel Core2 Quad Processor Q9300 - Intel® Core™2 Quad Processor Q9300 (6M Cache, 2.50 GHz, 1333 MHz FSB) Спецификации

ESXi - 6.0.0 (Build 3620759)

Вроде (по спецификациям) все поддерживает vt-d.

Но зайдя в Advanced Settings (VMware vSphere Client) - имею "Host does not support passthrough configuration"

Совсем не как не не получиться задействовать проброс устройств?

Hi,

You need to read this document from Ubuntu:

https://help.ubuntu.com/lts/installation-guide/i386/ch04s06.html

Also about VMware customization:

Судя по тем выводам вероятно host client не научили работать с лунами, которые определяются как снапшот.

И тогда надо либо пользоваться старым добрым c# клиентом, либо смонтировать VMFS из командной строки.

В принципе подобных проблем =можно ожидать, потому что релиз клиента имеет версию 1.0.0

Что в практике VMware означает совсем нулевой продукт. В следующей мажорной версии ESXi (например 6.5), его могут сильно допилить и привести к версионности ESXi.

Если есть возможно - рекомендую открыть кейс в техподдержке и сообщить о своей находке.

Вряд ли что-то получится сделать с помощью форума в вашем случае

Обычно это пишут в документации.

Например вот раздел best practice Networking Best Practices

For best performance, use VMXNET 3 virtual machine NICs.