I double checked and the configure script is properly finding the avahi headers and that liblxi and lxi are linked to the avahi libraries on both the desktop and the VM. As both the desktop and VM have the same version of avahi and other libraries installed, the only difference is that the avahi daemon is running on the desktop and not running in the VM.
Here is the output from
lxi discover on the desktop:
$ lxi discover
Searching for LXI devices - please wait...
Broadcasting on interface lo
Broadcasting on interface eth0
No devices found
$ lxi discover -m
Searching for LXI devices - please wait...
No services found
And the same as run in the VM:
$ lxi discover
Searching for LXI devices - please wait...
Broadcasting on interface lo
Broadcasting on interface eth0
Found "Siglent Technologies,SDS1202X-E,SDS1EBBXXXXXXX,5.1.3.13" on address 192.168.X.X
Found 1 device
$ lxi discover -m
Searching for LXI devices - please wait...
Error: Failed to create client: Daemon not running
No services found
Obviously lxi does not find the avahi daemon in the VM but raises no such complaint on the desktop.
I am puzzled that even when the
-m is not used, lxi cannot discover the 'scope.
I need to do some more studying of Wireshark to try and isolate any network traffic from lxi as my network interface is too busy to catch any lxi traffic just by watching it scroll by.