From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Areca RAID with Xen 3.4 and Linux 2.6.32 dom0 Date: Fri, 07 May 2010 11:25:44 -0700 Message-ID: <4BE45B28.1080905@goop.org> References: <20100506152537.758074dc@auedv3.syscomp.de> <4BE3054D.8070500@goop.org> <20100507105434.0e2d0ff3@auedv3.syscomp.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20100507105434.0e2d0ff3@auedv3.syscomp.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Florian Wagner Cc: xen-devel@lists.xensource.com, Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On 05/07/2010 01:54 AM, Florian Wagner wrote: > Using 3.4.3-rc (http://xenbits.xensource.com/xen-3.4-testing.hg) > vanilla the system boots. > Good. > Seems to me that the Debian kernel I'm trying requires the IOAPC stuff > (and thus hypervisor >=3.4.3) that is mentioned on XenParavirtOps in > the wiki. Sadly package dependencies on the kernel were not set up to > require the hypervisor from unstable (which would have been 3.4.3-rc3). > OK, that makes sense. Legacy interrupts (<16) will be automatically set up, and that would be enough to get the system into a semi-working state, but beyond that setup would fail and devices requiring them would not work. It would probably be a good idea to put a nice big clear warning message up to alert people to the problem... J