Attempt of prevu Xen 3.4.1 Hypervisor on Ubuntu Jaunty Server (64-bit)

PVOPS kernel been installed to run under Xen 3.4.1 was 2.6.31-rc5. To build Xen 3.4.1 Dom0 via Bug Attachments at Please merge xen-3.4 (3.4.0-2) from debian unstable installed “prevu” and performed build to obtain debian packages.
The same procedure will work for xenified 2.6.30.2 ( aka Suse ) kernel.
To avoid problems with debian packages install would be better to have
python-all-dev installed at the beginning.



I have to notice , that straight forward port Xen 3.4.1 to Ubuntu Jaunty Server requires only python6-dev and is doesn’t depend on network-manager presence or absence.

# apt-get install prevu
# DISTRO=jaunty prevu-init

When done.

# wget http://launchpadlibrarian.net/30283878/xen-3.4_3.4.1-1ubuntu1.diff.gz
# wget http://launchpadlibrarian.net/30283881/xen-3.4_3.4.1-1ubuntu1.dsc
# wget http://launchpadlibrarian.net/30283951/xen-3.4_3.4.1.orig.tar.gz

Now build packages

# /usr/bin/prevu xen-3.4_3.4.1-1ubuntu1.dsc
. . . . . . . . . . .
-> unmounting /var/cache/prevu/jaunty-debs filesystem
-> unmounting dev/pts filesystem
-> unmounting proc filesystem
-> cleaning the build env
-> removing directory /var/cache/prevu/builds/20765 and its subdirectories
** Success!. You can find source packages and .debs at /var/cache/prevu/jaunty-debs **

Build succeeded. Attempt to install generated packages.

dpkg -i libxen3_3.4.1-1ubuntu1~9.04prevu1_amd64.deb \
libxen3-dev_3.4.1-1ubuntu1~9.04prevu1_amd64.deb \
python-xen-3.4_3.4.1-1ubuntu1~9.04prevu1_amd64.deb \
xen-docs-3.4_3.4.1-1ubuntu1~9.04prevu1_amd64.deb \
xen-hypervisor-3.4_3.4.1-1ubuntu1~9.04prevu1_amd64.deb \
xen-utils-3.4_3.4.1-1ubuntu1~9.04prevu1_amd64.deb

root@ServerJaunty:/var/cache/prevu/jaunty-debs# ./install.sh

root@ServerJaunty:/var/cache/prevu/jaunty-debs# ./install.sh
Selecting previously deselected package libxen3.
(Reading database ... 125571 files and directories currently installed.)
Unpacking libxen3 (from libxen3_3.4.1-1ubuntu1~9.04prevu1_amd64.deb) ...
Selecting previously deselected package libxen3-dev.
Unpacking libxen3-dev (from libxen3-dev_3.4.1-1ubuntu1~9.04prevu1_amd64.deb) ...
Selecting previously deselected package python-xen-3.4.
Unpacking python-xen-3.4 (from python-xen-3.4_3.4.1-1ubuntu1~9.04prevu1_amd64.deb) ...
Selecting previously deselected package xen-docs-3.4.
Unpacking xen-docs-3.4 (from xen-docs-3.4_3.4.1-1ubuntu1~9.04prevu1_amd64.deb) ...
Selecting previously deselected package xen-hypervisor-3.4.
Unpacking xen-hypervisor-3.4 (from xen-hypervisor-3.4_3.4.1-1ubuntu1~9.04prevu1_amd64.deb) ...
Selecting previously deselected package xen-utils-3.4.
Unpacking xen-utils-3.4 (from xen-utils-3.4_3.4.1-1ubuntu1~9.04prevu1_amd64.deb) ...
Setting up libxen3 (3.4.1-1ubuntu1~9.04prevu1) ...

Setting up libxen3-dev (3.4.1-1ubuntu1~9.04prevu1) ...
Setting up python-xen-3.4 (3.4.1-1ubuntu1~9.04prevu1) ...
Setting up xen-docs-3.4 (3.4.1-1ubuntu1~9.04prevu1) ...
Setting up xen-hypervisor-3.4 (3.4.1-1ubuntu1~9.04prevu1) ...
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Ignoring Xen kernel on non-Xen host: vmlinuz-2.6.31-rc3
Ignoring Xen kernel on non-Xen host: vmlinuz-2.6.30.1.old
Found Xen hypervisor 3.4, kernel: /vmlinuz-2.6.31-rc3
Found Xen hypervisor 3.4, kernel: /vmlinuz-2.6.30.1.old
Found Xen hypervisor 3.4, kernel: /vmlinuz-2.6.30.1
Found kernel: /vmlinuz-2.6.30.1
Found kernel: /vmlinuz-2.6.28-11-server
Found kernel: /memtest86+.bin
Updating /boot/grub/menu.lst ... done

Setting up xen-utils-3.4 (3.4.1-1ubuntu1~9.04prevu1) ...
grep: /proc/xen/capabilities: No such file or directory

Processing triggers for man-db ...
Processing triggers for libc6 ...
ldconfig deferred processing now taking place

root@ServerJaunty:/usr/lib/python2.6/site-packages# ls -l xen*

-rw-r--r-- 1 root root 171 2009-08-12 21:51 xen-3.0-py2.6.egg-info

xen:
total 36
-rw-r--r-- 1 root root 2 2009-08-06 17:57 __init__.py
-rw-r--r-- 1 root root 134 2009-08-12 21:51 __init__.pyc
drwxr-xr-x 2 root root 4096 2009-08-12 21:51 lowlevel
drwxr-xr-x 2 root root 4096 2009-08-12 21:51 sv
drwxr-xr-x 3 root root 4096 2009-08-12 21:51 util
drwxr-xr-x 2 root root 4096 2009-08-12 21:51 web
drwxr-xr-x 5 root root 4096 2009-08-12 21:51 xend
drwxr-xr-x 3 root root 4096 2009-08-12 21:51 xm
drwxr-xr-x 2 root root 4096 2009-08-12 21:51 xsview



root@ServerJaunty:~# dpkg -l '*xen*'|grep "^ii"

ii libxen3 3.4.1-1ubuntu1~9.04pre library interface for Xen, a Virtual Machine Monitor
ii libxen3-dev 3.4.1-1ubuntu1~9.04pre headers for Xen, a Virtual Machine Monitor
ii python-xen-3.4 3.4.1-1ubuntu1~9.04pre python bindings for Xen, a Virtual Machine Monitor
ii xen-docs-3.4 3.4.1-1ubuntu1~9.04pre documentation for XEN, a Virtual Machine Monitor
ii xen-hypervisor-3.4 3.4.1-1ubuntu1~9.04pre The Xen Hypervisor for i386 and amd64.
ii xen-utils-3.4 3.4.1-1ubuntu1~9.04pre XEN administrative tools

To setup xen bridged networking commented out all xen-bridge declarations in /etc/xen/xend-config.sxp and manually edited /etc/network/interfaces as follows .

# apt-get remove network-manager

root@ServerJaunty:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet dhcp
# Bridge definied
auto br0
iface br0 inet static
address 192.168.1.45
network 192.168.0.0
netmask 255.255.255.0
broadcast 192.168.1.255
gateway 192.168.1.1
bridge_ports eth0
bridge_fd 9
bridge_hello 2
bridge_maxage 12
bridge_stp off

Reboot into Xen Host via grub entry like :-

title Xen 3.4 / Ubuntu 9.04 kernel 2.6.31-rc5
uuid b019ef2b-f019-43c2-b6c9-de684155ac92
kernel /xen-3.4.gz
module /vmlinuz-2.6.31-rc5 root=/dev/sdc2 ro console=tty0
module /initrd-2.6.31-rc5.img


Not sure what could be the reason of the issue with eth0 brought up with IP address from the same subnet for both PVOPS and xenified 2.6.30.2 (aka Suse) kernel. The way to fix it (for me) appears to be /etc/init.d/networking restart after login via gnome terminal session.

root@ServerJaunty:~# ifconfig
br0 Link encap:Ethernet HWaddr 00:1e:8c:25:d9:23
inet addr:192.168.1.45 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21e:8cff:fe25:d923/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:22 errors:0 dropped:0 overruns:0 frame:0
TX packets:59 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3556 (3.5 KB) TX bytes:7153 (7.1 KB)

eth0 Link encap:Ethernet HWaddr 00:1e:8c:25:d9:23
inet addr:192.168.1.42 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21e:8cff:fe25:d923/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:24 errors:0 dropped:0 overruns:0 frame:0
TX packets:78 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3648 (3.6 KB) TX bytes:11520 (11.5 KB)
Interrupt:17

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:58 errors:0 dropped:0 overruns:0 frame:0
TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3740 (3.7 KB) TX bytes:3740 (3.7 KB)

root@ServerJaunty:~# /etc/init.d/networking restart
* Reconfiguring network interfaces... postconf: fatal: open /etc/postfix/main.cf: No such file or directory
There is already a pid file /var/run/dhclient.eth0.pid with pid 3409
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:1e:8c:25:d9:23
Sending on LPF/eth0/00:1e:8c:25:d9:23
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.1.1 port 67
* Reloading /etc/samba/smb.conf smbd only
...done.
postconf: fatal: open /etc/postfix/main.cf: No such file or directory
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:1e:8c:25:d9:23
Sending on LPF/eth0/00:1e:8c:25:d9:23
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPOFFER of 192.168.1.42 from 192.168.1.1
DHCPREQUEST of 192.168.1.42 on eth0 to 255.255.255.255 port 67
DHCPACK of 192.168.1.42 from 192.168.1.1
* Reloading /etc/samba/smb.conf smbd only
...done.
bound to 192.168.1.42 -- renewal in 105513 seconds.
* if-up.d/mountnfs[eth0]: waiting for interface br0 before doing NFS mounts
postconf: fatal: open /etc/postfix/main.cf: No such file or directory

Waiting for br0 to get ready (MAXWAIT is 20 seconds).
postconf: fatal: open /etc/postfix/main.cf: No such file or directory
[ OK ]
root@ServerJaunty:~# ifconfig
br0 Link encap:Ethernet HWaddr 00:1e:8c:25:d9:23
inet addr:192.168.1.45 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21e:8cff:fe25:d923/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:790 (790.0 B) TX bytes:3503 (3.5 KB)

eth0 Link encap:Ethernet HWaddr 00:1e:8c:25:d9:23
inet6 addr: fe80::21e:8cff:fe25:d923/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:46 errors:0 dropped:0 overruns:0 frame:0
TX packets:124 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6862 (6.8 KB) TX bytes:19101 (19.1 KB)
Interrupt:17

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:58 errors:0 dropped:0 overruns:0 frame:0
TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3740 (3.7 KB) TX bytes:3740 (3.7 KB)






Finally , after :-
# apt-get remove network-manager
i was able to configure standard bridge via xend-config.sxp

root@ServerJaunty:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp

root@ServerJaunty:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:1e:8c:25:d9:23
inet addr:192.168.1.42 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21e:8cff:fe25:d923/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:19 errors:0 dropped:0 overruns:0 frame:0
TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3838 (3.8 KB) TX bytes:8413 (8.4 KB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:74 errors:0 dropped:0 overruns:0 frame:0
TX packets:74 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4700 (4.7 KB) TX bytes:4700 (4.7 KB)

peth0 Link encap:Ethernet HWaddr 00:1e:8c:25:d9:23
inet6 addr: fe80::21e:8cff:fe25:d923/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:20 errors:0 dropped:0 overruns:0 frame:0
TX packets:71 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3884 (3.8 KB) TX bytes:9531 (9.5 KB)
Interrupt:17

root@ServerJaunty:~# brctl show
bridge name bridge id STP enabled interfaces
eth0 8000.001e8c25d923 no peth0
pan0 8000.000000000000 no




Regarding , Xen 3.4.1 port to Ubuntu 9.04 Server view also :-
Setup Xen 3.4.1 Dom0 on top of Ubuntu 9.04 Server via Marc – A. Dahlhaus’s UDEV patch

About these ads

8 Responses to Attempt of prevu Xen 3.4.1 Hypervisor on Ubuntu Jaunty Server (64-bit)

  1. Bruce says:

    Great tutorial thanks!

    While I did still remove network-manager, I was able to get things working without the /etc/network/interfaces etc/xen/xend-config.sxp hacking.
    I left both of these files unmodified and was able to bring up domUs with dhcp assigned addresses.

    Why is that step necessary?

    Also, it shows that you have eth0 assigned as a dhcp configured port and as a bridge port. Is that valid?

  2. vps says:

    You have a very well informed. In a few places here will show as the source. I wish you continued working

  3. enesmedia says:

    reat thanks for the pointers, I had a quick look at Eucalyptus on Ubuntu, I’m not convinced… I’ll give a try a Open Nebula if I get the time.

  4. vps says:

    thank you bderzhavets!

  5. vps says:

    Write very useful information. Thank you for sharing this information.

  6. vps sunucu says:

    You have a very well informed. In a few places here will show as the source. I wish you continued working Best Regards.

  7. vps says:

    You have a very well informed. In a few places here will show as the source. thanks

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: