|
|
|
|
|
|
|
|
|
|
xen-bugs
[Xen-bugs] [Bug 204] New: too much output kills xenconsoled
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=204
Summary: too much output kills xenconsoled
Product: Xen
Version: unstable
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Tools
AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
ReportedBy: pl@xxxxxxxxxx
CC: hohnbaum@xxxxxxxxxx
To reproduce this, xm console into a domain. I've found two very quick and easy
methods to exhibit the behaviour.
1. telnet <somewhere> chargen
--or--
2. yes
"AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA"
Either one of these will dump you out of the console within seconds. If you try
to reattach, you see:
xenconsole: Could not open tty `/dev/pts/1': No such file or directory
xenconsoled no longer shows up in the process list on dom0, and silently fails
if you try to restart it. However, if you do a xm shutdown -a, wait for the
guest to shut down, and *then* try to bring xenconsoled back up, it comes up
fine.
--
Configure bugmail:
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-bugs] [Bug 204] New: too much output kills xenconsoled,
bugzilla-daemon <=
|
|
|
|
|