Comment 33 for bug 362691

Revision history for this message
Boris Derzhavets (bderzhavets) wrote :

Honestly, i don't see much sense in forward porting Xen 3.3 , because it doesn't support ( http://wiki.xensource.com/xenwiki/XenParavirtOps) :-

1. The ability for the Xen hypervisor to load and boot bzImage pv_ops dom0 kernel
2. The ability for the Xen tools to use the sysfs memory ballooning support provided by pv_ops dom0 kernel

Coming soon F11 (and even F10 in meantime) has Xen 3.3.1 with mentioned feature back ported from Xen Unstable (3.4). View for instance:-

http://lxer.com/module/newswire/view/120005/index.html.

My major concern in details follows bellow has been posted on xen-devel mailing list :-

Re: [Xen-devel] Changeset 19594 for Xen 3.4 build on Ubuntu Server 9.04

From:"Boris Derzhavets" <email address hidden> Friday, May 15, 2009 12:38 PM Add sender to Contacts
To:"Ian Jackson" < ... @eu.citrix.com>
Cc:"<email address hidden>" <email address hidden>, "Keir Fraser" < .... @eu.citrix.com>

Per /usr/lib/python2.6/site.py:-

For Debian and derivatives, this sys.path is augmented with directories
for packages distributed within the distribution. Local addons go
into /usr/local/lib/python<version>/dist-packages, Debian addons
install into /usr/{lib,share}/python<version>/dist-packages.
/usr/lib/python<version>/site-packages is not used.

It is different from /usr/lib/python2.5/site.py

With Config.mk:-

PYTHON = python
PYTHON_PREFIX_ARG =

Packages gets installed into /usr/local/lib/python2.6/dist-packages:-

root@ServerJaunty:/usr/local/lib/python2.6/dist-packages# ls -ld xen
drwxr-sr-x 9 root staff 4096 2009-05-15 10:35 xen

Xend starts fine, pygrub doesn't fail. Xen host seems to be OK.
But, "xm create -c DomU.cfg" doesn't work any more,even with xenified kernel. DomU gets paused at startup and no matter of been unpaused or no, finally crashes with message:-

"Hotplug scripts not working"

I believe Xen 3.4 has problem been installed on Ubuntu 9.04 Server (64-bit)
with python 2.6 installed with default settings. Same situation will happen on any Debian derivative with Python 2.6.
If i am wrong about that, please advise.

Boris.