Re: [Xen-users] Xen DomU Communication Problems [SOLVED for me]

Andrea Brugiolo
2008-10-01T12:43:33Z

On Mon, Sep 29, 2008 at 02:09:54PM +0200, Andrea Brugiolo
wrote:
> On Tue, Feb 19, 2008 at 11:56:35AM -0500, Sarah Scheibe wrote:
> > Thank you, that helped at least part of the problem.
> > I no longer get an error message when trying to create the domU, and
it
> > appears that the device is getting passed in. However, dmesg on the
domU
> > gives me
> >
> > "PCI: Enabling device 0000:00:00.0 (0000 -> 0003)
> > scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
> >         <Adaptec 29160 Ultra160 SCSI adapter>
> >         aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
> >
> > Unable to handle kernel NULL pointer dereference at 0000000000000078
RIP:
> >  [<ffffffff880043a2>]
:scsi_mod:scsi_calculate_bounce_limit+0x15/0x49
> > PGD 20750067 PUD 20751067 PMD 0
> > Oops: 0000 [1] SMP
> > CPU 0
> > Modules linked in: aic7xxx scsi_transport_spi scsi_mod
> > Pid: 510, comm: modprobe Not tainted 2.6.18-6-xen-amd64 #1
> > RIP: e030:[<ffffffff880043a2>]  [<ffffffff880043a2>]
> > :scsi_mod:scsi_calculate_bounce_limit+0x15/0x49"
> >
> > .... followed by a call trace, etc. The device does not show up in
/dev.
> >
> > I will keep at it
>
> Hi all
>
> I have exactly the same problem with the same kernel; dom0 is Debian
> etch and domU is Debian lenny.

FYI: the Debian kernel staff wrote a simple patch that seems to fix
the problem: I downloaded the current linux-source-2.6.18 snapshot
(2.6.18.dfsg.1-23~snapshot.12203) from
http://kernel-archive.buildserver.net/debian-kernel, built it and now
it works.

References at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=445987

Bye,

Andrea

--
Andrea Brugiolo                          andrea.brugiolo@unipd.it
Universita` degli Studi di Padova        http://www.unipd.it
Centro di Ateneo per le Biblioteche      http://www.cab.unipd.it
tel +39-049-827-3688                     fax +39-049-827-3651