RE: Using Debian packages

RE: Using Debian packages

[Ian Pratt]

> Does the 2.0.5 packages (kernel-patch-xen_2.0.5-1_i386.deb) 
> apply to Debian 
> kernels in the Sarge tree which is 2.6.8 at the moment?
> 
> If so, is it possible to build a domU kernel using the debian 
> packages too?

If you've got a kernel built with all the drivers as modules, then
there's little point building a separate domU kernel -- just use the
same for privileged and unprivileged domains.


Ian


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click

Re: Using Debian packages

[Lars E. D. Jensen]

Onsdag den 16. marts 2005 09:17 skrev Ian Pratt:
> > Does the 2.0.5 packages (kernel-patch-xen_2.0.5-1_i386.deb)
> > apply to Debian
> > kernels in the Sarge tree which is 2.6.8 at the moment?
> >
> > If so, is it possible to build a domU kernel using the debian
> > packages too?
>
> If you've got a kernel built with all the drivers as modules, then
> there's little point building a separate domU kernel -- just use the
> same for privileged and unprivileged domains.

Hmmm... I really have problems using those packages.

Is there someone who is using those packages, if so... how do you use them?

What kernel-source (from where) are you patching?

Maybe a small step-by-step guide would be good.

My problem is that I can't get a kernel compiled "the debian way" ... into a 
debian package.

I'm not sure if I should use vanilla or not, but I've downloaded the vanilla 
2.6.10 which kernel-patch-xen_2.0.5-1_i386.deb is for (I think). I've 
installed kernel-patch-xen_2.0.5-1_i386.deb and then copied my .config into 
source directory and run:
make-kpkg --added-patches=xen --revision=xenserver.0.1 kernel_image

It compiles fine, but is this the right way of doing it if I want a debian 
package?

"make ARCH=xen menuconfig" fails since there is no xen arch in vanilla.

Also I get this when trying to install the 2.0.5 Debian packages:
Python C API version mismatch for module xen.lowlevel.xu: This Python has API 
version 1012, module xen.lowlevel.xu has version 1011.

Thanks.

-- 
Med venlig hilsen / Best regards
Lars E. D. Jensen 
lars@dangvard.dk


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Using Debian packages

[Nuutti Kotivuori]

Lars E. D. Jensen wrote:
> Onsdag den 16. marts 2005 09:17 skrev Ian Pratt:
>>> Does the 2.0.5 packages (kernel-patch-xen_2.0.5-1_i386.deb)
>>> apply to Debian
>>> kernels in the Sarge tree which is 2.6.8 at the moment?
>>>
>>> If so, is it possible to build a domU kernel using the debian
>>> packages too?
>>
>> If you've got a kernel built with all the drivers as modules, then
>> there's little point building a separate domU kernel -- just use
>> the same for privileged and unprivileged domains.
>
> Hmmm... I really have problems using those packages.
>
> Is there someone who is using those packages, if so... how do you
> use them?
>
> What kernel-source (from where) are you patching?
>
> Maybe a small step-by-step guide would be good.
>
> My problem is that I can't get a kernel compiled "the debian way"
> ... into a debian package.
>
> I'm not sure if I should use vanilla or not, but I've downloaded the
> vanilla 2.6.10 which kernel-patch-xen_2.0.5-1_i386.deb is for (I
> think). I've installed kernel-patch-xen_2.0.5-1_i386.deb and then
> copied my .config into source directory and run: make-kpkg
> --added-patches=xen --revision=xenserver.0.1 kernel_image
>
> It compiles fine, but is this the right way of doing it if I want a
> debian package?
>
> "make ARCH=xen menuconfig" fails since there is no xen arch in
> vanilla.
>
> Also I get this when trying to install the 2.0.5 Debian packages:
> Python C API version mismatch for module xen.lowlevel.xu: This
> Python has API version 1012, module xen.lowlevel.xu has version
> 1011.

Close, but not quite.

You can take a vanilla 2.6.10 or the Debian patched 2.6.10. I would
recommend the Debian patched one. You uncompress the kernel-source
somewhere, copy in your .config, that is fine.

The command you wish to run is:

  make-kpkg --added-patches=xen --arch=xen --subarch=xen0 --revision=xenserver.0.1 debian

This patches the kernel and creates the ./debian directory in your
source. After that you can run:

  make ARCH=xen menuconfig

And tune it to your liking. And after that, you compile the kernel:

  make-kpkg --added-patches=xen --arch=xen --subarch=xen0 --revision=xenserver.0.1 kernel-image

And you are done. Not all of the flags need to be present in all
phases, but it doesn't hurt either. Do also note that make-kpkg has
some problems with --initrd combined with --arch=xen, so don't do
that.

-- Naked



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Re: Using Debian packages

[Lars E. D. Jensen]

> Close, but not quite.
>
> You can take a vanilla 2.6.10 or the Debian patched 2.6.10. I would
> recommend the Debian patched one. You uncompress the kernel-source
> somewhere, copy in your .config, that is fine.
>
> The command you wish to run is:
>
>   make-kpkg --added-patches=xen --arch=xen --subarch=xen0
> --revision=xenserver.0.1 debian
>
> This patches the kernel and creates the ./debian directory in your
> source. After that you can run:
>
>   make ARCH=xen menuconfig
>
> And tune it to your liking. And after that, you compile the kernel:
>
>   make-kpkg --added-patches=xen --arch=xen --subarch=xen0
> --revision=xenserver.0.1 kernel-image
>
> And you are done. Not all of the flags need to be present in all
> phases, but it doesn't hurt either. Do also note that make-kpkg has
> some problems with --initrd combined with --arch=xen, so don't do
> that.

Thanks a lot for outlining the steps above.

But since I haven't succeeded in getting any xen kernel to boot yet, I 
probably need to spell out what I've done so far (at least for my self)...
I haven't really used grub until now, so maybe that's a reason to my troubles.

I was able to compile and install the kernel for dom0.
After install /boot directory now looks like this:

-rw-r--r--   1 root root  542011 Jan 20 03:47 System.map-2.4.27-2-386
-rw-r--r--   1 root root  546234 Mar 18 00:35 System.map-2.6.10
-rw-r--r--   1 root root       0 Mar 18 17:47 bootdir.txt
-rw-r--r--   1 root root   44853 Jan 20 02:53 config-2.4.27-2-386
-rw-r--r--   1 root root   25807 Mar 18 00:23 config-2.6.10
drwxr-xr-x   2 root root    1024 Mar 18 16:08 grub
-rw-r--r--   1 root root 3878912 Mar 18 16:07 initrd.img-2.4.27-2-386
drwxr-xr-x   2 root root   12288 Mar 18 16:03 lost+found
-rw-r--r--   1 root root      39 Mar 18 00:35 patches-2.6.10
-rw-r--r--   1 root root  816260 Jan 20 03:47 vmlinuz-2.4.27-2-386
-rw-r--r--   1 root root  115165 Mar 18 17:08 xen-linux-2.6.10

And I manually added this to /boot/grub/menu.lst:

title  XenLinux 2.0.5
root  (hd0,0)
kernel /boot/xen.gz dom0_mem=131072
module /boot/xen-linux-2.6.10 root=/dev/sda6 ro console=tty0

Nomatter what I've done so far I get grub error 15:

15 : File not found
This error is returned if the specified file name cannot be found,
but everything else (like the disk/partition info) is OK.

I more or less just pasted the menu.lst from documentation with a few changes. 
And noticed that xen kernerl xen.gz is missing in /boot directory. I've then 
tried to copy xen.gz from xen binary distribution, but I still get error 15.

Any help is really appriciated since I've been struggling with this for quite 
a while.

Thanks 
-- 
Med venlig hilsen / Best regards
Lars E. D. Jensen 
lars@dangvard.dk


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Re: Using Debian packages

[M.A. Williamson]

> title  XenLinux 2.0.5
> root  (hd0,0)
> kernel /boot/xen.gz dom0_mem=131072
> module /boot/xen-linux-2.6.10 root=/dev/sda6 ro console=tty0

Looks OK.

