Re: A weird behavior of xenconsole on XEN/IA64

[Anthony Liguori <aliguori@us.ibm.com>]

Tian, Kevin wrote:

>>I'm not sure I fully understand, you're hitting Ctrl + ] and it's not
>>taking you out of the console?
>>    
>>
>
>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

>Thanks,
>Kevin
>  
>
>>That code is in the client (tools/console/client/main.c) and hasn't
>>really changed.  Maybe Ctrl + ] generates a different scancode on your
>>system?
>>
>>Regards,
>>
>>Anthony Liguori
>>
>>    
>>
>>>Exactly at third "xm console 1", the subsequent messages continues to
>>>show. Seems like this is not delayed message because domU's progress
>>>seems also halt for same long period and then continue to boot.
>>>
>>>Definitely I don't want to confuse anybody here, and it's very likely
>>>      
>>>
>to
>  
>
>>>be an XEN/IA64 specific issue (out of sync for some time). I post it
>>>here just in case any guys familiar with this part can point me some
>>>possible clues about normal work flow of xenconsole, which then can
>>>      
>>>
>help
>  
>
>>>me to find root cause. ;-)
>>>
>>>Actually some time later, wait_for_blkif in blkfront also warns
>>>      
>>>
>"timeout
>  
>
>>>to connect to device". Though there may be other reasons for the
>>>connection, I'm also interested whether the reason for incontinuous
>>>console message also relates to this one.
>>>
>>>Is it possible from the lock of xenbus? One background is, xenstore
>>>      
>>>
>has
>  
>
>>>already been setup correctly, and I can see some transaction succeeded
>>>on that page.
>>>
>>>Appreciate your comments.
>>>
>>>Thanks,
>>>Kevin
>>>
>>>_______________________________________________
>>>Xen-devel mailing list
>>>Xen-devel@lists.xensource.com
>>>http://lists.xensource.com/xen-devel
>>>
>>>
>>>
>>>      
>>>
>
>
>  
>