xen and reiserfs

xen and reiserfs

[Jim Martin]

Hi
I'm running Xen on Fedora core 3...
uname -a
Linux groucho 2.6.10-1.1148_FC4xen0 #1 SMP Sat Feb 19 15:15:24 EST 2005 
i686 i686 i386 GNU/Linux

# xm list
Name              Id  Mem(MB)  CPU  State  Time(s)  Console
Domain-0           0      121    0  r----    140.9

What I'm trying to do is get SuSE 9.2 to come up in it's own domain..
/dev/hda2 = root for FC-3
/dev/hdb2 = root for SuSE 9.2

My config file in /etc/xen (suse)
# cat suse
kernel ="/boot/vmlinuz-2.6.10-1.1148_FC4xenU"
memory = 64
name = "suse"
nics = 1
disk = ['phy:hdb2,hdb2,w']
root = "/dev/hdb2 ro"

My problem...
When I run 'xm create -c suse' everything seems fine right up to the 
point of
mounting root and I get this error:
md: ... autorun DONE.
Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(3,66)
 <0>Rebooting in 1 seconds..

This is a reiserfs /dev/hdb2 - does this xen kernel support reiserfs ?
Or is my config file wrong ?

Thanks !!
Jim (Jim Martin - jamesm@wwt.net)


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: xen and reiserfs

[Robin Green]

On Mon, 21 Feb 2005, Jim Martin wrote:
> Hi
> I'm running Xen on Fedora core 3...
> uname -a
> Linux groucho 2.6.10-1.1148_FC4xen0 #1 SMP Sat Feb 19 15:15:24 EST 2005 i686 
> i686 i386 GNU/Linux
>
> # xm list
> Name              Id  Mem(MB)  CPU  State  Time(s)  Console
> Domain-0           0      121    0  r----    140.9
>
> What I'm trying to do is get SuSE 9.2 to come up in it's own domain..
> /dev/hda2 = root for FC-3
> /dev/hdb2 = root for SuSE 9.2
>
> My config file in /etc/xen (suse)
> # cat suse
> kernel ="/boot/vmlinuz-2.6.10-1.1148_FC4xenU"
> memory = 64
> name = "suse"
> nics = 1
> disk = ['phy:hdb2,hdb2,w']
> root = "/dev/hdb2 ro"
>
> My problem...
> When I run 'xm create -c suse' everything seems fine right up to the point of
> mounting root and I get this error:
> md: ... autorun DONE.
> Kernel panic - not syncing: VFS: Unable to mount root fs on 
> unknown-block(3,66)
> <0>Rebooting in 1 seconds..
>
> This is a reiserfs /dev/hdb2 - does this xen kernel support reiserfs ?
> Or is my config file wrong ?

Xen kernels have no problem with reiserfs (indeed, they should work with 
any filesystem). Your problem is due to the fact that you are booting with
a Fedora kernel, which unlike (IIRC) the suse kernels, has reiserfs as a
module, not compiled in.

Not to worry, all you have to do is add an initrd line. Unfortunately,
the kernel-xenU package from Fedora does not currently ship with an 
initrd, so I think you'll have to build one yourself. Try this command
(I haven't tested it, but it should work):

  mkinitrd /boot/initrd-2.6.10-1.1148_FC4xenU.img 2.6.10-1.1148_FC4xenU

Then add

  ramdisk=/boot/initrd-2.6.10-1.1148_FC4xenU.img

to your config file in /etc/xen.

The kernel will load the necessary module(s) automatically so it should
not be necessary to modify the initrd produced by mkinitrd.

Hope this helps,
-- 
Robin


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: xen and reiserfs

[Mark Williamson]

> I'm running Xen on Fedora core 3...
> uname -a
> Linux groucho 2.6.10-1.1148_FC4xen0 #1 SMP Sat Feb 19 15:15:24 EST 2005
> i686 i686 i386 GNU/Linux
>
> # xm list
> Name              Id  Mem(MB)  CPU  State  Time(s)  Console
> Domain-0           0      121    0  r----    140.9

Looks good.

> What I'm trying to do is get SuSE 9.2 to come up in it's own domain..
> /dev/hda2 = root for FC-3
> /dev/hdb2 = root for SuSE 9.2
>
> My config file in /etc/xen (suse)
> # cat suse
> kernel ="/boot/vmlinuz-2.6.10-1.1148_FC4xenU"
> memory = 64
> name = "suse"
> nics = 1
> disk = ['phy:hdb2,hdb2,w']
> root = "/dev/hdb2 ro"

Also looks good, although I doubt the FC4 kernel includes support for ReiserFS 
- you might need to build a new one.

> My problem...
> When I run 'xm create -c suse' everything seems fine right up to the
> point of
> mounting root and I get this error:
> md: ... autorun DONE.
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(3,66)
>  <0>Rebooting in 1 seconds..
>
> This is a reiserfs /dev/hdb2 - does this xen kernel support reiserfs ?
> Or is my config file wrong ?

I don't think this is a filesystem support problem - it looks like it's not 
getting that far.  However, SuSE 9.2 uses udev, so it seems likely you'll 
need to boot the SuSE domain with an initrd.  The stock one in your 
SuSE /boot may do the trick (If that doesn't work, I think there's also a 
Xen-specific one in the SuSE Xen rpms).

Does anyone know whether FC4 is currently on the -stable, -testing or 
-unstable version of Xen?  If it's -stable or -testing, you could use the 
standard SuSE Xen kernel, otherwise you'll have to build your own with 
ReiserFS support.

Cheers,
Mark

> Thanks !!
> Jim (Jim Martin - jamesm@wwt.net)
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: xen and reiserfs

[Jim Martin]

Thanks Robin !
This got me a lot further on..but now I'm seeing this..

[root@groucho xen]# xm create -c suse
Using config file "suse".
Started domain suse, console on port 9607
************ REMOTE CONSOLE: CTRL-] TO QUIT ********
Linux version 2.6.10-1.1148_FC4xenU (bhcompile@bugs.build.redhat.com) 
(gcc version 3.4.3 20050209 (Red Hat 3.4.3-19)) #1 SMP Sat Feb 19 
15:28:44 EST 2005
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000004000000 (usable)
64MB LOWMEM available.
Using x86 segment limits to approximate NX protection
DMI not present.
IRQ lockup detection disabled
Built 1 zonelists
Kernel command line:  root=/dev/hdb2 ro
Initializing CPU#0
 >>>snip<<<<