> 
> Nomatter what I've done so far I get grub error 15:
> 
> 15 : File not found
> This error is returned if the specified file name cannot be found,
> but everything else (like the disk/partition info) is OK.

What does your menu.lst entry for vanilla Linux look like? What does your 
/etc/fstab look like (i.e. do you have a /boot partition or something else 
that's throwing off your grub setup?)

> I more or less just pasted the menu.lst from documentation with a few 
> changes. And noticed that xen kernerl xen.gz is missing in /boot 
> directory. I've then tried to copy xen.gz from xen binary distribution, 
> but I still get error 15.

Hrm... Copying it in should work. Could you please do an ls -l of your 
/boot?

Cheers,
Mark

> Any help is really appriciated since I've been struggling with this for 
> quite a while.
> 
> Thanks 
> 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Re: Using Debian packages

[Lars E. D. Jensen]

> What does your menu.lst entry for vanilla Linux look like? What does your
> /etc/fstab look like (i.e. do you have a /boot partition or something else
> that's throwing off your grub setup?)

/boot/grub/menu.lst:
## ## End Default Options ##

title           Debian GNU/Linux, kernel 2.4.27-2-386
root            (hd0,0)
kernel          /vmlinuz-2.4.27-2-386 root=/dev/sda6 ro
initrd          /initrd.img-2.4.27-2-386
savedefault
boot

title           Debian GNU/Linux, kernel 2.4.27-2-386 (recovery mode)
root            (hd0,0)
kernel          /vmlinuz-2.4.27-2-386 root=/dev/sda6 ro single
initrd          /initrd.img-2.4.27-2-386
savedefault
boot

### END DEBIAN AUTOMAGIC KERNELS LIST

title           XenLinux 2.0.5 SMP
root            (hd0,0)
kernel          /boot/xen.gz dom0_mem=131072
module          /boot/xen-linux-2.6.10 root=/dev/sda6 ro console=tty0


/etc/fstab :
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
/dev/sda6       /               ext3    defaults,errors=remount-ro 0       1
/dev/sda1       /boot           ext3    defaults        0       2
/dev/sda5       none            swap    sw              0       0
/dev/hdd        /media/cdrom0   iso9660 ro,user,noauto  0       0
/dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0

> > I more or less just pasted the menu.lst from documentation with a few
> > changes. And noticed that xen kernerl xen.gz is missing in /boot
> > directory. I've then tried to copy xen.gz from xen binary distribution,
> > but I still get error 15.
>
> Hrm... Copying it in should work. Could you please do an ls -l of your
> /boot?

I all ready posted that in a former mail, except from that I copied xen.gz 
from binary xen distribution into /boot/...


-- 
Med venlig hilsen / Best regards
Lars E. D. Jensen 
lars@dangvard.dk


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Re: Using Debian packages

[Mark Williamson]

Here's the difference:

This one works...

> title           Debian GNU/Linux, kernel 2.4.27-2-386
> root            (hd0,0)
> kernel          /vmlinuz-2.4.27-2-386 root=/dev/sda6 ro
------------------^
No /boot here.


This one doesn't...

> title           XenLinux 2.0.5 SMP
> root            (hd0,0)
> kernel          /boot/xen.gz dom0_mem=131072
------------------^
Path includes /boot

Bear in mind the "root (hd0,0)" directive doesn't tell grub "this is my / 
(root) filesystem", it means "interpret path references relative to the root 
of this partition's filesystem".

> # <file system> <mount point>   <type>  <options>       <dump>  <pass>
> proc            /proc           proc    defaults        0       0
> /dev/sda6       /               ext3    defaults,errors=remount-ro 0      
> 1 /dev/sda1       /boot           ext3    defaults        0       2

On your system /dev/sda1 == (hd0,0) and is your boot partition, so you only 
need to specify the location of a kernel / module within this partition.

Try this in your menu.lst:

title           XenLinux 2.0.5 SMP
root            (hd0,0)
kernel          /xen.gz dom0_mem=131072
module          /xen-linux-2.6.10 root=/dev/sda6 ro console=tty0

HTH,
Mark

> /dev/sda5       none            swap    sw              0       0
> /dev/hdd        /media/cdrom0   iso9660 ro,user,noauto  0       0
> /dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0
>
> > > I more or less just pasted the menu.lst from documentation with a few
> > > changes. And noticed that xen kernerl xen.gz is missing in /boot
> > > directory. I've then tried to copy xen.gz from xen binary distribution,
> > > but I still get error 15.
> >
> > Hrm... Copying it in should work. Could you please do an ls -l of your
> > /boot?
>
> I all ready posted that in a former mail, except from that I copied xen.gz
> from binary xen distribution into /boot/...


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Re: Using Debian packages

[Lars E. D. Jensen]

> Try this in your menu.lst:
>
> title           XenLinux 2.0.5 SMP
> root            (hd0,0)
> kernel          /xen.gz dom0_mem=131072
> module          /xen-linux-2.6.10 root=/dev/sda6 ro console=tty0

Ok, major progress. It now boots, but I get this when booting:

---snip--- 
LOADING DOMAIN 0
Not a Xen-ELF image: '__xen_guest' sect...

**************
Could not set up DOM0 guest OS
Aieee! CPU0 is toast...
**************
---snip---

Ok, it would be very strange if CPU0 is toast since it's a brand new server 
and it boots with normal images.

I've compiled a debian package of the kernel for dom0.
And I've copied xen.gz from xen binary distribution.

Even though I copied xen.gz from xen binary dist, the compiled kernel has the 
exact same size as xen.gz.
Should xen.gz and xen-linux-2.6.10 be the same kernel? 

Thanks.

-- 
Med venlig hilsen / Best regards
Lars E. D. Jensen 
lars@dangvard.dk


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Using Debian packages

[Nuutti Kotivuori]

Lars E. D. Jensen wrote:
>> Try this in your menu.lst:
>>
>> title           XenLinux 2.0.5 SMP
>> root            (hd0,0)
>> kernel          /xen.gz dom0_mem=131072
>> module          /xen-linux-2.6.10 root=/dev/sda6 ro console=tty0
>
> Ok, major progress. It now boots, but I get this when booting:
>
> ---snip--- 
> LOADING DOMAIN 0
> Not a Xen-ELF image: '__xen_guest' sect...
>
> **************
> Could not set up DOM0 guest OS
> Aieee! CPU0 is toast...
> **************
> ---snip---
>
> Ok, it would be very strange if CPU0 is toast since it's a brand new
> server and it boots with normal images.
>
> I've compiled a debian package of the kernel for dom0.
> And I've copied xen.gz from xen binary distribution.
>
> Even though I copied xen.gz from xen binary dist, the compiled
> kernel has the exact same size as xen.gz.  Should xen.gz and
> xen-linux-2.6.10 be the same kernel?
>
> Thanks.

xen.gz is the hypervisor. xen-linux-2.6.10 is your kernel. They should
*not* be the same size at all:

-rw-r--r--  1 root root  116602 Feb  4 00:40 /boot/xen.gz
-rw-r--r--  1 root root 2210694 Feb  9 01:36 /boot/xen-linux-2.6.10-xen0-shiro-1

Please reinstall the debian package you made with make-kpkg, you've
probably corrupted your kernel binary somehow.

-- Naked




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Re: Using Debian packages

[Lars E. D. Jensen | DCmedia]

> xen.gz is the hypervisor. xen-linux-2.6.10 is your kernel. They should
> *not* be the same size at all:
>
> -rw-r--r--  1 root root  116602 Feb  4 00:40 /boot/xen.gz
> -rw-r--r--  1 root root 2210694 Feb  9 01:36
> /boot/xen-linux-2.6.10-xen0-shiro-1
>
> Please reinstall the debian package you made with make-kpkg, you've
> probably corrupted your kernel binary somehow.

Ok, should the debian package I've created also generate a xen.gz file 
in /boot?

Or should the xen.gz be copied from the binary dist allways?

I've reinstalled now, but now I get kernel panic with some message "unknown 
bootoptions", it reboots in 1 sec and I'm not able to read that fast! :/

-- 
Med venlig hilsen / Best regards
Lars E. D. Jensen - DCmedia - TYPO3 Business Solutions
+45 3695 9177
ledj@dcmedia.biz - http://dcmedia.biz


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Using Debian packages

[Nuutti Kotivuori]

Lars E. D. Jensen wrote:
>> xen.gz is the hypervisor. xen-linux-2.6.10 is your kernel. They
>> should *not* be the same size at all:
>>
>> -rw-r--r--  1 root root  116602 Feb  4 00:40 /boot/xen.gz
>> -rw-r--r--  1 root root 2210694 Feb  9 01:36
>> /boot/xen-linux-2.6.10-xen0-shiro-1
>>
>> Please reinstall the debian package you made with make-kpkg, you've
>> probably corrupted your kernel binary somehow.
>
> Ok, should the debian package I've created also generate a xen.gz
> file in /boot?

No, it is not included in the packages. However, I think that is a bug
in the packages - xen.gz should be included, otherwise they are
useless.

> Or should the xen.gz be copied from the binary dist allways?

For now, you should copy it.

> I've reinstalled now, but now I get kernel panic with some message
> "unknown bootoptions", it reboots in 1 sec and I'm not able to read
> that fast! :/

Add 'noreboot' on the line where you load xen.gz in grub.

-- Naked



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Re: Using Debian packages

[Tommi Virtanen]

Nuutti Kotivuori wrote:
>>Ok, should the debian package I've created also generate a xen.gz
>>file in /boot?
> No, it is not included in the packages. However, I think that is a bug
> in the packages - xen.gz should be included, otherwise they are
> useless.

/boot/xen.gz is in xen.deb.


-------------------------------------------------------
This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
for the chance to win $25,000 and application distribution. Enter today at
http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click

Re: Re: Using Debian packages

[Nuutti Kotivuori]

Tommi Virtanen wrote:
> Nuutti Kotivuori wrote:
>>> Ok, should the debian package I've created also generate a xen.gz
>>> file in /boot?
>> No, it is not included in the packages. However, I think that is a
>> bug in the packages - xen.gz should be included, otherwise they are
>> useless.
>
> /boot/xen.gz is in xen.deb.

Ah, sorry, I was still using the 2.0.4-3 debs and not the 2.0.5-3
debs. Apparently this was fixed in 2.0.4-4.

-- Naked



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Re: Using Debian packages

[Lars E. D. Jensen]

> xen.gz is the hypervisor. xen-linux-2.6.10 is your kernel. They should
> *not* be the same size at all:
>
> -rw-r--r--  1 root root  116602 Feb  4 00:40 /boot/xen.gz
> -rw-r--r--  1 root root 2210694 Feb  9 01:36
> /boot/xen-linux-2.6.10-xen0-shiro-1
>
> Please reinstall the debian package you made with make-kpkg, you've
> probably corrupted your kernel binary somehow.

Ok, should the debian package I've created also generate a xen.gz file 
in /boot?

Or should the xen.gz be copied from the binary dist allways?

I've reinstalled now, but now I get kernel panic with some message "unknown 
bootoptions", it reboots in 1 sec and I'm not able to read that fast! :/

-- 
Med venlig hilsen / Best regards
Lars E. D. Jensen 
lars@dangvard.dk


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Re: Using Debian packages

[Lars E. D. Jensen]

Lørdag den 19. marts 2005 16:48 skrev Lars E. D. Jensen:
> > xen.gz is the hypervisor. xen-linux-2.6.10 is your kernel. They should
> > *not* be the same size at all:
> >
> > -rw-r--r--  1 root root  116602 Feb  4 00:40 /boot/xen.gz
> > -rw-r--r--  1 root root 2210694 Feb  9 01:36
> > /boot/xen-linux-2.6.10-xen0-shiro-1
> >
> > Please reinstall the debian package you made with make-kpkg, you've
> > probably corrupted your kernel binary somehow.
>
> Ok, should the debian package I've created also generate a xen.gz file
> in /boot?
>
> Or should the xen.gz be copied from the binary dist allways?
>
> I've reinstalled now, but now I get kernel panic with some message "unknown
> bootoptions", it reboots in 1 sec and I'm not able to read that fast! :/

The server boots just fine now, I used the shipped .config from the source 
dist. I guess I has a misconfiguration with make ARCH=xen oldconfig...

Thanks.

-- 
Med venlig hilsen / Best regards
Lars E. D. Jensen 
lars@dangvard.dk


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click

Re: Re: Using Debian packages

[Adam Heath]

On Sat, 19 Mar 2005, Lars E. D. Jensen wrote:

> > xen.gz is the hypervisor. xen-linux-2.6.10 is your kernel. They should
> > *not* be the same size at all:
> >
> > -rw-r--r--  1 root root  116602 Feb  4 00:40 /boot/xen.gz
> > -rw-r--r--  1 root root 2210694 Feb  9 01:36
> > /boot/xen-linux-2.6.10-xen0-shiro-1
> >
> > Please reinstall the debian package you made with make-kpkg, you've
> > probably corrupted your kernel binary somehow.
>
> Ok, should the debian package I've created also generate a xen.gz file
> in /boot?

No, that file is in xen.deb.

> Or should the xen.gz be copied from the binary dist allways?
>
> I've reinstalled now, but now I get kernel panic with some message "unknown
> bootoptions", it reboots in 1 sec and I'm not able to read that fast! :/

Add panic=0 to the second module line, and use a serial console.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Using Debian packages

[michal urbanski]

I gave up on compiling a kernel the debian way... once I applied the
xen patch by running /usr/src/kernel-patches/i386/apply/xen from
/usr/src/linux, I did the whole "make ARCH=xen" and manually copied the
resulting vmlinuz to /boot/vmlinuz-2.6.10-xen0.

Now, has anyone else had problems with these debian packages? I've built
a U kernel with my same config, and am using this as my vm config:

kernel = "/boot/vmlinuz-2.6.10-xenU"
memory = 256 
name = "test"
disk = ['file:/var/lib/xen/diskimages/test_disk,sda1,w']
disk = ['file:/var/lib/xen/diskimages/test_swap_disk,sda2,w']
root = "/dev/sda1 rw"
restart = 'never'

but whenever I try "xm create -f vm_test", all I get is:

Using config file "./vm_test".
Error: Not Found

Any possible explanations? Have I done something braindead in my vm
config?

-michal urbanski


On Thu, Mar 17, 2005 at 04:48:08PM +0100, Lars E. D. Jensen wrote:
> Onsdag den 16. marts 2005 09:17 skrev Ian Pratt:
> > > Does the 2.0.5 packages (kernel-patch-xen_2.0.5-1_i386.deb)
> > > apply to Debian
> > > kernels in the Sarge tree which is 2.6.8 at the moment?
> > >
> > > If so, is it possible to build a domU kernel using the debian
> > > packages too?
> >
> > If you've got a kernel built with all the drivers as modules, then
> > there's little point building a separate domU kernel -- just use the
> > same for privileged and unprivileged domains.
> 
> Hmmm... I really have problems using those packages.
> 
> Is there someone who is using those packages, if so... how do you use them?
> 
> What kernel-source (from where) are you patching?
> 
> Maybe a small step-by-step guide would be good.
> 
> My problem is that I can't get a kernel compiled "the debian way" ... into a 
> debian package.
> 
> I'm not sure if I should use vanilla or not, but I've downloaded the vanilla 
> 2.6.10 which kernel-patch-xen_2.0.5-1_i386.deb is for (I think). I've 
> installed kernel-patch-xen_2.0.5-1_i386.deb and then copied my .config into 
> source directory and run:
> make-kpkg --added-patches=xen --revision=xenserver.0.1 kernel_image
> 
> It compiles fine, but is this the right way of doing it if I want a debian 
> package?
> 
> "make ARCH=xen menuconfig" fails since there is no xen arch in vanilla.
> 
> Also I get this when trying to install the 2.0.5 Debian packages:
> Python C API version mismatch for module xen.lowlevel.xu: This Python has API 
> version 1012, module xen.lowlevel.xu has version 1011.
> 
> Thanks.
> 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click