From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: guests started with xl create -V have no monitoring process Date: Fri, 27 Sep 2013 14:53:06 +0200 Message-ID: <20130927125306.GA4048@aepfle.de> References: <20130927091047.GA1800@aepfle.de> <1380277061.29483.179.camel@kazak.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1380277061.29483.179.camel@kazak.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Fri, Sep 27, Ian Campbell wrote: > On Fri, 2013-09-27 at 11:10 +0200, Olaf Hering wrote: > > The following command leaves no xl monitoring process for the domU. The > > result is that shutdown for this guest is not working properly, there is > > always a stale domid left behind: > > > > xl -v create -V -d -f some.cfg < /dev/null & > > > > Removing the -V option is a workaround. This happens with 4.3 and is not > > fixed in master. > > The placement of > if (dom_info->vnc) > vncviewer(domid, vncautopass); > seems pretty bogus, given that function exec()s without forking! > > Does this help? Build tested only. Yes, that works. Thanks. Olaf