Replies: 17 comments 46 replies
-
You sire, is a genius! |
Beta Was this translation helpful? Give feedback.
-
Glad it helped! Just to add to this I learned that by design the Coral will change its device ID when the first inferance is attempted, so when I just rebooted my ESXi and it came back as the dreaded Global Unichip Corp, I wanted to test that, so I started up Frigate, the first search for the TPU failed - as expected.
At this point the device ID changed And when Frigate auto restarted we're good again
|
Beta Was this translation helpful? Give feedback.
-
This post will be extremely useful if I can ever find a google coral, easier to buy a kidney atm. My setup is Esxi 6.5 ---> Xpenology (Synology) ---> Docker on synology |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Just to add some things here to help others. I've been running ESXi 7 on my home server for some time. I have Frigate running on an Ubuntu VM. The only way I could get the Coral USB to work reliably was to us a cheap USB3 PCIe X1 controller card and then to use PCI pass-through on that for the whole card on that VM (after having to set; VMKernel.Boot.disableACSCheck = true on the ESXi server to allow the card to be passed through). What I did find as part of my testing was that you can't have a VM with multiple PCI devices passed through to the same VM otherwise it can cause the PCIe USB controller card to drop out, and you also can't have both USB PCI pass through and connected USB devices on the same VM - otherwise the USB bus scanning under Linux seems to get confused. Another thing to be aware of... I had set Frigate to use an NFS store for the recordings... By default the internal database for Frigate was getting stored on the same NFS path.
and in my Frigate configuration.yml file I have;
where /home/ubuntu/frigate/db is the local directory on SSD where the frigate DB is getting stored and /mnt/SECURITYCAM/frigate is the NFS directory where the recording are being stored. It would be great if the documentation for Frigate could specifically mention this as it caused me many hours to trace as similar errors were memory related - but this was not the case in this situation. On my VMware server, I'm getting consistently 7.6ms for the inference speed using the Coral USB stick and everything is working great! (I was previously getting about 40ms inference speed using the CPU detector and that was with an AMD 5950x). The hardest thing was actually getting hold of a Coral USB stick in the first place and figuring out the quirks under VMware! |
Beta Was this translation helpful? Give feedback.
-
thanks guys, |
Beta Was this translation helpful? Give feedback.
-
So.. I've been working to get my USB Coral to work on my R430 running ESXi 6.7.. Tried the above steps. The commands are accepted, but even if I reboot ESXI, I still end up with the same. Did I miss a step somewhere? localhost:~] esxcli hardware usb passthrough device list 2 3 1a6e 89a true yes Global Unichip Corp. Product: VMware ESXi |
Beta Was this translation helpful? Give feedback.
-
sadly this didn't work for me, ran " esxcli system module set -m=vmkusb -e=FALSE", rebooted but still see [root@asuspn50:~] esxcli hardware usb passthrough device list |
Beta Was this translation helpful? Give feedback.
-
Anyone tried and got it working on ESXi 8.0? |
Beta Was this translation helpful? Give feedback.
-
Ditched the whole ESXi setup because of this. |
Beta Was this translation helpful? Give feedback.
-
I run esxi 8.0.x Also running HassOS as a VM with 3 USB devices passed through (not controller, but devices). All runs fine. Now I want to pass through Coral to another VM... BUMP. When I run |
Beta Was this translation helpful? Give feedback.
-
JFYI - For those interested in using the Coral USB w/latest ESXi releases, please see the following write-up which has all the details. Please do not disable the vmkusb module, while this may have seem to work with earlier releases of ESXi, its not an actual solution and will disable all USB functionality for newer releases of ESXi https://williamlam.com/2023/05/google-coral-usb-edge-tpu-accelerator-on-esxi.html |
Beta Was this translation helpful? Give feedback.
-
William, cool! I will test asap and report back. |
Beta Was this translation helpful? Give feedback.
-
Does this guide work for 6.7? The advanced USB quirks parameters? If not, are they needed in 6.7? Thanks. |
Beta Was this translation helpful? Give feedback.
-
So... As I was saying that I figured it out and it works. Well. For a small amount of time yes. But after like a week the USB coral stopped to work. So like 70% of the steps needed to be redone again. And after another week the same. So basically it was not stable... |
Beta Was this translation helpful? Give feedback.
-
re: PCIe Coral - There's no easy fix after speaking w/Engr on our side and best option would be for Coral team to update/fix their firmware so that it doesn't violate the PCIe specification (as originally shared from one of our Principal Engr). I've even filed an issue google-coral/libedgetpu#48 but haven't had any response from the team. I would recommend folks here chime in there to see if we can get Coral team to consider this augmentation to their firmware by either hiding MSI-X (which might be needed to function, not sure honestly OR actually fix the firmware so that it conforms to PCIe spec and would allow ESXi to properly consume it) re: USB Coral - I've heard of some folks running into instability issues but I know others who've not had any problems over duration of time. The only difference that I could tell is that ones not having issues were using recent systems including Intel NUC 11th Gen or later ... even for myself, I was using Intel NUC 12/13th Gen |
Beta Was this translation helpful? Give feedback.
-
Sorry to bump this "old" post. Im using the USB Coral with ESXI 8 on a Intel NUC13. Its working very fine, BUT after some time (few days, maybe one week) the Coral stops working, Frigate is stopped and during restart complaining about not finding the TPU. ESXI shows:
My Setup was done after reading https://williamlam.com/2023/05/google-coral-usb-edge-tpu-accelerator-on-esxi.html My Setup is ESXI 8 > VM with HassIO > Frigate as HA Addon. If this issue is happening i rerun the following on the ESXI-Host:
But after that, the Google-Coral is completely gone:
So only way to go if this happens is walking to the NUC and reinserting the USB Coral, Mapping the Coral "GlobalChip" via ESXI to my Ubuntu VM, reruning the initialization. Then i need to restart the usbarbitator on ESXI Host, this also affects my Skyconnect USB Stick, so in that timefrime no ZigBee Device is working. And then Shutdown HA VM, remapping the Google-Coral as "Google Chip" to the HA VM and starting everything up again.... it is a mess for me... :-/ Someone fighting with the same problems? |
Beta Was this translation helpful? Give feedback.
-
Hey all - I've just spent a couple of hours troubleshooting Coral USB passthrough from ESXi 6.7 to Ubuntu then my frigate container - It looks like a reasonably common problem and I couldn't find this solution on Google so I thought I'd post it here in the hopes it might help someone.
Inititally I plugged my new Coral into my ESXi host and checked it was available
Adding that as a USB Device on my docker host (Ubuntu) then running
lsusb
didn't seem to workAfter some googling I discovered that I could disable the 'new' USB module in esxi so thought it was worth a try
esxcli system module set -m=vmkusb -e=FALSE
This requires a reboot
Low and behold
That's already looking better
Then
lsusb
on my docker host againAnd ....
Also make sure you are running a USB3 USB controller if using a USB3 device!
Hope this helps anyone
Beta Was this translation helpful? Give feedback.
All reactions