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

["You, Yongkang" <yongkang.you@xxxxxxxxx>]

>-----Original Message-----
>From: micky@xxxxxxxxxxxxxxxxxxxxxxxxxxx
>[mailto:micky@xxxxxxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of
>Doi.Tsunehisa@xxxxxxxxxxxxxx
>Sent: 2006年10月18日 15:56
>To: You, Yongkang
>Cc: DOI Tsunehisa; xen-ia64-devel
>Subject: Re: [Xen-ia64-devel] Please try PV-on-HVM on IPF
>
>  Hi Yongkang,
>
>  Thank you for your report.
>
>  Does it output this trace back message when you detach vnif with
>xm network-detach command ?
No. I didn't use above command to detach vnif. Usually I used following ways to 
enable vnif NIC.
1. create VTI with vif = [ '' ]
2. After VTI boot up, insert 3 related PV drivers to enable VNIF.
3. If there is a /etc/sysconfig/network-script/ifcfg-eth0, I need not do 
anything, VNIF eth0 will be brought up.

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', '' ]

>
>  What is the guest OS vesion ?
The VTI guest OS is RHEL4u3.
>
>Thanks,
>- Tsunehisa
>


Best Regards,
Yongkang (Kangkang) 永康

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