WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] making new initrd, how to do it?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] making new initrd, how to do it?
From: Steven Timm <timm@xxxxxxxx>
Date: Thu, 28 Jun 2007 09:22:56 -0500 (CDT)
Delivery-date: Thu, 28 Jun 2007 07:23:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <Pine.LNX.4.64.0706271617450.7210@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <Pine.LNX.4.64.0706271617450.7210@xxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
The error described below was due to the
fact that I had not
done

depmod -F/boot/System.map-2.6.18-xen 2.6.18-xen

Without the module dependencies correctly known in
the kernel that came from the xensource tarball, the mkinitrd
process was not aware of the dependencies and didn't put the
right modules into the initrd.

Once I did that, dom0 now boots fine under xen 3.1.

I believe this is the solution to the other initrd question that was
asked on this list last night as well.



Steve Timm


On Wed, 27 Jun 2007, Steven Timm wrote:


I have installed the xen 3.1.0 x86_64 tarball
compiled for RHEL5 on a RHEL5 system. The system in question
was able to boot with the xen kernel that came with RHEL5.

I untarred the tarball, and did

cd /boot
mkinitrd /boot/initrd-2.6.18-xen.img 2.6.18-xen

The command exited properly and made a initrd image.
The machine booted with a grub.conf entry like this:

title Xen 3.1.0
       root (hd0,0)
       kernel /boot/xen.gz com1=115200,8n1
module /boot/vmlinuz-2.6-xen ro root=LABEL=/ console=tty0 console=ttyS0,115200
       module /boot/initrd-2.6.18-xen.img

It loaded the initrd in question, but it couldn't detect the root device.
<Jun/27 03:57 pm>uhci_hcd: no version for "struct_module" found: kernel tainted.

