Xen users - Jan 2006 - Debian packages for xen3 + kernel images for dom0/U

Hi,

I just wanted to let all interessted debian users know, that on my xen3 
repository are now kernel images available for dom0/U.

My Xen3 packages are using the latest xen3-testing (changeset 8269) and are 
available for sid, sarge & etch as well as for 32bit, 32bit-pae and 64bit. 
The kernel image is 2.6.12.6-xen with a std. xen config.

So there is no reason for compiling your own kernel on a debian system 
anymore, unless you need something very special. For such a case there is a 
"linux-patch-xen" package which applies to a vanilla 2.6.12 source
tree (and
converts it to a 2.6.12.6-xen).

If someone wants to use the new packages, please add the following two lines  
to /etc/apt/sources.list:

 deb http://packages.debianbase.de/<DISTRO>/<ARCH>/xen3 ./
 deb-src http://packages.debianbase.de/sources/xen3 ./

If you need 32bit + PAE instead, use the following two lines:

 deb http://packages.debianbase.de/<DISTRO>/<ARCH>/xen3-pae ./
 deb-src http://packages.debianbase.de/sources/xen3-pae ./

(Please always repleace <DISTRO> with either sid, sarge or etch and
<ARCH>
with i386 or amd64.)

After adding the lines to sources.list xen3 + kernel is installable with the 
following commands:

 apt-get update
 apt-get install xen linux-xen0-2.6

After that is completed only the initrd needs to be created and the
grub''s
menu.lst needs an entry for booting the new kernel.

the "linux-xen0-2.6" package will give instructions upon installation
on how
to build a initrd and how to change the grub config.

If there is something not working as expected, please let me know... Feedback 
is always appreciated.

Some instructions on how to compile your own xen kernel with debian is 
available here: http://www.debian-administration.org/articles/320
(thanks to Steve Kemp)

--Ralph

P.s.:
My Version "tha11" now uses the Xen 3.0-testing upstream, all versions
before
used xen 3.0.0. 

If someone upgrades from <= tha11 to the recent package there is a mismatch 
between the old self compiled xen kernel and the hypervisor (now using 
xen3-testing). In this case, please compile a new kernel with an updated 
"linux-patch-xen" package (>= tha11) or simply switch to use
linux-xen0-2.6
as kernel (which will always matches the hypervisor).

For more information what changed in each xen3 package, see the packages 
changelog.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> I just wanted to let all interessted debian users know, that on my xen3 
> repository are now kernel images available for dom0/U.
> 
> My Xen3 packages are using the latest xen3-testing (changeset 8269) and are
> available for sid, sarge & etch as well as for 32bit, 32bit-pae and
64bit.
> The kernel image is 2.6.12.6-xen with a std. xen config.
> 
> So there is no reason for compiling your own kernel on a debian system 
> anymore, unless you need something very special. For such a case there is a
> "linux-patch-xen" package which applies to a vanilla 2.6.12
source tree (and
> converts it to a 2.6.12.6-xen).
> 
> If someone wants to use the new packages, please add the following two
lines
> to /etc/apt/sources.list:
> 
>  deb http://packages.debianbase.de/<DISTRO>/<ARCH>/xen3 ./
>  deb-src http://packages.debianbase.de/sources/xen3 ./
> 
> If you need 32bit + PAE instead, use the following two lines:
> 
>  deb http://packages.debianbase.de/<DISTRO>/<ARCH>/xen3-pae ./
>  deb-src http://packages.debianbase.de/sources/xen3-pae ./
> 
Thank you very much for doing this.  I was just about to report kernel
compilation errors for the latest unstable Xen source when I saw this
message.  But sarge/i386/Packages.gz is missing so presently "apt-get
update" will not work.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Am Dienstag, 17. Januar 2006 00:00 schrieb
prosolutions@gmx.net:
> > I just wanted to let all interessted debian users know, that on my
xen3
> > repository are now kernel images available for dom0/U.
> >
> > My Xen3 packages are using the latest xen3-testing (changeset 8269)
and
> > are available for sid, sarge & etch as well as for 32bit,
32bit-pae and
> > 64bit. The kernel image is 2.6.12.6-xen with a std. xen config.
> >
> > So there is no reason for compiling your own kernel on a debian system
> > anymore, unless you need something very special. For such a case there
is
> > a "linux-patch-xen" package which applies to a vanilla
2.6.12 source tree
> > (and converts it to a 2.6.12.6-xen).
> >
> > If someone wants to use the new packages, please add the following two
> > lines to /etc/apt/sources.list:
> >
> >  deb http://packages.debianbase.de/<DISTRO>/<ARCH>/xen3 ./
> >  deb-src http://packages.debianbase.de/sources/xen3 ./
> >
> > If you need 32bit + PAE instead, use the following two lines:
> >
> >  deb
http://packages.debianbase.de/<DISTRO>/<ARCH>/xen3-pae ./
> >  deb-src http://packages.debianbase.de/sources/xen3-pae ./
>
> Thank you very much for doing this.  I was just about to report kernel
> compilation errors for the latest unstable Xen source when I saw this
> message.  But sarge/i386/Packages.gz is missing so presently "apt-get
> update" will not work.
Your problem is probably a wrong line in your /etc/apt/sources.list... correct 
for sarge -> i386 -> xen3 (without pae) would be:

"deb http://packages.debianbase.de/sarge/i386/xen3 ./"

I think you have missed the "./" at the end or even the "xen3
./" at the end.

--Ralph

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> My Xen3 packages are using the latest xen3-testing (changeset 8269) and are
> available for sid, sarge & etch as well as for 32bit, 32bit-pae and
64bit.
> The kernel image is 2.6.12.6-xen with a std. xen config.
> 
> So there is no reason for compiling your own kernel on a debian system 
> anymore, unless you need something very special. For such a case there is a

Thanks.  I was curious why your xen package has dependencies for
xfree86-common and xlibs-data?


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Am Dienstag, 17. Januar 2006 18:36 schrieb
prosolutions@gmx.net:
> > My Xen3 packages are using the latest xen3-testing (changeset 8269)
and
> > are available for sid, sarge & etch as well as for 32bit,
32bit-pae and
> > 64bit. The kernel image is 2.6.12.6-xen with a std. xen config.
> >
> > So there is no reason for compiling your own kernel on a debian system
> > anymore, unless you need something very special. For such a case there
is
>
> Thanks.  I was curious why your xen package has dependencies for
> xfree86-common and xlibs-data?
I never put any x dependencies in in the xen package, but in fact the xen 
packages are compiled against sdl, and so my packages are depending on sdl.