Creating root device
Mounting root filesystem
VFS: Can't find ext3 filesystem on dev hdb2.
mount: error 22 mounting ext3
mount: error 2 mounting none
Switching to new root
switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!
 <0>Rebooting in 1 seconds..

[root@groucho ~]# xm list
Name              Id  Mem(MB)  CPU  State  Time(s)  Console
Domain-0           0      121    0  r----   5515.8
suse               7       64    0  ---s-      1.0    9607

SO CLOSE.....

Jim
---------------------------------------------------------------




Robin Green wrote:

> On Mon, 21 Feb 2005, Jim Martin wrote:
>
>> Hi
>> I'm running Xen on Fedora core 3...
>> uname -a
>> Linux groucho 2.6.10-1.1148_FC4xen0 #1 SMP Sat Feb 19 15:15:24 EST 
>> 2005 i686 i686 i386 GNU/Linux
>>
>> # xm list
>> Name              Id  Mem(MB)  CPU  State  Time(s)  Console
>> Domain-0           0      121    0  r----    140.9
>>
>> What I'm trying to do is get SuSE 9.2 to come up in it's own domain..
>> /dev/hda2 = root for FC-3
>> /dev/hdb2 = root for SuSE 9.2
>>
>> My config file in /etc/xen (suse)
>> # cat suse
>> kernel ="/boot/vmlinuz-2.6.10-1.1148_FC4xenU"
>> memory = 64
>> name = "suse"
>> nics = 1
>> disk = ['phy:hdb2,hdb2,w']
>> root = "/dev/hdb2 ro"
>>
>> My problem...
>> When I run 'xm create -c suse' everything seems fine right up to the 
>> point of
>> mounting root and I get this error:
>> md: ... autorun DONE.
>> Kernel panic - not syncing: VFS: Unable to mount root fs on 
>> unknown-block(3,66)
>> <0>Rebooting in 1 seconds..
>>
>> This is a reiserfs /dev/hdb2 - does this xen kernel support reiserfs ?
>> Or is my config file wrong ?
>
>
> Xen kernels have no problem with reiserfs (indeed, they should work 
> with any filesystem). Your problem is due to the fact that you are 
> booting with
> a Fedora kernel, which unlike (IIRC) the suse kernels, has reiserfs as a
> module, not compiled in.
>
> Not to worry, all you have to do is add an initrd line. Unfortunately,
> the kernel-xenU package from Fedora does not currently ship with an 
> initrd, so I think you'll have to build one yourself. Try this command
> (I haven't tested it, but it should work):
>
>  mkinitrd /boot/initrd-2.6.10-1.1148_FC4xenU.img 2.6.10-1.1148_FC4xenU
>
> Then add
>
>  ramdisk=/boot/initrd-2.6.10-1.1148_FC4xenU.img
>
> to your config file in /etc/xen.
>
> The kernel will load the necessary module(s) automatically so it should
> not be necessary to modify the initrd produced by mkinitrd.
>
> Hope this helps,



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: xen and reiserfs

[Robin Green]

On Mon, 21 Feb 2005, Mark Williamson wrote:
>> I'm running Xen on Fedora core 3...
>> uname -a
>> Linux groucho 2.6.10-1.1148_FC4xen0 #1 SMP Sat Feb 19 15:15:24 EST 2005
>> i686 i686 i386 GNU/Linux
>>
>> # xm list
>> Name              Id  Mem(MB)  CPU  State  Time(s)  Console
>> Domain-0           0      121    0  r----    140.9
>
> Looks good.
>
>> What I'm trying to do is get SuSE 9.2 to come up in it's own domain..
>> /dev/hda2 = root for FC-3
>> /dev/hdb2 = root for SuSE 9.2
>>
>> My config file in /etc/xen (suse)
>> # cat suse
>> kernel ="/boot/vmlinuz-2.6.10-1.1148_FC4xenU"
>> memory = 64
>> name = "suse"
>> nics = 1
>> disk = ['phy:hdb2,hdb2,w']
>> root = "/dev/hdb2 ro"
>
> Also looks good, although I doubt the FC4 kernel includes support for ReiserFS

Actually, it does - but as a module, not built-in. So he needs to build an 
initrd - see my previous message.

> I don't think this is a filesystem support problem - it looks like it's not
> getting that far.  However, SuSE 9.2 uses udev

So does Fedora Core 3, so its initrds should work.

> so it seems likely you'll
> need to boot the SuSE domain with an initrd.

Yup

>  The stock one in your
> SuSE /boot may do the trick

Not with this kernel it won't, because this is a Fedora xenU kernel.

> (If that doesn't work, I think there's also a
> Xen-specific one in the SuSE Xen rpms).

The only trouble with that is, the SuSE Xen rpms probably use a different
version of the Xen patch, which might be incompatible, as you point out.

> Does anyone know whether FC4 is currently on the -stable, -testing or
> -unstable version of Xen?

-unstable

-- 
Robin


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: xen and reiserfs

[Robin Green]

On Mon, 21 Feb 2005, Jim Martin wrote:

> Thanks Robin !
> This got me a lot further on..but now I'm seeing this..

Woops! My mistake. Do this instead:

  mkdir /mnt/suse
  mount -t reiserfs -o ro /dev/hdb2 /mnt/suse
  rm -f /boot/initrd-2.6.10-1.1148_FC4xenU.img

  # all on one line
  mkinitrd --fstab=/mnt/suse/etc/fstab /boot/initrd-2.6.10-1.1148_FC4xenU.img 2.6.10-1.1148_FC4xenU

  umount /mnt/suse  # DO NOT OMIT THIS STEP!

That should detect the root filesystem type correctly. Then try
xm create again.

--
Robin

>
> [root@groucho xen]# xm create -c suse
> Using config file "suse".
> Started domain suse, console on port 9607
> ************ REMOTE CONSOLE: CTRL-] TO QUIT ********
> Linux version 2.6.10-1.1148_FC4xenU (bhcompile@bugs.build.redhat.com) (gcc 
> version 3.4.3 20050209 (Red Hat 3.4.3-19)) #1 SMP Sat Feb 19 15:28:44 EST 
> 2005
> BIOS-provided physical RAM map:
> Xen: 0000000000000000 - 0000000004000000 (usable)
> 64MB LOWMEM available.
> Using x86 segment limits to approximate NX protection
> DMI not present.
> IRQ lockup detection disabled
> Built 1 zonelists
> Kernel command line:  root=/dev/hdb2 ro
> Initializing CPU#0
>>>> snip<<<<
> Creating root device
> Mounting root filesystem
> VFS: Can't find ext3 filesystem on dev hdb2.
> mount: error 22 mounting ext3
> mount: error 2 mounting none
> Switching to new root
> switchroot: mount failed: 22
> umount /initrd/dev failed: 2
> Kernel panic - not syncing: Attempted to kill init!
> <0>Rebooting in 1 seconds..
>
> [root@groucho ~]# xm list
> Name              Id  Mem(MB)  CPU  State  Time(s)  Console
> Domain-0           0      121    0  r----   5515.8
> suse               7       64    0  ---s-      1.0    9607
>
> SO CLOSE.....
>
> Jim
> ---------------------------------------------------------------
>
>
>
>
> Robin Green wrote:
>
>> On Mon, 21 Feb 2005, Jim Martin wrote:
>> 
>>> Hi
>>> I'm running Xen on Fedora core 3...
>>> uname -a
>>> Linux groucho 2.6.10-1.1148_FC4xen0 #1 SMP Sat Feb 19 15:15:24 EST 2005 
>>> i686 i686 i386 GNU/Linux
>>> 
>>> # xm list
>>> Name              Id  Mem(MB)  CPU  State  Time(s)  Console
>>> Domain-0           0      121    0  r----    140.9
>>> 
>>> What I'm trying to do is get SuSE 9.2 to come up in it's own domain..
>>> /dev/hda2 = root for FC-3
>>> /dev/hdb2 = root for SuSE 9.2
>>> 
>>> My config file in /etc/xen (suse)
>>> # cat suse
>>> kernel ="/boot/vmlinuz-2.6.10-1.1148_FC4xenU"
>>> memory = 64
>>> name = "suse"
>>> nics = 1
>>> disk = ['phy:hdb2,hdb2,w']
>>> root = "/dev/hdb2 ro"
>>> 
>>> My problem...
>>> When I run 'xm create -c suse' everything seems fine right up to the point 
>>> of
>>> mounting root and I get this error:
>>> md: ... autorun DONE.
>>> Kernel panic - not syncing: VFS: Unable to mount root fs on 
>>> unknown-block(3,66)
>>> <0>Rebooting in 1 seconds..
>>> 
>>> This is a reiserfs /dev/hdb2 - does this xen kernel support reiserfs ?
>>> Or is my config file wrong ?
>> 
>> 
>> Xen kernels have no problem with reiserfs (indeed, they should work with 
>> any filesystem). Your problem is due to the fact that you are booting with
>> a Fedora kernel, which unlike (IIRC) the suse kernels, has reiserfs as a
>> module, not compiled in.
>> 
>> Not to worry, all you have to do is add an initrd line. Unfortunately,
>> the kernel-xenU package from Fedora does not currently ship with an initrd, 
>> so I think you'll have to build one yourself. Try this command
>> (I haven't tested it, but it should work):
>> 
>>  mkinitrd /boot/initrd-2.6.10-1.1148_FC4xenU.img 2.6.10-1.1148_FC4xenU
>> 
>> Then add
>> 
>>  ramdisk=/boot/initrd-2.6.10-1.1148_FC4xenU.img
>> 
>> to your config file in /etc/xen.
>> 
>> The kernel will load the necessary module(s) automatically so it should
>> not be necessary to modify the initrd produced by mkinitrd.
>> 
>> Hope this helps,
>
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: xen and reiserfs

[Jim Martin]

WAHOO !!! It worked !!
Beautiful Robin !

Name              Id  Mem(MB)  CPU  State  Time(s)  Console
Domain-0        0      121          0  r----        7554.8
suse                 9       64          0  -b---           6.3        9609

Thanks for the help !!!!!
This is a great project ! I'm really looking forward to using this in 
the future...
Now to go play... :-D
Cheers !
Jim
----------------------------------------------------------------------------------------------

Robin Green wrote:

> On Mon, 21 Feb 2005, Jim Martin wrote:
>
>> Thanks Robin !
>> This got me a lot further on..but now I'm seeing this..
>
>
> Woops! My mistake. Do this instead:
>
>  mkdir /mnt/suse
>  mount -t reiserfs -o ro /dev/hdb2 /mnt/suse
>  rm -f /boot/initrd-2.6.10-1.1148_FC4xenU.img
>
>  # all on one line
>  mkinitrd --fstab=/mnt/suse/etc/fstab 
> /boot/initrd-2.6.10-1.1148_FC4xenU.img 2.6.10-1.1148_FC4xenU
>
>  umount /mnt/suse  # DO NOT OMIT THIS STEP!
>
> That should detect the root filesystem type correctly. Then try
> xm create again.
>
> -- 
> Robin
>
>>
>> [root@groucho xen]# xm create -c suse
>> Using config file "suse".
>> Started domain suse, console on port 9607
>> ************ REMOTE CONSOLE: CTRL-] TO QUIT ********
>> Linux version 2.6.10-1.1148_FC4xenU (bhcompile@bugs.build.redhat.com) 
>> (gcc version 3.4.3 20050209 (Red Hat 3.4.3-19)) #1 SMP Sat Feb 19 
>> 15:28:44 EST 2005
>> BIOS-provided physical RAM map:
>> Xen: 0000000000000000 - 0000000004000000 (usable)
>> 64MB LOWMEM available.
>> Using x86 segment limits to approximate NX protection
>> DMI not present.
>> IRQ lockup detection disabled
>> Built 1 zonelists
>> Kernel command line:  root=/dev/hdb2 ro
>> Initializing CPU#0
>>
>>>>> snip<<<<
>>>>
>> Creating root device
>> Mounting root filesystem
>> VFS: Can't find ext3 filesystem on dev hdb2.
>> mount: error 22 mounting ext3
>> mount: error 2 mounting none
>> Switching to new root
>> switchroot: mount failed: 22
>> umount /initrd/dev failed: 2
>> Kernel panic - not syncing: Attempted to kill init!
>> <0>Rebooting in 1 seconds..
>>
>> [root@groucho ~]# xm list
>> Name              Id  Mem(MB)  CPU  State  Time(s)  Console
>> Domain-0           0      121    0  r----   5515.8
>> suse               7       64    0  ---s-      1.0    9607
>>
>> SO CLOSE.....
>>
>> Jim
>> ---------------------------------------------------------------
>>
>>
>>
>>
>> Robin Green wrote:
>>
>>> On Mon, 21 Feb 2005, Jim Martin wrote:
>>>
>>>> Hi
>>>> I'm running Xen on Fedora core 3...
>>>> uname -a
>>>> Linux groucho 2.6.10-1.1148_FC4xen0 #1 SMP Sat Feb 19 15:15:24 EST 
>>>> 2005 i686 i686 i386 GNU/Linux
>>>>
>>>> # xm list
>>>> Name              Id  Mem(MB)  CPU  State  Time(s)  Console
>>>> Domain-0           0      121    0  r----    140.9
>>>>
>>>> What I'm trying to do is get SuSE 9.2 to come up in it's own domain..
>>>> /dev/hda2 = root for FC-3
>>>> /dev/hdb2 = root for SuSE 9.2
>>>>
>>>> My config file in /etc/xen (suse)
>>>> # cat suse
>>>> kernel ="/boot/vmlinuz-2.6.10-1.1148_FC4xenU"
>>>> memory = 64
>>>> name = "suse"
>>>> nics = 1
>>>> disk = ['phy:hdb2,hdb2,w']
>>>> root = "/dev/hdb2 ro"
>>>>
>>>> My problem...
>>>> When I run 'xm create -c suse' everything seems fine right up to 
>>>> the point of
>>>> mounting root and I get this error:
>>>> md: ... autorun DONE.
>>>> Kernel panic - not syncing: VFS: Unable to mount root fs on 
>>>> unknown-block(3,66)
>>>> <0>Rebooting in 1 seconds..
>>>>
>>>> This is a reiserfs /dev/hdb2 - does this xen kernel support reiserfs ?
>>>> Or is my config file wrong ?
>>>
>>>
>>>
>>> Xen kernels have no problem with reiserfs (indeed, they should work 
>>> with any filesystem). Your problem is due to the fact that you are 
>>> booting with
>>> a Fedora kernel, which unlike (IIRC) the suse kernels, has reiserfs 
>>> as a
>>> module, not compiled in.
>>>
>>> Not to worry, all you have to do is add an initrd line. Unfortunately,
>>> the kernel-xenU package from Fedora does not currently ship with an 
>>> initrd, so I think you'll have to build one yourself. Try this command
>>> (I haven't tested it, but it should work):
>>>
>>>  mkinitrd /boot/initrd-2.6.10-1.1148_FC4xenU.img 2.6.10-1.1148_FC4xenU
>>>
>>> Then add
>>>
>>>  ramdisk=/boot/initrd-2.6.10-1.1148_FC4xenU.img
>>>
>>> to your config file in /etc/xen.
>>>
>>> The kernel will load the necessary module(s) automatically so it should
>>> not be necessary to modify the initrd produced by mkinitrd.
>>>
>>> Hope this helps,
>>
>>
>>
>
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: xen and reiserfs

[Kurt Garloff]

[-- Attachment #1: Type: text/plain, Size: 729 bytes --]

Hi Jim,

On Mon, Feb 21, 2005 at 09:28:20AM -0600, Jim Martin wrote:
> md: ... autorun DONE.
> Kernel panic - not syncing: VFS: Unable to mount root fs on 
> unknown-block(3,66)

hdb2

> <0>Rebooting in 1 seconds..
> 
> This is a reiserfs /dev/hdb2 - does this xen kernel support reiserfs ?
> Or is my config file wrong ?

Did you compile reiserfs statically into the kernel?
If not, you'll need to put the module into an initrd.
(Use -s off if you use the suse mkinitrd.)

Regards,
-- 
Kurt Garloff                   <kurt@garloff.de>             [Koeln, DE]
Physics:Plasma modeling <garloff@plasimo.phys.tue.nl> [TU Eindhoven, NL]
Linux: SUSE Labs (Director)    <garloff@suse.de>            [Novell Inc]

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Xen and ReiserFS

[David F Barrera]

I am unable to boot Dom0 on a machine with Reiser file systems. Reiser
support is built into the xen0 kernel. I have similar setup with ext3
file systems working just fine, so I don't think it is a setup problem.
I have tried booting with and without and initrd file, booting with the
original Linux distro initrd file, etc, but nothing seems to work. I
recall seeing a thread about ReiserFS on this list some time ago, but I
don't remember what the resolution was. Any ideas would be appreciated.

Here's a snip of the log:

xen_mem: Initialising balloon driver.
SCSI subsystem initialized
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Ignoring BAR0-3 of IDfloppy0: no floppy controllers found
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
HP CISS Driver (v 2.6.4)
Intel(R) PRO/1000 Network Driver - version 5.6.10.1-k2
Copyright (c) 1999-2004 Intel Corporation.
pcnet32.c:v1.30i 06.28.2004 tsbogend@alpha.franken.de
e100: Intel(R) PRO/100 Network Driver, 3.3.6-k2-NAPI
e100: Copyright(c) 1999-2004 Intel Corporation
tg3.c:v3.23 (February 15, 2005)
eth0: Tigon3 [partno(BCM95704A41) rev 2100 PHY(serdes)] (PCIX:133MHz:64-
bit) 10/100/1000BaseT Ethernet 00:11:25:9d:63:18
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1]
TSOcap[0]
eth1: Tigon3 [partno(BCM95704A41) rev 2100 PHY(serdes)] (PCIX:133MHz:64-
bit) 10/100/1000BaseT Ethernet 00:11:25:9d:63:19
eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1]
TSOcap[1]
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Xen virtual console successfully installed as ttyS0
Event-channel device installed.
Blkif backend is using grant tables.
Initialising Xen netif backend
Blkif frontend is using grant tables.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
ICH5: IDE controller at PCI slot 0000:00:1f.1
ICH5: chipset revisioRed Hat/Adaptec aacraid driver (1.1.2-lk2 Jun  9
2005)
3ware Storage Controller device driver for Linux v1.26.02.000.
Fusion MPT base driver 3.01.18
Copyright (c) 1999-2004 LSI Logic Corporation
mptbase: Initiating ioc0 bringup
ioc0: 53C1030: Capabilities={Initiator}
mptbase: Initiating ioc0 recovery
mptbase: Initiating ioc0 recovery
mptbase: Initiating ioc0 recovery
mptbase: Initiating ioc0 recovery
mptbase: Initiating ioc0 recovery
mptbase: Initiating ioc0 recovery
Fusion MPT SCSI Host driver 3.01.18
scsi0 : ioc0: LSI53C1030, FwRev=01032700h, Ports=1, MaxQ=222, IRQ=10
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting bus reset! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting host reset! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptbase: ioc0: WARNING - Unexpected doorbell active!
mptbase: ioc0: ERROR - Wait IOC_READY state timeout(1500)!
mptbase: ioc0: ERROR - Doorbell INT timeout (count=999), IntStatus=8!
mptscsih: ioc0: Issue of TaskMgmt failed!
mptscsih: ioc0: WARNING - Error issuing abort task!
(sc=ffff88001f178a80)
scsi: Device offlined - not ready after error recovery: host 0 channel 0
id 0 lun 0
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting bus reset! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting host reset! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptbase: ioc0: WARNING - Unexpected doorbell active!
mptbase: ioc0: ERROR - Wait IOC_READY state timeout(1500)!
mptbase: ioc0: ERROR - Doorbell INT timeout (count=999), IntStatus=8!
mptscsih: ioc0: Issue of TaskMgmt failed!
mptscsih: ioc0: WARNING - Error issuing abort task!
(sc=ffff88001f178a80)
scsi: Device offlined - not ready after error recovery: host 0 channel 0
id 1 lun 0
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting bus reset! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting host reset! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptbase: ioc0: WARNING - Unexpected doorbell active!
mptbase: ioc0: ERROR - Wait IOC_READY state timeout(1500)!
mptbase: ioc0: ERROR - Doorbell INT timeout (count=999), IntStatus=8!
mptscsih: ioc0: Issue of TaskMgmt failed!
mptscsih: ioc0: WARNING - Error issuing abort task!
(sc=ffff88001f178a80)
scsi: Device offlined - not ready after error recovery: host 0 channel 0
id 2 lun 0
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting bus reset! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting host reset! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptbase: ioc0: WARNING - Unexpected doorbell active!
mptbase: ioc0: ERROR - Wait IOC_READY state timeout(1500)!
mptbase: ioc0: ERROR - Doorbell INT timeout (count=999), IntStatus=8!
mptscsih: ioc0: Issue of TaskMgmt failed!
mptscsih: ioc0: WARNING - Error issuing abort task!
(sc=ffff88001f178a80)
scsi: Device offlined - not ready after error recovery: host 0 channel 0
id 3 lun 0
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting bus reset! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting host reset! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptbase: ioc0: WARNING - Unexpected doorbell active!
mptbase: ioc0: ERROR - Wait IOC_READY state timeout(1500)!
mptbase: ioc0: ERROR - Doorbell INT timeout (count=999), IntStatus=8!
mptscsih: ioc0: Issue of TaskMgmt failed!
mptscsih: ioc0: WARNING - Error issuing abort task!
(sc=ffff88001f178a80)
scsi: Device offlined - not ready after error recovery: host 0 channel 0
id 4 lun 0
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting bus reset! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting host reset! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptbase: ioc0: WARNING - Unexpected doorbell active!
mptbase: ioc0: ERROR - Wait IOC_READY state timeout(1500)!
mptbase: ioc0: ERROR - Doorbell INT timeout (count=999), IntStatus=8!
mptscsih: ioc0: Issue of TaskMgmt failed!
mptscsih: ioc0: WARNING - Error issuing abort task!
(sc=ffff88001f178a80)
scsi: Device offlined - not ready after error recovery: host 0 channel 0
id 5 lun 0
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting bus reset! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting host reset! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptbase: ioc0: WARNING - Unexpected doorbell active!
mptbase: ioc0: ERROR - Wait IOC_READY state timeout(1500)!
mptbase: ioc0: ERROR - Doorbell INT timeout (count=999), IntStatus=8!
mptscsih: ioc0: Issue of TaskMgmt failed!
mptscsih: ioc0: WARNING - Error issuing abort task!
(sc=ffff88001f178a80)
scsi: Device offlined - not ready after error recovery: host 0 channel 0
id 6 lun 0
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting bus reset! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting host reset! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptbase: ioc0: WARNING - Unexpected doorbell active!
mptbase: ioc0: ERROR - Wait IOC_READY state timeout(1500)!
mptbase: ioc0: ERROR - Doorbell INT timeout (count=999), IntStatus=8!
mptscsih: ioc0: Issue of TaskMgmt failed!
mptscsih: ioc0: WARNING - Error issuing abort task!
(sc=ffff88001f178a80)
scsi: Device offlined - not ready after error recovery: host 0 channel 0
id 8 lun 0
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting bus reset! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting host reset! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptbase: ioc0: WARNING - Unexpected doorbell active!
mptbase: ioc0: ERROR - Wait IOC_READY state timeout(1500)!
mptbase: ioc0: ERROR - Doorbell INT timeout (count=999), IntStatus=8!
mptscsih: ioc0: Issue of TaskMgmt failed!
mptscsih: ioc0: WARNING - Error issuing abort task!
(sc=ffff88001f178a80)
scsi: Device offlined - not ready after error recovery: host 0 channel 0
id 9 lun 0
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting bus reset! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting host reset! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptbase: ioc0: WARNING - Unexpected doorbell active!
mptbase: ioc0: ERROR - Wait IOC_READY state timeout(1500)!
mptbase: ioc0: ERROR - Doorbell INT timeout (count=999), IntStatus=8!
mptscsih: ioc0: Issue of TaskMgmt failed!
mptscsih: ioc0: WARNING - Error issuing abort task!
(sc=ffff88001f178a80)
scsi: Device offlined - not ready after error recovery: host 0 channel 0
id 10 lun 0
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting bus reset! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting host reset! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptbase: ioc0: WARNING - Unexpected doorbell active!
mptbase: ioc0: ERROR - Wait IOC_READY state timeout(1500)!
mptbase: ioc0: ERROR - Doorbell INT timeout (count=999), IntStatus=8!
mptscsih: ioc0: Issue of TaskMgmt failed!
mptscsih: ioc0: WARNING - Error issuing abort task!
(sc=ffff88001f178a80)
scsi: Device offlined - not ready after error recovery: host 0 channel 0
id 11 lun 0
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting bus reset! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting host reset! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptbase: ioc0: WARNING - Unexpected doorbell active!
mptbase: ioc0: ERROR - Wait IOC_READY state timeout(1500)!
mptbase: ioc0: ERROR - Doorbell INT timeout (count=999), IntStatus=8!
mptscsih: ioc0: Issue of TaskMgmt failed!
mptscsih: ioc0: WARNING - Error issuing abort task!
(sc=ffff88001f178a80)
scsi: Device offlined - not ready after error recovery: host 0 channel 0
id 12 lun 0
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting bus reset! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting host reset! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptbase: ioc0: WARNING - Unexpected doorbell active!
mptbase: ioc0: ERROR - Wait IOC_READY state timeout(1500)!
mptbase: ioc0: ERROR - Doorbell INT timeout (count=999), IntStatus=8!
mptscsih: ioc0: Issue of TaskMgmt failed!
mptscsih: ioc0: WARNING - Error issuing abort task!
(sc=ffff88001f178a80)
scsi: Device offlined - not ready after error recovery: host 0 channel 0
id 13 lun 0
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting bus reset! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting host reset! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptbase: ioc0: WARNING - Unexpected doorbell active!
mptbase: ioc0: ERROR - Wait IOC_READY state timeout(1500)!
mptbase: ioc0: ERROR - Doorbell INT timeout (count=999), IntStatus=8!
mptscsih: ioc0: Issue of TaskMgmt failed!
mptscsih: ioc0: WARNING - Error issuing abort task!
(sc=ffff88001f178a80)
scsi: Device offlined - not ready after error recovery: host 0 channel 0
id 14 lun 0
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting bus reset! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptscsih: ioc0: >> Attempting host reset! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: >> Attempting task abort! (sc=ffff88001f178a80)
mptbase: Initiating ioc0 recovery
mptbase: ioc0: WARNING - Unexpected doorbell active!
mptbase: ioc0: ERROR - Wait IOC_READY state timeout(1500)!
mptbase: ioc0: ERROR - Doorbell INT timeout (count=999), IntStatus=8!
mptscsih: ioc0: Issue of TaskMgmt failed!
mptscsih: ioc0: WARNING - Error issuing abort task!
(sc=ffff88001f178a80)
scsi: Device offlined - not ready after error recovery: host 0 channel 0
id 15 lun 0
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard on isa0060/serio0
input: PS/2 Logitech Mouse on isa0060/serio1
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: 5, 131072 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
NET: Registered protocol family 1
NET: Registered protocol family 17
Bridge firewalling registered
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Insert root floppy and press ENTER



