Mailing List Archive

"John M. Johnson III" <johnsonj@ospex.com> writes:

> Has anyone had issues starting xen0 on a md? I have installed it a few
> times now w/ and w/o raid. Anytime I have a raid1 mirror, Xen panics on
> boot when trying to mount /.
> It gets past waiting for /dev/md0 to appear.

Hmm, I had some trouble as well with a LVM setup. Cause seems to be
that the device mapper block devices get a different major number
depending on whenever it runs on native linux or on xen. On my system
it sucessfully mounted the root fs, but bailed out shortly after when
trying to check the filesystems. So it was a different (but maybe
related) issue.

Setting HOTPLUG_DEV_ON_TMPFS to "yes" (in /etc/sysconfig/hotplug) and
then let udev create all the device nodes dynamically at boot time
fixed it for me.

HTH,

Gerd

--
#define printk(args...) fprintf(stderr, ## args)

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

> Has anyone had issues starting xen0 on a md? I have
> installed it a few times now w/ and w/o raid. Anytime I have
> a raid1 mirror, Xen panics on boot when trying to mount /.
> It gets past waiting for /dev/md0 to appear.

You're talking about booting dom0, right?

I've used raid1 and lvm for dom0 root without problems.

What kind of panic is it, just a failure to mount root?

Thanks,
Ian

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

Hi, I've got the same problem (boot Suse 9.3 from md0).





When Xen boots, there is this message:







>reiserfs: disagrees about version of symbol struct_module

>insmod: error inserting
'/lib/modules/2.6.11.4-20a-smp/kernel/fs/reiserfs(reiserfs.ko': -1
invalid module format

>loading kernel/fs/reiserfs/reiserfs.ko

>raidautorun ...

>... done

>waiting for device /dev/md0 to appear: ok

>rootfs: major=9 minor=0 devn=2304

>[: volume: unexpected operator

>mounting root /dev/md0

>usage: mount [-r] [-w9 8-o options] [-t type] device directory

>umount2: Device or resource busy

>kernel panic - not syncing: Attempt to kill init!



>reboot in ... seconds





What is the problem and what can I do to solve this?



greetings, Stefan

thanks for the hint. But no love :(

On Tue, 26 Apr 2005, Gerd Knorr wrote:

> "John M. Johnson III" <johnsonj@ospex.com> writes:
>
> > Has anyone had issues starting xen0 on a md? I have installed it a few
> > times now w/ and w/o raid. Anytime I have a raid1 mirror, Xen panics on
> > boot when trying to mount /.
> > It gets past waiting for /dev/md0 to appear.
>
> Hmm, I had some trouble as well with a LVM setup. Cause seems to be
> that the device mapper block devices get a different major number
> depending on whenever it runs on native linux or on xen. On my system
> it sucessfully mounted the root fs, but bailed out shortly after when
> trying to check the filesystems. So it was a different (but maybe
> related) issue.
>
> Setting HOTPLUG_DEV_ON_TMPFS to "yes" (in /etc/sysconfig/hotplug) and
> then let udev create all the device nodes dynamically at boot time
> fixed it for me.
>
> HTH,
>
> Gerd
>
> --
> #define printk(args...) fprintf(stderr, ## args)
>

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

Yes, in fact it does look like a mount issue. Right when mounting /.

On Tue, 26 Apr 2005, Ian Pratt wrote:

>
> > Has anyone had issues starting xen0 on a md? I have
> > installed it a few times now w/ and w/o raid. Anytime I have
> > a raid1 mirror, Xen panics on boot when trying to mount /.
> > It gets past waiting for /dev/md0 to appear.
>
> You're talking about booting dom0, right?
>
> I've used raid1 and lvm for dom0 root without problems.
>
> What kind of panic is it, just a failure to mount root?
>
> Thanks,
> Ian
>

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

I replied to the user not the list the other day...

I have a gentoo system running for both xen0 and xenU's on the server.

I use have 3 xenU's - one runs a stripe, another runs a mirror and the
third is just a single basic partition.

There are no problems with any of these.

this is using xen 2.0.4 on this system - I've seen no reason to upgrade
as yet as the performance is better than UML and 2.0.4 is working
flawlessly.

Thanks much.

If anyone needs to know configs or settings, let me know, I'll do what I
can to help.

Thanks,
Jack



On Tue, 2005-04-26 at 23:46 -0500, John M. Johnson III wrote:
> Has anyone had issues starting xen0 on a md? I have installed it a few
> times now w/ and w/o raid. Anytime I have a raid1 mirror, Xen panics on
> boot when trying to mount /.
> It gets past waiting for /dev/md0 to appear.
>
> John
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
--
Jack Downes <jack@chainreactionweb.com>
Chain Reaction Web


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

John M. Johnson III wrote:
> Has anyone had issues starting xen0 on a md? I have installed it a few
> times now w/ and w/o raid. Anytime I have a raid1 mirror, Xen panics on
> boot when trying to mount /.
> It gets past waiting for /dev/md0 to appear.

Yes, I am seeing this too.

I believe the initrd is broken, or rather the /sbin/mkinitrd shell
script that generates /boot/initrd-xxxx is broken.

here is what I mean

Robbie's shell session>
> paradox:~ # cd /tmp
> paradox:/tmp # mkdir initrd-tree
> paradox:/tmp # cd initrd-tree/
> paradox:/tmp/initrd-tree # cat /boot/initrd-2.6.11.4-20a-xen | gunzip | cpio -i
^^^
> 8668 blocks
> paradox:/tmp/initrd-tree # ls
> . bin etc init proc run_init sys var
> .. dev events lib root sbin tmp
> paradox:/tmp/initrd-tree # ls -l lib/modules/
> total 16
> drwxr-xr-x 4 root root 4096 Apr 29 09:36 .
> drwxr-xr-x 4 root root 4096 Apr 29 09:36 ..
> drwxr-xr-x 3 root root 4096 Apr 29 09:36 2.6.11.4-20a-default
^^^^^^^
> drwxr-xr-x 3 root root 4096 Apr 29 09:36 2.6.11.4-20a-xen
> paradox:/tmp/initrd-tree # grep -r raid1 init
> echo "Loading /lib/modules/2.6.11.4-20a-default/kernel/drivers/md/raid1.ko"
> insmod /lib/modules/2.6.11.4-20a-default/kernel/drivers/md/raid1.ko
^^^^^^^
> echo "Loading kernel/drivers/md/raid1.ko"
> insmod /lib/modules/2.6.11.4-20a-xen/kernel/drivers/md/raid1.ko
> paradox:/tmp/initrd-tree #

I see two trees of kernel modules for both the -default and -xen
kernels and it appears that the init shell script is loading up the
modules for the wrong kernel (i.e -xen kernel, -default modules !)

I don't know how to fix mkinitrd, but I am going to try to fix up
the initrd image by hand. delete the extraneous modules and edit
the init script to load just the -xen modules.

I'll reply when I find out if this helps or not.

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

Robbie Dinn wrote:
> I don't know how to fix mkinitrd, but I am going to try to fix up
> the initrd image by hand. delete the extraneous modules and edit
> the init script to load just the -xen modules.
>
> I'll reply when I find out if this helps or not.

Did that but no change in behaviour. ho hum...

I have shell, but not any final root filesystem. Currently
using the initrd filesystem image.

I can see a directory /sys/block/md0 but if I look in
/sys/block/md0/size, it contains 0 (zero).

I editted the file ./init in the initrd image, changing
the line line that reads

mount -t tmpfs -o 'size=5%' initramfsdevs $devdir

to

mount -t tmpfs -o 'size=10%' initramfsdevs $devdir

instead.

Then I dropped mdadm and rmmod into the ./sbin/ directory

rebuild initrd with:

cd /base/of/initrd/image
find ./ | cpio -H newc --create | gzip -9 >/boot/new-initrd-image

Rebooting and then getting shell prompt...

Doing 'rmmod raid1 ; insmod raid1.ko' didn't help.
Doing 'mdadm /dev/md0 --stop ; mdadm /dev/md0 --run' did not help.

Any one else got any ideas?


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

Robbie Dinn <robbie@microbus.com> writes:

> Any one else got any ideas?

Had a look today, figured mkinitrd has a bug which causes it using the
default kernel modules, not the xen kernel ones in case you have both
-default and -xen installed (which most likely is the case).

Try the patch below, rerun mkinitrd, reboot and see whenever it works
better then.

HTH,

Gerd

--- /sbin/mkinitrd.o 2005-05-10 14:52:30.201725832 +0200
+++ /sbin/mkinitrd 2005-05-10 15:11:45.752785097 +0200
@@ -1671,6 +1671,8 @@
fi

# Filter modules into fs and non-fs (driver) modules
+ fs_modules=""
+ drv_modules=""
for module in $resolved_modules; do
case $module in
*/kernel/fs/*)

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

Dear Gerd

>Robbie Dinn <robbie@xxxxxxxxxxxx> writes:

>> Any one else got any ideas?

>Had a look today, figured mkinitrd has a bug which
>causes it using the
>default kernel modules, not the xen kernel ones in
>case you have both
>-default and -xen installed (which most likely is the
>case).

You were correct at least in my case...

>Try the patch below, rerun mkinitrd, reboot and see
>whenever it works
>better then.

Did, but no success, so I killed the setup and just
installed using nothing but the xen kernel and still
no success

greets chris
>HTH,

> Gerd

>--- /sbin/mkinitrd.o 2005-05-10 14:52:30.201725832
>+0200
>+++ /sbin/mkinitrd 2005-05-10 15:11:45.752785097
>+0200
>@@ -1671,6 +1671,8 @@
> fi
>
> # Filter modules into fs and non-fs (driver)
>modules
>+ fs_modules=""
>+ drv_modules=""
> for module in $resolved_modules; do
> case $module in
> */kernel/fs/*)






___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de

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

Gerd Knorr wrote:
> Had a look today, figured mkinitrd has a bug which causes it using the
> default kernel modules, not the xen kernel ones in case you have both
> -default and -xen installed (which most likely is the case).
>
> Try the patch below, rerun mkinitrd, reboot and see whenever it works
> better then.

I can confirm what Chris Epicier reported.

Your patch does indeed fix the mkinitrd bug. I looked at the contents
of the generated initrd and it now contains only the disired modules.
Thank you.

However the software raid1 (mirror) is still not working with
kernel-2.6.11.4-20a-xen from the SuSE-9.3 distribution. I guess
the mkinitrd bug isn't the source of the problem.

I tried various kernels from Kurt Garloff's web page
http://www.suse.de/~garloff/linux/xen/

Here is what I found

kernel version software raid1 status
kernel-2.6.11.4-20a-xen broken
kernel-xen-2.6.8-24.14.i586.rpm working
kernel-xen-2.6.10-20.i586.rpm broken
kernel-xen-2.6.11.4-21.i586.rpm broken

So I have a workaround, use kernel-xen-2.6.8-24.14.i586.rpm .

Thanks for your help.

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

Hi Gerd,

On Tuesday 10 May 2005 15:19, Gerd Knorr wrote:
> Robbie Dinn <robbie@microbus.com> writes:
> > Any one else got any ideas?
>
> Had a look today, figured mkinitrd has a bug which causes it using the
> default kernel modules, not the xen kernel ones in case you have both
> -default and -xen installed (which most likely is the case).
>
> Try the patch below, rerun mkinitrd, reboot and see whenever it works
> better then.
>
> HTH,
>
> Gerd
>
> --- /sbin/mkinitrd.o 2005-05-10 14:52:30.201725832 +0200
> +++ /sbin/mkinitrd 2005-05-10 15:11:45.752785097 +0200
> @@ -1671,6 +1671,8 @@
> fi
>
> # Filter modules into fs and non-fs (driver) modules
> + fs_modules=""
> + drv_modules=""
> for module in $resolved_modules; do
> case $module in
> */kernel/fs/*)

both variables are local to mkinitrd_kernel(), so they don't need to be
initialized separately. The bug must be somewhere else, sorry.

Could you please run mkinitrd via bash so that we see the trace,

bash -x /sbin/mkinitrd?

Thanks,
--
Andreas Gruenbacher <agruen@suse.de>
SUSE Labs, SUSE LINUX PRODUCTS GMBH

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

Hi there

I have just tested robie's workauround and confirm:

kernel-xen-2.6.8-24.14.i586.rpm working

I succeded in booting Dom 0, now moving on to Dom U:
wish me luck!

chris






___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de

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

> > # Filter modules into fs and non-fs (driver) modules
> > + fs_modules=""
> > + drv_modules=""

> both variables are local to mkinitrd_kernel(),

They are not, at least not in the version shipped with 9.3:

eskarina kraxel ~# grep fs_modules /sbin/mkinitrd
fs_modules="${fs_modules}${fs_modules:+\n}${module}"
done < <(echo -e "$fs_modules")
eskarina kraxel ~#

Maybe you look at something more recent?

Gerd


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

> However the software raid1 (mirror) is still not working with
> kernel-2.6.11.4-20a-xen from the SuSE-9.3 distribution. I guess
> the mkinitrd bug isn't the source of the problem.

Any chance the initrd attempts to load the raid6 module?
If so, can you try to prevent it from doing that? I'm not
sure how the initrd decides which raid modules it should
pick, maybe it's simply listed in /etc/sysconfig/kernel,
in the INITRD_MODULES variable.

Just loading the raid6 module in a xen domain makes my
machine oops, log below. I'd guess it's because the
module attempts to use mmx within the kernel, which is
a bit tricky because you have to save/restore userspace
fp state for that. Could be a corner case which simply
doesn't work with xen.

Gerd

==============================[ cut here ]==============================
raid6: int32x1 114 MB/s
raid6: int32x2 123 MB/s
raid6: int32x4 105 MB/s
raid6: int32x8 108 MB/s
general protection fault: 0000 [#1]
Modules linked in: raid6 raid5 xor raid1 raid0 md autofs4 ipv6 snd_pcm_oss snd_mixer_oss snd_seq_midi snd_seq_midi_event snd_seq snd_ens1370 gameport snd_rawmidi snd_seq_device snd_pcm snd_timer snd_page_alloc snd_ak4531_codec snd af_packet budget_ci tda1004x firmware_class budget_core dvb_core saa7146 ttpci_eeprom stv0299 tda9887 tuner saa7134 video_buf v4l2_common v4l1_compat soundcore ir_common videodev tun bridge edd evdev joydev sg st sr_mod nls_iso8859_1 nls_cp437 vfat fat intel_agp uhci_hcd agpgart usbcore tulip i2c_piix4 i2c_core dm_mod parport_pc lp parport ext3 jbd ide_cd cdrom ide_disk sym53c8xx scsi_transport_spi piix ide_core sd_mod scsi_mod
CPU: 0
EIP: 0061:[<f0d0463f>] Not tainted VLI
EFLAGS: 00011296 (2.6.11.4-20a-xen)
EIP is at raid6_mmx1_gen_syndrome+0x1f/0xb0 [raid6]
eax: eb3f1000 ebx: eb3dff48 ecx: eb3dff48 edx: 00001000
esi: 0000000f edi: 00000012 ebp: 00001000 esp: eb3dfe9c
ds: 007b es: 007b ss: 0069
Process modprobe (pid: 6457, threadinfo=eb3de000 task=ee0bba80)
Stack: eb3f1000 eb3f0000 0000000a fbfee000 c011e9e2 00000001 00000082 00000000
c011ea97 eb3dfef4 c010e46b 0000001b c011a330 00000000 00000000 c0106203
ffffdd26 fbfee000 00000000 eb3dff48 c010974f eb3dfef4 ffffdd26 f0d151cc
Call Trace:
[<c011e9e2>] __do_softirq+0x52/0xc0
[<c011ea97>] do_softirq+0x47/0x60
[<c010e46b>] do_IRQ+0x3b/0x70
[<c011a330>] __call_console_drivers+0x40/0x60
[<c0106203>] evtchn_do_upcall+0x53/0xa0
[<c010974f>] hypervisor_callback+0x37/0x40
[<f09de0fe>] raid6_select_algo+0xde/0x201 [raid6]
[<f09de005>] raid6_init+0x5/0x20 [raid6]
[<c0131592>] sys_init_module+0x122/0x1b0
[<c0109590>] syscall_call+0x7/0xb
Code: c0 c1 e8 17 83 e0 01 c3 8d 74 26 00 55 89 d5 57 89 c7 56 8d 70 fd 53 83 ec 78 89 cb 8b 44 b1 04 89 44 24 04 8b 44 b1 08 89 04 24 <0f> 20 c0 0f 06 89 44 24 74 9b dd 74 24 08 9b 0f 6f 05 c4 51 d1


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

Gerd Knorr wrote:
> Any chance the initrd attempts to load the raid6 module?
> If so, can you try to prevent it from doing that? I'm not
> sure how the initrd decides which raid modules it should
> pick, maybe it's simply listed in /etc/sysconfig/kernel,
> in the INITRD_MODULES variable.
>

Unfortunately, I am fairly sure (95% confident ?) that there
was no raid6.ko in the initrd, only raid1.ko. But I can't go
back to check because I have wiped the domain 0. I will have
to reinstall.

I will try to capture the boot time chatter with a serial
console.


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

Gerd Knorr wrote:
> Any chance the initrd attempts to load the raid6 module?
> If so, can you try to prevent it from doing that? I'm not
> sure how the initrd decides which raid modules it should
> pick, maybe it's simply listed in /etc/sysconfig/kernel,
> in the INITRD_MODULES variable.

I have
INITRD_MODULE="piix jdb ext3 raid1 dm_mod"

I am using your patched mkinitrd which correctly builds
the initrd. I have reproduced the serial console output
below. That shows modules ide_cd, dm_snapshot, md
and ide_core also present.
raid6 is absent.


Note for the boot messages below, I am using raid1
but I only have one disk attached! The other disk of the
pair has data on it that I don't want to wipe. I believe
using just the one disk did not affect the outcome. The
system behaved the same as in an earlier test where I
had both disks present. And of course the system boots
fine with a non-xen kernel.

Also note that near the end, the init script helpfully
dumps you into a shell, so I ran a few commands.

PS I should also add that the ide drive for /dev/hda
is working OK because I was able to mount /dev/hda1
(the /boot filesystem) onto /mnt. It just struck me that
that would be an easy root to smuggle in some debugging
tools!

-------------%<--%<--------------------
__ __ ____ ___
\ \/ /___ _ __ |___ \ / _ \
\ // _ \ '_ \ __) || | | |
/ \ __/ | | | / __/ | |_| |
/_/\_\___|_| |_| |_____(_)___/

http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory

Xen version 2.0 (abuild@suse.de) (gcc version 3.3.5 20050117
(prerelease) (SUSE Linux)) Wed Mar 23 23:11:00 UTC 2005
Latest ChangeSet: information unavailable

(XEN) Physical RAM map:
(XEN) 0000000000000000 - 00000000000a0000 (usable)
(XEN) 00000000000f0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 0000000014000000 (usable)
(XEN) 00000000ffff0000 - 0000000100000000 (reserved)
(XEN) System RAM: 319MB (327296kB)
(XEN) Xen heap: 10MB (10744kB)
(XEN) CPU0: Before vendor init, caps: 0383f9ff 00000000 00000000, vendor
= 0
(XEN) CPU caps: 0383f9ff 00000000 00000000 00000000
(XEN) ACPI: Unable to locate RSDP
(XEN) Using scheduler: Borrowed Virtual Time (bvt)
(XEN) Initializing CPU#0
(XEN) Detected 735.016 MHz processor.
(XEN) Local APIC disabled by BIOS -- reenabling.
(XEN) Found and enabled local APIC!
(XEN) CPU0: Before vendor init, caps: 0383fbff 00000000 00000000, vendor
= 0
(XEN) CPU caps: 0383fbff 00000000 00000000 00000000
(XEN) CPU0 booted
(XEN) SMP motherboard not detected.
(XEN) enabled ExtINT on CPU#0
(XEN) ESR value before enabling vector: 00000000
(XEN) ESR value after enabling vector: 00000000
(XEN) Using local APIC timer interrupts.
(XEN) Calibrating APIC timer for CPU0...
(XEN) ..... CPU speed is 735.0015 MHz.
(XEN) ..... Bus speed is 66.8182 MHz.
(XEN) ..... bus_scale = 0x0000446D
(XEN) Time init:
(XEN) .... System Time: 20001153ns
(XEN) .... cpu_freq: 00000000:2BCF77B0
(XEN) .... scale: 00000001:5C4A9401
(XEN) .... Wall Clock: 1115925102s 60000us
(XEN) PCI: PCI BIOS revision 2.10 entry at 0xfa780, last bus=1
(XEN) PCI: Using configuration type 1
(XEN) PCI: Probing PCI hardware
(XEN) PCI: Probing PCI hardware (bus 00)
(XEN) PCI: Using IRQ router default [8086/7110] at 00:07.0
(XEN) mtrr: v2.0 (20020519)
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen-ELF header found:
'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=2.0,VIRT_BASE=0xC0000000,LOADER=generic,PT_MODE_WRITABLE'

(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Kernel image: 00c00000->00e8b448
(XEN) Initrd image: 00e8c000->01217e00
(XEN) Dom0 alloc.: 01400000->11400000
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0100000->c03daafc
(XEN) Init. ramdisk: c03db000->c0766e00
(XEN) Phys-Mach map: c0767000->c07a7000
(XEN) Page tables: c07a7000->c07ab000
(XEN) Start info: c07ab000->c07ac000
(XEN) Boot stack: c07ac000->c07ad000
(XEN) TOTAL: c0000000->c0c00000
(XEN) ENTRY ADDRESS: c0100000
(XEN) Scrubbing DOM0 RAM: ...done.
(XEN) Initrd len 0x38be00, start at 0xc03db000
(XEN) Scrubbing Free RAM: ....done.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
input to Xen).
Linux version 2.6.11.4-20a-xen (geeko@buildhost) (gcc version 3.3.5
20050117 (prerelease) (SUSE Linux)) #1 Wed Mar 23 21:52:37 UTC 2005
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000010000000 (usable)
0MB HIGHMEM available.
256MB LOWMEM available.
DMI not present.
IRQ lockup detection disabled
Allocating PCI resources starting at 10000000 (gap: 10000000:f0000000)
Built 1 zonelists
Kernel command line: root=/dev/system/dom0_root selinux=0
splash=silent console=ttyS0 showopts
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 32768 bytes)
Xen reported: 735.016 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 252288k/262144k available (1876k kernel code, 9564k reserved,
558k data, 128k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode...
Ok.
Security Framework v1.0.0 initialized
SELinux: Disabled at boot.
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 128K
CPU: Intel Celeron (Coppermine) stepping 0a
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... disabled
checking if image is initramfs... it is
Freeing initrd memory: 3631k freed
NET: Registered protocol family 16
PCI: Using configuration type Xen
Linux Plug and Play Support v0.97 (c) Adam Belay
xen_mem: Initialising balloon driver.
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Probing PCI hardware (bus 01)
PCI: Probing PCI hardware
TC classifier action (bugs to netdev@oss.sgi.com cc hadi@cyberus.ca)
audit: initializing netlink socket (disabled)
audit(1115925107.320:0): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
loop: loaded (max 8 devices)
Xen virtual console successfully installed as ttyS
Event-channel device installed.
Initialising Xen netif backend
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
NET: Registered protocol family 1
NET: Registered protocol family 8
NET: Registered protocol family 20
Freeing unused kernel memory: 128k freed
Starting udev
Creating devices
input: AT Translated Set 2 keyboard on isa0060/serio0
Loading kernel/drivers/ide/ide-core.ko
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Loading kernel/drivers/ide/pci/piix.ko
PIIX4: IDE controller at PCI slot 0000:00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio
hda: ST3120022A, ATA DISK drive
hdb: DM-2000TE, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Loading kernel/drivers/md/md.ko
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
Loading kernel/drivers/md/raid1.ko
md: raid1 personality registered as nr 3
Loading kernel/drivers/md/dm-mod.ko
device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
Loading kernel/drivers/md/dm-snapshot.ko
Loading kernel/drivers/ide/ide-disk.ko
hda: max request size: 1024KiB
hda: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=16383/255/63,
UDMA(33)
hda: cache flushes supported
hda: hda1 hda2 hda3
Loading kernel/drivers/cdrom/cdrom.ko
Loading kernel/drivers/ide/ide-cd.ko
hdb: ATAPI 50X DVD-ROM drive, 256kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
Waiting for /dev/mapper/control to appear: ok
Loading kernel/fs/jbd/jbd.ko
Loading kernel/fs/ext3/ext3.ko
raidautorun ...
done...
Waiting for device /dev/system/dom0_root to appear: . Unable to find
volume group "system"
. Unable to find volume group "system"
. Unable to find volume group "system"
. Unable to find volume group "system"
. Unable to find volume group "system"
Reading all physical volumes. This may take a while...
No volume groups found
Unable to find volume group "system"
not found -- exiting to /bin/sh
sh: can't access tty; job control turned off
$ cat /proc/modules
ext3 138248 0 - Live 0xd08be000
jbd 63652 1 ext3, Live 0xd085c000
ide_cd 39940 0 - Live 0xd088a000
cdrom 38688 1 ide_cd, Live 0xd087f000
ide_disk 18304 0 - Live 0xd0829000
dm_snapshot 18204 0 - Live 0xd0823000
dm_mod 59772 1 dm_snapshot, Live 0xd086f000
raid1 17408 0 - Live 0xd081d000
md 45136 1 raid1, Live 0xd084f000
piix 10372 0 [permanent], Live 0xd0812000
ide_core 123520 3 ide_cd,ide_disk,piix, Live 0xd082f000
$ ls /lib/modules
2.6.11.4-20a-xen
$ ls /lib/modules/2.6.11.4-20a-xen/kernel/drivers/md
dm-mod.ko dm-snapshot.ko md.ko raid1.ko
$ ls /sys/block
hda loop1 loop4 loop7 ram1 ram12 ram15 ram4 ram7
hdb loop2 loop5 md0 ram10 ram13 ram2 ram5 ram8
loop0 loop3 loop6 ram0 ram11 ram14 ram3 ram6 ram9
$ ls /sys/block/md0
dev range removable size stat
$ cat /block/md0/dev
/block/md0/dev: No such file or directory
$ cat /block/sy
/block/sy: No such file or directory
$ cat /sys/block/md0/dev
9:0
$ cat /sys/block/md0/size
0
$ cat /proc/mdstat
Personalities : [raid1]
unused devices: <none>
$ exit
error: not found
[: open: unexpected operator
Mounting root /dev/system/dom0_root
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Kernel panic - not syncing: Attempted to kill init!
<0>Rebooting in 1 seconds..

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

> Note for the boot messages below, I am using raid1
> but I only have one disk attached! The other disk of the
> pair has data on it that I don't want to wipe. I believe
> using just the one disk did not affect the outcome.

It shouldn't, yes. That is the point of having a raid ;)

> Linux version 2.6.11.4-20a-xen (geeko@buildhost) (gcc version 3.3.5

> Kernel command line: root=/dev/system/dom0_root selinux=0
^^^^^^^^^^^^^^^^^^^^^^^^^^
Hmm, that looks strange. Shouldn't that be /dev/md0?
How do your grub entries look like? What boot messages
do you get when booting the default kernel?

> raidautorun ...
> done...
> Waiting for device /dev/system/dom0_root to appear: . Unable to find
> volume group "system"
> . Unable to find volume group "system"
> . Unable to find volume group "system"
> . Unable to find volume group "system"
> . Unable to find volume group "system"
> Reading all physical volumes. This may take a while...
> No volume groups found
> Unable to find volume group "system"

Hmm, tries to activate lvm. Doesn't find volume groups. Not
that surprising ...

> $ ls /sys/block
> hda loop1 loop4 loop7 ram1 ram12 ram15 ram4 ram7
> hdb loop2 loop5 md0 ram10 ram13 ram2 ram5 ram8
> loop0 loop3 loop6 ram0 ram11 ram14 ram3 ram6 ram9

So md0 is there, good.

> $ cat /sys/block/md0/dev
> 9:0

Fine.

> $ cat /sys/block/md0/size
> 0

Hmm. Not sure whenever this is a problem.

Gerd

--
-mm seems unusually stable at present.
-- akpm about 2.6.12-rc3-mm3

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

Gerd Knorr wrote:
>>Kernel command line: root=/dev/system/dom0_root selinux=0
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^
> Hmm, that looks strange. Shouldn't that be /dev/md0?
> How do your grub entries look like? What boot messages
> do you get when booting the default kernel?
>
Sorry, I didn't provide all the information.

I forgot to mention that I was using LVM on top of raid1.

I'll append the boot messages for the default kernel at
the end of the message.

My grub entry

title XEN
kernel (hd0,0)/xen.gz dom0_mem=262144 com1=9600,8n1
module (hd0,0)/vmlinuz-xen root=/dev/system/dom0_root \
selinux=0 splash=silent console=ttyS0 showopts
module (hd0,0)/initrd-xen


Here is what my disk layout looks like

/dev/hda
/dev/hda1 ext3 mounted on /boot in domain 0
/dev/hda2 swap unused at present
/dev/hda3 software rsid

/dev/hdc
/dev/hdc1 ext3 mounted on /foot in domain 0
(to boot from if /dev/hda is missing!)
/dev/hdc2 ext3 unused at present
/dev/hdc3 software rsid

/dev/md0 (/dev/hda3 + /dev/hdc3)

volume group 'system' using physical volume /dev/md0
volume groups
/dev/system/dom0_root root filesystem for domain 0
/dev/system/domU1_root root filesystem for domain 1
/dev/system/domU2_root root filesystem for domain 2
etc

grub installed in MBR's of both /dev/hda and /dev/hdc
and in /boot and /foot file systems.

>
>>raidautorun ...
>>done...
>>Waiting for device /dev/system/dom0_root to appear: . Unable to find
>>volume group "system"
>>. Unable to find volume group "system"
>>. Unable to find volume group "system"
>>. Unable to find volume group "system"
>>. Unable to find volume group "system"
>> Reading all physical volumes. This may take a while...
>> No volume groups found
>> Unable to find volume group "system"
>
>
> Hmm, tries to activate lvm. Doesn't find volume groups. Not
> that surprising ...

I think it is not finding the volume groups because vgchange
in the init script can't read the physical volume /dev/md0.

If you wish, I could simply do away with LVM for testing purposes
and put the root filesystem on the bare /dev/md0 device.

>
>
>>$ ls /sys/block
>>hda loop1 loop4 loop7 ram1 ram12 ram15 ram4 ram7
>>hdb loop2 loop5 md0 ram10 ram13 ram2 ram5 ram8
>>loop0 loop3 loop6 ram0 ram11 ram14 ram3 ram6 ram9
>
>
> So md0 is there, good.
>
>
>>$ cat /sys/block/md0/dev
>>9:0
>
>
> Fine.
>
>
>>$ cat /sys/block/md0/size
>>0
>
>
> Hmm. Not sure whenever this is a problem.
I was expecting to see the value 232299648 in /sys/block/md0/size
This struck me as strange. There is enough of the raid stuff
working for you to see the /sys/block/md0 directory, but not
enough working to see a correctly reported size or an entry
corresponding to md0 in /proc/mdstat.

>
> Gerd
>

Here is the boot messages for the -default kernel:
Sorry it is a bit garbled. And yuk, escape sequences!
Perhaps this should be an attachment instead?

-----------%<----%<---------------

Linux version 2.6.11.4-20a-default (geeko@buildhost) (gcc version 3.3.5
20050117 (prerelease) (SUSE Linux)) #1 Wed Mar 23 21:52:37 UTC 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000014000000 (usable)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
320MB LOWMEM available.
DMI not present.
ACPI: Unable to locate RSDP
Allocating PCI resources starting at 14000000 (gap: 14000000:ebff0000)
Built 1 zonelists
Kernel command line: root=/dev/system/dom0_root selinux=0
splash=silent console=ttyS0,9600n8 showopts
bootsplash: silent mode.
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 32768 bytes)
Detected 735.057 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 319416k/327680k available (1865k kernel code, 7660k reserved,
659k data, 204k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode...
Ok.
Security Framework v1.0.0 initialized
SELinux: Disabled at boot.
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 128K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: Intel Celeron (Coppermine) stepping 0a
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
checking if image is initramfs... it is
Freeing initrd memory: 1542k freed
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfa780, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20050211
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Using IRQ router default [8086/7110] at 0000:00:07.0
TC classifier action (bugs to netdev@oss.sgi.com cc hadi@cyberus.ca)
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
audit: initializing netlink socket (disabled)
audit(1115994033.879:0): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
loop: loaded (max 8 devices)
mice: PS/2 mouse device common for all mice
input: PC Speaker
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
NET: Registered protocol family 1
Freeing unused kernel memory: 204k freed
Starting udev
Creating devicinput: AT Translated Set 2 keyboard on isa0060/serio0
es
Loading kernel/drivers/ide/ide-cUniform Multi-Platform E-IDE driver
Revision: 7.00alpha2
ore.ko
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Loading kernel/dPIIX4: IDE controller at PCI slot 0000:00:07.1
rivers/ide/pci/pPIIX4: chipset revision 1
iix.ko
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio
hda: ST3120022A, ATA DISK drive
hdb: DM-2000TE, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Loading kernel/dmd: raid1 personality registered as nr 3
rivers/md/raid1.device-mapper: 4.4.0-ioctl (2005-01-12) initialised:
dm-devel@redhat.com
ko
Loading kernel/drivers/md/dm-mod.ko
Loadinghda: max request size: 1024KiB
kernel/drivers/hda: 234441648 sectors (120034 MB)md/dm-snapshot.k
w/2048KiB Cacheo
Loading kerne, CHS=16383/255/63l/drivers/ide/id, UDMA(33)e-disk.ko

hda: cache flushes supported
hda: hda1 hda2 hda3
Loading kernel/drivers/cdrom/cdrom.ko
Loading kernel/drivers/ide/ide-cd.ko
hdb: ATAPI 50X DVD-ROM drive, 256kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
Waiting for /dev/mapper/control to appear: ok
Loading kernel/fs/jbd/jbd.ko
Loading kernel/fs/ext3/ext3.ko
ramd: Autodetecting RAID arrays.
idautorun ...
md: autorun ...
md: considering hda3 ...
md: adding hda3 ...
md: created md0
md: bind<hda3>
md: running: <hda3>
raid1: raid set md0 active with 1 out of 2 mirrors
md: ... autorun DONE.
done...
Waiting for device /dev/system/dom0_root to appear: . 4 logical
volume(s) in volume group "system" now active
ok
rootfs: major=253 minor=0 devn=64768
fsck 1.36kjournald starting. Commit interval 5 seconds
(05-Feb-2005)
EXT3 FS on dm-0, /dev/system/dom0internal journal
_root: clean, 12EXT3-fs: mounted filesystem with ordered data mode.
3770/393216 files, 726204/786432 blocks
fsck succeeded. Mounting root device read-write.
Mounting root /dev/system/dom0_root
INIT: version 2.85 booting
System Boot Control: Running /etc/init.d/boot
Mounting /proc filesystem7[.?25l [.80C[.10D[.1;32mdone[.m8[.?25h
Mounting sysfs on /sys7[.?25l [.80C[.10D[.1;32mdone[.m8[.?25h
Mounting /dev/pts7[.?25l [.80C[.10D[.1;32mdone[.m8[.?25h
Boot logging started on /dev/ttyS0(/dev/console) at Fri May 13
15:20:43 2005
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
Mounting shared memory FS on /dev/shm [.80C[.10D[.1;32mdone[.m
Activating swap-devices in /etc/fstab...
7[.?25l[.1A [.80C[.10D[.1;32mdone[.m8[.?25hActivating device mapper...
Starting udevd Creating /dev/mapper/control character device with
major:10 minor:63.
7[.?25l [.80C[.10D[.1;32mdone[.m8[.?25h
7[.?25l [.80C[.10D[.1;32mdone[.m8[.?25h
Scanning for LVM volume groups...
Coldplug
Coldplug: cleaning /events Reading all physical volumes. This may
take a while...
hwup: Loading module 'lp' for device 'printer'
parport0: PC-style at 0x378 [PCSPP,TRISTATE,EPP]
Found volume group "system" using metadata type lvm2
Activating LVM volume glp0: using parport0 (polling).
roups...
4 logical volume(s) in volume group "system" now active
7[.?25l [.80C[.10D[.1;32mdone[.m8[.?25h
processing events7[.?25l [.80C[.10D[.1;32mdone[.m8[.?25h
Checking file systems...
fsck 1.36 (05-Feb-2005)
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /boot] fsck.ext3 -a /dev/hda1
/foot1 (/dev/hda1): clean, 47/66400 files, 8230/132528 blocks
7[.?25l[.1A [.80C[.10D[.1;32mdone[.m8[.?25hSetting up kernel module
dependencies (if required)e100: Intel(R) PRO/100 Network Driver, 3.4.1-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
e100: eth0: e100_probe: addr 0xe7041000, irq 10, MAC addr 00:80:79:03:17:8F
e100: eth1: e100_probe: addr 0xe7040000, irq 11, MAC addr 00:80:79:83:17:8F
piix4_smbus 0000:00:07.3: Found 0000:00:07.3 device
SCSI subsystem initialized
st: Version 20041025, fixed bufsize 32768, s/g segs 256
BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected an Intel 440GX Chipset.
agpgart: Maximum main memory to use for agp memory: 263M
agpgart: AGP aperture is 64M @ 0xe0000000
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v2.2
uhci_hcd 0000:00:07.2: UHCI Host Controller
uhci_hcd 0000:00:07.2: irq 10, io base 0xe000
uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
usb 1-1: new low speed USB device using uhci_hcd and address 2
7[.?25l [.80C[.10D[.1;32mdone[.m8[.?25h
Mounting local fkjournald starting. Commit interval 5 seconds
ile systems... EXT3 FS on hda1,
proc on /proc tinternal journal
ype proc (rw)
EXT3-fs: mounted filesystem with ordered data mode.
sysfs on /sys type sysfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/hda1 on /boot type ext3 (rw,acl,user_xattr)
7[.?25l[.1A [.80C[.10D[.1;32mdone[.m8[.?25hSetting up the CMOS
clock7[.?25l [.80C[.10D[.1;32mdone[.m8[.?25h
Creating /var/log/boot.msg
7[.?25l[.1A [.80C[.10D[.1;32mdone[.m8[.?25hLoading required kernel
modules
Capability LSM initialized
ieee1394: raw1394: /dev/raw1394 device initialized
video1394: Installed video1394 module
7[.?25l[.1A [.80C[.10D[.1;32mdone[.m8[.?25hcdrom: open failed.
Setting up hostname 'adler'7[.?25l [.80C[.10D[.1;32mdone[.m8[.?25h
Setting up loopback interface lo
Restore device permissions7[.?25l [.80C[.10D[.1;32mdone[.m8[.?25h
lo IP address: 127.0.0.1/8
usbcore: registered new driver hiddev
input: USB HID v1.00 Mouse [1241:1111] on usb-0000:00:07.2-1
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.01:USB HID core driver
7[?25l done8[?25h
Disk /dev/md0 doesn't contain a valid partition table
Activating remaining swap-devices in /etc/fstab...
7[?25l done8[?25hStarting Firewall
Initialization (phase 1 of 2) Setting current sysctl status from
/etc/sysctl.conf
NET: Registered protocol family 10
Disabled Privacy Extensions on device c033d600(lo)
IPv6 over IPv4 tunneling driver
ip6_tables: (C) 2000-2002 Netfilter core team
Disabled Privacy Extensions on device cc0f1400(sit0)
SuSEfirewall2: Warning: ip6tables does not support state matching.
Extended IPv6 support disabled.
net.ipv4.icmp_echo_ignore_broadcasts = 1
net.ipv4.conf.all.rp_filter = 1
7[?25l p_tables: (C) 2000-2002 Netfilter core team
0Ddoneip_conntrack version 2.1 (2560 buckets, 20480 max) - 248
bytes per conntrack
8[?25h
Enabling syn flood protection done
Disabling IP forwarding7[?25l done8[?25h
Disabling IPv6 forwarding7[?25l done8[?25h
Disabling IPv6 privacy7[?25l done8[?25h
7[?25l done8[?25h
7[?25l done8[?25h
System Boot Control: The system has been set up
System Boot Control: Running /etc/init.d/boot.local
7[?25l done8[?25h INIT: Entering runlevel: 5
Boot logging started on /dev/ttyS0(/dev/console) at Fri May 13
15:21:51 2005
Master Resource Control: previous runlevel: N, switching to
runlevel: 5
Starting syslog services7[?25l done8[?25h
Starting D-BUS daemon7[?25l done8[?25h
Setting up network interfaces:
Initializing random number generator7[?25l
done8[?25h
Starting resource manager7[?25l done8[?25h
Loading keymap qwerty/uk.map.gz
7[?25l done8[?25h lo
lo IP address: 127.0.0.1/8
7[?25l done8[?25he100: eth0: e100_watchdog:
link up, 10Mbps, half-duplex
eth0 device: Intel Corporation 8255xER/82551IT Fast Ethernet
Controller (rev 09)
eth0 configuration: eth-id-00:80:79:03:17:8f
eth0 IP address: 10.0.0.19/8
7[?25l done8[?25hLoading compose table
winkeys shiftctrl latin1.add7[?25l done8[?25h
Start Unicode mode
7[?25l done8[?25hLoading console font
lat9w-16.psfu -m trivial G0:loadable
7[?25l done8[?25h eth1 device:
Intel Corporation 8255xER/82551IT Fast Ethernet Controller (rev 09)
eth1 No configuration found for eth1
7[?25l unused8[?25hWaiting for mandatory
devices: eth-id-00:80:79:03:f1:55
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
eth-id-00:80:79:03:f1:55 No interface found
7[?25l failed8[?25hSetting up service
network . . . . . . . . . . . . . . .
.7[?25l failed8[?25h
Starting RPC portmap daemon7[?25l done8[?25h
Importing Net File System (NFS) unused
Starting mail service (Postfix)Starting nfsboot
(sm-notify) 7[?25l done8[?25h
7[?25l done8[?25h
Starting sound driver7[?25l done8[?25h
Starting CRON daemon7[?25l done8[?25h
Starting HAL daemonStarting hardware scan on boot7[?25l
done8[?25h
Starting Name Service Cache Daemon7[?25l
done8[?25h
This machine supports APM Starting powersaved 7[?25l
failed8[?25h
Starting SSH daemon7[?25l done8[?25h
Starting service xdm7[?25l done8[?25h
Starting xend 7[?25l unused8[?25h
7[?25l done8[?25h
Master Resource Control: runlevel 5 has been reached
Failed services in runlevel 5: network powersaved
Skipped services in runlevel 5: nfs xend

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

> volume group 'system' using physical volume /dev/md0
> volume groups
> /dev/system/dom0_root root filesystem for domain 0

Oh, ok.

> >>$ cat /sys/block/md0/size
> >>0
> >
> >Hmm. Not sure whenever this is a problem.
> I was expecting to see the value 232299648 in /sys/block/md0/size
> This struck me as strange.

Yes, it's at least suspious.

> md: considering hda3 ...
> md: adding hda3 ...
> md: created md0
> md: bind<hda3>
> md: running: <hda3>
> raid1: raid set md0 active with 1 out of 2 mirrors

... and these lines are missing when booting the xen kernel.

Ok, so it looks like /dev/md0 wasn't activated correctly for
some reason, thus lvm didn't find any volume groups there.

I don't think placing the root fs directly in /dev/md0 would
change anything. You'll get the different error then (rootfs
mount fails). But the reason most likely is the same: md0
is not (or only half-way) activated ...

Gerd


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

> >>raidautorun ...
> >>done...

Turned out that 'CONFIG_BLK_DEV_MD=m' is the culpit. For some
strange reason the raidautorun ioctl is not supported when md is
built as module ...

Gerd

--
-mm seems unusually stable at present.
-- akpm about 2.6.12-rc3-mm3

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