Hi I have been searching for a howto get iptables working in my DomU. I got it working in my Dom0. basicly I have tracked it down to the fact that a "net" dir is missing in the Domu /lib/modules/2.6.11.10-XenU/kernel. How do you compile the DomU kernel ? to support iptables. Thanks Andrew _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Andrew Turnbull wrote:>Hi > >I have been searching for a howto get iptables working in my DomU. > >I got it working in my Dom0. > >basicly I have tracked it down to the fact that a "net" dir is missing >in the Domu /lib/modules/2.6.11.10-XenU/kernel. > >How do you compile the DomU kernel ? to support iptables. > >Thanks > >Andrew > >_______________________________________________ >Xen-users mailing list >Xen-users@lists.xensource.com >http://lists.xensource.com/xen-users > >Hi, I tried a little bit with loading it as a module but then I choose to bind it directly into the kernel and that works perfect for me. (cd /usr/src/xen*/*xenU/;make ARCH=xen menuconfig -> M -> *;cd ..;make kernels) If anyone acctually was able to load it as a module I''m interested in. Frieder ''cfreak'' Kundel (sorry for any mistakes - didn''t sleep much) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 05/07/05, Frieder Kundel <cfreak@ckras.com> wrote:> Andrew Turnbull wrote: > > >Hi > > > >I have been searching for a howto get iptables working in my DomU. > > > >I got it working in my Dom0. > > > >basicly I have tracked it down to the fact that a "net" dir is missing > >in the Domu /lib/modules/2.6.11.10-XenU/kernel. > > > >How do you compile the DomU kernel ? to support iptables. > > > >Thanks > > > >Andrew > > > >_______________________________________________ > >Xen-users mailing list > >Xen-users@lists.xensource.com > >http://lists.xensource.com/xen-users > > > > > Hi, > > I tried a little bit with loading it as a module but then I choose to > bind it directly into the kernel and that works perfect for me. > (cd /usr/src/xen*/*xenU/;make ARCH=xen menuconfig -> M -> *;cd ..;make > kernels) > > If anyone acctually was able to load it as a module I''m interested in. > > Frieder ''cfreak'' Kundel > > (sorry for any mistakes - didn''t sleep much) > >Hi there Sorry really rookie question, but all I have is the Xen-2.0 dir I dont have the source xen kernel anywhere at least not the domU. where do I get that from ? Thanks _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Andrew Turnbull wrote:>Hi there > >Sorry really rookie question, but all I have is the Xen-2.0 dir I dont >have the source xen kernel anywhere at least not the domU. > >where do I get that from ? > > >If you get the installer from http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads.html, it will be UNDER the xen-2.0 dir. Something like xen-2.0/linux-2.6.11-xenU. As for getting modules, you should copy /lib/modules/2.6.11.10-xenU/ (assuming you use Xen-2.0.6) from you dom-0 (e.g. physical host) to your dom-U filesystem. Personally I prefer Frieder''s way, compile everything that I need in dom-U built-in into the kernel, not as modules. I also use symbolic links to specify the kernel for domU, e.g. something like this on a domain''s config file : kernel="/etc/xen/kernel/linux" and /etc/xen/kernel/linux is a symbolic link to linux-2.6.11-xenU-HS20 (I use my own dom-U kernel). That way a kernel (or Xen) upgrade is simply a matter of changing the symlink in dom0 and rebooting domU as necessary, without having to touch domU''s filesystems. Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Andrew Turnbull wrote:>Hi there > >Sorry really rookie question, but all I have is the Xen-2.0 dir I dont >have the source xen kernel anywhere at least not the domU. > >where do I get that from ? > > >If you get the installer from http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads.html, it will be UNDER the xen-2.0 dir. Something like xen-2.0/linux-2.6.11-xenU. As for getting modules, you should copy /lib/modules/2.6.11.10-xenU/ (assuming you use Xen-2.0.6) from you dom-0 (e.g. physical host) to your dom-U filesystem. Personally I prefer Frieder''s way, compile everything that I need in dom-U built-in into the kernel, not as modules. I also use symbolic links to specify the kernel for domU, e.g. something like this on a domain''s config file : kernel="/etc/xen/kernel/linux" and /etc/xen/kernel/linux is a symbolic link to linux-2.6.11-xenU-HS20 (I use my own dom-U kernel). That way a kernel (or Xen) upgrade is simply a matter of changing the symlink in dom0 and rebooting domU as necessary, without having to touch domU''s filesystems. Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 05/07/05, Fajar A. Nugraha <fajar@telkom.net.id> wrote:> Andrew Turnbull wrote: > > >Hi there > > > >Sorry really rookie question, but all I have is the Xen-2.0 dir I dont > >have the source xen kernel anywhere at least not the domU. > > > >where do I get that from ? > > > > > > > If you get the installer from > http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads.html, it will > be UNDER the xen-2.0 dir. Something like xen-2.0/linux-2.6.11-xenU.drwxrwxr-x 12 94 141 4096 May 22 11:56 . drwxr-xr-x 3 root root 4096 Jul 5 13:41 .. drwxrwxr-x 2 94 141 4096 May 22 11:56 buildconfigs -rw-rw-r-- 1 94 141 531234 May 22 11:56 ChangeLog -rw-rw-r-- 1 94 141 19355 May 22 11:56 COPYING drwxrwxr-x 5 94 141 4096 May 22 11:56 docs drwxrwxr-x 3 94 141 4096 May 22 11:56 extras drwxrwxr-x 5 94 141 4096 May 22 11:56 freebsd-5.3-xen-sparse -rwxrwxr-- 1 94 141 741 May 22 11:56 install.sh drwxrwxr-x 9 94 141 4096 May 22 11:56 linux-2.4.30-xen-sparse drwxrwxr-x 7 94 141 4096 May 22 11:56 linux-2.6.11-xen-sparse -rw-rw-r-- 1 94 141 5865 May 22 11:56 Makefile drwxrwxr-x 3 94 141 4096 May 22 11:56 netbsd-2.0-xen-sparse drwxrwxr-x 3 94 141 4096 May 22 11:56 patches -rw-rw-r-- 1 94 141 3336 May 22 11:56 README drwxrwxr-x 13 94 141 4096 May 22 11:56 tools drwxrwxr-x 7 94 141 4096 May 22 11:56 xen These are the only files within the xen-2.0 dir, no mention of the DomU (this is from a fresh tar zxf ) there is a mention of it in buildconfigs ? Im sorry but when it comes to messing with Kernels Im hopeless.> > As for getting modules, you should copy /lib/modules/2.6.11.10-xenU/ > (assuming you use Xen-2.0.6) from you dom-0 (e.g. physical host) to your > dom-U filesystem. > > Personally I prefer Frieder''s way, compile everything that I need in > dom-U built-in into the kernel, not as modules. I also use symbolic > links to specify the kernel for domU, e.g. something like this on a > domain''s config file : > > kernel="/etc/xen/kernel/linux" > > and /etc/xen/kernel/linux is a symbolic link to linux-2.6.11-xenU-HS20 > (I use my own dom-U kernel). > > That way a kernel (or Xen) upgrade is simply a matter of changing the > symlink in dom0 and rebooting domU as necessary, without having to touch > domU''s filesystems. > > Regards, > > Fajar > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Andrew Turnbull wrote:>On 05/07/05, Fajar A. Nugraha <fajar@telkom.net.id> wrote: > > >>If you get the installer from >>http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads.html, it will >>be UNDER the xen-2.0 dir. Something like xen-2.0/linux-2.6.11-xenU. >> >> > >drwxrwxr-x 12 94 141 4096 May 22 11:56 . >drwxr-xr-x 3 root root 4096 Jul 5 13:41 .. >drwxrwxr-x 2 94 141 4096 May 22 11:56 buildconfigs >-rw-rw-r-- 1 94 141 531234 May 22 11:56 ChangeLog >-rw-rw-r-- 1 94 141 19355 May 22 11:56 COPYING >drwxrwxr-x 5 94 141 4096 May 22 11:56 docs >drwxrwxr-x 3 94 141 4096 May 22 11:56 extras >drwxrwxr-x 5 94 141 4096 May 22 11:56 freebsd-5.3-xen-sparse >-rwxrwxr-- 1 94 141 741 May 22 11:56 install.sh >drwxrwxr-x 9 94 141 4096 May 22 11:56 linux-2.4.30-xen-sparse >drwxrwxr-x 7 94 141 4096 May 22 11:56 linux-2.6.11-xen-sparse >-rw-rw-r-- 1 94 141 5865 May 22 11:56 Makefile >drwxrwxr-x 3 94 141 4096 May 22 11:56 netbsd-2.0-xen-sparse >drwxrwxr-x 3 94 141 4096 May 22 11:56 patches >-rw-rw-r-- 1 94 141 3336 May 22 11:56 README >drwxrwxr-x 13 94 141 4096 May 22 11:56 tools >drwxrwxr-x 7 94 141 4096 May 22 11:56 xen > >These are the only files within the xen-2.0 dir, no mention of the DomU >(this is from a fresh tar zxf ) > > >That was from a fresh SOURCE tgz (http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/xen-2.0.6-src.tgz). The question is, how did you get Xen running in the first place? Possibilities are - Official installer (http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/xen-2.0.6-install-x86_32.tgz). You will have linux-2.6.11-xenU from there. - Building from source. On your xen-2.0 dir, run make dist and make install. You will find linux-2.6.11-xenU after running make dist. - From your OS binary (e.g RPM, deb, etc.). There should be a package that holds the modules and source code. The point is, your kernel and modules must match (I think gcc versions must match too). So if you rebuild xen manually from source, you may have to replace your current running kernel with the one you built. Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 06/07/05, Fajar A. Nugraha <fajar@telkom.net.id> wrote:> Andrew Turnbull wrote: > > >On 05/07/05, Fajar A. Nugraha <fajar@telkom.net.id> wrote: > > > > > >>If you get the installer from > >>http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads.html, it will > >>be UNDER the xen-2.0 dir. Something like xen-2.0/linux-2.6.11-xenU. > >> > >> > > > >drwxrwxr-x 12 94 141 4096 May 22 11:56 . > >drwxr-xr-x 3 root root 4096 Jul 5 13:41 .. > >drwxrwxr-x 2 94 141 4096 May 22 11:56 buildconfigs > >-rw-rw-r-- 1 94 141 531234 May 22 11:56 ChangeLog > >-rw-rw-r-- 1 94 141 19355 May 22 11:56 COPYING > >drwxrwxr-x 5 94 141 4096 May 22 11:56 docs > >drwxrwxr-x 3 94 141 4096 May 22 11:56 extras > >drwxrwxr-x 5 94 141 4096 May 22 11:56 freebsd-5.3-xen-sparse > >-rwxrwxr-- 1 94 141 741 May 22 11:56 install.sh > >drwxrwxr-x 9 94 141 4096 May 22 11:56 linux-2.4.30-xen-sparse > >drwxrwxr-x 7 94 141 4096 May 22 11:56 linux-2.6.11-xen-sparse > >-rw-rw-r-- 1 94 141 5865 May 22 11:56 Makefile > >drwxrwxr-x 3 94 141 4096 May 22 11:56 netbsd-2.0-xen-sparse > >drwxrwxr-x 3 94 141 4096 May 22 11:56 patches > >-rw-rw-r-- 1 94 141 3336 May 22 11:56 README > >drwxrwxr-x 13 94 141 4096 May 22 11:56 tools > >drwxrwxr-x 7 94 141 4096 May 22 11:56 xen > > > >These are the only files within the xen-2.0 dir, no mention of the DomU > >(this is from a fresh tar zxf ) > > > > > > > That was from a fresh SOURCE tgz > (http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/xen-2.0.6-src.tgz).I download this, however what I didnt appreciate is that Instead of just doing the "make world" to get to be able to change the XenU you need to do a "make dist" cd into the xenU dir and the do a make menuconfig ARCH=xen, make the appropriate changed then cd.. do a make dist and the a make install, and hey presto the sucker worked. thanks for bearing with me, but I just needed the instructions, understand came after that. Thanks> The question is, how did you get Xen running in the first place? > Possibilities are > - Official installer > (http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/xen-2.0.6-install-x86_32.tgz). > You will have linux-2.6.11-xenU from there. > - Building from source. On your xen-2.0 dir, run make dist and make > install. You will find linux-2.6.11-xenU after running make dist. > - From your OS binary (e.g RPM, deb, etc.). There should be a package > that holds the modules and source code. > > The point is, your kernel and modules must match (I think gcc versions > must match too). So if you rebuild xen manually from source, you may > have to replace your current running kernel with the one you built. > > Regards, > > Fajar > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users