Florian Wagner
2010-May-06 13:25 UTC
[Xen-devel] Areca RAID with Xen 3.4 and Linux 2.6.32 dom0
Hello, I''m trying to boot Xen 3.4.1 with a Linux 2.6.32-12 with dom0 support from Debian unstable (linux-image-2.6.32-12-xen-amd64). The result is a system unable to find its root filesystem on an Areaca ARC-1120 RAID controller because of some SCSI issues. I''ve attach the Xen and Linux boot messages. Booting the very same kernel without a the Xen hypervisor works with no problems. Another system with a LSI MegaRAID SCSI 320-2 shows the same behaviour but with different error messages. If helpful I could provide captured boot messages for this system, too. Any idea if this is a hypervisor or a kernel problem? Regards Florian Wagner -------------- Florian Wagner Abteilung EDV Telefon: 0821 / 4201 - 453 Fax: 0821 / 4201 - 411 E-Mail: f_wagner@syscomp.de Syscomp Biochemische Dienstleistungen GmbH August-Wessels-Straße 5, 86154 Augsburg Postfach 102506, 86015 Augsburg Telefon: 0821 / 4201 - 0 Fax: 0821 / 417992 Web: http://www.syscomp.de E-Mail: syscomp@syscomp.de Geschäftsführer: Dr. med. Bernd Schottdorf Gabriele Schottdorf Registergericht Augsburg HRB 8670 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2010-May-06 18:07 UTC
Re: [Xen-devel] Areca RAID with Xen 3.4 and Linux 2.6.32 dom0
On 05/06/2010 06:25 AM, Florian Wagner wrote:> I''m trying to boot Xen 3.4.1 with a Linux 2.6.32-12 with dom0 support > from Debian unstable (linux-image-2.6.32-12-xen-amd64).I''m not exactly sure what kernel version this is. Have you tried a xen.git 2.6.32.12 kernel?> The result is > a system unable to find its root filesystem on an Areaca ARC-1120 RAID > controller because of some SCSI issues. I''ve attach the Xen and Linux > boot messages. > > Booting the very same kernel without a the Xen hypervisor works with no > problems. >OK, that''s good to know.> Another system with a LSI MegaRAID SCSI 320-2 shows the same behaviour > but with different error messages. If helpful I could provide captured > boot messages for this system, too. >Yes please.> Any idea if this is a hypervisor or a kernel problem? >It looks like the kernel is having some problem mapping the device into its address space, but it isn''t clear where the problem lies. Things to try: 1. boot with dom0 with <4G and <2G RAM and see if that changes the behaviour (dom0_mem= on the Xen command line) 2. boot Xen with iommu=off (though I''m not sure it gets used on AMD systems?) 3. try a newer version of Xen (3.4.2, 3.4.3-rc or 4.0.0) 4. try a current xen.git xen/stable-2.6.32.x kernel Thanks, J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Florian Wagner
2010-May-07 08:54 UTC
Re: [Xen-devel] Areca RAID with Xen 3.4 and Linux 2.6.32 dom0
> On 05/06/2010 06:25 AM, Florian Wagner wrote: > > I''m trying to boot Xen 3.4.1 with a Linux 2.6.32-12 with dom0 > > support from Debian unstable (linux-image-2.6.32-12-xen-amd64). > > I''m not exactly sure what kernel version this is. Have you tried a > xen.git 2.6.32.12 kernel?As I understand it, it''s pv_ops dom0 support backported to Debians 2.6.32 kernel. It intends to replace the old 2.6.26 from lenny which uses forward ports of the Xen patches against 2.6.18.> It looks like the kernel is having some problem mapping the device > into its address space, but it isn''t clear where the problem lies. > > Things to try: > > [...] > > 3. try a newer version of Xen (3.4.2, 3.4.3-rc or 4.0.0)Sorry typo in my first mail. The version I''m using is 3.4.2 (from Debian testing, extended with one of the patches from 3.4.3 to make it work with Grub2 on i386). Using 3.4.3-rc (http://xenbits.xensource.com/xen-3.4-testing.hg) vanilla the system boots. 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). Regards Florian Wagner -------------- Florian Wagner Abteilung EDV Telefon: 0821 / 4201 - 453 Fax: 0821 / 4201 - 411 E-Mail: f_wagner@syscomp.de Syscomp Biochemische Dienstleistungen GmbH August-Wessels-Straße 5, 86154 Augsburg Postfach 102506, 86015 Augsburg Telefon: 0821 / 4201 - 0 Fax: 0821 / 417992 Web: http://www.syscomp.de E-Mail: syscomp@syscomp.de Geschäftsführer: Dr. med. Bernd Schottdorf Gabriele Schottdorf Registergericht Augsburg HRB 8670 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2010-May-07 18:25 UTC
Re: [Xen-devel] Areca RAID with Xen 3.4 and Linux 2.6.32 dom0
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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel