Sometimes immediately after grub, and sometimes goes further. Anyway, once the 
HVM domain is created, it's very likely for xen to crash on dom0's context. At 
that time, because crashing cpu does infinitely page fault on guest stack, 
another cpu then block at smp_function_call and then whole system halts. Weird!
-- Dexuan
-----Original Message-----
From: Keir Fraser [mailto:keir@xxxxxxxxxxxxx] 
Sent: 2007年7月19日 16:32
To: Cui, Dexuan; Tian, Kevin; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Anyone succeeds HVM on latest x86-64 xen
How far does it get?
 K.
On 19/7/07 09:26, "Cui, Dexuan" <dexuan.cui@xxxxxxxxx> wrote:
> I'm using a 64-bit Linux HVM guest on the latest 64-bit Xen.
>
> -- Dexuan
>
> -----Original Message-----
> From: Keir Fraser [mailto:keir@xxxxxxxxxxxxx]
> Sent: 2007年7月19日 16:21
> To: Cui, Dexuan; Tian, Kevin; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] Anyone succeeds HVM on latest x86-64 xen
>
> I definitely am able to boot a 32-bit HVM guest on 64-bit Xen with current
> unstable.
>
> -- Keir
>
> On 19/7/07 07:45, "Cui, Dexuan" <dexuan.cui@xxxxxxxxx> wrote:
>
>> It seems some c/s between 15516 and 15604 breaks x86_64 Xen.
>> IA32pae Xen c/s 15605 is OK.
>> 
>> -- Dexuan
>> 
>> -----Original Message-----
>> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Tian, Kevin
>> Sent: 2007年7月19日 14:32
>> To: xen-devel@xxxxxxxxxxxxxxxxxxx
>> Subject: [Xen-devel] Anyone succeeds HVM on latest x86-64 xen
>> 
>> I tried latest xen and linux-xen staging tree, but failed to run HVM
>> domain on x86-64 environment. domU creation is OK.
>> 
>> However the weird thing is not HVM domain itself. Instead system
>> crashed on dom0 context. I saw once with some stack dump that
>> xen's page fault handler is executed on a dom0's stack which then
>> causes nested page fault due to unable to fetch vcpu pointer. But
>> I'm curious why stack switch doesn't happen?
>> 
>> Does anybody else observe same failure? I'm still debugging it and
>> send out early in case it's my environment issue.
>> 
>> Thanks,
>> Kevin
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel 
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel 
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel