From: "Zhai, Edwin" Subject: Re: stubdom questions Date: Wed, 27 Feb 2008 10:05:13 +0800 Message-ID: <20080227020513.GJ8550@edwin-srv.sh.intel.com> References: <20080219113941.GF21201@edwin-srv.sh.intel.com> <20080225115635.GD4380@implementation.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Return-path: Content-Disposition: inline In-Reply-To: <20080225115635.GD4380@implementation.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Samuel Thibault , "Zhai, Edwin" , Keir , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Samuel, Thanks for your reply. On Mon, Feb 25, 2008 at 12:56:35PM +0100, Samuel Thibault wrote: > Hello, > > Zhai, Edwin, le Tue 19 Feb 2008 19:39:41 +0800, a écrit : > > I have a try with HVM stubdomain on r17062, but failed to make on 32b platform. > > Attached patch can fix it, but don't know if okay. > > That is how such issues have usually been solved so I guess in principle > it is. Is your code coming from freebsd too? Maybe. I copy this code from xen/common/lib.c > > > After installation, I failed to start stubdom. So I created it manually > > See the commented "xm create" line in the stubdom-dm script, to enable > debugging. > I have enabled this to pop up a xterm for debug, but got same result. > > 1. I use default vnclisten. Does it matter? > > Yes: > > > #---------------------------------------------------------------------------- > > # address that should be listened on for the VNC server if vnc is set. > > # default is to use 'vnc-listen' setting from /etc/xen/xend-config.sxp > > #vnclisten="localhost" > > So if your vnc-listen setting is e.g. localhost, the VNC server of the > stubdom will be restricted to the stub domain itself, and you won't be > able to connect. vnclisten = "172.30.206.1"" I still have issue with the IP addr. How to select it, the dom0 ip or whatever in the subnet? vif = [ 'ip=172.30.206.1', 'ip=10.0.1.1,mac=aa:00:00:12:23:34'] Does it mean the stubdom would create an extra vnif with the ip and start a VNC server on it? So I need ping 172.30.206.1 first to see if the vnif works? I saw "changeset 17122 -- minios: add PVFB support". Is it a must for stubdom vnc? > > > > 2. Seems qemu in stubdom has some issue and couldn't update the 'vnc-port' in > > xenstore. > > Actually mini-os has no name resolving support so that it won't be able > to understand the default "localhost" for vnclisten and hence not start > VNC. > > > Or the stubdom didn't run at all. > > It did: messages like > > ******************* BLKFRONT for /local/domain/45/device/vbd/5632 ********** > > come from Mini-OS and mean that qemu is currently connecting to the > block backend. > > > 3. "Create /etc/xen/stubdom-hvmconfig" in readme -- seems "hvmconfig" should > > match the domain name rather than config file. > > Oh indeed, here is a patch to fix that and other documentation/debugging > issues: > > -- best rgds, edwin