|
|
|
|
|
|
|
|
|
|
xen-users
RE: [Xen-users] Some xen 4.1. troubles.
Hello Hans.
Try pvops xen 2.6.32.xx or better xenified suse kernel from ftp.suse.com
, 2.6.37 from OpenSUSE-11.3 src. Im having very good experience with
this kernels.
BTW, use only stanard VESA driver in kernel, don`t use any other.
Rene
-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Hans de
Bruin
Sent: Monday, April 04, 2011 10:28 PM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Some xen 4.1. troubles.
Hi.
I have got xen 4.0.1 (x32) and Linux 2.6.32.24 (x32) running fine. So
time to upgrade to 4.1 (x64) and linux 2.6.38 (64). And now I am running
into some problems. After scrubbing the memory the screen looks weird. I
do not know whether this is a problem or not. A 'screen capture' is at:
http://www.xs4all.nl/~bruinjm/bootingXen.mpg4
An some more problematic xend will not start. After 'xend start' the
prompt does not return and after while this appears in dmesg:
INFO: task xend:1374 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
xend D ffff88001ff57ec0 0 1374 1372 0x00000000
ffff88001a319db8 0000000000000286 0000000000000293 ffff88001a286b50
0000000000012ec0 0000000000012ec0 0000000000012ec0 ffff88001a286b50
ffff88001a286dd0 ffff88001a319fd8 ffff88001a286dd8 ffff88001a318010
Call Trace:
[<ffffffff81078e50>] ? prepare_to_wait+0x60/0x90
[<ffffffff8131c8d5>] read_reply+0xa5/0x140
[<ffffffff81078ba0>] ? autoremove_wake_function+0x0/0x40
[<ffffffff81321825>] ? xenbus_file_write+0x485/0x560
[<ffffffff8131ca54>] xenbus_dev_request_and_reply+0xa4/0xc0
[<ffffffff81321629>] xenbus_file_write+0x289/0x560
[<ffffffff812568c3>] ? security_file_permission+0x23/0x90
[<ffffffff81112418>] vfs_write+0xc8/0x190
[<ffffffff811125d1>] sys_write+0x51/0x90
[<ffffffff8100a942>] system_call_fastpath+0x16/0x1b
INFO: task xend:1374 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
xend D ffff88001ff57ec0 0 1374 1372 0x00000000
ffff88001a319db8 0000000000000286 0000000000000293 ffff88001a286b50
0000000000012ec0 0000000000012ec0 0000000000012ec0 ffff88001a286b50
ffff88001a286dd0 ffff88001a319fd8 ffff88001a286dd8 ffff88001a318010
Call Trace:
[<ffffffff81078e50>] ? prepare_to_wait+0x60/0x90
[<ffffffff8131c8d5>] read_reply+0xa5/0x140
[<ffffffff81078ba0>] ? autoremove_wake_function+0x0/0x40
[<ffffffff81321825>] ? xenbus_file_write+0x485/0x560
[<ffffffff8131ca54>] xenbus_dev_request_and_reply+0xa4/0xc0
[<ffffffff81321629>] xenbus_file_write+0x289/0x560
[<ffffffff812568c3>] ? security_file_permission+0x23/0x90
[<ffffffff81112418>] vfs_write+0xc8/0x190
[<ffffffff811125d1>] sys_write+0x51/0x90
[<ffffffff8100a942>] system_call_fastpath+0x16/0x1b
INFO: task xend:1374 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
xend D ffff88001ff57ec0 0 1374 1372 0x00000000
ffff88001a319db8 0000000000000286 0000000000000293 ffff88001a286b50
0000000000012ec0 0000000000012ec0 0000000000012ec0 ffff88001a286b50
ffff88001a286dd0 ffff88001a319fd8 ffff88001a286dd8 ffff88001a318010
Call Trace:
[<ffffffff81078e50>] ? prepare_to_wait+0x60/0x90
[<ffffffff8131c8d5>] read_reply+0xa5/0x140
[<ffffffff81078ba0>] ? autoremove_wake_function+0x0/0x40
[<ffffffff81321825>] ? xenbus_file_write+0x485/0x560
[<ffffffff8131ca54>] xenbus_dev_request_and_reply+0xa4/0xc0
[<ffffffff81321629>] xenbus_file_write+0x289/0x560
[<ffffffff812568c3>] ? security_file_permission+0x23/0x90
[<ffffffff81112418>] vfs_write+0xc8/0x190
[<ffffffff811125d1>] sys_write+0x51/0x90
[<ffffffff8100a942>] system_call_fastpath+0x16/0x1b root@luna:~#
I 'am using a kernel from the linus tree.
--
Hans
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|