1 2 3 4 Previous Next 275 Replies Latest reply on Dec 17, 2014 11:39 PM by ripeed Go to original post
      • 15. Re: Esxi 5.1 pci passthrough broken
        Flappje Novice

        Hi,

         

        also having problems with my passthrough here, i think it has to do with the problems desciped here. because it worked like a charm in 5.0 and not in 5.1 (onboard usb passthrough on a supermicro x8sil-f).

         

        Is there any way we can track this issue so we can see when it is solved? or do we just need to check for updates in a few months/weeks/days?

        • 16. Re: Esxi 5.1 pci passthrough broken
          FastLaneJB Novice

          Looking in /etc/vmware/esx.conf I can see the device being added for passthrough just fine but on reboot its vanished. An ATI Radeon card however works just fine.

           

          They must be removing USB class devices on purpose, I don't see why else it would just vanish from the config perfectly?

          • 17. Re: Esxi 5.1 pci passthrough broken
            aetafoya Lurker

            Just confirming the same issue...ATI video card pass through is working here. My USB controller is selectable for pass through, but vanishes after a reboot. 5.0 update 1 worked perfectly.

            • 18. Re: Esxi 5.1 pci passthrough broken
              FastLaneJB Novice

              So looking in the vmkernel.log I can see the following which is my Radeon Card with it's HDMI audio.

               

              2012-09-18T17:55:54.463Z cpu3:4453)WARNING: PCI: 3771: 00:04:00.0: Bypassing non-ACS capable device in hierarchy
              2012-09-18T17:55:54.463Z cpu3:4453)VMK_PCI: 317: device 00:04:00.0 event: Device changed ownership: new owner vm
              2012-09-18T17:55:54.463Z cpu3:4453)WARNING: PCI: 4265: 00:04:00.0 is nameless
              2012-09-18T17:55:54.463Z cpu3:4453)VMK_PCI: 709: Device 00:04:00.0 has no name
              2012-09-18T17:55:54.463Z cpu3:4453)LinPCI: LinuxPCIDeviceRemoved:385: Device 0000:04:00.0  is not claimed by vmklinux drivers
              2012-09-18T17:55:54.463Z cpu3:4453)PCI: 3812: 00:04:00.1 to 3
              2012-09-18T17:55:54.463Z cpu3:4453)WARNING: PCI: 3771: 00:04:00.1: Bypassing non-ACS capable device in hierarchy
              2012-09-18T17:55:54.463Z cpu3:4453)VMK_PCI: 317: device 00:04:00.1 event: Device changed ownership: new owner vm
              2012-09-18T17:55:54.463Z cpu3:4453)WARNING: PCI: 4265: 00:04:00.1 is nameless
              2012-09-18T17:55:54.463Z cpu3:4453)VMK_PCI: 709: Device 00:04:00.1 has no name
              2012-09-18T17:55:54.463Z cpu3:4453)LinPCI: LinuxPCIDeviceRemoved:385: Device 0000:04:00.1  is not claimed by vmklinux drivers

               

              There's no lines that I can see for it trying the USB controller even though it was selected. Note that this USB Controller is PCI-Express and not PCI so it's got to be another bug than the crashing or maybe this is a by design change?

               

              Here's where it's seeing the controller card, I cannot use this one inside ESXi as in if I plug a device into it, I cannot use the single device passthrough as ESXi doesn't see it. That does work on the internal motherboard USB controller. I cannot pass that through anymore to a VM though like the add in card.

               

              0:00:00:04.194 cpu0:4096)PCI: 6344: 07:00.0: PCIe v2 PCI Express Endpoint
              0:00:00:04.194 cpu0:4096)PCI: 5327: 00:07:00.0: Found Advanced Error Reporting support
              0:00:00:04.194 cpu0:4096)PCI: 5327: 00:07:00.0: Found Device Serial Number support
              0:00:00:04.194 cpu0:4096)PCI: 6277: 07:00.0: PCIe v2 PCI Express Endpoint
              0:00:00:04.194 cpu0:4096)PCI: 6282: Not a ACS capable device
              0:00:00:04.194 cpu0:4096)PCI: 3520: 00:07:00.0 104c:8241 0000:0000 added
              0:00:00:04.194 cpu0:4096)PCI: 3522:   classCode 0c03 progIFRevID 3002
              0:00:00:04.194 cpu0:4096)PCI: 3526:   intPIN A intLine 11
              0:00:00:04.194 cpu0:4096)Chipset: 404: 07:00 A busIRQ=  0 on 00-16
              0:00:00:04.194 cpu0:4096)PCI: 3535:   irq 11 vector 0x88
              0:00:00:04.194 cpu0:4096)Device: 527: Registered device: p=0x41000d0fa230 0x41000d0f9440 00:07:00.0 104c:8241 0000:0000 bd=0x41000187b610
              0:00:00:04.194 cpu0:4096)VMK_PCI: 317: device 00:07:00.0 event: Device inserted: new owner module
              0:00:00:04.194 cpu0:4096)Device: 196: Found driver pci for device 0x41000d0fa230
              0:00:00:04.194 cpu0:4096)PCI: 3520: 00:00:1a.0 8086:1c2d 103c:330d added

               

              This might not be for the same device but all the USB lines seem to be roughly the same...

               

              2012-09-18T17:55:53.866Z cpu3:4545)<6>uhci_hcd: USB Universal Host Controller Interface driver
              2012-09-18T17:55:53.866Z cpu3:4545)PCI: driver uhci_hcd is looking for devices
              2012-09-18T17:55:53.866Z cpu3:4545)DMA: 609: DMA Engine 'vmklnxpci-0:1:0.4' created using mapper 'DMANull'.
              2012-09-18T17:55:53.866Z cpu3:4545)DMA: 609: DMA Engine 'vmklnxpci-0:1:0.4' created using mapper 'DMANull'.
              2012-09-18T17:55:53.866Z cpu3:4545)<6>uhci_hcd 0000:01:00.4: UHCI Host Controller
              2012-09-18T17:55:53.866Z cpu3:4545)<6>uhci_hcd 0000:01:00.4: new USB bus registered, assigned bus number 3
              2012-09-18T17:55:53.866Z cpu3:4545)<6>uhci_hcd 0000:01:00.4: port count misdetected? forcing to 2 ports
              2012-09-18T17:55:53.866Z cpu3:4545)IRQ: 233: 0x88 <uhci_hcd:usb3> sharable (entropy source), flags 0x10
              2012-09-18T17:55:53.866Z cpu3:4545)VMK_VECTOR: 138: Added handler for shared vector 136, flags 0x10
              2012-09-18T17:55:53.866Z cpu3:4545)<6>uhci_hcd 0000:01:00.4: irq 136, io base 0x00002000
              2012-09-18T17:55:53.866Z cpu3:4545)<6>usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
              2012-09-18T17:55:53.866Z cpu3:4545)<6>usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
              2012-09-18T17:55:53.866Z cpu3:4545)<6>usb usb3: Product: UHCI Host Controller
              2012-09-18T17:55:53.866Z cpu3:4545)<6>usb usb3: Manufacturer: vmklinux_9  uhci_hcd
              2012-09-18T17:55:53.866Z cpu3:4545)<6>usb usb3: SerialNumber: 0000:01:00.4
              2012-09-18T17:55:53.866Z cpu3:4545)<6>hub 3-0:1.0: USB hub found
              2012-09-18T17:55:53.866Z cpu3:4545)<6>hub 3-0:1.0: 2 ports detected
              2012-09-18T17:55:53.866Z cpu3:4545)<6>hub 3-0:1.0: interface is claimed by hub
              2012-09-18T17:55:53.866Z cpu3:4545)<6>usb usb3: device is not available for passthrough
              2012-09-18T17:55:53.866Z cpu3:4545)<6>usb usb3: usbfs: registered usb0301
              2012-09-18T17:55:53.866Z cpu3:4545)PCI: driver uhci_hcd claimed device 0000:01:00.4
              2012-09-18T17:55:53.866Z cpu3:4545)PCI: driver uhci_hcd claimed 1 device
              2012-09-18T17:55:53.866Z cpu3:4545)Mod: 4485: Initialization of usb-uhci succeeded with module ID 17.
              2012-09-18T17:55:53.866Z cpu3:4545)usb-uhci loaded successfully.

              Not got a 5.0 box currently to look on to see what's changed.

               

              Hope this info might help VMWare provide a fix for this.

              • 19. Re: Esxi 5.1 pci passthrough broken
                lowdownshame Novice

                just upgraded to 5.1 and im having issues passing through this device [asmedia asm1042 usb 3.0 controller] which is PCIe. worked perfectly fine under 5.0. After adding it, it disappears after reboot! Any workarounds available ?? 

                • 20. Re: Esxi 5.1 pci passthrough broken
                  mlai Novice

                  I have having the same problem in trying to pass through asmedia asm1042 usb3.0 hub to vm as well.  Worked flawlessly under 5.0u1!

                   

                  Please!  Fix this ASAP! 

                  • 21. Re: Esxi 5.1 pci passthrough broken
                    BlackBurn1983 Novice

                    Got exactly the same problem passing through a simple Firewire card (PCI).

                     

                    Just downgraded back to 5.0 update 1, a fix would be nice, so I can get the console to work from Windows 8.

                    • 22. Re: Esxi 5.1 pci passthrough broken
                      derickso Enthusiast

                      Just adding my voice to this, I would like to upgrade to 5.1 but PCIe pass-through not working is a showstopper for me.

                      • 23. Re: Esxi 5.1 pci passthrough broken
                        THHV Lurker

                        +1

                         

                        XEON E3-1230V2 / ASUS P8CWS passthrough "Panther Point AHCI Controller" = ESXi 5.1 crash!

                         

                        Works in 5.0.0U1

                         

                        Regards

                        Thomas Kristensen

                        • 24. Re: Esxi 5.1 pci passthrough broken
                          srwsol Enthusiast

                          Has anyone who has full maintenance opened an incident about this to VMWare?  Unfortunately I have just the basic essentials kit license, so it would cost me $299 to open an incident.  If somebody in this thread who is having this problem can open an incident without charge I highly encourage you to do so.

                           

                           

                          Scott W.

                          • 25. Re: Esxi 5.1 pci passthrough broken
                            Batmac Lurker

                            Hello all,

                            This to confirm that I am also having the purple screen (crash with dump) as soon as I add a PCI and/or PCIe device in passthrough mode to a VM, then launch the VM.

                            System stable when no passthrough selected however.

                            • 26. Re: Esxi 5.1 pci passthrough broken
                              NealSu Novice

                              Confirmed, too.

                               

                              i've spent more than just two hours. obviously using the wrong keywords searching for others with this issue and more frustratingly even trying to troubleshoot what exactly was the cause for my setup not working anymore. Finally i got the right keyword leding me to this thread!

                               

                              i had issues with installing ESXi to flashdrives (USB, SD-card) before, so i thought it was an issue with the bootbank, i believed that it was related to settings/config not saved after reboots after switching from HDD to SSD. Or maybe, because i've been using HP custom image, which had an issue of its own. Also suspected it might be, because i installed over an exisiting installation without prior formating. I've thought of so many different possibilities, that i'm really relieved to see others with this issue.

                               

                              Anyway, i've successfuly used USB-passthrough with 5.0 u1 and when upgrading to 5.1 (also even after a clean install of 5.1), it is possible to mark USB for passthrough, but after reboot, it's neither available nor marked - i didn't check ESX.conf yet.

                               

                               

                              i'm using an HP ProLiant ML110 G7. The onboard USB can't be passed through, but the onboard NICs can. Those are listed as "PCI Express Root" though, so it is likely that it really might be only related to PCI and not PCIe.

                               

                              Would also appreciate a patch for this and am going to switch back to 5.0 u1 for the timebeing.

                              • 27. Re: Esxi 5.1 pci passthrough broken
                                Bembel Novice

                                Hi all,

                                 

                                having exactly the same issue with a simple hardware vendor certified PCI-X SCSI adapter which worked like charm under ESXi 5.0 for months.

                                If I remove the pass-through device in the VMs configuration I am having no problems at all.

                                The pass-through device shows up correctly in the host's configuration though.

                                 

                                I have already opened a call at VMware, uploaded logs and screenshots and will be waiting for a "cure".

                                 

                                Until now I have not rolled back to ESXi 5 since I want to be able to reproduce the crash if VMware asks me to.

                                 

                                System:

                                 

                                HP ProLiant DL 360 G6 (latest firmware)

                                LSI/Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra 320 SCSI with attached HP Autoloader 1/8 G2 tape library

                                • 28. Re: Esxi 5.1 pci passthrough broken
                                  srwsol Enthusiast

                                  Which issue are you having?  Is ESXi 5.1 crashing when you pass through the SCSI adapter, or does it just disappear from the eligible device list for the VMs after you select it as a pass through device and reboot ESXi?

                                  • 29. Re: Esxi 5.1 pci passthrough broken
                                    Bembel Novice

                                    Since the pass-through device shows up correctly when the ESXi host is running, the host only crashes when a VM is starting with this device configured.

                                    The crash actually happens at 95% of the event "Power On virtual machine".

                                    1 2 3 4 Previous Next