[Xen-users] 答复: xl network-attach

[席康杰 <xikangjie@xxxxxx>]

Thank you very much, xl network-attach is very important for me.

-----邮件原件-----
发件人: Wei Liu [mailto:wei.liu2@xxxxxxxxxx] 
发送时间: 2016年5月19日 0:25
收件人: 席康杰
抄送: Xen-users@xxxxxxxxxxxxx; Wei Liu
主题: Re: [Xen-users] xl network-attach

On Wed, May 18, 2016 at 04:45:43PM +0100, Wei Liu wrote:
> On Wed, May 18, 2016 at 01:12:39PM +0000, 席康杰 wrote:
> > Hi,
> > 
> > 
> > 
> > I use ‘xl network-attach’ to attach a nic, but failed.
> > 
> > 
> > 
> > # xl -vvv network-attach 6028 mac=00:16:3e:eb:ca:81 bridge=virbr0
> 
> As a starter, can you try:
> 
>  xl -vvv network-attach 6028 "mac=00:16:3e:eb:ca:81,bridge=virbr0"
> 
> ISTR there is a problem with command line argument parsing and even 
> wrote a patch series for it.
> 
> Worth trying anyway.
> 
> > 
> > libxl: debug: libxl.c:4247:libxl_device_nic_add: ao 0x20a9190: 
> > create: how=(nil) callback=(nil) poller=0x20a91f0
> > 
> > libxl: debug: libxl_event.c:577:libxl__ev_xswatch_register: watch 
> > w=0x20a5948 wpath=/local/domain/0/backend/vif/6028/0/state 
> > token=3/0: register slotnum=3
> > 
> > libxl: debug: libxl.c:4247:libxl_device_nic_add: ao 0x20a9190: 
> > inprogress: poller=0x20a91f0, flags=i
> > 
> > libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0x20a5948 
> > wpath=/local/domain/0/backend/vif/6028/0/state token=3/0: event 
> > epath=/local/domain/0/backend/vif/6028/0/state
> > 
> > libxl: debug: libxl_event.c:834:devstate_watch_callback: backend 
> > /local/domain/0/backend/vif/6028/0/state wanted state 2 still 
> > waiting state 1
> > 
> > libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0x20a5948 
> > wpath=/local/domain/0/backend/vif/6028/0/state token=3/0: event 
> > epath=/local/domain/0/backend/vif/6028/0/state
> > 
> > libxl: debug: libxl_event.c:830:devstate_watch_callback: backend 
> > /local/domain/0/backend/vif/6028/0/state wanted state 2 ok
> > 
> > libxl: debug: libxl_event.c:615:libxl__ev_xswatch_deregister: watch 
> > w=0x20a5948 wpath=/local/domain/0/backend/vif/6028/0/state 
> > token=3/0: deregister slotnum=3
> > 
> > libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch 
> > w=0x20a5948: deregister unregistered
> > 
> > libxl: debug: libxl_device.c:1028:device_hotplug: calling hotplug 
> > script: /etc/xen/scripts/vif-bridge online
> > 
> > libxl: debug: libxl_aoutils.c:513:libxl__async_exec_start: forking 
> > to execute: /etc/xen/scripts/vif-bridge online
> > 
> > libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch 
> > w=0x20a59d0: deregister unregistered
> > 
> > libxl: debug: libxl_device.c:1028:device_hotplug: calling hotplug 
> > script: /etc/xen/scripts/vif-bridge add
> > 
> > libxl: debug: libxl_aoutils.c:513:libxl__async_exec_start: forking 
> > to execute: /etc/xen/scripts/vif-bridge add
> > 
> > libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: 
> > /etc/xen/scripts/vif-bridge add [-1] exited with error status 255
> > 
> 
> This is the culprit.
> 
> > libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch 
> > w=0x20a59d0: deregister unregistered
> > 
> > libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch 
> > w=0x20a59d0: deregister unregistered
> > 
> > libxl: error: libxl.c:1965:device_addrm_aocomplete: unable to add 
> > vif with id 0
> > 
> > libxl: debug: libxl_event.c:1765:libxl__ao_complete: ao 0x20a9190: 
> > complete, rc=-3
> > 
> > libxl: debug: libxl_event.c:1737:libxl__ao__destroy: ao 0x20a9190: destroy 
> > libxl_device_nic_add failed.
> > 
> > xc: debug: hypercall buffer: total allocations:26 total releases:26
> > 
> > xc: debug: hypercall buffer: current allocations:0 maximum 
> > allocations:2
> > 
> > xc: debug: hypercall buffer: cache current size:2
> > 
> > xc: debug: hypercall buffer: cache hits:20 misses:2 toobig:4
> > 
> > 
> > 
> > # xl network-list 6028
> > 
> > Idx BE Mac Addr.         handle state evt-ch   tx-/rx-ring-ref BE-path
> > 
> > 0   0  00:16:3e:eb:ca:81     0     1     -1    -1/-1          
> > /local/domain/0/backend/vif/6028/0
> > 
> > 
> > 
> > # brctl show
> > 
> > bridge name     bridge id               STP enabled     interfaces
> > 
> > virbr0          8000.feffffffffff       no              vif6028.0
> > 
> > 
> > 
> > If succeed to attach，’brctl show’ will output:
> > 
> > bridge name     bridge id               STP enabled     interfaces
> > 
> > virbr0          8000.feffffffffff       no              vif6028.0
> > 
> >                                                   vif6028.0-emu
> > 
> > 
> > 
> > # cat /var/log/xen/xen-hotplug.log
> > 
> > Cannot find device "vif6028.0-emu"
> > 
> 
> This is strange...
> 
> Let me try to test this functionality a bit.
> 

OK, so apparently the attachment of the PV interface is successfully
(vif6028.0) and you can check that in your guest with ifconfig -a.

It's the attachment of emulated interface that failed. I will have a closer 
look of the code tomorrow.

Wei.

> Wei.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users