On Sunday June 22 2008 11:58:54 am Thomas wrote:
> I also noticed that when installing using debootstrap, I do not have a
> /etc/lilo.conf in my DomU. Could that be part of the problem?
Since you are using kernel/ramdisk= in your config, ultimately no. I don't
know if Debian etch prefers lilo over grub, but if it's like
grub, /etc/lilo.conf would just be a link to something in /boot.
On Sunday June 22 2008 01:06:27 pm Thomas wrote:
> Here is my config file:
> ----
> -*- mode: python; -*-
> kernel="/boot/domU_32/vmlinuz-2.6.18-6-xen-686"
> initrd="/boot/domU_32/initrd.img-2.6.18-6-xen-686"
> memory = "256"
> name = "VM1-2.6.18"
> vif = [ 'mac=00:16:3e:00:00:01, ip=10.0.0.1' ]
> netmask = "255.255.255.0"
> gateway = "10.0.0.128"
> disk = [ 'phy:/dev/mapper/xenvg-VM1,/dev/hda1,w',
> 'phy:/dev/mapper/xenvg-VM1--swap,/dev/hda2,w' ]
>
> root = "/dev/hda1"
>
> extra='console=hvc0 xencons=hvc0'
See next comment.
> Here is what gets printed out when using the "xm create -c
> VM1-2.6.18-6" command:
>
> -------
> Linux version 2.6.18-6-xen-686 (Debian 2.6.18.dfsg.1-18etch1)
[...]
> RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
> Xen virtual console successfully installed as tty1
hvc0 is a pvops kernel thing (2.6.24 and up). 2.6.18 used xvc0 and tty1
interchangeably, so you really don't need the extra= line. (Not that that has
anything to do with root not mounting.)
> Also I'd like to know what should be the folder name for modules
> inside /lib/modules of my domU?
As in the 'Linux version' line above: /lib/modules/2.6.18-6-xen-686 . You
should copy it over from a 2.6.18-6 Debian xen distro. Once your ramdisk is
done setting up your initial device drivers necessary for finding and
mounting your root device, it's space is released, and all further modprobes
are done from /lib/modules, so you will need it anyway, whether you use
kernel/ramdisk= or bootloader=.
Of course, you haven't even gotten that far if it can't find the root device
to mount. That's why cleaning out /lib/modules and /etc/fstab doesn't
matter - *yet*. I'm not familiar w/debootstrap, and whether it creates a
straight ext3 partition or whether it uses lvm, but your dom0 initrd from
your ramdisk= line has to have all the proper modules to find your domu root
device, and is your current problem. I can't help you with what should be in
there for your domu, but I can help with telling you what is in there now.
Naturally, if your dom0 initrd is actually used to boot your dom0, you are
going to want a new name for your initrd before you change it for your domu.
(It looks like you put it in a separate subdir 'domu_32'.)
Do a 'file /boot/domU_32/initrd.img-2.6.18-6-xen-686'. It will most likely
return and tell you it is a gzip-ed file. The contents of the ungzip-ed is
either a tar or cpio archive. I'm assuming cpio. To see the contents, do:
gunzip -c /boot/domU_32/initrd.img-2.6.18-6-xen-686 | cpio -t
You can use 'cpio -tv' to get an 'ls -l' style listing. Some distros have
the 'lsinitrd' command to make this easier. (Relatively new, I think. F9 has
it.)
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home