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

Re: [Xen-API] XCP 1.6 xenconsole freezes


  • To: xen-api@xxxxxxxxxxxxx
  • From: George Shuklin <george.shuklin@xxxxxxxxx>
  • Date: Mon, 03 Dec 2012 07:29:19 +0400
  • Delivery-date: Mon, 03 Dec 2012 03:29:36 +0000
  • List-id: User and development list for XCP and XAPI <xen-api.lists.xen.org>

Yep, I do _KNOW_ this. Mostly because we running alternative version of console for our customers, which is websocket web2.0 based, not the ugly Java-VNC applet.

Anyway, here the story:

When PV VM starts, xenconsoled creates a unix-98 pseudo-terminal: /dev/pts/X for VM console.
If someone use xenconsole, or xl console (same thing) or use it own application for VM console access it simply open /dev/pts/num and operates.

Oder version of XCP have only one way to access Vm consoles - via VNC. It was specific service (vncterm) wich open /dev/pts/X and listen on localhost to provide consoles via VNC. xapi wrap it to http/ssl and allows to connect to console with known key. Xapi had a special (undocumented) key for vm: other-config:disable_pv_vnc=true, which simply says xapi 'hands of' from /dev/pts.

New version of XCP (1.6) now provides VT100 (actually, simple byte stream) connection to VM and ignores key 'disable_pv_vnc'. If two or more listeners are connected to same /dev/pts/X, some bytes streamed to one reader, some to other... Mess and pure chaos.

Morale:
1) Use xe console vm=vm_name to get local access to PV console.
OR
2) Connect to VNC to specified port (xenstore-read /local/domain/DOMID/console/tc-port)

We decided to go second way. If you just want to see vm console on console (lol), use xe console.


02.12.2012 12:26, Grant McWilliams пишет:
Our team has noticed that the /usr/lib/xen/binxenconsole has stopped working on all XCP 1.6 systems (including final). We initially thought it was a problem with running XCP inside of VirtualBox which we do on occasion. Upon moving our physical hosts to XCP 1.6 we also noticed that it's happening consistently on real XCP 1.6 hosts as well. Using the XCP VM install tutorials I wrote here results in a hung terminal. During the kickstart/preseed installs the console does output garbled data so you can tell when the install is over but it's not legible enough to interact with the installer. Once the VM has rebooted and you try to log in the console just hangs. Sometimes after about 5-10 minutes it will show the login prompt but then be unresponsive. These tutorials work for XCP 1.0 to 1.5b. 

Anyone have any idea why? 


Grant McWilliams
Xenapi Admin Documentation Project

_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

 


Rackspace

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