Interesting: XENBUS: Device with no driver: device/vbd/2048 XENBUS: Device with no driver: device/vif/0 Freeing unused kernel memory: 124k freed device-mapper: 4.5.5-ioctl ( 2006-12-01 ) initialised: [EMAIL PROTECTED] Kernel panic - not syncing: Attempted to kill init!
Not sure where to go from here. ----- Original Message ----- From: "Chris Lalancette" <[EMAIL PROTECTED]> To: "Jim Klein" <[EMAIL PROTECTED]> Cc: "fedora-xen" <[email protected]> Sent: Tuesday, October 30, 2007 1:23:08 PM (GMT-0800) America/Los_Angeles Subject: Re: [Fedora-xen] RHEL4 DomU Update Problem Jim Klein wrote: > Am attempting to update a RHEL4 domU from a custom created Xen kernel > (created before RHEL5) to a supported kernel (2.6.9-55.0.9.ELxenU) and > RHEL5 host without success. For some reason, the kernel can no longer > find xvda. Boots fine on the old kernel and host, so I'm at a bit of a > loss. Host has other domUs booted off the same SAN, with no security > restrictions, so I don't see how it could be hardware. Copy of configs > and partial debug log below. Ideas? Hm, everything below, at a first glance, seems to be right. What does the console output look like from the RHEL-4 kernel (make sure to take rhgb quiet off of the command-line)? Chris Lalancette
-- Fedora-xen mailing list [email protected] https://www.redhat.com/mailman/listinfo/fedora-xen
