Subject: Re: NetBSD-Current/XEN3 : XM CREATE problem
To: None <port-xen@netbsd.org>
From: KlinT <klint@klintcentral.net>
List: port-xen
Date: 07/16/2006 19:21:45
SOLVED :

Here are the configuration that works for me :

On Domain0 / NetBSD 3.99.22 / Xen 3.0.2.2 :

/etc/ifconfig.bridge0 ( "re0" is my default network device )
-----------------------------------------------------------------------
create
!brconfig $int add re0 stp re0 up
-----------------------------------------------------------------------
/usr/pkg/etc/xen/xend-config.sxp : changing the following line

(network-script network-bridge)
by this one :
(network-script 'network-bridge netdev=3Dre0')

And finally : the configuration file itself :
-----------------------------------------------------------------------
kernel =3D "/root/netbsd-XEN3_DOMU"
memory =3D 128
name =3D "test"
#cpus =3D ""         # leave to Xen to pick
#cpus =3D "0"        # all vcpus run on CPU0
#cpus =3D "0-3,5,^1" # run on cpus 0,2,3,5
# vcpus =3D 1
vif =3D [ 'bridge=3Dbridge0' ]
# disk =3D [ 'phy:/dev/wd0h,0x03,w', 'phy:/dev/cd0a,0x04,r' ]
disk =3D [ 'phy:/dev/wd0h,0x03,w' ]
root =3D "/dev/wd0d ro"
-----------------------------------------------------------------------

Hope these tests will help ...

Best Regards

Arnaud.

Le 16 juil. 06 =E0 19:07, KlinT a =E9crit :

>
> Well, it seems to work :
>
> Here is what i did :
>
> my config file is "test" :
>
> #---------------------------------------------------------------------=20=

> -------
> kernel =3D "/root/netbsd-INSTALL_XEN3_DOMU"
> # kernel =3D "/root/netbsd-XEN3_DOMU"
> # ramdisk =3D "/boot/initrd.gz"
> # builder=3D'linux'
> memory =3D 128
> name =3D "test"
> # List of which CPUS this domain is allowed to use, default Xen picks
> #cpus =3D ""         # leave to Xen to pick
> #cpus =3D "0"        # all vcpus run on CPU0
> #cpus =3D "0-3,5,^1" # run on cpus 0,2,3,5
> # vcpus =3D 1
> # vif =3D [ '', 'bridge=3Dxenbr1' ]
> # vif =3D [ '', 'bridge=3Dbridge0' ]
> # vif =3D [ '' ]
> # vif =3D [ '', 'bridge=3Dxenbr0' ]
> disk =3D [ 'phy:/dev/wd0h,0x03,w', 'phy:/dev/cd0a,0x04,r' ]
> # disk =3D [ 'phy:/dev/wd0h,0x03,w' ]
> root =3D "/dev/wd0d ro"
> extra =3D "4"
> #---------------------------------------------------------------------=20=

> -------
>
> With this, I have successfully install NetBSD.DomU ...
>
> But at this point I still have no network :(
>
> I've tried many configuration parameters in xend-config.sxp without =20=

> any success
>
> Any idea ?
>
> Le 16 juil. 06 =E0 18:18, KlinT a =E9crit :
>
>>
>> Well,
>>
>> I've made some tests and read some documentation .... :D
>>
>> I forgot to start xenbackend daemon :D This solve the error I've =20
>> posted before without using "0x03" :
>>
>> =3D=3D> xbdback: can' read backend/vbd/1/3/handle: 79
>>
>> But the "xm create" still not work ... :(
>>
>> =3D=3D> Error: Device 0 (vif) could not be connected. Hotplug scripts =
not
>>
>> Any idea ?
>>
>> Do I need a ifconfig.bridge0 like in xen 2.0.7 ?
>>
>> Is there any parameters to setup in xend-config.sxp ?
>>
>> Many thanks ...
>>
>> Arnaud
>>
>> Le 16 juil. 06 =E0 10:50, KlinT a =E9crit :
>>
>>>
>>> Le 16 juil. 06 =E0 10:40, Juan RP a =E9crit :
>>>
>>>> On Sun, 16 Jul 2006 10:23:42 +0200
>>>> KlinT <klint@klintcentral.net> wrote:
>>>>
>>>> [...]
>>>>
>>>>> xm create -c ./test
>>>>> Using config file "./test".
>>>>> Error: Device 0 (vif) could not be connected. Hotplug scripts not
>>>>> working.
>>>>>
>>>>> Here is my config file :
>>>>>
>>>>> kernel =3D "/root/netbsd-INSTALL_XEN3_DOMU"
>>>>> # kernel =3D "/root/netbsd-XEN3_DOMU"
>>>>> memory =3D 128
>>>>> name =3D "test"
>>>>> cpus =3D ""
>>>>> vif =3D [ 'bridge=3Dbridge0' ]
>>>>> disk =3D [ 'phy:/dev/wd0h,wd0d,w' ]
>>>>> root =3D "/dev/wd0d ro"
>>>>
>>>> I read through the archives and looks like you need to change wd0d
>>>> to 0x03.
>>>>
>>>
>>> Yeah, this solve a part of my problem ...
>>>
>>> xm create -c ./test
>>> Using config file "./test".
>>> Error: Device 0 (vif) could not be connected. Hotplug scripts not =20=

>>> working.
>>>
>>> Same error :D
>>>
>>> But, this solves the following error :
>>>
>>> xbdback: can' read backend/vbd/1/3/handle: 79
>>>
>>> Maybe I missed the VIF/Bridge configuration
>>>
>>> many thanks
>>>
>>> Best regards
>>>
>>> arnaud.
>>
>>
>
>