From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: xl create PV guest with qcow/qcow2 disk images fail Date: Fri, 04 Nov 2011 11:45:31 +0000 Message-ID: <4EB3D05B.3090503@cantab.net> References: <1319808450-9617-1-git-send-email-cyliu@suse.com> <4EB184DE020000660000603E@novprvlin0050.provo.novell.com> <1320238770.3084.51.camel@cthulhu.hellion.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= Cc: "xen-devel@lists.xensource.com" , Stefano Stabellini , Chunyan Liu , Ian Campbell List-Id: xen-devel@lists.xenproject.org On 04/11/11 09:14, Roger Pau Monné wrote: > 2011/11/4 Chunyan Liu : >>> This needs to be libxl_fork, I think. Perhaps even this whole thing >>> should be libxl__spawn_spawn (not sure about that)? >> >> I noticed that in libxl, some places use fork() and other places use >> libxl_fork(), device-model uses libxl__spawn_spwan. As for this place, I am >> not clear if fork() + execvp() might cause some problem? Or it is just >> considered better to use libxl_fork or libxl__spawn_spwan? vfork() no longer exists in the POSIX.1-2008 standard so you probably should not use it. David