From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: A weird behavior of xenconsole on XEN/IA64 Date: Thu, 15 Sep 2005 09:00:41 -0500 Message-ID: <43297E89.80208@us.ibm.com> References: <571ACEFD467F7749BC50E0A98C17CDD802C0685A@pdsmsx403> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <571ACEFD467F7749BC50E0A98C17CDD802C0685A@pdsmsx403> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Tian, Kevin" Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Tian, Kevin wrote: >I saw a weird behavior related to xenconsole, when I'm working on domU >support on XEN/IA64: > >After following sequence: ># lomount -t ext2 -diskimage /root/xenia64.img -partition2 /mnt ># xend start ># xm create -c > >I can see domU boot messages flushed out immediately, but quiet at about >ACPI initialization. Then I have to do: > ># Ctrl + ] ># xm console 1 ># Ctrl + ] ># xm console 1 ># Ctrl + ] ># xm console 1 > > I'm not sure I fully understand, you're hitting Ctrl + ] and it's not taking you out of the console? 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 > > >