WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] telnet xend

The machine now locks up while spitting out the error message below when
the non-privileged domain is initially *started*.

Let me know what information you need.

                                -Kip

On Fri, 14 May 2004, Kip Macy wrote:

>
> That works great.
>
> I just did a shutdown -r now in the non-privileged domain and now I'm
> seeing an endless stream of the messages below. DOM0 is now
> unresponsive. Any suggestions?
>
> Thanks for your help.
>
>
> KERNEL: assertion (flags&MSG_PEEK) failed at tcp.c(1540)
> KERNEL: assertion (skb==NULL || before(tp->copied_seq,
> TCP_SKB_CB(skb)->end_seq)) failed at tcp.c(1290)
> KERNEL: assertion (tp->copied_seq == tp->rcv_nxt ||
> (flags&(MSG_PEEK|MSG_TRUNC))) failed at tcp.c(1603)
> KERNEL: assertion (flags&MSG_PEEK) failed at tcp.c(1540)
> KERNEL: assertion (skb==NULL || before(tp->copied_seq,
> TCP_SKB_CB(skb)->end_seq)) failed at tcp.c(1290)
> KERNEL: assertion (tp->copied_seq == tp->rcv_nxt ||
> (flags&(MSG_PEEK|MSG_TRUNC))) failed at tcp.c(1603)
> KERNEL: assertion (flags&MSG_PEEK) failed at tcp.c(1540)
> KERNEL: assertion (skb==NULL || before(tp->copied_seq,
> TCP_SKB_CB(skb)->end_seq)) failed at tcp.c(1290)
> KERNEL: assertion (tp->copied_seq == tp->rcv_nxt ||
> (flags&(MSG_PEEK|MSG_TRUNC))) failed at tcp.c(1603)
> KERNEL: assertion (flags&MSG_PEEK) failed at tcp.c(1540)
> KERNEL: assertion (skb==NULL || before(tp->copied_seq,
> TCP_SKB_CB(skb)->end_seq)) failed at tcp.c(1290)
> KERNEL: assertion (tp->copied_seq == tp->rcv_nxt ||
> (flags&(MSG_PEEK|MSG_TRUNC))) failed at tcp.c(1603)
> KERNEL: assertion (flags&MSG_PEEK) failed at tcp.c(1540)
>
>
> On Fri, 14 May 2004, Ian Pratt wrote:
>
> > > Please remind me what the proper way is to interact with non-privileged
> > > consoles. Without any telnet negotation no control characters get
> > > transmitted and there is no notion of what type of terminal the client
> > > is running.
> >
> > "xencons <machine> <port>" is what we use. Any raw terminal
> > program should work.
> >
> > xend should probably have support to spot a telnet client and do
> > the necessary negotiation to put the client into raw character
> > mode.
> >
> > Ian
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: SourceForge.net Broadband
> > Sign-up now for SourceForge Broadband and get the fastest
> > 6.0/768 connection for only $19.95/mo for the first 3 months!
> > http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxxxx
> > https://lists.sourceforge.net/lists/listinfo/xen-devel
> >
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: SourceForge.net Broadband
> Sign-up now for SourceForge Broadband and get the fastest
> 6.0/768 connection for only $19.95/mo for the first 3 months!
> http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>


-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel