Using Debian packages

Using Debian packages

[Lars E. D. Jensen]

Hi list

I'm about to install XenLinux on Debian. And I noticed this repository was 
submitted to this list a while ago:

http://people.debian.org/~doogie/xen/

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?

Or should I manually compile a domU from the original Xen 2.0.5 source?

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

[Ted Hilts]

Lars

Someone more informed on this than me will probably give you an answer. 
 Until you asked, I just assumed that was the case.

You might be interested in the following:

There is now a beta2 version of the Live Xen CD which I understand is an 
Xen-(Debian) Linux based system now hosting several OS's.  Have not 
tried it myself but saw several postings (very positive).  My only hold 
up is the download which I have arranged to have done on my hehalf by 
another party and has not yet been done.  I am looking forward to 
running this Live Xen system CD (also Xenoboot -- after I build my own 
Xen system).  You might benefit by getting and running the CD before you 
actually do what you are planning because there seem to be a lot of 
similarities.  What is nice about this well made CD is that it works 
"out of the box" so one does not have to struggle with compilation 
issues and other things while they learn about Xen. I believe (someone 
correct me if I am mistaken) that the Live CD comes with all the tools 
you need and this would give us all the opportunity to analyze the 
performance and play with the tools -- something I very much need to do 
in order to understand some of the problems and solutions set out on 
this list. Apparently (from the CD) , you can create additional virtual 
systems and even migrate them. I don't know how they actually make this 
happen from a CD but the people involved with it's making and Xen are a 
sharp bunch.

BTW:  The SuSE list is starting to show a lot of interest in Xen and 
leading Linux magazines and news sources are producing articles on Xen.

If you get the CD let the list know if there are any problems.

Thanks -- Ted

Lars E. D. Jensen wrote:

>Hi list
>
>I'm about to install XenLinux on Debian. And I noticed this repository was 
>submitted to this list a while ago:
>
>http://people.debian.org/~doogie/xen/
>
>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?
>
>Or should I manually compile a domU from the original Xen 2.0.5 source?
>
>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: Using Debian packages

[Nuutti Kotivuori]

Lars E. D. Jensen wrote:
> I'm about to install XenLinux on Debian. And I noticed this
> repository was submitted to this list a while ago:
>
> http://people.debian.org/~doogie/xen/
>
> 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?

Most likely not. Xen 2.0.5 does not work with 2.6.8, AFAIK.

> If so, is it possible to build a domU kernel using the debian
> packages too?

It is possible. Just use make-kpkg. make-kpkg --arch=xen
--subarch=xenu would be the way. (As opposed to make-kpkg --arch=xen
--subarch=xen0).

> Or should I manually compile a domU from the original Xen 2.0.5
> source?

You can do that as well - but you will not get the debian patches to
stock kernels that way.

-- 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: Using Debian packages

[Ian Pratt]

 

Please can you see if there's a more helpful error report in
/var/log/xend.log or /var/log/xend-debug.log

Thanks,
Ian

> 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
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
> 


-------------------------------------------------------
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

[michal urbanski]

xen.log:

[2005-03-17 14:14:36 xend] INFO (SrvDaemon:610) Xend Daemon started
[2005-03-17 14:14:36 xend] INFO (XendRoot:91) EVENT> xend.start 0

network start bridge=xen-br0 netdev=eth0 antispoof=no
Traceback (most recent call last):
  File "/usr/sbin/xend", line 121, in ?
    sys.exit(main())
  File "/usr/sbin/xend", line 107, in main
    return daemon.start()
  File "/usr/lib/python2.3/site-packages/xen/xend/server/SrvDaemon.py", line 525, in start
    self.run()
  File "/usr/lib/python2.3/site-packages/xen/xend/server/SrvDaemon.py", line 615, in run
    SrvServer.create(bridge=1)
  File "/usr/lib/python2.3/site-packages/xen/xend/server/SrvServer.py", line 50, in create
    reactor.listenTCP(port, site, interface=interface)
  File "/usr/lib/python2.3/site-packages/twisted/internet/default.py", line 283, in listenTCP
    p.startListening()
  File "/usr/lib/python2.3/site-packages/twisted/internet/tcp.py", line 594, in startListening
    raise CannotListenError, (self.interface, self.port, le)
twisted.internet.error.CannotListenError: Couldn't listen on any:8000: (98, 'Address already in use').

... which is from when I first started it with "(xend-port 8000)" in /etc/xend-config.sxp, but
which I then changed to 6000. 

ps auxf|grep xen shows:

root       725  0.0  0.0     0    0 ?        S    14:06   0:00 [xenblkd]
root      1503  0.6  5.9 10000 7476 ?        S    15:18   0:00 python /usr/sbin/xend start


I hope some of this is useful.

-michal urbanski


On Thu, Mar 17, 2005 at 11:11:33PM -0000, Ian Pratt wrote:
>  
> 
> Please can you see if there's a more helpful error report in
> /var/log/xend.log or /var/log/xend-debug.log
> 
> Thanks,
> Ian
> 
> > 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
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/xen-devel
> > 


-------------------------------------------------------
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

[Adam Heath]

On Thu, 17 Mar 2005, michal urbanski wrote:

