http://news.gmane.org/find-root.php?message_id=%3cfe9771a80708170311o432fcd35jab5d7e16354c6e1%40mail.gmail.com%3e shows that other users are having the same problem. It also provides a solution, which is referred from the Xen Users Mailing List.
>From the Xen Users Mailing List: (http://lists.xensource.com/archives/html/xen- users/2006-05/msg00818.html) > - That is one bug or resource? It will be corrected? It's a bug. And shortly before 3.0.2 was relesed there were some attempts to fix it. It is intended as an optimisztion, but it failed for some (or IMHO most real world) setups. A solution: "I can confirm that disabling tx offloading fixes the problem! For gutsy ( in our case ), just add the following line at the bottom of your /etc/network/interfaces file: up ethtool -K eth0 tx off repeat for every interface ( i only have 1 :) )" Hopes this solves the problem temporarely and I for one hope that a fixed version of Xen will be in Gutsy, otherwise the whole purpose of having Xen in Gutsy is quite defeated. -- Unable to connect to network from Xen Linux https://bugs.launchpad.net/bugs/71362 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
