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

[Xen-users] Re: installing xen on a vmware work station


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Abhishek Dixit <abhidixit87@xxxxxxxxx>
  • Date: Wed, 2 Mar 2011 21:01:46 +0530
  • Delivery-date: Wed, 02 Mar 2011 07:33:36 -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 :content-type:content-transfer-encoding; b=Qi/LbKhPs6yvDEUcMYUf6emXJly2RG86pxNeCXgjwNo/zv1uzUqxguKoIMtdIJOF5+ XtAGMSPN6Y6KM/CuHsGkUZgBHCpKJo5sLj0xtgTOHW/H4BsWFiYraDvdX2IaQJSGDANf Yb7bapA50lQ5uy4ZxRIBunnBTmx2Oox8PxQNo=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Wed, Mar 2, 2011 at 8:35 PM, Abhishek Dixit <abhidixit87@xxxxxxxxx> wrote:
> Hi,
> I am trying to run Xen inside a Vmware guest.
> So I installed Vmware on a VT machine which is 64 bit.
> Then installed Ubuntu 10.04 64 bit HVM.
> Now I compiled Xen-4.0.1 from sources and a pv-ops Dom0 kernel for the same.
> Changed the grub etc and got kernel panics (and some errors which
> could not be logged)
>
>
> Step 1)
> apt-get install libcurl4-openssl-dev xserver-xorg-dev mercurial gitk
> build-essential libncurses5-dev uuid-dev gawk gettext texinfo bcc
> libncurses5-dev dpkg-dev debhelper iasl texinfo bridge-utils bison
> flex apt-get build-dep xen-3.3
>
> Step 2)
> cd /usr/src
> git clone
> git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git linux-2.6-xen
> cd linux-2.6-xen
> git checkout -b xen/stable-2.6.32.x origin/xen/stable-2.6.32.x
>
> Step 3)
> make -j 2
> make modules_install install
> chmod g-s /usr/src -R
> make deb-pkg
> dpkg -i ../linux-image*2.6.32.25*.deb
> depmod 2.6.32.25
> update-initramfs -c -k 2.6.32.25
>
> Here I am not clear as how did the version changed from 2.6.32.25 as
> original git pull happened at 2.6.32.27
>
>
> echo “xen-evtchn” >> /etc/modules
>
>
> Step  4)
>
> tar -xzvf  xen-4.0.1.tar.gz
> cd /usr/src/xen-4.0.1
>  make xen
>  make tools
>  make install-xen
>
>  make install-tools PYTHON_PREFIX_ARG=
>
> at this point I got some errors during make install-tools PYTHON_PREFIX_ARGS=
>
>
> xen/lowlevel/xc/xc.c:2353: error: expected declaration specifiers
> before ‘initxc’
> xen/lowlevel/xc/xc.c:2382: error: expected ‘{’ at end of input
> error: command 'gcc' failed with exit status 1
> make[3]: *** [buildpy] Error 1
> make[3]: Leaving directory `/usr/src/xen-4.0.1/tools/python'
> make[2]: *** [subdir-install-python] Error 2
> make[2]: Leaving directory `/usr/src/xen-4.0.1/tools'
> make[1]: *** [subdirs-install] Error 2
> make[1]: Leaving directory `/usr/src/xen-4.0.1/tools'
> make: *** [install-tools] Error 2
>
>
>
> Step 5)
>
> So I had installed from this page http://wiki.xensource.com/xenwiki/Xen4.0
> apt-get install bcc bin86 gawk bridge-utils iproute libcurl3
> libcurl4-openssl-dev bzip2 module-init-tools transfig tgif texinfo
> texlive-latex-base texlive-latex-recommended texlive-fonts-extra
> texlive-fonts-recommended pciutils-dev mercurial build-essential make
> gcc libc6-dev zlib1g-dev python python-dev python-twisted
> libncurses5-dev patch libvncserver-dev libsdl-dev libjpeg62-dev iasl
> libbz2-dev e2fslibs-dev git-core uuid-dev ocaml libx11-dev bison fle
>
> apt-get install  gcc-multilib xz-utils
> then proceeded with make install-tools
>
>
>
> Step 6)
>
> update-rc.d xend defaults 20 21
> update-rc.d xendomains defaults 21 20
>
> Things upto here worked perfectly.
> Now I reboot in Xen with grub entry
>
>
> menuentry 'Xen 4 Ubuntu 10.04 kernel 2.6.32.25 ' {
>        insmod ext2
>        set root='(hd0,1)'
>        multiboot (hd0,1)/boot/xen.gz dummy=dummy
>        module  /boot/vmlinuz-2.6.32.25 dummy=dummy noapt
> root=/dev/sda1 ro console=tty0
>        module  /boot/initrd.img-2.6.32.25
> }
>
>
>
>
>
> Now  I see a lot of kernel panic and similar messages which did not
> got logged in any where?
> Can any one tell me what wrong thing did I do above since there is no
> log any where?
>
> Can some where I can catch these errors some how?
>
Here are some logs
/var/log/messages

Mar  2 07:26:16 ubuntu rsyslogd: [origin software="rsyslogd"
swVersion="4.2.0" x-pid="672" x-info="http://www.rsyslog.com";]
(re)start
Mar  2 07:26:16 ubuntu rsyslogd: rsyslogd's groupid changed to 103
Mar  2 07:26:16 ubuntu rsyslogd: rsyslogd's userid changed to 101


/var/log/boot

(Nothing has been logged yet.)

/var/log/boot.log


fsck from util-linux-ng 2.17.2
udevd[326]: BUS= will be removed in a future udev version, please use
SUBSYSTEM= to match the event device, or SUBSYSTEMS= to match a parent
device, in /etc/udev/rules.d/99-vmware-scsi-udev.rules:12
^M
udevd[326]: SYSFS{}= will be removed in a future udev version, please
use ATTR{}= to match the event device, or ATTRS{}= to match a parent
device, in /etc/udev/rules.d/99-vmware-scsi-udev.rules:12
^M
/dev/sda1: clean, 328783/1253376 files, 3982056/5012992 blocks
 * Setting sensors limits       ^[[80G ^M^[[74G[ OK ]
 ^[[33m*^[[39;49m Speech-dispatcher configured for user sessions
 * Starting Common Unix Printing System: cupsd       ^[[80G ^M^[[74G[ OK ]
 ^[[33m*^[[39;49m PulseAudio configured for per-user sessions
 * Enabling additional executable binary formats binfmt-support
^[[80G ^M^[[74G[ OK ]
 * Checking battery state...       ^[[80G ^M^[[74G[ OK ]

/var/log/debug

Mar  2 07:26:11 ubuntu rtkit-daemon[1402]: Sucessfully called chroot.
Mar  2 07:26:11 ubuntu rtkit-daemon[1402]: Sucessfully dropped privileges.
Mar  2 07:26:11 ubuntu rtkit-daemon[1402]: Sucessfully limited resources.
Mar  2 07:26:11 ubuntu rtkit-daemon[1402]: Running.
Mar  2 07:26:11 ubuntu rtkit-daemon[1402]: Watchdog thread running.
Mar  2 07:26:11 ubuntu rtkit-daemon[1402]: Canary thread running.
Mar  2 07:26:12 ubuntu rtkit-daemon[1402]: Supervising 1 threads of 1
processes of 1 users.
Mar  2 07:26:12 ubuntu rtkit-daemon[1402]: Supervising 2 threads of 1
processes of 1 users.
Mar  2 07:26:18 ubuntu rtkit-daemon[1402]: Supervising 3 threads of 1
processes of 1 users.

/var/log/dmesg
http://pastebin.com/PXzbBrET


Ok here is some  more information when I booted without the hypervisor
I was able to cleanly boot into the pv-ops Dom0 kernel.
i.e. with following grub entry
menuentry 'Ubuntu, with Linux 2.6.32.25' --class ubuntu --class
gnu-linux --class gnu --class os {
        recordfail
        insmod ext2
        set root='(hd0,1)'
        search --no-floppy --fs-uuid --set ef6fb0a3-17d8-46b8-944b-4d84fbd3c236
        linux   /boot/vmlinuz-2.6.32.25
root=UUID=ef6fb0a3-17d8-46b8-944b-4d84fbd3c236 ro   quiet splash
        initrd  /boot/initrd.img-2.6.32.25
}

but if I try to boot with hypervisor i.e. following grub


 menuentry 'Xen 4 Ubuntu 10.04 kernel 2.6.32.25 ' {
        insmod ext2
        set root='(hd0,1)'
        multiboot (hd0,1)/boot/xen.gz dummy=dummy
        module  /boot/vmlinuz-2.6.32.25 dummy=dummy noapt
 root=/dev/sda1 ro console=tty0
        module  /boot/initrd.img-2.6.32.25
 }

then I get some panic etc.

uname -a
Linux ubuntu 2.6.32.25 #1 SMP Wed Mar 2 02:03:42 PST 2011 x86_64 GNU/Linux

_______________________________________________
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®.