<Jun/27 03:57 pm>uhci_hcd: Unknown symbol usb_hcd_pci_suspend
<Jun/27 03:57 pm>uhci_hcd: Unknown symbol usb_hcd_resume_root_hub
<Jun/27 03:57 pm>uhci_hcd: Unknown symbol usb_hcd_pci_probe
<Jun/27 03:57 pm>uhci_hcd: Unknown symbol usb_check_bandwidth
<Jun/27 03:57 pm>uhci_hcd: Unknown symbol usb_disabled
<Jun/27 03:57 pm>uhci_hcd: Unknown symbol usb_release_bandwidth
<Jun/27 03:57 pm>uhci_hcd: Unknown symbol usb_claim_bandwidth
<Jun/27 03:57 pm>uhci_hcd: Unknown symbol usb_hcd_pci_resume
<Jun/27 03:57 pm>uhci_hcd: Unknown symbol usb_hcd_giveback_urb
<Jun/27 03:57 pm>uhci_hcd: Unknown symbol usb_hcd_poll_rh_status
<Jun/27 03:57 pm>uhci_hcd: Unknown symbol usb_hcd_pci_remove
<Jun/27 03:57 pm>uhci_hcd: Unknown symbol usb_root_hub_lost_power
<Jun/27 03:57 pm>insmod: error inserting '/lib/uhci-hcd.ko': -1 Unknown symbol i
n module
<Jun/27 03:57 pm>Loading ohci-hcd.ko module
<Jun/27 03:57 pm>ohci_hcd: Unknown symbol usb_hcd_pci_suspend
<Jun/27 03:57 pm>ohci_hcd: Unknown symbol usb_hcd_resume_root_hub
<Jun/27 03:57 pm>ohci_hcd: Unknown symbol usb_hcd_pci_probe
<Jun/27 03:57 pm>ohci_hcd: Unknown symbol usb_disabled
<Jun/27 03:57 pm>ohci_hcd: Unknown symbol usb_calc_bus_time
<Jun/27 03:57 pm>ohci_hcd: Unknown symbol usb_hcd_pci_resume
<Jun/27 03:57 pm>ohci_hcd: Unknown symbol usb_hcd_giveback_urb
<Jun/27 03:57 pm>ohci_hcd: Unknown symbol usb_hcd_suspend_root_hub
<Jun/27 03:57 pm>ohci_hcd: Unknown symbol usb_hcd_pci_remove
<Jun/27 03:57 pm>ohci_hcd: Unknown symbol usb_root_hub_lost_power
<Jun/27 03:57 pm>insmod: error inserting '/lib/ohci-hcd.ko': -1 Unknown symbol i
n module
<Jun/27 03:57 pm>Loading ehci-hcd.ko module
<Jun/27 03:57 pm>ehci_hcd: Unknown symbol usb_hcd_pci_suspend
<Jun/27 03:57 pm>ehci_hcd: Unknown symbol usb_free_urb
<Jun/27 03:57 pm>ehci_hcd: Unknown symbol usb_hub_tt_clear_buffer
<Jun/27 03:57 pm>ehci_hcd: Unknown symbol usb_hcd_resume_root_hub
<Jun/27 03:57 pm>ehci_hcd: Unknown symbol usb_hcd_pci_probe
<Jun/27 03:57 pm>ehci_hcd: Unknown symbol usb_calc_bus_time
<Jun/27 03:57 pm>ehci_hcd: Unknown symbol usb_hcd_pci_resume
<Jun/27 03:57 pm>ehci_hcd: Unknown symbol usb_get_urb
<Jun/27 03:57 pm>ehci_hcd: Unknown symbol usb_hcd_giveback_urb
<Jun/27 03:57 pm>ehci_hcd: Unknown symbol usb_hcd_pci_remove
<Jun/27 03:57 pm>ehci_hcd: Unknown symbol usb_root_hub_lost_power
<Jun/27 03:57 pm>insmod: error inserting '/lib/ehci-hcd.ko': -1 Unknown symbol i
n module
<Jun/27 03:57 pm>mount: could not find filesystem '/proc/bus/usb'
<Jun/27 03:57 pm>Loading ext3.ko module
<Jun/27 03:57 pm>ext3: Unknown symbol journal_force_commit
<Jun/27 03:57 pm>ext3: Unknown symbol journal_dirty_data
<Jun/27 03:57 pm>ext3: Unknown symbol journal_force_commit_nested
<Jun/27 03:57 pm>ext3: Unknown symbol journal_init_dev
<Jun/27 03:57 pm>ext3: Unknown symbol journal_dirty_metadata
<Jun/27 03:57 pm>ext3: Unknown symbol journal_forget
<Jun/27 03:57 pm>ext3: Unknown symbol journal_wipe
<Jun/27 03:57 pm>ext3: Unknown symbol journal_blocks_per_page
<Jun/27 03:57 pm>ext3: Unknown symbol journal_blocks_per_page
<Jun/27 03:57 pm>ext3: Unknown symbol journal_errno
<Jun/27 03:57 pm>ext3: Unknown symbol journal_extend
<Jun/27 03:57 pm>ext3: Unknown symbol journal_invalidatepage
<Jun/27 03:57 pm>ext3: Unknown symbol journal_create
<Jun/27 03:57 pm>ext3: Unknown symbol journal_unlock_updates
<Jun/27 03:57 pm>ext3: Unknown symbol journal_revoke
<Jun/27 03:57 pm>ext3: Unknown symbol journal_lock_updates
<Jun/27 03:57 pm>ext3: Unknown symbol journal_start_commit
<Jun/27 03:57 pm>ext3: Unknown symbol journal_flush
<Jun/27 03:57 pm>ext3: Unknown symbol journal_load
<Jun/27 03:57 pm>ext3: Unknown symbol journal_try_to_free_buffers
<Jun/27 03:57 pm>ext3: Unknown symbol journal_update_format
<Jun/27 03:57 pm>ext3: Unknown symbol journal_get_write_access
<Jun/27 03:57 pm>ext3: Unknown symbol journal_get_undo_access
<Jun/27 03:57 pm>ext3: Unknown symbol journal_get_create_access
<Jun/27 03:57 pm>ext3: Unknown symbol journal_destroy
<Jun/27 03:57 pm>ext3: Unknown symbol journal_clear_err
<Jun/27 03:57 pm>ext3: Unknown symbol journal_stop
<Jun/27 03:57 pm>ext3: Unknown symbol journal_init_inode
<Jun/27 03:57 pm>ext3: Unknown symbol journal_start
<Jun/27 03:57 pm>ext3: Unknown symbol log_wait_commit
<Jun/27 03:57 pm>ext3: Unknown symbol journal_release_buffer
<Jun/27 03:57 pm>ext3: Unknown symbol journal_check_available_features
<Jun/27 03:57 pm>ext3: Unknown symbol journal_abort
<Jun/27 03:57 pm>ext3: Unknown symbol journal_restart
<Jun/27 03:57 pm>insmod: error inserting '/lib/ext3.ko': -1 Unknown symbol in mo
dule
<Jun/27 03:57 pm>Loading megaraid_sas.ko module
<Jun/27 03:57 pm>megaraid_sas: Unknown symbol scsi_remove_host
<Jun/27 03:57 pm>megaraid_sas: Unknown symbol scsi_host_put
<Jun/27 03:57 pm>megaraid_sas: Unknown symbol scsi_scan_host
<Jun/27 03:57 pm>megaraid_sas: Unknown symbol scsi_add_host
<Jun/27 03:57 pm>megaraid_sas: Unknown symbol scsi_host_alloc
<Jun/27 03:57 pm>insmod: error inserting '/lib/megaraid_sas.ko': -1 Unknown symb
ol in module
<Jun/27 03:57 pm>Loading usb-storage.ko module

<Jun/27 03:57 pm>Creating root device.
<Jun/27 03:57 pm>Mounting root filesystem.
<Jun/27 03:57 pm>mount: could not find filesystem '/dev/root'
<Jun/27 03:57 pm>Setting up other filesystems.
<Jun/27 03:57 pm>Setting up new root fs
<Jun/27 03:57 pm>setuproot: moving /dev failed: No such file or directory
<Jun/27 03:57 pm>no fstab.sys, mounting internal defaults
<Jun/27 03:57 pm>setuproot: error mounting /proc: No such file or directory
<Jun/27 03:57 pm>setuproot: error mounting /sys: No such file or directory
<Jun/27 03:57 pm>Switching to new root and running init.
<Jun/27 03:57 pm>unmounting old /dev


It used to be that you could pull an initrd image apart and see what
it was missing.  Has that trick changed with RHEL5 so that you
can't do that now?  I can see the initrd that I made with mkinitrd
is significantly smaller than the one that was made with the rhel
install.

Steve Timm



--
------------------------------------------------------------------
Steven C. Timm, Ph.D  (630) 840-8525
timm@xxxxxxxx  http://home.fnal.gov/~timm/
Fermilab Computing Division, Scientific Computing Facilities,
Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader.

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

<Prev in Thread] Current Thread [Next in Thread>