So far the DX support remains on feature level 10.0.

Never mind.  4th time was the charm it seems.  Installed fine this time.  Nothing done differently this time.  Ignore this for now. 

/var/log # cat vmkernel.log | grep xhci

VMB: 212: name: /xhci_xhc.v00

2017-07-18T03:35:16.458Z cpu0:32768)VisorFSTar: 1960: xhci_xhc.v00 for 0x2a17f bytes

2017-07-18T03:35:23.556Z cpu0:33344)Loading module xhci ...

2017-07-18T03:35:23.557Z cpu0:33344)Elf: 1861: module xhci has license GPL

2017-07-18T03:35:23.557Z cpu0:33344)module heap vmklnx_xhci: creation succeeded. id = 0x410953fed000

2017-07-18T03:35:23.557Z cpu0:33344)PCI: driver xhci_hcd is looking for devices

2017-07-18T03:35:23.557Z cpu0:33344)<6>xhci_hcd 0000:00:14.0: xHCI Host Controller

2017-07-18T03:35:23.557Z cpu0:33344)<6>xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3

2017-07-18T03:35:23.558Z cpu0:33344)IRQ: 540: 0x31 <xhci_hcd:usb3> sharable, flags 0x10

2017-07-18T03:35:23.558Z cpu0:33344)<6>xhci_hcd 0000:00:14.0: irq 16, io mem 0xf7d20000

2017-07-18T03:35:23.558Z cpu0:33344)IRQ: 540: 0x37 <xhci_hcd> exclusive, flags 0x10

2017-07-18T03:35:23.558Z cpu0:33344)<6>usb usb3: Manufacturer: vmklinux_9 xhci_hcd

2017-07-18T03:35:23.558Z cpu0:33344)<7>xHCI xhci_add_endpoint called for root hub

2017-07-18T03:35:23.558Z cpu0:33344)<7>xHCI xhci_check_bandwidth called for root hub

2017-07-18T03:35:23.558Z cpu0:33344)<6>xhci_hcd 0000:00:14.0: xHCI Host Controller

2017-07-18T03:35:23.558Z cpu0:33344)<6>xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4

2017-07-18T03:35:23.558Z cpu0:33344)<6>usb usb4: Manufacturer: vmklinux_9 xhci_hcd

2017-07-18T03:35:23.558Z cpu0:33344)<7>xHCI xhci_add_endpoint called for root hub

2017-07-18T03:35:23.558Z cpu0:33344)<7>xHCI xhci_check_bandwidth called for root hub

2017-07-18T03:35:23.558Z cpu0:33344)PCI: driver xhci_hcd claimed device 0000:00:14.0

2017-07-18T03:35:23.558Z cpu0:33344)PCI: driver xhci_hcd claimed 1 device

2017-07-18T03:35:23.558Z cpu0:33344)Mod: 4780: Initialization of xhci succeeded with module ID 4126.

2017-07-18T03:35:23.558Z cpu0:33344)xhci loaded successfully.

VMB: 212: name: /xhci_xhc.v00

2017-07-18T03:56:36.455Z cpu0:32768)VisorFSTar: 1960: xhci_xhc.v00 for 0x37d7f bytes

2017-07-18T03:56:43.463Z cpu6:33343)Loading module xhci ...

2017-07-18T03:56:43.463Z cpu6:33343)Elf: 1861: module xhci has license GPL

2017-07-18T03:56:43.464Z cpu6:33343)module heap vmklnx_xhci: creation succeeded. id = 0x41092d4fd000

2017-07-18T03:56:43.464Z cpu6:33343)PCI: driver xhci_hcd is looking for devices

2017-07-18T03:56:43.464Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: xHCI Host Controller

2017-07-18T03:56:43.464Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3

2017-07-18T03:56:43.464Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: Resetting HCD

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: Reset complete

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: Enabling 64-bit DMA addresses.

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: Calling HCD init

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: Called HCD init

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: hcc params 0x20007181 hci version 0x100 quirks 0x0000b930

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: Got SBRN 48

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: Finished xhci_pci_reinit

2017-07-18T03:56:43.465Z cpu6:33343)IRQ: 540: 0x37 <xhci_hcd> exclusive, flags 0x10

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: Command ring memory map follows:

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: ERST memory map follows:

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: Event ring:

2017-07-18T03:56:43.465Z cpu6:33343)<6>usb usb3: Manufacturer: vmklinux_9 xhci-hcd

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: set port power, actual port 0 status = 0x2a0

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: set port power, actual port 1 status = 0x2a0

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: set port power, actual port 2 status = 0x2a0

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: set port power, actual port 3 status = 0x2a0

2017-07-18T03:56:43.466Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: xHCI Host Controller

2017-07-18T03:56:43.466Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4

2017-07-18T03:56:43.466Z cpu6:33343)<6>usb usb4: Manufacturer: vmklinux_9 xhci-hcd

2017-07-18T03:56:43.466Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: set port power, actual port 0 status = 0x802a0

2017-07-18T03:56:43.466Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: set port power, actual port 1 status = 0x802a0

2017-07-18T03:56:43.466Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: set port power, actual port 2 status = 0x802a0

2017-07-18T03:56:43.466Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: set port power, actual port 3 status = 0x802a0

2017-07-18T03:56:43.466Z cpu6:33343)PCI: driver xhci_hcd claimed device 0000:00:14.0

2017-07-18T03:56:43.466Z cpu6:33343)PCI: driver xhci_hcd claimed 1 device

2017-07-18T03:56:43.466Z cpu6:33343)Mod: 4780: Initialization of xhci succeeded with module ID 4130.

2017-07-18T03:56:43.466Z cpu6:33343)xhci loaded successfully.

2017-07-18T03:56:43.566Z cpu1:33318)<6>xhci_hcd 0000:00:14.0: clear port warm(BH) reset change, actual port 0 status = 0x2a0

2017-07-18T03:56:43.566Z cpu1:33318)<6>xhci_hcd 0000:00:14.0: clear port warm(BH) reset change, actual port 1 status = 0x2a0

2017-07-18T03:56:43.566Z cpu1:33318)<6>xhci_hcd 0000:00:14.0: clear port warm(BH) reset change, actual port 2 status = 0x2a0

