similar to: RE: RE: [Xen-ia64-devel] Paravirtualized xenlinux/ia64available

Yes, like real Linux/ia64, it is not possible to run the same Xenlinux bits both on ski and on real hardware. A different configuration and build is required. The config difference is the same as it was with the privified xenlinux... I think you did that successfully before (with privified xenlinux) so give that config file a try and if it doesn''t work, let me know. BTW, I think I know

I''ve just finished Xeno-HOWTO which contains a detailed list of instructions on how to setting up Xen and XenoLinux, from downloading Bitkeeper, compilation of Xen, XenoLinux, tools to configuration, start and stop of new domains. A complete version has just been pushed in xeno.bk and xeno-1.1.bk in our Laboratory. A partital version is already available in

Hi Xen people, I can read in the Xen 3.0 Roadmap that "A port to IA64 is making good progress". I have found nothing about IA-64 support in the "bk://xen.bkbits.net/xeno-unstable.bk" repository. Could you tell if an advanced version for IA-64 is available and where the source files can downloaded from ? Regards Jean-Paul Pigache

klibc integrated with the kernel can now be found at: http://linux-sam.bkbits.net Se the repository: klibc. For non-BK users the patches can be retreived using the following links: klibc on top of 2.6.8-rc2: http://linux-sam.bkbits.net:8080/klibc/gnupatch@41098c67CQHEC6lH2E3rfIXcnRW1RA kbuild adaptions to klibc: http://linux-sam.bkbits.net:8080/klibc/gnupatch@4109923a7O1XqfXw_V7JzAmet_AzbA

This seem to be a good timing taking up the integration of klibc in the kernel again. Based one klibc-0.152 and klibc.bkbits.net/2.5-klibc I will take a shot of it. I will focus on getting the library compiled (should be pretty straighforward). Next two steps are: 2) Adding minimum applications to the kernel (if any) 3) Support applications outside the kernel I will put my work on bkbits.net

Hi all. I have pushed my earlier announced kbuild improvements patch to: bk://linux-sam.bkbits.net/2.5-klibc First cset is the earlier posted cset, whit a few small modifications. One important change is that the usr/Makefile now uses *.a files in initramfs-y assignment. I realised that the purpose was to express what kinit were using / referring. Second cset is a trivial cset that just move

This patch implements a checker to detect instructions which should be paravirtualized instead of direct writing raw instruction. This patch does rough check so that it doesn't fully cover all cases, but it can detects most cases of paravirtualization breakage of hand written assembly codes. Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> Cc: "Luck, Tony"

This patch implements a checker to detect instructions which should be paravirtualized instead of direct writing raw instruction. This patch does rough check so that it doesn't fully cover all cases, but it can detects most cases of paravirtualization breakage of hand written assembly codes. Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> Cc: "Luck, Tony"

Hi, Greg - I have a 2.5.70 BK repository, with klibc integrated, at: bk://klibc.bkbits.net/2.5-klibc This repo has the following features: * Completely up-to-date w.r.t. klibc itself. * Kbuild sort of happy, but still needs an eyeball from Kai to figure out why it always rebuilds everything in usr/. * Supports both IP autoconfig and NFS root from initramfs.

Hello, I have attached a patch wich adds support for 4kb pages to xen 2.0 proper. (No changes were required from xen 2.0-beta. Apprently mixing xenolinux from one release and xen kernel from another release is a no-no. Other than that there were no problems. Thanks to Rupert Schlick for helping to nail it down. The "noacpi" parameter does not seem to be mandatory. Finally

It's now in sync with 2.5.71. bk://klibc.bkbits.net/2.5-klibc <b

Hi all, I'm a bit concerned about the following statement included in 2.6.0-test4: +For active users, you are better off using the klibc BitKeeper +repositories, at http://klibc.bkbits.net/ Since I refuse to use bk because I consider the anti-competition clause in the free bk license to (a) be abhorrent and (b) meaning that it's of at best questionable legality for me to use free BK,

I've updated the BK klibc tree to reflect all of the recent flurry of activity. Complete CVS change history is preserved. http://klibc.bkbits.net/klibc <b

Link below: http://www.osdl.org/cgi-bin/osdl_development_wiki.pl?Virtualization It's just a basic snapshot of current bits on list. Please update as you see useful. thanks, -chris -- Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net

Link below: http://www.osdl.org/cgi-bin/osdl_development_wiki.pl?Virtualization It's just a basic snapshot of current bits on list. Please update as you see useful. thanks, -chris -- Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net

If you only run released (rather than development) versions of rsync then you can skip this message. rsync's source tree has been converted from CVS to BitKeeper. This message contains brief instructions for people who want to track development or make contributions. I think it should take about 30-60 minutes to get started with BK. I hope you will agree that it is worthwhile. First

hi, lately i try to download xen from bitkeeper - bk://xen.bkbits.net/xen-2.0.bk (ought to be version 2.0); but encounter a probelm when build from source. it has error as follow. the env is cygwin, gcc 3.3.3 and make 3.80 how to slove it? i appreciate any suggestion. sinrecely. jason ===============ERROR BEG ============ ac_timer.c:44: warning: alignment of `ac_timers'' is greater than

Since I admin the gateway for a network of bandwidth-greedy machines, I figured that esfq with "hash src" would be a more fair allocation of bandwidth than sfq. Unfortunately, there didn''t seem to be a recent patch for 2.6, so I endeavored to build one. The three patches I made (described below) are available within the attached tar.bz2 or at: http://fatooh.org/esfq-2.6/ 1. I

import include/asm-ia64/xen/interface.h to introduce introduce definitions necessary for ia64/xen hypercalls. They are basic structures to communicate with xen hypervisor and will be used later. Cc: Robin Holt <holt at sgi.com> Cc: Jeremy Fitzhardinge <jeremy at goop.org> Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> Cc: "Luck, Tony" <tony.luck at

import include/asm-ia64/xen/interface.h to introduce introduce definitions necessary for ia64/xen hypercalls. They are basic structures to communicate with xen hypervisor and will be used later. Cc: Robin Holt <holt at sgi.com> Cc: Jeremy Fitzhardinge <jeremy at goop.org> Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> Cc: "Luck, Tony" <tony.luck at