RE: Problem with auto-starting DomU on NetBSD5.0.2 running Xen3.3

To: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
Subject: RE: Problem with auto-starting DomU on NetBSD5.0.2 running Xen3.3
From: Kalpesh Zinjuwadia <kzinjuwadia%force10networks.com@localhost>
Date: Wed, 25 Aug 2010 10:13:26 -0700

I fixed ifconfig.bridge1 file. However, still get same error. On console I see 
a new log which I didn't see earlier. Xen-debug.log says brctl not found. Can 
this be the root cause?

Appreciate your continuous help.

Kalpesh

Xen Dom0 console:

xbd backend attach device vnd0d for domain1 
Failed to read /local/domain/0/backend/console/1/0/script (no such file or 
directory)
NEW >>>>xbd backend: detach device vnd0d for domain 1 <<<< NEW
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
Starting local daemons:.

Ifconfig.bridge1:
create
!brconfig $int add ex0 up

netbsdjasper# ifconfig bridge1
bridge1: flags=41<UP,RUNNING> mtu 1500
netbsdjasper# brconfig bridge1
bridge1: flags=41<UP,RUNNING>
        Configuration:
                priority 32768 hellotime 2 fwddelay 15 maxage 20
                ipfilter disabled flags 0x0
        Interfaces:
                ex0 flags=3<LEARNING,DISCOVER>
                        port 1 priority 128
        Address cache (max cache: 100, timeout: 1200):
                00:1f:29:d5:a3:22 ex0 933 flags=0<>
                00:0f:20:e0:3a:e0 ex0 454 flags=0<>
                00:01:e9:45:00:03 ex0 450 flags=0<>
                00:0f:20:e0:3a:f5 ex0 449 flags=0<>
                00:14:5e:5d:a8:70 ex0 447 flags=0<>

Xenbackend.log
brconfig: unable to get interface flags: Device not configured
Failed to read /local/domain/0/backend/console/1/0/script (No such file or 
directory)
Failed to read /local/domain/0/backend/console/1/0/script (No such file or 
directory)

Xend-debug.log
Xend started at Wed Aug 25 11:54:44 2010.
brctl: not found
brctl: not found

