On Fri, 2008-10-31 at 16:44 +0100, Guido Günther wrote:
> On Fri, Oct 31, 2008 at 12:56:48PM +0000, Ian Campbell wrote:
> > On Fri, 2008-10-31 at 12:58 +0100, Guido Guenther wrote:
> > > Package: installation-reports
> > > Version: 2.38
> > > Severity: normal
> > > 
> > > Boot method: network
> > > Image version: http://people.debian.org/~joeyh/d-i/images/current/
> > > Date: 20081031
> > > 
> > > Machine: Xen Paravirtual machine on a lenny Dom0
> > > Partitions: 
> > >     Device Boot      Start         End      Blocks   Id  System
> > > /dev/xvda1   *           1         242     1943833+  83  Linux
> > > /dev/xvda2             243         261      152617+   5  Extended
> > > /dev/xvda5             243         261      152586   82  Linux swap / 
> > > Solaris
> > > 
> > > 
> > > Base System Installation Checklist:
> > > [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
> > > 
> > > Initial boot:           [O]
> > > Detect network card:    [O]
> > > Configure network:      [O]
> > > Detect CD:              [ ]
> > > Load installer modules: [O]
> > > Detect hard drives:     [O]
> > > Partition hard drives:  [O]
> > > Install base system:    [O]
> > > Clock/timezone setup:   [O]
> > > User/password setup:    [O]
> > > Install tasks:          [O]
> > > Install boot loader:    [0]
> > > Overall install:        [E]
> > > 
> > > Comments/Problems:
> > > 
> > > The installtion itself worked great but d-i failed to install an
> > > appropriate kernel for Xen Paravirt so the system failed to boot.  To
> > > fix this up I mounted the partition in the dom0 and installed the
> > > correct kernel. d-i installed linux-image-2.6.26-1-486 while it should
> > > have picked linux-image-2.6.26-1-xen-686 (this also pulls in libc6-xen
> > > via a Recommends). Seems base-installer/kernel/i386.sh needs an
> > > detect_xen_paravirt?
> > 
> > d-i should have installed the 686-bigmem image when running under Xen
> > due to the use of the 686-bigmem kernel for the Xen variant of the
> > installer. I'll investigate why this didn't happen.
> > 
> > Could you please send /var/log/installer/syslog.
> Attached.
> 
> > > One more thing: in order to get console output via "virsh console" I had
> > > to add "xencons=tty" to the grub command line. 
> > 
> > With the 686-bigmem kernel I don't think this will be necessary, if you
> > could try it and let me know that would be great.
> Yes, the 686-bigmem kernel doesn't need "xencons=tty" since hvc0 works.

Since 2.6.26-9 hvc should work by default for the -xen-686 kernel too. I
guess you installed -8 from testing?

> But we still need libc6-xen due to nosegneg? Should we schedule this for
> installtion on xen installs?

It's an optimisation only and is only required when running a PAE
hypervisor, nothing breaks if you don't install it.

If you are running a PAE guest on a 64 bit hypervisor then you don't
need libc6-xen.

So far d-i hasn't had to care explicitly about Xen installs or not and
certainly hasn't had to care about the bit width of the hypervisor. I'm
inclined to say that people still running on a PAE hypervisor can
install the package by hand, mainly because it's rather late in the
game...

Ian.

-- 
Ian Campbell
Current Noise: Deep Purple - Listen, Learn, Read On

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
                -- Benjamin Franklin, 1759




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to