From: user@example.net   
      
   Aragorn wrote:   
      
   > I currently haven't gotten very far yet.  In fact, I still am in that   
   > chroot'ed environment and I still have to configure and build a kernel, but   
   > unfortunately lots of other stuff has kept me busy these last few days.   
      
   That is life, always something coming in between.   
   As I noticed it goes quite painlessly to setup a basic environment on a pre   
   compiled distro, but then you loose most of the customizing. I think it took   
   me like a hour to setup Xen on CentOS, the main problem I had was how to   
   access the RPMs over http, until I figured out to use the external ip-number   
   of the host system and then everything went fine.   
   Something I did a bit later on was to install the Xen on it's own slices   
   instead of a image file, which seems to be the default setup, but I have to   
   say I don't like the image files, they tend to be slow and require more CPU   
   when doing file I/O.   
      
      
   > Now that I know you're interested in my "project" I will of course keep you   
   > posted and fill you on on what I have (or have not) come to accomplish. ;-)   
      
   I look forward for your posts and I will keep on trying to make some inputs,   
   which may sometimes not be that much worth.   
      
      
   > P.S.: It would seem that I was wrong in the post from which you quoted...   
   > As it turns out, the newer and more powerful Intel-based machines do indeed   
   > have an on-board IOMMU, but as is also the case for the regular memory   
   > controller, it's on the motherboard, contrary to AMD-based platforms, where   
   > the memory controller and IOMMU are part of the processor chip itself.   
   >   
   > Intel did however announce that their future line of processor chips will   
   > also have an on-chip memory controller, which means that they too are   
   > realizing the benefits of a ccNUMA architecture for the x86 platform.  As a   
   > sidenote to this, the upcoming 2.6.25 kernel will no longer even support a   
   > flat memory model as the sparse memory model has overtaken both the   
   > contiguous and flat models and seems to work equally well for NUMA and   
   > non-NUMA machines. ;-)   
      
   Ok, thats good to know, recently went to kernel 2.6.24 on all my machines   
   except the Sparc, which I haven't turned on for 6 month, and starting to think   
   of getting rid of it, it's too slow for me and too noisy even if I have   
   switched to more quite fans on the machine.   
      
   You know if there is plans of merge Xen into the kernel source or will it keep   
   on being a separated packages?   
      
      
   --   
      
      //Aho   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)