> xen.log:
>
> [2005-03-17 14:14:36 xend] INFO (SrvDaemon:610) Xend Daemon started
> [2005-03-17 14:14:36 xend] INFO (XendRoot:91) EVENT> xend.start 0
>
> network start bridge=xen-br0 netdev=eth0 antispoof=no
> Traceback (most recent call last):
>   File "/usr/sbin/xend", line 121, in ?
>     sys.exit(main())
>   File "/usr/sbin/xend", line 107, in main
>     return daemon.start()
>   File "/usr/lib/python2.3/site-packages/xen/xend/server/SrvDaemon.py", line 525, in start
>     self.run()
>   File "/usr/lib/python2.3/site-packages/xen/xend/server/SrvDaemon.py", line 615, in run
>     SrvServer.create(bridge=1)
>   File "/usr/lib/python2.3/site-packages/xen/xend/server/SrvServer.py", line 50, in create
>     reactor.listenTCP(port, site, interface=interface)
>   File "/usr/lib/python2.3/site-packages/twisted/internet/default.py", line 283, in listenTCP
>     p.startListening()
>   File "/usr/lib/python2.3/site-packages/twisted/internet/tcp.py", line 594, in startListening
>     raise CannotListenError, (self.interface, self.port, le)
> twisted.internet.error.CannotListenError: Couldn't listen on any:8000: (98, 'Address already in use').
>
> ... which is from when I first started it with "(xend-port 8000)" in /etc/xend-config.sxp, but
> which I then changed to 6000.

netstat -anp | grep 8000

Plus, you aren't using the debian packages.  There is no such file
/etc/xend-config.sxp.



-------------------------------------------------------
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]

On Thu, Mar 17, 2005 at 06:03:20PM -0600, Adam Heath wrote:
> On Thu, 17 Mar 2005, michal urbanski wrote:
> 
> > xen.log:
> >
> > [2005-03-17 14:14:36 xend] INFO (SrvDaemon:610) Xend Daemon started
> > [2005-03-17 14:14:36 xend] INFO (XendRoot:91) EVENT> xend.start 0
> >
> > network start bridge=xen-br0 netdev=eth0 antispoof=no
> > Traceback (most recent call last):
> >   File "/usr/sbin/xend", line 121, in ?
> >     sys.exit(main())
> >   File "/usr/sbin/xend", line 107, in main
> >     return daemon.start()
> >   File "/usr/lib/python2.3/site-packages/xen/xend/server/SrvDaemon.py", line 525, in start
> >     self.run()
> >   File "/usr/lib/python2.3/site-packages/xen/xend/server/SrvDaemon.py", line 615, in run
> >     SrvServer.create(bridge=1)
> >   File "/usr/lib/python2.3/site-packages/xen/xend/server/SrvServer.py", line 50, in create
> >     reactor.listenTCP(port, site, interface=interface)
> >   File "/usr/lib/python2.3/site-packages/twisted/internet/default.py", line 283, in listenTCP
> >     p.startListening()
> >   File "/usr/lib/python2.3/site-packages/twisted/internet/tcp.py", line 594, in startListening
> >     raise CannotListenError, (self.interface, self.port, le)
> > twisted.internet.error.CannotListenError: Couldn't listen on any:8000: (98, 'Address already in use').
> >
> > ... which is from when I first started it with "(xend-port 8000)" in /etc/xend-config.sxp, but
> > which I then changed to 6000.
> 
> netstat -anp | grep 8000
> 
> Plus, you aren't using the debian packages.  There is no such file
> /etc/xend-config.sxp.

Sorry... mistyped, it is in fact /etc/xen/xend-config.sxp

"dpkg -l|grep xen":

ii  libxen-dev     2.0.5-1        development files for the control library fo
ii  libxen-python  2.0.5-1        python wrapper around libxc, the control lib
ii  libxen2.0      2.0.5-1        control library for XEN, a Virtual Machine M
ii  xen            2.0.5-1        a Virtual Machine Monitor like User-Mode-Lin
ii  xen-docs       2.0.5-1        documentation for XEN, a Virtual Machine Mon

... and during all this, I solved my problem. Found an old python2.1,
and an old xen 1.2 package (libxc-python) which after removal, caused 
/etc/init.d/xend to start up properly.

Which is somewhat strange, as /usr/bin/python -> python2.3.

-michal


-------------------------------------------------------
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

[Adam Heath]

On Thu, 17 Mar 2005, michal urbanski wrote:

> Sorry... mistyped, it is in fact /etc/xen/xend-config.sxp
>
> "dpkg -l|grep xen":
>
> ii  libxen-dev     2.0.5-1        development files for the control library fo
> ii  libxen-python  2.0.5-1        python wrapper around libxc, the control lib
> ii  libxen2.0      2.0.5-1        control library for XEN, a Virtual Machine M
> ii  xen            2.0.5-1        a Virtual Machine Monitor like User-Mode-Lin
> ii  xen-docs       2.0.5-1        documentation for XEN, a Virtual Machine Mon
>
> ... and during all this, I solved my problem. Found an old python2.1,
> and an old xen 1.2 package (libxc-python) which after removal, caused
> /etc/init.d/xend to start up properly.
>
> Which is somewhat strange, as /usr/bin/python -> python2.3.

Hrm, that's interesting.  Could you try to track this down more?  The reason I
placed these in experimental, is because I haven't tried doing upgrade
testing; this may be a problem that I need to work around/fix.


-------------------------------------------------------
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

[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: 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

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

Using Debian packages

[Lars E. D. Jensen]

Hi list

I'm about to install XenLinux on Debian. And I noticed this repository was 
submitted to this list a while ago:

http://people.debian.org/~doogie/xen/

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?

Or should I manually compile a domU from the original Xen 2.0.5 source?

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