From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Fwd: Display/Console for HVM domUs Date: Thu, 16 Nov 2006 12:58:02 -0600 Message-ID: <455CB4BA.9040609@us.ibm.com> References: <20061115005241.54029.qmail@web35801.mail.mud.yahoo.com> <20061115010528.GE21142@redhat.com> <1163693799.24087.30.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1163693799.24087.30.camel@localhost> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: aball@linux.vnet.ibm.com Cc: xen-devel List-Id: xen-devel@lists.xenproject.org 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 wrote: Date: Thu, 9 Nov 2006 18:37:07 -0800 (PST) >>> From: jdsw >>> Subject: Display/Console for HVM domUs >>> To: XenUsers >>> >>> 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 >> >> >> >> Regards, >> Dan.