[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [spam] Re: [Xen-users] Xen on Jaunty
- To: xen-users@xxxxxxxxxxxxxxxxxxx, Jason TRuiz <jason.t.ruiz@xxxxxxxxxxx>
- From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
- Date: Thu, 16 Jul 2009 09:01:33 -0700 (PDT)
- Cc:
- Delivery-date: Thu, 16 Jul 2009 09:02:56 -0700
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=Ej9zcZ0Uo9/z7iRPd7OM7udtPh19KeoNFAyaPJIvm7gvdwxcRGoFIGyVZLhS+4XLMGmtIx0tAysF2OhAjqk+95yDcA7rdOt5N2hzy0KcMfuX9C9UEwGFn6QiWLcwYjxSP8KTRCxUFK8dVtZA7dbyUz6T7uZ3y7Gr2Felm/YBrkc=;
- List-id: Xen user discussion <xen-users.lists.xensource.com>
Tne answer is NO. Any vanilla kernel (> 2.6.27) itself allows only to enable PV Guest (paravirtual) mode, but not Xen Dom0 Support. Mainline Linux
doesn't contain Xen Dom0 Support merged. You have to work on it on your
own.
I've sent you two links in the very first message. View second one - patching 2.6.30.1 via Andrew's Lyon rebase patch set :-
http://lxer.com/module/newswire/view/122758/index.html
The procedure above will build 2.6.30.1 xenified kernel, i.e. will implement
Xen Privelege (Dom0) Domain Support. My Config.mk is attached.
Boris.
P.S. You may want to build another type of kernel, enabling Xen Dom0 Support. It's pvops enabled kernel via Jereme Fitzhardinge Git Repo.
Then view :-
http://lxer.com/module/newswire/view/122253/index.html
B.
--- 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:25 AM
Didn't reboot properly. Maybe I'm misunderstanding the
kernel part, using a vanilla 2.6.30 with all of the xen stuff enabled should
work, correct?
Sincerely,
Jason T.
Ruiz
IT Service Desk Tier II
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-----
|
-----Inline Attachment Follows-----
|
Attachment:
Config.mk
Description: Binary data
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
