[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: "Anthony Liguori" <aliguori@xxxxxxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Thu, 15 Sep 2005 22:23:00 +0800
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 15 Sep 2005 14:20:50 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcW5/ej+I6gZvWUmQnO6vwGPzZnEhAAAoV5Q
  • Thread-topic: [Xen-devel] A weird behavior of xenconsole on XEN/IA64

>From: Anthony Liguori [mailto:aliguori@xxxxxxxxxx]
>>
>>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?

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.

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@xxxxxxxxxxxxxxxxxxx
>>http://lists.xensource.com/xen-devel
>>
>>
>>


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.