NetBSD -current / Xen 3.0.3: Problem starting xend

Sorry, the link wasn't complete. What i talked about was
this:
http://mail-index.netbsd.org/port-xen/2006/07/22/0004.
html

So, xencons and xenevt wouldn't be enough.
There seems to be a /dev/xsd_kva needed.

And my MAKEDEV don't create it (it is not up to date yet).
I think i have to finish the NetBSD update to get the needed
entrys (The kernel is already).
But i would like to test the kernel first and after that
finishing the update.
So it would be great to know what extra lines in MAKEDEV is
needed to create the xsd_kva device.

regards,
Rainer


> -----Ursprüngliche Nachricht-----
> Von: haad <haaaadgmail.com>
> Gesendet: 07.11.06 10:17:53
> An: Rainer Brinkmoeller <rainer.brinkmoellerweb.de>
> CC: port-xennetbsd.org
> Betreff: Re: NetBSD -current / Xen 3.0.3: Problem
starting xend


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi
> 
> You need this two devices in dev to run xen3 on netbsd
dom0 system.
> 
> $ ls /dev/xen*
> /dev/xencons  /dev/xenevt
> 
> You can create them with MAKEDEV .
> 
> $ cd /dev/
> 
> $ ./MAKEDEV xen*
> 
> If you have properly updated system you don't need to
patch MAKEDEV file

On Tue, Nov 07, 2006 at 11:22:27AM +0100, Rainer Brinkmöller
wrote:
> Sorry, the link wasn't complete. What i talked about
was this:
> http://mail-index.netbsd.org/port-xen/2006/07/22/0004.
html
> 
> So, xencons and xenevt wouldn't be enough.
> There seems to be a /dev/xsd_kva needed.
> 
> And my MAKEDEV don't create it (it is not up to date
yet).
> I think i have to finish the NetBSD update to get the
needed entrys (The kernel is already).
> But i would like to test the kernel first and after
that finishing the update.
> So it would be great to know what extra lines in
MAKEDEV is needed to create the xsd_kva device.

MAKEDEV is in the etc.tgz set. Just extract it somewhere and
copy the new
MAKEDEV to /dev, and run
cd /dev
./MAKEDEV xen

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

On Tue, 7 Nov 2006, Manuel Bouyer wrote:
> MAKEDEV is in the etc.tgz set. Just extract it
somewhere and copy the new
> MAKEDEV to /dev, and run
> cd /dev
> ./MAKEDEV xen

Shouldn't this happen automatically, to make the transition
from 
NetBSD/i386 to NetBSD/xen easier?

I've had a quick look at src/etc/etc.i386/MAKEDEV.conf, but
I'm not sure 
what 'target' runs by default. If it's "init",
maybe 'xen' should be added 
to that (and the xbd devices added to 'xen')?


  - Hubert

On Tue, Nov 07, 2006 at 01:02:39PM +0100, Hubert Feyrer
wrote:
> On Tue, 7 Nov 2006, Manuel Bouyer wrote:
> >MAKEDEV is in the etc.tgz set. Just extract it
somewhere and copy the new
> >MAKEDEV to /dev, and run
> >cd /dev
> >./MAKEDEV xen
> 
> Shouldn't this happen automatically, to make the
transition from 
> NetBSD/i386 to NetBSD/xen easier?
> 
> I've had a quick look at src/etc/etc.i386/MAKEDEV.conf,
but I'm not sure 
> what 'target' runs by default. If it's
"init", maybe 'xen' should be added 
> to that (and the xbd devices added to 'xen')?

Well, it adds a few devices that are of no use if you're not
on a Xen dom0
system (devices required in a domU are in 'all' target). I'm
not against
moving the dom0 devices to 'all' if noone (especially the
i386 portmaster)
objects.

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

On Tue, 7 Nov 2006, Manuel Bouyer wrote:
>> I've had a quick look at
src/etc/etc.i386/MAKEDEV.conf, but I'm not sure
>> what 'target' runs by default. If it's
"init", maybe 'xen' should be added
>> to that (and the xbd devices added to 'xen')?
>
> Well, it adds a few devices that are of no use if
you're not on a Xen dom0
> system (devices required in a domU are in 'all'
target). I'm not against
> moving the dom0 devices to 'all' if noone (especially
the i386 portmaster)
> objects.

Maybe we can ask him - who's it these days?


  - Hubert