qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: malc <av1474@comtv.ru>
To: Gene Czarcinski <gene@czarc.net>
Cc: Mark McLoughlin <markmc@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Justin M. Forbes" <jforbes@redhat.com>
Subject: Re: [Qemu-devel] Re: audio segfault in qemu-kvm-0.11.0
Date: Fri, 23 Oct 2009 21:34:41 +0400 (MSD)	[thread overview]
Message-ID: <Pine.LNX.4.64.0910232128350.3114@linmac.oyster.ru> (raw)
In-Reply-To: <200910231111.20637.gene@czarc.net>

On Fri, 23 Oct 2009, Gene Czarcinski wrote:

> 
> The real sound hardware should not be relevant since qemu-kvm current does not 
> support sound and "has it disabled" even if, by default, there is an ES1370 
> virtual device defined.

I don't know anything about qemu-kvm and mysterious ways it walks (by
having audio stuff compiled in and yet somehow disabled)

Nor do i quite frankly understand why -soundhw es1370 was specified on
the command line.

[..snip..]

> 
> Can I reproduce the problem with qemu only (no kvm) ... If I could reproduce 
> the problem at all, then maybe.  I have no idea what causes the problem.
> 
> All occurrences of the problem were on a previous install with 
> qemu-kvm-0.11.0-6.fc12.x86_64.
> 
> I am currently running F12-Beta with qemu-kvm-0.11.0-7.fc12.x86_64 but still 
> have the "old" system "just a re-boot away".
> 
> At the time I was running (most likely) two guests ... an F11 and an F12 and 
> the guest had been running for some time (the crash did not occur immediately 
> or soon after guest start).  I was certainly doing nothing with respect to 
> sound since, as far as I was concerned, it did not work.
> 
> I had five occurrences of qemu-kvm segfault (according to grep'ing 
> /var/log/messages* between 6 October and 13 October and an addition occurrence 
> on 19 October ... all with qemu-kvm "-6".
> 
> As far as I can tell, I only have abrt data from the 19 October occurrence.
> 
> If this was a problem which I could cause "on demand", this situation may be 
> different ... but I don't.  I have not had this problem occur on my fresh 
> install of F12-Beta.
> 
> I can bring up q qemu guest and "let it sit" but I am not sure what to do to 
> cause the problem.
> 
> Comments?

Basically this - i've never seen this problem, nor to the best of my
knowledge anyone else, the only way to understand what's going on is
for you to try to reproduce it capture a backtrace, preferably with
vanilla qemu, and in having optimizations disabled.

-- 
mailto:av1474@comtv.ru

      reply	other threads:[~2009-10-23 17:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-23 13:16 [Qemu-devel] audio segfault in qemu-kvm-0.11.0 Mark McLoughlin
2009-10-23 13:31 ` [Qemu-devel] " malc
2009-10-23 13:41   ` malc
2009-10-23 13:50     ` Mark McLoughlin
2009-10-23 14:29       ` malc
2009-10-23 15:11         ` Gene Czarcinski
2009-10-23 17:34           ` malc [this message]

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=Pine.LNX.4.64.0910232128350.3114@linmac.oyster.ru \
    --to=av1474@comtv.ru \
    --cc=gene@czarc.net \
    --cc=jforbes@redhat.com \
    --cc=markmc@redhat.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).