From: "Andrew D. Ball" <aball@linux.vnet.ibm.com>
To: "Daniel P. Berrange" <berrange@redhat.com>,
xen-devel@lists.xensource.com
Subject: Re: Fwd: Display/Console for HVM domUs
Date: Thu, 16 Nov 2006 11:16:38 -0500 [thread overview]
Message-ID: <1163693799.24087.30.camel@localhost> (raw)
In-Reply-To: <20061115010528.GE21142@redhat.com>
Is anyone considering FreeNX in addition to VNC?
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@yahoo.com> wrote: Date: Thu, 9 Nov 2006 18:37:07 -0800 (PST)
> > From: jdsw <jdsw2002@yahoo.com>
> > Subject: Display/Console for HVM domUs
> > To: XenUsers <xen-users@lists.xensource.com>
> >
> > 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.
next prev parent reply other threads:[~2006-11-16 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 0:52 Fwd: Display/Console for HVM domUs jdsw
2006-11-15 1:05 ` Daniel P. Berrange
2006-11-15 2:07 ` jdsw
2006-11-16 16:16 ` Andrew D. Ball [this message]
2006-11-16 18:58 ` Anthony Liguori
2006-11-15 9:54 ` Ewan Mellor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1163693799.24087.30.camel@localhost \
--to=aball@linux.vnet.ibm.com \
--cc=berrange@redhat.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.