Hi everybody ! I haved use Xen 2.06 with my two Domains from some months and all working pretty good ! Now i have remove Xen 2.06 and put Xen 3 (unstable.hg) , i haved build this morning with make world and make install. My Dom0 and DomU starts successfuly, but on my Dom0 i haved network-bridge defunct when i type ps -aux, so you imagne that in DomU netwrok wan''t work :( I see network vif1.1 start whant DOmU start ... I use Debian SID updated today (18/10/05) with latest Xen mercurial ... Would you like more information to correct these issue ? Thanks Michael _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Tue, Oct 18, 2005 at 09:48:07AM -0400, Michael Lessard wrote:> Hi everybody ! > > I haved use Xen 2.06 with my two Domains from some months and all working > pretty good ! Now i have remove Xen 2.06 and put Xen 3 (unstable.hg) , i > haved build this morning with make world and make install. My Dom0 and > DomU starts successfuly, but on my Dom0 i haved network-bridge defunct > when i type ps -aux, so you imagne that in DomU netwrok wan''t work :(The defunct network-bridge is not a problem. There are other problems with networking, and I''ll let other people answer, because I don''t have a handle on them at the moment, but the defunct network-bridge process isn''t a problem in and of itself. Ewan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 10/18/05, Ewan Mellor <ewan@xensource.com> wrote:> > On Tue, Oct 18, 2005 at 09:48:07AM -0400, Michael Lessard wrote: > > > Hi everybody ! > > > > I haved use Xen 2.06 with my two Domains from some months and all > working > > pretty good ! Now i have remove Xen 2.06 and put Xen 3 (unstable.hg) , i > > haved build this morning with make world and make install. My Dom0 and > > DomU starts successfuly, but on my Dom0 i haved network-bridge defunct > > when i type ps -aux, so you imagne that in DomU netwrok wan''t work :( > > The defunct network-bridge is not a problem. There are other problems with > networking, and I''ll let other people answer, because I don''t have a > handle on > them at the moment, but the defunct network-bridge process isn''t a problem > in > and of itself. > > Ewan. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >If i use brctl to create bridge like in the script, # brctl addif xen-testbridge eth0 error on eth0 but if i use : # brctl addbr xen-testbridge # brctl addif xen-testbridge eth0 no error reported ... But i thinkg to make it work with Xen, i need other things... _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 10/18/05, Michael Lessard <michael.lessard@gmail.com> wrote:> > > > On 10/18/05, Ewan Mellor <ewan@xensource.com> wrote: > > > > On Tue, Oct 18, 2005 at 09:48:07AM -0400, Michael Lessard wrote: > > > > > Hi everybody ! > > > > > > I haved use Xen 2.06 with my two Domains from some months and all > > working > > > pretty good ! Now i have remove Xen 2.06 and put Xen 3 (unstable.hg) , > > i > > > haved build this morning with make world and make install. My Dom0 and > > > DomU starts successfuly, but on my Dom0 i haved network-bridge defunct > > > when i type ps -aux, so you imagne that in DomU netwrok wan''t work :( > > > > The defunct network-bridge is not a problem. There are other problems > > with > > networking, and I''ll let other people answer, because I don''t have a > > handle on > > them at the moment, but the defunct network-bridge process isn''t a > > problem in > > and of itself. > > > > Ewan. > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > > > If i use brctl to create bridge like in the script, > # brctl addif xen-testbridge eth0 > error on eth0 > > but if i use : > # brctl addbr xen-testbridge > # brctl addif xen-testbridge eth0 > no error reported ... > > But i thinkg to make it work with Xen, i need other things... > > > >With latest mercurial source, network-bridge defunct is now ok ;) But i still could not ping my Dom0 for DomU ... My setup : 2 Network Carfs on Debian Sid for both of my domains (Dom0 and DomU) 1 network cards (eth0) for my DomU, the config for network cards on Dom0 is : iface eth0 inet manual up /sbin/ifconfig eth0 up When i start DomU, i see appear vif1.0 , when i ping Dom0 from Dom0 i see only RX bytes growth On Dom0 , i have do echo "1" > /proc/sys/net/ipv4/ip_forward and iptables -P FORWARD ACCEPT My xen config for DomU : kernel = "/boot/vmlinuz-2.6.12-xenU" memory = 200 name = "Albert" nics=1 vif = [ ''mac=aa:00:00:00:00:11, bridge=xenbr0'' ] disk = [ ''phy:/dev/hdc3,hdc3,w'', ''phy:/dev/hdc5,hdc5,w'', ''phy:/dev/hdc1,hdc1,w'' ] root = "/dev/hdc3 ro" I have try with and without mac address specified ... What''s wrong with my setup ? thanks Michael _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Tue, Oct 25, 2005 at 03:49:09PM -0400, Michael Lessard wrote:> My setup : > 2 Network Carfs on Debian Sid for both of my domains (Dom0 and DomU) > 1 network cards (eth0) for my DomU, the config for network cards on Dom0 > is : > iface eth0 inet manual > up /sbin/ifconfig eth0 up > > When i start DomU, i see appear vif1.0 , when i ping Dom0 from Dom0 i see > only RX bytes growth > > On Dom0 , i have do echo "1" > /proc/sys/net/ipv4/ip_forward and iptables > -P FORWARD ACCEPT > > My xen config for DomU : > kernel = "/boot/vmlinuz-2.6.12-xenU" > memory = 200 > name = "Albert" > nics=1 > vif = [ ''mac=aa:00:00:00:00:11, bridge=xenbr0'' ] > disk = [ ''phy:/dev/hdc3,hdc3,w'', ''phy:/dev/hdc5,hdc5,w'', > ''phy:/dev/hdc1,hdc1,w'' ] > root = "/dev/hdc3 ro" > > I have try with and without mac address specified ... > What''s wrong with my setup ?The network-bridge script is for multiplexing each domain''s packets onto a single network interface, through a bridge. If you want to have one card dedicated to dom0, and one dedicated to domU, then you don''t want to use the network-bridge configuration at all. I think what you want to use is network-route / vif-route. Edit your xend-config.sxp to set (network-script network-route) (vif-script vif-route) The intention is to have dom0 route traffic for your domU from eth1 to vif1.0, and vice versa. You''re going to need to have the two cards on different subnets for this to work using the standard scripts, though I guess that''s what you''re doing already. These scripts haven''t had a lot of testing, and I''m not sure they are even the right thing for you, so you may have to do some hacking to get the right result. Let us know how you get on. Ewan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 10/26/05, Ewan Mellor <ewan@xensource.com> wrote:> > On Tue, Oct 25, 2005 at 03:49:09PM -0400, Michael Lessard wrote: > > > My setup : > > 2 Network Carfs on Debian Sid for both of my domains (Dom0 and DomU) > > 1 network cards (eth0) for my DomU, the config for network cards on Dom0 > > is : > > iface eth0 inet manual > > up /sbin/ifconfig eth0 up > > > > When i start DomU, i see appear vif1.0 , when i ping Dom0 from Dom0 i > see > > only RX bytes growth > > > > On Dom0 , i have do echo "1" > /proc/sys/net/ipv4/ip_forward and > iptables > > -P FORWARD ACCEPT > > > > My xen config for DomU : > > kernel = "/boot/vmlinuz-2.6.12-xenU" > > memory = 200 > > name = "Albert" > > nics=1 > > vif = [ ''mac=aa:00:00:00:00:11, bridge=xenbr0'' ] > > disk = [ ''phy:/dev/hdc3,hdc3,w'', ''phy:/dev/hdc5,hdc5,w'', > > ''phy:/dev/hdc1,hdc1,w'' ] > > root = "/dev/hdc3 ro" > > > > I have try with and without mac address specified ... > > What''s wrong with my setup ? > > The network-bridge script is for multiplexing each domain''s packets onto a > single network interface, through a bridge. If you want to have one card > dedicated to dom0, and one dedicated to domU, then you don''t want to use > the > network-bridge configuration at all. > > I think what you want to use is network-route / vif-route. Edit your > xend-config.sxp to set > > (network-script network-route) > (vif-script vif-route) > > The intention is to have dom0 route traffic for your domU from eth1 to > vif1.0, > and vice versa. You''re going to need to have the two cards on different > subnets for this to work using the standard scripts, though I guess that''s > what you''re doing already. > > These scripts haven''t had a lot of testing, and I''m not sure they are even > the > right thing for you, so you may have to do some hacking to get the right > result. Let us know how you get on. > > Ewan. >What i modigy to xend-config.sxp (network-script network-route) (vif-script vif-route) #(network-script network-bridge) #(vif-bridge xenbr0) #(vif-script vif-bridge) I restart Xend and restart my DomU ... i still couldn''t ping dom0 from DomU _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel