Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
bug 716498 introduced a regression when booting x86_64 pv guest with
following xm config
-------------
maxmem = 4096
memory = 512
vcpus = 1
kernel = "mp2mkernel"
extra = "ignore_loglevel console=hvc0 "
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "preserve"
------------
Problem started to appear with usage of extend_brk in this patch-set.
In RHEL6 there is another commit that fixes guest boot failure by removing
usage of extend_brk 2d5f59f50.
Bisecting upstream doesn't help, a crash magically disappears on with unrelated
commit. Failing address is always the same however after adding extra debugging
code failing address changes to another constant. Looks like crash point
depends on the kernel size.
So far no know fix. Thus reopening this bug.
Version-Release number of selected component (if applicable):
How reproducible:
always
Additional info:
guest kernel 2.6.32-169
(In reply to comment #1)
> Patch range 1382eec..c5b979d for reverting.
We can keep
91ceeef [virt] Unset CONFIG_DEBUG_FORCE_WEAK_PER_CPU on x86/x86_64 platforms
8d641fc [virt] xen: bump memory limit for x86 domU PV guest to 128Gb
Which fix the incorrect config and bumps 32-bit PV guest memory.
Comment 5RHEL Program Management
2011-07-26 10:20:14 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update release.
(In reply to comment #4)
> (In reply to comment #1)
> > Patch range 1382eec..c5b979d for reverting.
>
> We can keep
>
> 91ceeef [virt] Unset CONFIG_DEBUG_FORCE_WEAK_PER_CPU on x86/x86_64 platforms
> 8d641fc [virt] xen: bump memory limit for x86 domU PV guest to 128Gb
>
> Which fix the incorrect config and bumps 32-bit PV guest memory.
Yes sure, these patches shouldn't hurt.
Reproduced on kernel-2.6.32-169.el6.
The test step is simply xm create with the config in comment 0, with kernel replaced with "vmlinuz-2.6.32-169.el6.x86_64". xm console has nothing output. xm dmesg has the same crash info as comment 28 of bug 716498.
Verified on kernel -176 and -194, that the same crash info does not occur. They can output messages on the console, until crashed at
VFS: Cannot open root device "(null)" or unknown-block(0,0)
which is expected.
Putting this to VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2011-1530.html