From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: 9d02b43dee0d7fb18dfb13a00915550b1a3daa9f (xen PVonHVM: use E820_Reserved area for shared_info) causes regression with 32-bit PVHVM guests (v3.8-rcX) on Xen 4.1 Date: Wed, 13 Feb 2013 13:11:03 -0500 Message-ID: <20130213181103.GC20042@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: olaf@aepfle.de, xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Hey Olaf, The commit 9d02b43dee0d7fb18dfb13a00915550b1a3daa9f (xen PVonHVM: use E820_Reserved area for shared_info) causes a regression when doing 'xm restore' (or migrate) of a 32-bit PVHVM guest with Xen 4.1. This is xen-4.1-testing with v3.8-rc7 and me just doing 'xm save ' followed by 'xm restore && xm console ' and I don't see anything on the serial console. The 'xentop' shows the guest consuming 100% cycles spinning around in pvlock_read. By just reverting this patch (well, also a7be94ac8d69c037d08f0fd94b45a593f1d45176) the problem disappears. Any thoughts of what might be wrong?