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: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Mon, 7 Jun 2010 18:56:49 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 07 Jun 2010 10:57:58 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C0D2055.10204@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcsGaBfgCjxXtHPHRSSzKLZsul7h8wAArVdi
Thread-topic: [Xen-devel] [PATCH] qemu-xen-3.4-testing: Fix read-only image file handling
User-agent: Microsoft-Entourage/12.24.0.100205
On 07/06/2010 17:37, "Michal Novotny" <minovotn@xxxxxxxxxx> wrote:

>> Do files /proc/xen/xsd_kva and /proc/xen/xsd_port exist? If not you need to
>> configure and/or install the appropriate xenstore-related kernel module
>> (whatever that may be, in pv_ops land).
>> 
>>   -- Keir
>>    
> 
> Thanks but I checked it and they exist and it seems to be OK. Also, the
> strange thing is that even if I put modprobe to /etc/init.d/xend before
> start the module can't get probed and lsmod is showing only xenfs module
> but no xen_evtchn loaded. I need to modprobe it manually, run xenstored
> manually and then after starting xen daemon the error of dom0 state happens.

I suggest add some tracing to function dom0_init() in xenstored and see
where that function is failing. The two most obvious places were the opening
of those two files in /proc. If they exist then I'm not sure what else could
be going wrong.

Oh, you should be able to cat /proc/xen/ksd_port and get an integer value.
/proc/xen/ksd_kva by contrast gets mmap()ed by xenstored.

 -- Keir



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

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