I agree with the affirmation that this isn't a Hypervisor or xen-3.2 bug. I have tested Hardy Kernel linux-2.6.24 with "Hypervisor" and "Tools" from original xen-3.2.0.tar.gz and I got the same network problem with hypervisor/tools compiled from source, so, this isn't a xen-3.2 bug. Ah, and I have purged xen-hypervisor-3.2 and xen-utils-3.2 before doing "make install-hypervisor;make install-tools", of course.
And if the networking works with other kernels like 2.6.22 from Gutsy or even 2.6.18.8-xen from xen.org, It's clean to me that there is a incompatible stuff with the Hardy Kernel. And resting only 8 days to release Hardy, /etc/init.d/xendomains has horrible, primary errors! Vide: https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/216761 .. I'm feeling fear... fear... what more we can expect!? Maybe forgetting about XEN and joining KVM?! The options are all over the table. -- networking not working https://bugs.launchpad.net/bugs/204010 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
