From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Stekloff Subject: Re: [PATCH][XM-TEST] Add mounting /sys to ramdisk Date: Tue, 14 Mar 2006 09:10:40 -0800 Message-ID: <1142356241.7001.16.camel@localhost.localdomain> References: <1142296948.16893.46.camel@w-stekloff.beaverton.ibm.com> <1142305832.3172.27.camel@dyn9047022067.beaverton.ibm.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1142305832.3172.27.camel@dyn9047022067.beaverton.ibm.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: marvel@us.ibm.com Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On Mon, 2006-03-13 at 19:10 -0800, Woody Marvel wrote: > Dan > > Is that the only check you can used is 2.6 from uname? Is there any > other piece of info you can check? Hi Woody, Yeah... sysfs is compiled into the 2.6 domU kernel, which we are assuming is the kernel for the ramdisk. The HVM disk.img, which goes and finds its own non-xen kernel, could be an issue - if the kernel it finds doesn't compile in sysfs - such as an embedded kernel. I'm not sure this really is an issue, however. Even if it shouldn't find sysfs to mount, the image will still boot and still be able to run tests. Is that ok? Thanks, Dan