xen-users
RE: [spam] Re: [Xen-users] Xen on Jaunty
I would suggest get rid from 3.4 :-
# apt-get install mercurial gitk # hg clone http://xenbits.xensource.com/xen-3.4-testing.hg # cd xen-3.4-testing.hg
Fix Config.mk and build Xen 3.4.1-rc7 right away
# make xen # make tools # make stubdom
Install
# make install-xen # make install-tools # make install-stubdom
Actually, patching 3.4 might be not safe per my opinion. Issue with udev version > 124 has to be fixed anyway, otherwise hotplug script would reject to work I am sending you this message from environment you intend to build.
Boris.
--- On Thu, 7/16/09, Ruiz, Jason T <jason.t.ruiz@xxxxxxxxxxx> wrote:
From: Ruiz, Jason T
<jason.t.ruiz@xxxxxxxxxxx> Subject: RE: [spam] Re: [Xen-users] Xen on Jaunty To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx Date: Thursday, July 16, 2009, 11:07 AM
It's 3.4.0 from their site. I've fixed the python
issue, I think, but I'm not sure about udev now. I did apply the patch found in the link Boris provided. What sucks
is this machine is at home, and I am of course at work, so any issues when
modifying grub, I gotta wait til I get
home.
Sincerely,
Jason T.
Ruiz
In other words, to build Xen 3.4.1 you have to
understand what Changeset 19594 does. To build Xen 3.4.0 you also have to
back port CS 19668 to be able detect properly udev 141. I am not
sure what version of Xen you've tried to build on
Jaunty.
Boris.
--- On Thu, 7/16/09, Boris Derzhavets
<bderzhavets@xxxxxxxxx> wrote:
From:
Boris Derzhavets <bderzhavets@xxxxxxxxx> Subject: Re:
[Xen-users] Xen on Jaunty To: xen-users@xxxxxxxxxxxxxxxxxxx, "Jason
TRuiz" <jason.t.ruiz@xxxxxxxxxxx> Date: Thursday, July 16,
2009, 10:09 AM
>Traceback (most recent call
last): > File "/usr/sbin/xm", line 8, in
<module> > from xen.xm import main >ImportError:
No module named xen.xm
Set in
Config.mk PYTHON = python PYTHON_PREFIX_ARG
=
Tuning Config.mk results Xen packages to be placed
into /usr/local/lib/python2.6/dist-packages due to Changeset 19594
in xen-3.4-testing.hg. Otherwise, Xen packages would go to
/usr/lib/python2.6/site-packages, which is not default location
for python 2.6 on Ubuntu 9.04 ( vs F11 ). Thus you won’t be able
to start xend in Dom0. Same thing happens when building Xen
Unstable on Ubuntu 9.04 Server.
If you need more details
for pvops kernel
:-
http://bderzhavets.wordpress.com/2009/06/25/setup-xen-3-4-1-dom0-on-top-of-ubuntu-9-04-server-via-marc-a-dahlhauss-udev-patch/
If
you need more details for xenified kernel
:-
http://bderzhavets.wordpress.com/2009/07/07/building-xenified-2-6-30-1-kernel-via-xen-patches-2-6-30-2-tar-bz2/
Boris.
---
On Thu, 7/16/09, Ruiz, Jason T
<jason.t.ruiz@xxxxxxxxxxx> wrote:
From:
Ruiz, Jason T <jason.t.ruiz@xxxxxxxxxxx> Subject:
[Xen-users] Xen on Jaunty To:
xen-users@xxxxxxxxxxxxxxxxxxx Date: Thursday, July 16, 2009,
9:23 AM
I
decided to give this a try as I'm out of fun things to do, but
I'm at my wits end on this one. I have compiled
a 2.6.30 kernel with Xen enabled, and compiled and
installed Xen 3.4 from source. 2 major problems I have noticed
is that after configuring grub per the documentation I've found,
it either reboots my PC after grub loads the config, or stays at
a black screen. The second problem is the error
below:
Traceback (most recent call
last): File "/usr/sbin/xm", line 8, in
<module> from xen.xm import
main ImportError: No module named xen.xm
Sincerely,
Jason T.
Ruiz
-----Inline Attachment
Follows-----
| -----Inline
Attachment Follows-----
|
|
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- RE: [spam] Re: [Xen-users] Xen on Jaunty,
Boris Derzhavets <=
|
|
|