On 06/19/2014 08:23 AM, Paul Raines wrote: [please don't top-post on technical lists] > > virt-v2v is not an option for me as all I have are the VMDK images and > don't have the VMware software to covert to OVA first. Still, asking the virt-v2v developers (on the libguestfs mailing list, rather than here), may get you more insight into your issues than what we can provide here. > > I really don't understand what is going wrong. I also found > https://access.redhat.com/site/solutions/20511 and that still doesn't > work. Both /etc/fstab and grub.conf refer to the LABEL and not any > device name. > > In the boot process I see it explicitly says it is loading virtio_blk > before > the panic. So it is like that driver just doesn't see the disk. The > host machine is a CentOS 6 box. Is it possible the virtio in the libvirt > for CentOS/RHEL6 is not compatiable with the virtio_blk driver in > CentOS/RHEL5? Either that, or something else getting loaded is causing > interference? Alas, I have no clue on what to suggest as your next debugging step. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users
