Comment 4 for bug 1781038

Revision history for this message
Daniel Axtens (daxtens) wrote :

Based on the most recent information we have available to us (2018-05-09):

1. What is the server model and at least basic config info (I/O cards, firmware level)? Use /proc/meminfo, etc. Attach the syslog and the /var/log/libvirt/qemu logs.

I am struggling a bit to determine the server model, but I'm uploading the relevant logs.

2. What is running on the host (at least uname -a). Sounds like from comment above like it's an older fix level, so let's get it updated to the curent level (and ensure the problem still exists) before proceeding: There is zero point in trying to figure out whether fixes that are known to exist in 16.04 are in this *particular* build level.

Linux apsoscmp-as-a4p 4.4.0-109-generic #132-Ubuntu SMP Tue Jan 9 20:00:40 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

I don't have any answers for (3); the user has been asked.