WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] qemu-xen-3.4-testing: Fix read-only image file h

To: Michal Novotny <minovotn@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] qemu-xen-3.4-testing: Fix read-only image file handling
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Mon, 07 Jun 2010 11:24:29 -0700
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Mon, 07 Jun 2010 11:25:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C0CEF78.3000703@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C83298E6.16E28%keir.fraser@xxxxxxxxxxxxx> <4C0CEF78.3000703@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-2.fc12 Lightning/1.0b2pre Thunderbird/3.0.4
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"<minovotn@xxxxxxxxxx>  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

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>