Red Hat Bugzilla – Bug 541538
[RHEL4 Xen]: PV guest crash on poweroff
Last modified: 2011-02-16 10:49:27 EST
In point of fact, I'm going
Sigh, ignore my last (cut-off) comment. In point of fact, this bug is really a clone of BZ 428892. That is, a 32-bit guest shows a bogus value in LowTotal. However, in the process of fixing that bug, we also need to add the code into blkfront to avoid bounce buffering. Chris Lalancette
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.
Committed in 89.34.EL . RPMS are available at http://people.redhat.com/vgoyal/rhel4/
Hi Chris, Can you tell me on what kernel-xen this would reproduce? I was unable to reproduce it either with kernel-xenU-2.6.9-89.EL.i686 or -89.33.EL. When poweroff in the guest there is no "BUG". host: kernel-xen-2.6.18-236.el5.x86_64. Is it 'too' new?
It's been a long time. I don't remember if I ever reproduced this on RHEL-4 or not. The version of the host should be mostly irrelevant to the test, since it is a guest-side bug. There are 2 things you can check here: 1) Before this patch, a 32-bit RHEL-4 guest should show a bogus value in /proc/meminfo LowTotal. After this patch, the 32-bit RHEL-4 guest should show a valid value in LowTotal. 2) Make sure that the patch listed at the end of the original comment is applied. This will prevent us from using bounce buffering, which should make sure we never run into the original BUG. I'm not quite sure how to force the bug otherwise. Chris Lalancette
inside guest created with 512M memory, cat /proc/meminfo | grep LowTotal 2.6.9-89.ELxenU: LowTotal: 4294692996 kB 2.6.9-93.ELxenU: LowTotal: 524420 kB so this is VERIFIED according to comment 10.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2011-0263.html