From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fantu Subject: Re: xen-unstable: Qemu upstream domUs not start on Wheezy Date: Tue, 6 Mar 2012 05:51:16 -0800 (PST) Message-ID: <1331041876758-5540860.post@n5.nabble.com> References: <1329924493728-5505409.post@n5.nabble.com> <1329986957327-5507375.post@n5.nabble.com> <1329987508.8557.23.camel@zakaz.uk.xensource.com> <1329987975739-5507438.post@n5.nabble.com> <1330080608338-5512352.post@n5.nabble.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Stefano Stabellini-3 wrote > > On Fri, 24 Feb 2012, Fantu wrote: >> Does Xen and all of its parts (include qemu upstream) has debug on >> build-time >> enabled by default or must be enabled? > > Yes, they are enabled by default. > Unfortunately from the log you posted in the previous email I am not > sure what could cause QEMU to fail opening the unix socket in > /var/run/xen. > Problem found, /var/run/xen is erased at every reboot, probably by Wheezy. -- View this message in context: http://xen.1045712.n5.nabble.com/xen-unstable-Qemu-upstream-domUs-not-start-on-Wheezy-tp5505409p5540860.html Sent from the Xen - Dev mailing list archive at Nabble.com.