[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

OK something wrong here.

Free image from Stacklet.com - please download here:

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?

So my question - what am doing wrong?

Thanks for looking

2016-02-01 10:58 GMT+01:00 Ian Campbell <ian.campbell@xxxxxxxxxx>:
On Fri, 2016-01-29 at 23:48 +0100, Peter Braun wrote:
> Hi all,
> we have couple of really old Xen hosts running Xen 3.4 (gitco repo) with
> CentOS 5 dom0.
> Guests are PV and mostly old OSes like Debian 6 and CentOS 5.
> We are planning of migrating the guest to brand new hardware with Debian
> 8 or Ubuntu 14 server.
> Unfortunatelly we are unable to run any of those old guest in the new
> envrionment.

Are you able to run any new guests, or any guests at all? i.e. is it just
the old imported guests which are the problem?

> Debian 8 + Xen 4.4.1 + lvm based guest Debian 6 with 2.6.32 kernel
> ---------
> xenconsole: Could not open tty `': No such file or directory

This seems to suggest an issue with the xenconsole daemon (which should
have written the tty to xenstore for the client to use).

Is xenconsoled running?

>                                                             libxl: error:
> libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited
> with error status 2
>       libxl: error: libxl_dom.c:35:libxl__domain_type: unable to get
> domain type for domid=6
>             Unable to attach console
>                                     libxl: error:
> libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited
> with error status 1
> ------
> #bootloader = "/usr/bin/pygrub"
> bootloader = "pygrub"
> #extra = "console=hvc0"
> #vcpus = 1
> memory = 512
> name = "sec"
> #vif = [ 'vifname=sec' ]
> disk = [ 'phy:/dev/vg/sechd,sda1,w','phy:/dev/vg/secswp,sda2,w' ]
> root = "/dev/sda1 ro"
> ----
> Generally is it supported to run such old pv guests on Xen 4.4?

In general yes, and Debian 6 (squeeze) with a 2.6.32 is not so very old
that I would expect problems.

In fact we test Squeeze as a domU on a weekly basis (against Xen unstable)
and in general it is fine, e.g.

Is the 2.6.32 kernel in these guests up to date with the latest in Squeeze
(3.2.68-1+deb7u3 or 3.2.73-2+deb7u2 from the security repo for example)?

It would be useful to see the logs (see [0] for examples of where to look
and what to include) as well as the full output of:
    xl -vvv create <cfgfile>


[0] http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen

Xen-users mailing list



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