From: Gleb Natapov <gleb@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Jordan Justen <jordan.l.justen@intel.com>,
qemu-devel Developers <qemu-devel@nongnu.org>,
Dunrong Huang <riegamaths@gmail.com>,
Hannes Reinecke <hare@suse.de>,
Paolo Bonzini <pbonzini@redhat.com>,
Jordan Justen <jljusten@gmail.com>
Subject: Re: [Qemu-devel] VM can not boot after commit 235e898
Date: Wed, 24 Jul 2013 19:53:35 +0300 [thread overview]
Message-ID: <20130724165335.GN6029@redhat.com> (raw)
In-Reply-To: <51F00041.3010005@suse.de>
On Wed, Jul 24, 2013 at 06:26:41PM +0200, Alexander Graf wrote:
> >before. Are you saying configuring BIOS memslot differently solves the
> >problem?
>
> Git bisect pointed to the commit mentioned in this email. The
> following patch also gets me a working guest again:
>
> diff --git a/kvm-all.c b/kvm-all.c
> index 4fb4ccb..deca9e5 100644
> --- a/kvm-all.c
> +++ b/kvm-all.c
> @@ -1455,7 +1455,7 @@ int kvm_init(void)
> s->irq_set_ioctl = KVM_IRQ_LINE_STATUS;
> }
>
> -#ifdef KVM_CAP_READONLY_MEM
> +#if 0 //def KVM_CAP_READONLY_MEM
> kvm_readonly_mem_allowed =
> (kvm_check_extension(s, KVM_CAP_READONLY_MEM) > 0);
> #endif
>
Can you disable emulate_invalid_state on 3.7? What happens on upstream kernel
(works for me obviously :)).
--
Gleb.
next prev parent reply other threads:[~2013-07-24 16:53 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
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 [this message]
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=20130724165335.GN6029@redhat.com \
--to=gleb@redhat.com \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=hare@suse.de \
--cc=jljusten@gmail.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).