On Fri, 2007-11-23 at 13:29 +0800, Zhang, Xing Z wrote:
> --- a/tools/examples/xmexample.vti Fri Aug 03 10:44:39 2007 -0600
> +++ b/tools/examples/xmexample.vti Thu Nov 22 14:03:24 2007 +0800
> @@ -37,9 +37,13 @@ name = "ExampleVTIDomain"
>
> # Optionally define mac and/or bridge for the network interfaces.
> # Random MACs are assigned if not given.
> -#vif = [ 'type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0,
> model=ne2k_pci' ]
> +# 'model' parameter specify which network card to use, current we
> have below
> +# selections:
> +# { rtl8139(default) ------ support linux
> +# e100(recommend) ------ support linux/windows }
> +#vif = [ 'type=ioemu, mac=00:16:3e:00:00:11, bridge=eth0,
> model=e100' ]
> # type=ioemu specify the NIC is an ioemu device not netfront
> -vif = [ 'type=ioemu, bridge=xenbr0' ]
> +vif = [ 'type=ioemu, bridge=eth0, model=e100' ]
I'm reluctant to make this the default because of the issues with the
e100 driver under Linux. Most (all?) Linux distros will attempt to use
the e100 driver instead of the eepro100 driver and experience the
problems you described. I think there should be a comment to that
affect here and the recommended nic for Linux guests should probably
remain the rtl8139 until your upstream e100 patch propagates to a few
distros.
Also, why the change from xenbr0 to eth0? xmexample.hvm still uses
xenbr0. I still use xenbr0 on my test system. Thanks,
Alex
--
Alex Williamson HP Open Source & Linux Org.
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
Home