Boris, I'd appreciate if you kept the discussion on this bug focused on this bug - if you see other issues with the Xen packaging, then you should open another bug. Upgrading to 3.3.1, for example, while an excellent idea, is not related to this bug, and I in particular would prefer to get my version of 3.3.0-1ubuntu10 uploaded before I look into upgrading to 3.3.1, which is a non-trivial change from the current version:
For 9.04, neither the Xen packages in jaunty or the ones in jaunty-proposed are using Python 2.6, so the switch to dist-packages isn't relevant. For Karmic, one of my changes is to patch the xen-python-patch script to look in dist-packages as well as site-packages.
Using my test builds of the Karmic packages in my PPA (https://launchpad.net/~broder/+archive/ppa), I've been able to successfully build a domU and boot it up completely, so I believe the issues with hotplug scripts may be specific to your configuration.
Boris, I'd appreciate if you kept the discussion on this bug focused on this bug - if you see other issues with the Xen packaging, then you should open another bug. Upgrading to 3.3.1, for example, while an excellent idea, is not related to this bug, and I in particular would prefer to get my version of 3.3.0-1ubuntu10 uploaded before I look into upgrading to 3.3.1, which is a non-trivial change from the current version:
fanty:~/Downloads evan$ diff -ur xen-3.3.0 xen-3.3.1 | diffstat | tail -n 1
185 files changed, 2874 insertions(+), 1467 deletions(-)
For 9.04, neither the Xen packages in jaunty or the ones in jaunty-proposed are using Python 2.6, so the switch to dist-packages isn't relevant. For Karmic, one of my changes is to patch the xen-python-patch script to look in dist-packages as well as site-packages.
Using my test builds of the Karmic packages in my PPA (https:/ /launchpad. net/~broder/ +archive/ ppa), I've been able to successfully build a domU and boot it up completely, so I believe the issues with hotplug scripts may be specific to your configuration.