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

Re: [Xen-devel] Installing Xen 3.3.1 from sources on Hardy or Lenny.


  • To: Thiago Camargo Martins Cordeiro <thiagocmartinsc@xxxxxxxxx>
  • From: Dulloor <dulloor@xxxxxxxxx>
  • Date: Sun, 22 Feb 2009 17:29:19 -0500
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Sun, 22 Feb 2009 14:29:59 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=IxZIjjstNw4akPxaJYpHQuBWdoH0Y5HuCs52UuDW701/w4BT6icNaL2oH7HkCWCPqY D5LC3zbbztnbF1BQx0hB81V7QTIiZs2ZHNw1PZoPaaz92iICsJo5VwYxWLwha/FTUMMC 9LQyxypxoYY5j0MMHs0VxItwSHkVasj8aveTk=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

syslog output :
Feb 22 17:23:26 billthepony kernel: PM: Adding info for xen-backend:vfb-9-0
Feb 22 17:23:26 billthepony kernel: PM: Adding info for xen-backend:vif-9-0
Feb 22 17:23:27 billthepony kernel: PM: Adding info for xen-backend:console-9-0
Feb 22 17:23:27 billthepony logger: /etc/xen/scripts/vif-nat: online XENBUS_PATH=backend/vif/9/0
Feb 22 17:23:27 billthepony logger: /etc/xen/scripts/vif-nat: Successful vif-nat online for vif9.0.
Feb 22 17:23:27 billthepony logger: /etc/xen/scripts/vif-nat: Writing backend/vif/9/0/hotplug-status connected to xenstore.
Feb 22 17:23:28 billthepony kernel: PM: Adding info for xen-backend:vkbd-10-0
Feb 22 17:23:28 billthepony kernel: PM: Adding info for xen-backend:vfb-10-0
Feb 22 17:23:28 billthepony kernel: PM: Adding info for xen-backend:vbd-10-768
Feb 22 17:23:28 billthepony kernel: PM: Adding info for xen-backend:vbd-10-5632
Feb 22 17:23:28 billthepony kernel: PM: Adding info for xen-backend:vif-10-0
Feb 22 17:23:28 billthepony kernel: PM: Adding info for xen-backend:vif-10-1
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/vif-nat: online XENBUS_PATH=backend/vif/10/0
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/10/768
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/vif-nat: online XENBUS_PATH=backend/vif/10/1
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/10/5632
Feb 22 17:23:28 billthepony kernel: PM: Adding info for xen-backend:console-10-0
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/block: Writing backend/vbd/10/768/node /dev/loop0 to xenstore.
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/block: Writing backend/vbd/10/768/physical-device 7:0 to xenstore.
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/block: Writing backend/vbd/10/768/hotplug-status connected to xenstore.
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/vif-nat: Successful vif-nat online for vif10.0.
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/vif-nat: Writing backend/vif/10/0/hotplug-status connected to xenstore.
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/block: Writing backend/vbd/10/5632/node /dev/loop1 to xenstore.
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/block: Writing backend/vbd/10/5632/physical-device 7:1 to xenstore.
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/block: Writing backend/vbd/10/5632/hotplug-status connected to xenstore.
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/vif-nat: Writing backend/vif/10/1/hotplug-error ip route add 10.0.0.1 dev vif10.1 src 10.0.0.128 failed backend/vif/10/1/hotplug-status error to xenstore.
Feb 22 17:23:28 billthepony logger: /etc/xen/scripts/vif-nat: ip route add 10.0.0.1 dev vif10.1 src 10.0.0.128 failed
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/10/5632
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/vif-nat: offline XENBUS_PATH=backend/vif/10/0
Feb 22 17:23:29 billthepony kernel: PM: Removing info for xen-backend:vkbd-10-0
Feb 22 17:23:29 billthepony kernel: PM: Removing info for xen-backend:vfb-10-0
Feb 22 17:23:29 billthepony kernel: PM: Removing info for xen-backend:console-10-0
Feb 22 17:23:29 billthepony kernel: PM: Removing info for xen-backend:vbd-10-768
Feb 22 17:23:29 billthepony kernel: PM: Removing info for xen-backend:vbd-10-5632
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/10/5632
Feb 22 17:23:29 billthepony kernel: PM: Removing info for xen-backend:vif-10-0
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/vif-nat: ifconfig vif10.0 down failed
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/vif-nat: Successful vif-nat offline for vif10.0.
Feb 22 17:23:29 billthepony kernel: PM: Removing info for xen-backend:vif-10-1
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vkbd/10/0
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/vif-nat: offline XENBUS_PATH=backend/vif/10/1
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/10/768
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/console/10/0
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vif/10/0
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vfb/10/0
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/10/768
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/vif-nat: ifconfig vif10.1 down failed
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/vif-nat: Successful vif-nat offline for vif10.1.
Feb 22 17:23:29 billthepony logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vif/10/1
Feb 22 17:23:37 billthepony kernel: vif9.0: no IPv6 routers present


I have turned off avahi-daemon, which didn't matter anyway.

-dulloor

On Sun, Feb 22, 2009 at 4:36 PM, Dulloor <dulloor@xxxxxxxxx> wrote:
Have you verified this with stubdom ?
stubdom still doesn't work for me (on hardy) with any vif configuration (please see my other mail). Without a vif, there is no problem. Any ideas ?

-dulloor

On Sun, Feb 22, 2009 at 1:22 PM, Thiago Camargo Martins Cordeiro <thiagocmartinsc@xxxxxxxxx> wrote:
Hi folks!

 This is how I install Xen from sources on Hardy, maybe it work for Lenny too...

# Necessary packages to compile Xen (this packages can be purged after the compilation of Xen):

aptitude install --without-recommends bcc bin86 build-essential comerr-dev debhelper defoma diffstat dpkg-dev fontconfig fontconfig-config g++ g++-4.2 gawk gettext ghostscript graphviz gs-common gsfonts html2text intltool-debian libc6-dev-i386 libc6-i386 libcairo2 libcupsimage2 libcupsys2 libcurl4-openssl-dev libdatrie0 libdrm2 libfontconfig1 libfreetype6 libgd2-noxpm libgl1-mesa-dev libgl1-mesa-glx libglib2.0-0 libglu1-mesa libglu1-mesa-dev libglu1-xorg-dev libgraphviz4 libgs8 libice6 libidn11-dev libjpeg62 libjpeg62-dev libkadm55 libkpathsea4 libkrb5-dev libldap2-dev libltdl3 libncurses5-dev libpango1.0-0 libpango1.0-common libpaper1 libpcre3 libpixman-1-0 libpng12-0 libpoppler2 libpthread-stubs0 libpthread-stubs0-dev libsdl1.2-dev libsm6 libssl-dev libstdc++6-4.2-dev libthai-data libthai0 libtiff4 libtimedate-perl libvncserver-dev libvncserver0 libx11-6 libx11-data libx11-dev libxau-dev libxau6 libxaw7 libxcb-xlib0 libxcb-xlib0-dev libxcb1 libxcb1-dev libxdamage1 libxdmcp-dev libxdmcp6 libxext6 libxfixes3 libxft2 libxml2-dev libxmu6 libxpm4 libxrender1 libxt6 libxxf86vm1 make mesa-common-dev mercurial patch pciutils-dev pkg-config po-debconf python-all python-all-dev python2.4 python2.4-dev python2.4-minimal quilt tex-common texinfo texlive-base texlive-base-bin texlive-common texlive-doc-base texlive-fonts-recommended texlive-latex-base texlive-latex-recommended transfig ttf-dejavu ttf-dejavu-core ttf-dejavu-extra x11-common x11proto-core-dev x11proto-input-dev x11proto-kb-dev xtrans-dev zlib1g-dev


mkdir ~/xen-sources && cd ~/xen-sources
wget -c http://bits.xensource.com/oss-xen/release/3.3.1/xen-3.3.1.tar.gz
tar xzf xen-3.3.1.tar.gz && cd xen-3.3.1
make dist
cd dist/ ; ./install.sh

# Necessary packages to run Xen after installing it:

aptitude install --without-recommends binutils binutils-static bridge-utils debootstrap gcc gcc-4.2 libasound2 libbeecrypt6 libc6-dev libconfig-inifiles-perl libcurl3 libdirectfb-1.0-0 libexpect-perl libgomp1 libio-pty-perl libio-stty-perl libneon27 librpm4.4 libsdl1.2debian libsdl1.2debian-alsa libterm-readline-gnu-perl libterm-size-perl libtext-template-perl libxml2 linux-libc-dev linux-restricted-modules-common nvidia-kernel-common perl-doc python-dev python2.5-dev rinse rpm screen sgml-base vnstat xen-shell xen-tools xfsprogs xml-core python-xml

# Python XML is obsolete will be removed soon, but for now, the Xen depends on it.
echo oldxml >> /usr/lib/python2.5/site-packages/oldxml.pth

# Linux 2.6.18.8-xen does not have AppArmor.
/etc/init.d/apparmor stop
update-rc.d -f apparmor remove

# Update modules / make new initramfs image
depmod -a 2.6.18.8-xen
update-initramfs -k 2.6.18.8-xen -c -u

# Edit /boor/grub/menu.lst and configure you Xen boot options, if you wish.

#--- menu.lst ---
## Xen hypervisor options to use with the default Xen boot option
# xenhopt=dom0_mem=512M

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0 nosmp
#--- menu.lst

# Update Grub's menu:
update-grub

# Configure the system to start Xen on every boot:
update-rc.d xend defaults 20 21
update-rc.d xendomains defaults 21 20

# Reboot into you new Hypervisor
reboot

# If you have a root file system of your dom0 on LVM (or even LVM on top of raid1), you probaly can't boot your dom0.
# So, if you see this prompt:

(initramfs)

# Run the following command to continue the system boot at (initramfs) prompt :
(initramfs) lvm vgchange -ay
(initramfs) exit

Welcome to your new hypervisor!

Regards,
Thiago


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



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

 


Rackspace

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