<div>Mark,</div>
<div> </div>
<div>You have to way to affect DomU networkin setup:</div>
<div> </div>
<div>1) Modifying Xen-guest config file, take a look at <a href="http://wiki.xensource.com/xenwiki/XenNetworking#head-4f6aecaa0342826a7259cd08948266093cca4365">http://wiki.xensource.com/xenwiki/XenNetworking#head-4f6aecaa0342826a7259cd08948266093cca4365
</a></div>
<div>2) Manually adding or deleting interfaces to the bridges via brctl, thus selecting witch peth is connected to which vif.</div>
<div> </div>
<div>hope this help</div>
<div> </div>
<div>Raul<br><br> </div>
<div><span class="gmail_quote">On 4/9/06, <b class="gmail_sendername">Mark A Heilpern</b> <<a href="mailto:mark@heilpern.com">mark@heilpern.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">After seeing what others with similar problems have posted, I've learned that my problem seems to be with Xen's pethX creation procedure... but I'm not sure how to convince Xen to do things just a little differently.
<br><br>As a recap, my system has two ethernet devices:<br>My lan: eth0, 192.168.2.X<br>The Internet: eth1<br><br>When I reboot and Xen has created its various interfaces, I get peth1 as a part of my xenbr0 device. This is a problem though since I need my guest machines to be tied to the lan, not the internet -- but there is no peth0 device to service this. I've tried swapping which card is which eth through mac assignment but this just caused a peth0 to be created (mapping again to my internet ethX device) and no peth1. I also tried swapping which device gets the lan address vs. my external address, and the pethX device being created is consistantly finding my internet device.
<br><br>How can I change the way pethX is created?<br><br>-------------------------<br>Original Message:<br>From: Mark A Heilpern <<a href="mailto:mark@heilpern.com">mark@heilpern.com</a>><br>To: <a href="mailto:fedora-xen@redhat.com">
fedora-xen@redhat.com</a><br>Date: Friday, April 7 2006 03:14 PM<br>Subject: Re: [Fedora-xen] Network problem during FC5 XEN Guest install<br>For what it's worth I'm having the exact same problem you are... no solution for me yet.
<br><br>In my case my dom0 has two physical ethernet interfaces and a Firestarter-managed firewall letting my local traffic (on eth0) NAT out to the internet (eth1), blocking most ports on eth1 from the outside world. I haven't explored enough to determine if either multiple eth's or the firewall are contributing towards my problem. I've failed both with DHCP in the guest as well as with a static IP for it. The IP I've used statically is
<a href="http://192.168.2.250">192.168.2.250</a> (where my eth0 device is <a href="http://192.168.2.1">192.168.2.1</a>).<br><br><br>Is there anywhere I can download a guest disk image pre-installed?<br><br><br><br><br>----- Original Message -----From: Raul Saura <
<a href="mailto:raul.saura@gmail.com">raul.saura@gmail.com</a>>To: <<a href="mailto:fedora-xen@redhat.com">fedora-xen@redhat.com</a>>Cc: Date: Friday, April 7 2006 02:20 PMSubject: [Fedora-xen] Network problem during FC5 XEN Guest installHello,
<br><br>I'm trying to create a xen-guest install using xenguest-install.py script, following the indications from <a href="http://fedoraproject.org/wiki/FedoraXenQuickstartFC5">http://fedoraproject.org/wiki/FedoraXenQuickstartFC5
</a><br>.<br>I've had to shrink mi xen0 domain to 128MB in order to allow guest to start install, otherwise I get the "The privileged domain did not balloon!" error-message.<br>I've exported the FC5 DVD through NFS from the xen0 domain itself hoping it will be visible from the guest during the install process.
<br><br><br>Now I'm in the first stage of the anaconda Installer and DHCP IP learning does not seems to work, in fact no network seems to be available from the guest, because when I manually configure an IP, the guest can not see the NFS export either...
<br><br><br>I've been tcpduming for a while, and I can not see any traffic from/to the guest. But in fact I don't even known if i should be seeing any traffic from the xen0 eth0 interface, should I?<br><br>Any help will be welcomed.
<br><br><br>Thanks a lot.<br><br>Raul.<br><br><br>--<br>Fedora-xen mailing list<br><a href="mailto:Fedora-xen@redhat.com">Fedora-xen@redhat.com</a><br><a href="https://www.redhat.com/mailman/listinfo/fedora-xen">https://www.redhat.com/mailman/listinfo/fedora-xen
</a><br><br>--<br>Fedora-xen mailing list<br><a href="mailto:Fedora-xen@redhat.com">Fedora-xen@redhat.com</a><br><a href="https://www.redhat.com/mailman/listinfo/fedora-xen">https://www.redhat.com/mailman/listinfo/fedora-xen
</a><br><br>--<br>Fedora-xen mailing list<br><a href="mailto:Fedora-xen@redhat.com">Fedora-xen@redhat.com</a><br><a href="https://www.redhat.com/mailman/listinfo/fedora-xen">https://www.redhat.com/mailman/listinfo/fedora-xen
</a><br></blockquote></div><br>