Re: [Xen-devel] Unable to boot Xen on top of Xen, any help?

[Derek Murray <Derek.Murray@xxxxxxxxxxxx>]

If making an initrd does not work, then it's possible that your dom0  
kernel build does not build all of the correct modules. You should be  
able to retrieve a kernel .config file for the non-Xen kernel  
(ideally, the distro would have a specific .config for a Xen dom0,  
which I know is the case for FC5), and use this as the configuration  
for building your dom0 kernel. Then try making an initrd as before.
Hope this helps.

Regards,

Derek.

On 30 May 2007, at 02:50, Mark Williamson wrote:

> Are you using an initrd in the guest?  Is your distro expecting you  
> to use
> one?
>
> Boot the guest non-Xen, then you can use mkinitrd to generate one  
> for your
> dom0 kernel and modify the grub.conf / menu.lst accordingly.
>
> Cheers,
> Mark
>
> On Wednesday 30 May 2007, Wei, Jinpeng wrote:
> > Hi Everyone,
> >
> > I am trying to run Xen-unstable in a HVM domain which is inside
> > Xen-unstable (I am using Intel VT-enabled processor). For the HVM  
> > domain
> > I am using a file-backed block device to hold the file system, so the
> > config file contains one line:
> >
> > disk = [ 'file:path/imgfile, ioemu:hda, w' ]
> >
> > But when I boot Xen-unstable in the HVM domain, I got the following
> > panic message:
> >
> > Xen virtual console successfully installed as ttyS0
> > Event-channel device installed.
> > ...
> > Freeing unused kernel memory: 192k freed
> > Red Hat nash version 5.1.19 starting
> > Mounting proc filesystem
> > Mounting sysfs filesystem
> > Creating /dev
> > Creating initial device nodes
> > Setting up hotplug.
> > input: ImExPS/2 Generic Explorer Mouse as /class/input/input1
> > Creating block device nodes.
> > Loading usbcore.ko module
> > usbcore: registered new driver usbfs
> > usbcore: registered new driver hub
> > Loading uhci-hcd.ko module
> > USB Universal Host Controller Interface driver v3.0
> > Loading ohci-hcd.ko module
> > Loading ehci-hcd.ko module
> > Loading jbd.ko module
> > Loading ext3.ko module
> > Loading ide-disk.ko module
> > Creating root device.
> > Mounting root filesystem.
> > mount: could not find filesystem '/dev/root'
> > Setting up other filesystems.
> > Setting up new root fs
> > setuproot: moving /dev failed: No such file or directory
> > no fstab.sys, mounting internal defaults
> > setuproot: error mounting /proc: No such file or directory
> > setuproot: error mounting /sys: No such file or directory
> > Switching to new root and running init.
> > unmounting old /dev
> > unmounting old /proc
> > unmounting old /sys
> > switchroot: mount failed: No such file or directory
> > Kernel panic - not syncing: Attempted to kill init!
> >
> > It looks like that the internal dom 0 Linux (Red Hat nash version
> > 5.1.19) does not recognize the disk device emulated by the  
> > external Xen.
> > This is because I can boot Fedora Core 6 in the same HVM domain, and
> > from dmesg I can see that the emulated disk was recognized as 'QEMU
> > HARDDISK, ATA DISK drive', but in the above message I can not see  
> > this
> > line.
> >
> > So my question is: How do I configure the dom0 Linux coming with
> > Xen-unstable so that it can recognize the emulated disk? Am I  
> > missing a
> > device driver for this QEMU HARDDISK?
> >
> > Thanks!
> > Jinpeng
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
>
>
> --
> Dave: Just a question. What use is a unicyle with no seat?  And no  
> pedals!
> Mark: To answer a question with a question: What use is a skateboard?
> Dave: Skateboards have wheels.
> Mark: My wheel has a wheel!
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

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