On Fri, Oct 31, 2008 at 03:52:43PM +0000, Ian Campbell wrote: [..snip..] > > > 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? Yes, this was the version 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. No, but it just would make things even nicer. The additional package doesn't hurt on non pae. > > 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... Agreed. What would be the right package to file the wishlist bug against? -- Guido -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
