OpenSolaris

Printable Version Enter a New Search
Bug ID 6718906
Synopsis xVM console should be more verbose
State 10-Fix Delivered (Fix available in build)
Category:Subcategory xvm:utility
Keywords
Responsible Engineer John Levon
Reported Against snv_89
Duplicate Of
Introduced In
Commit to Fix snv_94
Fixed In snv_94
Release Fixed solaris_nevada(snv_94)
Related Bugs 6718462
Submit Date 25-June-2008
Last Update Date 18-July-2008
Description
The xVM console does not provide any confirmation when it connects to a domain, disconnects or what the escape sequence is. This can lead to confusion of which domain you are connected to.

eg.

Starting in dom0, connecting to a domain that's logged in as root already, and disconnecting again :

# 
# uname -a
SunOS muncie 5.11 snv_89 i86pc i386 i86xpv
# virsh list
 Id Name                 State
----------------------------------
  0 Domain-0             running
  3 indy1-bld-x          blocked

# virsh console indy1-bld-x
# 						     <--- Silently connected to the domU
# 
# uname -a
SunOS indy1-bld-x 5.11 snv_86 i86pc i386 i86xpv
# 
# 
# 					             <--- CTRL-] here
# 
# 
# uname -a
SunOS muncie 5.11 snv_89 i86pc i386 i86xpv
# 
# 


Compare this is a telnet session :

2 stomper-> telnet muncie
Trying 129.156.186.129...
Connected to muncie.
Escape character is '^]'.
login: xxxx
Password: 
rm: /tmp/history.pts/1: No such file or directory
1 muncie-> 
telnet> q
Connection to muncie closed.
3 stomper-> 

Ignoring the user login, we get a message for the connect and disconnect, and a notice of what the escape sequence is. There should be no confusion of which system is currently connected.
People are likely to be scripting around the current virsh console,
so we can't change anything by default. Instead, add a --verbose option:

# /virt-console -v domu-220
Connected to domain domu-220
Escape character is '^]'
...
Domain  "domu-220" has shutdown.
Connection to domain domu-220 closed.
Work Around
N/A
Comments
N/A