2017-07-18T03:56:43.566Z cpu1:33318)<6>xhci_hcd 0000:00:14.0: clear port warm(BH) reset change, actual port 3 status = 0x2a0

2017-07-18T03:56:46.520Z cpu4:33305)<6>xhci_hcd 0000:00:14.0: set port remote wake mask, actual port 0 status = 0xe0002a0

2017-07-18T03:56:46.520Z cpu4:33305)<6>xhci_hcd 0000:00:14.0: set port remote wake mask, actual port 1 status = 0xe0002a0

2017-07-18T03:56:46.520Z cpu4:33305)<6>xhci_hcd 0000:00:14.0: set port remote wake mask, actual port 2 status = 0xe0002a0

2017-07-18T03:56:46.520Z cpu4:33305)<6>xhci_hcd 0000:00:14.0: set port remote wake mask, actual port 3 status = 0xe0002a0

2017-07-18T04:05:59.039Z cpu2:33310)<6>xhci_hcd 0000:00:14.0: set port remote wake mask, actual port 0 status = 0xe0002a0

2017-07-18T04:05:59.039Z cpu2:33310)<6>xhci_hcd 0000:00:14.0: set port remote wake mask, actual port 1 status = 0xe0002a0

2017-07-18T04:05:59.039Z cpu2:33310)<6>xhci_hcd 0000:00:14.0: set port remote wake mask, actual port 2 status = 0xe0002a0

2017-07-18T04:05:59.039Z cpu2:33310)<6>xhci_hcd 0000:00:14.0: set port remote wake mask, actual port 3 status = 0xe0002a0

2017-07-18T04:22:52.484Z cpu6:35925)<6>xhci_hcd 0000:00:14.0: Port Status Change Event for port 8

2017-07-18T04:22:52.484Z cpu6:35925)<6>xhci_hcd 0000:00:14.0: resume root hub

2017-07-18T04:22:52.484Z cpu6:35925)<6>xhci_hcd 0000:00:14.0: handle_port_status: starting port polling.

2017-07-18T04:22:52.504Z cpu0:33315)<6>xhci_hcd 0000:00:14.0: clear port connect change, actual port 3 status = 0x1203

2017-07-18T04:22:52.615Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: Slot 1 output ctx = 0xdac2e000 (dma)

2017-07-18T04:22:52.615Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: Slot 1 input ctx = 0xdac30000 (dma)

2017-07-18T04:22:52.615Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: Set slot id 1 dcbaa entry 0x41092be97008 to 0xdac2e000

2017-07-18T04:22:52.615Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: set port reset, actual port 3 status = 0x1311

2017-07-18T04:22:52.615Z cpu6:35925)<6>xhci_hcd 0000:00:14.0: Port Status Change Event for port 8

2017-07-18T04:22:52.615Z cpu6:35925)<6>xhci_hcd 0000:00:14.0: handle_port_status: starting port polling.

2017-07-18T04:22:52.736Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: clear port reset change, actual port 3 status = 0x81203

2017-07-18T04:22:52.736Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: Set root hub portnum to 8

2017-07-18T04:22:52.736Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: Set fake root hub portnum to 4

2017-07-18T04:22:52.736Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: udev->tt = 0x0

2017-07-18T04:22:52.736Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: udev->ttport = 0x0

2017-07-18T04:22:52.736Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: Slot ID 1 Input Context:

2017-07-18T04:22:52.736Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: Slot ID 1 Input Context:

2017-07-18T04:22:52.736Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: Slot ID 1 Output Context:

2017-07-18T04:22:52.736Z cpu5:33341)<6>usb 4-4: new SuperSpeed USB device number 2 using xhci_hcd

2017-07-18T04:22:52.757Z cpu6:35930)<6>xhci_hcd 0000:00:14.0: Waiting for status stage event

2017-07-18T04:22:52.757Z cpu6:35930)<6>xhci_hcd 0000:00:14.0: Waiting for status stage event

2017-07-18T04:22:52.757Z cpu6:35930)<6>xhci_hcd 0000:00:14.0: Waiting for status stage event

2017-07-18T04:22:52.757Z cpu6:35930)<6>xhci_hcd 0000:00:14.0: Waiting for status stage event

2017-07-18T04:22:52.757Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: add ep 0x84, slot id 1, new drop flags = 0x0, new add flags = 0x200

2017-07-18T04:22:52.757Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: add ep 0x1, slot id 1, new drop flags = 0x0, new add flags = 0x204

2017-07-18T04:22:52.757Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: xhci_check_bandwidth called for udev 0x4109320f3a10

2017-07-18T04:22:52.757Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: New Input Control Context:

2017-07-18T04:22:52.757Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: Output context after successful config ep cmd:

2017-07-18T04:22:52.758Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: clear port warm(BH) reset change, actual port 3 status = 0x1203

2017-07-18T04:22:52.876Z cpu0:33302)<6>xhci_hcd 0000:00:14.0: xhci_hub_status_data: stopping port polling.

/var/log # cat vmkernel.log | grep 0000:00:14.0:

2017-07-18T03:35:23.513Z cpu5:33343)<6> 0000:00:14.0: USB3.0 ports routing map: 0x0 (was x00)

2017-07-18T03:35:23.557Z cpu0:33344)<6>xhci_hcd 0000:00:14.0: xHCI Host Controller

2017-07-18T03:35:23.557Z cpu0:33344)<6>xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3

2017-07-18T03:35:23.558Z cpu0:33344)<6>xhci_hcd 0000:00:14.0: irq 16, io mem 0xf7d20000

2017-07-18T03:35:23.558Z cpu0:33344)WARNING: LinPCI: LinuxPCI_EnableMSIX:886: 0000:00:14.0: Interrupt allocation failed with Failure

2017-07-18T03:35:23.558Z cpu0:33344)<6>xhci_hcd 0000:00:14.0: xHCI Host Controller

2017-07-18T03:35:23.558Z cpu0:33344)<6>xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4

2017-07-18T03:56:42.904Z cpu5:33340)<6> 0000:00:14.0: USB 3.0 ports that are now enabled under xHCI: 0xf

2017-07-18T03:56:42.904Z cpu5:33340)<6> 0000:00:14.0: USB 2.0 ports that are now switched over to xHCI: 0xf

2017-07-18T03:56:43.464Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: xHCI Host Controller

2017-07-18T03:56:43.464Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3

2017-07-18T03:56:43.464Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: Resetting HCD

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: Reset complete

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: Enabling 64-bit DMA addresses.

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: Calling HCD init

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: Called HCD init

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: hcc params 0x20007181 hci version 0x100 quirks 0x0000b930

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: Got SBRN 48

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: Finished xhci_pci_reinit

2017-07-18T03:56:43.465Z cpu6:33343)WARNING: LinPCI: LinuxPCI_EnableMSIX:886: 0000:00:14.0: Interrupt allocation failed with Failure

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: Command ring memory map follows:

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: ERST memory map follows:

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: Event ring:

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: set port power, actual port 0 status = 0x2a0

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: set port power, actual port 1 status = 0x2a0

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: set port power, actual port 2 status = 0x2a0

2017-07-18T03:56:43.465Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: set port power, actual port 3 status = 0x2a0

2017-07-18T03:56:43.466Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: xHCI Host Controller

2017-07-18T03:56:43.466Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4

2017-07-18T03:56:43.466Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: set port power, actual port 0 status = 0x802a0

2017-07-18T03:56:43.466Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: set port power, actual port 1 status = 0x802a0

2017-07-18T03:56:43.466Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: set port power, actual port 2 status = 0x802a0

2017-07-18T03:56:43.466Z cpu6:33343)<6>xhci_hcd 0000:00:14.0: set port power, actual port 3 status = 0x802a0

2017-07-18T03:56:43.566Z cpu1:33318)<6>xhci_hcd 0000:00:14.0: clear port warm(BH) reset change, actual port 0 status = 0x2a0

2017-07-18T03:56:43.566Z cpu1:33318)<6>xhci_hcd 0000:00:14.0: clear port warm(BH) reset change, actual port 1 status = 0x2a0

2017-07-18T03:56:43.566Z cpu1:33318)<6>xhci_hcd 0000:00:14.0: clear port warm(BH) reset change, actual port 2 status = 0x2a0

2017-07-18T03:56:43.566Z cpu1:33318)<6>xhci_hcd 0000:00:14.0: clear port warm(BH) reset change, actual port 3 status = 0x2a0

2017-07-18T03:56:46.520Z cpu4:33305)<6>xhci_hcd 0000:00:14.0: set port remote wake mask, actual port 0 status = 0xe0002a0

2017-07-18T03:56:46.520Z cpu4:33305)<6>xhci_hcd 0000:00:14.0: set port remote wake mask, actual port 1 status = 0xe0002a0

2017-07-18T03:56:46.520Z cpu4:33305)<6>xhci_hcd 0000:00:14.0: set port remote wake mask, actual port 2 status = 0xe0002a0

2017-07-18T03:56:46.520Z cpu4:33305)<6>xhci_hcd 0000:00:14.0: set port remote wake mask, actual port 3 status = 0xe0002a0

2017-07-18T04:05:59.039Z cpu2:33310)<6>xhci_hcd 0000:00:14.0: set port remote wake mask, actual port 0 status = 0xe0002a0

2017-07-18T04:05:59.039Z cpu2:33310)<6>xhci_hcd 0000:00:14.0: set port remote wake mask, actual port 1 status = 0xe0002a0

2017-07-18T04:05:59.039Z cpu2:33310)<6>xhci_hcd 0000:00:14.0: set port remote wake mask, actual port 2 status = 0xe0002a0

2017-07-18T04:05:59.039Z cpu2:33310)<6>xhci_hcd 0000:00:14.0: set port remote wake mask, actual port 3 status = 0xe0002a0

2017-07-18T04:22:52.484Z cpu6:35925)<6>xhci_hcd 0000:00:14.0: Port Status Change Event for port 8

2017-07-18T04:22:52.484Z cpu6:35925)<6>xhci_hcd 0000:00:14.0: resume root hub

2017-07-18T04:22:52.484Z cpu6:35925)<6>xhci_hcd 0000:00:14.0: handle_port_status: starting port polling.

2017-07-18T04:22:52.504Z cpu0:33315)<6>xhci_hcd 0000:00:14.0: clear port connect change, actual port 3 status = 0x1203

2017-07-18T04:22:52.615Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: Slot 1 output ctx = 0xdac2e000 (dma)

2017-07-18T04:22:52.615Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: Slot 1 input ctx = 0xdac30000 (dma)

2017-07-18T04:22:52.615Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: Set slot id 1 dcbaa entry 0x41092be97008 to 0xdac2e000

2017-07-18T04:22:52.615Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: set port reset, actual port 3 status = 0x1311

2017-07-18T04:22:52.615Z cpu6:35925)<6>xhci_hcd 0000:00:14.0: Port Status Change Event for port 8

2017-07-18T04:22:52.615Z cpu6:35925)<6>xhci_hcd 0000:00:14.0: handle_port_status: starting port polling.

2017-07-18T04:22:52.736Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: clear port reset change, actual port 3 status = 0x81203

2017-07-18T04:22:52.736Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: Set root hub portnum to 8

2017-07-18T04:22:52.736Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: Set fake root hub portnum to 4

2017-07-18T04:22:52.736Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: udev->tt = 0x0

2017-07-18T04:22:52.736Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: udev->ttport = 0x0

2017-07-18T04:22:52.736Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: Slot ID 1 Input Context:

2017-07-18T04:22:52.736Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: Slot ID 1 Input Context:

2017-07-18T04:22:52.736Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: Slot ID 1 Output Context:

2017-07-18T04:22:52.757Z cpu6:35930)<6>xhci_hcd 0000:00:14.0: Waiting for status stage event

2017-07-18T04:22:52.757Z cpu6:35930)<6>xhci_hcd 0000:00:14.0: Waiting for status stage event

2017-07-18T04:22:52.757Z cpu6:35930)<6>xhci_hcd 0000:00:14.0: Waiting for status stage event

2017-07-18T04:22:52.757Z cpu6:35930)<6>xhci_hcd 0000:00:14.0: Waiting for status stage event

2017-07-18T04:22:52.757Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: add ep 0x84, slot id 1, new drop flags = 0x0, new add flags = 0x200

2017-07-18T04:22:52.757Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: add ep 0x1, slot id 1, new drop flags = 0x0, new add flags = 0x204

2017-07-18T04:22:52.757Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: xhci_check_bandwidth called for udev 0x4109320f3a10

2017-07-18T04:22:52.757Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: New Input Control Context:

2017-07-18T04:22:52.757Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: Output context after successful config ep cmd:

2017-07-18T04:22:52.758Z cpu5:33341)<6>xhci_hcd 0000:00:14.0: clear port warm(BH) reset change, actual port 3 status = 0x1203

2017-07-18T04:22:52.876Z cpu0:33302)<6>xhci_hcd 0000:00:14.0: xhci_hub_status_data: stopping port polling.

/var/log # cat vmkernel.log | grep usb

VMB: 212: name: /ohci_usb.v00

VMB: 212: name: /uhci_usb.v00

2017-07-18T03:35:16.455Z cpu0:32768)VisorFSTar: 1960: ohci_usb.v00 for 0xe894 bytes

2017-07-18T03:35:16.458Z cpu0:32768)VisorFSTar: 1960: uhci_usb.v00 for 0xe62b bytes

2017-07-18T03:35:23.413Z cpu4:33341)Loading module usb ...

2017-07-18T03:35:23.413Z cpu4:33341)Elf: 1861: module usb has license GPL

2017-07-18T03:35:23.415Z cpu4:33341)module heap vmklnx_usb: creation succeeded. id = 0x410933bde000

2017-07-18T03:35:23.470Z cpu0:33341)<6>usbcore: registered new interface driver usbfs

2017-07-18T03:35:23.470Z cpu0:33341)<6>usbcore: registered new interface driver hub

2017-07-18T03:35:23.471Z cpu0:33341)<6>usbcore: registered new device driver usb

2017-07-18T03:35:23.471Z cpu0:33341)Mod: 4780: Initialization of usb succeeded with module ID 4124.

2017-07-18T03:35:23.471Z cpu0:33341)usb loaded successfully.

2017-07-18T03:35:23.487Z cpu5:33343)IRQ: 540: 0x31 <ehci_hcd:usb1> sharable, flags 0x10

2017-07-18T03:35:23.513Z cpu5:33343)<6>usb usb1: New USB device found, idVendor=1d6b, idProduct=0002

2017-07-18T03:35:23.513Z cpu5:33343)<6>usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1

2017-07-18T03:35:23.513Z cpu5:33343)<6>usb usb1: Product: EHCI Host Controller

2017-07-18T03:35:23.513Z cpu5:33343)<6>usb usb1: Manufacturer: vmklinux_9 ehci_hcd

2017-07-18T03:35:23.513Z cpu5:33343)<6>usb usb1: SerialNumber: 0000:00:1a.0

2017-07-18T03:35:23.513Z cpu5:33343)<6>usb usb1: device is not available for passthrough

2017-07-18T03:35:23.513Z cpu5:33343)<6>usb usb1: usbfs: registered usb0101

2017-07-18T03:35:23.517Z cpu5:33343)IRQ: 540: 0x34 <ehci_hcd:usb2> sharable, flags 0x10

2017-07-18T03:35:23.543Z cpu5:33343)<6>usb usb2: New USB device found, idVendor=1d6b, idProduct=0002

2017-07-18T03:35:23.543Z cpu5:33343)<6>usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1

2017-07-18T03:35:23.543Z cpu5:33343)<6>usb usb2: Product: EHCI Host Controller

2017-07-18T03:35:23.543Z cpu5:33343)<6>usb usb2: Manufacturer: vmklinux_9 ehci_hcd

2017-07-18T03:35:23.543Z cpu5:33343)<6>usb usb2: SerialNumber: 0000:00:1d.0

2017-07-18T03:35:23.543Z cpu5:33343)<6>usb usb2: device is not available for passthrough

2017-07-18T03:35:23.543Z cpu5:33343)<6>usb usb2: usbfs: registered usb0201

2017-07-18T03:35:23.558Z cpu0:33344)IRQ: 540: 0x31 <xhci_hcd:usb3> sharable, flags 0x10

2017-07-18T03:35:23.558Z cpu0:33344)<6>usb usb3: New USB device found, idVendor=1d6b, idProduct=0002

2017-07-18T03:35:23.558Z cpu0:33344)<6>usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1

2017-07-18T03:35:23.558Z cpu0:33344)<6>usb usb3: Product: xHCI Host Controller

2017-07-18T03:35:23.558Z cpu0:33344)<6>usb usb3: Manufacturer: vmklinux_9 xhci_hcd

2017-07-18T03:35:23.558Z cpu0:33344)<6>usb usb3: SerialNumber: 0000:00:14.0

2017-07-18T03:35:23.558Z cpu0:33344)<6>usb usb3: device is not available for passthrough

2017-07-18T03:35:23.558Z cpu0:33344)<6>usb usb3: usbfs: registered usb0301

2017-07-18T03:35:23.558Z cpu0:33344)<6>usb usb4: New USB device found, idVendor=1d6b, idProduct=0003

2017-07-18T03:35:23.558Z cpu0:33344)<6>usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1

2017-07-18T03:35:23.558Z cpu0:33344)<6>usb usb4: Product: xHCI Host Controller

2017-07-18T03:35:23.558Z cpu0:33344)<6>usb usb4: Manufacturer: vmklinux_9 xhci_hcd

2017-07-18T03:35:23.558Z cpu0:33344)<6>usb usb4: SerialNumber: 0000:00:14.0

2017-07-18T03:35:23.558Z cpu0:33344)<6>usb usb4: device is not available for passthrough

2017-07-18T03:35:23.558Z cpu0:33344)<6>usb usb4: usbfs: registered usb0401

2017-07-18T03:35:23.565Z cpu0:33345)<6>usbcore: registered new interface driver usbhid

2017-07-18T03:35:23.826Z cpu3:33361)Loading module usb-storage ...

2017-07-18T03:35:23.826Z cpu3:33361)Elf: 1861: module usb-storage has license GPL

