Thanks very much for the tip. That did give me some additional information:
Scanning and configuring dmraid supported devices
Scanning logical volumes
Reading all physical volumes. This may take a while...
Activating logical volumes
Volume group "virt01vg00" not found
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!
Scanning logical volumes
Reading all physical volumes. This may take a while...
Activating logical volumes
Volume group "virt01vg00" not found
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!
This brings me back to suspecting the problem is in the different file structures. I'm still trying to wrap my head around the other replies in this thread.
On Sat, Nov 7, 2009 at 2:24 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
On Fri, Nov 06, 2009 at 11:49:41AM -0800, Christopher Hunt wrote:> [1]http://lists.xensource.com/archives/html/xen-users/2008-03/msg00603.html,
> First let me say that I'm not a sysadmin, but am simply wearing that hat
> this week so please excuse my ignorance. I need to temporarily move some
> virtual servers from a CentOS-KVM platform to a CentOS-XEN platform while
> I do some upgrades to the CentOS box. I've created a local LV, and used
> DD and SCP to transfer the block device from the VKM machine to the XEN
> machine. For quite a while I struggled with the "Error: (2, 'Invalid
> kernel', 'xc_dom_parse_elf_kernel: ELF image has no shstrtab\n')" error
> but thanks to Nick Couchman from
> I've passed that. Now I'm stuck with a kernel panic situation.Stop the guest and edit /etc/xen/<guest> cfgfile.
> Unfortunately the kernel panic error doesn't appear using "xm console" and
> flashes so quickly through "virt-viewer" that I can't get any details.
>
Remove (or comment out) the vfb line, and then restart the guest.
Now you get the full console output to "xm console".
-- Pasi
_______________________________________________
CentOS-virt mailing list
CentOS-virt@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos-virt
_______________________________________________ CentOS-virt mailing list CentOS-virt@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos-virt
