On 01-13 10:31, Axel Beckert wrote: > found 609852 3.9-4, 4.1-1~bpo50+1 > notfound 609852 4.2-1 > tags 609852 + pending > kthxbye > > Hi Witold, > > Witold Baryluk wrote: > > Package: xen-tools > > Version: 4.2-1 > > Well, the bug is not in 4.2 -- that one has support for installing > Squeeze (obviously :).
Ah. Yes indeed. I used reportbug utility on wrong machine.
Lenny version i was referring is xen-tools 3.9-4+lenny1.
>
> But I'm working on a BPO version of 4.2 which should solve that issue.
Indeed it can be better option.
>
> > I tested this changes and they works perfectly :)
>
> I must admit, I'm surprised about that. And a little bit suspicious.
> ;-)
Yes, I also was very suprised. But it works, boots, console available, disks
working.
So I still would appreciete this three small changes in lennys nonBPO version
(queued on next upload).
There was small problem due to the domU missing modules for xen networking
(but block devices and console apperantly works). Actually xen-tools
brute-force-copied /lib/modules/`uname -r`/kernel directory from dom0
(which obviously copied incorrectly 2.6.26-2-xen-686 ,
as 2.6.32-5-xen-686 was not installed&used in lenny) to domU, and this directory
of course was useless in domU due to the different version of kernel.
(I deleated it later manually from domU, as it is not handled by package
managment).
So I installed linux-modules-2.6-xen-686 in domU (which pulled few
dependencies namely linux-image-2.6.32-5-xen-686, libuuid-perl,
initramfs-tools, klibc-utils, libklibc, linux-base), and problem was solved
(proper modules loaded later in boot process automatically). I was thinking that
xen-tools will instll it automaticaly (using package linux-image-2.6-xen-686 on
i386),
but apperantly it did not do so.
I also tried to force dom0 initramfs-tools to put this networking modules
into initramfs (i inspected initrd and it contained only netxen_nic, xenblkfront
from relevant modules; crucial xen-netfront was missing, as well other xen
modules,
like xenfs, or blktap, but they are not critically needed).
It also worked ( by adding nacassary modules names into domO
/etc/initramfs/modules),
but I think puting real kernel in domU and then using pygrub is better option,
than always having all kernels/initrds versions synchronized on both domU and
domO.
So even better is to install whole kernel image (kernel and modules).
This way modules will be present and kernel and properly generated initramfs
from inside domU. This will make both pygrub and non-pygrub loading easier.
So last things will be to add "linux-image-2.6-xen-{686,amd64}"
as default installed package in all debian profiles in xen-tools.
If it is not available xen-tools as I understand will not install it.
(linux-modules- package only is an other option, but squeeze do not provide it
anymore, and it will not help in scenario with pygrub).
BTW. I do not know how, but squeeze domU load so much faster than lenny domU
(on lenny dom0), about 12 seconds comparing to 30 seconds. :)
--
Witold Baryluk
JID: witold.baryluk // jabster.pl
signature.asc
Description: Digital signature
