Re: [Xen-users] DomU's unable to connect to vnet0 / bridge

[Sreeharsha Totakura <sreeharsha.totakura@xxxxxxx>]

> "Fajar A. Nugraha" <fajar@xxxxxxxxx>
> Sent by: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
>
> 06/17/2009 06:52 AM
>
> To
>
> Xen User-List <xen-users@xxxxxxxxxxxxxxxxxxx>
>
> cc
>
> Subject
>
> Re: [Xen-users] DomU's unable to connect to vnet0 / bridge
>
> On Wed, Jun 17, 2009 at 2:56 AM, <cyber@xxxxxxxxxxxxxxxxxxx> wrote:
> > I'm working now.  I talked with one of the NOC nerds here at work and
he had
> > JUST fought through the same problems the previous weekend so had the
> > solution at hand.  In the end, it seems that the XEN bridge scripts for
RHEL
> > 5.3 will ONLY work for ETH0.
>
> If it's true, that would be a bug, and you should use RHN to report
> that. After all, that's what you're paying RHEL support for isn't it?
>
> >  I made a number of changes along the way, so
> > I'm not 100% sure exactly which modifications were required to get
things
> > working, but this is the best guess at the mods made that got me
working:
> > 1)  Switched over my named.conf to only listen on lo, eth0, and eth1.
> >
> > 2)  Set dnsmasq.conf to only listen on vnet1 and exclude lo, eth0,and
eth1.
> >
>
> I'm actually confused to read this. What's vnet1? xen on RHEL only
> create xenbr0 and virbr0 by default. Did you create your own bridge?
>

I guess the virt-manager on RHEL creates  a virtual interface vnetX for
every vitual machine you start. If you have two virtual machines, you will
have two vnet interfaces, vnet1, vnet2. xenbr0 is used to bridge these
virtual interfaces with the physical network through eth0/eth1

-Harsha

=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you




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