From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Lalancette Subject: Re: [PATCH] Print Guest VMCS state on vmexit failure Date: Tue, 20 Oct 2009 10:57:39 +0200 Message-ID: <4ADD7B83.2050603@redhat.com> References: <1256025045-4972-1-git-send-email-clalance@redhat.com> <4ADD70CB.10109@redhat.com> <4ADD77F0.6010102@redhat.com> <20091020085522.GA6416@develbox.linuxbox.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Avi Kivity , kvm@vger.kernel.org, nikola.ciprich@linuxbox.cz To: Nikola Ciprich Return-path: Received: from mx1.redhat.com ([209.132.183.28]:9653 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751386AbZJTI5q (ORCPT ); Tue, 20 Oct 2009 04:57:46 -0400 In-Reply-To: <20091020085522.GA6416@develbox.linuxbox.cz> Sender: kvm-owner@vger.kernel.org List-ID: Nikola Ciprich wrote: > Hi, > maybe it's stupid question, but is this available also when qemu/kvm > is started using libvirt & stuff? I think it uses monitor so it's > inaccessible for user no? Yes and no. The monitor is inaccessible when using libvirt, but I totally forgot that qemu dumps the register state to stderr before abort()'ing on an unknown vm exit. Libvirt takes the output from stderr and stores it in /var/log/libvirt/qemu/. So you would still be able to see this output when using libvirt. -- Chris Lalancette