I have a domU set up as a nat router/dhcp server and another domU on the same box that is used as a test client. The test domU gets its DHCP address from the dhcp server but other than that no traffic between hosts is acknowledged by the other, not even a single, diminuitive packet. The OS''s used are all ubuntu server. Traffic can get in and out of the domU server just fine except traffic that is intended for the client. Where did I go wrong? What higher force saw fit to punish me in this punitive manner? Will I be able to get a date this Friday? These are questions we must all confront sometime in our lives. UPDATE: Just before sending this email I noticed that traffic between the two domUs starts flowing as expected only after I ping the client from the server, however I''m still mystified as to what is really going on. Justin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Aug 03, 2006 at 04:39:47PM -0600, Justin R Findlay wrote:> I have a domU set up as a nat router/dhcp server and another domU on the > same box that is used as a test client. The test domU gets its DHCP > address from the dhcp server but other than that no traffic between > hosts is acknowledged by the other, not even a single, diminuitive > packet. The OS''s used are all ubuntu server. Traffic can get in and > out of the domU server just fine except traffic that is intended for the > client. > > Where did I go wrong? What higher force saw fit to punish me in this > punitive manner?My son, you have committed some sins in a former life. Now you must pay penitence. $100 will do ;) Brian Will I be able to get a date this Friday? These are> questions we must all confront sometime in our lives. > > UPDATE: Just before sending this email I noticed that traffic between > the two domUs starts flowing as expected only after I ping the client > from the server, however I''m still mystified as to what is really going > on. > > > Justin > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-- Powered by Suse Linux 9.2 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 8/3/06, Justin R Findlay <justin@jfindlay.us> wrote:> > UPDATE: Just before sending this email I noticed that traffic between > the two domUs starts flowing as expected only after I ping the client > from the server, however I''m still mystified as to what is really going > on.I''m working with Justin on this and wanted to add a few details. As he said, if you try to ping the client DomU from the gateway/firewall/router server DomU, then (after 5 or 6 seconds) the traffic will start flowing. Only *after* doing this can the client DomU then ping the gateway (or beyond). I''m 99.9% sure that the networking is setup correctly and *should* be working. I believe it''s a Xen or NIC kernel module problem. We are testing a setup like it and it *seems* to work well for us on different hardware. This box is a Dell PowerEdge with Broadcom chips (e1000). Ever heard of this type of behavior? Any ideas? Thanks, Gabe P.S. Additional info: It''s running Ubuntu 6.06 LTS Server (updated) with the official Xen 3.0.2kernel. # lspci | grep Ether Intel Corporation 82544EI Gigabit Ethernet Controller (Copper) (rev 02) Intel Corporation 82544EI Gigabit Ethernet Controller (Copper) (rev 02) P.P.S. D''oh! I just noticed all of these dropped packets shown below ( vif0.0, vif12.0, vif12.1, vif12.2, vif13.0). Now I have to figure out what that means. peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:89084 errors:0 dropped:0 overruns:0 frame:0 TX packets:110727 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:24713772 (23.5 MiB) TX bytes:18362931 (17.5 MiB) Base address:0xdce0 Memory:feb60000-feb80000 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:79852 errors:0 dropped:0 overruns:0 frame:0 TX packets:60698 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:13187315 (12.5 MiB) TX bytes:10060245 (9.5 MiB) vif12.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3856 errors:0 dropped:0 overruns:0 frame:0 TX packets:5290 errors:0 dropped:224 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:471277 (460.2 KiB) TX bytes:1723434 (1.6 MiB) vif12.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1030 errors:0 dropped:0 overruns:0 frame:0 TX packets:1817 errors:0 dropped:223 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1230197 (1.1 MiB) TX bytes:132427 (129.3 KiB) vif12.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:1484 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif13.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4850 errors:0 dropped:0 overruns:0 frame:0 TX packets:2441 errors:0 dropped:97 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:842701 (822.9 KiB) TX bytes:1314526 (1.2 MiB) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4470 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:202946 (198.1 KiB) TX bytes:468 (468.0 b) -- Gabriel Gunderson http://gundy.org _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Can you post the contents of /etc/network/interfaces from dom-0 on the machine having the problems? Thanks - Tim On Fri, 2006-08-04 at 11:17 -0600, Gabriel Gunderson wrote:> On 8/3/06, Justin R Findlay <justin@jfindlay.us> wrote: > UPDATE: Just before sending this email I noticed that traffic > between > the two domUs starts flowing as expected only after I ping the > client > from the server, however I''m still mystified as to what is > really going > on. > > I''m working with Justin on this and wanted to add a few details. As > he said, if you try to ping the client DomU from the > gateway/firewall/router server DomU, then (after 5 or 6 seconds) the > traffic will start flowing. Only *after* doing this can the client > DomU then ping the gateway (or beyond). I''m 99.9% sure that the > networking is setup correctly and *should* be working. > > I believe it''s a Xen or NIC kernel module problem. We are testing a > setup like it and it *seems* to work well for us on different > hardware. This box is a Dell PowerEdge with Broadcom chips (e1000). > Ever heard of this type of behavior? Any ideas? > > Thanks, > Gabe > > P.S. Additional info: > > It''s running Ubuntu 6.06 LTS Server (updated) with the official Xen > 3.0.2 kernel. > > # lspci | grep Ether > Intel Corporation 82544EI Gigabit Ethernet Controller (Copper) (rev > 02) > Intel Corporation 82544EI Gigabit Ethernet Controller (Copper) (rev > 02) > > P.P.S. D''oh! I just noticed all of these dropped packets shown below > (vif0.0, vif12.0, vif12.1, vif12.2, vif13.0). Now I have to figure > out what that means. > > peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 > RX packets:89084 errors:0 dropped:0 overruns:0 frame:0 > TX packets:110727 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:24713772 (23.5 MiB) TX bytes:18362931 (17.5 MiB) > Base address:0xdce0 Memory:feb60000-feb80000 > > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:79852 errors:0 dropped:0 overruns:0 frame:0 > TX packets:60698 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:13187315 (12.5 MiB) TX bytes:10060245 (9.5 MiB) > > vif12.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:3856 errors:0 dropped:0 overruns:0 frame:0 > TX packets:5290 errors:0 dropped:224 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:471277 (460.2 KiB) TX bytes:1723434 (1.6 MiB) > > vif12.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:1030 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1817 errors:0 dropped:223 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:1230197 (1.1 MiB) TX bytes:132427 (129.3 KiB) > > vif12.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:1484 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > vif13.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:4850 errors:0 dropped:0 overruns:0 frame:0 > TX packets:2441 errors:0 dropped:97 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:842701 (822.9 KiB) TX bytes:1314526 (1.2 MiB) > > xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:4470 errors:0 dropped:0 overruns:0 frame:0 > TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:202946 (198.1 KiB) TX bytes:468 (468.0 b) > > > -- > Gabriel Gunderson > http://gundy.org > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sat, Aug 05, 2006 at 09:53:57AM +0800, Tim Post wrote:> Can you post the contents of /etc/network/interfaces from dom-0 on the > machine having the problems?$ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet static address 11.22.33.130 netmask 255.255.255.123 network 11.22.33.123 broadcast 11.22.33.255 gateway 11.22.33.124 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 123.21.0.1 This may or may not be related: http://lists.us.dell.com/pipermail/linux-poweredge/2006-August/026705.html Justin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Arsen Hayrapetyan
2006-Aug-06 15:40 UTC
[Xen-users] Error: Device 2049 (vbd) could not be connected. Backend device not found.
Hello, I am getting the following error when trying to start domU with ''xm -c /etc/xen/xmdefconfig'': =====================================================Error: Device 2049 (vbd) could not be connected. Backend device not found. ===================================================== My /etc/xen/xmdefconfig contains the following line: =====================================================disk = [''phy:/dev/vg/compnode,sda1,w'',''phy:/dev/vg/compswap,hda3,w'',''phy:/dev/vg/modules,sda2,r''] ===================================================== When I do ''lvscan'', I get the following: ===================================================== inactive ''/dev/vg/compnode'' [14.00 GB] inherit inactive ''/dev/vg/compswap'' [1.00 GB] inherit inactive ''/dev/vg/modules'' [100.00 MB] inherit ===================================================== And also one strange thing... Though ''xm'' is giving the error above, when I run ''xm list'' it shows the domain started, but paused: ======================================================Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 219 1 r----- 772.7 compnode 6 512 1 --p--- 0.0 ====================================================== If now I doing ''xm console 6'', it stucks... If I do ''xm unpause 6'', it unpauses: =====================================================Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 219 1 r----- 783.0 compnode 6 512 1 ------ 1.3 ===================================================== But after few seconds I see the compnode, having ID=7 ! And finally it disappears: #> xm list =====================================================Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 219 1 r----- 788.5 ===================================================== Can anybody explain what is going on here? Thanks in advance, Arsen. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Tim Post
2006-Aug-06 16:20 UTC
Re: [Xen-users] Error: Device 2049 (vbd) could not be connected. Backend device not found.
On Sun, 2006-08-06 at 17:40 +0200, Arsen Hayrapetyan wrote:> disk > [''phy:/dev/vg/compnode,sda1,w'',''phy:/dev/vg/compswap,hda3,w'',''phy:/dev/vg/modules,sda2,r'']wondering why you have sda1 sda2 and hda3 , since obviously its using 3 partitions from an lv volume group on the same sata (or scsi) drive. Is that a typo or do you have some kind of odd raid setup also? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 8/4/06, Gabriel Gunderson <ggundy@gmail.com> wrote:> > On 8/3/06, Justin R Findlay <justin@jfindlay.us> wrote: > > > UPDATE: Just before sending this email I noticed that traffic between > > the two domUs starts flowing as expected only after I ping the client > > from the server, however I''m still mystified as to what is really going > > on. > > > I''m working with Justin on this and wanted to add a few details. As he > said, if you try to ping the client DomU from the gateway/firewall/router > server DomU, then (after 5 or 6 seconds) the traffic will start flowing. > Only *after* doing this can the client DomU then ping the gateway (or > beyond). I''m 99.9% sure that the networking is setup correctly and > *should* be working. > > I believe it''s a Xen or NIC kernel module problem. We are testing a setup > like it and it *seems* to work well for us on different hardware. This box > is a Dell PowerEdge with Broadcom chips (e1000). Ever heard of this type of > behavior? Any ideas? >I just wanted to update anyone who might be wondering about this problem. We recreated this setup on different hardware and it still does the same thing. So, it must be in the software. Has anyone seen this kind of thing before? Any ideas about what might be wrong? Thanks again. -- Gabriel Gunderson http://gundy.org _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users