srwsol's Posts

Excellent!   I upgraded from 6.5U1 to 6.7U3 this past weekend and found that I couldn't check my raid device status.  I downloaded the LSA software, installed it on Win7 (yes it installs on Win7 ... See more...
Excellent!   I upgraded from 6.5U1 to 6.7U3 this past weekend and found that I couldn't check my raid device status.  I downloaded the LSA software, installed it on Win7 (yes it installs on Win7 even though it doesn't list it as supported), and it all just worked with the stock lsi_mr3 and lsiprovider drivers that were installed by the 6.7U3 update process.   Looks like all the functionality that was present in the old Megaraid Storage Manager is here, and the bonus is that there isn't a fight each time getting the software to find the ESXi server.  P.S.  Has anyone gotten the email alerts to work?  I can't seem to get it to send any emails.  When I click test, it just comes back and nothing happens.  I run my own email server and I can verify that it saw nothing.  If I deliberately put in a bad IP address it says that it can't send the mail, so it's doing something. 
I ended up doing the upgrade via booting the iso image and doing the interactive upgrade, so I don't know whether or not the offline bundle would have worked. For those reading this thread in ... See more...
I ended up doing the upgrade via booting the iso image and doing the interactive upgrade, so I don't know whether or not the offline bundle would have worked. For those reading this thread in the future as a reference, please be aware that if you do the upgrade via the iso image you are not offered any choices regarding keeping third party vibs (i.e. the difference between doing an "install" upgrade versus an "update" upgrade that you have the option of specifying if you do it via the CLI); all it asks is for you to identify the hard drive you want to install to and if there is an esxi installation on it whether you want to do an upgrade or a clean install.  Also note that the nomenclature is different in the bootable iso versus the offline bundle.  In the offline bundle CLI "install" versus "update" means deleting all third party vibs versus keeping them, whereas in the bootable iso image it means the difference between wiping your installation completely and starting from scratch versus updating your installation while keeping all third party vibs.   As I said, it is apparently not possible to do an upgrade via the bootable iso and remove all third party vibs at the same time.  If you want that you must either use the offline bundle and do it via the CLI, or use the CLI to manually remove third party vibs before booting the iso. In my case I had already resolved the vib conflicts in my current installation before I booted the iso image, which involved removing the maclearn fling vib and removing and reinstalling the vmtools vib which was messed up as an artifact of a previous upgrade attempt a year ago.  I still had one third party vib, a SCSI raid driver, which the bootable iso upgrade left alone.  I still would have preferred to use the offline bundle to do the upgrade because you can perform a dry-run to see what's going to happen before you do it, whereas the bootable iso image doesn't give you that option or tell you what it's doing.  As I indicated in my initial post, the only reason I went this route is that the offline bundle indicated that it was only to be used for a 6.7 or 6.7u1 to 6.7u3 upgrade, and even though the dry-run of that offline bundle said it would successfully update my 6.5 installation, I didn't want to take the chance on trying it. _______________________________________________________________________________________________________ "Did you find this helpful? Let us know by completing this survey (takes 1 minute!)"
I looked over the matrix and the upgrade is supported, but it doesn't specify if I can do it via the offline bundles versus the bootable iso.   I fixed the dependency problems with 6.5U1 this eve... See more...
I looked over the matrix and the upgrade is supported, but it doesn't specify if I can do it via the offline bundles versus the bootable iso.   I fixed the dependency problems with 6.5U1 this evening and afterward I tried a dry-run of the 6.7 to 6.7U3 offline bundle and it said that it would install.  Not sure if that means it will really work though.   Also haven't investigated any bios issues yet.  Did you upgrade your bios because the hardware compatibility site said it was necessary, or did you try the upgrade and it wouldn't take?
Is it possible to upgrade from 6.5u1 to 6.7u3 using the latest offline bundle?  The name says 6.7-6.7u3, which implies that you can't, but I don't see anything in the release notes saying that yo... See more...
Is it possible to upgrade from 6.5u1 to 6.7u3 using the latest offline bundle?  The name says 6.7-6.7u3, which implies that you can't, but I don't see anything in the release notes saying that you can't.  The reason I want to do it that way is so that I can do a dry run first and see if there are any conflicts first, which I believe there might be as I tried an upgrade about a year ago and had to go back and I think it left some problems with the vib for the vmware tools.  I suppose I could go from 6.5 to 6.7 and then from 6.7 to 6.7u3, with different offline bundles, but if I do it that way I believe I'll lose the ability to get back to 6.5u1 if something goes wrong as I would have done two updates, thus erasing 6.5u1 from the bootbank backup. 
Hi folks: About 8 months ago I tried to upgrade my ESXi 6.5 to 6.7, but I had William Lam's DVIMaclearn vib installed and couldn't do the upgrade.  I gave up on it at the time and went about f... See more...
Hi folks: About 8 months ago I tried to upgrade my ESXi 6.5 to 6.7, but I had William Lam's DVIMaclearn vib installed and couldn't do the upgrade.  I gave up on it at the time and went about fixing the VM that was using it (a linux copy of OpenVPN that was doing bridge mode and needed promiscuous mode).   Now I was going back to see if I could prepare to upgrade from 6.5 to 6.7 and the first step was going to be to remove the DVIMaclearn vib, but it appears that the change management database is screwed up.  When I did a dry run of trying to remove the Maclearn vib I got this error: [root@intelserver:~] esxcli software vib remove --dry-run --vibname=esx-dvfilter-maclearn [DependencyError] VIB VMware_locker_tools-light_10.3.2.9925305-10176879 requires esx-version >= 6.6.0, but the requirement cannot be satisfied within the ImageProfile. Please refer to the log file for more details. [root@intelserver:~] I then read somewhere that if I manually upgraded the tools package that error would go away, so I downloaded the tools package, manually extracted the 6.5 vib and did a dry-run install in it, and got the following errors: [root@intelserver:~] esxcli software vib update --dry-run -v /tmp/VMware_locker_tools-light_6.5.0-10.2.5.8068406.vib [DependencyError] VIB VMware_locker_tools-light_10.3.2.9925305-10176879 requires esx-version >= 6.6.0, but the requirement cannot be satisfied within the ImageProfile. File path of '/usr/libexec/jumpstart/plugins/dvfilter-maclearn.json' is claimed by multiple non-overlay VIBs: {'VMware_bootbank_vmware-esx-dvfilter-maclearn_1.00-1.00', 'VMware_bootbank_esx-dvfilter-maclearn_6.5.0-0.0.4282379'} File path of '/usr/lib/vmware/vmkmod/dvfilter-maclearn' is claimed by multiple non-overlay VIBs: {'VMware_bootbank_vmware-esx-dvfilter-maclearn_1.00-1.00', 'VMware_bootbank_esx-dvfilter-maclearn_6.5.0-0.0.4282379'} Please refer to the log file for more details. [root@intelserver:~] So just for the heck of it I tried a dry-run on both using the -f option and it says it would have done the first one, and the second one it would have skipped I think, but I don't know if it would have fixed the dependency error or not: [root@intelserver:~] esxcli software vib remove -f --dry-run --vibname=esx-dvfilter-maclearn Removal Result    Message: Dryrun only, host not changed. The following installers will be applied: [LiveImageInstaller, BootBankInstaller]    Reboot Required: false    VIBs Installed:    VIBs Removed: VMware_bootbank_esx-dvfilter-maclearn_6.5.0-0.0.4282379    VIBs Skipped: [root@intelserver:~] [root@intelserver:~] esxcli software vib update --dry-run -f -v /tmp/VMware_locker_tools-light_6.5.0-10.2.5.8068406.vib Installation Result    Message: Dryrun only, host not changed. The following installers will be applied: []    Reboot Required: false    VIBs Installed:    VIBs Removed:    VIBs Skipped: VMware_locker_tools-light_6.5.0-10.2.5.8068406 [root@intelserver:~] So now I'm not sure how to proceed.  Should I only try forcing one of these first, and if so which one first, or should I do both, or something else?  I'm also not sure what happened on the original 6.6 attempt that resulted in this issue, as I thought I ended up backing out of the whole thing on reboot by going back to the previous version.  Suggestions welcome. Edit: I did some more playing around with vib remove --dry-run and it appears that no matter what vib I try to remove I get the same dependency errors, so I must conclude that these specific vibs aren't tied to each other in some way, or to any other vib, but rather are screwed up somehow in and of themselves and short of using -f, either to remove them, or force install something else without removing them, I'm not going to be able to update anything. I feel pretty good about force removing dvfilter-maclearn and vmware-esx-dvfilter-maclearn (I think this latter one is part of the original maclearn as it has a 2015 date on the vib where all the rest of the stuff is 2017 or later), as I don't believe they had any relationship to any other vibs.  I'm not so sure though about locker_tools_light though, especially when the dry-run on force updating it to a newer version shows that the update was skipped. Edit 2: After more research I find that the issue with the tools-light is an artifact from rolling back from 6.7 to 6.5.   The instructions in the release notes say to re-install the older version, but I apparently can't without force removing the current tools-light, and then because of the maclearn issue I'm would have to force install the 6.5 version afterward.  I'm thinking I'm going to have to do this first, and then tackle the maclearn dependency issue.  Does anyone know if this change management system somehow keeps track of the order you do things (i.e. does it matter which order I do things in if I have to use -f to make it happen)?
Wow.   This is a text book example of why one should never have anything that ESXi is dependent upon running as a virtual machine under ESXi.  
I know this is an old conversation, but I never did upgrade.  However, now I want to upgrade to 6.7 and of course I've got the same issue.  Unfortunately I've got the essentials bundle, so I can'... See more...
I know this is an old conversation, but I never did upgrade.  However, now I want to upgrade to 6.7 and of course I've got the same issue.  Unfortunately I've got the essentials bundle, so I can't create a VDS.  The reason I need promiscuous mode is that I'm running an OpenVPN server as a VM, and in order to support bridge mode clients (layer 2 client where they receive a MAC address and IP address on the same subnet as the VM's nic) promiscuous mode is necessary. I guess my question is whether or not maclearn had a dependency set for the current version just out of caution, or if there really is something that won't work in the later versions.  I'm toying with the idea of trying to force the install with -f to see what happens, but if it's a certainty that something changed that would render it non-functional or cause a crash, then of course I won't try it.  Comments welcome.
Hi folks: I'm not sure if this is the right place to put this question or not, but I've been using William Lam's maclearn vib for a couple of years now because I have a VM that runs OpenVPN in... See more...
Hi folks: I'm not sure if this is the right place to put this question or not, but I've been using William Lam's maclearn vib for a couple of years now because I have a VM that runs OpenVPN in bridge mode, and that needs promiscuous mode.  As with the nested ESXi situation that he wrote maclearn to address, this causes excessive CPU usage on that VM if there is lots of traffic on the virtual switch.  Because of that when I did updates I had to use "software profile update" instead of "software profile install" so that the maclearn vib didn't get removed.  I was going through the dry-run of updating to 6.5d and it failed with a dependency check: [root@naplesesxi:~] esxcli software profile update --dry-run --depot=/vmfs/volumes/539b4dcd-0d43b62e-2a98-e840f2d1736d/Upgrades/ESXi650-201704001 .zip --profile=ESXi-6.5.0-20170404001-standard [DependencyError] File path of '/usr/lib/vmware/vmkmod/dvfilter-maclearn' is claimed by multiple non-overlay VIBs: {'VMware_bootbank_vmware-esx-dvfilter-maclearn_1.00-1.00', 'VMware_bootbank_esx-dvfilter-maclearn_6.5.0-0.0.4282379'} File path of '/usr/libexec/jumpstart/plugins/dvfilter-maclearn.json' is claimed by multiple non-overlay VIBs: {'VMware_bootbank_vmware-esx-dvfilter-maclearn_1.00-1.00', 'VMware_bootbank_esx-dvfilter-maclearn_6.5.0-0.0.4282379'} Please refer to the log file for more details. I had read something about a new fling being available that added a better version of maclearn, but it required a Distributed Virtual Switch, and as I only have the essentials package, I didn't have the ability to create a Distributed Virtual Switch, so I was intending to just stay with what I had.  I had not read or heard that the original version of maclearn was going to actually become a standard part of ESXi, but if I am reading the error message correctly, I believe it's trying to tell me that it is.  If I do the command as "install" instead of update, it says that my version will be removed, along with some other ones that I'll need to research: [root@naplesesxi:~] esxcli software profile install --dry-run --depot=/vmfs/volumes/539b4dcd-0d43b62e-2a98-e840f2d1736d/Upgrades/ESXi650-20170400 1.zip --profile=ESXi-6.5.0-20170404001-standard [Exception] You attempted to install an image profile which would have resulted in the removal of VIBs ['VFrontDe_bootbank_sata-xahci_1.10-1', 'VMware_bootbank_vmware-esx-dvfilter-maclearn_1.00-1.00', 'VMware_bootbank_lsu-lsi-mptsas-plugin_1.0.0-1vmw.600.0.0.2494585', 'VMware_bootbank_esx-dvfilter-maclearn_6.5.0-0.0.4282379']. If this is not what you intended, you may use the esxcli software profile update command to preserve the VIBs above. If this is what you intended, please use the --ok-to-remove option to explicitly allow the removal. Please refer to the log file for more details. [root@naplesesxi:~] The release notes didn't mention anything about maclearn, but it looks like it's here.  I guess my best bet would be to remove Lam's original vib first, assuming that this new vib is really the old maclearn version that works on systems without a Distributed Virtual Switch, and then apply the update in "update" mode so that I don't remove the others.  I guess what I'm looking for feedback on is whether or not that VMware_bootbank_esx-dvfilter-maclearn_6.5.0-0.0.4282379 really is a plug replacement for the original maclearn vib. Comments welcome.
Hi folks: I backup my VMs to OVA files (I'm got the essentials bundle and only a couple of hosts so I can do this manually), which I've typically done with the C client.  However, I created a ... See more...
Hi folks: I backup my VMs to OVA files (I'm got the essentials bundle and only a couple of hosts so I can do this manually), which I've typically done with the C client.  However, I created a new VM the other day and set it up as hardware version 13, meaning that it can't be managed with the C client any longer.  After I got it all configured I tried to export it to an OVA file with the vcenter server appliance 6.5 flash client, but I find that there is no option to create an OVA file.  Also, when I try to export to an OVF file, I don't get any choices of where the file is to be saved.  All I see are some tasks running saying exporting OVF template and OVF package that are stuck on 0 percent, and nothing else happens. Am I missing something here, or is this whole OVF / OVA export thing completely broken other than via the C client? srwsol
The one thing that is buggy about ESXi 6.5 is the USB support with the new driver.   If you are going to use ESXi 6.5 and have host USB devices that VMs use, I'd strongly suggest that you disable... See more...
The one thing that is buggy about ESXi 6.5 is the USB support with the new driver.   If you are going to use ESXi 6.5 and have host USB devices that VMs use, I'd strongly suggest that you disable the new USB driver per this kb article: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2147650 Here's a thread discussing the issues: https://communities.vmware.com/thread/547408?start=0&tstart=0
I upgraded a different ESXi box and the same thing happened.  When I was copying files on an Arch Linux VM with kernel 4.9.11.1 I was getting this message over and over again: Feb 25 23:43:27 ... See more...
I upgraded a different ESXi box and the same thing happened.  When I was copying files on an Arch Linux VM with kernel 4.9.11.1 I was getting this message over and over again: Feb 25 23:43:27 archnfs kernel: usb 2-2: reset SuperSpeed USB device number 3 using xhci_hcd I did a hash check on the copied file and it looked like it copied correctly, but there were hundreds of these in the kernel log for a copy of a 4gb file.  I also noticed that the transfer speed was less than half normal.  I then disabled the driver per your suggestion,, rebooted ESXi, and that fixed everything.  Copying was back to full speed and no error messages in the log.  They really need to better test these drivers before they put them out.  Hopefully they aren't going to remove the old drivers anytime soon. Thanks for your help.
Sorry for taking so long to get back.  Per my other post, I rolled back and didn't do anything else regarding the problem.  I'm going to try again next week with an 8tb drive, but using a differe... See more...
Sorry for taking so long to get back.  Per my other post, I rolled back and didn't do anything else regarding the problem.  I'm going to try again next week with an 8tb drive, but using a different cradle ( https://www.amazon.com/gp/product/B01GYOLGSA/ref=oh_aui_search_detailpage?ie=UTF8&psc=1 ), as that's what I have available here at my place in Florida.  This cradle has been working fine under ESXi 6.0 with several different drives, including the 8tb one, so it should work.  I guess I'm going to have to mount the hard drives read only to start with and see if I can recreate the problem while just reading, as I'm afraid the problem is causing data loss if it happens during writes.  If I can recreate the problem, what debugging information do you suggest I gather besides the vmkernel log and the linux vm logs?  I do want to get upgraded to ESXi 6.5 as it has the lastest VM hardware version which has some fixes for linux graphics.
Sorry for taking so long to get back to this.  I backed out the update and have been running on the older version, so I haven't had any issues.  I'm going to try to update one of my boxes in the ... See more...
Sorry for taking so long to get back to this.  I backed out the update and have been running on the older version, so I haven't had any issues.  I'm going to try to update one of my boxes in the next week or so using the latest version, which came out after I ran the previous tests, and if it doesn't work, then I'll try your suggestion.  By the way, what symptoms were you experiencing MarcHuppert, and which version were you using?
As this problem also happens on the ESXi 6.5 host html 5 interface, I don't think the problem is specifically in vCenter Server.   There is another thread in the ESXi 6 forum that has referenced ... See more...
As this problem also happens on the ESXi 6.5 host html 5 interface, I don't think the problem is specifically in vCenter Server.   There is another thread in the ESXi 6 forum that has referenced the issue which I'm linking to here, and I would suggest that all further posts be directed to that thread. https://communities.vmware.com/thread/547244
I've already rolled back to 6.0u2, but I can provide you the usb information from there, which should be the same.   Also, since I only have the Essentials bundle, I cannot submit a support reque... See more...
I've already rolled back to 6.0u2, but I can provide you the usb information from there, which should be the same.   Also, since I only have the Essentials bundle, I cannot submit a support request without paying a fee.  The host is an Intel S2600CWTS motherboard with 128gb of memory and Xeon E5-2697 v3 processor.   In addition to the onboard hardware it has a LSI Megaraid controller that disks in a RAID 6 configuration which house the ESXi code partition and the datastores.   It also has two additional uPD72021 chipset USB 3 PCI devices in addition to the onboard USB 3 controller.   There are over a dozen USB devices connected to the system, most of which are USB disks that are connected to a single Arch Linux VM which acts as a NAS server to the rest of the VMs on the system. The particular device that had an issue was a Seagate 8tb ST8000AS0002 drive in a Plugable USB 3.0 SATA hard drive dock ( https://www.amazon.com/gp/product/B00APP6694/ref=oh_aui_search_detailpage?ie=UTF8&psc=1 ).  What follows is information about the devices, but remember these come from 6.0u2 as I'd have to reinstall 6.5 to extract information from it. PCI Device Info [root@intelserver:~] lspci 0000:00:00.0 Bridge: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DMI2 [PCIe RP[0000:00:00.0]] 0000:00:01.0 Bridge: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express Root Port 1 [PCIe RP[0000:00:01.0]] 0000:00:02.0 Bridge: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express Root Port 2 [PCIe RP[0000:00:02.0]] 0000:00:03.0 Bridge: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express Root Port 3 [PCIe RP[0000:00:03.0]] 0000:00:03.2 Bridge: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express Root Port 3 [PCIe RP[0000:00:03.2]] 0000:00:04.0 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DMA Channel 0 0000:00:04.1 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DMA Channel 1 0000:00:04.2 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DMA Channel 2 0000:00:04.3 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DMA Channel 3 0000:00:04.4 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DMA Channel 4 0000:00:04.5 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DMA Channel 5 0000:00:04.6 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DMA Channel 6 0000:00:04.7 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DMA Channel 7 0000:00:05.0 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Address Map, VTd_Misc, System Management 0000:00:05.1 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Hot Plug 0000:00:05.2 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 RAS, Control Status and Global Errors 0000:00:05.4 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 I/O APIC 0000:00:11.0 : Intel Corporation C610/X99 series chipset SPSR 0000:00:11.4 Mass storage controller: Intel Corporation Wellsburg AHCI Controller [vmhba2] 0000:00:14.0 Serial bus controller: Intel Corporation C610/X99 series chipset USB xHCI Host Controller 0000:00:16.0 Communication controller: Intel Corporation C610/X99 series chipset MEI Controller #1 0000:00:16.1 Communication controller: Intel Corporation C610/X99 series chipset MEI Controller #2 0000:00:1a.0 Serial bus controller: Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #2 0000:00:1c.0 Bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #4 [PCIe RP[0000:00:1c.0]] 0000:00:1c.4 Bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #5 [PCIe RP[0000:00:1c.4]] 0000:00:1d.0 Serial bus controller: Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #1 0000:00:1f.0 Bridge: Intel Corporation C610/X99 series chipset LPC Controller 0000:00:1f.2 Mass storage controller: Intel Corporation Wellsburg AHCI Controller [vmhba0] 0000:00:1f.3 Serial bus controller: Intel Corporation C610/X99 series chipset SMBus Controller 0000:01:00.0 Network controller: Intel Corporation Ethernet Controller 10 Gigabit X540-AT2 [vmnic0] 0000:01:00.1 Network controller: Intel Corporation Ethernet Controller 10 Gigabit X540-AT2 [vmnic1] 0000:03:00.0 Mass storage controller: Avago (LSI) MegaRAID SAS Invader Controller [vmhba1] 0000:04:00.0 Serial bus controller: Renesas Technology Corp. uPD720201 USB 3.0 Host Controller 0000:06:00.0 Display controller: Matrox Electronics Systems Ltd. MGA G200e [Pilot] ServerEngines (SEP1) 0000:07:00.0 Serial bus controller: Renesas Technology Corp. uPD720201 USB 3.0 Host Controller 0000:ff:0b.0 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 R3 QPI Link 0 & 1 Monitoring 0000:ff:0b.1 Signal processing controller: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 R3 QPI Link 0 & 1 Monitoring 0000:ff:0b.2 Signal processing controller: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 R3 QPI Link 0 & 1 Monitoring 0000:ff:0c.0 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers 0000:ff:0c.1 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers 0000:ff:0c.2 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers 0000:ff:0c.3 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers 0000:ff:0c.4 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers 0000:ff:0c.5 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers 0000:ff:0c.6 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers 0000:ff:0c.7 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers 0000:ff:0d.0 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers 0000:ff:0d.1 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers 0000:ff:0d.2 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers 0000:ff:0d.3 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers 0000:ff:0d.4 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers 0000:ff:0d.5 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers 0000:ff:0f.0 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Buffered Ring Agent 0000:ff:0f.1 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Buffered Ring Agent 0000:ff:0f.2 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Buffered Ring Agent 0000:ff:0f.3 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Buffered Ring Agent 0000:ff:0f.4 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 System Address Decoder & Broadcast Registers 0000:ff:0f.5 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 System Address Decoder & Broadcast Registers 0000:ff:0f.6 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 System Address Decoder & Broadcast Registers 0000:ff:10.0 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCIe Ring Interface 0000:ff:10.1 Signal processing controller: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCIe Ring Interface 0000:ff:10.5 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Scratchpad & Semaphore Registers 0000:ff:10.6 Signal processing controller: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Scratchpad & Semaphore Registers 0000:ff:10.7 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Scratchpad & Semaphore Registers 0000:ff:12.0 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Home Agent 0 0000:ff:12.1 Signal processing controller: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Home Agent 0 0000:ff:12.4 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Home Agent 1 0000:ff:12.5 Signal processing controller: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Home Agent 1 0000:ff:13.0 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Target Address, Thermal & RAS Registers 0000:ff:13.1 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Target Address, Thermal & RAS Registers 0000:ff:13.2 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder 0000:ff:13.3 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder 0000:ff:13.6 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO Channel 0/1 Broadcast 0000:ff:13.7 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO Global Broadcast 0000:ff:14.0 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 0 Thermal Control 0000:ff:14.1 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 1 Thermal Control 0000:ff:14.2 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 0 ERROR Registers 0000:ff:14.3 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 1 ERROR Registers 0000:ff:14.4 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 0 & 1 0000:ff:14.5 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 0 & 1 0000:ff:14.6 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 0 & 1 0000:ff:14.7 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 0 & 1 0000:ff:16.0 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 1 Target Address, Thermal & RAS Registers 0000:ff:16.1 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 1 Target Address, Thermal & RAS Registers 0000:ff:16.2 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 1 Channel Target Address Decoder 0000:ff:16.3 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 1 Channel Target Address Decoder 0000:ff:16.6 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO Channel 2/3 Broadcast 0000:ff:16.7 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO Global Broadcast 0000:ff:17.0 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 1 Channel 0 Thermal Control 0000:ff:17.1 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 1 Channel 1 Thermal Control 0000:ff:17.2 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 1 Channel 0 ERROR Registers 0000:ff:17.3 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 1 Channel 1 ERROR Registers 0000:ff:17.4 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 2 & 3 0000:ff:17.5 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 2 & 3 0000:ff:17.6 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 2 & 3 0000:ff:17.7 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 2 & 3 0000:ff:1e.0 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit 0000:ff:1e.1 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit 0000:ff:1e.2 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit 0000:ff:1e.3 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit 0000:ff:1e.4 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit 0000:ff:1f.0 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 VCU 0000:ff:1f.2 Generic system peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 VCU [root@intelserver:~] USB Devices [root@intelserver:~] lsusb Bus 006 Device 010: ID 1058:0748 Western Digital Technologies, Inc. My Passport (WDBKXH) Bus 006 Device 006: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 005 Device 009: ID 0480:a003 Toshiba America Info. Systems, Inc. Bus 006 Device 004: ID 174c:55aa ASMedia Technology Inc. ASM1051 SATA 3Gb/s bridge Bus 006 Device 003: ID 1058:082a Western Digital Technologies, Inc. Bus 004 Device 006: ID 0bc2:50a5 Seagate RSS LLC FreeAgent GoFlex Desk USB 3.0 Bus 004 Device 005: ID 059b:0070 Iomega Corp. eGo Portable Hard Drive Bus 008 Device 004: ID 0480:d011 Toshiba America Info. Systems, Inc. Bus 008 Device 003: ID 0480:d011 Toshiba America Info. Systems, Inc. Bus 008 Device 002: ID 0411:01e7 BUFFALO INC. (formerly MelCo., Inc.) Bus 005 Device 008: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 005 Device 007: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 005 Device 006: ID 1058:1100 Western Digital Technologies, Inc. My Book Essential Edition 2.0 (WDH1U) Bus 005 Device 005: ID 0781:5583 SanDisk Corp. Bus 005 Device 003: ID 0781:5583 SanDisk Corp. Bus 005 Device 002: ID 1058:1003 Western Digital Technologies, Inc. Elements 1000 GB Bus 006 Device 002: ID 05e3:0617 Genesys Logic, Inc. Bus 003 Device 002: ID 2109:2812 Bus 004 Device 004: ID 1058:0824 Western Digital Technologies, Inc. Bus 004 Device 003: ID 0bc2:3312 Seagate RSS LLC SRD00F2 [Expansion Desktop Drive 2TB] Bus 004 Device 002: ID 2109:0812 Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [root@intelserver:~] Tree View of USB Devices [root@intelserver:~] lsusb -t -v Bus#  8 `-Dev#   1 Vendor 0x1d6b Product 0x0003 Linux Foundation 3.0 root hub   |-Dev#   2 Vendor 0x0411 Product 0x01e7 BUFFALO INC. (formerly MelCo., Inc.)   |-Dev#   3 Vendor 0x0480 Product 0xd011 Toshiba America Info. Systems, Inc.   `-Dev#   4 Vendor 0x0480 Product 0xd011 Toshiba America Info. Systems, Inc. Bus#  7 `-Dev#   1 Vendor 0x1d6b Product 0x0002 Linux Foundation 2.0 root hub Bus#  6 `-Dev#   1 Vendor 0x1d6b Product 0x0003 Linux Foundation 3.0 root hub   |-Dev#  12 Vendor 0x1058 Product 0x0748 Western Digital Technologies, Inc. My Passport (WDBKXH)   `-Dev#   2 Vendor 0x05e3 Product 0x0617 Genesys Logic, Inc.     |-Dev#   3 Vendor 0x1058 Product 0x082a Western Digital Technologies, Inc.     |-Dev#   4 Vendor 0x174c Product 0x55aa ASMedia Technology Inc. ASM1051 SATA 3Gb/s bridge     `-Dev#   6 Vendor 0x0b95 Product 0x1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus#  5 `-Dev#   1 Vendor 0x1d6b Product 0x0002 Linux Foundation 2.0 root hub   |-Dev#   2 Vendor 0x1058 Product 0x1003 Western Digital Technologies, Inc. Elements 1000 GB   |-Dev#   3 Vendor 0x0781 Product 0x5583 SanDisk Corp.   |-Dev#   5 Vendor 0x0781 Product 0x5583 SanDisk Corp.   |-Dev#  11 Vendor 0x1058 Product 0x1100 Western Digital Technologies, Inc. My Book Essential Edition 2.0 (WDH1U)   |-Dev#   7 Vendor 0x05e3 Product 0x0610 Genesys Logic, Inc. 4-port hub   | `-Dev#   9 Vendor 0x0480 Product 0xa003 Toshiba America Info. Systems, Inc.   `-Dev#   8 Vendor 0x046b Product 0xff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus#  4 `-Dev#   1 Vendor 0x1d6b Product 0x0003 Linux Foundation 3.0 root hub   |-Dev#   2 Vendor 0x2109 Product 0x0812   | |-Dev#   5 Vendor 0x059b Product 0x0070 Iomega Corp. eGo Portable Hard Drive   | `-Dev#   6 Vendor 0x0bc2 Product 0x50a5 Seagate RSS LLC FreeAgent GoFlex Desk USB 3.0   |-Dev#   3 Vendor 0x0bc2 Product 0x3312 Seagate RSS LLC SRD00F2 [Expansion Desktop Drive 2TB]   `-Dev#   4 Vendor 0x1058 Product 0x0824 Western Digital Technologies, Inc. Bus#  3 `-Dev#   1 Vendor 0x1d6b Product 0x0002 Linux Foundation 2.0 root hub   `-Dev#   2 Vendor 0x2109 Product 0x2812 Bus#  2 `-Dev#   1 Vendor 0x1d6b Product 0x0002 Linux Foundation 2.0 root hub   `-Dev#   2 Vendor 0x8087 Product 0x8002 Intel Corp. Bus#  1 `-Dev#   1 Vendor 0x1d6b Product 0x0002 Linux Foundation 2.0 root hub   `-Dev#   2 Vendor 0x8087 Product 0x800a Intel Corp. [root@intelserver:~] Plugable USB 3 SATA Dock w Seagate 8tb Drive [root@intelserver:~] lsusb -v -d:55aa Bus 006 Device 004: ID 174c:55aa ASMedia Technology Inc. ASM1051 SATA 3Gb/s bridge Device Descriptor:   bLength                18   bDescriptorType         1   bcdUSB               3.00   bDeviceClass            0 (Defined at Interface level)   bDeviceSubClass         0   bDeviceProtocol         0   bMaxPacketSize0         9   idVendor           0x174c ASMedia Technology Inc.   idProduct          0x55aa ASM1051 SATA 3Gb/s bridge   bcdDevice            1.00   iManufacturer           2 Plugable   iProduct                3 USB3-SATA-UASP1   iSerial                 1 123456789012   bNumConfigurations      1   Configuration Descriptor:     bLength                 9     bDescriptorType         2     wTotalLength          121     bNumInterfaces          1     bConfigurationValue     1     iConfiguration          0     bmAttributes         0xc0       Self Powered     MaxPower                0mA     Interface Descriptor:       bLength                 9       bDescriptorType         4       bInterfaceNumber        0       bAlternateSetting       0       bNumEndpoints           2       bInterfaceClass         8 Mass Storage       bInterfaceSubClass      6 SCSI       bInterfaceProtocol     80 Bulk-Only       iInterface              0       Endpoint Descriptor:         bLength                 7         bDescriptorType         5         bEndpointAddress     0x81  EP 1 IN         bmAttributes            2           Transfer Type            Bulk           Synch Type               None           Usage Type               Data         wMaxPacketSize     0x0400  1x 1024 bytes         bInterval               0         bMaxBurst              15       Endpoint Descriptor:         bLength                 7         bDescriptorType         5         bEndpointAddress     0x02  EP 2 OUT         bmAttributes            2           Transfer Type            Bulk           Synch Type               None           Usage Type               Data         wMaxPacketSize     0x0400  1x 1024 bytes         bInterval               0         bMaxBurst              15     Interface Descriptor:       bLength                 9       bDescriptorType         4       bInterfaceNumber        0       bAlternateSetting       1       bNumEndpoints           4       bInterfaceClass         8 Mass Storage       bInterfaceSubClass      6 SCSI       bInterfaceProtocol     98       iInterface              0       Endpoint Descriptor:         bLength                 7         bDescriptorType         5         bEndpointAddress     0x81  EP 1 IN         bmAttributes            2           Transfer Type            Bulk           Synch Type               None           Usage Type               Data         wMaxPacketSize     0x0400  1x 1024 bytes         bInterval               0         bMaxBurst              15         MaxStreams             32         Data-in pipe (0x03)       Endpoint Descriptor:         bLength                 7         bDescriptorType         5         bEndpointAddress     0x02  EP 2 OUT         bmAttributes            2           Transfer Type            Bulk           Synch Type               None           Usage Type               Data         wMaxPacketSize     0x0400  1x 1024 bytes         bInterval               0         bMaxBurst              15         MaxStreams             32         Data-out pipe (0x04)       Endpoint Descriptor:         bLength                 7         bDescriptorType         5         bEndpointAddress     0x83  EP 3 IN         bmAttributes            2           Transfer Type            Bulk           Synch Type               None           Usage Type               Data         wMaxPacketSize     0x0400  1x 1024 bytes         bInterval               0         bMaxBurst              15         MaxStreams             32         Status pipe (0x02)       Endpoint Descriptor:         bLength                 7         bDescriptorType         5         bEndpointAddress     0x04  EP 4 OUT         bmAttributes            2           Transfer Type            Bulk           Synch Type               None           Usage Type               Data         wMaxPacketSize     0x0400  1x 1024 bytes         bInterval               0         bMaxBurst               0         Command pipe (0x01) Binary Object Store Descriptor:   bLength                 5   bDescriptorType        15   wTotalLength           22   bNumDeviceCaps          2   USB 2.0 Extension Device Capability:     bLength                 7     bDescriptorType        16     bDevCapabilityType      2     bmAttributes   0x0000f41e       Link Power Management (LPM) Supported   SuperSpeed USB Device Capability:     bLength                10     bDescriptorType        16     bDevCapabilityType      3     bmAttributes         0x00     wSpeedsSupported   0x000e       Device can operate at Full Speed (12Mbps)       Device can operate at High Speed (480Mbps)       Device can operate at SuperSpeed (5Gbps)     bFunctionalitySupport   1       Lowest fully-functional device speed is Full Speed (12Mbps)     bU1DevExitLat          10 micro seconds     bU2DevExitLat        2047 micro seconds Device Status:     0x0001   Self Powered [root@intelserver:~]
I don't see anything really bad right off the bat.  Have you checked the I/O and memory performance?    If you have lots of users Exchange uses lots of memory, especially if you are running anti-... See more...
I don't see anything really bad right off the bat.  Have you checked the I/O and memory performance?    If you have lots of users Exchange uses lots of memory, especially if you are running anti-malware software for the Exchange server in the same box.   The datastore(s) which contain the Exchange databases can also take a beating if you have lots of users.  There are settings in ESXi where you can dedicate physical processor cores to a particular VM and there are ways to fence off memory for particular VMs if you find one of those to be the problem.  If it turns out to be database I/Os that's the bottleneck your best bet would probably be to setup dedicated hardware for the databases.  You can do this either by dedicating hardware to specific datastores and only put the exchange databases on those datastores, or by using a NAS or SAN setup, or even by using PCI pass through to give the exchange VM full control of say a RAID controller with it's own attached drives (note that this method has implications for things like VMotion and snapshots). 
What was the difference between the card readers?  By any chance was the one that failed USB 3 and the one that worked USB 2?
Yes, the sensor data does display perfectly if you connect the native C client directly to the ESXi 6.5 host, so this is not an issue of ESXi 6.5 being unable to obtain the sensor data from the h... See more...
Yes, the sensor data does display perfectly if you connect the native C client directly to the ESXi 6.5 host, so this is not an issue of ESXi 6.5 being unable to obtain the sensor data from the hardware.   It does appear to be an issue with how that data is made available to the GUI interfaces, both the native html5 interface within ESXi 6.5 itself and the GUI interfaces within vCenter Server.   I've sinced rolled back ESXi 6.5 to 6.0u2 due to problems with host connected USB devices and VMs, so I can't say whether or not the sensor data was being presented correctly via the CLI interface as I didn't try that.
My Arch Linux VM eventually got hung up so my copy test couldn't finish.  I rolled back ESXi 6.5 to 6.0u2, reran the test, and it worked perfectly; so there is definitely a problem here.   If you... See more...
My Arch Linux VM eventually got hung up so my copy test couldn't finish.  I rolled back ESXi 6.5 to 6.0u2, reran the test, and it worked perfectly; so there is definitely a problem here.   If you are using host usb devices with your VMs I'd recommend that you not upgrade until this gets addressed.
Has anyone else experienced any issues with ESXi 6.5 and host USB 3 devices attached to VMs? I'm seeing messages like this from an Arch Linux VM that has a number of USB 3 hard disks attached ... See more...
Has anyone else experienced any issues with ESXi 6.5 and host USB 3 devices attached to VMs? I'm seeing messages like this from an Arch Linux VM that has a number of USB 3 hard disks attached to it: Nov 25 02:07:40 archnfs kernel: usb 1-4.1: reset high-speed USB device number 8 using xhci_hcd There are quite a number of other error messages associated with it to, and I'm betting that data is being lost.  I'm running a big test copy right now, and when it finishes I'm going to verify the md5sum versus the source to find out for sure.