From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Collins Subject: Re: xen-unstable and pvops kernel Date: Mon, 04 Jan 2010 21:07:38 -0500 Message-ID: <1262657258.16610.21.camel@localhost> References: <499298627-1262650110-cardhu_decombobulator_blackberry.rim.net-1546771770-@bda261.bisx.prod.on.blackberry> <20100105001056.GA23087@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20100105001056.GA23087@phenom.dumpdata.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: Konrad Rzeszutek Wilk Cc: xen-devel@lists.xensource.com, mdlabriola@yahoo.com, xen-devel-bounces@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Ok, got it working with using the below setting. Now I can boot into pvops kernel dom0. Of course, I'm now getting the dreaded xenfs busy or already mounted error and am getting a no such device back from /dev/rtc. Seems like CentOS is just too old for all the new fangled things in this kernel. I will research this tomorrow night and maybe look into grabbing a newer OS in the meantime. Mike On Mon, 2010-01-04 at 19:10 -0500, Konrad Rzeszutek Wilk wrote: > On Tue, Jan 05, 2010 at 12:06:39AM +0000, mdlabriola@yahoo.com wrote: > > Sorry for the top-post... > > > > I had a similar problem on FC5 that was because of some deprecated sysfs stuff. There's a compatibility setting for those of us with really old userland tools (like LVM)... Don't remember the exact name of it off hand. I'll look it up when I get to work tomorrow. > > CONFIG_SYSFS_DEPRECATED=y