Hi,
I just rebuilt xeno-unstable.bk in my machine according to the
''HOWTO'' by Bin Ren.
Everything goes well except that I cannot get a xenolinux.gz file.
I have built this unstable version before, and everything is ok.
The problem is,
# cd /xeno-unstable.bk/xenolinux-2.4.26
# ARCH=xeno make oldconfig
# ARCH=xeno make dep bzImage
don''t result in a xenolinux.gz file.
I tried the same steps on another machine, but still got this problem.
The build process seems ok, and the last several lines are as follows:
make[1]: Entering directory
''/xeno-unstable.bk/xenolinux-2.4.26/arch/xen/boot''
objcopy -R .note -R .comment -S /xeno-unstable.bk/xenolinux-2.4.26/vmlinux
Image
gzip -f -9 < Image > bzImage
rm -f Image
make[1]: Leaving directory
''/xeno-unstable.bk/xenolinux-2.4.26/arch/xen/boot''
Can someone tell me where is wrong?
Thanks.
Xiaofang
> I just rebuilt xeno-unstable.bk in my machine according to the ''HOWTO'' by Bin Ren. > Everything goes well except that I cannot get a xenolinux.gz file. > I have built this unstable version before, and everything is ok.The howto is out of date. Just type ''make world'' at the top level. (If you haven''t already got a pristine linux src tar ball at the top level it attempts to download one.) All of the files that are built are placed under the ./install directory. E.g. looking in install/boot/ : install/boot/xen.gz The Xen ''kernel'' (formerly called image.gz) install/boot/vmlinuz-2.4.26-xen0 Domain 0 xenolinux kernel (xenolinux.gz) install/boot/vmlinuz-2.4.26-xenU Unprivileged xenolinux kernel The difference between the two linux kernels that are built is due to the configuration file used for each. The "U" suffixed unprivileged version doesn''t contain any of the physical hardware device drivers, so is 30% smaller and hence may be preferred for domains>0. The install/boot directory will also contain the config files used for building the xenlinux kernels, and also versions of xen and xenlinux kernels that contain debug symbols (xen-syms and vmlinux-syms-2.4.26-xen0) and are hence essential for interpreting crash dumps. Your grub config will thus look something like the following: title Xen running Linux 2.4.26 root(hd0,0) kernel /boot/xen.gz dom0_mem=131072 watchdog com1=115200,8n1 noht module /boot/vmlinuz-2.4.26-xen0 root=/dev/hda1 ro The old "console=" xenlinux option is typically unnecessary as it now has more sane defaults: by default, domain0 will grab the screen and keyboard directly (tty1) and also access the serial line via Xen (ttyS0). This means that most distribution''s start up scripts (in particular /etc/inittab) should work without modification. Somebody should put this message in a howto ;-) Ian ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Ian, Thanks so much for your patient replies. I just find that the README file has this info. Sorry about my careless. Thanks. Xiaofang On Thu, 24 Jun 2004, Ian Pratt wrote:> > > I just rebuilt xeno-unstable.bk in my machine according to the ''HOWTO'' by Bin Ren. > > Everything goes well except that I cannot get a xenolinux.gz file. > > I have built this unstable version before, and everything is ok. > > The howto is out of date. Just type ''make world'' at the top > level. (If you haven''t already got a pristine linux src tar ball > at the top level it attempts to download one.) > > All of the files that are built are placed under the ./install > directory. E.g. looking in install/boot/ : > > install/boot/xen.gz The Xen ''kernel'' (formerly called image.gz) > install/boot/vmlinuz-2.4.26-xen0 Domain 0 xenolinux kernel (xenolinux.gz) > install/boot/vmlinuz-2.4.26-xenU Unprivileged xenolinux kernel > > The difference between the two linux kernels that are built is > due to the configuration file used for each. The "U" suffixed > unprivileged version doesn''t contain any of the physical hardware > device drivers, so is 30% smaller and hence may be preferred for > domains>0. > > The install/boot directory will also contain the config files > used for building the xenlinux kernels, and also versions of xen > and xenlinux kernels that contain debug symbols (xen-syms and > vmlinux-syms-2.4.26-xen0) and are hence essential for > interpreting crash dumps. > > > Your grub config will thus look something like the following: > > title Xen running Linux 2.4.26 > root(hd0,0) > kernel /boot/xen.gz dom0_mem=131072 watchdog com1=115200,8n1 noht > module /boot/vmlinuz-2.4.26-xen0 root=/dev/hda1 ro > > The old "console=" xenlinux option is typically unnecessary as it > now has more sane defaults: by default, domain0 will grab the > screen and keyboard directly (tty1) and also access the serial > line via Xen (ttyS0). This means that most distribution''s start > up scripts (in particular /etc/inittab) should work without > modification. > > > Somebody should put this message in a howto ;-) > > Ian > > > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel >------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Sorry to bother you even more with this, but I still have bootup problems I can''t figure out. I have now updated to the unstable version and builded xen.gz and vmlinuz-2.4.26-xen0 When i bootup the system hangs on: . . .. EXT3-fs: mounted root (ext3 filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly Freeing unused kernel memory: 112k freed" The grub file is now: title Xen ... root(0,0) kernel /xen.gz dom0_mem=131072 watchdog noreboot com1=115200 noht module /vmlinuz-2.4.26-xen0 root=/dev/hda2 ro console=tty0 The grub, for some reasons, search automaticly on the /boot map so i have to skip /boot the hda1 is the boot partition and hda2 is /. I get no failure messages, it just hangs. I have compiled the files the correct way with ians updated information in the previous mail. Could it be some HW problems? I have the boot manager on the MBR, is this a problem? Does it mather which grub version I use? etc. I had som similar problems on the XEN CD installation, so i guess there could be som HW problems (??) Thank you for your patience :-) regards rune ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> Sorry to bother you even more with this, but I still have bootup > problems I can''t figure out. > I have now updated to the unstable version and builded xen.gz and > vmlinuz-2.4.26-xen0 > > When i bootup the system hangs on: > > . > . > .. > EXT3-fs: mounted root (ext3 filesystem with ordered data mode. > VFS: Mounted root (ext3 filesystem) readonly > Freeing unused kernel memory: 112k freed" > > The grub file is now: > > title Xen ... > > root(0,0) > kernel /xen.gz dom0_mem=131072 watchdog noreboot com1=115200 noht > module /vmlinuz-2.4.26-xen0 root=/dev/hda2 ro console=tty0Are you looking at serial output? If so, there are two problem I see in your grub config: 1. ''com1=115200'' should be ''com1=115200,8n1'' 2. Try removing ''console=tty0'' from your Linux boot options -- Keir ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Well, adding 8n1 makes it hang even before on (XEN) PCI: sharing IRQ 9 with 00:id.2 How can i see a serial output? I am now looking at the bootup and use norboot in grubconfig. Anyway, do any of you have experience with hang up in any of these stages? (in this mail or in the before?) thank you :) regards rune On Jun 24, 2004, at 3:18 PM, Keir Fraser wrote:>> Sorry to bother you even more with this, but I still have bootup >> problems I can''t figure out. >> I have now updated to the unstable version and builded xen.gz and >> vmlinuz-2.4.26-xen0 >> >> When i bootup the system hangs on: >> >> . >> . >> .. >> EXT3-fs: mounted root (ext3 filesystem with ordered data mode. >> VFS: Mounted root (ext3 filesystem) readonly >> Freeing unused kernel memory: 112k freed" >> >> The grub file is now: >> >> title Xen ... >> >> root(0,0) >> kernel /xen.gz dom0_mem=131072 watchdog noreboot com1=115200 noht >> module /vmlinuz-2.4.26-xen0 root=/dev/hda2 ro console=tty0 > > Are you looking at serial output? > > If so, there are two problem I see in your grub config: > 1. ''com1=115200'' should be ''com1=115200,8n1'' > 2. Try removing ''console=tty0'' from your Linux boot options > > -- Keir > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel