Bug 2567

Summary:	Build appliance QEMU failure disappears too quickly for me to figure out what's going on
Product:	[Build System, Metadata & Runtime] Runtime	Reporter:	Dave Stewart <david.c.stewart>
Component:	build-appliance	Assignee:	Ross Burton <ross.burton>
Status:	RESOLVED INVALID	QA Contact:
Severity:	enhancement
Priority:	Medium	CC:	alexandru.damian, jessica.zhang, laurentiu.serban, poky.bs.watcher, poky.watcher, sgw, song.liu
Version:	1.2
Target Milestone:	Future
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Don't know

Description Dave Stewart 2012-06-08 21:59:54 UTC

I did a build of poky-tiny (which apparently Hob should not have allowed because it hadn't cleaned out libc or some such). Anyway, the resulting system wouldn't boot, which is not a surprise. But the window launching QEMU disappeared so quickly that I couldn't see the error message - if any.

If the qemu craps out quickly, there should be a way to capture the messages from the window before it disappears.

Comment 1 Cristian Iorga 2013-04-02 12:13:24 UTC

This is a enhacement, namely:

Better report errors if qemu crashes while trying to start a virtual machine.
There should be a way to capture boot and crash messages before qemu ends its execution.

Comment 2 Alexandru Damian 2013-04-02 13:11:00 UTC

Please don't change target milestone and severity of an issue if not prior agreed so with the bug triage team.

Please mail Jessica with the target/severity request change.

Comment 3 Cristian Iorga 2013-04-02 13:14:52 UTC

Hello Jessica,

Judging from the description of this bug report, this is a request for an enhancement (see my comment). Can you please change the target milestone and severity accordingly, if you do agree with me?

Thanks,
Cristian

Comment 4 Ross Burton 2016-02-02 14:52:49 UTC

If qemu craps out so quickly you can't see what's happening, you can pass "console" to runqemu to get the full output in the terminal.