Xen users - Jul 2007 - Debian Etch DomU on SUSE SLES 10.SP1 Dom0

Hi,
I''am thinking about setting Etch DomU on SLES 10 SP1.
My server is 64-bit machine with Gigabit ethernet.
In HVM mode everything works fine, but I need more then 100 Mbit
ethernet for DomU (is it possible?)

What about PV? I''am looking for as stable as possible solution but I
don''t want to modify SLES kernel. So what kernel for DomU should I
choose?

1. Sles 10SP1 works on 2.6.16-46 with XEN 3.04++ (3.0.4_13138)
2. Debian Etch works on 2.6.18-4 with XEN 3.03.
3. XEN 3.04_1 from source is build on 2.6.16-33.
4. XEN 3.1 from source is build on 2.6.18.

Is that possible to have stable working DomU from XEN3.1-source on
Dom0 with XEN 3.0.4++ ?

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

Remigiusz Stachura wrote:
> [...]
> 1. Sles 10SP1 works on 2.6.16-46 with XEN 3.04++ (3.0.4_13138)
With SuSE kernels it''s a bit fiddling needed to get a Debian guest
running.
In general, you can run Suse, Fedora and Ubuntu as guests on Debian
quite fine with Debian kernels, but on SuSE and Fedora (OpenSuSE 10.2
and FC6 tested) running other distributions with their native Kernels is
a bit tricky - in fact, it works with SuSE once you found out how, with
Fedora I only got it working once to run Debian, but could never
reproduce it from scratch.
> 2. Debian Etch works on 2.6.18-4 with XEN 3.03.
This kernel should match Debian''s userspace tools best. Install this
kernel in your Debian guest, and run it either through pygrub(IIRC SuSE
has even anothe script to load Kernels from inside the guest filesystem,
but I have no SuSE at hand now) or copy it into /boot on the dom0 system
and configure your domains to use this Kernel and the matching initrd.
> 3. XEN 3.04_1 from source is build on 2.6.16-33.
> 4. XEN 3.1 from source is build on 2.6.18.
These should work, too, and I had success running Debian as guest on FC6
and OpenSuSE 10.2 with these.

But you don''t have security support and updates on these kernels, if
you
are interested in such things.
> 
> Is that possible to have stable working DomU from XEN3.1-source on
> Dom0 with XEN 3.0.4++ ?
The Hypervisor interface is frozen since a while, and these should be
compatible.

Henning

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

Henning Sprang wrote:
> 
> In general, you can run Suse, Fedora and Ubuntu as guests on Debian
> quite fine with Debian kernels
> 
Hi, I''ve tried to install a SLES10 SP1 guest on a xen-debian etch host,
but
without results.
I''ve tried to do the reverse thing but the best result is that the
kernel
hangs on the guest.

There is some documentation to install a SLES guest on a debian host ?
(I have a NON-HVM CPU  for the test).

Thanks.
Fabio.


-- 
View this message in context:
http://www.nabble.com/Debian-Etch-DomU-on-SUSE-SLES-10.SP1-Dom0-tf4136930.html#a11808290
Sent from the Xen - User mailing list archive at Nabble.com.


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

hi,


Bassgey schrieb:
> Hi, I''ve tried to install a SLES10 SP1 guest on a xen-debian etch
host, but
> without results.
> I''ve tried to do the reverse thing but the best result is that the
kernel
> hangs on the guest.
someone mailed me, that he was able to install SLES on a Debian Host
with a workaround. He bootet the whole system from a life SLES CD-Rom
and told yast to install the system into a folder.

After that he configured the fstab. let create the Xen config (suse.cfg)
 and use the debian kernel.

What is very important, to copy the modules into the system and after
the first start, notice the MAC inside and put it into the suse.cfg file.

i will to try install SLES with yum, but time is rare.

cu denny



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

Bassgey wrote:
> 
> Henning Sprang wrote:
>> In general, you can run Suse, Fedora and Ubuntu as guests on Debian
>> quite fine with Debian kernels
>>
> 
> Hi, I''ve tried to install a SLES10 SP1 guest on a xen-debian etch
host, but
> without results.
What do you mean with "without results"? What did you try exactly, and
what happened?

Sure, you need a base image, which you have to either bootstrap with
yum(a bit complicated) or build with
> I''ve tried to do the reverse thing but the best result is that the
kernel
> hangs on the guest.
> There is some documentation to install a SLES guest on a debian host ?
> (I have a NON-HVM CPU  for the test).
I have documented OpenSUSE 10.2 (not working with commercial stuff
normally) in german language in my book on Xen, I might try to write the
most important steps down in english somewhere.

Out of my head it''s not more than:

- build a minimal image with yast "install into directory" on a suse
host
- create your vm config on debian by hand or with xen-tools (use
no-install option to get an empty image and surpass the installation of
an OS)
- copy the stuff from the install into directory into the vm

And there you should be...

Henning

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

Denny Schierz wrote:
> [...]
> i will to try install SLES with yum, but time is rare.
I have the (very complex) command line for bootstrapping OpenSuSE 10.2
with yum somewhere.

You''ll need to figure somehow where to get the right package list for
SLES from, I guess, but it would be a start.

(then you don''t need the install into directory from a SALES host I
described before)

I once did this:

yum config:
=========
[main]
reposdir=/dev/null

[base]
name=Suse Linux - Base Repository
baseurl=http://ftp.hosteurope.de/mirror/ftp.opensuse.org/distribution/
10.2/
	http://suse.inode.at/opensuse/distribution/10.2/repo/oss/suse/
	http://ftp.gwdg.de/pub/opensuse/distribution/10.2/repo/oss/suse/
	http://ftp.tu-chemnitz.de/pub/linux/opensuse/distribution/10.2/
repo/oss/suse/
enabled=1


yum call:
========
yum -c yum-xen-suse.conf --exclude exim.i586
--installroot=/var/xen/domains/test-vm/imagemount -y install $(wget -O -
http://ftp.uni-ulm.de/mirrors/opensuse/distribution/10.2/repo/oss/suse/setup/descr/base-10.2-145.i586.pat
| sed -n ''/^+Prq:$/,/^+Psg:$/{ /:$/d; p; }'')

yum -c yum-xen-suse.conf
--installroot=/var/xen/domains/test-vm/imagemount -y install yum pwdutils


Not beautiful exactly, but the best I could get.

Henning

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

On Fri Jul 27, 2007 at 14:00:47 +0200, Henning Sprang wrote:
> I have the (very complex) command line for bootstrapping OpenSuSE 10.2
> with yum somewhere.
  I''ve been working on bootstrapping RPM-based distributions upon
 Debian hosts for a while now and will have OpenSUSE supported very
 shortly.

  See here for details:

        http://xen-tools.org/software/rinse

  Currently it supports Centos 4 & 5, Fedora Core 4-7, for both
 32 and 64 bits.

Steve
-- 

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

Steve Kemp wrote:
> [...]
>   See here for details:
> 
>         http://xen-tools.org/software/rinse
> [...]
Ah yes, I should know this very well, and I have it on my "to test"
list
since a while, just lacking time.

The problem with the SuSE thing is, it seems hard to find the list of
minimal needed packages - how will/did you solve this?

Did you already test rinse running on other distributions(assuming you
run it mostly on Debian)?
I have very mixed reports from people trying to run the yum stuff for
fedora under SLES and Ubuntu, for example.

Henning

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

On Fri Jul 27, 2007 at 15:37:45 +0200, Henning Sprang wrote:
> The problem with the SuSE thing is, it seems hard to find the list of
> minimal needed packages - how will/did you solve this?
  I used trial and error.  There aren''t too many packages which
 are required so it was mostly a matter of getting yum, then
 seeing which .so files were complained about when you tried
 to run a binary...
> Did you already test rinse running on other distributions(assuming you
> run it mostly on Debian)?
  Tested on Ubuntu + Debian only.  It almost certainly will fail
 upon other hosts, since it uses ''alien'' as a middle-step.

  Still that can be fixed.  I just need some process to unpack
 a .rpm file without using rpm directly and I''m sure some magic
 combination of ar, etc, will allow that to work.

Steve
-- 
# Commercial Debian GNU/Linux Support
http://www.linux-administration.org/


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

Steve Kemp wrote:
> [...]
>> Did you already test rinse running on other distributions(assuming you
>> run it mostly on Debian)?
> 
>   Tested on Ubuntu + Debian only.  It almost certainly will fail
>  upon other hosts, since it uses ''alien'' as a
middle-step.
Yes, last time I checked (FC6) there was no alien on Fedora, and install
instructions I found all sound complex.
On SuSE, alien is available.

But, yes, simply unpacking it with more generic tools is easier (hmm, I
think cpio is your friend here IIRC - or was that debian?).

Henning

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

Steve Kemp wrote:
>   I''ll spend a while tonight getting this sorted.  I''ve
not been
>  able to find explicit instructions anywhere, but it should be
>  simple enough.
Maybe I''m wrong, cpio seems to be only an intermediate tool to unpack
rpms:
http://www.rpm.org/max-rpm/s1-rpm-miscellania-rpm2cpio.html

When I think about it - why do you want to do it without rpm, anyway?

Doesn''t the yum dirinstall require rpm to be available, and an (empty,
and never actiually used) rpm db on the host being there, anyway?
(I might have missed some command line options to circumvent this, but
remember something that I needed these) - or is it exactly that you are
going to work around?

Can''t you make rpm a dependency for rinse - in the end, people want to
do rpm stuff, so the basic tool for this can be expected...

Henning

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

On Fri Jul 27, 2007 at 16:27:39 +0200, Henning Sprang wrote:
> Maybe I''m wrong, cpio seems to be only an intermediate tool to
unpack rpms:
> http://www.rpm.org/max-rpm/s1-rpm-miscellania-rpm2cpio.html
  Yes it looks simple enough:

  rpm2cpio foo.rpm | (cd /tmp/lah ; cpio --extract --make-directories \
  --no-absolute-filenames --preserve-modification-time) 2>&1
> When I think about it - why do you want to do it without rpm, anyway?
  My tool is .. non-standard .. and broken.

  (Sadly).

  The basic process goes:

   1.  Download each package which I''ve manually determined to be
      required to result in a working ''rpm'' +
''yum'' command.
      (There are about 50 packages.)

   2.  Unpack each one.  Currently this is a hack[*]

   3.  Once you''ve unpacked them you''ll have a working system
with
       yum + rpm, and from there you can bootstrap the yum + rpm
       database.

  The *only* place I currently use yum/rpm is in the second step.
  At the time I started writing I had a simple idea of how to
  unpack rpms.  This goes:

     for i in *.rpm; do 
        alien --to-tgz $i
        rm $i
     done
     for i in *.tgz; do
        tar -zxf $i
        rm $i
     done

  As you can see this is nasty, but surprisingly it all actually
 works.  There aren''t many packages required to get RPM + Yum working
 just things like libssl, so having a static list of packages is
 not a big deal to maintain - I don''t hard-wire the *version* of the
 packages so it is future-proof, unlike rpmstrap.

  With the rpm2cpio usage I can now drop the dependency upon alien
 and the script *should* be completely portable to any system which
 has a native rpm + rpm2cpio command :)

Steve
-- 
Debian GNU/Linux System Administration
http://www.debian-administration.org/


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