On Tue, Jun 4, 2013 at 2:41 PM, Jordan Justen <jljus...@gmail.com> wrote:
> Fixed in 651eb0f4? > No, it still fails. > > On Mon, Jun 3, 2013 at 8:47 PM, Dunrong Huang <riegama...@gmail.com> > wrote: > > > > 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.jus...@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. > > > > Any information I should provide? > > > > -- > > Best Regards, > > > > Dunrong Huang > > > > Homepage: http://mathslinux.org > > > -- Best Regards, Dunrong Huang Homepage: http://mathslinux.org
