public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Mike Kelly <pioto@pioto.org>
Cc: kvm@vger.kernel.org
Subject: Re: Segfault while booting Windows XP x64
Date: Tue, 31 Mar 2009 15:53:06 +0300	[thread overview]
Message-ID: <20090331125306.GD26286@redhat.com> (raw)
In-Reply-To: <20090331085025.41ae2983@aether.home.pioto.org>

On Tue, Mar 31, 2009 at 08:50:25AM -0400, Mike Kelly wrote:
> On Tue, 31 Mar 2009 08:54:48 +0300
> Gleb Natapov <gleb@redhat.com> wrote:
> 
> > On Mon, Mar 30, 2009 at 11:26:52PM -0400, Mike Kelly wrote:
> > > I'm on a Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz, using a 2.6.29
> > > vanilla kernel, x86_64. kvm userland version 84.
> > > 
> > > When I try to boot my x64 Windows XP, it gets partway through the
> > > windows booting process, with the progress bar and what not. Then, I
> > > get the attached backtrace.
> > > 
> > > The various -no-kvm options don't seem to make a difference.
> > > 
> > > I created, and was able to boot, this image using linux 2.6.28. I'll
> > > give it a shot again later to confirm that is still the case.
> > > 
> > Are you sure you have write permission to that image?
> 
> Hmm, I thought I did, but looks like I messed up my mount this time
> around. Dang.
> 
> That still shouldn't cause a segfault, though. But, yes, fixing my
> mount fixes the crash.
> 
This crash is known and fix is been working on. It happens on IO
cancellation path and usually you get there if you don't have write
permission to you image.

--
			Gleb.

  reply	other threads:[~2009-03-31 12:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31  3:26 Segfault while booting Windows XP x64 Mike Kelly
2009-03-31  5:54 ` Gleb Natapov
2009-03-31 12:50   ` Mike Kelly
2009-03-31 12:53     ` Gleb Natapov [this message]
2009-03-31 13:02       ` Mike Kelly

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=20090331125306.GD26286@redhat.com \
    --to=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=pioto@pioto.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