[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Fw: [Xen-users] Re: Xen 3.4 Hackery on Ubuntu 9.04 (aka Jaunty) Server


  • To: Niels Jende <mylists1@xxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
  • Date: Thu, 28 May 2009 02:59:09 -0700 (PDT)
  • Cc:
  • Delivery-date: Thu, 28 May 2009 03:00:03 -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=I7yz/s8tlrk1IgjEv6NuBdE9jDyx9s9DXcprZ4d+/mxQdPYfXB9c5eJDMQtF2/ABjA3bLeyrF0smL0/bvCEtHDbWM2NXuy3AwKc0jUM75NS6g5U8UNDgAxO0cnjeeW+ZUYJAcDCRW26Epf1amTgEZUkDjFomvC4cVUahrXV+mPA=;
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

> # make install-tools
> came up with an error.
> Here is what I got as an output:
> /bin/sh: git: not found
> make[1]: ***[ioemu-dir-find] Error 127
> make[1]: Leaving Directory 'usr/src/xen-3.4-testing.hg/tools
>make: *** [tools/ioemu-dir] Error 2

At thist point:-

# apt-get install gitk

You just don't have git core system installed

When git clone will be done i would expect you to get several
more errors. The shortest way to fix it is install Ubuntu Desktop
via "tasksel" and be able to load Synaptic Manager GUI tool.
It allows to find package without knowledge of it's exact name.
Put in search window of Synaptic Manager :-
First gitk
1. openssl-dev
2. xorg-dev
3. python2.5-dev
4. bcc
5. gettext
6. texinfo

Synaptic Manager will automatically shows up matching names , not
exactly the same as required by search, resolves all dependencies
and suggests to apply.
Like "x11-server-dev". Just think a bit and mark right ones for
install. Then click apply. The set of packages on 9.04 is different
from 8.10. Any time build fails means you are missing some package
again. All required are Ubuntu 9.04 Repos. It's for sure.
I would be hesitant to reproduce it in text environment. An exact
names on apt-get install list should be required.

When failing do first:-
# make tools
# make stubdoms
When this builds commited rerun:-
# make world
Guess why ? :)

Boris.


--- On Thu, 5/28/09, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:

From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Subject: [Xen-users] Re: Xen 3.4 Hackery on Ubuntu 9.04 (aka Jaunty) Server
To: "Fabian Zimmermann" <xen-users@xxxxxxxxxxxxxxxxx>
Cc: "Niels Jende" <mylists1@xxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Date: Thursday, May 28, 2009, 2:44 AM

Make Xen 3.4 biuld with python 2.6 (default) on Ubuntu 9.04 Server:-
Install all packages required by Xen build:-

# cd /usr/src
# hg clone http://xenbits.xensource.com/xen-3.4-testing.hg
# cd xen-3.4-testing.hg
Set in Config.mk
PYTHON = python
PYTHON_PREFIX_ARG =
# make install-xen
# make install-tools
# make install-stubdom

Install any xenified or pvops kernel.

Dom0 kernel loads with no problems under Xen 3.4 Hypervisor.
Xend starts fine.

# xm info
# brctl show
# ifconfig

all looks good.

Then try create DomU. See what happens.

Boris.


--- On Thu, 5/28/09, Fabian Zimmermann <xen-users@xxxxxxxxxxxxxxxxx> wrote:

From: Fabian Zimmermann <xen-users@xxxxxxxxxxxxxxxxx>
Subject: Re: Xen 3.4 Hackery on Ubuntu 9.04 (aka Jaunty) Server
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: "Niels Jende" <mylists1@xxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Date: Thursday, May 28, 2009, 2:28 AM

Hi,
>
> > As soon as "xm info" is running without problems. You have
> successfully installed and
> > started Xen.
>
> That's a mistake.
> Have ever get a messages:
> 1. "Device 0 (vif) cannot be connected. Hotplug scripts not working"
> 2. "XENBUS timed out waiting for vbd" ?
>
> Boris.
>
Right, better would be:



Fabian


-----Inline Attachment Follows-----

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.