Resuming bug hunt

Tuesday, December 12, 2017

Spice server de-sync bug

Still getting this one after a few seconds, and this is "new" (saw it last week before leaving for Paris):

ddd@f25-turbo[version] spice-streaming-agent> DISPLAY=:1 spice-streaming-agent -c noblock=yes

spice-streaming-agent[2967]: UNKNOWN msg of type 5 spice-streaming-agent[2967]: BAD VERSION 0 (expected is 1) spice-streaming-agent[2967]: BAD VERSION 108 (expected is 1) spice-streaming-agent[2967]: BAD VERSION 97 (expected is 1) spice-streaming-agent[2967]: read command from device FAILED -- read 1 expected 8 spice-streaming-agent[2967]: FAILED to read command

Fixing networking in Linux VM

The Linux partition VM that I had repaired after the upgrade to High Sierra was still not functional. It had no network. After looking for the usual suspects in a VM, I traced it back to having no /etc/sysconfig/network-scripts/ifcfg-ens160 for my network card.

Why this file disappeared I don't know, but this seems to be a somewhat regular occurence. Recreated it as indicated in that thread, and everything is fine now.

Adding MSYS2 in Windows 10 VM

I added MSYS2 in my Windows 10 partition VM. What is annoying is that after installing it, I have only 5G left out of a 40G disk. I fondly remember a time where filling a 40MB disk took some effort. Now, a basic OS with just some development tools (Visual Studio + MSYS2) takes 35G.

At the same time, disk space on typical corporate laptops remains an issue. With a 500G disk, running a main OS and two VMs is a bit problematic. Of course, I can carry around a 3TB disk to have extra space, but if 3TB disks are available, why do beancounters insist on me having to buy it rather than have it INSIDE the laptop to start with?

So for now, I guess I will put data files remotely on the main partition.

Installing Windows 10 VM on Muse

Started installation of a Windows 10 VM on Muse. For some reason, the Windows10 VM on Turbo runs until the point where I connect to it with virt-manager, at which point it dies abruptly.

I suspect this is related to the de-sync issue I am seeing above, and that means my SPICE server library is not working correctly. Indeed, connecting with my homebuilt spicy client works (that one was actually built with c3d/build). It's annoying if version mismatches between client and server cause the guest to die.

Looking at the qemu log, I see:

/usr/bin/qemu-system-x86_64: symbol lookup error: /usr/local/lib/ undefined symbol: celt051_mode_create
2017-12-12 17:43:27.214+0000: shutting down, reason=crashed

So the problem is really with the dynamic linking of libcelt051. Probably something wrong with the way c3d/build links libraries.

Of course, now the Windows10 VM on Turbo is complaining that it did not restart correctly, adn is showing all sorts of nasty messages in beautiful blue. The color palette at Microsoft improved, the messages did not.


A lot of this setup effort is related to my attempts to add some Windows and Fedora machines to my Jenkins setup.