the sdl library depends on xlibs, thats why xen depends indirectly to some x 
package, but in fact only one library package and the -common package, which 
is harmless at all.
 
see yourself:

# apt-cache show libsdl1.2debian-oss
Package: libsdl1.2debian-oss
Priority: extra
Section: libs
Installed-Size: 420
Maintainer: Debian SDL maintainers <mrd-sdl@debian.org>
Architecture: i386
Source: libsdl1.2
Version: 1.2.7+1.2.8cvs20041007-4.1
Replaces: libsdl1.2-all, libsdl1.2-esd, libsdl1.2-oss, libsdl1.2-arts, 
libsdl1.2 (<< 1.2.1-1), libsdl1.2debian-all, libsdl1.2debian-alsa, 
libsdl1.2debian-esd, libsdl1.2debian-arts, libsdl1.2debian-nas, libsdl1.2-nas
Provides: libsdl1.2-oss
Depends: libc6 (>= 2.3.2.ds1-4), libx11-6 | xlibs (>> 4.1.0), libxext6
| xlibs
(>> 4.1.0)
Conflicts: libsdl1.2-all, libsdl1.2-esd, libsdl1.2-oss, libsdl1.2-arts, 
libsdl1.2 (<< 1.2.1-1), libsdl1.2debian-all, libsdl1.2debian-alsa, 
libsdl1.2debian-esd, libsdl1.2debian-arts, libsdl1.2debian-nas, libsdl1.2-nas
Filename: 
pool/main/libs/libsdl1.2/libsdl1.2debian-oss_1.2.7+1.2.8cvs20041007-4.1_i386.deb
Size: 182604
MD5sum: 824029b7ef572cbd8555da5809063fba
Description: Simple DirectMedia Layer (with X11 and OSS options)
 SDL is a library that allows programs portable low level access to a video
 framebuffer, audio output, mouse, and keyboard.
 .
 This version of SDL is compiled with X11 graphics and oss sound.

--Ralph

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

I have another question: in /boot there are:

-rw-r--r--  1 root root  200019 Jan 15 00:03 xen-3.0.0.gz
lrwxrwxrwx  1 root root      12 Jan 17 10:00 xen-3.0.gz -> xen-3.0.0.gz
lrwxrwxrwx  1 root root      12 Jan 17 10:00 xen-3.gz -> xen-3.0.0.gz
-rw-r--r--  1 root root  503826 Jan 15 00:03 xen-syms-3.0.0
lrwxrwxrwx  1 root root      12 Jan 17 10:00 xen.gz -> xen-3.0.0.gz


is xen-syms-3.0.0 the same as System.map?  

With the standard xen pacakge I had the recommended grub stanza of:

title           Xen 3.0 / XenLinux 2.6
root            (hd0,0)
kernel          /xen-3.0.gz dom0_mem=262144
module          /vmlinuz-2.6-xen0 root=/dev/cciss/c0d0p1 ro

I am not sure now what to replace the module line with.

Also - is this kernel compiled with the widest possible amount of
hardware support?  The reason I was trying to build my own xen kernel in
the first place was because of the lack of Compaq Array 5i controller
support (cciss) in the binary kernel xen provides.

Thank you for all your help.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Am Dienstag, 17. Januar 2006 19:25 schrieb
prosolutions@gmx.net:
> I have another question: in /boot there are:
>
> -rw-r--r--  1 root root  200019 Jan 15 00:03 xen-3.0.0.gz
> lrwxrwxrwx  1 root root      12 Jan 17 10:00 xen-3.0.gz -> xen-3.0.0.gz
> lrwxrwxrwx  1 root root      12 Jan 17 10:00 xen-3.gz -> xen-3.0.0.gz
> -rw-r--r--  1 root root  503826 Jan 15 00:03 xen-syms-3.0.0
> lrwxrwxrwx  1 root root      12 Jan 17 10:00 xen.gz -> xen-3.0.0.gz
>
>
> is xen-syms-3.0.0 the same as System.map?
honestly, i don''t know, maybe someone else knows more
:)
>
> With the standard xen pacakge I had the recommended grub stanza of:
>
> title           Xen 3.0 / XenLinux 2.6
> root            (hd0,0)
> kernel          /xen-3.0.gz dom0_mem=262144
> module          /vmlinuz-2.6-xen0 root=/dev/cciss/c0d0p1 ro
>
> I am not sure now what to replace the module line with.
the linux-xen0-2.6 package informs you what to do and how a 
the /boot/grub/menu.lst should look like.

in fact the steps are:

1) install the actual kernel with "dpkg -i /usr/src/*xen*.deb"
(I used wildcards, because I don''t know which kernel image you exactly
use.
the filename in sid, sarge and etch + i386/amd64 is not the same!)

2) build initrd with: mkinitrd -o /boot/xen-modules-2.6.12.6-xen 2.6.12.6-xen

3) modify your /boot/grub/menu.lst

4) copy the libraries from /lib/modules/2.6.12.6-xen to your 
domainU''s /lib/modules directory. (The domU system wants the kernel
modules
too)

Normaly all these steps should get shown when you install the linux-xen0-2.6 
package for the first time. Only the fourth step is missing in the instuction 
that gets shown automaticly. I will add that in the next version.

if you didn''t saw that output, you can execute "dpkg-reconfigure 
linux-xen0-2.6" to get that message again.

for my system it looks like this:

  title        Xen 3.0.0 - Linux 2.6.12.6-xen
                kernel      /boot/xen-3.0.0.gz
                module     /boot/xen-linux-2.6.12.6-xen root=/dev/hda7 ro
                module     /boot/xen-modules-2.6.12.6-xen
> Also - is this kernel compiled with the widest possible amount of
> hardware support? 
it''s compiled with xen''s std. config, but that includes really
a lot. the
kernel image is about 16mb, so that must mean a lot modules :)
> The reason I was trying to build my own xen kernel in 
> the first place was because of the lack of Compaq Array 5i controller
> support (cciss) in the binary kernel xen provides.
is that the MEGARAID module? the MEGARAID module is available, yes.

