Bug 589930

I suspect this bug is related to https://bugzilla.redhat.com/show_bug.cgi?id=561290

I could reproduce this on my own hardware with same components:

[root@test2 ~]# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.48.el6.x86_64
[root@test2 ~]# rpm -q kernel
kernel-2.6.32-23.el6.x86_64
[root@test2 ~]# uname -a
Linux test2 2.6.32-23.el6.x86_64 #1 SMP Tue Apr 27 21:17:28 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
[root@test2 ~]# rpm -q seabios
seabios-0.5.1-0.3.20100108git669c991.el6.x86_64
[root@test2 ~]# 

Daniel

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

I tested a seabios patch for 561290,
and with that seabios, I could not duplicate this error
using a RHEL5-164 guest, and a rhel6/2.6.32-15 kernel;
qemu-kvm: 0.12.1.2-2.15.

I was working off the tip of seabios, which was same as above version.
so, that clears (the patched for better dmidecode) seabios; could be qemu or guest kernel problem...

Don,

I am not sure I follow you. Are you saying the Seabios patch made the problem go away or were you not able to reproduce it prior to the Seabios patch either?

FWIW I only saw this problem when trying to boot RHEL6 guests, not with RHEL5 ones. But that may be due to a memory layout problem so it doesn't show.

Cheers,
Jes

Hi,

With more testing I found that this is can in fact be reproduced on real hardware, by specifying an appropriate limit using the memmap= option. So reassigning it to the kernel component.

On a system with less than ~11GB of RAM, the following boot time argument should show the problem:

memmap=8G$0x100044000

With more memory, just increase the '8G' to something higher.

This happens both with upstream and the RHEL6 kernel.

Jes

Update bug title - forgot earlier when updated component

Moving to 6.1.

Jes

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

This request was erroneously denied for the current release of Red Hat
Enterprise Linux.  The error has been fixed and this request has been
re-proposed for the current release.

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

This request was erroneously denied for the current release of
Red Hat Enterprise Linux.  The error has been fixed and this
request has been re-proposed for the current release.

Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Can someone test the latest RHEL6 kernel and see if this is still a problem?  There have been several changes to the RHEL6 memory initialization code that probably fixed this problem.

Larry

(In reply to Larry Woodman from comment #19)
> Can someone test the latest RHEL6 kernel and see if this is still a problem?
> There have been several changes to the RHEL6 memory initialization code that
> probably fixed this problem.
> 
> Larry

Sorry for the late response. Qianqian will give an update soon.

(In reply to Larry Woodman from comment #19)
> Can someone test the latest RHEL6 kernel and see if this is still a problem?
> There have been several changes to the RHEL6 memory initialization code that
> probably fixed this problem.
> 
> Larry

Reproduced with:
Red Hat Enterprise Linux Server release 6.7
kernel-2.6.32-573.el6.x86_64
qemu-kvm-0.12.1.2-2.481.el6.x86_64
seabios-0.6.1.2-30.el6.x86_64

Steps:
1. Install RHEL6.7 guest on RHEL6.7 host
2. Start guest with memory 3585MB/3586MB/3608MB/3708MB/3709MB separately
3. Boot it
  
Actual results:
Guest boot successfully.

Sorry, made mistakes here, make corrections as below:

(In reply to qianqianzhu from comment #21)
> (In reply to Larry Woodman from comment #19)
> > Can someone test the latest RHEL6 kernel and see if this is still a problem?
> > There have been several changes to the RHEL6 memory initialization code that
> > probably fixed this problem.
> > 
> > Larry
> 

Tested with:
Red Hat Enterprise Linux Server release 6.7
kernel-2.6.32-583.el6.x86_64
qemu-kvm-0.12.1.2-2.481.el6.x86_64
seabios-0.6.1.2-30.el6.x86_64

Steps:
1. Install RHEL6.7 guest on RHEL6.7 host
2. Start guest with memory 3585MB/3586MB/3608MB/3708MB/3709MB separately
3. Boot it
   
Actual results:
Guest boot successfully.