Xen devel - Nov 2004 - Xen 2.0.1 debian packages at xen.terrabox.com

I''ve finally managed to create a Xen based kernel based on
kernel-patch-xen 2.0.1 from xen.terrabox.com. I used make-kpkg (not
xenlinux-builder) and configured grub manually. Works like a dream,
good work.

However, the other packages do not seem to be in too good of a
condition. For example, the libxc2.0 package contains:

,----
| /.
| /usr
| /usr/lib
| /usr/share
| /usr/share/doc
| /usr/share/doc/libxc2.0
| /usr/share/doc/libxc2.0/copyright
| /usr/share/doc/libxc2.0/changelog.Debian.gz
| /usr/lib/libxc.so
`----

Where /usr/lib/libxc.so looks like this:

,----
| lrwxrwxrwx  1 root root 12 Nov 30 13:27 /usr/lib/libxc.so -> libxc.so.1.3
`----

E.g. a dangling symlink to a non-existant file.

Because of this, xend refuses to start:

,----
|     from xen.lowlevel import xu
| ImportError: libxc.so.1.3: cannot open shared object file: No such
| file or directory
`----

About the repository structure in general, the source part seems to be
haywire. There are no packages for 2.0.1, only the old 2.0 - it has a
Packages and Packages.gz file, neither of which should be there - and
it doesn''t have a Sources.gz which should be there, if it is to be a
source directory for apt.

And just in case - Brian - I am not complaining at all about these
packages. I''m just pointing out stuff to fix when you get time for it.

Thumbs up,
-- 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://productguide.itmanagersjournal.com/
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

On Tue, 2004-11-30 at 20:04 +0200, Nuutti Kotivuori
wrote:
> I''ve finally managed to create a Xen based kernel based on
> kernel-patch-xen 2.0.1 from xen.terrabox.com. I used make-kpkg (not
> xenlinux-builder) and configured grub manually. Works like a dream,
> good work.
> 
> However, the other packages do not seem to be in too good of a
> condition. For example, the libxc2.0 package contains:
> 
> ,----
> | /.
> | /usr
> | /usr/lib
> | /usr/share
> | /usr/share/doc
> | /usr/share/doc/libxc2.0
> | /usr/share/doc/libxc2.0/copyright
> | /usr/share/doc/libxc2.0/changelog.Debian.gz
> | /usr/lib/libxc.so
> `----
> 
> Where /usr/lib/libxc.so looks like this:
> 
> ,----
> | lrwxrwxrwx  1 root root 12 Nov 30 13:27 /usr/lib/libxc.so ->
libxc.so.1.3
> `----
> 
Ouch. marked for fixing. Just started getting the dev branch setup on
auto-building. I''ll cut a new one later this evening to fix the lib
issue.

> E.g. a dangling symlink to a non-existant file.
> 
> Because of this, xend refuses to start:
> 
> ,----
> |     from xen.lowlevel import xu
> | ImportError: libxc.so.1.3: cannot open shared object file: No such
> | file or directory
> `----
> 
> About the repository structure in general, the source part seems to be
> haywire. There are no packages for 2.0.1, only the old 2.0 - it has a
> Packages and Packages.gz file, neither of which should be there - and
> it doesn''t have a Sources.gz which should be there, if it is to be
a
> source directory for apt.
Yep. I was out of it when I rebuilt the indexes. 8-P
> 
> And just in case - Brian - I am not complaining at all about these
> packages. I''m just pointing out stuff to fix when you get time for
it.
Feh. Didn''t come across as whining. so don''t worry about it.

Any other bugs or cleanups that you have come across yet?

btw, did you check out the xenlinuxbuilder package I created? make-kpkg
works nicely for Debian systems, but if you want to create kernels for
non-debian systems you wil have to either use the xen source tree or
xenlinuxbuilder. I plan on having xenlinuxbuilder use make-kpkg when the
target packaging is .deb, and the standard compile for .tgz. 

I should probably make xenlinuxbuilder available as a tar.gz 8-P.
> 
> Thumbs up,
> -- 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://productguide.itmanagersjournal.com/
> _______________________________________________
> 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://productguide.itmanagersjournal.com/
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

Brian Wolfe wrote:
> On Tue, 2004-11-30 at 20:04 +0200, Nuutti Kotivuori wrote:
>> However, the other packages do not seem to be in too good of a
>> condition. For example, the libxc2.0 package contains:
[...]
> Ouch. marked for fixing. Just started getting the dev branch setup
> on auto-building. I''ll cut a new one later this evening to fix the
> lib issue.
Installing libxutil.so.1.3.0, libxc.so.1.3.0 and relevant symlinks
manually under /usr/lib resolved the problem. Now xend starts.

So now xend starts, xensv can be stated and xm command work. There
seem to be some complains about missing scripts or default configs -
and I am not certain that all paths are correct - but I was able to
start a domain (if only momentarily, since I didn''t manage a proper
root device configuration).
> Feh. Didn''t come across as whining. so don''t worry about
it.
Then I need not mention it again :-)
> Any other bugs or cleanups that you have come across yet?
Will mail them here as I stumble on them. Well, one more - the
description of xen-dev says it is for xen 1.3 - the version number
should be updated to 2.0.
> btw, did you check out the xenlinuxbuilder package I created? 
> make-kpkg works nicely for Debian systems, but if you want to create
> kernels for non-debian systems you wil have to either use the xen
> source tree or xenlinuxbuilder. I plan on having xenlinuxbuilder use
> make-kpkg when the target packaging is .deb, and the standard
> compile for .tgz.
>
> I should probably make xenlinuxbuilder available as a tar.gz 8-P.
Only momentarily. My main goal has been to be able to use a xen kernel
as domain0 in everyday usage - I think today I finally reached that
goal, more or less. So soon I will concentrate more on actually using
the features Xen offers - and will probably try making some
non-priviledged kernels with xenlinux-builder.

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