PDA

View Full Version : xen bridged networking fails after a few minutes


lax
7th March 2006, 05:05 PM
I am trying to use xen hypervisor/client install on an x86_64.
The hypervisor portion installs and runs fine ... except that the networking dies after a while.

peth0 timeout.

I tried 2 other another network cards to be sure. still failed.
I also used the hardware without xen hypervisor - no problems whatsoever.

The symptom, again, is after a few minutes of network usage, the networking stops and peth0 gives timeouts.

This basically prevents me to install a guest xen client ,or even rsync large amount of files, or run yum to the end.

What list should I read? fedora or xen? Where do I susbscribe to those lists?

Thanks

lax
7th March 2006, 05:06 PM
Has anyone successfully installed and run an x86_64 xen hypervisor/guest setup? Any suggestions?

Thanks

explainer
19th June 2007, 11:13 PM

I have installed Xen on FC7 (64 bit) and have created both a Windows 2000 and an Ubuntu 7.04 guest OSes. The host is a dual core AMD64 system with 4GB RAM and 300GB hard disk. The guests are 32-bit OSes. On the guest OS I have built, all failed to set up the network correctly. The linux guest does not even list the network hardware, so it must not think it is there. The host OS connects with the network normally, using DHCP to my router.

I would like to use a bridged network so that my guests are peers on my local lan, but the networking problems I have encountered may cause me to abandon Xen and go with VMware.

If anyone has a bridged configuration for Xen on FC7-64, I would very much appreciate getting info about your solution.

cr4ck3r
23rd June 2007, 03:02 PM
I don't use XEN, but the KVM come with F7, I had the same problem with you. The guest OS can dig google.com, but cannot connect to the internet, after enable IP forwarding in the host, everything runs fine now. There's is a bug raised against this (I'm not remember the bug id)
To enable IP forwarding:
echo "1" > /proc/sys/net/ipv4/ip_forward
Or edit the file /etc/sysctl.conf and set net.ipv4.ip_forwarding = 1
Hope this may help.