From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] qemu-xen-3.4-testing: Fix read-only image file handling Date: Mon, 7 Jun 2010 18:56:49 +0100 Message-ID: References: <4C0D2055.10204@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4C0D2055.10204@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" List-Id: xen-devel@lists.xenproject.org On 07/06/2010 17:37, "Michal Novotny" 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