On Sun, Oct 29, 2006 at 07:34:21PM -0800, master@xxxxxxxxxxxxxxx wrote: > > Correct -- it seems the messages only appear on the guest's console during > boot. No messages like that on dom0. The results of the commands you > suggested look as expected(?): > > [root@zeus ~]# ldconfig -p|grep segneg > libthread_db.so.1 (libc6, hwcap: 0x0018000000000000, OS ABI: Linux > 2.6.9) => /lib/i686/nosegneg/libthread_db.so.1 > librt.so.1 (libc6, hwcap: 0x0018000000000000, OS ABI: Linux 2.6.9) > => /lib/i686/nosegneg/librt.so.1 > libpthread.so.0 (libc6, hwcap: 0x0018000000000000, OS ABI: Linux > 2.6.9) => /lib/i686/nosegneg/libpthread.so.0 > libm.so.6 (libc6, hwcap: 0x0018000000000000, OS ABI: Linux 2.6.9) > => /lib/i686/nosegneg/libm.so.6 > libc.so.6 (libc6, hwcap: 0x0018000000000000, OS ABI: Linux 2.6.9) > => /lib/i686/nosegneg/libc.so.6 > > [root@zeus ld.so.conf.d]# cat kernelcap-2.6.18-1.2200.fc5.conf > # This directive teaches ldconfig to search in nosegneg subdirectories > # and cache the DSOs there with extra bit 0 set in their hwcap match > # fields. In Xen guest kernels, the vDSO tells the dynamic linker to > # search in nosegneg subdirectories and to match this extra hwcap bit > # in the ld.so.cache file. > hwcap 0 nosegneg > > [root@zeus ld.so.conf.d]# uname -a > Linux zeus.bradleyland.com 2.6.18-1.2200.fc5xen0 #1 SMP Sat Oct 14 > 17:49:47 EDT 2006 i686 athlon i386 GNU/Linux > > I tried running ldconfig without arguments in any case and then tried to > start a guest. I don't have the modules for the kernel in the guest yet, > but it should still boot. Here's the results: > > Starting hidd: Can't open HIDP control socket: Address family not > supported by protocol > [FAILED] > Starting automount: printk: 1224600 messages suppressed. > 4gb seg fixup, process syslogd (pid 759), cs:ip 73:00a62036 > [ OK ] > Starting smartd: [ OK ] > Starting sshd: [ OK ] > Heartbeat not configured: /etc/ha.d/ha.cf not found. > Starting crond: [ OK ] > Starting ldirectord Config file ldirectord.cf not found > [FAILED] > Starting anacron: [ OK ] > Starting atd: [printk: 1082344 messages suppressed. > 4gb seg fixup, process S95atd (pid 998), cs:ip 73:0056cc42 > OK ] > Starting HAL daemon: [ OK ] Ok, I've figured out what's up here - HAL is actually one of the last, if not the last, init script to be run. So it has actually completed booting at this point & is running. The 2.6.18 kernel though now has the paravirt framebuffer support integrated. This means the primary console is now the graphical console, not the text console. If you happen to have a fixed (or otherwise known) IP for the guest you should be able to login with SSH & see that its all running. The thing is the mingetty proesses are now spawning on the framebuffer instead, so as for fullyvirt, you need to turn on the VNC support int he guest config 'vnc=1' and one or more of vncunused=1, vnclisten="0.0.0.0", vncpassword='123456'. To make it launch a login prompt on the serial console too, it is neccessary to have an extra line in /etc/inittab, ie co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav Ordinaryily kudzu should make such an addition automatically upon bootup if it detects a Xen guest, so I am co-ordinating to get an update for kudzu too. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| -- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
