15.02.2013 07:43, Kevin O'Connor wrote: > On Fri, Feb 15, 2013 at 04:10:59AM +0100, Laszlo Ersek wrote: >> On 02/15/13 02:22, Kevin O'Connor wrote: >>> On Thu, Feb 14, 2013 at 08:16:02PM -0500, Kevin O'Connor wrote: >>> By chance, are you using an older version of kvm? There was a bug in >>> kvm that caused changes to memory mapped at 0xe0000-0xfffff to also be >>> reflected in the "rom" image at 0xfffe0000-0xffffffff. It was my >>> understand that this bug was fixed though. >> >> You are great! Disabling KVM for the guest (/domain/@type='qemu') made >> the reboot work on both the RHEL-6 devel version of qemu and on upstream >> 1.3.1. >> >> (I didn't try suspend/resume yet.) >> >> Do you recall the precise commit that fixed the "reflection"? I've been >> eyeballing kvm commit messages for a few ten minutes now, but of course >> in vain. (CC'ing Gleb and Marcelo.) > > I found this email thread: > > http://kerneltrap.org/mailarchive/linux-kvm/2010/9/21/6267744 > > and: http://marc.info/?l=kvm-commits&m=128576215909532
This patch is more than 2 years old and is applied to all more or less recent qemu versions. This does not tell us why disabling kvm (with this patch applied!) makes a difference. So there must be another (maybe similar) bug somewhere... /mjt
