similar to: [PATCH 2/4] [XMTEST] Network tests: 02_network_local_ping_pos

Some network test utilities for the library: Signed-off-by: Jim Dykman <dykman@us.ibm.com> Jim _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hao Yu Commercial Scale Out IBM T.J. Watson Research Center 1101 Kitchawan Rd/Route 134, Rm 36-019 Yorktown Heights, NY 10598-0218 914-945-1854, Email: yuh@us.ibm.com ----- Forwarded by Hao Yu/Watson/IBM on 10/31/2006 09:52 AM ----- Jimi

Hao Yu Commercial Scale Out IBM T.J. Watson Research Center 1101 Kitchawan Rd/Route 134, Rm 36-019 Yorktown Heights, NY 10598-0218 914-945-1854, Email: yuh@us.ibm.com ----- Forwarded by Hao Yu/Watson/IBM on 10/31/2006 09:52 AM ----- Jimi

Hallo @all, i can ping my domU maschine from dom0, but ssh/dns between dom0 and domU dosn''t work :-( here any tests: blackhat2 = dom0 (192.168.1.1) blackhat2web = domU (192.168.1.2) (ping from dom0 to dom0) blackhat2:~# ping -c1 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.074 ms (ping dom0 to domU)

Another checksum offload problem was reported on xen-users, when using a domU as a firewall: http://lists.xensource.com/archives/html/xen-users/2006-04/msg01150.html It also fails without VLANs. The path from dom0->domU with ip_summed==CHECKSUM_HW/proto_csum_blank==1 is broken. - skb_checksum_setup() assumes that a checksum will definitely be calculated in dev_queue_xmit(), but the

Thank you all for you replies! For anyone following the fedora xen quickstart guide here are the steps to follow to get your eth0 working. At rawhide mkdir /lib/modules/2.6.12-1.1411_FC4xen0 depmod -a At the domain0 (make sure rawhide is down) mount -o loop /root/fedora.img /mnt cd /mnt cp /etc/sysconfig/network-scripts/ifcfg-eth0 etc/sysconfig/network-scripts/ifcfg-eth0 cp

Hi I installed xen by following this link: http://www.howtoforge.com/virtualization-with-xen-on-debian-lenny-amd64 Dom0(debian) has two IP :174.x.x.79 , 67.x.x.32 gateway is 174.x.x.65 DomU(win2003) IP is :67.x.x.38 The problem is : 1.weird network issue in win2003(can not access the internet in win2003): A:weird ping time for 127.0.0.1 B:weird ping time for its own ip 67.x.x.38 C:timeout

Hi list, I''m looking for some help in getting my domU network aware. Currently I can run /etc/xen/scripts/network from dom0 to successfully create xen-br0. After I do this, dom0 can still access any network resource that it could before. However, when I start up a domU, it can only ping dom0; it fails to connect to any other ip. I don''t receive any sort of error message,

So, I have been running into network problems for a while on 4 boxes that I installed xen on so that some engineers have places to test code. This particular problem is happening on all 4 of these boxes. (although, it isn''t happening on an older box running xen from debian etch). What appears to be the problem is that traffic is getting dropped between the vif#.0 interface in dom0

Hello @all, thanks for all the helpfull answers in this mailing list. They helped me compiling a new kernel 2.6.10.11 with Xen 2.0.6 (my first one), setting up a dom0 with RAID, LVM and loop devices for domU, integrating a second network as xen-br1 (I''m calling the /etc/xen/scripts/network script from within /etc/init.d/xend to bring up / down the second bridge.) and bootstrapping

Hi everyone, I have some trouble with the network on a domu on a new host : I''ve made a bridge and configured it but when I start the domu, I can''t ping any network... seems like the bridge is not working :''( I''ve created the bridge directly in /etc/network/interface and I''m using Xen 3.0.3 on a debian etch, bellow are the xen packages installed on

Hello Xen folks, I have independently verified that this patch indeed fixes the issue (I posted a message about the issue over the summer: http://lists.xensource.com/archives/html/xen-devel/2005-08/msg00114.html). I used changeset 8911 of xen-unstable.hg. The patch as written expects kernel linux-2.6.16-rc2, but changeset 8911 uses kernel 2.6.16-rc4. I verified that the patch works with

BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px; } Dear All, I was trying to set up a virtual network with fc7 Dom0 and ubuntu 8 (Hardy) & Fedora 9 (etc) as DomU images on AMD Opetron 152 processor based machine. I was able to successfuly establish a virtual network using bridge connection Xen Network configuration. After that I tried to install cpufreq-utils on Dom0 which

In netfront, the current driver reserves pools of grant refs for the tx and rx paths, each big enough to satisfy one virtual nic. With more than one nic active you will run out. Both the tx and rx path will BUG() when you do. This patch creates separate tx and rx ref pools for each interface. Signed-off-by: Jim Dykman <dykman@us.ibm.com> Jim

This patch fixes the root cause of bug 183: per-interface transaction ids are being used to index global tables. Signed-off-by: Jim Dykman <dykman@us.ibm.com> Jim _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hello, I have the following Xen 3.0.2-2 related problem: A host system with Centos 4.4 in the dom0, guest systems are Fedora Core 5 (images from jailtime.org) mounted on LVM. Networking on the domUs is not working, Iptables in the guests are not working either. Each Guest system should have at least 1 dedicated public IP assigned to it, but should have the capability to have more than 1

changeset: 11278:8273f730371b tag: tip user: Ian Campbell <ian.campbell@xensource.com> date: Tue Aug 29 06:23:11 2006 +0100 summary: Fix definition of LINUX_VER so that doesn''t pickup LINUX_VER3 Hardware: x460 ******************** x86_32(no PAE): *************************** * dom0: SLES10 GM * dom0 boots fine * xend starts without problem --- Linux

changeset: 10151:ad33b3882867 tag: tip user: cl349@firebug.cl.cam.ac.uk date: Wed May 24 13:41:47 2006 +0100 summary: Fix IDE CD-drive PIO mode. Hardware: x460 ******************** x86_32(no PAE): *************************** * dom0: SLES9 SP2 * dom0 boots fine * xend starts without problem --- Linux HVM domain status: --- * Xm-test completes. * Able to boot

changeset: 10910:aa1ab056bfbf tag: tip user: emellor@leeni.uk.xensource.com date: Wed Aug 2 11:42:38 2006 +0100 summary: Clarify the use of vcpu-set. Closes bug #686. Hardware: x460 ******************** x86_32(no PAE): *************************** * dom0: SLES9 SP2 * dom0 boots fine * xend starts without problem --- Linux HVM domain status: --- * Xm-test

Hi folks, I read quite some posts about "Destination host unreachable" problems before, but none could help me to solve my issue. So here we go: This is what I am using: SUSE Linux Enterprise Desktop 10 SP1 - Current with all updates Network configuration of my dom0: foobar:~ # ip a 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd