WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] Getting frustrated with Xen

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Getting frustrated with Xen
From: Art Fore <art.fore@xxxxxxxxx>
Date: Fri, 27 Oct 2006 23:30:59 +0800
Delivery-date: Fri, 27 Oct 2006 08:37:09 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:reply-to:to:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=LC+s38p70Nq5VRTp4i1nR/ZihiIbg+MT1ftgZqvF7YL4c3ItW4kJF+j95q0j0psAvE69chS/z8oqJtDncG47Ws6bk4LlmjMBvAbDf4/zhfC+q/JFeA4LOYJafRRsVN+162YQd6RVGRRqOCzaiGT5OomkY0ekdnFZajGLLJDH0no=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <907625E08839C4409CE5768403633E0B018E168D@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <907625E08839C4409CE5768403633E0B018E168D@xxxxxxxxxxxxxxxxx>
Reply-to: art.fore@xxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, 2006-10-27 at 17:28 +0200, Petersson, Mats wrote:
> > 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)
> 
> Unfortunately, different distributors have different options for
> mkinitrd, so you'll have to do "man mkinitrd" and see what the options
> are for manually forcing certain drivers into your initrd-file [assuming
> you actually NEED to have aacraid, sd_mod and scsi_mod in your initrd -
> you really shouldn't need to specify them manually in normal cases - but
> if you know you need those, then it's a good idea to force them in there
> just in case...]. 
> 
> On SuSE 9.x, you specify the moudles you want with -m, and -f, -v are
> both "meaningless". 
> On FC4, -f means "force overwrite of initrd file", and -v means "print
> verbose information". It also has the --with options. Note also that
> mkinitrd is a shell-script, so whilst it may not be immediately obvious
> what it does, you can "just read it", rather than binary files that you
> have to find the source of. 
> 
> I also think you should specify 2.6.16.29-xen, but maybe that's only
> when you build from unstable? Check what your version is called in
> /lib/modules/  - my machine has /lib/modules/2.6.16.29-xen and various
> older ones. You need to specify exactly the right version of linux, even
> if your initrd doesn't have that name in it... 
> 
> --
> Mats
Well, the machine is dead in the water now. When I boot into the non xen
kernnel, I get so many failures and cannot even go to run level 5. Why
should those commands have done anything to the normal kernel? Guess I
will have to do a reinstall to get back to where I was before. This is
really the shits. (am doing this from my laptop now)

Art


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users