I am happy to announce that today I was able to successfully add a Graphics Processing Unit (GPU) to my Dell PowerEdge R330 server in order to use it for Plex transcoding on a VM under ESXi. After extensive research, I ended up settling on a NVIDIA Quadro P400 which can be found used for fairly cheap these days.
Continue reading
I recently ran into an issue after deploying a new Ubuntu VM where the following message would spam my syslog server every 5 seconds:
sda: failed to get udev uid: Invalid argument
sda: failed to get sgio uid: No such file or directoryTurns out these are multipathd messages that VMware began reporting in the operating system a while back and the following resolution can safely be applied:
disk.EnableUUIDTRUEClick Ok and save. Now you must shutdown the VM and start it back up in order for changes to take effect.
The messages should now stop appearing in the logs.
In this guide I will show you how to create an Ubuntu Server 20.04 VM on ESXi 7.0 and setup basic security such as firewall and SSH key.
Head over to the releases page and download the image. For this guide, we will be using the “64-bit PC (AMD64) server install image”.
Continue readingUnder the ESXi host, navigate to Host->Manage->System->Advanced Settings and search for Syslog.global.logHost and click edit. Now input the address of the syslog server, in my case, a Graylog VM:
udp://192.168.139.11:8515
Enable SSH on the host and login. Navigate to /etc/vmware/firewall and create a file name.xml and add the following editing as needed:
<ConfigRoot>
<service id="0000">
<id>graylog</id>
<rule id='0000'>
<direction>outbound</direction>
<protocol>udp</protocol>
<porttype>dst</porttype>
<port>8515</port>
</rule>
<enabled>true</enabled>
<required>true</required>
</service>
</ConfigRoot>Save the file and reload the firewall by issuing
esxcli network firewall unload
esxcli network firewall loadYou should now start seeing logs in your syslog server. Just be warned that it is not persistent across reboots.
Recently I’ve decided to give Frigate a try since as some of you already know, motion detection on most cameras can be very flaky at times and I was looking for a permanent solution to false alerts outside my home. One of the issues I encountered during the process was Frigate suggests the use of a Google Coral Accelerator for object detection (which I was lucky enough to score one during the chip shortage) but since my Frigate instance is running under a VM on ESXi, I needed to passthrough the Coral to the VM which turns out it doesn’t work under ESXi 7.x. Simply plugging in the Coral to my PowerEdge R330 server and passing it through to the VM wasn’t enough.
Lucky, a user at the Frigate repo shared that passing through an entire USB controller to the VM instead of just the Coral DOES work so I had to give it a try. I purchased a controller from Amazon and went to work powering down the server, attaching the controller and powering back up. Once I finished toggling passthrough under ESXi settings and re-configuring the VM to use the controller with the Coral attached, Frigate successfully found it. There was one more issue, although a personal one: the fans on my server went nuts! Most Dell servers that detect a third party PCIe card in the configuration tend to increase the fans to account for the foreign device which for me, was excessively loud and unacceptable.
I then had the idea of maybe passing through the internal USB controller since I have no USB devices currently being used on this server and with the help of iDRAC Enterprice, I can manage this server remotely. The problem is even though I found the controller under the hardware tab in ESXi, I couldn’t toggle passthrough as the option showed not capable. But there had to be a way! Research led me to this article which turns out it does work!
After following the instructions in the link above my server is now running nice and quiet with the Coral being passed through the internal controller and Frigate purring along! Did I mention how awesome Frigate object detection really is?