similar to: [PATCH 1/4] [XMTEST] Network tests: Network test library/utilities

Single domU, ping loopback and the local eth0. 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

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 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

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

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

The attached patches enable the xenstore client utilities (xenstore-read/write and friends) to be built statically and against uclibc. This is useful for utility domains where a small userspace is desired. Both static building with glibc and linking with uclibc seem to have problems with threading and so the static version of the library is built without thread support. This is OK since none of

Hi, This patch and the two that will follow add a new network infrastructure to xm-test. The goal is to make writing tests with networking easy. The patches add a new XenDevice class and NetConfig class. The XenDevice and the XenNetDevice subclass represent devices in xm-test and are linked to the XenDomains. The NetConfig class manages xm-test''s network configuration. The patches make

I was cleaning out old sandboxes on my machine and realized that the fix for bug 143 was not in the tree yet. Jon Mason posted a patch, with no negative feedback: http://lists.xensource.com/archives/html/xen-devel/2006-02/msg00162.html The bug originator tested the patch successfully on -rc4: http://lists.xensource.com/archives/html/xen-devel/2006-02/msg00763.html I''ve retested on

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, In order to research the feasibility of moving onto *nix based systems I am currently testing Windows-only applications under WINE 1.1.8 on Mandriva Free 2009. The application I am currently testing is Raxco's DameWare NT Utilities (including DameWare Mini Remote Control), latest version as available after registering. I have found that there is an AppDB entry for DameWare stating that

Today I experienced a hanging dom0 and domU. Applications that tried to access /proc, such as ps, ifconfig, lvdisplay, mdadm all hung after displaying between one and ten lines of output. ''free'' worked and didn''t output anything weird. Apache was running in domU and also didn''t respond. This occurred in both dom0 as well as domU. After some time googling and

The following patch allows the network tests to pass with hvm support enabled. More specifically: 02_network_local_ping_pos.py REASON: ping loopback failed for size 65507. ping eth0 failed for size 65507. (but all other size pings work) 05_network_dom0_ping_pos.py REASON: Ping to dom0 failed for size 65507. (but all other size pings work) 11_network_domU_ping_pos.py passes 100% (even the large

Add two new functions: xenbus_for_each_backend and xenbus_for_each_frontend to iterate the backend and frontend buses respectively and apply the supplied test to each one. Signed-off-by: Kieran Mansley <kmansley@solarflare.com> _______________________________________________ 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

"Old" tested version had not actually been tested; therefore in this flight we test it, rather than a new candidate. The baseline, if any, is the most recent actually tested revision. flight 20079 qemu-upstream-4.3-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/20079/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking:

This patch adds a test that tries to create a domain with only 16MB of RAM. It verifies that the domain is created and that the console works. Right now this test fails for me: the domain just dies immediately with no indication of why, or with any useful console data. Should we put a sanity check on xm''s create and mem-set commands that prevent the user from doing something we know

"Old" tested version had not actually been tested; therefore in this flight we test it, rather than a new candidate. The baseline, if any, is the most recent actually tested revision. flight 20078 qemu-upstream-4.2-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/20078/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking:

This patch (against unstable) makes sure that the skel/etc/init.d/rcS file is executable before building the final ramdisk image. This should fix the problem some people are having with their ramdisk builds. -- Dan Smith IBM Linux Technology Center Open Hypervisor Team email: danms@us.ibm.com _______________________________________________ Xen-devel mailing list

Hi, i have some problems with xen-3.0.1 and the network-bridge script. After ''/etc/init.d/xend start'' or ''/etc/xen/script/network-bridge start'' everything works perfect (as well as the domU''s network) - but only for a few seconds (~20s). After that the network seems to crash - no outgoing or incoming connection possible. I have read a forum