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

[Xen-devel] Re: Fwd: Display/Console for HVM domUs

To: aball@xxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: Fwd: Display/Console for HVM domUs
From: Anthony Liguori <aliguori@xxxxxxxxxx>
Date: Thu, 16 Nov 2006 12:58:02 -0600
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 16 Nov 2006 10:58:30 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1163693799.24087.30.camel@localhost>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20061115005241.54029.qmail@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <20061115010528.GE21142@xxxxxxxxxx> <1163693799.24087.30.camel@localhost>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.7 (X11/20060918)
Andrew D. Ball wrote:
Is anyone considering FreeNX in addition to VNC?

FreeNX isn't a framebuffer based protocol. It is a window based protocol. There's not enough information at the QEMU level to do a window based protocol. Perhaps if we had a paravirtual display driver...

Regards,

Anthony Liguori

Peace.
Andrew

On Wed, 2006-11-15 at 01:05 +0000, Daniel P. Berrange wrote:
On Tue, Nov 14, 2006 at 04:52:41PM -0800, jdsw wrote:
Forwarding to dev list.
/Jd

jdsw <jdsw2002@xxxxxxxxx> wrote: Date: Thu, 9 Nov 2006 18:37:07 -0800 (PST)
From: jdsw <jdsw2002@xxxxxxxxx>
Subject: Display/Console for  HVM domUs
To: XenUsers <xen-users@xxxxxxxxxxxxxxxxxxx>

Hi I have couple of questions on displays under HVM 1. When I kill window of DomU with sdl=1, the dom also dies... Is this a bug ? or expected behaviour. (quite annoying)
Its expected - whether its desirable is a completely different matter. I 
question
the usefullness of SDL at all because of its dependance on having a connection 
to
the X server available form the shell in which you launch the guest. I can't
imagine how this will ever work once XenD has support for managing inactive 
domains
and stopping/starting them via the XML-RPC interface - since you'll not even 
have
the SSH forwarded display anymore.

2. How do I determine the display number for DomUs running with vnc ? For me, the vnc display numbers are determined by the order in which the domUs were started. This is highly inconveniernt. I tried the vncdisplay=5 in the domu config file but it does not help.
If you specify 'vncunused=1' in the config file it will allocate the first 
unused
port number counting from 5900. If you want to specify an explicit display then
set 'vncdisplay=5' and 'vncunused=0'.

   Also, xm list -l domname also does not contain any indication of what display
 is being used ? I want to programatically determined the display number.
The info on what port is being listened on is not exposed by either xm or XenD.
Instead it is hidden away in xenstore.

  # xenstore-ls /local/domain/1 | grep vnc
     vnc-port = "5902"

If you have libvirt installed, then it is also available when using virsh
command to view an XML dump of a domain, eg

 # virsh dumpxml demovm | grep graphics
    <graphics type='vnc' port='5902'/>


Regards,
Dan.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel