All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Goirand <zigo@debian.org>
To: chris <tknchris@gmail.com>
Cc: Xen-Devel List <xen-devel@lists.xensource.com>,
	Xen-Users List <xen-users@lists.xensource.com>
Subject: Re: [Xen-devel] issue moving guest from 3.2 to 4.01
Date: Thu, 23 Dec 2010 13:37:27 +0800	[thread overview]
Message-ID: <4D12E017.1020504@debian.org> (raw)
In-Reply-To: <AANLkTikMndOod2rk+xLf=FaonjsDT376DxHM=_Smqojq@mail.gmail.com>

On 12/23/2010 02:59 AM, chris wrote:
> Hello,
>
> I have a pv linux guest which works perfectly on 3.2 and when I moved
> the guest to the new server (debian squeeze, xen 4.0.1) I cannot start
> it, I get the following error:
>
> # xm create vm-customer.cfg
> Using config file "./vm-customer.cfg".
> Error: (1, 'Internal error', 'launch_vm: SETVCPUCONTEXT failed (rc=-1)\n')
>
> here is my domain config:
>
> http://pastebin.com/FEw9k9dr
>
> I assumed that it was due to the domU kernel not being compatible with
> the hypervisor so i replaced them with the domU kernel from squeeze
> but I still get the same error.
> A quick google returns a post about someone starting 100 domains and
> this occuring on the 101st domain, however in this case this is the
> first vm im putting on this machine so I don't think it is related.
>
> Has anyone had this issue? Any idea how I can debug this? I tried
> setting vcpus=1 and cpus=1 just to see if it wanted those directives
> but it doesnt seem to make any difference
>   
Your VM is using sda1. Switch to the new device name system: xvda1.
Then you might have a chance to have it working... :)

Thomas

  reply	other threads:[~2010-12-23  5:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-22 18:59 issue moving guest from 3.2 to 4.01 chris
2010-12-23  5:37 ` Thomas Goirand [this message]
2010-12-23  5:52   ` [Xen-devel] " chris

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D12E017.1020504@debian.org \
    --to=zigo@debian.org \
    --cc=tknchris@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.