2567 2012-06-08 21:59:54 +0000 Build appliance QEMU failure disappears too quickly for me to figure out what's going on 2016-02-02 14:52:49 +0000 1 1 7 Build System, Metadata & Runtime Runtime build-appliance 1.2 x86 Multiple RESOLVED INVALID Medium enhancement Future 1 david.c.stewart ross.burton alexandru.damian jessica.zhang laurentiu.serban poky.bs.watcher poky.watcher sgw song.liu --- --- Don't know oldest_to_newest 21951 0 david.c.stewart 2012-06-08 21:59:54 +0000 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. 31359 1 cristian.iorga 2013-04-02 12:13:24 +0000 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. 31364 2 alexandru.damian 2013-04-02 13:11:00 +0000 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. 31365 3 cristian.iorga 2013-04-02 13:14:52 +0000 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 58455 4 ross.burton 2016-02-02 14:52:49 +0000 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.