Re: [Xen-users] Problem booting xen domU Guest

["Todd Deshane" <deshantm@xxxxxxxxx>]

On Fri, Jan 2, 2009 at 4:12 AM, Philipp <Xerberus999X@xxxxxxx> wrote:
> Thanks for hints Todd!
>
> The priviliged guest(dom0) is a 2.6.26.4 kernel (xen hypervisor 3.3.0). 
> Originally a vanilla kernel, manually patched. But I didnt encounter any 
> problems with that. I run several 2.6.18 domU´s (debian etch) on it, without 
> any trouble. The 2.6.28 I´m having these problems with, is a vanilla kernel 
> as well.
>

When you say manually patched, where are you getting the patches for dom0?

I haven't tried out the 2.6.28 kernel.org domU kernel yet, but I
haven't heard of any projects like this yet.

I suspect that it is still either the kernel config or the initial ram
disk, but I don't see anything obvious yet.

Your config here:
http://pastebin.com/m645174dd

Maybe others can take a look?


> Unfortunately there´s no option or flag in the 2.6.28 for any "Fusion MPT 
> device support". But on the other hand its not quite clear to me, what that 
> would be needed. As the domU would only communicate with the host through the 
> "Xen virtual block device support". And that one is enabled.
>

Yeah that is just a quick google for the errors you are seeing...Not
sure of the details of that.

> No I dont get into the initramfs prompt. These are the last messages I get:
> #######################################
> ....

Something is missing for sure. The sysfs stuff seems to be included.

I wonder if there is something (a module or the like) either missing
from or not loading...

Could it be that the domU is just missing some base package?

If I get a chance, I will try to build a kernel.org-based vanilla domU
kernel, but
there should be others that have tried/tested it. I would google around and also
look for others that have mentioned using testing the kernel.org stuff and get
their configs as an example.

One last thought, doublecheck:

/etc/modprobe.d/options
and
/etc/initramfs-tools/initramfs.conf

I have had weird problems with Ubuntu modprobe options that didn't work
well on a Xen kernel

For me, it was the following that broke libata from loading
options libata ignore_hpa=1

Best of luck.

Cheers,
Todd


> XENBUS: Device with no driver: device/console/0
> Freeing unused kernel memory: 264k freed
> /bin/cat: /sys/block/sda/dev: No such file or directory
> Waiting 1 seconds for /sys/block/sda/dev to show up
> /bin/cat: /sys/block/sda/dev: No such file or directory
> Waiting 2 seconds for /sys/block/sda/dev to show up
> /bin/cat: /sys/block/sda/dev: No such file or directory
> Waiting 4 seconds for /sys/block/sda/dev to show up
> /bin/cat: /sys/block/sda/dev: No such file or directory
> Waiting 8 seconds for /sys/block/sda/dev to show up
> /bin/cat: /sys/block/sda/dev: No such file or directory
> Waiting 16 seconds for /sys/block/sda/dev to show up
> /bin/cat: /sys/block/sda/dev: No such file or directory
> Device /sys/block/sda/dev seems to be down.
> /bin/mknod: missing operand after `b'
> Special files require major and minor device numbers.
> Try `/bin/mknod --help' for more information.
> /bin/cat: /sys/block/sda/sda1/dev: No such file or directory
> Waiting 1 seconds for /sys/block/sda/sda1/dev to show up
> /bin/cat: /sys/block/sda/sda1/dev: No such file or directory
> Waiting 2 seconds for /sys/block/sda/sda1/dev to show up
> /bin/cat: /sys/block/sda/sda1/dev: No such file or directory
> Waiting 4 seconds for /sys/block/sda/sda1/dev to show up
> /bin/cat: /sys/block/sda/sda1/dev: No such file or directory
> Waiting 8 seconds for /sys/block/sda/sda1/dev to show up
> /bin/cat: /sys/block/sda/sda1/dev: No such file or directory
> Waiting 16 seconds for /sys/block/sda/sda1/dev to show up
> /bin/cat: /sys/block/sda/sda1/dev: No such file or directory
> Device /sys/block/sda/sda1/dev seems to be down.
> /bin/mknod: missing operand after `b'
> Special files require major and minor device numbers.
> Try `/bin/mknod --help' for more information.
> mount: special device /dev/sda1 does not exist
> Switching root ...
> /usr/lib/yaird/exec/run_init: current directory on the same filesystem as the 
> root: Success
> Kernel panic - not syncing: Attempted to kill init!
> #######################################
>
>
> I already thought of something perhaps beeing wrong the ramdisk. But then 
> again, all necessary xen components are compiled into the kernel, and not as 
> module.
> Normally I use this command to create my ramdisk:
>
> yaird -f cpio -o /boot/kernel-2.6.28.ramdisk 2.6.28
>
>
>
>
>

-- 
Todd Deshane
http://todddeshane.net
http://runningxen.com

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