I went back and followed Todd Deshane's input above, reverting to revert to the earlier kernel (2.6.19-4-generic-amd64) for both my dom0 and domU. However, I am still experiencing the same problems as reported above with the latest kernel. After using "xen-create-image" to create the image and "xm create" the first time, the guest is created and networking works just fine..
However, if I do an "xm shutdown" on the newly created guest, followed by another "xm create" using the same guest configuration file, the same guest created again cannot access the network interfaces.. When attempting to do a simple ping, I get the following response: "connect: Network is unreachable" As the next step, I went back and reviewed the /var/log/xen log file generated when creating the xen image, and noticed the following lines of interest: Running hook 40-setup-networking /usr/lib/xen-tools/gutsy.d/40-setup-networking: 139: bcast: not found hook 40-setup-networking: done. Why does the networking error occur in the log file when generating the xen image? Why does guest correctly access the network the first time it is created via "xm create", but not after it is shutdown (via "xm shutdown") and subsequently recreated again via "xm create"? Is this a xen 3.1 problem, a xen-tools 3.1 problem, or perhaps both? Finally, in the interests of full disclosure, I have set the following in my xend-config.sxp: (network-script network-bridge) (vif-script vif-bridge) Please advise if I can assist in any further testing of this issue, or to provide any other supporting detail in helping resolve this problem. Thanks, -Fred- -- domU fails to get network connection https://bugs.launchpad.net/bugs/150805 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