-- 
Regards,

David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "
                                                        Euripides

Re: Xen and ReiserFS

[Keir Fraser]

On 9 Jun 2005, at 21:13, David F Barrera wrote:

> I am unable to boot Dom0 on a machine with Reiser file systems. Reiser
> support is built into the xen0 kernel. I have similar setup with ext3
> file systems working just fine, so I don't think it is a setup problem.
> I have tried booting with and without and initrd file, booting with the
> original Linux distro initrd file, etc, but nothing seems to work. I
> recall seeing a thread about ReiserFS on this list some time ago, but I
> don't remember what the resolution was. Any ideas would be appreciated.

The boot log hasn't got as far as looking at the rootfs when the 
problems start. It looks like things go bad as soon as the SCSI driver 
starts to run. Does the same kernel work on the same machine if you 
point it at an ext3 system? Or do problems occur when you compile 
reiserfs into the kernel?

  -- Keir

Re: Xen and ReiserFS

[David F Barrera]

On Thu, 2005-06-09 at 21:23 +0100, Keir Fraser wrote:
> On 9 Jun 2005, at 21:13, David F Barrera wrote:
> 
> > I am unable to boot Dom0 on a machine with Reiser file systems. Reiser
> > support is built into the xen0 kernel. I have similar setup with ext3
> > file systems working just fine, so I don't think it is a setup problem.
> > I have tried booting with and without and initrd file, booting with the
> > original Linux distro initrd file, etc, but nothing seems to work. I
> > recall seeing a thread about ReiserFS on this list some time ago, but I
> > don't remember what the resolution was. Any ideas would be appreciated.
> 
> The boot log hasn't got as far as looking at the rootfs when the 
> problems start. It looks like things go bad as soon as the SCSI driver 
> starts to run. Does the same kernel work on the same machine if you 
> point it at an ext3 system? 

I have two identical machines with essentially the same setup, except
one has ext3 and the other has Reiser file systems. The same kernel
build works on the one that has ext3. 

> Or do problems occur when you compile 
> reiserfs into the kernel?
Reiserfs is compiled into the kernel by default. I tried compiling it as
a module and making sure the initrd file contains it, but it does not
make any difference.
> 
>   -- Keir
> 
> 

Re: Xen and ReiserFS

[Paul Larson]

[-- Attachment #1.1: Type: text/plain, Size: 1530 bytes --]

On Thu, 2005-06-09 at 15:51 -0500, David F Barrera wrote:
> On Thu, 2005-06-09 at 21:23 +0100, Keir Fraser wrote:
> > On 9 Jun 2005, at 21:13, David F Barrera wrote:
> > 
> > > I am unable to boot Dom0 on a machine with Reiser file systems. Reiser
> > > support is built into the xen0 kernel. I have similar setup with ext3
> > > file systems working just fine, so I don't think it is a setup problem.
> > > I have tried booting with and without and initrd file, booting with the
> > > original Linux distro initrd file, etc, but nothing seems to work. I
> > > recall seeing a thread about ReiserFS on this list some time ago, but I
> > > don't remember what the resolution was. Any ideas would be appreciated.
> > 
> > The boot log hasn't got as far as looking at the rootfs when the 
> > problems start. It looks like things go bad as soon as the SCSI driver 
> > starts to run. Does the same kernel work on the same machine if you 
> > point it at an ext3 system? 
> 
> I have two identical machines with essentially the same setup, except
> one has ext3 and the other has Reiser file systems. The same kernel
> build works on the one that has ext3. 
ReiserFS is working fine on my box, with both the current bitkeeper tree
and with last nights unstable build.  From your boot log though, it
looks like it's breaking down in the mpt scsi driver pretty badly.  Does
the other working machine also use this driver?

-- 
Thanks,
Paul Larson
plars@linuxtestproject.org
http://www.linuxtestproject.org

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Xen and ReiserFS

[David F Barrera]

On Thu, 2005-06-09 at 15:58 -0500, Paul Larson wrote:
> On Thu, 2005-06-09 at 15:51 -0500, David F Barrera wrote:
> > On Thu, 2005-06-09 at 21:23 +0100, Keir Fraser wrote:
> > > On 9 Jun 2005, at 21:13, David F Barrera wrote:
> > > 
> > > > I am unable to boot Dom0 on a machine with Reiser file systems. Reiser
> > > > support is built into the xen0 kernel. I have similar setup with ext3
> > > > file systems working just fine, so I don't think it is a setup problem.
> > > > I have tried booting with and without and initrd file, booting with the
> > > > original Linux distro initrd file, etc, but nothing seems to work. I
> > > > recall seeing a thread about ReiserFS on this list some time ago, but I
> > > > don't remember what the resolution was. Any ideas would be appreciated.
> > > 
> > > The boot log hasn't got as far as looking at the rootfs when the 
> > > problems start. It looks like things go bad as soon as the SCSI driver 
> > > starts to run. Does the same kernel work on the same machine if you 
> > > point it at an ext3 system? 
> > 
> > I have two identical machines with essentially the same setup, except
> > one has ext3 and the other has Reiser file systems. The same kernel
> > build works on the one that has ext3. 
> ReiserFS is working fine on my box, with both the current bitkeeper tree
> and with last nights unstable build.  From your boot log though, it
> looks like it's breaking down in the mpt scsi driver pretty badly.  Does
> the other working machine also use this driver?
Yes. They are identical machines.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: Xen and ReiserFS

[Andrew Theurer]

On Thursday 09 June 2005 16:03, David F Barrera wrote:
> On Thu, 2005-06-09 at 15:58 -0500, Paul Larson wrote:
> > On Thu, 2005-06-09 at 15:51 -0500, David F Barrera wrote:
> > > On Thu, 2005-06-09 at 21:23 +0100, Keir Fraser wrote:
> > > > On 9 Jun 2005, at 21:13, David F Barrera wrote:
> > > > > I am unable to boot Dom0 on a machine with Reiser file
> > > > > systems. Reiser support is built into the xen0 kernel. I have
> > > > > similar setup with ext3 file systems working just fine, so I
> > > > > don't think it is a setup problem. I have tried booting with
> > > > > and without and initrd file, booting with the original Linux
> > > > > distro initrd file, etc, but nothing seems to work. I recall
> > > > > seeing a thread about ReiserFS on this list some time ago,
> > > > > but I don't remember what the resolution was. Any ideas would
> > > > > be appreciated.
> > > >
> > > > The boot log hasn't got as far as looking at the rootfs when
> > > > the problems start. It looks like things go bad as soon as the
> > > > SCSI driver starts to run. Does the same kernel work on the
> > > > same machine if you point it at an ext3 system?
> > >
> > > I have two identical machines with essentially the same setup,
> > > except one has ext3 and the other has Reiser file systems. The
> > > same kernel build works on the one that has ext3.
> >
> > ReiserFS is working fine on my box, with both the current bitkeeper
> > tree and with last nights unstable build.  From your boot log
> > though, it looks like it's breaking down in the mpt scsi driver
> > pretty badly.  Does the other working machine also use this driver?
>
> Yes. They are identical machines.

Have you tried ext3 on the system which shows problems with reiserfs?  
If these are hot swap disks, can you swap the disks witht he two 
systems ans see what happens?  It really looks like the "broken" one 
has a scsi HW related issue.

-Andrew

Re: Xen and ReiserFS

[David F Barrera]

On Thu, 2005-06-09 at 16:18 -0500, Andrew Theurer wrote:
> On Thursday 09 June 2005 16:03, David F Barrera wrote:
> > On Thu, 2005-06-09 at 15:58 -0500, Paul Larson wrote:
> > > On Thu, 2005-06-09 at 15:51 -0500, David F Barrera wrote:
> > > > On Thu, 2005-06-09 at 21:23 +0100, Keir Fraser wrote:
> > > > > On 9 Jun 2005, at 21:13, David F Barrera wrote:
> > > > > > I am unable to boot Dom0 on a machine with Reiser file
> > > > > > systems. Reiser support is built into the xen0 kernel. I have
> > > > > > similar setup with ext3 file systems working just fine, so I
> > > > > > don't think it is a setup problem. I have tried booting with
> > > > > > and without and initrd file, booting with the original Linux
> > > > > > distro initrd file, etc, but nothing seems to work. I recall
> > > > > > seeing a thread about ReiserFS on this list some time ago,
> > > > > > but I don't remember what the resolution was. Any ideas would
> > > > > > be appreciated.
> > > > >
> > > > > The boot log hasn't got as far as looking at the rootfs when
> > > > > the problems start. It looks like things go bad as soon as the
> > > > > SCSI driver starts to run. Does the same kernel work on the
> > > > > same machine if you point it at an ext3 system?
> > > >
> > > > I have two identical machines with essentially the same setup,
> > > > except one has ext3 and the other has Reiser file systems. The
> > > > same kernel build works on the one that has ext3.
> > >
> > > ReiserFS is working fine on my box, with both the current bitkeeper
> > > tree and with last nights unstable build.  From your boot log
> > > though, it looks like it's breaking down in the mpt scsi driver
> > > pretty badly.  Does the other working machine also use this driver?
> >
> > Yes. They are identical machines.
> 
> Have you tried ext3 on the system which shows problems with reiserfs?  
> If these are hot swap disks, can you swap the disks witht he two 
> systems ans see what happens?  It really looks like the "broken" one 
> has a scsi HW related issue.
I read what you are saying, but the machine works fine with the distro
kernel. So, I don't believe it is a HW related issue.
> 
> -Andrew
> 

Re: Xen and ReiserFS

[David F Barrera]

OK. Mea culpa. I found out the problem was I had 'acpi=off' as a kernel
parameters in my grub entry for Xen, due to an earlier problem where it
was suggested to try it. Thanks for the responses.

On Fri, 2005-06-10 at 08:04 -0500, David F Barrera wrote:
> On Thu, 2005-06-09 at 16:18 -0500, Andrew Theurer wrote:
> > On Thursday 09 June 2005 16:03, David F Barrera wrote:
> > > On Thu, 2005-06-09 at 15:58 -0500, Paul Larson wrote:
> > > > On Thu, 2005-06-09 at 15:51 -0500, David F Barrera wrote:
> > > > > On Thu, 2005-06-09 at 21:23 +0100, Keir Fraser wrote:
> > > > > > On 9 Jun 2005, at 21:13, David F Barrera wrote:
> > > > > > > I am unable to boot Dom0 on a machine with Reiser file
> > > > > > > systems. Reiser support is built into the xen0 kernel. I have
> > > > > > > similar setup with ext3 file systems working just fine, so I
> > > > > > > don't think it is a setup problem. I have tried booting with
> > > > > > > and without and initrd file, booting with the original Linux
> > > > > > > distro initrd file, etc, but nothing seems to work. I recall
> > > > > > > seeing a thread about ReiserFS on this list some time ago,
> > > > > > > but I don't remember what the resolution was. Any ideas would
> > > > > > > be appreciated.
> > > > > >
> > > > > > The boot log hasn't got as far as looking at the rootfs when
> > > > > > the problems start. It looks like things go bad as soon as the
> > > > > > SCSI driver starts to run. Does the same kernel work on the
> > > > > > same machine if you point it at an ext3 system?
> > > > >
> > > > > I have two identical machines with essentially the same setup,
> > > > > except one has ext3 and the other has Reiser file systems. The
> > > > > same kernel build works on the one that has ext3.
> > > >
> > > > ReiserFS is working fine on my box, with both the current bitkeeper
> > > > tree and with last nights unstable build.  From your boot log
> > > > though, it looks like it's breaking down in the mpt scsi driver
> > > > pretty badly.  Does the other working machine also use this driver?
> > >
> > > Yes. They are identical machines.
> > 
> > Have you tried ext3 on the system which shows problems with reiserfs?  
> > If these are hot swap disks, can you swap the disks witht he two 
> > systems ans see what happens?  It really looks like the "broken" one 
> > has a scsi HW related issue.
> I read what you are saying, but the machine works fine with the distro
> kernel. So, I don't believe it is a HW related issue.
> > 
> > -Andrew
> > 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
-- 
Regards,

David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "
                                                        Euripides

Re: Xen and ReiserFS

[Kurt Garloff]

[-- Attachment #1.1: Type: text/plain, Size: 705 bytes --]

Hi David,

On Thu, Jun 09, 2005 at 03:13:05PM -0500, David F Barrera wrote:
> I am unable to boot Dom0 on a machine with Reiser file systems. Reiser
> support is built into the xen0 kernel. I have similar setup with ext3
> file systems working just fine, so I don't think it is a setup problem.
> I have tried booting with and without and initrd file, booting with the
> original Linux distro initrd file, etc, but nothing seems to work. I
> recall seeing a thread about ReiserFS on this list some time ago, but I
> don't remember what the resolution was. Any ideas would be appreciated.

We used reiser in testing successfully.

Strange!
-- 
Kurt Garloff, Director SUSE Labs, Novell Inc.

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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