[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Migrating legacy guests from Xen 3.4 to 4.4

On Mon, Mar 7, 2016 at 4:29 PM, Peter Braun <xenware@xxxxxxxxx> wrote:
> OK something wrong here.
> Free image from Stacklet.com - please download here:
> http://www.stacklet.com/downloads/images/xen/debian/6.0/x86-64
> 1) Centos 5.5 + Xen 3.4.3 - kernel 2.6.18
> - I can startup VM from this file image
> - mount without any problem
>   mount -o loop debian.6-0.x86.20130508.img /mnt/img/
> 2) Centos 7-1511 + Xen 4.6.1 - kernel 3.18.25-18.el7.x86_64
> - Unable to startup VM from this file image
> the xen error message is saying that is unable to find aby partition
> containing boot.
> - Unable to even mount this image
>   mount -o loop debian.6-0.x86.20130508.img /mnt/img/
> mount: /dev/loop1 is write-protected, mounting read-only
> NTFS signature is missing.
> Failed to mount '/dev/loop1': Invalid argument
> The device '/dev/loop1' doesn't seem to have a valid NTFS.
> Maybe the wrong device is used? Or the whole disk instead of a
> partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

Well looking at your config file, the .img files should be plain
filesystems (i.e., the files don't contain a partition).

Well it looks like the kernel thinks there's an NTFS filesystem in
this image, which I suppose is possible but seems rather unlikely.

I guess the first thing to do is check to make sure the files are
actually the same -- "ls -l" to check the size, then cksum / md5sum /

Then try adding "-t <actual fs type>" to let the kernel a hint what
filesystem it might be.

Also worth checking to make sure that whatever the filesystem is, you
actually have a module in the new kernel for it.


Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.