Bureaucrats, confirmed, Administrators
4,558
edits
Changes
no edit summary
== Analyze Failures ==
=== Background ===
This question was a challenge because I have never done kernel debugging, or used QEMU before. But a few doses of Google later, and using simple deduction based on other experiences, I'm getting through.
So, I installed QEMU + dependencies on my Bionic workstation.
=== Command to Start ===
> Please show the commands you use to start via libvirt with this XML.
=== Apache ===
> Apache is not starting, why?
There's a syntax error on line 153 of /etc/apache2/apache2.conf. More accurately, it can not open the file that it's trying to open at /etc/apache2/extra.conf. And actually, looking at that file, someone with a sense of humor symlinked it to <code>/dev/urandom</code> -- which is why Apache has a problem with the syntax :-D
=== Crash File ===
> What is going on with /var/crash/_usr_sbin_postconf.1000.crash?
TBD == Makefile Weirdness (LDFLAGS ) ==
> It turns out this change actually made LDFLAGS empty. Why?
I thought this was a trick question, because it looked like the syntax for $CFLAGS and $CPPFLAGS are incorrect. But, that syntax actually does look correct. Since the sed expression also looks correct, I have to surmise thought that somehow CFLAGS and/or LDFLAGS weren't configured correctly. But that's was only a guess. '''R'''eading '''T'''he '''F'''ine '''M'''anual on <code>dpkg-buildflags</code>, it tells me that <span style="background-color:#a8e2a8;"> <code>LDFLAGS</code> defaults to empty. So sed is a no-op, and LDFLAGS would still be empty.</span>