otherwise check yourself. after you installed the kernel image the kernel 
config is available in /boot/config-2.6.12.6-xen.

if the module you need is not enabled, just give me a hint what you need 
exactly. if the module doesn''t brake anything else I can enable it in
the
next version...
> Thank you for all your help.
--Ralph

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

So wrote Ralph Passgang on Tuesday, 17 January 2006:
> Date: Tue, 17 Jan 2006 21:15:54 +0100
> From: Ralph Passgang <ralph@debianbase.de>
> To: prosolutions@gmx.net, xen-users@lists.xensource.com
> Subject: Re: [Xen-users] Debian packages for xen3 + kernel images for
dom0/U
> User-Agent: KMail/1.9.1
> 
> Am Dienstag, 17. Januar 2006 19:25 schrieb prosolutions@gmx.net:
> > I have another question: in /boot there are:
> >
> > -rw-r--r--  1 root root  200019 Jan 15 00:03 xen-3.0.0.gz
> > lrwxrwxrwx  1 root root      12 Jan 17 10:00 xen-3.0.gz ->
xen-3.0.0.gz
> > lrwxrwxrwx  1 root root      12 Jan 17 10:00 xen-3.gz ->
xen-3.0.0.gz
> > -rw-r--r--  1 root root  503826 Jan 15 00:03 xen-syms-3.0.0
> > lrwxrwxrwx  1 root root      12 Jan 17 10:00 xen.gz -> xen-3.0.0.gz
> >
> >
> > is xen-syms-3.0.0 the same as System.map?
> 
> honestly, i don''t know, maybe someone else knows more :)
> >
> > With the standard xen pacakge I had the recommended grub stanza of:
> >
> > title           Xen 3.0 / XenLinux 2.6
> > root            (hd0,0)
> > kernel          /xen-3.0.gz dom0_mem=262144
> > module          /vmlinuz-2.6-xen0 root=/dev/cciss/c0d0p1 ro
> >
> > I am not sure now what to replace the module line with.
> 
> the linux-xen0-2.6 package informs you what to do and how a 
> the /boot/grub/menu.lst should look like.
> 
> in fact the steps are:
> 
> 1) install the actual kernel with "dpkg -i /usr/src/*xen*.deb"
> (I used wildcards, because I don''t know which kernel image you
exactly use.

Thank you.  I wasn''t clear about that.  I apt-get installed
linux-xen0-2.6 but didn''t realize after this the need to manually
install the .deb in /usr/src.  I was expecting a debconf dialog with
information and neglected to see the output message.  I will keep
plugging away at this and let you know my results.  By the way, I am
installing this on an HP Proliant DL380 with a Compaq 5i SCSI RAID
controller and if we get this working it will be the first time I''ve
seen Xen run on this platform.





_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

So wrote prosolutions@gmx.net on Tuesday, 17 January
2006:
> Date: Tue, 17 Jan 2006 14:09:47 -0800
> From: prosolutions@gmx.net
> To: Ralph Passgang <ralph@debianbase.de>
> Subject: Re: [Xen-users] Debian packages for xen3 + kernel images for
dom0/U
> User-Agent: Mutt/1.5.11
> Cc: prosolutions@gmx.net, xen-users@lists.xensource.com
> 
> So wrote Ralph Passgang on Tuesday, 17 January 2006:
> > Date: Tue, 17 Jan 2006 21:15:54 +0100
> > From: Ralph Passgang <ralph@debianbase.de>
> > To: prosolutions@gmx.net, xen-users@lists.xensource.com
> > Subject: Re: [Xen-users] Debian packages for xen3 + kernel images for
dom0/U
> > User-Agent: KMail/1.9.1
> > 
> > Am Dienstag, 17. Januar 2006 19:25 schrieb prosolutions@gmx.net:
> > > I have another question: in /boot there are:
> > >
> > > -rw-r--r--  1 root root  200019 Jan 15 00:03 xen-3.0.0.gz
> > > lrwxrwxrwx  1 root root      12 Jan 17 10:00 xen-3.0.gz ->
xen-3.0.0.gz
> > > lrwxrwxrwx  1 root root      12 Jan 17 10:00 xen-3.gz ->
xen-3.0.0.gz
> > > -rw-r--r--  1 root root  503826 Jan 15 00:03 xen-syms-3.0.0
> > > lrwxrwxrwx  1 root root      12 Jan 17 10:00 xen.gz ->
xen-3.0.0.gz
> > >
> > >
> > > is xen-syms-3.0.0 the same as System.map?
> > 
> > honestly, i don''t know, maybe someone else knows more :)
> > >
> > > With the standard xen pacakge I had the recommended grub stanza
of:
> > >
> > > title           Xen 3.0 / XenLinux 2.6
> > > root            (hd0,0)
> > > kernel          /xen-3.0.gz dom0_mem=262144
> > > module          /vmlinuz-2.6-xen0 root=/dev/cciss/c0d0p1 ro
> > >
> > > I am not sure now what to replace the module line with.
> > 
> > the linux-xen0-2.6 package informs you what to do and how a 
> > the /boot/grub/menu.lst should look like.
> > 
> > in fact the steps are:
> > 
> > 1) install the actual kernel with "dpkg -i
/usr/src/*xen*.deb"
> > (I used wildcards, because I don''t know which kernel image
you exactly use.
> 
> 
> Thank you.  I wasn''t clear about that.  I apt-get installed
> linux-xen0-2.6 but didn''t realize after this the need to manually
> install the .deb in /usr/src.  I was expecting a debconf dialog with
> information and neglected to see the output message.  I will keep
> plugging away at this and let you know my results.  By the way, I am
> installing this on an HP Proliant DL380 with a Compaq 5i SCSI RAID
> controller and if we get this working it will be the first time
I''ve
> seen Xen run on this platform.
> 
> 
Sorry to report that the booting of this version of Xen also failed on
the Proliant DL380 running Debian/stable.  I cannot give you much
information as the bootup was very fast and what initially looked like a
normal bootup quickly went to a blank screen and the machine promptly
rebooted.  

I think the only way I am going to get Xen to run on this hardware is to
build my own kernel - but all my experience with Xen so far is that it
is essentially so brittle as to be virtually unusable.  That is sad,
because I have seen a lot of positive press about it and really was keen
to start testing it for use in a production environment.

Thanks for your help.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Here''s some more feedback - I watched the bootup process more carefully
and the last line I saw before it blanked out was

XFS....

does this kernel have XFS support?


Another question: do you know about this:
http://wiki.xensource.com/xenwiki/DebianSarge   specifically, about the
libc6-i686 issue:

"Debian sarge comes with glibc-2.3.2 and gcc-3.3. The latter
doesn''t
know yet the -mno-tls-direct-seg-refs option recommended in
XenSpecificGlibc. But the good news: I''ve just tried to build a
libc6-i686 with only the patch but without the option, and it seems to
work nice! (no warnings, NPTL working)"

I did install his version of it using the following in my sources.list:

#modified libc6-i686 for use with Xen
deb http://www.hodek.net/debian/ sarge roman/


At this point what I would like to do is install your deb sources and
change some kernel config options.  If you need someone who is willing
to spend time and devote CPU resources to compiling kernels I volunteer.
Maybe we can create a generic 386, 686, and SMP versions.  I would like
to build kernels supporting the maximum set of hardware possible.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Am Dienstag, 17. Januar 2006 23:28 schrieb
prosolutions@gmx.net:
> So wrote prosolutions@gmx.net on Tuesday, 17 January 2006:
[...]
> > Thank you.  I wasn''t clear about that.  I apt-get installed
> > linux-xen0-2.6 but didn''t realize after this the need to
manually
> > install the .deb in /usr/src.  I was expecting a debconf dialog with
> > information and neglected to see the output message.
no, just some simple echos to std.out in the postinst scripts for now... I 
might change to using templates and debconf in future.

linux-xen0-2.6 is just a kind of container/meta-package. It helps me compiling 
the kernel for each debian distro and arch without having to do it manually. 
It also gives me the possibility to divert the kernel from the hypervisor & 
userspace tools. I don''t need to provide a new kernel when I build a
new xen
package. Only on new upstream versions of xen a new kernel is really needed.
> > I will keep 
> > plugging away at this and let you know my results.  By the way, I am
> > installing this on an HP Proliant DL380 with a Compaq 5i SCSI RAID
> > controller and if we get this working it will be the first time
I''ve
> > seen Xen run on this platform.
>
> Sorry to report that the booting of this version of Xen also failed on
> the Proliant DL380 running Debian/stable.
hmmm, I can''t support that kind of problems myself, because that is far
away
from "packaging-problems"... but maybe some other here can.

but was always may be worth investigating is the bios setting of your server. 
try to disable every not really needed feature (like usb, onboard sound, 
etc...) maybe some bios switch might help you to boot the kernel.

also using the noacpi boot-parameter might help. don''t know...

ah, and if you are using the pae version, try the normal version instead. 
might work better... is also helps to exclude pae as your problem.
> I cannot give you much 
> information as the bootup was very fast and what initially looked like a
> normal bootup quickly went to a blank screen and the machine promptly
> rebooted.
oh, there is way to get a bit more output... is the dom0 kernel 
hanging/rebooting or the xen hypervisor?

I never saw the hypervisor crash, but if something is wrong with your dom0, 
then you should append "noreboot" to menu.list line regarding the
kernel.

for example: 
 ...
 module       /boot/xen-linux-2.6.12.6-xen root=/dev/hda7 ro noreboot
 ...

then you can at least try to see when the kernel crash... that could maybe 
help to see where the problem is.
> I think the only way I am going to get Xen to run on this hardware is to
> build my own kernel - 
That would only help, if you find the part that is causing the trouble and 
when you don''t need this part, so you can safely disable it.

I have exactly this kernel running on a dual xeon smp machine with 3ware sata 
controller and on a dual xeon machine with a adaptec scsi controller. both 
are orig. intel boards, but not from a distributor like dell, hp or so... 
they are both running without any issues.
> but all my experience with Xen so far is that it 
> is essentially so brittle as to be virtually unusable. 
to help you, if you want to try it with your own kernel, take a look at: 
http://www.debian-administration.org/articles/320 (again thx to Steve Kemp)

It''s written for sid(unstable) but also working 1:1 for sarge...
> That is sad, 
> because I have seen a lot of positive press about it and really was keen
> to start testing it for use in a production environment.
it''s really great... I have running about 12 domains on a dual xeon
with 3GB
ram without any performance issues... with a bit more ram I think about 20 
(any maybe more) production domainU are realistic. If I see that correctly on 
our box, the first bottleneck will be the disk drives (but at the moment
it''s
ok), because there is quite a lot of disk usage from the domainUs in our 
setup. cpu usage is quite moderate for 12 productions systems and would be 
enough for even more domains.
> Thanks for your help.
btw... so that others can better help you... do you use xen3 in 32bit mode or 
xen3 32bit + pae or even xen3 in 64bit mode? that could be quite important.

ah, before I forget to mention, you are running xen3-testing with changeset 
8269. that could be important for other to know and for further debugging.

sorry... I can''t do anything more, but I am not a developer or a kernel
guru :)

--Ralph

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Am Dienstag, 17. Januar 2006 23:58 schrieb
prosolutions@gmx.net:
> Here''s some more feedback - I watched the bootup process more
carefully
> and the last line I saw before it blanked out was
>
> XFS....
>
> does this kernel have XFS support?
of course... but as module, so you need the initrd or your system will not be 
able to mount the root filesystem:

~$ cat /boot/config-2.6.12.6-xen |grep XFS
# XFS support
CONFIG_XFS_FS=m
CONFIG_XFS_EXPORT=y
CONFIG_XFS_RT=y
CONFIG_XFS_QUOTA=y
CONFIG_XFS_SECURITY=y
CONFIG_XFS_POSIX_ACL=y
CONFIG_VXFS_FS=m
> Another question: do you know about this:
> http://wiki.xensource.com/xenwiki/DebianSarge   specifically, about the
> libc6-i686 issue:
>
> "Debian sarge comes with glibc-2.3.2 and gcc-3.3. The latter
doesn''t
> know yet the -mno-tls-direct-seg-refs option recommended in
> XenSpecificGlibc. But the good news: I''ve just tried to build a
> libc6-i686 with only the patch but without the option, and it seems to
> work nice! (no warnings, NPTL working)"
>
> I did install his version of it using the following in my sources.list:
>
> #modified libc6-i686 for use with Xen
> deb http://www.hodek.net/debian/ sarge roman/
I never used this libc6 version mentioned in the wiki, so I don''t know
if is
really working and compatible to xen3 and/or my packages...

I will test them tomorrow, I didn''t saw that on the xen wiki till now,
must be
new :)

but if you want to be sure, reinstall the orig. libc6, mv /lib/tls 
to /lib/tls.disabled and reboot your machine with the xen hypervisor&kernel.
If it crashes again at the same moment, then it is probably not a problem 
related to that libc6 package. But I guess the libc6 isn''t problem
anyway,
because your crash seems to happen before the rootfs is even mounted.
> At this point what I would like to do is install your deb sources and
> change some kernel config options.  If you need someone who is willing
> to spend time and devote CPU resources to compiling kernels I volunteer.
> Maybe we can create a generic 386, 686, and SMP versions.  I would like
> to build kernels supporting the maximum set of hardware possible.
put the following line in your /etc/apt/sources.list:
 deb-src http://packages.debianbase.de/sources/xen3 ./

then "apt-get update; apt-get source linux-xen0-2.6" and change to 
"linux-xen0-2.6" then.

now edit "debian/rules" and see if you want to change something, maybe
the
MAINTAINER or PAE option.

then run "debian/rules build"... this will not build the kernel, but
will
download & patch the kernel source as well as building the default config.

if you want to change the kernel config, change dir to "linux-2.6.12" 
and
run: "make ARCH=xen menuconfig", change what you want to change and
then
"cd .." again.

now it''s time to compile the kernel and package it... run
"debian/rules
install" for that.

your done... for now my source package for the kernel is more or less a hack, 
but working. I will make it more eleganter if I have to for it.

compiling xen is even easier (but needs more installed packages, because of 
dependencies).... compiling is easy as:

"apt-get source xen"
"cd xen-3.0.0"
"dpkg-buildpackage -b"

done.

--Ralph

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

prosolutions@gmx.net wrote:
> Sorry to report that the booting of this version of Xen also failed on
> the Proliant DL380 running Debian/stable.  I cannot give you much
> information as the bootup was very fast and what initially looked like a
> normal bootup quickly went to a blank screen and the machine promptly
> rebooted.  
> 
> I think the only way I am going to get Xen to run on this hardware is to
> build my own kernel - but all my experience with Xen so far is that it
> is essentially so brittle as to be virtually unusable.  That is sad,
> because I have seen a lot of positive press about it and really was keen
> to start testing it for use in a production environment.
I had exactly the same problem on a very different machine (VIA EPIA
board with a Nehemia CPU) when I used a 2.6.12.6-xen kernel built with
the dom0 defconfig. I don''t remember exactly what caused this problem
(I
think it was USB related), but building my own kernel with only the
hardware enabled that was really present did solve the problem and now
the system is up and running stable for almost two weeks. Don''t give up
yet (you''ll definitely miss something ;-) ), as soon as you get it
running it works very well.

Hope this helps,
Michael

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

installation and booting
with your debian packages works fine
thanks a lot for this work !

dom0 works fine
I get a problem starting a domU
I only changed the kernel-line in the config-file
this config was working with a 2.0.7 xen konfiguration

after: xm create /etc/xen/vm01.conf I get an error

"...(vif1) no backend device .... "

any idea ?

boris




_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi !

I just installed debian sarge and the debianbase xen3 packages.

My hardware
HP Proliant 330
2.5GB ram
raid5 Smart Array 641 (4 disks)


xen:~# cat /etc/apt/sources.list
deb http://packages.debianbase.de/sarge/i386/xen3 ./
deb-src http://packages.debianbase.de/sources/xen3 ./
deb http://ftp.se.debian.org/debian/ stable main
deb-src http://ftp.se.debian.org/debian/ stable main
deb http://security.debian.org/ stable/updates main


xen:~# cat /etc/xen/sarge1.cfg
kernel = "/boot/xen-3.gz"
memory = 128
name   = "sarge1"
disk   = [
''file:/home/xen/domains/sarge1/disk.img,sda1,w'',''file:/
home/xen/domains/sarge1/swap.img,sda2,w'' ]
root   = "/dev/sda1 ro"
dhcp="dhcp"

xen:~# cat /var/log/xend-debug.log
ERROR: Not a Xen-ELF image: ''__xen_guest'' section not found.
ERROR: Error constructing guest OS
Traceback (most recent call last):
   File "/usr/lib/python2.3/site-packages/xen/xend/server/ 
SrvDomainDir.py", line 77, in op_create
     dominfo = self.xd.domain_create(config)
   File "/usr/lib/python2.3/site-packages/xen/xend/XendDomain.py",  
line 226, in domain_create
     dominfo = XendDomainInfo.create(config)
   File "/usr/lib/python2.3/site-packages/xen/xend/ 
XendDomainInfo.py", line 182, in create
     vm.initDomain()
   File "/usr/lib/python2.3/site-packages/xen/xend/ 
XendDomainInfo.py", line 1190, in initDomain
     channel_details = self.image.createImage()
   File "/usr/lib/python2.3/site-packages/xen/xend/image.py", line  
115, in createImage
     return self.createDomain()
   File "/usr/lib/python2.3/site-packages/xen/xend/image.py", line  
134, in createDomain
     result = self.buildDomain()
   File "/usr/lib/python2.3/site-packages/xen/xend/image.py", line  
183, in buildDomain
     ramdisk        = self.ramdisk)
error: (0, ''Error'')


xen:~# cat /boot/grub/menu.lst
default         0
timeout         5
color cyan/blue white/blue

title        Xen 3.0.0 - Linux 2.6.12.6-xen
              kernel      /boot/xen-3.0.0.gz dom0_mem=262144  
console=tty0
              module      /boot/xen-linux-2.6.12.6-xen root=/dev/ 
cciss/c0d0p1 ro
              module      /boot/xen-modules-2.6.12.6-xen nousb
- -----

the Guest is installed with xen-tools.

could it be the guest-kernel ? its the kernel from the debianbase.de  
package.

Any suggestions would be great !



- --
Anders Johansson
Anykey Solutions
Security/Network/Computer/Administration
E-Mail: anders@anykey.se
Cellphone: +46 (0)708494996
Office: +46 (0)13 73244
Fax: +46 (0)13 73190

Snailmail:
Vistlöt kvarn
59062 Linghem


Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html



On Jan 16, 2006, at 2:46 PM, Ralph Passgang wrote:
> Hi,
>
> I just wanted to let all interessted debian users know, that on my  
> xen3
> repository are now kernel images available for dom0/U.
>
> My Xen3 packages are using the latest xen3-testing (changeset 8269)  
> and are
> available for sid, sarge & etch as well as for 32bit, 32bit-pae and  
> 64bit.
> The kernel image is 2.6.12.6-xen with a std. xen config.
>
> So there is no reason for compiling your own kernel on a debian system
> anymore, unless you need something very special. For such a case  
> there is a
> "linux-patch-xen" package which applies to a vanilla 2.6.12
source
> tree (and
> converts it to a 2.6.12.6-xen).
>
> If someone wants to use the new packages, please add the following  
> two lines
> to /etc/apt/sources.list:
>
>  deb http://packages.debianbase.de/<DISTRO>/<ARCH>/xen3 ./
>  deb-src http://packages.debianbase.de/sources/xen3 ./
>
> If you need 32bit + PAE instead, use the following two lines:
>
>  deb http://packages.debianbase.de/<DISTRO>/<ARCH>/xen3-pae ./
>  deb-src http://packages.debianbase.de/sources/xen3-pae ./
>
> (Please always repleace <DISTRO> with either sid, sarge or etch and  
> <ARCH>
> with i386 or amd64.)
>
> After adding the lines to sources.list xen3 + kernel is installable  
> with the
> following commands:
>
>  apt-get update
>  apt-get install xen linux-xen0-2.6
>
> After that is completed only the initrd needs to be created and the  
> grub''s
> menu.lst needs an entry for booting the new kernel.
>
> the "linux-xen0-2.6" package will give instructions upon  
> installation on how
> to build a initrd and how to change the grub config.
>
> If there is something not working as expected, please let me  
> know... Feedback
> is always appreciated.
>
> Some instructions on how to compile your own xen kernel with debian is
> available here: http://www.debian-administration.org/articles/320
> (thanks to Steve Kemp)
>
> --Ralph
>
> P.s.:
> My Version "tha11" now uses the Xen 3.0-testing upstream, all  
> versions before
> used xen 3.0.0.
>
> If someone upgrades from <= tha11 to the recent package there is a  
> mismatch
> between the old self compiled xen kernel and the hypervisor (now using
> xen3-testing). In this case, please compile a new kernel with an  
> updated
> "linux-patch-xen" package (>= tha11) or simply switch to use
linux-
> xen0-2.6
> as kernel (which will always matches the hypervisor).
>
> For more information what changed in each xen3 package, see the  
> packages
> changelog.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFD10inAQ7rAwCL1U8RAiZSAKCSnp2s1xddu+pEpoWPMmwAFOtbXwCaA247
XA9hEL4sZbrPZMrSvWye3Sk=yD/v
-----END PGP SIGNATURE-----

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Am Mittwoch, 25. Januar 2006 10:45 schrieb Anders
Johansson:
> Hi !
>
> I just installed debian sarge and the debianbase xen3 packages.
>
> My hardware
> HP Proliant 330
> 2.5GB ram
> raid5 Smart Array 641 (4 disks)
>
>
> xen:~# cat /etc/apt/sources.list
> deb http://packages.debianbase.de/sarge/i386/xen3 ./
> deb-src http://packages.debianbase.de/sources/xen3 ./
> deb http://ftp.se.debian.org/debian/ stable main
> deb-src http://ftp.se.debian.org/debian/ stable main
> deb http://security.debian.org/ stable/updates main
>
>
> xen:~# cat /etc/xen/sarge1.cfg
> kernel = "/boot/xen-3.gz"
> memory = 128
> name   = "sarge1"
> disk   = [
''file:/home/xen/domains/sarge1/disk.img,sda1,w'',''file:/
> home/xen/domains/sarge1/swap.img,sda2,w'' ]
> root   = "/dev/sda1 ro"
> dhcp="dhcp"
here is your error... /boot/xen-3.gz is not the kernel image, it''s the
xen
hypervisor itself. 

If you have installed the "linux-xen0-2.6" package correctly, you
should have
a /boot/xen-linux-2.6.12.6-xen file, which is a xen kernel for dom0 and/or 
any domU. So using "kernel = /boot/xen-linux-2.6.12.6-xen" would be
correct.

You additionally need an initrd, which normaly exists 
in /boot/xen-modules-2.6.12.6-xen. If it''s not existing, you have not
created
it with mkinitrd... In your domU config you have to include the inird with: 
"initrd = /boot/xen-modules-2.6.12.6-xen"

I guess there is also some network settings missing, but maybe it also works 
without them, never tested that really... 

For example configuration files you can take a look 
at /usr/share/doc/xen/examples.
> xen:~# cat /var/log/xend-debug.log
> ERROR: Not a Xen-ELF image: ''__xen_guest'' section not
found.
> ERROR: Error constructing guest OS
> Traceback (most recent call last):
>    File "/usr/lib/python2.3/site-packages/xen/xend/server/
> SrvDomainDir.py", line 77, in op_create
>      dominfo = self.xd.domain_create(config)
>    File
"/usr/lib/python2.3/site-packages/xen/xend/XendDomain.py",
> line 226, in domain_create
>      dominfo = XendDomainInfo.create(config)
>    File "/usr/lib/python2.3/site-packages/xen/xend/
> XendDomainInfo.py", line 182, in create
>      vm.initDomain()
>    File "/usr/lib/python2.3/site-packages/xen/xend/
> XendDomainInfo.py", line 1190, in initDomain
>      channel_details = self.image.createImage()
>    File "/usr/lib/python2.3/site-packages/xen/xend/image.py",
line
> 115, in createImage
>      return self.createDomain()
>    File "/usr/lib/python2.3/site-packages/xen/xend/image.py",
line
> 134, in createDomain
>      result = self.buildDomain()
>    File "/usr/lib/python2.3/site-packages/xen/xend/image.py",
line
> 183, in buildDomain
>      ramdisk        = self.ramdisk)
> error: (0, ''Error'')
>
>
> xen:~# cat /boot/grub/menu.lst
> default         0
> timeout         5
> color cyan/blue white/blue
>
> title        Xen 3.0.0 - Linux 2.6.12.6-xen
>               kernel      /boot/xen-3.0.0.gz dom0_mem=262144
> console=tty0
>               module      /boot/xen-linux-2.6.12.6-xen root=/dev/
> cciss/c0d0p1 ro
>               module      /boot/xen-modules-2.6.12.6-xen nousb
> -----
>
> the Guest is installed with xen-tools.
>
> could it be the guest-kernel ? its the kernel from the debianbase.de
> package.
>
> Any suggestions would be great !
the rest of your setup looks quite well, so if you fixed your domU config, you 
should be able to start the new domU. If not let me know...

--Ralph

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> 
> I had exactly the same problem on a very different machine (VIA EPIA
> board with a Nehemia CPU) when I used a 2.6.12.6-xen kernel built with
> the dom0 defconfig. I don''t remember exactly what caused this
problem (I
> think it was USB related), but building my own kernel with only the
> hardware enabled that was really present did solve the problem and now
> the system is up and running stable for almost two weeks. Don''t
give up
> yet (you''ll definitely miss something ;-) ), as soon as you get it
> running it works very well.
> 
Thanks all for your support.  In the end it was just too much to try and
get the custom kernel with Compaq Array cciss support built.  I
downloaded and installed Fedora Core 5 test2 and and getting a Xen 3
dom0 up and running on it has been as easy as "yum install
kernel-xen-hypervisor.i686 xen"  Even if I had eventually managed to get
a compile to successfully complete (which I doubt) the fact that it was
so incredibly brittle meant I wouldn''t have really wanted to rely on
it.
Hopefully someone will try to create a Debian Xen kernel with the
philosophy that as much hardware as possible should be supported -
including the full range of ATA, SATA, and SCSI controllers that may
serve as boot and root devices.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Ralph Passgang wrote:
> Hi,
>
> I just wanted to let all interessted debian users know, that on my xen3 
> repository are now kernel images available for dom0/U.
>
> My Xen3 packages are using the latest xen3-testing (changeset 8269) and are
> available for sid, sarge & etch as well as for 32bit, 32bit-pae and
64bit.
> The kernel image is 2.6.12.6-xen with a std. xen config.
Thanks for the packages. If you could use "python2.3" instead of 
"python" and adjust the dependencies accordingly the packages would
work
in Ubuntu Breezy as well (I use Breezy because the distribute gnbd) and 
possibly in other Debian-based distributions.


Per.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Am Freitag, 27. Januar 2006 20:30 schrieb Per Andreas
Buer:
> Ralph Passgang wrote:
> > Hi,
> >
> > I just wanted to let all interessted debian users know, that on my
xen3
> > repository are now kernel images available for dom0/U.
> >
> > My Xen3 packages are using the latest xen3-testing (changeset 8269)
and
> > are available for sid, sarge & etch as well as for 32bit,
32bit-pae and
> > 64bit. The kernel image is 2.6.12.6-xen with a std. xen config.
>
> Thanks for the packages. If you could use "python2.3" instead of
> "python" and adjust the dependencies accordingly the packages
would work
> in Ubuntu Breezy as well (I use Breezy because the distribute gnbd) and
> possibly in other Debian-based distributions.
I never tested my packages in ubuntu for now, but got a similar report from 
another ubuntu user.

I will definitly take a look at this and will change the dependencies if it 
doen''t brake anything on debian sid, sarge or etch. It''s on
the todo list for
the next version. (I think available next week when 3.0.1 is released).

gnbd is also available on packages.debianbase.de. take a look at:
http://packages.debianbase.de/sarge/i386/gnbd/

But it''s really only gnbd (without the rest of the redhat cluster
suite) and I
am not very happy about the packages at all (a working but ugly hack). I 
would like to see at least a recent gnbd version in debian natively... I 
think I will submit a whishlist bug against the old and broken original gnbd 
packages which are still in unstable. I need gnbd myself and it
shouldn''t be
a problem for the maintainer to update the gnbd packages, don''t know
why this
didn''t happend in the last time. Maybe the debian guys could take the
ubuntu
solution if gnbd is working well there.
> Per.
--Ralph

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Mon, Jan 16, 2006 at 02:46:29PM +0100, Ralph Passgang
wrote:
> I just wanted to let all interessted debian users know, that on my xen3 
> repository are now kernel images available for dom0/U.
Hi Ralph,

I just switched to your sarge xen3 packages from working from source
- very nice work indeed!

My main reason for switching though was to get the vifname
functionality that recently got re-added to xen-testing.

So, the vif line in my domain''s config file now looks like:

vif    = [ ''mac=00:16:3e:6b:18:81, bridge=xenbr0,
vifname=vif-test.0'' ]

which is what I am used to having work in xen 2.x, but I see no
difference.  i.e. I still get the next vifx.0 interface.

Do you know if the syntax changed with xen3, or were your packages
made before this feature was added?

xen_changeset          : Mon Dec 12 18:47:47 2005 +0100 8270:4ad23e798798

Thanks,
Andy


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hi, 

the same problem i have figured out too.
but in my information ( xensource manual ), the syntax has not changed, and i 
have the newest packets got from xen3

stephan

Am Dienstag, 31. Januar 2006 12:06 schrieb Andy Smith:
> On Mon, Jan 16, 2006 at 02:46:29PM +0100, Ralph Passgang wrote:
> > I just wanted to let all interessted debian users know, that on my
xen3
> > repository are now kernel images available for dom0/U.
>
> Hi Ralph,
>
> I just switched to your sarge xen3 packages from working from source
> - very nice work indeed!
>
> My main reason for switching though was to get the vifname
> functionality that recently got re-added to xen-testing.
>
> So, the vif line in my domain''s config file now looks like:
>
> vif    = [ ''mac=00:16:3e:6b:18:81, bridge=xenbr0,
vifname=vif-test.0'' ]
>
> which is what I am used to having work in xen 2.x, but I see no
> difference.  i.e. I still get the next vifx.0 interface.
>
> Do you know if the syntax changed with xen3, or were your packages
> made before this feature was added?
>
> xen_changeset          : Mon Dec 12 18:47:47 2005 +0100 8270:4ad23e798798
>
> Thanks,
> Andy
-- 
Stephan Augustin
Rosenpark 3
65795 Hattersheim
06190/9355448
0173/1735867

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Tue, Jan 31, 2006 at 11:06:13AM +0000, Andy Smith
wrote:
> On Mon, Jan 16, 2006 at 02:46:29PM +0100, Ralph Passgang wrote:
> > I just wanted to let all interessted debian users know, that on my
xen3
> > repository are now kernel images available for dom0/U.
> 
> Hi Ralph,
> 
> I just switched to your sarge xen3 packages from working from source
> - very nice work indeed!
> 
> My main reason for switching though was to get the vifname
> functionality that recently got re-added to xen-testing.
Thanks to the archives of the list I answered my own question.  The
feature was readded to -unstable and is not yet present in -testing.
However it is only changes to xend so you can patch it in yourself
fairly easily it seems:

http://xenbits.xensource.com/xen-unstable.hg?cmd=changeset;node=95f84e37c90d573dd01cc29db5b81ffb5f86f84a

Appears to work.

Sorry for the noise, but at least here''s another hit for the
archive.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Am Dienstag, 31. Januar 2006 12:36 schrieb Andy Smith:
> On Tue, Jan 31, 2006 at 11:06:13AM +0000, Andy Smith wrote:
> > On Mon, Jan 16, 2006 at 02:46:29PM +0100, Ralph Passgang wrote:
> > > I just wanted to let all interessted debian users know, that on
my xen3
> > > repository are now kernel images available for dom0/U.
> >
> > Hi Ralph,
> >
> > I just switched to your sarge xen3 packages from working from source
> > - very nice work indeed!
> >
> > My main reason for switching though was to get the vifname
> > functionality that recently got re-added to xen-testing.
>
> Thanks to the archives of the list I answered my own question.  The
> feature was readded to -unstable and is not yet present in -testing.
> However it is only changes to xend so you can patch it in yourself
> fairly easily it seems:
>
> http://xenbits.xensource.com/xen-unstable.hg?cmd=changeset;node=95f84e37c90
>d573dd01cc29db5b81ffb5f86f84a
>
> Appears to work.
>
> Sorry for the noise, but at least here''s another hit for the
> archive.
I think xen 3.0.1 will be released within the next days. I guess from that 
point on the mssing feature will be available in the released and -testing 
trees again and so my packages will also support vifnames again.

If xen 3.0.1 isn''t released soon, then I will probably supply one last
3.0.0
package update (with your patch also included).

thx for the feedback.

--Ralph

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Tue, Jan 31, 2006 at 01:30:06PM +0100, Ralph Passgang
wrote:
> Am Dienstag, 31. Januar 2006 12:36 schrieb Andy Smith:
> > Thanks to the archives of the list I answered my own question.  The
> > feature was readded to -unstable and is not yet present in -testing.
> > However it is only changes to xend so you can patch it in yourself
> > fairly easily it seems:
> >
> >
http://xenbits.xensource.com/xen-unstable.hg?cmd=changeset;node=95f84e37c90
> >d573dd01cc29db5b81ffb5f86f84a
> >
> > Appears to work.
> >
> > Sorry for the noise, but at least here''s another hit for the
> > archive.
> 
> I think xen 3.0.1 will be released within the next days. I guess from that 
> point on the mssing feature will be available in the released and -testing 
> trees again and so my packages will also support vifnames again.
Thanks for these packages, Ralph, it''s nice to have a more
Debian-like way to manage the xen software and still have custom
kernels.
> If xen 3.0.1 isn''t released soon, then I will probably supply one
last 3.0.0
> package update (with your patch also included).
You probably didn''t mean to say it, but just to clarify, it''s
not my
patch :)  I just found the link to it in the archives and wouldn''t
have a clue how to do that myself.  Appears to be by Ewan Mellor.
Thanks Ewan!



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hi there again...


On Feb 6, 2006, at 23:01, Ralph Passgang wrote:
> Am Montag, 6. Februar 2006 22:32 schrieben Sie:
>
>> And a question for everyone... what method do people normally use to
>> generate the initramfs for the domU kernels?
>
> mkinitrd -o /boot/xen-modules-2.6.12.6-xen 2.6.12.6-xen
> (mkinitrd -o <outfile> <kernelversion>)
>
> debian unstable changed to yaird for creating initrd images, but I had
> problems with a software raid (even if was not the root device) and  
> so I
> personally switched back to mkinitrd. Debian sarge uses mkinitrd at  
> all and
> I''ve I remember right woody also used mkinitrd.
>
> But you should be able to use whatever "method" you want as long
as
> it''s
> mountable for the kernel. for supported types see the xen kernel  
> config
> (in /boot/config-2.6.12.6-xen if you installed my kernel linux- 
> xen0-2.6).
Ironically, yaird is what I use for dom0, in fact I had to since I  
ran into an upgrade problem with udev, the kernel, and mkinitrd...  
Fortunately, yaird saved me from that... the problem I have is with  
my domU kernels, since they need a different subset of modules than  
does my dom0. I was wondering if anyone had a generic solution for  
creating a domU initramfs without having to boot the aforementioned  
initramfs with all of the modules loaded.

At the moment I grab the initramfs created for my dom0 and modify it  
so that it is suitable for my domU. But I was really hoping that  
there was a better way.

Cheers,
Paul

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hi,

Am Sonntag, 29. Januar 2006 23:01 schrieb Ralph Passgang:
[..]
> gnbd is also available on packages.debianbase.de. take a look at:
> http://packages.debianbase.de/sarge/i386/gnbd/
> But it''s really only gnbd (without the rest of the redhat cluster
suite)
> and I am not very happy about the packages at all (a working but ugly
> hack). I would like to see at least a recent gnbd version in debian
> natively... I think I will submit a whishlist bug against the old and
> broken original gnbd packages which are still in unstable. I need gnbd
> myself and it shouldn''t be a problem for the maintainer to update
the gnbd
> packages, don''t know why this didn''t happend in the last
time. Maybe the
> debian guys could take the ubuntu solution if gnbd is working well there.
i really like these packages because they are __without__ the redhat cluster 
suite.
So with Xen 3.0.2 and kernel version 2.6.16 i need Version 1.02 instead of 
1.01 but in debian unstable they all depend on the cluster suite. Are there 
any packages without these dependencies like the packages on 
http://packages.debianbase.de/sarge/i386/gnbd/ ?


-- 
greetings

eMHa


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users