search for: nivedita

...recommended that they drop the other topics and contain it to only the first one (kernel interface) though. Does anyone want to bring these up at either one of the Xen events or the Virtualization BoF? (I think there will be an IOMMU BoF and a secure Xen BoF), info unknown at this point. thanks, Nivedita

...im pitch in on the state of his patches.. Chris? What's happening with the Xen patches? I know Rusty needed to farm out some of the work to get done before OLS - any volunteers? We'd like to put up a tasklist, if there isn't already one. Ditto a wiki page. Thoughts, folks? thanks, Nivedita

I recently noticed that after starting xend ethtool no longer work for my e1000 card. In my 2.X box which is a P4, ethtool is working after xend start. Same version of e1000 on both boxes. The unstable box is a Tyan 2462 SMP, FC4 dom0 The 2.X box is Dell P330 UP, Centos 4.1 domO Until xend start ethtool is fine, in both setups I am using the e1000 as eth0. Regards, Ted

Looks to me like the first series of patches should be OK to post now. I propose that: 001-apply-to-page-range.patch 001a-reboot-use-struct.patch 002-sync-bitops.patch 003-remove-ring0-assumptions.patch 004-abstract-asm.patch 005-cpuid-cleanup.patch unfix-fixmap.patch fixmap-bootparam.patch remove-read-hazard-from-cow.patch pte-clear-not-present.patch

Hi I would like to add some documentation to the xensource wiki. In particular I would like to add some notes on setting up firewalling on a Xen machine using a SuSE 9.3 dom0. (this is the Distribution I am familiar with) I can''t see an appropriate place linked off the front page to add this stuff. Also I can''t edit the front page itself to add a new catagory because it is

skb_copy_bits() can return an err, so have netif_be_start_xmit() crash informatively.. thanks, Nivedita _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...e the user (but this would need sanitizing xend to use the right params) or restore the original piece of code? It latter worked well before, you could set it in one place and have it be seen by script and xend. I had both in test, will send off whichever is desirable when I get in tmrw.. thanks, Nivedita _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I booted into X11 and have networking working and a kernel compile = running. SMP and PAE should be less than a day away. This completes = the proof of concept, I believe ;) I didn't cc LKML since I didn't want to spam them with graphics. Very = controversial graphics. Hopefully you appreciate the humor. Zach -------------- next part -------------- A non-text attachment was

...lem was solved by a reinstall of the native linux (RHEL4) with selecting all packages. I had initially chosen some packages and I believe hotplug support was left off (don''t know which package it belonged to. Regards - Padma -------------- Original message ---------------------- From: Nivedita Singhvi <niv@us.ibm.com> > pak333@comcast.net wrote: > > Hi, > > > > I have seen many posts regarding this but have not found the soultion. So > please cna someone shed some light on this > > Thanks > > - padma > > The usual reason is that the netw...

On Tuesday 02 August 2005 10:42, Xen patchbot -unstable wrote: > # HG changeset patch > # User smh22@firebug.cl.cam.ac.uk > # Node ID 59e76450e286240decceda23eca343ec4604124f > # Parent 48dea637aac96bcbabe788d036b52570520cc82e > Fixes. Sorry, but could we not make checkin comments like "Fixes."? It would just take a few more seconds to describe it in a complete

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

Hi, I have seen many posts regarding this but have not found the soultion. So please cna someone shed some light on this Thanks - padma I get this error when I do try to create a domU guest (xen 3.0.0, 2.6.12.6). The vif is set to vif = [ '' mac=aa:00:00:00:11, bridge=xenbr0'' ] and a "brctl show" shows xenbr0 8000,fefffffff interfaces vif0.0 peth0 Xend.log

Hi everyone, I''m doing some networking experiments over high BDP topologies. Right now the configuration is quite simple -- two Xen boxes connected via a dummynet router. The dummynet router is set to limit bandwidth to 500Mbps and simulate an RTT of 80ms. I''m using the following sysctl values: net.ipv4.tcp_rmem = 4096 87380 4194304 net.ipv4.tcp_wmem = 4096

hi, it would be extremely useful for me if someone with knowledge of how the current tools and drivers use Xenstore would be kind enough to update the Wiki with current information. I have been spending quite a lot of time trying to get my domU connected to a block device in dom0 using a home-brewed domain creation tool, and I am still at the ''Timeout connecting to device!''

Hi there! I was wondering what the general opinion on autotoolizing xen is? I am volunteering to do so, if there is interest in updating the build system to use autoconf, automake and/or libtool. Is one configure script for all of xen enough or do you want to be able to configure all/some tools separately? I know that Anthony is no fan of libtool... are there more reservations about some

I''m tracking performance on the machine I installed yesterday. mutt running on one Xen instance, accessing via imap to another instance, accessing via nfs the maildir in another instances, seems little laggy when moving up and down the message index list. Network latency seems low < 30ms on average. So I was tracking vmstat. On the mutt instances is seems reasonable: [nic@shell:~]

At OLS I gave a talk on some of the Xen scalability inhibitors, and one of these was writable page tables. We went over why the feature does not scale, but just as important, we found that the uniprocessor case does not provide any advantage either. These tests were done on x86_64, so I wanted to run the 1-way test on 32 bit to show the same problem. So, I have run with writable PTs and

Xen patchbot -unstable wrote: ># HG changeset patch ># User cl349@firebug.cl.cam.ac.uk ># Node ID 8fe8a99b1c2a6ea88624546ab625eaa0758e3a17 ># Parent e69cbfee4011da1648718f1f5cbe8dabb956e72a >New console transport and update xenconsoled. >Add a new console interface using a seperate shared page and event channel >instead of passing the console input/output over control

The attached patch to the qemu emulation of the pcnet hardware fixes several problems. It will now only read and write a transmit or receive descriptor once. It will correctly handle transmitting frames with more than two fragments. It will discard oversize frames instead of corrupting memory. I have tested all the changes I have made and even seen an improvement in receive performance from

...mukadam <nishants@marvell.com> Nishanth Aravamudan <nacc@us.ibm.com> Nishanth Menon <nm@ti.com> Nithin Nayak Sujir <nsujir@broadcom.com> Nitin A. Kamble <nitin.a.kamble@intel.com> Nitin Gupta <ngupta@vflare.org> Niu Yawei <yawei.niu@intel.com> Nivedita Singhvi <niv@us.ibm.com> Noam Camus <noamc@ezchip.com> Nobuhiro Iwamatsu <iwamatsu@nigauri.org> Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com> Norbert Preining <preining@logic.at> Octavian Moraru <octmoraru@gmail.com> Octavian Purdila <octavi...