All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
Subject: Re: [PATCH] Make Xend use consoled and xc_console
Date: Wed, 03 Aug 2005 17:04:31 -0500	[thread overview]
Message-ID: <42F13F6F.4060502@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D28292E@liverpoolst.ad.cl.cam.ac.uk>

Ian Pratt wrote:

>>The attached patch removes all of the console handling code 
>>from Xend and changes xm to simply exec /usr/libexec/xen/xc_console.
>>    
>>
>
>Please can you provide some more detail, particularly how it changes
>things from a user point of view. How do you disconnect and reconnect to
>consoles? Does the '-c' option to xm still work? Can the user control
>allocation of are tty names?
>  
>
xm console still connects and disconnects to the console.

xm create -c still works as expected.

You still disconnect from the console with C-].  The only user facing 
difference is that xm list does not have a console field (the port it 
showed previously was meaningless anyway with domain sockets) and xm no 
longer supports the consoles command (since again, the information it 
was displaying wasn't all that useful).

If we export over tcp then we can add some info back into xm.  However, 
I'd much rather implement the NSS plugin we talked about at the Summit.

tty names are automatically chosen by the OS so there isn't really 
anything to control.

>Also, should consoled really line in /usr/sbin/ ?  I think it should be
>in /usr/lib/xen/bin
>  
>
I put it there since that's where we have xenstored installed.  We can 
certainly install it somewhere else though.

>(Didn't we decide /usr/libexec was deprecated anyhow?)
>  
>
If it is, I'll submit a patch to relocate the contents of /usr/libexec/xen.

>BTW: does this fix the console output corruption bug that's on the
>books?
>  
>
I've not been able to reproduce it.  I had 50 domains running all 
cat'ing /dev/urandom and I was able to input/output large amounts of 
data without corruption to another domain.

With that said though, I'm still not convinced it's fixed completely 
because I don't think xcs buffers everything correctly.  The new console 
drivers should do the trick though since we won't need to go through xcs.

Regards,

Anthony Liguori

>Thanks,
>Ian 
>
>
>  
>
>>I've done a pretty good amount of testing and this seems to 
>>clear up all of the Xend console issues in bugzilla.
>>
>>This is a pretty big change to Xend though with a lot of 
>>deleted code so I'd appreciate if people more familiar with 
>>the Xend codebase could look through it critically.
>>
>>In addition to the patch, the following files are no longer used:
>>
>>tools/python/xen/util/console_client.py
>>tools/python/xen/xend/XendConsole.py
>>tools/python/xen/xend/server/SrvConsole.py
>>tools/python/xen/xend/server/SrvConsoleDir.py
>>tools/python/xen/xend/server/console.py
>>
>>Regards,
>>
>>Anthony Liguori
>>
>>Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
>>
>>_______________________________________________
>>Xen-devel mailing list
>>Xen-devel@lists.xensource.com
>>http://lists.xensource.com/xen-devel
>>
>>    
>>
>
>  
>

  reply	other threads:[~2005-08-03 22:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-03 21:56 [PATCH] Make Xend use consoled and xc_console Ian Pratt
2005-08-03 22:04 ` Anthony Liguori [this message]
2005-08-04  0:31   ` Rusty Russell
2005-08-04 19:23 ` Anthony Liguori
2005-08-04 22:03   ` Robert Read
2005-08-04 22:08     ` Anthony Liguori
  -- strict thread matches above, loose matches on Subject: below --
2005-08-04 23:17 Ian Pratt
2005-08-03 22:22 Ian Pratt
2005-08-03 23:10 ` Anthony Liguori
2005-08-03 21:26 Anthony Liguori
2005-08-03 21:30 ` Anthony Liguori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42F13F6F.4060502@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=Christian.Limpach@cl.cam.ac.uk \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.