From mboxrd@z Thu Jan  1 00:00:00 1970
From: Hui Kang <hkang@cs.sunysb.edu>
Subject: Is this a bug of xentrace?
Date: Sat, 09 May 2009 14:56:47 -0400
Message-ID: <4A05D1EF.2090405@cs.sunysb.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

Hi,
I am using xentrace to trace the events of guest domains on a host 
physical machine.  In the parsed trace file,
if the guest domain is created on the host machine, then the entry is good
switch_infprev    [ old_domid = 0x00000002
// the guest domain has a id of 2.
switch_infnext    [ new_domid = 0x00000000

However, if the guest domain is migrated from another host machine,  the 
parsed trace file shows
switch_infprev    [ old_domid = 0x00007ffff
// the guest domain has a id of 2.
switch_infnext    [ new_domid = 0x00000000
Even the domain Id is 2, it shows 0x00007ffff.
Can anyone explain this? Thanks.