[Vm-dev] Unexpected external library dependencies on linux

tim Rowledge tim at rowledge.org
Thu Apr 16 21:55:46 UTC 2020

> On 2020-04-16, at 2:42 PM, David T. Lewis <lewis at mail.msen.com> wrote:
> On Thu, Apr 16, 2020 at 06:53:51PM +0200, Levente Uzonyi wrote:
>> However, recent VMs (202003050026 from March, 202004160240 from April) 
>> also depend on the following:
>> libuuid.so.1
>> libutil.so.1
>> libpulse-simple.so.0
>> libasound.so.2
>> The last two are the most worrying as servers usually don't need or have 
>> sound installed. So, without pulseaudio installed, these VMs won't start.
>> Does anyone know how and why those new dependencies got there?
>> (These are the dependencies of the VM binary itself not dependencies of 
>> external plugins).
> Hi Levente,
> I don't know the answer to your question, but the sound dependencies are
> likely associated with the VM plugin modules vm-sound-*.so as opposed to
> any of the conventional VM plugins such as UUIDPlugin.so. It is quite
> likely that specifying the -vm-sound-null parameter to the VM will bypass
> any problems. Otherwise, deleting the offending vm-sound-* modules should
> be harmless.

Is it possible some edit to the build files made the pulse audio stuff a default (this was discussed recently) and set it to link to the VM instead of the (expected to be) separate vm-sound-* module? 

tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Strange OpCodes: CSD: Charge Surreptitiously to DOE

More information about the Vm-dev mailing list