This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] win2008r2sp1 AllocatePage cause Bug check 0x000000C2 while m

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] win2008r2sp1 AllocatePage cause Bug check 0x000000C2 while migration
From: alice wan <wanjia19870902@xxxxxxxxx>
Date: Sat, 30 Apr 2011 17:37:41 +0800
Delivery-date: Sat, 30 Apr 2011 02:38:45 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=HTEj6wyNY7J/siOoLK+Ilak0QQmernukACdUH5OwYuY=; b=SDhGq/rcqY8/qBLOt+8nfwgCP4rrfZYLIxsfODyMlYLV7/PiB7pWLRJF3rZTTAemPa Uzhjn2WzkRBjcxQPKheknwFrvNXpIslGQ4HT2BduYwu3B1Nc5tCaEWlYyAQaUjGRQ6HN QYm/xYBQhcC+/Al2f8iclVcWqiIudvnM3YV5M=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=TUoW53ZeI2rd7zXJhx8/csBAwouAJ2dDZrSyJVB8OGOyCsvBRF7C9lVo/zroQrx8a2 kiKCPeB92wvvtr/JAGJmZHizdlGVkyYHFZurWjVKszML8y6sl3vNEErNfGP8CgAjYo+X LDYvYd1lIJK27jYnTQEV0xgQeWab98JKQGDsA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
hi james,
    the win2008r2 vm crash problem while migration seems related about the AllocatePage.
    according to the previous  BSOD info, we modified code to test if page address after AllocatePage is FFFFFA8000000000 or FFFFFA8000000002. if FFFFFA8000000000 , then free it immediately, and allocate again.
    the test result shows
12948535073500: XenPCI --- AllocatePages IRQL = 0, Buf = FFFFFA8000000000
12948535073500: XenPCI     XEN_INIT_TYPE_RING - tx-ring-ref = FFFFFA8000000000
12948535073500: XenPCI     test - tx-ring-ref = 18446738026395598848
12948535073515: XenPCI --- FreePages IRQL = 0, Buf = FFFFFA8000000000
12948535073515: XenPCI FreePages 1
12948535073515: XenPCI FreePages 2
Log-dirty command enable
Log-dirty command disable
XenPCI     Bug check 0x000000C2 (0x0000000000000042, 0xFFFFFA8000000000, 0x0000000000000000, 0x0000000000000000)
reset requested in cpu_handle_ioreq.
Issued domain 1436 reboot
    the previous test result without no modification of code is vm crashed, BSOD  is also 0x000000C2.
    it means when it call ExAllocatePoolWithTag in AllocatePage func, the return address is already wrong.
    is this the bug of win2008r2, even pactched with sp1?
    And the curious thing is why it always happened in vif allocate ? sometimes tx-ring-ref, sometimes rx-ring-ref
    any advice?
    maybe, later, we can do some test about allocate,free in win2008r2sp1 image without pv.
Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] win2008r2sp1 AllocatePage cause Bug check 0x000000C2 while migration, alice wan <=