[ DELL PE2850 ] - support for LSI Logic 53c1030 ?

Hi,

having a DELL PowerEdge 2850 lying in a cupboard, I decided to try
NetBSD/xen on it. Installation of 3.0/i386 worked OK. I followed Xen
HOWTO and it seems the Xen kernel don't access the disk - it doesn't
find the root automatically, don't want to use 'sd0a' as I tell him and
sd0 don't appear in the 'root device' choices.

From /i386, the hardware is :
mpt0 at pci2 dev 5 function 0: LSI Logic 53c1030 Ultra320 SCSI
mpt0: interrupting at ioapic1 pin 2 (irq 7)
scsibus0 at mpt0: 16 targets, 8 luns per target
mpt1 at pci2 dev 5 function 1: LSI Logic 53c1030 Ultra320 SCSI
mpt1: interrupting at ioapic1 pin 1 (irq 3)
scsibus1 at mpt1: 16 targets, 8 luns per target
scsibus0: waiting 2 seconds for devices to settle...
scsibus1: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 0 lun 0: <SEAGATE, ST3146807LC, DS09> disk fixed
sd1 at scsibus0 target 1 lun 0: <SEAGATE, ST3146807LC, DS09> disk fixed
sd2 at scsibus0 target 2 lun 0: <SEAGATE, ST3146807LC, DS09> disk fixed
ses0 at scsibus0 target 6 lun 0: <PE/PV, 1x6 SCSI BP, 1.0> processor
fixed

My menu.lst is :
title NetBSD/xen
        root    (hd0,0)
        kernel  (hd0,0,a)/xen.gz dom0_mem=65536
        module  (hd0,0,a)/netbsd console=tty0

Grub and Xen are installed from pkgsrc-2005Q4.

Re: [ DELL PE2850 ] - support for LSI Logic 53c1030 ?

On Tue, Jan 03, 2006 at 03:12:15PM +0100, Joel CARNAT wrote:
> Hi,
> 
> having a DELL PowerEdge 2850 lying in a cupboard, I decided to try
> NetBSD/xen on it. Installation of 3.0/i386 worked OK. I followed Xen
> HOWTO and it seems the Xen kernel don't access the disk - it doesn't
> find the root automatically, don't want to use 'sd0a' as I tell him and
> sd0 don't appear in the 'root device' choices.
> 
> From /i386, the hardware is :
> mpt0 at pci2 dev 5 function 0: LSI Logic 53c1030 Ultra320 SCSI
> mpt0: interrupting at ioapic1 pin 2 (irq 7)
> scsibus0 at mpt0: 16 targets, 8 luns per target
> mpt1 at pci2 dev 5 function 1: LSI Logic 53c1030 Ultra320 SCSI
> mpt1: interrupting at ioapic1 pin 1 (irq 3)
> scsibus1 at mpt1: 16 targets, 8 luns per target
> scsibus0: waiting 2 seconds for devices to settle...
> scsibus1: waiting 2 seconds for devices to settle...
> sd0 at scsibus0 target 0 lun 0: <SEAGATE, ST3146807LC, DS09> disk fixed
> sd1 at scsibus0 target 1 lun 0: <SEAGATE, ST3146807LC, DS09> disk fixed
> sd2 at scsibus0 target 2 lun 0: <SEAGATE, ST3146807LC, DS09> disk fixed
> ses0 at scsibus0 target 6 lun 0: <PE/PV, 1x6 SCSI BP, 1.0> processor
> fixed
> 
> My menu.lst is :
> title NetBSD/xen
>         root    (hd0,0)
>         kernel  (hd0,0,a)/xen.gz dom0_mem=65536
>         module  (hd0,0,a)/netbsd console=tty0
> 

Re: Re: [ DELL PE2850 ] - support for LSI Logic 53c1030 ?

Dans l'épisode précédent (Tue, Jan 03 2006 - 15:26), Quentin Garnier nous apprenait que :
> On Tue, Jan 03, 2006 at 03:12:15PM +0100, Joel CARNAT wrote:
> > Hi,
> > 
> > having a DELL PowerEdge 2850 lying in a cupboard, I decided to try
> > NetBSD/xen on it. Installation of 3.0/i386 worked OK. I followed Xen
> > HOWTO and it seems the Xen kernel don't access the disk - it doesn't
> > find the root automatically, don't want to use 'sd0a' as I tell him and
> > sd0 don't appear in the 'root device' choices.
> > 
> > From /i386, the hardware is :
> > mpt0 at pci2 dev 5 function 0: LSI Logic 53c1030 Ultra320 SCSI
> > mpt0: interrupting at ioapic1 pin 2 (irq 7)
> > scsibus0 at mpt0: 16 targets, 8 luns per target
> > mpt1 at pci2 dev 5 function 1: LSI Logic 53c1030 Ultra320 SCSI
> > mpt1: interrupting at ioapic1 pin 1 (irq 3)
> > scsibus1 at mpt1: 16 targets, 8 luns per target
> > scsibus0: waiting 2 seconds for devices to settle...
> > scsibus1: waiting 2 seconds for devices to settle...
> > sd0 at scsibus0 target 0 lun 0: <SEAGATE, ST3146807LC, DS09> disk fixed
> > sd1 at scsibus0 target 1 lun 0: <SEAGATE, ST3146807LC, DS09> disk fixed
> > sd2 at scsibus0 target 2 lun 0: <SEAGATE, ST3146807LC, DS09> disk fixed
> > ses0 at scsibus0 target 6 lun 0: <PE/PV, 1x6 SCSI BP, 1.0> processor
> > fixed
> > 
> > My menu.lst is :
> > title NetBSD/xen
> >         root    (hd0,0)
> >         kernel  (hd0,0,a)/xen.gz dom0_mem=65536
> >         module  (hd0,0,a)/netbsd console=tty0

Re: Re: [ DELL PE2850 ] - support for LSI Logic 53c1030 ?

On Tue, Jan 03, 2006 at 03:29:48PM +0100, Joel CARNAT wrote:
> Dans l'épisode précédent (Tue, Jan 03 2006 - 15:26), Quentin Garnier nous apprenait que :
> > On Tue, Jan 03, 2006 at 03:12:15PM +0100, Joel CARNAT wrote:
> > > Hi,
> > > 
> > > having a DELL PowerEdge 2850 lying in a cupboard, I decided to try
> > > NetBSD/xen on it. Installation of 3.0/i386 worked OK. I followed Xen
> > > HOWTO and it seems the Xen kernel don't access the disk - it doesn't
> > > find the root automatically, don't want to use 'sd0a' as I tell him and
> > > sd0 don't appear in the 'root device' choices.
> > > 
> > > From /i386, the hardware is :
> > > mpt0 at pci2 dev 5 function 0: LSI Logic 53c1030 Ultra320 SCSI
> > > mpt0: interrupting at ioapic1 pin 2 (irq 7)
> > > scsibus0 at mpt0: 16 targets, 8 luns per target
> > > mpt1 at pci2 dev 5 function 1: LSI Logic 53c1030 Ultra320 SCSI
> > > mpt1: interrupting at ioapic1 pin 1 (irq 3)
> > > scsibus1 at mpt1: 16 targets, 8 luns per target
> > > scsibus0: waiting 2 seconds for devices to settle...
> > > scsibus1: waiting 2 seconds for devices to settle...
> > > sd0 at scsibus0 target 0 lun 0: <SEAGATE, ST3146807LC, DS09> disk fixed
> > > sd1 at scsibus0 target 1 lun 0: <SEAGATE, ST3146807LC, DS09> disk fixed
> > > sd2 at scsibus0 target 2 lun 0: <SEAGATE, ST3146807LC, DS09> disk fixed
> > > ses0 at scsibus0 target 6 lun 0: <PE/PV, 1x6 SCSI BP, 1.0> processor
> > > fixed
> > > 
> > > My menu.lst is :
> > > title NetBSD/xen
> > >         root    (hd0,0)
> > >         kernel  (hd0,0,a)/xen.gz dom0_mem=65536

Re: Re: Re: [ DELL PE2850 ] - support for LSI Logic 53c1030 ?

OK... works better now.
Just added :
ident           "PE2850-XEN0-$Revision: 1.0.0 $"
mpt*            at pci? dev ? function ?        # LSI Fusion SCSI/FC
scsibus*        at scsi?
scsibus*        at mpt?
sd*             at scsibus? target ? lun ?      # SCSI disk drives
ses*            at scsibus? target ? lun ?      # SCSI Enclosure
Services devices

to XEN0 config file and it's up :)
Looks like it's running OK now.
Sorry for the noise.
	Jo

Dans l'épisode précédent (Tue, Jan 03 2006 - 15:45), Quentin Garnier nous apprenait que :
> On Tue, Jan 03, 2006 at 03:29:48PM +0100, Joel CARNAT wrote:
> > Dans l'épisode précédent (Tue, Jan 03 2006 - 15:26), Quentin Garnier nous apprenait que :
> > > On Tue, Jan 03, 2006 at 03:12:15PM +0100, Joel CARNAT wrote:
> > > > Hi,
> > > > 
> > > > having a DELL PowerEdge 2850 lying in a cupboard, I decided to try
> > > > NetBSD/xen on it. Installation of 3.0/i386 worked OK. I followed Xen
> > > > HOWTO and it seems the Xen kernel don't access the disk - it doesn't
> > > > find the root automatically, don't want to use 'sd0a' as I tell him and
> > > > sd0 don't appear in the 'root device' choices.
> > > > 
> > > > From /i386, the hardware is :
> > > > mpt0 at pci2 dev 5 function 0: LSI Logic 53c1030 Ultra320 SCSI
> > > > mpt0: interrupting at ioapic1 pin 2 (irq 7)

Error: Error creating domain: (0, 'Error')

Hi,

I'm trying to start a netbsd (3-release) into netbsd/xen (3.0) too.
I read and did accordingly to
http://www.netbsd.org/Ports/xen/howto.html.

At the point of creating my first domain, I get :
	Error: Error creating domain: (0, 'Error')

Didn't found any interesting info on google...
Any idea what I do wrong ?

Here's a few things about my conf.
xen# uname -a
NetBSD xen.tumfatig.net 3.0_STABLE NetBSD 3.0_STABLE
(PE2850-XEN0-$Revision: 1.0.0 $) #0: Tue Jan  3 18:32:56 CET 2006
root <at> xen.tumfatig.net:/home/cvs/src/sys/arch/i386/compile/PE2850 i386

xen# /etc/rc.d/xend start
Starting xend.
/usr/pkg/lib/python2.3/site-packages/xen/xend/server/SrvDir.py:3:
DeprecationWarning: twisted.protocols.http has moved to
twisted.web.http. See http://twistedmatrix.com/projects/web.
  from twisted.protocols import http
log> [2006-01-03 19:40:47 xend] INFO (SrvDaemon:610) Xend Daemon started
log> [2006-01-03 19:40:47 xend] INFO (XendRoot:113) EVENT> xend.start 0

xen# xm list
Name              Id  Mem(MB)  CPU  State  Time(s)  Console
Domain-0           0       64    0  r----    348.1        

Re: Error: Error creating domain: (0, 'Error')

On Tue, Jan 03, 2006 at 05:46:37PM +0100, Joel CARNAT wrote:
> Hi,
> 
> I'm trying to start a netbsd (3-release) into netbsd/xen (3.0) too.
> I read and did accordingly to
> http://www.netbsd.org/Ports/xen/howto.html.
> 
> At the point of creating my first domain, I get :
> 	Error: Error creating domain: (0, 'Error')
> 
> Didn't found any interesting info on google...
> Any idea what I do wrong ?
> 
> Here's a few things about my conf.
> xen# uname -a
> NetBSD xen.tumfatig.net 3.0_STABLE NetBSD 3.0_STABLE
> (PE2850-XEN0-$Revision: 1.0.0 $) #0: Tue Jan  3 18:32:56 CET 2006
> root <at> xen.tumfatig.net:/home/cvs/src/sys/arch/i386/compile/PE2850 i386
> 
> xen# /etc/rc.d/xend start
> Starting xend.
> /usr/pkg/lib/python2.3/site-packages/xen/xend/server/SrvDir.py:3:
> DeprecationWarning: twisted.protocols.http has moved to
> twisted.web.http. See http://twistedmatrix.com/projects/web.
>   from twisted.protocols import http
> log> [2006-01-03 19:40:47 xend] INFO (SrvDaemon:610) Xend Daemon started
> log> [2006-01-03 19:40:47 xend] INFO (XendRoot:113) EVENT> xend.start 0
> 
> xen# xm list
> Name              Id  Mem(MB)  CPU  State  Time(s)  Console

Re: port-xen/30977: FPU troubles

On Mon, Dec 19, 2005 at 09:34:01AM +1100, Paul Ripke wrote:
> OK, I've had a closer look at this, and come up with the included patch,
> which appears to work fine for me, with threaded and non-threaded 
> programs.
> I can't repeat the behaviour of the FPU state being not being restored,
> restored to the wrong thread, or wiped.

This is great, many thanks ! I commited the attached patch, which
calls HYPERVISOR_fpu_taskswitch() at the end of npxsave_lwp() instead of the
various places in which call npxsave_lwp() in the code.

> 
> Thoughts behind the patch:
> - since clts() is a no-op under xen 2 (in xen 3, 
> HYPERVISOR_fpu_taskswitch
>   takes an int parameter allowing set/clear), it makes no sense to 
> stts()
>   inside the DNA handler. We can't clear it again.
> - I don't get the npxsave_lwp() calls in the DNA handler. On SMP, it's
>   used to dump an LWP's FPU state from a different CPU. On a 
> uniprocessor,
>   the FPU state has already been dumped by npxsave_cpu(). SMP support 
> isn't
>   relevant for xen 2.

Sure, but as it's #ifdef MULTIPROCESSOR, there's no problem keeping
it here. The goal is to eventually be able to share more code with i386.

--

-- 
Manuel Bouyer <bouyer <at> antioche.eu.org>

Re: port-xen/30977: FPU troubles

On Tue, Jan 03, 2006 at 09:21:52PM +0100, Manuel Bouyer wrote:
> On Mon, Dec 19, 2005 at 09:34:01AM +1100, Paul Ripke wrote:
> > OK, I've had a closer look at this, and come up with the included patch,
> > which appears to work fine for me, with threaded and non-threaded 
> > programs.
> > I can't repeat the behaviour of the FPU state being not being restored,
> > restored to the wrong thread, or wiped.
> 
> This is great, many thanks ! I commited the attached patch, which

 here is the patch

--

-- 
Manuel Bouyer <bouyer <at> antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--

Index: npx.c
===================================================================
RCS file: /cvsroot/src/sys/arch/xen/i386/npx.c,v
retrieving revision 1.6
diff -u -r1.6 npx.c
--- i386/npx.c	24 Dec 2005 20:07:48 -0000	1.6
+++ i386/npx.c	3 Jan 2006 19:09:33 -0000
 <at>  <at>  -146,7 +146,7  <at>  <at> 
 #define	stts()			lcr0(rcr0() | CR0_TS)
 #else
 #define	clts()
-#define	stts()			HYPERVISOR_fpu_taskswitch()

Re: Re: Error: Error creating domain: (0, 'Error')

woops - I'm just damm stupid...

trying your 'vnconfig' method, and the error still being there, I
re-read the whole HOWTO and checked my VM configuration file...
the 'kernel = ' file was pointing to the conf file (and not a kernel
file) }

now that's it's pointing to a *** real *** kernel file, it is much
better. the install process ran, saw and formatted the disk.

and BTW, using 'file: ' does work now my conf file is correct.
maybe the patches you talked about where submitted.

thanks for the help and sorry for the noise.
	Jo

Dans l'épisode précédent (Tue, Jan 03 2006 - 19:49), Manuel Bouyer nous apprenait que :
> On Tue, Jan 03, 2006 at 05:46:37PM +0100, Joel CARNAT wrote:
> > Hi,
> > 
> > I'm trying to start a netbsd (3-release) into netbsd/xen (3.0) too.
> > I read and did accordingly to
> > http://www.netbsd.org/Ports/xen/howto.html.
> > 
> > At the point of creating my first domain, I get :
> > 	Error: Error creating domain: (0, 'Error')
> > 
> > Didn't found any interesting info on google...
> > Any idea what I do wrong ?
> >