| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] Attempt to build xen-unstable on Ubuntu 9.04 Server (Ubu
Notice, that direct port Xen 3.4 ( with 2.6.30-rc3-tip) to F11 (preview) has been tested with no problems. Just no xen-lib and xen-lib dependent packages: libvirt,libvirt-python,.. is a must .
Problem been described seems to me as python 2.6 implementation issue on Ubuntu 9.04 Server.
Boris.
--- On Fri, 5/8/09, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Subject: Re: [Xen-devel] Attempt to build xen-unstable on Ubuntu 9.04 Server (Ubuntu Desktop installed)
To: "Alex Zeffertt" <alex.zeffertt@xxxxxxxxxxxxx>
Cc: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Ian Jackson"
<Ian.Jackson@xxxxxxxxxxxxx>
Date: Friday, May 8, 2009, 11:45 AM
Follow your suggestion i was able to build Xen Host on Ubuntu 9.04 Server
with the most recent Xen-3.4-rc4-pre and 2.6.30-rc3-tip pvops kernel via
Jeremy's git repo.
Due to newly built Xen Host dual boot with similar one on top of Ubuntu 8.10 Server i just copied F10 PV profile to new Xen Host and attempted to run
F10 PV :-
# xm create -c
f10.pyrun
Name ID Mem VCPUs State
Time(s)
Domain-0 0 6034 4 r----- 138.5
F10PV 5 2048 1 --p--- 0.0
root@ServerJaunty:/home/boris/vm# xm unpause F10PV
/usr/lib/python2.6/site-packages/xen/util/acmpolicy.py:20: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
import sha
# xm unpause F10PV
PCI: Fatal: No config space access
function found
IO APIC resources could be not be allocated.
Loading /lib/kbd/keymaps/i386/qwerty/us.map
root@ServerJaunty:/home/boris/vm# Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
Then i've tried to comment out vif in profile:
PCI: Fatal: No config space access function found
IO APIC resources could be not be allocated.
Loading /lib/kbd/keymaps/i386/qwerty/us.map
BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
IP: [<ffffffffa00010e5>] backend_changed+0x2d5/0x3af [xen_blkfront]
PGD 7d1a0067 PUD 7d1a1067 PMD 7d1b0067 PTE 0
Oops: 0000 [1] SMP
CPU 1
Modules linked in: xen_blkfront
Pid: 19, comm: xenwatch Not tainted 2.6.27.19-170.2.35.fc10.x86_64 #1
RIP: e030:[<ffffffffa00010e5>] [<ffffffffa00010e5>] backend_changed+0x2d5/0x3af [xen_blkfront]
RSP: e02b:ffff88007f40fdf0 EFLAGS: 00010246
RAX:
0000000000000000 RBX: ffff88007d09b2c0 RCX: 0000000000000000
RDX: ffff88007f40fe28 RSI: 0000000000000005 RDI: ffff88007ff5f400
RBP: ffff88007f40fe80 R08: ffff88007f40fdd0 R09: ffff88007f40fcc0
R10: 0000000000000001 R11: ffff880000000018 R12: ffff88007ff5f400
R13: ffff88007d0be000 R14: 000000000000000a R15: ffffffff817e6eb4
FS: 00007f80e570a6f0(0000) GS:ffff88007fc04880(0000) knlGS:0000000000000000
CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000000 CR3: 000000007d1a4000 CR4: 0000000000002660
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process xenwatch (pid: 19, threadinfo ffff88007f40e000, task ffff88007ffd5c40)
Stack: ffff88007f40fe00 ffff88007f40fe40 ffffffff816e2500 ffffffff816e2500
ffffffff81458716 ffffffff8146545f ffff88007f40fe7c 0000000000000000
000000000000000a
ffff88007d09b2c0 ffff88007ff5f400 ffffffffa0002ac0
Call Trace:
[<ffffffff811ca80a>] otherend_changed+0x81/0x8a
[<ffffffff811c9438>] xenwatch_thread+0x101/0x134
[<ffffffff8105553d>] ? autoremove_wake_function+0x0/0x38
[<ffffffff811c9337>] ? xenwatch_thread+0x0/0x134
[<ffffffff810551f7>] kthread+0x49/0x76
[<ffffffff81011719>] child_rip+0xa/0x11
[<ffffffff81010a37>] ? restore_args+0x0/0x30
[<ffffffff8101170f>] ? child_rip+0x0/0x11
Code: 58 08 e9 97 00 00 00 49 8b 7d 00 48 c7 c2 b9 15 00 a0 be ed ff ff ff 48 8b 4f 10 31 c0 e8 fe 75 1c e1 e9 cf 00 00 00 49 8b 45 08 <8b> 38 c1 e7 14 0b 78 04 e8 5a 5c 0e e1 48 85 c0 48 89 c3 75 16
RIP [<ffffffffa00010e5>] backend_changed+0x2d5/0x3af [xen_blkfront]
RSP <ffff88007f40fdf0>
CR2: 0000000000000000
---[ end trace 06219b74fe5c0c01
]---
root@ServerJaunty:/home/boris/vm# Error: Device 51712 (vbd) could not be connected. Hotplug scripts not work
The image been used (on /dev/sdc) works fine with the same F10 PV @ Xen
Host ( absolutly identical new one) , but been built on top of Ubuntu 8.10 Server ( all servers 64-bit).
Boris.
--- On Wed, 5/6/09, Alex Zeffertt <alex.zeffertt@xxxxxxxxxxxxx> wrote:
From: Alex Zeffertt <alex.zeffertt@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Attempt to build xen-unstable on Ubuntu 9.04 Server (Ubuntu Desktop installed)
To: "bderzhavets@xxxxxxxxx" <bderzhavets@xxxxxxxxx>
Cc: "Ian Jackson" <Ian.Jackson@xxxxxxxxxxxxx>, "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Wednesday, May 6, 2009, 12:37 PM
Hi,
It looks like the problem is that if you have
python2.6
installed then
xen-unstable.hg installs into /usr/lib/python2.6/site-packages/xen, but
site-packages is no longer in the default path in python2.6.
A hack which fixes this is to add the following two lines to
/etc/python2.6/sitecustomize.py:
import sys
sys.path.append('/usr/lib/python2.6/site-packages')
but I'm not sure what the proper fix would be...
Regards,
Alex
PS This is also relevant
https://bugs.launchpad.net/ubuntu/+source/python2.6/+bug/362570
|
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home