Xend.log
[2010-08-25 11:54:45 212] DEBUG (XendDomainInfo:89) 
XendDomainInfo.create(['vm', ['name', 'nbsd03'], ['memory', 160], ['vcpus', 1], 
['on_xend_start', 'ignore'], ['on_xend_stop', 'i
gnore'], ['image', ['linux', ['kernel', '/netbsd-XEN3_DOMU'], ['ip', 
'10.11.204.184:127.0.255.255:10.11.204.254:255.255.255.0::eth0:off'], ['root', 
'xbd0']]], ['device', ['vbd', ['
uname', 'file:/dsk/nbsd03/nbsd03.img'], ['dev', '0x01'], ['mode', 'w']]], 
['device', ['vif', ['bridge', 'bridge1']]]])
[2010-08-25 11:54:45 212] DEBUG (XendDomainInfo:2043) 
XendDomainInfo.constructDomain
[2010-08-25 11:54:45 212] DEBUG (balloon:132) Balloon: 1255476 KiB free; need 
2048; done.
[2010-08-25 11:54:45 212] DEBUG (XendDomain:449) Adding Domain: 1
[2010-08-25 11:54:45 212] DEBUG (XendDomainInfo:2149) 
XendDomainInfo.initDomain: 1 256
[2010-08-25 11:54:45 212] DEBUG (XendDomainInfo:2230) 
_initDomain:shadow_memory=0x0, memory_static_max=0xa000000, 
memory_static_min=0x0.
[2010-08-25 11:54:45 212] DEBUG (balloon:132) Balloon: 1255468 KiB free; need 
164864; done.
[2010-08-25 11:54:45 212] INFO (image:166) buildDomain os=linux dom=1 vcpus=1
[2010-08-25 11:54:45 212] DEBUG (image:629) domid          = 1
[2010-08-25 11:54:45 212] DEBUG (image:630) memsize        = 160
[2010-08-25 11:54:45 212] DEBUG (image:631) image          = /netbsd-XEN3_DOMU
[2010-08-25 11:54:45 212] DEBUG (image:632) store_evtchn   = 1
[2010-08-25 11:54:45 212] DEBUG (image:633) console_evtchn = 2
[2010-08-25 11:54:45 212] DEBUG (image:634) cmdline        = root=xbd0 
ip=10.11.204.184:127.0.255.255:10.11.204.254:255.255.255.0::eth0:off
[2010-08-25 11:54:45 212] DEBUG (image:635) ramdisk        =
[2010-08-25 11:54:45 212] DEBUG (image:636) vcpus          = 1
[2010-08-25 11:54:45 212] DEBUG (image:637) features       =
[2010-08-25 11:54:47 212] INFO (XendDomainInfo:1907) createDevice: vbd : 
{'uuid': '4cb4f23c-327b-9dd6-7c1e-7e5184c33b1a', 'bootable': 1, 'driver': 
'paravirtualised', 'dev': '0x01',
 'uname': 'file:/dsk/nbsd03/nbsd03.img', 'mode': 'w'}
[2010-08-25 11:54:47 212] DEBUG (DevController:122) DevController: writing 
{'virtual-device': '1', 'device-type': 'disk', 'protocol': 'x86_64-abi', 
'backend-id': '0', 'state': '1',
 'backend': '/local/domain/0/backend/vbd/1/1'} to /local/domain/1/device/vbd/1.
[2010-08-25 11:54:47 212] DEBUG (DevController:124) DevController: writing 
{'domain': 'nbsd03', 'frontend': '/local/domain/1/device/vbd/1', 'uuid': 
'4cb4f23c-327b-9dd6-7c1e-7e5184c
33b1a', 'dev': '0x01', 'state': '1', 'params': '/dsk/nbsd03/nbsd03.img', 
'mode': 'w', 'online': '1', 'frontend-id': '1', 'type': 'file'} to 
/local/domain/0/backend/vbd/1/1.
[2010-08-25 11:54:47 212] INFO (XendDomainInfo:1907) createDevice: vif : 
{'bridge': 'bridge1', 'mac': '00:16:3e:01:5a:2e', 'uuid': 
'c8acbef5-6f0c-fe9d-66e2-1f42dee9dff8'}
[2010-08-25 11:54:47 212] DEBUG (DevController:122) DevController: writing 
{'mac': '00:16:3e:01:5a:2e', 'handle': '0', 'protocol': 'x86_64-abi', 
'backend-id': '0', 'state': '1', 'b
ackend': '/local/domain/0/backend/vif/1/0'} to /local/domain/1/device/vif/0.
[2010-08-25 11:54:47 212] DEBUG (DevController:124) DevController: writing 
{'bridge': 'bridge1', 'domain': 'nbsd03', 'handle': '0', 'uuid': 
'c8acbef5-6f0c-fe9d-66e2-1f42dee9dff8',
'script': '/usr/pkg/etc/xen/scripts/vif-bridge', 'mac': '00:16:3e:01:5a:2e', 
'frontend-id': '1', 'state': '1', 'online': '1', 'frontend': 
'/local/domain/1/device/vif/0'} to /local/
domain/0/backend/vif/1/0.
[2010-08-25 11:54:48 212] DEBUG (XendDomainInfo:2738) Storing VM details: 
{'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid': 
'34531194-ddfe-d774-0922-888727f0af3f', 'on_reboo
t': 'restart', 'start_time': '1282737288.26', 'on_poweroff': 'destroy', 
'bootloader_args': '', 'on_xend_start': 'ignore', 'on_crash': 'restart', 
'xend/restart_count': '0', 'vcpus':
 '1', 'vcpu_avail': '1', 'bootloader': '', 'image': "(linux (kernel 
/netbsd-XEN3_DOMU) (args 'root=xbd0 
ip=10.11.204.184:127.0.255.255:10.11.204.254:255.255.255.0::eth0:off ') (not
es))", 'name': 'nbsd03'}
[2010-08-25 11:54:48 212] DEBUG (XendDomainInfo:1360) Storing domain details: 
{'console/ring-ref': '312159', 'console/port': '2', 'name': 'nbsd03', 
'console/limit': '1048576', 'vm'
: '/vm/34531194-ddfe-d774-0922-888727f0af3f', 'domid': '1', 'store/port': '1', 
'cpu/0/availability': 'online', 'memory/target': '163840', 
'control/platform-feature-multiprocessor-s
uspend': '1', 'store/ring-ref': '312160', 'console/type': 'xenconsoled'}
[2010-08-25 11:54:48 212] DEBUG (DevController:122) DevController: writing 
{'protocol': 'x86_64-abi', 'state': '1', 'backend-id': '0', 'backend': 
'/local/domain/0/backend/console/1
/0'} to /local/domain/1/device/console/0.
[2010-08-25 11:54:48 212] DEBUG (DevController:124) DevController: writing 
{'domain': 'nbsd03', 'frontend': '/local/domain/1/device/console/0', 'uuid': 
'09899b33-127d-33b7-623e-69f
3d9951f09', 'frontend-id': '1', 'state': '1', 'location': '2', 'online': '1', 
'protocol': 'vt100'} to /local/domain/0/backend/console/1/0.
[2010-08-25 11:54:49 212] DEBUG (XendDomainInfo:1450) 
XendDomainInfo.handleShutdownWatch
[2010-08-25 11:54:49 212] DEBUG (DevController:166) Waiting for devices vif.
[2010-08-25 11:54:49 212] DEBUG (DevController:171) Waiting for 0.
[2010-08-25 11:54:49 212] DEBUG (DevController:656) hotplugStatusCallback 
/local/domain/0/backend/vif/1/0/hotplug-status.
[2010-08-25 11:56:29 212] DEBUG (XendDomainInfo:2409) XendDomainInfo.destroy: 
domid=1
[2010-08-25 11:56:29 212] DEBUG (XendDomainInfo:1946) Destroying device model
[2010-08-25 11:56:29 212] DEBUG (XendDomainInfo:1953) Releasing devices
[2010-08-25 11:56:29 212] DEBUG (XendDomainInfo:1966) Removing vif/0
[2010-08-25 11:56:29 212] DEBUG (XendDomainInfo:910) 
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2010-08-25 11:56:29 212] ERROR (XendDomainInfo:1973) Device release failed: 
nbsd03; vif; vif/0
Traceback (most recent call last):
  File "usr/pkg/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 
1967, in _releaseDevices
    self.destroyDevice(true_devclass, dev, False);
  File "usr/pkg/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 
924, in destroyDevice
    rc = self.getDeviceController(deviceClass).destroyDevice(devid, force)
  File "usr/pkg/lib/python2.5/site-packages/xen/xend/server/DevController.py", 
line 255, in destroyDevice
    self.writeBackend(dev, 'online', "0")
  File "usr/pkg/lib/python2.5/site-packages/xen/xend/server/DevController.py", 
line 501, in writeBackend
    raise VmError("Device %s not connected" % devid)
VmError: Device 0 not connected
[2010-08-25 11:56:29 212] DEBUG (XendDomainInfo:1966) Removing vbd/1
[2010-08-25 11:56:29 212] DEBUG (XendDomainInfo:910) 
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/1
[2010-08-25 11:56:29 212] DEBUG (XendDomainInfo:1966) Removing console/0
[2010-08-25 11:56:29 212] DEBUG (XendDomainInfo:910) 
XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
[2010-08-25 11:56:30 212] DEBUG (XendDomainInfo:1951) No device model
[2010-08-25 11:56:30 212] DEBUG (XendDomainInfo:1953) Releasing devices
[2010-08-25 11:56:30 212] DEBUG (DevController:656) hotplugStatusCallback 
/local/domain/0/backend/vif/1/0/hotplug-status.



-----Original Message-----
From: Manuel Bouyer [mailto:bouyer%antioche.eu.org@localhost] 
Sent: Wednesday, August 25, 2010 9:40 AM
To: Kalpesh Zinjuwadia
Cc: port-xen%netbsd.org@localhost
Subject: Re: Problem with auto-starting DomU on NetBSD5.0.2 running Xen3.3

On Wed, Aug 25, 2010 at 09:31:53AM -0700, Kalpesh Zinjuwadia wrote:
> How is the bridge interface created at boot ?
> /etc/ifconfig.bridge1 ?
> 
> KZ> Yes. Content of ifconfig.bridge1 are:
> create
> inet 10.11.204.182
but you can't set an IP address on a bridge. This line should be removed

> !brconfig bridge1 add $int up

this is also wrong, I guess you want
!brconfig $int add ex0 up

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

Follow-Ups:
- Re: Problem with auto-starting DomU on NetBSD5.0.2 running Xen3.3
  - From: Manuel Bouyer

References:
- Problem with auto-starting DomU on NetBSD5.0.2 running Xen3.3
  - From: Kalpesh Zinjuwadia
- Re: Problem with auto-starting DomU on NetBSD5.0.2 running Xen3.3
  - From: Manuel Bouyer
- RE: Problem with auto-starting DomU on NetBSD5.0.2 running Xen3.3
  - From: Kalpesh Zinjuwadia
- Re: Problem with auto-starting DomU on NetBSD5.0.2 running Xen3.3
  - From: Manuel Bouyer

Prev by Date: Re: Problem with auto-starting DomU on NetBSD5.0.2 running Xen3.3
Next by Date: RE: Problem with auto-starting DomU on NetBSD5.0.2 running Xen3.3
Previous by Thread: Re: Problem with auto-starting DomU on NetBSD5.0.2 running Xen3.3
Next by Thread: Re: Problem with auto-starting DomU on NetBSD5.0.2 running Xen3.3
Indexes:

Home | Main Index | Thread Index | Old Index