2017-07-18T03:35:23.827Z cpu3:33361)module heap vmklnx_usb_storage: creation succeeded. id = 0x410955067000

2017-07-18T03:35:23.841Z cpu2:33342)<6>usb 1-1: new high speed USB device number 2 using ehci_hcd

2017-07-18T03:35:24.000Z cpu2:33342)<6>usb 1-1: New USB device found, idVendor=8087, idProduct=0024

2017-07-18T03:35:24.000Z cpu2:33342)<6>usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0

2017-07-18T03:35:24.002Z cpu1:33342)<6>usb 1-1: device is not available for passthrough

2017-07-18T03:35:24.002Z cpu1:33342)<6>usb 1-1: usbfs: registered usb0102

2017-07-18T03:35:24.125Z cpu2:33342)<6>usb 2-1: new high speed USB device number 2 using ehci_hcd

2017-07-18T03:35:24.285Z cpu2:33342)<6>usb 2-1: New USB device found, idVendor=8087, idProduct=0024

2017-07-18T03:35:24.285Z cpu2:33342)<6>usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0

2017-07-18T03:35:24.287Z cpu0:33342)<6>usb 2-1: device is not available for passthrough

2017-07-18T03:35:24.287Z cpu0:33342)<6>usb 2-1: usbfs: registered usb0202

2017-07-18T03:35:24.372Z cpu2:33342)<6>usb 1-1.2: new full speed USB device number 3 using ehci_hcd

2017-07-18T03:35:24.494Z cpu1:33342)<6>usb 1-1.2: New USB device found, idVendor=1997, idProduct=2433

2017-07-18T03:35:24.494Z cpu1:33342)<6>usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0

2017-07-18T03:35:24.494Z cpu1:33342)<6>usb 1-1.2: Product: mini keyboard

2017-07-18T03:35:24.494Z cpu1:33342)<6>usb 1-1.2: Manufacturer:

2017-07-18T03:35:24.496Z cpu1:33342)<6>generic-usb 0003:1997:2433.0001: input: USB HID v1.01 Keyboard [ mini keyboard] on usb-0000:00:1a.0-1.2/input0

2017-07-18T03:35:24.496Z cpu1:33342)<6>usbhid 1-1.2:1.0: interface is claimed by usbhid

2017-07-18T03:35:24.496Z cpu1:33342)<6>usb 1-1.2: device is not available for passthrough

2017-07-18T03:35:24.498Z cpu1:33342)<6>generic-usb 0003:1997:2433.0002: input: USB HID v1.01 Mouse [ mini keyboard] on usb-0000:00:1a.0-1.2/input1

2017-07-18T03:35:24.498Z cpu1:33342)<6>usbhid 1-1.2:1.0: interface is claimed by usbhid

2017-07-18T03:35:24.498Z cpu1:33342)<6>usb 1-1.2: device is not available for passthrough

2017-07-18T03:35:24.498Z cpu1:33342)<6>usb 1-1.2: usbfs: registered usb0103

2017-07-18T03:35:24.498Z cpu1:33361)<6>usbcore: registered new interface driver usb-storage

2017-07-18T03:35:24.498Z cpu1:33361)Mod: 4780: Initialization of usb-storage succeeded with module ID 4139.

2017-07-18T03:35:24.498Z cpu1:33361)usb-storage loaded successfully.

2017-07-18T03:35:25.671Z cpu1:33320)<6>usb usb3: suspended

2017-07-18T03:35:26.543Z cpu4:33307)<6>usb 2-1: suspended

2017-07-18T03:35:26.729Z cpu0:33311)<6>usb usb4: suspended

2017-07-18T03:35:28.615Z cpu0:33320)<6>usb usb2: suspended

2017-07-18T03:37:53.702Z cpu7:33984)<6>usb passthrough enabled; all eligible devices will be unclaimed by kernel drivers

2017-07-18T03:55:58.066Z cpu2:38955)<6>usb passthrough disabled

VMB: 212: name: /ohci_usb.v00

VMB: 212: name: /uhci_usb.v00

2017-07-18T03:56:36.451Z cpu0:32768)VisorFSTar: 1960: ohci_usb.v00 for 0xe894 bytes

2017-07-18T03:56:36.454Z cpu0:32768)VisorFSTar: 1960: uhci_usb.v00 for 0xe62b bytes

2017-07-18T03:56:42.900Z cpu5:33340)Loading module usb ...

2017-07-18T03:56:42.900Z cpu5:33340)Elf: 1861: module usb has license GPL

2017-07-18T03:56:42.902Z cpu5:33340)module heap vmklnx_usb: creation succeeded. id = 0x4109320e4000

2017-07-18T03:56:43.078Z cpu5:33340)<6>usbcore: registered new interface driver usbfs

2017-07-18T03:56:43.078Z cpu5:33340)<6>usbcore: registered new interface driver hub

2017-07-18T03:56:43.079Z cpu5:33340)<6>usbcore: registered new device driver usb

2017-07-18T03:56:43.079Z cpu5:33340)Mod: 4780: Initialization of usb succeeded with module ID 4128.

2017-07-18T03:56:43.079Z cpu5:33340)usb loaded successfully.

2017-07-18T03:56:43.095Z cpu5:33342)IRQ: 540: 0x31 <ehci_hcd:usb1> sharable, flags 0x10

2017-07-18T03:56:43.425Z cpu5:33342)<6>usb usb1: New USB device found, idVendor=1d6b, idProduct=0002

2017-07-18T03:56:43.425Z cpu5:33342)<6>usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1

2017-07-18T03:56:43.425Z cpu5:33342)<6>usb usb1: Product: EHCI Host Controller

2017-07-18T03:56:43.425Z cpu5:33342)<6>usb usb1: Manufacturer: vmklinux_9 ehci_hcd

2017-07-18T03:56:43.425Z cpu5:33342)<6>usb usb1: SerialNumber: 0000:00:1a.0

2017-07-18T03:56:43.425Z cpu5:33342)<6>usb usb1: device is not available for passthrough

2017-07-18T03:56:43.425Z cpu5:33342)<6>usb usb1: usbfs: registered usb0101

2017-07-18T03:56:43.429Z cpu5:33342)IRQ: 540: 0x34 <ehci_hcd:usb2> sharable, flags 0x10

2017-07-18T03:56:43.455Z cpu5:33342)<6>usb usb2: New USB device found, idVendor=1d6b, idProduct=0002

2017-07-18T03:56:43.455Z cpu5:33342)<6>usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1

2017-07-18T03:56:43.455Z cpu5:33342)<6>usb usb2: Product: EHCI Host Controller

2017-07-18T03:56:43.455Z cpu5:33342)<6>usb usb2: Manufacturer: vmklinux_9 ehci_hcd

2017-07-18T03:56:43.455Z cpu5:33342)<6>usb usb2: SerialNumber: 0000:00:1d.0

2017-07-18T03:56:43.455Z cpu5:33342)<6>usb usb2: device is not available for passthrough

2017-07-18T03:56:43.455Z cpu5:33342)<6>usb usb2: usbfs: registered usb0201

2017-07-18T03:56:43.465Z cpu6:33343)<6>usb usb3: New USB device found, idVendor=1d6b, idProduct=0002

2017-07-18T03:56:43.465Z cpu6:33343)<6>usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1

2017-07-18T03:56:43.465Z cpu6:33343)<6>usb usb3: Product: xHCI Host Controller

2017-07-18T03:56:43.465Z cpu6:33343)<6>usb usb3: Manufacturer: vmklinux_9 xhci-hcd

2017-07-18T03:56:43.465Z cpu6:33343)<6>usb usb3: SerialNumber: 0000:00:14.0

2017-07-18T03:56:43.465Z cpu6:33343)<6>usb usb3: device is not available for passthrough

2017-07-18T03:56:43.465Z cpu6:33343)<6>usb usb3: usbfs: registered usb0301

2017-07-18T03:56:43.466Z cpu6:33343)<6>usb usb4: New USB device found, idVendor=1d6b, idProduct=0003

2017-07-18T03:56:43.466Z cpu6:33343)<6>usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1

2017-07-18T03:56:43.466Z cpu6:33343)<6>usb usb4: Product: xHCI Host Controller

2017-07-18T03:56:43.466Z cpu6:33343)<6>usb usb4: Manufacturer: vmklinux_9 xhci-hcd

2017-07-18T03:56:43.466Z cpu6:33343)<6>usb usb4: SerialNumber: 0000:00:14.0

2017-07-18T03:56:43.466Z cpu6:33343)<6>usb usb4: device is not available for passthrough

2017-07-18T03:56:43.466Z cpu6:33343)<6>usb usb4: usbfs: registered usb0401

2017-07-18T03:56:43.476Z cpu3:33344)<6>usbcore: registered new interface driver usbhid

2017-07-18T03:56:43.753Z cpu3:33341)<6>usb 1-1: new high speed USB device number 2 using ehci_hcd

2017-07-18T03:56:43.782Z cpu1:33360)Loading module usb-storage ...

2017-07-18T03:56:43.782Z cpu1:33360)Elf: 1861: module usb-storage has license GPL

2017-07-18T03:56:43.783Z cpu1:33360)module heap vmklnx_usb_storage: creation succeeded. id = 0x41092da4e000

2017-07-18T03:56:43.913Z cpu3:33341)<6>usb 1-1: New USB device found, idVendor=8087, idProduct=0024

2017-07-18T03:56:43.913Z cpu3:33341)<6>usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0

2017-07-18T03:56:43.914Z cpu3:33341)<6>usb 1-1: device is not available for passthrough

2017-07-18T03:56:43.914Z cpu3:33341)<6>usb 1-1: usbfs: registered usb0102

2017-07-18T03:56:44.037Z cpu3:33341)<6>usb 2-1: new high speed USB device number 2 using ehci_hcd

2017-07-18T03:56:44.197Z cpu3:33341)<6>usb 2-1: New USB device found, idVendor=8087, idProduct=0024

2017-07-18T03:56:44.197Z cpu3:33341)<6>usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0

2017-07-18T03:56:44.198Z cpu3:33341)<6>usb 2-1: device is not available for passthrough

2017-07-18T03:56:44.198Z cpu3:33341)<6>usb 2-1: usbfs: registered usb0202

2017-07-18T03:56:44.283Z cpu3:33341)<6>usb 1-1.2: new full speed USB device number 3 using ehci_hcd

2017-07-18T03:56:44.406Z cpu3:33341)<6>usb 1-1.2: New USB device found, idVendor=1997, idProduct=2433

2017-07-18T03:56:44.406Z cpu3:33341)<6>usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0

2017-07-18T03:56:44.406Z cpu3:33341)<6>usb 1-1.2: Product: mini keyboard

2017-07-18T03:56:44.406Z cpu3:33341)<6>usb 1-1.2: Manufacturer:

2017-07-18T03:56:44.408Z cpu3:33341)<6>generic-usb 0003:1997:2433.0001: input: USB HID v1.01 Keyboard [ mini keyboard] on usb-0000:00:1a.0-1.2/input0

2017-07-18T03:56:44.408Z cpu3:33341)<6>usbhid 1-1.2:1.0: interface is claimed by usbhid

2017-07-18T03:56:44.408Z cpu3:33341)<6>usb 1-1.2: device is not available for passthrough

2017-07-18T03:56:44.410Z cpu3:33341)<6>generic-usb 0003:1997:2433.0002: input: USB HID v1.01 Mouse [ mini keyboard] on usb-0000:00:1a.0-1.2/input1

2017-07-18T03:56:44.410Z cpu3:33341)<6>usbhid 1-1.2:1.0: interface is claimed by usbhid

2017-07-18T03:56:44.410Z cpu3:33341)<6>usb 1-1.2: device is not available for passthrough

2017-07-18T03:56:44.410Z cpu3:33341)<6>usb 1-1.2: usbfs: registered usb0103

2017-07-18T03:56:44.410Z cpu1:33360)<6>usbcore: registered new interface driver usb-storage

2017-07-18T03:56:44.410Z cpu1:33360)Mod: 4780: Initialization of usb-storage succeeded with module ID 4143.

2017-07-18T03:56:44.410Z cpu1:33360)usb-storage loaded successfully.

