ciuly's Posts

The reboot didn't help. I double checked and both VMs are from 2 other storages that were up just fine after the recovery/restore with other VMs on them showing up just fine. So the VM shows up in the vsphere client like /vmfs/volumes/<GUID>/folder/file.vmx (inaccessible) the exact path (checked letter by letter) is accessible via the esxi ssh shell. Access on the vmx file is -rwxr-xr-x, and matches other visible/accessible VMs on the same storage. I can do "less filename" on the vmx and see it ok. Doesn't look to be damaged/corrupted (compared the format/output with other (running) vmx file) Without removing the inaccessible VM, I have added it to the inventory again. It added just fine. Powered up fine as well. So I went ahead and removed the inaccessible "link". Gremlins, I tell you.

>>What type of storage is it (Local, NAS, SAN)? Local >> And how did you add it back (mount, resignature)? Just the "Add Storage..." link/button from the configuration\Storage (I also did a resscan but that didn't help any) >> Are other VMs - located on the same datastore - accessible? Well, as soon as I added the storage, the VMs on it were seen and recognized. I see now the 2 grayed out VMs are from the first storage that was loaded up "fine" including the other VMs on it. I will do a reboot in the evening and see what happens. Thanks

I scrolled all the logs from the esxi UI/schell but nothing popped up to me. Of course I didn't know what to look for so I was just hoping to see some errors or rejected connections or something. Eventually I used the rollback as you suggested and that cured it. Trouble next was that 1 of the storages got missing. So the VMs on it were no longer accessible. I manually added that back but for some reason there are still 2 VMs grayed out and in unknown status, saying vmx inaccessible. I am looking at the files on the volume though and they seem fine. Access rights and everything look good. Not sure on policies on this forum: should I create a new question for this issue? Thanks LE: I see some of the VMs from the previously existing datastore were no longer in the inventory either. They may have been added after the restore point was created? Just guessing.

The SHIFT+R option shows 2 entries Hypervisor1: 6.0.0-2.34.3620759 (default) Hypervisor2: 6.0.0-2.34.3620759 they both seem to be the same version. So I guess nothing to rollback. Before going the reinstall path, which will require some setup to get right, including the passthrough which I know I had a lot of trouble with, I'd like to explore other options. You mentioned logs. Can you detail which ones and what to look for?

I have no explanation to what has gone wrong or how it got "fixed". Basically I just rebooted the host this morning, allowed for all the VMs to power on and initialize, as usual and then start the 4th VM. All is good this time. I've done this exact thing quite a few times this past week. Thank you all for your time.

>> I suspect the two devices in VM #3 and VM #4 is behind the same PCI bridge. unlikely. The device in 3rd is a usb pcie card. The device in 4th is the onboard LAN. device info 3rd 00:06:00.0 USB controller Serial bus controller: NEC Corporation uPD720200 USB 3.0 Host Controller          Class 0c03: 1033:0194 4th 00:00:19.0 Ethernet controller Network controller: Intel Corporation 82579V Gigabit Network Connection          Class 0200: 8086:1503 # lspci -p Se:Bu:De.F Vend:Dvid Subv:Subd ISA/irq/Vect P M Module       Name                                Spawned bus 00:00:00.0 8086:0100 1462:7751 255/   /     @ V 00:00:01.0 8086:0101 0000:0000  11/ 11/0x78 A V              PCIe RP[00:00:01.0]                                 01 00:00:01.1 8086:0105 0000:0000  11/ 11/0x78 A V              PCIe RP[00:00:01.1]                                 02 00:00:14.0 8086:1e31 1462:7751  11/ 11/0x78 A V 00:00:16.0 8086:1e3a 1462:7751  11/ 11/0x78 A V 00:00:19.0 8086:1503 1462:7751   4/  4/0xa0 A P 00:00:1a.0 8086:1e2d 1462:7751  11/ 11/0x78 A P 00:00:1c.0 8086:1e10 0000:0000  11/ 11/0x78 A V              PCIe RP[00:00:1c.0]                                 03 00:00:1c.2 8086:1e14 0000:0000   5/  5/0x98 C V              PCIe RP[00:00:1c.2]                                 04 00:00:1c.3 8086:1e16 0000:0000   3/  3/0xa8 D V              PCIe RP[00:00:1c.3]                                 05 00:00:1c.4 8086:1e18 0000:0000  11/ 11/0x78 A V              PCIe RP[00:00:1c.4]                                 06 00:00:1c.5 8086:1e1a 0000:0000  10/ 10/0x88 B V              PCIe RP[00:00:1c.5]                                 07 00:00:1c.6 8086:1e1c 0000:0000   5/  5/0x98 C V              PCIe RP[00:00:1c.6]                                 08 00:00:1d.0 8086:1e26 1462:7751  11/ 11/0xb0 A P 00:00:1f.0 8086:1e44 1462:7751 255/   /     @ V 00:00:1f.2 8086:1e02 1462:7751   3/  3/0xa8 B V ahci         vmhba0 00:00:1f.3 8086:1e22 1462:7751   5/   /     C V 00:01:00.0 1002:5b62 1002:0b02  11/ 11/0x78 A V 00:01:00.1 1002:5b72 1002:0b03 255/   /     @ V 00:02:00.0 1002:6779 1462:2125  10/ 10/0xc8 A P 00:02:00.1 1002:aa98 1462:aa98   5/  5/0x31 B P 00:04:00.0 8086:10d3 8086:a01f   5/  5/0x98 A V e1000e       vmnic0 00:05:00.0 1b21:1042 174c:2104   3/  3/0xa8 A P 00:06:00.0 1033:0194 ffff:ffff  11/ 11/0x78 A P 00:07:00.0 1095:3531 1095:3531  10/ 10/0xd0 A P              vmhba1 00:08:00.0 1b21:0612 1462:7751   5/  5/0x98 A V ahci         vmhba32

Thanks for the info. Any idea how I can calcualte those BARs or if there is some log entry somewhere that tells me the BAR for each pci device? I don't think I've done mych stuff since I posted, I know I removed that device form the list, add it back, rebooted host a few times. Weird thing is now, when I try to start the 4th VM I get an error dialog with "Device 0:25.0 is not a passthrough device" the vmkernel.log entry for this operation is 2018-03-07T15:31:16.256Z cpu5:14114)Config: 347: "SIOControlFlag2" = 1, Old Value: 0, (Status: 0x0) 2018-03-07T15:31:16.289Z cpu7:77105)MemSched: vm 77105: 7756: extended swap to 8192 pgs 2018-03-07T15:31:16.433Z cpu5:77105)World: vm 77106: 1421: Starting world vmm0:gateway with flags 8 2018-03-07T15:31:16.433Z cpu5:77105)Sched: vm 77106: 6416: Adding world 'vmm0:gateway', group 'host/user/pool2', cpu: shares=-1 min=-1 minLimit=-1 max=-1, mem: shares=-1 min=262144 minLimit=-1 max=-1 2018-03-07T15:31:16.433Z cpu5:77105)Sched: vm 77106: 6431: renamed group 122514 to vm.77105 2018-03-07T15:31:16.433Z cpu5:77105)Sched: vm 77106: 6448: group 122514 is located under group 870 2018-03-07T15:31:16.434Z cpu5:77105)MemSched: vm 77105: 7756: extended swap to 23117 pgs 2018-03-07T15:31:16.473Z cpu5:77105)VSCSI: 3781: handle 8219(vscsi0:0):Creating Virtual Device for world 77106 (FSS handle 879596) 2018-03-07T15:31:16.481Z cpu5:77105)VMKPCIPassthru: 4471: Can not set device 00:19.0 for passthrough 2018-03-07T15:31:16.487Z cpu1:77105)VSCSI: 6343: handle 8219(vscsi0:0):Destroying Device for world 77106 (pendCom 0) 2018-03-07T15:31:16.522Z cpu5:4956)Config: 347: "SIOControlFlag2" = 0, Old Value: 1, (Status: 0x0) I removed the device from the VM, rebooted the vm, boots ok, added the pci device back to the VM and still this error happens. I cannot reboot the host today, will try that tomorrow. morning. But this error is weird, I've never received such an error before.

It appears someone has modified the sharing access to the google docs spreadsheet on this subject. I have restored full access to everyone and removed all editors plus prevented editors from changing these settings again. Hopefully all will be good now.

I use a DVI to HDMI adapter myself for my primary monitor. It was one of those cheap adapters. It works well, but I'm still on 5.1 and not planning to upgrade any time soon. If it works, don't break it

not exactly waht you want, but you can use the information in our community spreadsheet to see which card appears the most with success: http://is.gd/esxgpu Of course, if any card appears with failure that doesn't mean it is the cards fault, just keep that in mind, it may just be the configuration of MB+CPU that doesn't cut it, or the users inability to properly configure it. But it's a good start