qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Dunrong Huang <riegamaths@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Jordan Justen <jordan.l.justen@intel.com>
Subject: Re: [Qemu-devel] VM can not boot after commit 235e898
Date: Tue, 4 Jun 2013 10:51:07 +0300	[thread overview]
Message-ID: <20130604075107.GJ4725@redhat.com> (raw)
In-Reply-To: <CAOZVR5YM3oDDnRX+g=6_tWPVLjL=niN+54Ge2_baBL2AuggCxg@mail.gmail.com>

On Tue, Jun 04, 2013 at 03:47:47PM +0800, Dunrong Huang wrote:
> On Tue, Jun 4, 2013 at 2:47 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
> 
> > Il 04/06/2013 05:47, Dunrong Huang ha scritto:
> > >
> > > QEMU command:
> > > ~/usr/bin/qemu-system-x86_64 -enable-kvm -m 1024 debian-append.img
> > >
> > > git bisect tells that the following commit causes this bug:
> > >
> > > commit 235e8982ad393e5611cb892df54881c872eea9e1
> > > Author: Jordan Justen <jordan.l.justen@intel.com
> > > <mailto:jordan.l.justen@intel.com>>
> > > Date:   Wed May 29 01:27:26 2013 -0700
> > >
> > >     kvm: support using KVM_MEM_READONLY flag for regions
> > >
> > >     For readonly memory regions and rom devices in romd_mode,
> > >     we make use of the KVM_MEM_READONLY. A slot that uses
> > >     KVM_MEM_READONLY can be read from and code can execute from the
> > >     region, but writes will exit to qemu.
> > >
> > > After reverting this commit, VM can boot normally.
> >
> > A patch is queued for that.  Using kernel 3.8 or reverting the commit
> > will both work.
> >
> Ok, thanks for information, I will try it.
> 
The fix is 651eb0f4 and you claim it is still fails for you. This is
strange because the commit fixed the problem for everyone else. Can you
double check that you are testing the right commit and you recompiled
and reinstalled?

--
			Gleb.

  reply	other threads:[~2013-06-04  7:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-04  3:47 [Qemu-devel] VM can not boot after commit 235e898 Dunrong Huang
2013-06-04  6:41 ` Jordan Justen
2013-06-04  7:46   ` Dunrong Huang
2013-06-04  6:47 ` Paolo Bonzini
2013-06-04  7:47   ` Dunrong Huang
2013-06-04  7:51     ` Gleb Natapov [this message]
2013-06-04  8:26       ` Dunrong Huang
2013-06-04 17:03         ` Jordan Justen
2013-06-05  2:44           ` Dunrong Huang
2013-06-05  7:34             ` Dunrong Huang
2013-07-24  9:58             ` Alexander Graf
2013-07-24 15:16               ` Paolo Bonzini
2013-07-24 15:21                 ` Gleb Natapov
2013-07-24 15:31                   ` Alexander Graf
2013-07-24 16:17                     ` Gleb Natapov
2013-07-24 16:26                       ` Alexander Graf
2013-07-24 16:53                         ` Gleb Natapov
2013-07-24 20:25                           ` Alexander Graf
2013-07-25 11:30                             ` Gleb Natapov
2013-07-24 20:34                           ` Andreas Färber

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=20130604075107.GJ4725@redhat.com \
    --to=gleb@redhat.com \
    --cc=jordan.l.justen@intel.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=riegamaths@gmail.com \
    /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).