2017-07-18T03:56:45.697Z cpu2:33317)<6>usb usb3: suspended

2017-07-18T03:56:46.520Z cpu4:33305)<6>usb usb4: suspended

2017-07-18T03:56:46.635Z cpu1:33307)<6>usb 2-1: suspended

2017-07-18T03:56:48.697Z cpu4:33306)<6>usb usb2: suspended

2017-07-18T03:57:01.614Z cpu0:33759)<6>usb passthrough enabled; all eligible devices will be unclaimed by kernel drivers

2017-07-18T04:05:56.565Z cpu2:36719)<6>usb usb2: resumed

2017-07-18T04:05:56.627Z cpu0:36719)<6>usb 2-1: resumed

2017-07-18T04:05:56.649Z cpu1:36719)<6>usb usb4: resumed

2017-07-18T04:05:56.670Z cpu2:36719)<6>usb usb3: resumed

2017-07-18T04:05:59.010Z cpu1:33309)<6>usb usb3: suspended

2017-07-18T04:05:59.039Z cpu2:33310)<6>usb usb4: suspended

2017-07-18T04:05:59.070Z cpu7:33314)<6>usb 2-1: suspended

2017-07-18T04:06:01.860Z cpu0:33307)<6>usb usb2: suspended

2017-07-18T04:22:52.504Z cpu0:33315)<6>usb usb4: resumed

2017-07-18T04:22:52.736Z cpu5:33341)<6>usb 4-4: new SuperSpeed USB device number 2 using xhci_hcd

2017-07-18T04:22:52.757Z cpu5:33341)<6>usb 4-4: New USB device found, idVendor=067b, idProduct=2773

2017-07-18T04:22:52.757Z cpu5:33341)<6>usb 4-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3

2017-07-18T04:22:52.757Z cpu5:33341)<6>usb 4-4: Product: ATAPI-6 Bridge Controller

2017-07-18T04:22:52.757Z cpu5:33341)<6>usb 4-4: Manufacturer: Prolific Technology Inc.

2017-07-18T04:22:52.757Z cpu5:33341)<6>usb 4-4: SerialNumber: 0123456789000000005

2017-07-18T04:22:52.757Z cpu5:33341)<6>usb 4-4: Vendor: 0x067b, Product: 0x2773, Revision: 0x0100

2017-07-18T04:22:52.757Z cpu5:33341)<6>usb 4-4: Interface Subclass: 0x06, Protocol: 0x50

2017-07-18T04:22:52.758Z cpu5:33341)WARNING: LinScsiLLD: scsi_add_host:573: vmkAdapter (usb-storage) sgMaxEntries rounded to 255. Reported size was 65535

2017-07-18T04:22:52.758Z cpu5:33341)<6>usb-storage 4-4:1.0: interface is claimed by usb-storage

2017-07-18T04:22:52.758Z cpu5:33341)<6>usb 4-4: device is not available for passthrough

2017-07-18T04:22:52.758Z cpu5:33341)<6>usb 4-4: usbfs: registered usb0402

2017-07-18T04:22:53.832Z cpu0:39412)usb-storage: detected SCSI revision number 0 on vmhba37

2017-07-18T04:22:53.832Z cpu0:39412)usb-storage: patching inquiry data to change SCSI revision number from 0 to 2 on vmhba37

2017-07-18T04:22:53.832Z cpu0:39412)usb-storage: patching inquiry data to change removable media bit from 'off' to 'on' on vmhba37

2017-07-18T04:22:53.832Z cpu0:39412)usb-storage: setting peripheral qualifier to 'not connected' on vmhba37

2017-07-18T04:22:53.832Z cpu1:33305)<6>usb-storage 4-4:1.0: unclaiming vmhba37

2017-07-18T04:22:53.833Z cpu0:33305)<6>usb 4-4: device is available for passthrough

2017-07-18T04:29:22.733Z cpu4:40431)<6>usb usb2: resumed

2017-07-18T04:29:22.796Z cpu2:40431)<6>usb 2-1: resumed

2017-07-18T04:29:22.817Z cpu2:40431)<6>usb usb3: resumed

2017-07-18T04:29:25.078Z cpu3:33313)<6>usb usb3: suspended

2017-07-18T04:29:25.098Z cpu0:33303)<6>usb 2-1: suspended

2017-07-18T04:29:27.138Z cpu3:33315)<6>usb usb2: suspended

Your ESXi host and vCenter are on the same subnet? And your vCenter is running on Windows or it is an appliance? If running on Windows, make sure Windows firewall is disabled or allow traffic on port 902 UDP. For additional troubleshooting check the following VMware KB article: ESXi/ESX host disconnects from vCenter Server after adding or connecting it to the inventory (2040630) | VMware KB

The device section in my esx.conf has only this:

/device/000:000:31.2/vmkname = "vmhba0"

/device/000:001:00.0/owner = "passthru"

/device/000:001:00.0/device = "1142"

/device/000:001:00.0/vendor = "1b21"

/device/000:000:25.0/vmkname = "vmnic0"

Since you're using Standard switch, can you confirm if the VLAN 103 is assigned to the correct port group on the destination faulty host? And can you confirm if the physical switch port where hosts are connected shared the same exact VLAN configuration?

Thanks! Metal is enabled by default but if it causes rendering issues it can be disabled. In my testing it's been working out just fine, but I'm very likely not exercising it as much as it could be.

Performance wise we've seen many areas improve but also some areas that were slower, so we know there's work to be done, and that work is underway.

It does not change the DX or OpenGL version inside the guest tho, the gains we're seeing are around performance, "correctness" and energy consumption.

I also found this in the vmkernel.log:

2017-07-18T03:56:43.465Z cpu6:33343)WARNING: VMK_PCI: 705: device 0000:00:14.0 failed to allocate 8 MSIX interrupts

2017-07-18T03:56:43.465Z cpu6:33343)WARNING: LinPCI: LinuxPCI_EnableMSIX:886: 0000:00:14.0: Interrupt allocation failed with Failure

VMware Support,

I will switch to another product if I don't get a response on this. It's been more than a month that I have posted this and no replies so far.

Appreciate any help here.

Thanks!

Andre

Totalmente posible. Hasta 64 niveles. Mira el enlace inferior:

Nested Virtualization

A common question I get from customers and partners that are beginning their dive into the VMware Validated Designs is around the placement of the edge components.  This is often because these individuals have been doing some fantastic due diligence by reading not only the VMware Validated Designs, but also the NSX for vSphere documentation and the NSX Design Guide.

After reading these, a general concern is that the documentation and guide reference a “Management and Edge” cluster construct whereas the VMware Validated Designs reference an initial “Shared Edge and Compute Pod.”

So, why the difference?

First off,  the documentation and design guide for NSX is a starting point and seeks to address specific use cases. In turn, the VMware Validated Designs, such as, the VVD for Software-Defined Data Center and the VVD for Remote Office/Branch Office address their own use cases. That said, these designs have absolute synergies with and are fully supported by VMware’s Network and Security Business Unit.

The biggest thing to understand is that the VMware Validated Designs use NSX for both the management and compute workloads. When we crafted the designs, we made some key design decisions on how to construct edge services for the management domain and the workload domains. We could have combined the edge into either one of the two; however, we specifically decided to place edge services for workloads alongside the compute clusters for a couple reasons:

1. From a security and scale perspective, the design seeks to isolate the north/south traffic of the management pod for the SDDC from the tenant compute pods.
   
   
2. As compute clusters scale out, so can the NSX deployment. With on-demand network and security services for the tenant workloads automated by vRealize Automation, the design would have needed to scale the management pod to meet the potential NSX requirements for these components. Instead, we made a key decision to have the management pod isolated and sized to run the SDDC stack optimally.

Since an NSX Manager can be associated with one, and only one, vCenter Server the NSX Controllers and any ESGs must be deployed into a cluster that the associated vCenter Server instance manages.

As such, we created a management domain and tenant workload domain, each with their own instance of NSX Manager, NSX Controllers, etc.

The result is:

1. A management pod with its own vCenter Server associated with its own NSX Manager instance. These are instantiated within the management pod’s cluster itself.
   
   
2. A shared edge and compute pod with its own vCenter Server associated with it own NSX Manager instance. The NSX Manager is instantiated within the management domain cluster whereas, due to the one-to-one relationship, the NSX Controllers and any ESGs must for this pod are deployed into an initial shared edge and compute cluster that the associated vCenter Server instance manages.  Now, as organization grows beyond the capacity of initial shared cluster, any new compute only clusters for workloads will be deployed under the same vCenter Server instance and consume network and security services that are isolated from management.

Now,  if you step back for a moment, and look at it at it a little differently, you’ll notice that we technically implement a “Management and Edge” pod and a shared “Edge and Compute” pod.

Whoa, how so?

Management (and Edge) Pod - In the management cluster, we utilize NSX to provide network and security services to the management stack - think distributed logical routing, distributed firewall, north/south routing, and policies for the management stack solutions like vRealize Operations and vRealize Automation. Here, we have an NSX Manager - associated with the management vCenter Server instance - which deploys two NSX Edge Services Gateways (ESGs) for north/south routing, two highly-available pairs of ESGs to provide load balancing services for the Platform Services Controllers and the vRealize Operations and Automation components. Now, we don’t explicitly call it a “Management and Edge” pod since these ESGs are only service the management components, and don’t provide edge services to tenant workloads. We simple call it the "Management" pod.

Shared Edge and Compute Pod - In the initial shared edge and compute pod we also use NSX to provide network and security services to the tenant workloads. That is, of course, distributed logical routing, distribute firewall, north/south routing, policies, and on-demand network services for the tenant workloads in the stack. Since an NSX Manager can be associated with one, and only one vCenter Server instance the NSX Controllers and any ESGs must be deployed into a cluster that the associated vCenter Server instance manages. So, here we have an NSX Manager associated with a separate vCenter Server instance that serves the tenant compute workloads only. Therefore, the only option is for ESGs to be here in the hence named Shared Edge and Compute Pod.

And, there you have it, this is why there may appear to be a difference between the NSX documentation and design guide and what’s documented in the VMware Validated Designs. But, rest assured, it’s completely validated, tested, and supported architecture base on key design decisions for our use cases.

Got comments on this topic? Simply reply to this thread.

Got more questions,? Post your questions in the communities. We’re here to help.

First: Essentially I'm a basic knowledge Linux admin.

I set up vCSA 6.5 backup using this great article:

https://vm.knutsson.it/2017/01/vmware-vcsa-6-5-scheduled-backup/

Running the script manually works perfect.

However, I am not able to get the crontab automatic job working. From my testing, it's not running at all.

Putty'd to VCSA.

Launched crontab -e

It looks like this:

0 19 * * * /usr/local/bin/vCSA-Backup.sh

Saved and get:

crontab: installing new crontab

No backup.

In an article, I saw this recommendation to see if cron is running the crontab at all:

0 19 * * * touch /tmp/a_command_has_run

This makes a file in /tmp apparently and I ran it manually to confirm it does.

No file created from the automated job.

When I look at time it is showing UTC, but in case this is a time zone issue, I checked after an overnight where it should have run in either time zone and got nothing.

So just in case of a time zone problem, I modified the crontab to make two files based on time.

0 17 * * * touch /tmp/a_command_has_run17

0 12 * * * touch /tmp/a_command_has_run12

Neither were made.

I would appreciate any direction on this issue.

Thanks!

Great, i can have two licences on the PSC? STD and Ent +?

I had the same issue.  I was typing in the username into the box.  instead I searched for the username clicked it and that fixed my problem. 

I have no option to download certificates when going to https://IP/vsphere-client.  I've tried downloading them from the web browser and manually installing them, but they don't appear to stay nor do they work.

Paul,

Did you ever figure this one out?  I've got the same problem on one of my vCenter servers.

It seems no matter what ive done to attempt to correct this issue.
We are still seeing the Error#1009 on our vcenter server.  which results in a blank page prompting a complete browser close to hopefully resolve the iss

below are the errors we are seeing,
has anyone experienced this issue?

There is no direct downgrade available - if you have VC/VCD DB backup taken prior to upgrade you can restore and that will work for sure.