|
|
|
|
|
|
|
|
|
|
xen-users
Re: [Xen-users] issue moving guest from 3.2 to 4.01
# grep '^(' /etc/xen/xend-config.sxp
(vif-script vif-bridge)
(dom0-min-mem 196)
(enable-dom0-ballooning yes)
(total_available_memory 0)
(dom0-cpus 0)
(vnc-listen '0.0.0.0')
# xm info
host : mango
release : 2.6.32-5-xen-amd64
version : #1 SMP Fri Dec 10 17:41:50 UTC 2010
machine : x86_64
nr_cpus : 8
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 2
cpu_mhz : 2800
hw_caps :
bfebfbff:28100800:00000000:00001b40:0098e3fd:00000000:00000001:00000000
virt_caps : hvm
total_memory : 4087
free_memory : 256
node_to_cpu : node0:0-7
node_to_memory : node0:256
node_to_dma32_mem : node0:173
max_node_id : 0
xen_major : 4
xen_minor : 0
xen_extra : .1
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : unavailable
xen_commandline : placeholder
cc_compiler : gcc version 4.4.5 20100824 (prerelease)
(Debian 4.4.4-11)
cc_compile_by : waldi
cc_compile_domain : debian.org
cc_compile_date : Fri Sep 3 15:38:12 UTC 2010
xend_config_format : 4
>From the guest filesystem loop mounted at /mnt/tmp:
/mnt/tmp/lib/modules# ls
2.6.26-2-xen-amd64
I could try copying the modules for the newer domU kernel but would
that really cause an error that early on? I mean the kernel isn't even
starting so I don't think the modules are whats causing this.
On Wed, Dec 22, 2010 at 3:30 PM, Mark Pryor <tlviewer@xxxxxxxxx> wrote:
>
>
> --- On Wed, 12/22/10, chris <tknchris@xxxxxxxxx> wrote:
>
>> From: chris <tknchris@xxxxxxxxx>
>> Subject: [Xen-users] issue moving guest from 3.2 to 4.01
>> To: "Xen-Users List" <xen-users@xxxxxxxxxxxxxxxxxxx>, "Xen-Devel List"
>> <xen-devel@xxxxxxxxxxxxxxxxxxx>
>> Date: Wednesday, December 22, 2010, 10:59 AM
>> 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')
>>
>
> this looks to be a problem with dom0 config, not domU.
>
> It's easier to help if you post:
>
> #grep '^(' /etc/xen/xend-config.sxp ; (dom0-cpus 0) is a safe value
>
> #xm info
>
> in domU
> #ls -al /lib/modules/ ; chances are the modules are not compatible with
> dom0 kernel
>
> --
> Mark
>
>
>
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|