I''m having problems getting a fresh Xen 3.0.1 install booting. The server is running Debian 3.1, with /boot on an ext3 partition on the first SATA disk. I have / mounted on an ext3 partition that is inside LVM on a software RAID1 partition on both disks. The server boots fine without Xen, but with Xen it says it can''t find an NFS root. The (I think) relevant parts of /boot/grub/menu.lst are: title Debian GNU/Linux, kernel 2.6.8-2-386 root (hd0,1) kernel /vmlinuz-2.6.8-2-386 root=/dev/mapper/group1- dom0slash ro initrd /initrd.img-2.6.8-2-386 savedefault boot title Xen 3.0 / XenLinux 2.6 kernel /xen-3.0.gz dom0_mem=262144 root=/dev/mapper/group1-dom0slash ro console=tty0 module /vmlinuz-2.6.12-xen0 root=/dev/mapper/group1-dom0slash Any tips please? Thanks, Mark. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tuesday 21 February 2006 18:17, Mark Turner wrote:> I''m having problems getting a fresh Xen 3.0.1 install booting. > > The server is running Debian 3.1, with /boot on an ext3 partition on > the first SATA disk. I have / mounted on an ext3 partition that is > inside LVM on a software RAID1 partition on both disks. > > The server boots fine without Xen, but with Xen it says it can''t find > an NFS root. > > The (I think) relevant parts of /boot/grub/menu.lst are: > > title Debian GNU/Linux, kernel 2.6.8-2-386 > root (hd0,1) > kernel /vmlinuz-2.6.8-2-386 root=/dev/mapper/group1- > dom0slash ro > initrd /initrd.img-2.6.8-2-386^^^^^^> savedefault > boot > > title Xen 3.0 / XenLinux 2.6 > kernel /xen-3.0.gz dom0_mem=262144 root=/dev/mapper/group1-dom0slash > ro console=tty0 > module /vmlinuz-2.6.12-xen0 root=/dev/mapper/group1-dom0slash > > Any tips please? >Looks like your "normal" Linux boots using an initrd which sets up your raid/lvm. You''ll need an initrd doing the same for your Xen0 domain. with a bit of luck, "mkinitrd <xen-kernel-version>" does the right thing, check the mkinitrd docs or search the list for instructions. If you compile all needed modules statically into the kernel, maybe even the original initrd might work. /Ernst _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Feb 21, 2006 at 06:41:26PM +0100, Ernst Bachmann wrote:> with a bit of luck, "mkinitrd <xen-kernel-version>" does the right thing, > check the mkinitrd docs or search the list for instructions.Unfortunately sarge''s mkinitrd requires devfs for MD+LVM support, and the kernels supported by xen do not have devfs any more. I work that around by sticking the attached script to /etc/mkinitrd/scripts/ before running mkinitrd. It''s an ugly hack, but works. You will need to change /dev/mapper/xena-dom0 in it to the name of your root FS device file. Hope that helps. Marcin -- Marcin Owsiany <marcin@owsiany.pl> http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 "Every program in development at MIT expands until it can read mail." -- Unknown _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello Ernst and Marcin, thank-you both for your tips. On 21 Feb 2006, at 17:57, Marcin Owsiany wrote:> Unfortunately sarge''s mkinitrd requires devfs for MD+LVM support, and > the kernels supported by xen do not have devfs any more. I work that > around by sticking the attached script to /etc/mkinitrd/scripts/ > before > running mkinitrd.I tried running mkinitrd both before and after placing this script in /etc/mkinitrd/scripts: #!/bin/bash # make a lvm LV node here perl -pi -e ''s,^vgchange,mount_tmpfs /devfs\nmkdir /devfs/mapper \nmknod /dev/mapper/group1-dom0slash b 253 0\nvgchange,'' $INITRDDIR/ script # prevent umounting the tmp dir with the node (would happen before mounting, ruining the above mknod) perl -pi -e ''s,^,#, if /devfs/'' $INITRDDIR/sbin/init Each time I got the same results: dom0a:~# mkinitrd -o /boot/initrd.img-xen-2.6.12.6-xen0 2.6.12.6-xen0 File descriptor 3 left open File descriptor 4 left open File descriptor 5 left open File descriptor 6 left open File descriptor 7 left open Finding all volume groups Incorrect metadata area header checksum Finding volume group "group1" /usr/sbin/mkinitrd: /dev/mapper/group1-dom0slash: Kernel does not support LVM I think the error message is pretty clear, i.e. the kernel supplied with Xen 3.0.1 does not support LVM. I guess I have two options, either stop using LVM or build my own kernel? Cheers, Mark. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Feb 22, 2006 at 11:31:14AM +0000, Mark Turner wrote:> dom0a:~# mkinitrd -o /boot/initrd.img-xen-2.6.12.6-xen0 2.6.12.6-xen0 > File descriptor 3 left open > File descriptor 4 left open > File descriptor 5 left open > File descriptor 6 left open > File descriptor 7 left open > Finding all volume groups > Incorrect metadata area header checksum > Finding volume group "group1" > /usr/sbin/mkinitrd: /dev/mapper/group1-dom0slash: Kernel does not > support LVM > > I think the error message is pretty clear, i.e. the kernel supplied > with Xen 3.0.1 does not support LVM.If not, then how did you manage to boot the currently running system? Try sticking "set -x" into mkinitrd to see when it''s failing. Marcin -- Marcin Owsiany <marcin@owsiany.pl> http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 "Every program in development at MIT expands until it can read mail." -- Unknown _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 22 Feb 2006, at 12:20, Marcin Owsiany wrote:> If not, then how did you manage to boot the currently running system?The currently running system was booted using the 2.6.8-2-386 kernel supplied with Debian 3.1r1a. That kernel appears to have LVM support compiled in rather than as a module: dom0a:~# find /lib/modules/ -print|grep -i lvm dom0a:~#> Try sticking "set -x" into mkinitrd to see when it''s failing.With "set -x": dom0a:~# mkinitrd -o /boot/initrd.img-xen-2.6.12.6-xen0 2.6.12.6-xen0 [Lots of lines cut] + module_exists drivers/md/lvm-mod ++ find /lib/modules/2.6.12.6-xen0/kernel/drivers -name lvm-mod.ko + ''['' -n '''' '']'' + echo ''/usr/sbin/mkinitrd: /dev/mapper/group1-dom0slash: Kernel does not support LVM'' /usr/sbin/mkinitrd: /dev/mapper/group1-dom0slash: Kernel does not support LVM + exit 1 + rm -r /tmp/mkinitrd.JiViqZ + ''['' '']'' Cheers, Mark. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Feb 22, 2006 at 01:08:49PM +0000, Mark Turner wrote:> On 22 Feb 2006, at 12:20, Marcin Owsiany wrote: > >If not, then how did you manage to boot the currently running system? > > The currently running system was booted using the 2.6.8-2-386 kernel > supplied with Debian 3.1r1a. > > That kernel appears to have LVM support compiled in rather than as a > module: > > dom0a:~# find /lib/modules/ -print|grep -i lvm > dom0a:~# > > >Try sticking "set -x" into mkinitrd to see when it''s failing. > > With "set -x": > > dom0a:~# mkinitrd -o /boot/initrd.img-xen-2.6.12.6-xen0 2.6.12.6-xen0 > [Lots of lines cut] > + module_exists drivers/md/lvm-mod > ++ find /lib/modules/2.6.12.6-xen0/kernel/drivers -name lvm-mod.ko > + ''['' -n '''' '']''Ah, so it looks for lvm-mod for the target (2.6.12.6-xen0) kernel, and it''s not there. Are you using Ralph Passgang''s xen packages? Those somehow work for me with MD+LVM root, even though the module is not there (apparently compiled in as well). Marcin PS: Please don''t CC me, I do read this list. -- Marcin Owsiany <marcin@owsiany.pl> http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 "Every program in development at MIT expands until it can read mail." -- Unknown _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Feb 22, 2006 at 01:58:32PM +0000, Patrick Caulfield wrote:> Marcin Owsiany wrote: > > On Wed, Feb 22, 2006 at 01:08:49PM +0000, Mark Turner wrote: > >> On 22 Feb 2006, at 12:20, Marcin Owsiany wrote: > >>> If not, then how did you manage to boot the currently running system? > >> The currently running system was booted using the 2.6.8-2-386 kernel > >> supplied with Debian 3.1r1a. > >> > >> That kernel appears to have LVM support compiled in rather than as a > >> module: > >> > >> dom0a:~# find /lib/modules/ -print|grep -i lvm > >> dom0a:~# > >> > >>> Try sticking "set -x" into mkinitrd to see when it''s failing. > >> With "set -x": > >> > >> dom0a:~# mkinitrd -o /boot/initrd.img-xen-2.6.12.6-xen0 2.6.12.6-xen0 > >> [Lots of lines cut] > >> + module_exists drivers/md/lvm-mod > >> ++ find /lib/modules/2.6.12.6-xen0/kernel/drivers -name lvm-mod.ko > >> + ''['' -n '''' '']'' > > > > Ah, so it looks for lvm-mod for the target (2.6.12.6-xen0) kernel, and > > it''s not there. Are you using Ralph Passgang''s xen packages? Those > > somehow work for me with MD+LVM root, even though the module is not > > there (apparently compiled in as well). > > > > There''s no such thing as lvm-mod for a 2.6 kernel. LVM2 on 2.6 uses device > mapper, the module name is dm-mod.koMark, maybe you could have a look at mkinitrd''s code (BTW which version are you using?) and find out why is it looking for the "old" lvm module? Marcin -- Marcin Owsiany <marcin@owsiany.pl> http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 "Every program in development at MIT expands until it can read mail." -- Unknown _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 22 Feb 2006, at 14:09, Marcin Owsiany wrote:> Ah, so it looks for lvm-mod for the target (2.6.12.6-xen0) kernel, and > it''s not there. Are you using Ralph Passgang''s xen packages? Those > somehow work for me with MD+LVM root, even though the module is not > there (apparently compiled in as well).I wasn''t aware of Ralph''s packages. Thanks for the pointer. I''m installing Xen by doing: mkdir /usr/local/src/xen cd /usr/local/src/xen/ wget http://bits.xensource.com/Xen/latest/xen-3.0.1-install-x86_32.tgz tar -pzxf xen-3.0.1-install-x86_32.tgz cd xen-3.0.1-install apt-get update apt-get install bridge-utils apt-get install iproute apt-get install python2.3 apt-get install python sh ./install.sh update-rc.d xend defaults update-rc.d xendomains defaults mv /lib/tls /lib/tls.disabled Then I (attempt) to set up a new entry in /boot/grub/menu.lst, which is where this conversation started.>> There''s no such thing as lvm-mod for a 2.6 kernel. LVM2 on 2.6 >> uses device >> mapper, the module name is dm-mod.ko > > Mark, maybe you could have a look at mkinitrd''s code (BTW which > version > are you using?) and find out why is it looking for the "old" lvm > module?From the comments at the top of /usr/sbin/mkinitrd: $Id: mkinitrd,v 1.201 2004/05/16 22:00:48 herbert Exp $ It does look for both dm-mod and lvm-mod. I''m happy to email the mkinitrd script if anyone would like to take a look. Cheers, Mark. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Feb 22, 2006 at 03:24:16PM +0000, Mark Turner wrote:> On 22 Feb 2006, at 14:09, Marcin Owsiany wrote: > >Ah, so it looks for lvm-mod for the target (2.6.12.6-xen0) kernel, and > >it''s not there. Are you using Ralph Passgang''s xen packages? Those > >somehow work for me with MD+LVM root, even though the module is not > >there (apparently compiled in as well). > > I wasn''t aware of Ralph''s packages. Thanks for the pointer.Try them, they are really nice.> It does look for both dm-mod and lvm-mod.And you have neither module?> I''m happy to email the > mkinitrd script if anyone would like to take a look.Maybe post both the script and the log from running it with -x (gzipped if they are large). Marcin -- Marcin Owsiany <marcin@owsiany.pl> http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 "Every program in development at MIT expands until it can read mail." -- Unknown _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 22 Feb 2006, at 15:48, Marcin Owsiany wrote:> Try them, they are really nice.I''ll take a look.> And you have neither module?dom0a:~# updatedb dom0a:~# locate dm-mod /lib/modules/2.6.12.6-xen/kernel/drivers/md/dm-mod.ko /lib/modules/2.6.8-2-386/kernel/drivers/md/dm-mod.ko /usr/local/src/xen/xen-3.0.1-install/install/lib/modules/2.6.12.6-xen/ kernel/drivers/md/dm-mod.ko dom0a:~# locate lvm-mod dom0a:~#> Maybe post both the script and the log from running it with -x > (gzipped > if they are large).Attached. Thanks, Mark. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Feb 22, 2006 at 04:25:03PM +0000, Mark Turner wrote:> dom0a:~# locate dm-mod > /lib/modules/2.6.12.6-xen/kernel/drivers/md/dm-mod.ko > /lib/modules/2.6.8-2-386/kernel/drivers/md/dm-mod.koThere''s a typo somewhere: note the "0" after "xen" below, and the lack of it in locate output above. dom0a:~# mkinitrd -o /boot/initrd.img-xen-2.6.12.6-xen0 2.6.12.6-xen0 Marcin -- Marcin Owsiany <marcin@owsiany.pl> http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 "Every program in development at MIT expands until it can read mail." -- Unknown _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 22 Feb 2006, at 17:41, Marcin Owsiany wrote:> There''s a typo somewhere: note the "0" after "xen" below, and the lack > of it in locate output above. > > dom0a:~# mkinitrd -o /boot/initrd.img-xen-2.6.12.6-xen0 2.6.12.6-xen0Well spotted, thank-you. Ok, a little further forward now. Running mkinitrd with "set -x": dom0a:/boot# mkinitrd -o /boot/initrd.img-xen-2.6.12.6-xen 2.6.12.6-xen File descriptor 3 left open File descriptor 4 left open File descriptor 5 left open File descriptor 6 left open File descriptor 7 left open Finding all volume groups Incorrect metadata area header checksum Finding volume group "group1" /usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed FATAL: Could not load /lib/modules/2.6.12.6-xen/modules.dep: No such file or directory [ previous line repeated lots of times ] WARNING: This failure MAY indicate that your kernel will not boot! but it can also be triggered by needed modules being compiled into the kernel. dom0a:/boot# The using this in /boot/grub/menu.lst: title Xen 3.0 / XenLinux 2.6 kernel /xen-3.0.gz dom0_mem=262144 root=/dev/mapper/group1-dom0slash ro console=tty0 module /vmlinuz-2.6.12-xen root=/dev/mapper/group1-dom0slash initrd /initrd.img-xen-2.6.12.6-xen Trying to boot gives this error: Error 19: Linux kernel must be loaded before initrd Cheers, Mark. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thursday 23 February 2006 12:24, Mark Turner wrote:> /usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed > FATAL: Could not load /lib/modules/2.6.12.6-xen/modules.dep: No such > file or directory > [ previous line repeated lots of times ]you''ll have to generate the module.dep file first, try "depmod 2.6.12.6-xen" If that doesn''t work, you''ll also have to specify the kernel symbol file for your xen kernel, depmod --help shows how. /Ernst _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
[snip big chunk of mkinitrd problems which I''m not trying to help resolve - I can just barely make it work when I do it myself... ;-)]> The using this in /boot/grub/menu.lst: > > title Xen 3.0 / XenLinux 2.6 > kernel /xen-3.0.gz dom0_mem=262144 > root=/dev/mapper/group1-dom0slash ro console=tty0 > module /vmlinuz-2.6.12-xen root=/dev/mapper/group1-dom0slash > initrd /initrd.img-xen-2.6.12.6-xenFor Xen, you should not use initrd command in grub to load initrd - you want to use module to load the initrd too. So the line would be "module /initrd.img-xen-2.6.12.6-xen" This will avoid the Error 19 problem - it obviously won''t fix any problems with creating your initrd... ;-)> > Trying to boot gives this error: > > Error 19: Linux kernel must be loaded before initrd > > Cheers, > > Mark._______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 23 Feb 2006, at 11:50, Petersson, Mats wrote:> [snip big chunk of mkinitrd problems which I''m not trying to help > resolve - I can just barely make it work when I do it myself... ;-)]:)> For Xen, you should not use initrd command in grub to load initrd - > you > want to use module to load the initrd too. So the line would be > "module /initrd.img-xen-2.6.12.6-xen" > > This will avoid the Error 19 problem - it obviously won''t fix any > problems with creating your initrd... ;-)Thanks for the tip. It did fix the error 19 problem. I''m learning a lot here. I''m now using the following: title Xen 3.0 / XenLinux 2.6 kernel /xen-3.0.gz dom0_mem=262144 root=/dev/mapper/group1-dom0slash ro console=tty0 module /vmlinuz-2.6.12-xen root=/dev/mapper/group1-dom0slash module /initrd.img-xen-2.6.12.6-xen root=/dev/mapper/group1-dom0slash I also tried with: module /initrd.img-xen-2.6.12.6-xen The kernel does load now, but it falls over during boot with an error that flashes past so quickly that I can''t read it. I''ve tried videoing it using my phone but the quality is too low. I *think* it says something about failing to mount, and maybe initrd. Currently working on ways to capture the error message so that I can read it. If all else fails then I''ll use a decent video camera tomorrow. Cheers, Mark. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Mark Turner > Sent: 23 February 2006 13:25 > To: xen-users@lists.xensource.com > Cc: Mark Turner > Subject: Re: [Xen-users] Root fs on LVM on software RAID1? > > On 23 Feb 2006, at 11:50, Petersson, Mats wrote: > > [snip big chunk of mkinitrd problems which I''m not trying to help > > resolve - I can just barely make it work when I do it myself... ;-)] > > :) > > > For Xen, you should not use initrd command in grub to load initrd - > > you want to use module to load the initrd too. So the line would be > > "module /initrd.img-xen-2.6.12.6-xen" > > > > This will avoid the Error 19 problem - it obviously won''t fix any > > problems with creating your initrd... ;-) > > Thanks for the tip. It did fix the error 19 problem. I''m > learning a lot here. > > I''m now using the following: > > title Xen 3.0 / XenLinux 2.6 > kernel /xen-3.0.gz dom0_mem=262144 > root=/dev/mapper/group1-dom0slash ro console=tty0 > module /vmlinuz-2.6.12-xen root=/dev/mapper/group1-dom0slash > module /initrd.img-xen-2.6.12.6-xen > root=/dev/mapper/group1-dom0slash > > I also tried with: > > module /initrd.img-xen-2.6.12.6-xen > > The kernel does load now, but it falls over during boot with > an error that flashes past so quickly that I can''t read it. > I''ve tried videoing it using my phone but the quality is too > low. I *think* it says something about failing to mount, and > maybe initrd. Currently working on ways to capture the error > message so that I can read it. > If all else fails then I''ll use a decent video camera tomorrow.If you give xen a "noreboot" option, it won''t try to reboot when it crashes, which will help figuring out what the error is. Of course, even better is to have a serial port connected to another machine and log the data to a file - saves a lot of typing if you want to send it to the list ;-) I think the message you''ll see is that the system failed to mount the rootfs, which usually means either: * udev (or devfs) isn''t working right - thus /dev/mapper/<whatever> is not available when trying to mount / * the drivers for the hard-disk-controller and/or file-system(s) is not in your initrd [or in the kernel itself]. I''ve had both problems on my machine(s), and the fix is really to figure out what is causing the problem and figuring out which option in your config file needs to be twiddled to fix it. Unless you''ve done it several times before, it usually means a large number of kernel builds, mkinitrd and reboots. -- Mats> > Cheers, > > Mark. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 23 Feb 2006, at 13:32, Petersson, Mats wrote:> If you give xen a "noreboot" option, it won''t try to reboot when it > crashes, which will help figuring out what the error is.That did the trick, thanks.> I think the message you''ll see is that the system failed to mount the > rootfs, which usually means either: > * udev (or devfs) isn''t working right - thus /dev/mapper/<whatever> is > not available when trying to mount / > * the drivers for the hard-disk-controller and/or file-system(s) is > not > in your initrd [or in the kernel itself].It was the lack of devfs, which Marcin''s script fixed.> I''ve had both problems on my machine(s), and the fix is really to > figure > out what is causing the problem and figuring out which option in your > config file needs to be twiddled to fix it. Unless you''ve done it > several times before, it usually means a large number of kernel > builds, > mkinitrd and reboots.Understood, though I''m attempting to do this using "out of the box" Debian and Xen downloads, i.e. no kernel rebuilds. I''m so close now. Just one final problem, the ethernet card doesn''t work in dom0 but it did work without Xen. That''s not a problem for this list though. I''m very grateful to all on the list that have helped me sort this out. In case anyone is interested, here''s what I did (just the Xen- specific bits) to install Xen 3.0.1 on Debian 3.1r1 using LVM and software RAID1: mkdir /usr/local/src/xen cd /usr/local/src/xen/ wget http://bits.xensource.com/Xen/latest/xen-3.0.1-install-x86_32.tgz tar -pzxf xen-3.0.1-install-x86_32.tgz cd xen-3.0.1-install apt-get update apt-get install bridge-utils apt-get install iproute apt-get install python2.3 apt-get install python sh ./install.sh update-rc.d xend defaults update-rc.d xendomains defaults mv /lib/tls /lib/tls.disabled depmod 2.6.12.6-xen Create /etc/mkinitrd/scripts/dom0a, mode 755: #!/bin/bash # make a lvm LV node here perl -pi -e ''s,^vgchange,mount_tmpfs /devfs\nmkdir /devfs/mapper \nmknod /dev/mapper/group1-dom0slash b 253 0\nvgchange,'' $INITRDDIR/ script # prevent umounting the tmp dir with the node (would happen before mounting, ruining the above mknod) perl -pi -e ''s,^,#, if /devfs/'' $INITRDDIR/sbin/init mkinitrd -o /boot/initrd.img-xen-2.6.12.6-xen 2.6.12.6-xen Add to end of /boot/grub/menu.lst and change the "default 0" to point to the new entry: title Xen 3.0 / XenLinux 2.6 kernel /xen-3.0.gz dom0_mem=262144 root=/dev/mapper/group1- dom0slash ro console=tty0 module /vmlinuz-2.6.12-xen root=/dev/mapper/group1-dom0slash module /initrd.img-xen-2.6.12.6-xen Reboot Cheers, Mark. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Feb 23, 2006 at 11:24:04AM +0000, Mark Turner wrote:> module /vmlinuz-2.6.12-xen root=/dev/mapper/group1-dom0slash > initrd /initrd.img-xen-2.6.12.6-xenBoth of those should be "module" Marcin -- Marcin Owsiany <marcin@owsiany.pl> http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 "Every program in development at MIT expands until it can read mail." -- Unknown _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users