eth4 - The xen startup script renames eth4 to peth4, then creates a
bridge called eth4. You can also use the command "brctl show" to show
the currently configured bridges.
-Nick
>>> On 2009/11/03 at 09:49, James Pifer <jep@xxxxxxxxxxxxxxxx> wrote:
> On Tue, 2009-11-03 at 08:59 -0700, Nick Couchman wrote:
>> You might need to specify "bridge=<bridgename>" on the "vif=" line
in your
> config file and point it at a specific bridge.
>>
>> -Nick
>
> How can I tell what the bridge is called? Is it eth4 or peth4?
>
> brctl show gives me:
> bridge name bridge id STP enabled interfaces
> eth4 8000.002655827dd4 no peth4
>
>
> # ifconfig
> eth4 Link encap:Ethernet HWaddr 00:26:55:82:7D:D4
> inet addr:172.16.4.153 Bcast:10.96.5.255
Mask:255.255.254.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:147511 errors:0 dropped:0 overruns:0 frame:0
> TX packets:121841 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:30694748 (29.2 Mb) TX bytes:36280012 (34.5 Mb)
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:114 errors:0 dropped:0 overruns:0 frame:0
> TX packets:114 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:6850 (6.6 Kb) TX bytes:6850 (6.6 Kb)
>
> peth4 Link encap:Ethernet HWaddr 00:26:55:82:7D:D4
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:147623 errors:0 dropped:0 overruns:0 frame:0
> TX packets:124186 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:33415763 (31.8 Mb) TX bytes:36952614 (35.2 Mb)
> Interrupt:20 Memory:f8000000-f8012100
>
>
> I tied this these didn't work:
> vif=[ 'bridge=peth4,mac=00:16:3e:1a:45:41,model=rtl8139,type=ioemu',
]
> vif=[ 'bridge=eth4,mac=00:16:3e:1a:45:41,model=rtl8139,type=ioemu',
]
>
> I'd still like to get virt-manager working too, but not sure to go
about
> that.
>
> Thanks,
> James
--------
This e-mail may contain confidential and privileged material for the sole use
of the intended recipient. If this email is not intended for you, or you are
not responsible for the delivery of this message to the intended recipient,
please note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information. In such a case, you are strictly
prohibited from downloading, photocopying, distributing or otherwise using this
message, its contents or attachments in any way. If you have received this
message in error, please notify us immediately by replying to this e-mail and
delete the message from your mailbox. Information contained in this message
that does not relate to the business of SEAKR is neither endorsed by nor
attributable to SEAKR.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home