Fred: So, you can look can look closer at networking as you test this. Run a network analyzer such as wireshark, tshark, or similar on the dom0 when you ping the dom0. See if anything is going on. You should also be able to trace the virtual network card associated with the guest.
Other things to try: use strace on the domU when running some of the simple ping or other network commands. run commands like route, and ifconfig -a, and dmesg, and lspci, and lsmod, insmod <network module> on the guest to try to get some more intuition on that what it happening. Also look in more log files both on the guest and on dom0 /var/log/messages, /var/log/syslog, /var/log/xen/* Try reloading networking in the domU and watch dom0 log files. To me it doesn't make sense that networking works when it first boots and then doesn't on the second boot. Also, we really need to push on the latest kernels and packages, since those will be the ones that will be fixed, it is unlikely anybody will take the time to fix any of the old ones. I am soon going to focus my efforts on whatever is released for hardy, maybe that can get back ported. -- 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
