Re: Could not open channel to DOM0

[Manuel Bouyer <bouyer%antioche.lip6.fr@localhost>]

On Sun, Jul 10, 2005 at 11:55:36AM -0700, David Rio Deiros wrote:
> On Sat, Jul 09, 2005 at 11:39:08AM -0700, David Rio Deiros wrote:
> > Hi, 
> > 
> > I am trying to get working xen and I am having some issues when I 
> > try to create DOMUs.
> 
> [..]
> 
> > Can anyone tell me what is the problem here? Can the problem be 
> > that I am using an "old version" of netbsd-current and recent 
> > versions of xen and xentools?
> 
> The problem was I was using an old version of netbsd-current. After

Yes, I'll delete these snapshots (they were there becaus ethe daily build
were not up again at this time).

> installing one of the daily snapshots, almost everything seems to work. 
> 
> Now I am using:
> 
> NetBSD xen 3.99.7 NetBSD 3.99.7 (XEN0) #0: Wed Jul  6
> 
> as a domain0.
> 
> This is the hard drive partition table:
> 
> 0: NetBSD (sysid 169)
>     bootmenu: Read
>     start 63, size 8193087 (4001 MB, Cyls 0/1/1-510), Active
>         beg: cylinder    0, head   1, sector  1
>         end: cylinder  509, head 254, sector 63
> 1: NetBSD (sysid 169)
>     bootmenu: or
>     start 8194048, size 20481977 (10001 MB, Cyls 510/14/17-1785)
>         beg: cylinder  510, head  14, sector 17
>         end: cylinder 1023, head 254, sector 63
> 
> And this is the disklabel in the first partition:
> 
>  a:   7929936        63     4.2BSD   2048 16384 28872  # (Cyl.      0*-
> 7867*)
>  b:    263151   7929999       swap                     # (Cyl.   7867*-
> 8128*)
>  c:   8193087        63     unused      0     0        # (Cyl.      0*-
> 8128*)
>  d:  78165360         0     unused      0     0        # (Cyl.      0 -
> 77544)
>  e:  20481977   8194048     4.2BSD    512  4096 22640  # (Cyl.   8129*-
> 28448*)
> 
> And this is the config file for DOMU:
> 
> kernel = "/netbsd-XENU"
> memory = 32
> name = "nbsd"
> cpu = -1
> nics=0
> disk = [ 'phy:/dev/cd0a,cd0a,r', 'phy:/dev/wd0e,wd0d,w' ]
> root = "/dev/wd0d"
> 
> When I start the new domain, it stops at:
> 
> xbd: using event channel 4
> xbd0 at hypervisor0: Xen Virtual Block Device 10000 MB
> xbd1 at hypervisor0: Xen Virtual Block Device 195 MB
> 
> Can anyone tell me what I am doing wrong here?

I don't think a generic XENU kernel will work without nics. My guess it that
it's waiting for the xennet interfaces to come up.

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