Re: [Xen-ia64-devel] Please try PV-on-HVM on IPF

["Kasai Takanori" <kasai.takanori@xxxxxxxxxxxxxx>]

Hi Yangkang,

> > > You (yongkang.you) said:
> > > > The trace back message will happen when I just inserted vnif driver into
> > > > VTI, when I used 2 NICs for VTI (1 is IOEMU, the other is VNIF).
> > > >
> > > > >  I've looked `netif_release_rx_bufs: fix me for copying receiver.'
> > > > > message sometimes at vnif detaching. But I've not met domain-vti
> > > > > crash.
> > > > The crashing happened if I also use IOEMU NIC for VTI domain. The VTI
> > vif
> > > > config should like:
> > > > vif = [ 'type=ioemu, bridge=xenbr0', '' ]
> > >  Thanks. I'll try it.
> > I was able to confirm this problem occurred in the same environment.
> > (changeset :11810 )
> > We continue and investigate this problem.
Sorry, the reply was delayed.
I have confirmed this problem has already corrected it as follows. 
The crash doesn't happen even if IOEMU NIC is used for the VTI domain. 

> > > > >
・xen-unstable.hg       : cs 12048
・xen-ia64-unstable.hg  : cs 12062

[NET] front: Clean up error handling. 
This eliminates earlier work around patch for an observed crash.
> > > > >
However, IOEMU NIC is registered in xenwatch as VNIF. 
Then the crashing happened if 'xm network-detach' is executed for IOEMU NIC.
Because IOEMU NIC is shut as VNIF. 

I think that I should not register originally IOEMU NIC in xenwatch.
Because the same issue exists for x86 architecture, 
I'll contribute it to the xen-devel community.
Thanks,

--
Takanori Kasai




_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel