RE: [Xen-devel] A weird behavior of xenconsole on XEN/IA64

["Tian, Kevin" <kevin.tian@xxxxxxxxx>]

Finally the root cause is confirmed from event channel injection mechanism 
broken under some corner case (Yes, IA64 specific). Once that condition is hit, 
no event is injected to dom0 any more even when some event bits are pending. 
This is why xenstored can't receive message from another domain.

Later when issuing "xm console 1" and "Ctrl + ]", change of connection status 
may cause xenstored to query store page actively and thus xenU can forward 
progress a bit. Later when new transaction is coming, I have to do same thing 
to trigger.

After fixing the evtchn part, now it works as desired and thanks for hints. ;-)

Thanks,
Kevin

>-----Original Message-----
>From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Tian, Kevin
>Sent: 2005年9月16日 9:21
>To: Anthony Liguori
>Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>Subject: RE: [Xen-devel] A weird behavior of xenconsole on XEN/IA64
>
>>From: Anthony Liguori [mailto:aliguori@xxxxxxxxxx]
>>>No, Ctrl+] can take me out of the console. What I mean is, when domU
>>>boots to place around ACPI init, there's no console output then. Then
>I
>>>started to log on/off the console several times. However the first two
>>>"xm console 1" got no output at all. Only the third "xm console 1" can
>>>make domU continue to boot and output. If without the third, domU also
>>>halt there and the xenconsole page also shows no updated content.
>>>
>>>
>>Ah, okay, sorry I'm still a bit groggy :-)
>>
>>Sounds like event channel notifications aren't happening.  Upon
>startup,
>>the console client will check the console ring.  Otherwise, it will
>just
>>wait for an event channel notification.
>>
>>If you're not seeing data unless you reconnect to the console, it's
>>likely because that notification isn't being triggered (for whatever
>>reason).
>>
>>Hope this helps,
>>
>>Anthony Liguori
>>
>
>Ha, that's the useful info I want to look into now. Thanks a lot.
>
>- 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