public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: "Fischer, Anna" <anna.fischer@hp.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: pci-stub error and MSI-X for KVM guest
Date: Mon, 4 Jan 2010 07:16:59 -0800	[thread overview]
Message-ID: <20100104151659.GA27601@sequoia.sous-sol.org> (raw)
In-Reply-To: <0199E0D51A61344794750DC57738F58E6D723AADC9@GVW1118EXC.americas.hpqcorp.net>

* Fischer, Anna (anna.fischer@hp.com) wrote:
> > Ouch.  Can you do "debuginfo-install qemu-system-x86" to get the debug
> > packages, then attach gdb to the QEMU process so that when you do lspci
> > -v
> > in the guest (assuming this is QEMU segfaulting) you'll get a backtrace?
> 
> I don't know how I can tell virt-manager through the GUI to enable debug mode, e.g. call virt-manager with '-s'. From the command line I can attach gdb like this, but when running virt-manager from the GUI then I cannot connect to localhost:1234. However, the issues only arise when starting virt-manager from the GUI. I can't find the configuration option to somehow tell that I want it to be launched with '-s'?

Just looking for a backtrace of the qemu-kvm process itself.  So after
you launch it via virt-manager, gdb /usr/bin/qemu-kvm $(pidof qemu-kvm)
should be sufficient.

thanks,
-chris

  reply	other threads:[~2010-01-04 15:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-21 18:15 pci-stub error and MSI-X for KVM guest Fischer, Anna
2009-12-21 19:19 ` Chris Wright
2009-12-21 19:34   ` Fischer, Anna
2009-12-21 19:58     ` Chris Wright
2010-01-04 11:37       ` Fischer, Anna
2010-01-04 15:16         ` Chris Wright [this message]
2010-01-05 10:25           ` Fischer, Anna
2010-01-08  0:50             ` Chris Wright
2010-01-08 11:04               ` Daniel P. Berrange
2010-01-08 18:03                 ` Chris Wright
2010-01-04 11:42       ` Fischer, Anna

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100104151659.GA27601@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=anna.fischer@hp.com \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox