From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Novotny Subject: Re: [PATCH] qemu-xen-3.4-testing: Fix read-only image file handling Date: Mon, 07 Jun 2010 18:37:41 +0200 Message-ID: <4C0D2055.10204@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 06/07/2010 06:34 PM, Keir Fraser wrote: > On 07/06/2010 17:27, "Michal Novotny" wrote: > > >>> Try xm mem-set 0 2048 before the start and see if that makes it work. >>> >>> >> Well, now it changed to: >> >> # xenstored >> FATAL: Failed to initialize dom0 state: Invalid argument >> >> what does it mean and how to fix it? >> > 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. Michal > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > -- Michal Novotny, RHCE Virtualization Team (xen userspace), Red Hat