From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [PATCH] qemu-xen-3.4-testing: Fix read-only image file handling Date: Mon, 07 Jun 2010 11:24:29 -0700 Message-ID: <4C0D395D.6040601@goop.org> References: <4C0CEF78.3000703@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4C0CEF78.3000703@redhat.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: Michal Novotny Cc: "xen-devel@lists.xensource.com" , Keir Fraser List-Id: xen-devel@lists.xenproject.org On 06/07/2010 06:09 AM, Michal Novotny wrote: > On 06/07/2010 01:39 PM, Keir Fraser wrote: >> On 07/06/2010 12:21, "Michal Novotny" wrote: >> >> >>> "/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xsutil.py", line >>> 18, in xshandle >>> xs_handle = xen.lowlevel.xs.xs() >>> Error: (111, 'Connection refused') >>> >>> Any guess what may be going wrong? >>> >> Xenstored not running, or refusing connections for some other reason? >> >> -- Keir >> >> >> > Not running and refusing to run: FATAL: Failed to open evtchn device: > No such file or directory Make sure /dev/xen/evtchn exists. If you're running current libxc, it will not longer automatically create it, but rely on your distro mechanisms (typically udev) to create it for you. It should be: $ ls -l /dev/xen [...] crw-r-----. 1 root root 10, 61 2010-06-05 16:50 eventchn crw-rw----. 1 root root 10, 61 2010-06-05 16:49 evtchn crw-------. 1 root root 10, 60 2010-06-07 11:17 gntdev (not sure why there's the duplicate evtchn devices) If you're running an older libxc and a new pvops dom0, then it will get it wrong and destroy your existing good devices and replace them with junk. I should probably make sure the device name fix goes into .31 kernel as well. J