|
I have copied xen
modules into guest kernel directory (am running suse 10.1 guest), so I conclude
that is why ramdisk parameter is vital. Am running IDE drive, not
SCSI.
Bernard Golden
Chief Executive Officer, Navica
www.navicasoft.com
Author, "Succeeding
with Open Source," Addison-Wesley, 2005
(T) 650 585 5309 (C) 650 400 3204
(F) 650 591 3805
Sign up for
Navica's monthly open source newsletter
Read my open source blog for CIO
Magazine
Ramdisk is important if you have some critical kernel components built as
modules, as opposed to statically built into the kernel.
If you're exporting disk partitions from dom0 to domU's as SCSI drives,
you should have the necessary SCSI components turned on in the guest kernel
and have them available as modules or built into the kernel. If you have them
as modules, you should run depmod, do mkinitrd and have ramdisk settings in
your guest config file for it to recognize the root drive.
I think it's commented out (at least in mine) because it's assuming
you're exporting partitions as hda[012] (IDE drives). Are you exporting it as
SCSI?
S
On May 25, 2006, at 3:43 PM, Bernard Golden wrote:
I was having
problems bringing up a guest OS, getting a "root not found" error. The
config file, copied from the example file, had the ramdisk setting commented
out. I uncommented it and the guest OS came up just
fine.
Ramdisk is not
really described, so my question is "what function does it perform?" If it's
critical to getting guests up and running, why is it commented out in the
example, which would seem to imply it's not critical to bringing guest OS
systems up?
Bernard
Golden
_______________________________________________
Xen-users mailing list
|
