Sarton O'Brien | 1 Dec 01:23 2006

Re: Strange "root on %s" automatic selection

On Friday 01 December 2006 08:16, you wrote:
> > I tried "root=wd0" and "root=wd0a" but it still does not work.
> > Or maybe I didn't understood which part to modify :)
>
> Ops sorry it's not "root=wd0" it's "bootdev=wd0"

Awesome. This is the answer I was looking for when I plugged in my USB drive 
about 2 months ago :) ... I avoided altering the kernel config and this makes 
life a bit easier.

Sarton

KazushiMarukawa | 1 Dec 01:02 2006
Picon

Re: Strange "root on %s" automatic selection

   On Dec 1,  0:25, Juan RP wrote:
   > Subject: Re: Strange "root on %s" automatic selection
   > On Friday 01 December 2006 00:24, Kazushi  Marukawa wrote:
   > > P.S. I have another question.  Is there any way to pass -s
   > > or -a arguments to Multiboot NetBSD kernel from GRUB?
   > Sure, If I remember correctly:
   > 
   > title NetBSD/MultiBoot
   > kernel (hd0,1,a)/netbsd console=pc -s

   On Nov 30, 23:47, Pavel Cahyna wrote:
   > Subject: Re: Re: Strange "root on %s" automatic selection
   > it should be:
   > kernel ... -s root=...

Many thanks.  It's wonderful having Multiboot NetBSD kernel.  :-)

-- Kazushi
It is Mr. Mellon's credo that $200,000,000 can do no wrong.  Our
offense consists in doubting it.
		-- Justice Robert H. Jackson

david l goodrich | 1 Dec 02:06 2006

Re: Motherboard comments?

> Both have an AHCI SATA controller, but the PDSME+ is 3.0Gb/s (ws 1.5Gb/s for
> the P8SCi). 

speaking for the more general case, is there a good resource for
supported and unsupported SATA controllers in netbsd?  Are there
chipsets that are better or worse for use as a xen dom0 running
netbsd?
  --david

Steven M. Bellovin | 1 Dec 04:37 2006

Re: Motherboard comments?

On Fri, 1 Dec 2006 00:29:01 +0100
Manuel Bouyer <bouyer <at> antioche.eu.org> wrote:

> On Thu, Nov 30, 2006 at 06:05:56PM -0500, Steven M. Bellovin wrote:
> > On Thu, 30 Nov 2006 23:48:56 +0100
> > Manuel Bouyer <bouyer <at> antioche.eu.org> wrote:
> > 
> > > On Thu, Nov 30, 2006 at 05:14:16PM -0500, Steven M. Bellovin
> > > wrote:
> > > > I'm getting ready to build a new 1U server for myself; those two
> > > > MBs have been suggested.
> > > 
> > > I think you forgot to name the motherboards ...
> > > 
> > 
> > Oops!
> > 
> > http://www.supermicro.com/products/motherboard/Xeon3000/3010/PDSME+.cfm
> > http://www.supermicro.com/products/motherboard/P4/E7221/P8SCi.cfm
> 
> OK. I'm not sure the 82573 ethernet works fine with NetBSD, but I'm
> not sure about the broadcom either.

The 82573E and 82573L are listed in pcidevs, as is the Broadcom 5721,
so they *should* work.  The question is whether or not they do....

> VT support is definitively a plus for Xen, I can't live without it
> any more :)

What, precisely, does VT buy me?  I know that it lets me run non-Xen
(Continue reading)

Lubomir Sedlacik | 1 Dec 06:59 2006

Re: Motherboard comments?

On Thu, Nov 30, 2006 at 10:37:14PM -0500, Steven M. Bellovin wrote:
> On Fri, 1 Dec 2006 00:29:01 +0100 Manuel Bouyer wrote:
> >
> > OK. I'm not sure the 82573 ethernet works fine with NetBSD, but I'm
> > not sure about the broadcom either.
> 
> The 82573E and 82573L are listed in pcidevs, as is the Broadcom 5721,
> so they *should* work.  The question is whether or not they do....

FYI, being listed in pcidevs means nothing, really.  what counts is the
match table in the respective driver needs to include the reference to
the device.  (coincidentally, they are all listed there, this time)

regards,

--

-- 
-- Lubomir Sedlacik <salo <at> {NetBSD,Xtrmntr,silcnet}.org>   --
John R. Shannon | 1 Dec 11:41 2006

Re: Motherboard comments?

Steven M. Bellovin wrote:
> The 82573E and 82573L are listed in pcidevs, as is the Broadcom 5721,
> so they *should* work.  The question is whether or not they do....

I also have several Supermicro 5014C-MF running NetBSD/Xen.  These use 
the Broadcom 5721. I'm encountering no problems. These machine use CF 
card instead of disk drives so I've not tried the onboard SATA controller.

--

-- 
John R. Shannon, CISSP
Chief Scientist
DSCI, Information Assurance Division
jshannon <at> dsci-usa.com
john.r.shannon <at> us.army.mil
shannonjr <at> NetBSD.org
(208)522-4506

Matthias Scheler | 1 Dec 15:45 2006
Picon

Re: Motherboard comments?

On Fri, Dec 01, 2006 at 12:29:01AM +0100, Manuel Bouyer wrote:
> OK. I'm not sure the 82573 ethernet works fine with NetBSD, but I'm
> not sure about the broadcom either.

It should work fine in NetBSD current, see here:

http://mail-index.netbsd.org/tech-net/2006/11/20/0000.html

	Kind regards

--

-- 
Matthias Scheler                                  http://zhadum.org.uk/

Manuel Bouyer | 1 Dec 21:15 2006

Re: Motherboard comments?

On Thu, Nov 30, 2006 at 10:37:14PM -0500, Steven M. Bellovin wrote:
> > OK. I'm not sure the 82573 ethernet works fine with NetBSD, but I'm
> > not sure about the broadcom either.
> 
> The 82573E and 82573L are listed in pcidevs, as is the Broadcom 5721,
> so they *should* work.  The question is whether or not they do....
> 
> > VT support is definitively a plus for Xen, I can't live without it
> > any more :)
> 
> What, precisely, does VT buy me?  I know that it lets me run non-Xen
> guest OSs.  Does it help with performance when running a NetBSD DomU?

No. But it's nice to be able to play with non-Xen hardware :)
I use it for various tests too.

--

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

Rainer Brinkmoeller | 1 Dec 23:14 2006
Picon

Xen 3.0.3 with NetBSD -current and Win domU

I'd try to setup a Win domU for a while.
Try it with different configurations, different image files, again and 
again.
First, all seems to be fine. The setup starts, then there is the choice 
to press F6
to select SCSI drives (or the hint F5 for different setup methods),
the Win setup loads the drivers and in the moment it should show
the information to press Enter for start the main setup the screen get black
(sometimes there is a blue screen for a few seconds which says something
because hard disk problems or so)
A few minutes later the domU shutdown by itself.

Here the config file:
#==================================================
kernel = "/usr/pkg/lib/xen/boot/hvmloader"
builder='hvm'
memory = 512
name = "winxp-hvm"
vif = [ 'mac=00:16:3e:00:00:14, bridge=bridge0, type=ioemu' ]
device_model = "/usr/pkg/libexec/qemu-dm"

disk = [ 'file:/xenimg/windisk.img,ioemu:hda,w', 
'file:/data/cdimg/wxpsp1.img,ioemu:hdc:cdrom,r' ]
# disk = [ 'file:/xenimg/windisk.img,ioemu:sda,w', 
'file:/data/cdimg/wxpsp1.img,ioemu:hdc:cdrom,r' ]

boot='d'

ne2000 = 0
#==================================================
(Continue reading)

Simon Truss | 3 Dec 17:45 2006
Picon
Picon

Xen3 DomU spins 100% busy during console access

Hi,

I was in vim in insert mode and just pasted a large selection into the 
xenconsole - instant busy lockup. Once I figured out what caused it I 
was able to repeat this 5 out of 5 times.

I tried this with small simple lines and was never able to lockup the 
console. I have however managed to to cause this lockup by pasting less 
than 1KB of data, and then pasting more in small pieces until it exceeds 
1KB. I have no idea why 1KB might be a magic number but perhaps its a hint.

lastly I also had a similar lockup by just connecting to the console 
with 'xm console test1' no copy paste with the mouse at all.

this is an intel HT core, both Dom0 and DomU running 4.99.4 from Nov28 
daily builds.

xentools30-3.0.3nb1
xenkernel30-3.0.3

Simon


Gmane