On Fri, 2006年10月27日 at 15:15 +0200, Petersson, Mats wrote:
>
> > -----Original Message-----
> > From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> > [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Art Fore
> > Sent: 27 October 2006 13:43
> > To: xen-users@xxxxxxxxxxxxxxxxxxx
> > Subject: [Xen-users] Getting frustrated with Xen
> > 
> > Been trying to get Xen working on this machine for over two 
> > weeks. Every
> > time I end up against a brick wall again.
> > 
> > Tried the xen LiveCD on this machine (Athlon 64 X2 running Suse Linux
> > 10.1) and it worked. Had 3 vms working with no problem. The base Suse
> > 10.1 xen kernel works up to a point, that is I can xm list and get the
> > correct output, start a prebuilt guest, but it never comes up on
> > screent. Try stopping it, it says it says vm does not exist.
> > 
> > So, downloaded the xen-3.0.3_0-src tarball and follow instructions
> > compiling. Do a make dist and get 
> > 
> > ... x86-put-note-sections-into-a-pt_note-segment-in-vmlinux.patch
> > /bin/sh:
> > patches/linux-2.6.16.29/x86-put-note-sections-into-a-pt_note-s
> egment-in-vmlinux.patch: No such file or directory
> > make[2]: *** [ref-linux-2.6.16.29/.valid-ref] Error 1
> > make[2]: Leaving directory `/home/afore/Downloads/xen-3.0.3_0-src'
> > make[1]: *** [linux-2.6-xen-install] Error 2
> > make[1]: Leaving directory `/home/afore/Downloads/xen-3.0.3_0-src'
> > make: *** [install-kernels] Error 1
> > 
> > It downloaded the 2.6.16.29 kernel files, unpacked them, then 
> > looks like
> > it applied a bunch of patches up to the last one above. Other 
> > than that,
> > the error message is unintelligible to me. Can anyone tell me what the
> > problem is form the very cryptic error messages shown above?
>
> That you don't have the file called 
> "x86-put-note-sections-into-a-pt_note-segment-in-vmlinux.patch" 
> in your system. 
>
> I have attached the version hg changeset 11884 (I doubt it's changed
> since 3.0.3). 
>
> But it really should be part of your source-code in the tarball [I
> haven't tried the 3.0.3, since I'm usually "ahead" on the "unstable"
> version...].
>
> You asked about this same file a little while ago, but it appears that
> it was in some other directory?? [Although it could be that they are
> stored elsewhere first, and created in the correct directory when
> needed, as some of the patches are probably version independent].
>
> --
> Mats
>
> > 
> > Art
> > 
Well, another brick wall. I copied the following as a new entry
on /boot/grob/menu.lst
title Xen 3.0 / XenLinux 2.6
 kernel /boot/xen-3.0.gz console=vga
 module /boot/vmlinuz-2.6-xen root=<root-dev> ro console=tty0
 module /boot/initrd-2.6-xen.img
and modified it to:
title Xen 3.0 / XenLinux 2.6
 kernel /boot/xen-3.0.gz console=vga
 module /boot/vmlinuz-2.6-xen root=/dev/sda2 ro console=tty0
 module /boot/initrd-2.6-xen.img
Reboot, and I get /boot/initrd-2.6-xen.img: no such file and sure
enough, there is no such file. 
Tried the # depmod 2.6.16-xen that seemed to go OK.
Tried the 
mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod
initrd-2.6.16-xen.img 2.6.16-xen
and got -v no valid option, so check man mkinitrd and seen a -V option.
Thinking a typographical error, changed the -v to -V. Then get
unrecognized --. Only thing I could find that might fit was -m, so tried
mkinitrd -V -f -m initrd-2.6.16-xen.img 2.6.16-xen
No luck there either. So, how does this work? The instructions sure do
not. (Actually the 2.6.16-zen does not make sense at all)
Art
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users