I have tried 4 time unsuccessfully to install Xen 4 on Ubuntu Lucid (10.4) 64 bit version using the tutorial at http://bderzhavets.wordpress.com/2010/04/24/set-up-ubuntu-10-04-server-pv-domu-at-xen-4-0-dom0-pvops-2-6-32-10-kernel-dom0-on-top-of-ubuntu-10-04-server/ on a Lenovo thinkcentre workstation. When I boot I get a kernel panic. If I boot the Linux kernel that I compiled using the tutorial on it''s own it boots fine. Is the likely cause hardware? is there a common error made in this tutorial that would cause a panic on boot. Murray _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
1. I would suggest you to obtain a serial log and escalate the problem to
xen-devel.
2. Could you post yours /usr/src/linux-2.6-xen/.config ( gzipped)
,/boot/grub/grub.cfg,
"df -h" output.
Boris.
--- On Tue, 7/13/10, Murray Thomson <murray_thomson7788@yahoo.com> wrote:
From: Murray Thomson <murray_thomson7788@yahoo.com>
Subject: [Xen-users] Xen 4 Ubuntu Lucid panics
To: xen-users@lists.xensource.com
Date: Tuesday, July 13, 2010, 9:41 AM
I have tried 4 time unsuccessfully to install Xen 4 on Ubuntu Lucid (10.4) 64
bit version using the tutorial
at http://bderzhavets.wordpress.com/2010/04/24/set-up-ubuntu-10-04-server-pv-domu-at-xen-4-0-dom0-pvops-2-6-32-10-kernel-dom0-on-top-of-ubuntu-10-04-server/
on a Lenovo thinkcentre workstation.
When I boot I get a kernel panic. If I boot the Linux kernel that I compiled
using the tutorial on it''s own it boots fine. 
Is the likely cause hardware? is there a common error made in this tutorial that
would
 cause a panic on boot. 
Murray
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
      
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Tue, Jul 13, 2010 at 6:41 AM, Murray Thomson < murray_thomson7788@yahoo.com> wrote:> I have tried 4 time unsuccessfully to install Xen 4 on Ubuntu Lucid (10.4) > 64 bit version using the tutorial at > > http://bderzhavets.wordpress.com/2010/04/24/set-up-ubuntu-10-04-server-pv-domu-at-xen-4-0-dom0-pvops-2-6-32-10-kernel-dom0-on-top-of-ubuntu-10-04-server/on a Lenovo thinkcentre workstation. > > When I boot I get a kernel panic. If I boot the Linux kernel that I > compiled using the tutorial on it''s own it boots fine. > > Is the likely cause hardware? is there a common error made in this tutorial > that would cause a panic on boot. > > Murray > >Is this the error you''re seeieng? http://lists.xensource.com/archives/html/xen-devel/2010-06/msg01146.html -Bruce _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  load_env
fi
set default="2"
if [ ${prev_saved_entry} ]; then
  set saved_entry=${prev_saved_entry}
  save_env saved_entry
  set prev_saved_entry  save_env prev_saved_entry
  set boot_once=true
fi
function savedefault {
  if [ -z ${boot_once} ]; then
    saved_entry=${chosen}
    save_env saved_entry
  fi
}
function recordfail {
  set recordfail=1
  if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env 
recordfail; fi; fi
}
insmod ext2
set root=''(hd0,1)''
search --no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e
if loadfont /usr/share/grub/unicode.pf2 ; then
  set gfxmode=640x480
  insmod gfxterm
  insmod vbe
  if terminal_output gfxterm ; then true ; else
    # For backward compatibility with versions of terminal.mod that
don''t
    # understand terminal_output
    terminal gfxterm
  fi
fi
insmod ext2
set root=''(hd0,1)''
search --no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
if [ ${recordfail} = 1 ]; then
  set timeout=-1
else
  set timeout=10
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry ''Ubuntu, with Linux 2.6.32.15'' --class ubuntu
--class gnu-linux
--class gnu --class os {
recordfail
insmod ext2
set root=''(hd0,1)''
search --no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e
linux/boot/vmlinuz-2.6.32.15 root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro
quiet
initrd/boot/initrd.img-2.6.32.15
}
menuentry ''Ubuntu, with Linux 2.6.32.15 (recovery mode)''
--class ubuntu --class
gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root=''(hd0,1)''
search --no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e
echo''Loading Linux 2.6.32.15 ...''
linux/boot/vmlinuz-2.6.32.15 root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro 
single 
echo''Loading initial ramdisk ...''
initrd/boot/initrd.img-2.6.32.15
}
menuentry ''Ubuntu, with Linux 2.6.32-21-server'' --class ubuntu
--class gnu-linux
--class gnu --class os {
recordfail
insmod ext2
set root=''(hd0,1)''
search --no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e
linux/boot/vmlinuz-2.6.32-21-server 
root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro   quiet
initrd/boot/initrd.img-2.6.32-21-server
}
menuentry ''Ubuntu, with Linux 2.6.32-21-server (recovery
mode)'' --class ubuntu
--class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root=''(hd0,1)''
search --no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e
echo''Loading Linux 2.6.32-21-server ...''
linux/boot/vmlinuz-2.6.32-21-server 
root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro single 
echo''Loading initial ramdisk ...''
initrd/boot/initrd.img-2.6.32-21-server
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod ext2
set root=''(hd0,1)''
search --no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e
linux16/boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod ext2
set root=''(hd0,1)''
search --no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e
linux16/boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the ''exec tail'' line above.
menuentry "Xen 4 / Ubuntu 10.04 kernel 2.6.32.15" {
insmod ext2
set root=''(hd0,1)''
multiboot (hd0,1)/boot/xen.gz dom0_mem=1024M loglvl=all guest_loglvl=all
module (hd0,1)/boot/vmlinuz-2.6.32.15 root=/dev/sda1 ro nomodeset
module (hd0,1)/boot/initrd.img-2.6.32.15
}
#menuentry "Xen 4 / Ubuntu 10.04 kernel 2.6.32.15a" {
#insmod ext2
#set root=''(hd0,1)''
#multiboot (hd0,1)/boot/xen.gz dummy=dummy
#module (hd0,1)/boot/vmlinuz-2.6.32.15 dummy=dummy nopat root=/dev/sdc2 ro 
console=tty0 
#module (hd0,1)/boot/initrd.img-2.6.32.15
#}
#menuentry "Xen 4 / Ubuntu 10.04 kernel 2.6.32.15b" {
#insmod ext2
#set root=''(hd0,1)''
#multiboot (hd0,1)/boot/xen-4.0.1-rc4-pre.gz dummy=dummy
#module (hd0,1)/boot/vmlinuz-2.6.32.15 dummy=dummy nopat root=/dev/sdc2 ro 
console=tty0 
#module (hd0,1)/boot/initrd.img-2.6.32.15
#}
menuentry "Xen 4 / Ubuntu 10.04 kernel 2.6.32.15 config 2" {
insmod ext2
set root=''(hd0,1)''
multiboot (hd0,1)/boot/xen.gz dummy=dummy
module (hd0,1)/boot/vmlinuz-2.6.32.15 dummy=dummy nopat root=/dev/sdb5 ro 
console=tty0
module (hd0,1)/boot/initrd.img-2.6.32.15
}
### END /etc/grub.d/40_custom ###
 Murray Thomson
________________________________
From: Boris Derzhavets <bderzhavets@yahoo.com>
To: xen-users@lists.xensource.com; Murray Thomson
<murray_thomson7788@yahoo.com>
Sent: Tue, July 13, 2010 9:54:49 AM
Subject: Re: [Xen-users] Xen 4 Ubuntu Lucid panics
1. I would suggest you to obtain a serial log and escalate the problem to 
xen-devel.
2. Could you post yours /usr/src/linux-2.6-xen/.config ( gzipped) 
,/boot/grub/grub.cfg,
"df -h" output.
Boris.
--- On Tue, 7/13/10, Murray Thomson <murray_thomson7788@yahoo.com> wrote:
>From: Murray Thomson <murray_thomson7788@yahoo.com>
>Subject: [Xen-users] Xen 4 Ubuntu Lucid panics
>To: xen-users@lists.xensource.com
>Date: Tuesday, July 13, 2010, 9:41 AM
>
>
>I have tried 4 time unsuccessfully to install Xen 4 on Ubuntu Lucid (10.4)
64
>bit version using the  tutorial at 
>http://bderzhavets.wordpress.com/2010/04/24/set-up-ubuntu-10-04-server-pv-domu-at-xen-4-0-dom0-pvops-2-6-32-10-kernel-dom0-on-top-of-ubuntu-10-04-server/
> on a Lenovo thinkcentre workstation.
>
>
>When I boot I get a kernel panic. If I boot the Linux kernel that I compiled
>using the tutorial on it''s own it boots fine. 
>
>
>Is the likely cause hardware? is there a common error made in this tutorial
that
>would  cause a panic on boot. 
>
>
>Murray
>
>-----Inline Attachment Follows-----
>
>
>_______________________________________________
>Xen-users mailing list
>Xen-users@lists.xensource.com
>http://lists.xensource.com/xen-users 
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
1. First 
Yours tuning backends ( right ?)
                 <M> Xen /dev/xen/evtchn
device                                                       
                  [*] Backend driver
support                                          
                  < >   Xen backend network
device                                   
                  < >   Block-device backend
driver                                                     
                  < >   Block-device tap backend
driver                                                 
                  <*>   PCI-device backend
driver                                                       
                          PCI Backend Mode (Virtual PCI) 
--->                                          
                  [ ]     PCI Backend
Debugging                                                         
                 <M> Xen
filesystem                                                                    
                 [*]   Create compatibility mount point
/proc/xen                                      
                 [*] Create xen entries under
/sys/hypervisor                                          
                 < > xen platform pci device
driver                                                    
                 < > userspace grant access device driver  
Per tutorial :-
  <*> Xen /dev/xen/evtchn
device                                                       
                  [*] Backend driver
support                                          
                  <*>   Xen backend network
device                                   
                  <*>   Block-device backend
driver                                                     
                  <*>   Block-device tap backend
driver                                                 
                  <*>   PCI-device backend
driver                                                       
                          PCI Backend Mode (Virtual PCI) 
--->                                          
                  [ ]     PCI Backend
Debugging                                                         
                 <*> Xen
filesystem                                                                    
                 [*]   Create compatibility mount point
/proc/xen                                      
                 [*] Create xen entries under
/sys/hypervisor                                          
                 <*> xen platform pci device
driver                                                    
                 <*> userspace grant access device driver 
Now 
# diff -auN config.received config.071310  > conf.patch
# cat conf.patch
. . . . . .
-# CONFIG_XEN_NETDEV_BACKEND is not set
-# CONFIG_XEN_BLKDEV_BACKEND is not set
-# CONFIG_XEN_BLKDEV_TAP is not set
+CONFIG_XEN_NETDEV_BACKEND=y
+CONFIG_XEN_BLKDEV_BACKEND=y
+CONFIG_XEN_BLKDEV_TAP=y
+CONFIG_XEN_BLKBACK_PAGEMAP=y
I attached mine config and config.patch.
Make diff one more time on your box and watch errors for yourself
The best option - just use config attached after git pull ( 2.6.32.16 )
2. Second.
Please submit your working grub entry for Xen (just one)  and "df  -h"
for corresponding vanilla entry. /dev/sdb5 and (hd0,1) seem strange to me.
Boris.
--- On Tue, 7/13/10, Murray Thomson <murray_thomson7788@yahoo.com> wrote:
From: Murray Thomson <murray_thomson7788@yahoo.com>
Subject: Re: [Xen-users] Xen 4 Ubuntu Lucid panics
To: "Boris Derzhavets" <bderzhavets@yahoo.com>,
xen-users@lists.xensource.com
Date: Tuesday, July 13, 2010, 10:52 AM
grub.cfg
## DO NOT EDIT THIS FILE## It is automatically generated by
/usr/sbin/grub-mkconfig using templates# from /etc/grub.d and settings from
/etc/default/grub#
### BEGIN /etc/grub.d/00_header ###if [ -s $prefix/grubenv ];
then  load_envfiset default="2"if [ ${prev_saved_entry} ]; then  set
saved_entry=${prev_saved_entry}  save_env saved_entry  set
prev_saved_entry=  save_env prev_saved_entry  set boot_once=truefi
function savedefault {  if [
 -z ${boot_once} ]; then    saved_entry=${chosen}    save_env saved_entry  fi}
function recordfail {  set recordfail=1  if [ -n ${have_grubenv} ]; then if [ -z
${boot_once} ]; then save_env recordfail; fi; fi}insmod ext2set
root=''(hd0,1)''search --no-floppy --fs-uuid --set
a2f031e5-cdce-440f-a736-64fd0e4ec43eif loadfont /usr/share/grub/unicode.pf2 ;
then  set gfxmode=640x480  insmod gfxterm  insmod vbe  if terminal_output
gfxterm ; then true ; else    # For backward compatibility with versions of
terminal.mod that don''t    # understand terminal_output    terminal
 gfxterm  fifiinsmod ext2set root=''(hd0,1)''search --no-floppy
--fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43eset
locale_dir=($root)/boot/grub/localeset lang=eninsmod gettextif [ ${recordfail} =
1 ]; then  set timeout=-1else  set timeout=10fi### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###set menu_color_normal=white/blackset
menu_color_highlight=black/light-gray### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###menuentry ''Ubuntu, with Linux
2.6.32.15'' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail	insmod ext2	set root=''(hd0,1)''	search --no-floppy
--fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e	linux
/boot/vmlinuz-2.6.32.15 root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro  
quiet	initrd	/boot/initrd.img-2.6.32.15}menuentry ''Ubuntu, with Linux
2.6.32.15 (recovery mode)'' --class ubuntu --class gnu-linux --class gnu
--class os {	recordfail	insmod
 ext2	set root=''(hd0,1)''	search --no-floppy --fs-uuid --set
a2f031e5-cdce-440f-a736-64fd0e4ec43e	echo	''Loading Linux 2.6.32.15
...''	linux	/boot/vmlinuz-2.6.32.15
root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro single 	echo	''Loading
initial ramdisk ...''	initrd
	/boot/initrd.img-2.6.32.15}menuentry ''Ubuntu, with Linux
2.6.32-21-server'' --class ubuntu --class gnu-linux --class gnu --class
os {	recordfail	insmod ext2	set root=''(hd0,1)''	search
--no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e	linux
/boot/vmlinuz-2.6.32-21-server root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro
  quiet	initrd
	/boot/initrd.img-2.6.32-21-server}menuentry ''Ubuntu, with Linux
2.6.32-21-server (recovery mode)'' --class ubuntu --class gnu-linux
--class gnu --class os {	recordfail	insmod ext2	set
root=''(hd0,1)''	search --no-floppy --fs-uuid --set
a2f031e5-cdce-440f-a736-64fd0e4ec43e	echo	''Loading Linux
2.6.32-21-server ...''	linux	/boot/vmlinuz-2.6.32-21-server
 root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro single 	echo
''Loading initial ramdisk ...''	initrd
/boot/initrd.img-2.6.32-21-server}### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_memtest86+ ###menuentry "Memory test
(memtest86+)" {	insmod ext2	set root=''(hd0,1)''	search
--no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e
	linux16	/boot/memtest86+.bin}menuentry "Memory test (memtest86+, serial
console 115200)" {	insmod ext2	set root=''(hd0,1)''	search
--no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e	linux16
/boot/memtest86+.bin console=ttyS0,115200n8}### END /etc/grub.d/20_memtest86+
###
### BEGIN /etc/grub.d/30_os-prober ###### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom #### This file provides an easy way to add
custom
 menu entries.  Simply type the# menu entries you want to add after this
comment.  Be careful not to change# the ''exec tail'' line
above.menuentry "Xen 4 / Ubuntu 10.04 kernel 2.6.32.15" {insmod
ext2set root=''(hd0,1)''multiboot (hd0,1)/boot/xen.gz
dom0_mem=1024M loglvl=all guest_loglvl=allmodule (hd0,1)/boot/vmlinuz-2.6.32.15
root=/dev/sda1 ro nomodesetmodule (hd0,1)/boot/initrd.img-2.6.32.15}#menuentry
"Xen 4 / Ubuntu 10.04 kernel 2.6.32.15a" {#insmod ext2#set
root=''(hd0,1)''#multiboot (hd0,1)/boot/xen.gz
dummy=dummy#module (hd0,1)/boot/vmlinuz-2.6.32.15 dummy=dummy nopat
root=/dev/sdc2 ro console=tty0 #module
(hd0,1)/boot/initrd.img-2.6.32.15#}#menuentry "Xen 4 / Ubuntu 10.04 kernel
2.6.32.15b" {#insmod ext2#set
 root=''(hd0,1)''#multiboot (hd0,1)/boot/xen-4.0.1-rc4-pre.gz
dummy=dummy#module (hd0,1)/boot/vmlinuz-2.6.32.15 dummy=dummy nopat
root=/dev/sdc2 ro console=tty0 #module
(hd0,1)/boot/initrd.img-2.6.32.15#}menuentry "Xen 4 / Ubuntu 10.04 kernel
2.6.32.15 config 2" {insmod ext2set
root=''(hd0,1)''multiboot (hd0,1)/boot/xen.gz dummy=dummymodule
(hd0,1)/boot/vmlinuz-2.6.32.15 dummy=dummy nopat root=/dev/sdb5 ro
console=tty0module (hd0,1)/boot/initrd.img-2.6.32.15}### END
/etc/grub.d/40_custom ###
 Murray Thomson
From: Boris Derzhavets <bderzhavets@yahoo.com>
To: xen-users@lists.xensource.com; Murray Thomson
<murray_thomson7788@yahoo.com>
Sent: Tue, July 13, 2010 9:54:49 AM
Subject: Re: [Xen-users] Xen 4 Ubuntu Lucid panics
1. I would suggest you to obtain a serial log and escalate the problem to
xen-devel.
2. Could you post yours /usr/src/linux-2.6-xen/.config ( gzipped)
,/boot/grub/grub.cfg,
"df -h" output.
Boris.
--- On Tue, 7/13/10, Murray Thomson <murray_thomson7788@yahoo.com> wrote:
From: Murray Thomson
 <murray_thomson7788@yahoo.com>
Subject: [Xen-users] Xen 4 Ubuntu Lucid panics
To: xen-users@lists.xensource.com
Date: Tuesday, July 13, 2010, 9:41 AM
I have tried 4 time unsuccessfully to install Xen 4 on Ubuntu Lucid (10.4) 64
bit version using the
 tutorial
at http://bderzhavets.wordpress.com/2010/04/24/set-up-ubuntu-10-04-server-pv-domu-at-xen-4-0-dom0-pvops-2-6-32-10-kernel-dom0-on-top-of-ubuntu-10-04-server/
on a Lenovo thinkcentre workstation.
When I boot I get a kernel panic. If I boot the Linux kernel that I compiled
using the tutorial on it''s own it boots fine. 
Is the likely cause hardware? is there a common error made in this tutorial that
would
 cause a panic on boot. 
Murray
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
      
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
      
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
I would also disable UUID via /etc/default/grub
# Uncomment if you don''t want GRUB to pass "root=UUID=xxx"
parameter to Linux
GRUB_DISABLE_LINUX_UUID=true
and
# update-grub
Not sure it''s required , but cannot make things worse.
Just always disabled UUID for Xen Instances on Lucid,Karmic (Grub2)
Boris.
--- On Tue, 7/13/10, Murray Thomson <murray_thomson7788@yahoo.com> wrote:
From: Murray Thomson <murray_thomson7788@yahoo.com>
Subject: Re: [Xen-users] Xen 4 Ubuntu Lucid panics
To: "Boris Derzhavets" <bderzhavets@yahoo.com>,
xen-users@lists.xensource.com
Date: Tuesday, July 13, 2010, 10:52 AM
grub.cfg
## DO NOT EDIT THIS FILE## It is automatically generated by
/usr/sbin/grub-mkconfig using templates# from /etc/grub.d and settings from
/etc/default/grub#
### BEGIN /etc/grub.d/00_header ###if [ -s $prefix/grubenv ];
then  load_envfiset default="2"if [ ${prev_saved_entry} ]; then  set
saved_entry=${prev_saved_entry}  save_env saved_entry  set
prev_saved_entry=  save_env prev_saved_entry  set boot_once=truefi
function savedefault {  if [
 -z ${boot_once} ]; then    saved_entry=${chosen}    save_env saved_entry  fi}
function recordfail {  set recordfail=1  if [ -n ${have_grubenv} ]; then if [ -z
${boot_once} ]; then save_env recordfail; fi; fi}insmod ext2set
root=''(hd0,1)''search --no-floppy --fs-uuid --set
a2f031e5-cdce-440f-a736-64fd0e4ec43eif loadfont /usr/share/grub/unicode.pf2 ;
then  set gfxmode=640x480  insmod gfxterm  insmod vbe  if terminal_output
gfxterm ; then true ; else    # For backward compatibility with versions of
terminal.mod that don''t    # understand terminal_output    terminal
 gfxterm  fifiinsmod ext2set root=''(hd0,1)''search --no-floppy
--fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43eset
locale_dir=($root)/boot/grub/localeset lang=eninsmod gettextif [ ${recordfail} =
1 ]; then  set timeout=-1else  set timeout=10fi### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###set menu_color_normal=white/blackset
menu_color_highlight=black/light-gray### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###menuentry ''Ubuntu, with Linux
2.6.32.15'' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail	insmod ext2	set root=''(hd0,1)''	search --no-floppy
--fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e	linux
/boot/vmlinuz-2.6.32.15 root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro  
quiet	initrd	/boot/initrd.img-2.6.32.15}menuentry ''Ubuntu, with Linux
2.6.32.15 (recovery mode)'' --class ubuntu --class gnu-linux --class gnu
--class os {	recordfail	insmod
 ext2	set root=''(hd0,1)''	search --no-floppy --fs-uuid --set
a2f031e5-cdce-440f-a736-64fd0e4ec43e	echo	''Loading Linux 2.6.32.15
...''	linux	/boot/vmlinuz-2.6.32.15
root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro single 	echo	''Loading
initial ramdisk ...''	initrd
	/boot/initrd.img-2.6.32.15}menuentry ''Ubuntu, with Linux
2.6.32-21-server'' --class ubuntu --class gnu-linux --class gnu --class
os {	recordfail	insmod ext2	set root=''(hd0,1)''	search
--no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e	linux
/boot/vmlinuz-2.6.32-21-server root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro
  quiet	initrd
	/boot/initrd.img-2.6.32-21-server}menuentry ''Ubuntu, with Linux
2.6.32-21-server (recovery mode)'' --class ubuntu --class gnu-linux
--class gnu --class os {	recordfail	insmod ext2	set
root=''(hd0,1)''	search --no-floppy --fs-uuid --set
a2f031e5-cdce-440f-a736-64fd0e4ec43e	echo	''Loading Linux
2.6.32-21-server ...''	linux	/boot/vmlinuz-2.6.32-21-server
 root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro single 	echo
''Loading initial ramdisk ...''	initrd
/boot/initrd.img-2.6.32-21-server}### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_memtest86+ ###menuentry "Memory test
(memtest86+)" {	insmod ext2	set root=''(hd0,1)''	search
--no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e
	linux16	/boot/memtest86+.bin}menuentry "Memory test (memtest86+, serial
console 115200)" {	insmod ext2	set root=''(hd0,1)''	search
--no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e	linux16
/boot/memtest86+.bin console=ttyS0,115200n8}### END /etc/grub.d/20_memtest86+
###
### BEGIN /etc/grub.d/30_os-prober ###### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom #### This file provides an easy way to add
custom
 menu entries.  Simply type the# menu entries you want to add after this
comment.  Be careful not to change# the ''exec tail'' line
above.menuentry "Xen 4 / Ubuntu 10.04 kernel 2.6.32.15" {insmod
ext2set root=''(hd0,1)''multiboot (hd0,1)/boot/xen.gz
dom0_mem=1024M loglvl=all guest_loglvl=allmodule (hd0,1)/boot/vmlinuz-2.6.32.15
root=/dev/sda1 ro nomodesetmodule (hd0,1)/boot/initrd.img-2.6.32.15}#menuentry
"Xen 4 / Ubuntu 10.04 kernel 2.6.32.15a" {#insmod ext2#set
root=''(hd0,1)''#multiboot (hd0,1)/boot/xen.gz
dummy=dummy#module (hd0,1)/boot/vmlinuz-2.6.32.15 dummy=dummy nopat
root=/dev/sdc2 ro console=tty0 #module
(hd0,1)/boot/initrd.img-2.6.32.15#}#menuentry "Xen 4 / Ubuntu 10.04 kernel
2.6.32.15b" {#insmod ext2#set
 root=''(hd0,1)''#multiboot (hd0,1)/boot/xen-4.0.1-rc4-pre.gz
dummy=dummy#module (hd0,1)/boot/vmlinuz-2.6.32.15 dummy=dummy nopat
root=/dev/sdc2 ro console=tty0 #module
(hd0,1)/boot/initrd.img-2.6.32.15#}menuentry "Xen 4 / Ubuntu 10.04 kernel
2.6.32.15 config 2" {insmod ext2set
root=''(hd0,1)''multiboot (hd0,1)/boot/xen.gz dummy=dummymodule
(hd0,1)/boot/vmlinuz-2.6.32.15 dummy=dummy nopat root=/dev/sdb5 ro
console=tty0module (hd0,1)/boot/initrd.img-2.6.32.15}### END
/etc/grub.d/40_custom ###
 Murray Thomson
From: Boris Derzhavets <bderzhavets@yahoo.com>
To: xen-users@lists.xensource.com; Murray Thomson
<murray_thomson7788@yahoo.com>
Sent: Tue, July 13, 2010 9:54:49 AM
Subject: Re: [Xen-users] Xen 4 Ubuntu Lucid panics
1. I would suggest you to obtain a serial log and escalate the problem to
xen-devel.
2. Could you post yours /usr/src/linux-2.6-xen/.config ( gzipped)
,/boot/grub/grub.cfg,
"df -h" output.
Boris.
--- On Tue, 7/13/10, Murray Thomson <murray_thomson7788@yahoo.com> wrote:
From: Murray Thomson
 <murray_thomson7788@yahoo.com>
Subject: [Xen-users] Xen 4 Ubuntu Lucid panics
To: xen-users@lists.xensource.com
Date: Tuesday, July 13, 2010, 9:41 AM
I have tried 4 time unsuccessfully to install Xen 4 on Ubuntu Lucid (10.4) 64
bit version using the
 tutorial
at http://bderzhavets.wordpress.com/2010/04/24/set-up-ubuntu-10-04-server-pv-domu-at-xen-4-0-dom0-pvops-2-6-32-10-kernel-dom0-on-top-of-ubuntu-10-04-server/
on a Lenovo thinkcentre workstation.
When I boot I get a kernel panic. If I boot the Linux kernel that I compiled
using the tutorial on it''s own it boots fine. 
Is the likely cause hardware? is there a common error made in this tutorial that
would
 cause a panic on boot. 
Murray
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
      
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
      
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
(! 211)-> df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1             286G   13G  258G   5% /
none                  1.5G  196K  1.5G   1% /dev
none                  1.5G     0  1.5G   0% /dev/shm
none                  1.5G   68K  1.5G   1% /var/run
none                  1.5G     0  1.5G   0% /var/lock
none                  1.5G     0  1.5G   0% /lib/init/rw
grub entry:
Tried a bunch of different configs. This is the one I am using.
menuentry "Xen 4 / Ubuntu 10.04 kernel 2.6.32.15" {
insmod ext2
set root=''(hd0,1)''
multiboot (hd0,1)/boot/xen.gz dom0_mem=1024M loglvl=all guest_loglvl=all
module (hd0,1)/boot/vmlinuz-2.6.32.15 root=/dev/sda1 ro nomodeset
module (hd0,1)/boot/initrd.img-2.6.32.15
}
 Murray Thomson
________________________________
From: Boris Derzhavets <bderzhavets@yahoo.com>
To: xen-users@lists.xensource.com; Murray Thomson
<murray_thomson7788@yahoo.com>
Sent: Tue, July 13, 2010 12:31:09 PM
Subject: Re: [Xen-users] Xen 4 Ubuntu Lucid panics
1. First 
Yours tuning backends ( right ?)
                 <M> Xen /dev/xen/evtchn 
device                                                        
                  [*] Backend driver  
support                                           
                  < >   Xen backend network 
device                                    
                  < >   Block-device backend  
driver                                                      
                  < >   Block-device tap backend 
driver                                                  
                  <*>   PCI-device backend  
driver                                                        
                          PCI Backend Mode (Virtual PCI)  
--->                                           
                  [ ]     PCI Backend  
Debugging                                                          
                 <M> Xen 
filesystem                                                                     
                 [*]   Create compatibility mount point 
/proc/xen                                       
                 [*] Create xen entries under 
/sys/hypervisor                                           
                 < > xen platform pci device  
driver                                                     
                 < > userspace grant access device driver  
Per tutorial :-
  <*> Xen /dev/xen/evtchn 
device                                                        
                  [*] Backend driver 
support                                           
                  <*>   Xen backend network 
device                                    
                  <*>   Block-device backend  
driver                                                      
                  <*>   Block-device tap backend 
driver                                                  
                  <*>   PCI-device backend  
driver                                                        
                          PCI Backend Mode (Virtual PCI)  
--->                                           
                  [ ]     PCI Backend  
Debugging                                                          
                 <*> Xen 
filesystem                                                                     
                 [*]   Create compatibility mount point 
/proc/xen                                       
                 [*] Create xen entries under 
/sys/hypervisor                                           
                 <*> xen platform pci device  
driver                                                     
                 <*> userspace grant access device driver 
Now 
# diff -auN config.received config.071310  > conf.patch
# cat conf.patch
. . . . . .
-# CONFIG_XEN_NETDEV_BACKEND is not set
-# CONFIG_XEN_BLKDEV_BACKEND is not set
-# CONFIG_XEN_BLKDEV_TAP is not set
+CONFIG_XEN_NETDEV_BACKEND=y
+CONFIG_XEN_BLKDEV_BACKEND=y
+CONFIG_XEN_BLKDEV_TAP=y
+CONFIG_XEN_BLKBACK_PAGEMAP=y
I attached mine config and config.patch.
Make diff one more time on your box and watch errors for yourself
The  best option - just use config attached after git pull ( 2.6.32.16 )
2. Second.
Please submit your working grub entry for Xen (just one)  and "df  -h"
for
corresponding vanilla entry. /dev/sdb5 and (hd0,1) seem strange to me.
Boris.
--- On Tue, 7/13/10, Murray Thomson <murray_thomson7788@yahoo.com> wrote:
>From: Murray Thomson <murray_thomson7788@yahoo.com>
>Subject: Re: [Xen-users] Xen 4 Ubuntu Lucid panics
>To: "Boris Derzhavets" <bderzhavets@yahoo.com>,
xen-users@lists.xensource.com
>Date: Tuesday, July 13, 2010, 10:52 AM
>
>
>grub.cfg
>
>
>#
># DO NOT EDIT THIS  FILE
>#
># It is automatically generated by /usr/sbin/grub-mkconfig using templates
># from /etc/grub.d and settings from /etc/default/grub
>#
>
>
>### BEGIN /etc/grub.d/00_header ###
>if [ -s $prefix/grubenv ]; then
>  load_env
>fi
>set default="2"
>if [ ${prev_saved_entry} ]; then
>  set saved_entry=${prev_saved_entry}
>  save_env saved_entry
>  set prev_saved_entry>  save_env prev_saved_entry
>  set boot_once=true
>fi
>
>
>function savedefault {
>  if [  -z ${boot_once} ]; then
>    saved_entry=${chosen}
>    save_env saved_entry
>  fi
>}
>
>
>function recordfail {
>  set recordfail=1
>  if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env 
>recordfail; fi; fi
>}
>insmod ext2
>set root=''(hd0,1)''
>search --no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e
>if loadfont /usr/share/grub/unicode.pf2 ; then
>  set gfxmode=640x480
>  insmod gfxterm
>  insmod vbe
>  if terminal_output gfxterm ; then true ; else
>    # For backward compatibility with versions of terminal.mod that
don''t
>    # understand terminal_output
>    terminal  gfxterm
>  fi
>fi
>insmod ext2
>set root=''(hd0,1)''
>search --no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e
>set locale_dir=($root)/boot/grub/locale
>set lang=en
>insmod gettext
>if [ ${recordfail} = 1 ]; then
>  set timeout=-1
>else
>  set timeout=10
>fi
>### END /etc/grub.d/00_header ###
>
>
>### BEGIN /etc/grub.d/05_debian_theme ###
>set menu_color_normal=white/black
>set menu_color_highlight=black/light-gray
>### END /etc/grub.d/05_debian_theme ###
>
>
>### BEGIN /etc/grub.d/10_linux ###
>menuentry ''Ubuntu, with Linux 2.6.32.15'' --class ubuntu
--class gnu-linux
>--class gnu --class os {
>recordfail
>insmod ext2
>set root=''(hd0,1)''
>search --no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e
>linux/boot/vmlinuz-2.6.32.15 root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e
ro
>quiet
>initrd/boot/initrd.img-2.6.32.15
>}
>menuentry ''Ubuntu, with Linux 2.6.32.15 (recovery mode)''
--class ubuntu --class
>gnu-linux --class gnu --class os {
>recordfail
>insmod  ext2
>set root=''(hd0,1)''
>search --no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e
>echo''Loading Linux 2.6.32.15 ...''
>linux/boot/vmlinuz-2.6.32.15 root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e
ro
>single 
>echo''Loading initial ramdisk ...''
>initrd
>/boot/initrd.img-2.6.32.15
>}
>menuentry ''Ubuntu, with Linux 2.6.32-21-server'' --class
ubuntu --class gnu-linux
>--class gnu --class os {
>recordfail
>insmod ext2
>set root=''(hd0,1)''
>search --no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e
>linux/boot/vmlinuz-2.6.32-21-server 
>root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro   quiet
>initrd
>/boot/initrd.img-2.6.32-21-server
>}
>menuentry ''Ubuntu, with Linux 2.6.32-21-server (recovery
mode)'' --class ubuntu
>--class gnu-linux --class gnu --class os {
>recordfail
>insmod ext2
>set root=''(hd0,1)''
>search --no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e
>echo''Loading Linux 2.6.32-21-server ...''
>linux/boot/vmlinuz-2.6.32-21-server  
>root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro single 
>echo''Loading initial ramdisk ...''
>initrd/boot/initrd.img-2.6.32-21-server
>}
>### END /etc/grub.d/10_linux ###
>
>
>### BEGIN /etc/grub.d/20_memtest86+ ###
>menuentry "Memory test (memtest86+)" {
>insmod ext2
>set root=''(hd0,1)''
>search --no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e
>
>linux16/boot/memtest86+.bin
>}
>menuentry "Memory test (memtest86+, serial console 115200)" {
>insmod ext2
>set root=''(hd0,1)''
>search --no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e
>linux16/boot/memtest86+.bin console=ttyS0,115200n8
>}
>### END /etc/grub.d/20_memtest86+ ###
>
>
>### BEGIN /etc/grub.d/30_os-prober ###
>### END /etc/grub.d/30_os-prober ###
>
>
>### BEGIN /etc/grub.d/40_custom ###
># This file provides an  easy way to add custom  menu entries.  Simply type
the
># menu entries you want to add after this comment.  Be careful not to change
># the ''exec tail'' line above.
>menuentry "Xen 4 / Ubuntu 10.04 kernel 2.6.32.15" {
>insmod ext2
>set root=''(hd0,1)''
>multiboot (hd0,1)/boot/xen.gz dom0_mem=1024M loglvl=all guest_loglvl=all
>module (hd0,1)/boot/vmlinuz-2.6.32.15 root=/dev/sda1 ro nomodeset
>module (hd0,1)/boot/initrd.img-2.6.32.15
>}
>#menuentry "Xen 4 / Ubuntu 10.04 kernel 2.6.32.15a" {
>#insmod ext2
>#set root=''(hd0,1)''
>#multiboot (hd0,1)/boot/xen.gz dummy=dummy
>#module (hd0,1)/boot/vmlinuz-2.6.32.15 dummy=dummy nopat root=/dev/sdc2 ro 
>console=tty0 
>#module (hd0,1)/boot/initrd.img-2.6.32.15
>#}
>#menuentry "Xen 4 / Ubuntu 10.04 kernel 2.6.32.15b" {
>#insmod ext2
>#set  root=''(hd0,1)''
>#multiboot (hd0,1)/boot/xen-4.0.1-rc4-pre.gz dummy=dummy
>#module (hd0,1)/boot/vmlinuz-2.6.32.15 dummy=dummy nopat root=/dev/sdc2 ro 
>console=tty0 
>#module (hd0,1)/boot/initrd.img-2.6.32.15
>#}
>menuentry "Xen 4 / Ubuntu 10.04 kernel 2.6.32.15 config 2" {
>insmod ext2
>set root=''(hd0,1)''
>multiboot (hd0,1)/boot/xen.gz dummy=dummy
>module (hd0,1)/boot/vmlinuz-2.6.32.15 dummy=dummy nopat root=/dev/sdb5 ro 
>console=tty0
>module (hd0,1)/boot/initrd.img-2.6.32.15
>}
>### END /etc/grub.d/40_custom ###
>
>
>
>
>
> Murray Thomson
>
>
>
>
>
________________________________
From: Boris Derzhavets <bderzhavets@yahoo.com>>To: xen-users@lists.xensource.com; Murray Thomson 
<murray_thomson7788@yahoo.com>>Sent: Tue, July 13, 2010 9:54:49 AM
>Subject: Re: [Xen-users] Xen 4 Ubuntu Lucid panics
>
>
>1. I would suggest you to obtain a serial log and escalate the problem to 
>xen-devel.
>2. Could you post yours /usr/src/linux-2.6-xen/.config ( gzipped) 
>,/boot/grub/grub.cfg,
>"df -h" output.
>
>Boris.
>
>--- On Tue, 7/13/10, Murray Thomson <murray_thomson7788@yahoo.com>
wrote:
>
>
>>From: Murray Thomson  <murray_thomson7788@yahoo.com>
>>Subject: [Xen-users] Xen 4 Ubuntu Lucid panics
>>To: xen-users@lists.xensource.com
>>Date: Tuesday, July 13, 2010, 9:41 AM
>>
>>
>>I have tried 4 time unsuccessfully to install Xen 4 on Ubuntu Lucid
(10.4) 64
>>bit version using the  tutorial at 
>>http://bderzhavets.wordpress.com/2010/04/24/set-up-ubuntu-10-04-server-pv-domu-at-xen-4-0-dom0-pvops-2-6-32-10-kernel-dom0-on-top-of-ubuntu-10-04-server/
>> on a Lenovo thinkcentre workstation.
>>
>>
>>When I boot I get a kernel panic. If I boot the Linux kernel that I
compiled
>>using the tutorial on it''s own it boots fine. 
>>
>>
>>Is the likely cause hardware? is there a common error made in this
tutorial that
>>would  cause a panic on boot. 
>>
>>
>>Murray
>>
>>-----Inline Attachment Follows-----
>>
>>
>>_______________________________________________
>>Xen-users mailing list
>>Xen-users@lists.xensource.com
>>http://lists.xensource.com/xen-users 
>
>
>-----Inline Attachment Follows-----
>
>
>_______________________________________________
>Xen-users mailing list
>Xen-users@lists.xensource.com
>http://lists.xensource.com/xen-users 
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Per "howto" create entry into /boot/grub/grub.cfg:-
menuentry "Xen 4 / Ubuntu 10.04 kernel 
2.6.32.16-xen" {insmod ext2set root=''(hd0,1)''multiboot
 (hd0,1)/boot/xen.gz dummy=dummymodule (hd0,1)/boot/vmlinuz-2.6.32.16-xen
dummy=dummy
root=/dev/sda1 ro nopat console=tty0
module (hd0,1)/boot/initrd.img-2.6.32.16-xen}
Entry dummy=dummy is important at kernel line. It was skipped.
It causes a crash. Build 2.6.32.16 kernel with submitted config (64 bit)  :-
# cd /usr/src/linux-2.6-xen
# git pull
# cp ../config.071310   .config
# aptitude install kernel-package fakeroot
# export CONCURRENCY_LEVEL=(number_of_cores) +1
# make-kpkg clean
# fakeroot make-kpkg --initrd --append-to-version=-xen     kernel-image 
kernel-headers
# update-initramfs -c -k 2.6.32.16-xen
and see what happens
Boris.
--- On Tue, 7/13/10, Murray Thomson <murray_thomson7788@yahoo.com> wrote:
From: Murray Thomson <murray_thomson7788@yahoo.com>
Subject: Re: [Xen-users] Xen 4 Ubuntu Lucid panics
To: "Boris Derzhavets" <bderzhavets@yahoo.com>,
xen-users@lists.xensource.com
Date: Tuesday, July 13, 2010, 3:20 PM
(! 211)-> df -hFilesystem            Size  Used Avail Use% Mounted
on/dev/sda1             286G   13G  258G   5% /none                  1.5G  196K
 1.5G   1% /devnone                  1.5G     0  1.5G   0% /dev/shmnone        
         1.5G   68K  1.5G   1% /var/runnone                  1.5G     0  1.5G  
0% /var/locknone                  1.5G     0  1.5G   0% /lib/init/rw
grub entry:
Tried a bunch of different configs. This is the one I am using.
menuentry "Xen 4 / Ubuntu 10.04 kernel 2.6.32.15" {insmod ext2set
root=''(hd0,1)''multiboot
 (hd0,1)/boot/xen.gz dom0_mem=1024M loglvl=all guest_loglvl=allmodule
(hd0,1)/boot/vmlinuz-2.6.32.15 root=/dev/sda1 ro nomodesetmodule
(hd0,1)/boot/initrd.img-2.6.32.15}
 Murray Thomson
From: Boris Derzhavets <bderzhavets@yahoo.com>
To: xen-users@lists.xensource.com;
 Murray Thomson <murray_thomson7788@yahoo.com>
Sent: Tue, July 13, 2010 12:31:09 PM
Subject: Re: [Xen-users] Xen 4 Ubuntu Lucid panics
1. First 
Yours tuning backends ( right ?)
                 <M> Xen /dev/xen/evtchn
device                                                       
 
                  [*] Backend driver
 support                                           
                  < >   Xen backend network
device                                   
                  < >   Block-device backend
 driver                                                      
                  < >   Block-device tap backend
driver                                                 
                  <*>   PCI-device backend
 driver                                                        
                          PCI Backend Mode (Virtual PCI) 
--->                                          
                  [ ]     PCI Backend
 Debugging                                                          
                 <M> Xen
filesystem                                                                    
 
                 [*]   Create compatibility mount point
/proc/xen                                      
                 [*] Create xen entries under
/sys/hypervisor                                          
                 < > xen platform pci device
 driver                                                     
                 < > userspace grant access device driver  
Per tutorial :-
  <*> Xen /dev/xen/evtchn
device                                                       
 
                  [*] Backend driver
support                                          
                  <*>   Xen backend network
device                                   
                  <*>   Block-device backend
 driver                                                      
                  <*>   Block-device tap backend
driver                                                 
                  <*>   PCI-device backend
 driver                                                        
                          PCI Backend Mode (Virtual PCI) 
--->                                          
                  [ ]     PCI Backend
 Debugging                                                          
                 <*> Xen
filesystem                                                                    
 
                 [*]   Create compatibility mount point
/proc/xen                                      
                 [*] Create xen entries under
/sys/hypervisor                                          
                 <*> xen platform pci device
 driver                                                     
                 <*> userspace grant access device driver 
Now 
# diff -auN config.received config.071310  > conf.patch
# cat conf.patch
. . . . . .
-# CONFIG_XEN_NETDEV_BACKEND is not set
-# CONFIG_XEN_BLKDEV_BACKEND is not set
-# CONFIG_XEN_BLKDEV_TAP is not set
+CONFIG_XEN_NETDEV_BACKEND=y
+CONFIG_XEN_BLKDEV_BACKEND=y
+CONFIG_XEN_BLKDEV_TAP=y
+CONFIG_XEN_BLKBACK_PAGEMAP=y
I attached mine config and config.patch.
Make diff one more time on your box and watch errors for yourself
The
 best option - just use config attached after git pull ( 2.6.32.16 )
2. Second.
Please submit your working grub entry for Xen (just one)  and "df  -h"
for corresponding vanilla entry. /dev/sdb5 and (hd0,1) seem strange to me.
Boris.
--- On Tue, 7/13/10, Murray Thomson <murray_thomson7788@yahoo.com> wrote:
From: Murray Thomson <murray_thomson7788@yahoo.com>
Subject: Re: [Xen-users] Xen 4 Ubuntu Lucid panics
To: "Boris Derzhavets" <bderzhavets@yahoo.com>,
xen-users@lists.xensource.com
Date: Tuesday, July 13, 2010, 10:52 AM
grub.cfg
## DO NOT EDIT THIS
 FILE## It is automatically generated by /usr/sbin/grub-mkconfig using
templates# from /etc/grub.d and settings from /etc/default/grub#
### BEGIN /etc/grub.d/00_header ###if [ -s $prefix/grubenv ];
then  load_envfiset default="2"if [ ${prev_saved_entry} ]; then  set
saved_entry=${prev_saved_entry}  save_env saved_entry  set
prev_saved_entry=  save_env prev_saved_entry  set boot_once=truefi
function savedefault {  if [
 -z ${boot_once} ]; then    saved_entry=${chosen}    save_env saved_entry  fi}
function recordfail {  set recordfail=1  if [ -n ${have_grubenv} ]; then if [ -z
${boot_once} ]; then save_env recordfail; fi; fi}insmod ext2set
root=''(hd0,1)''search --no-floppy --fs-uuid --set
a2f031e5-cdce-440f-a736-64fd0e4ec43eif loadfont /usr/share/grub/unicode.pf2 ;
then  set gfxmode=640x480  insmod gfxterm  insmod vbe  if terminal_output
gfxterm ; then true ; else    # For backward compatibility with versions of
terminal.mod that don''t    # understand terminal_output    terminal
 gfxterm  fifiinsmod ext2set root=''(hd0,1)''search --no-floppy
--fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43eset
locale_dir=($root)/boot/grub/localeset lang=eninsmod gettextif [ ${recordfail} =
1 ]; then  set timeout=-1else  set timeout=10fi### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###set menu_color_normal=white/blackset
menu_color_highlight=black/light-gray### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###menuentry ''Ubuntu, with Linux
2.6.32.15'' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail	insmod ext2	set root=''(hd0,1)''	search --no-floppy
--fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e	linux
/boot/vmlinuz-2.6.32.15 root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro  
quiet	initrd	/boot/initrd.img-2.6.32.15}menuentry ''Ubuntu, with Linux
2.6.32.15 (recovery mode)'' --class ubuntu --class gnu-linux --class gnu
--class os {	recordfail
	insmod
 ext2	set root=''(hd0,1)''	search --no-floppy --fs-uuid --set
a2f031e5-cdce-440f-a736-64fd0e4ec43e	echo	''Loading Linux 2.6.32.15
...''	linux	/boot/vmlinuz-2.6.32.15
root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro single 	echo	''Loading
initial ramdisk ...''	initrd
	/boot/initrd.img-2.6.32.15}menuentry ''Ubuntu, with Linux
2.6.32-21-server'' --class ubuntu --class gnu-linux --class gnu --class
os {	recordfail	insmod ext2	set root=''(hd0,1)''	search
--no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e	linux
/boot/vmlinuz-2.6.32-21-server root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro
  quiet	initrd
	/boot/initrd.img-2.6.32-21-server}menuentry ''Ubuntu, with Linux
2.6.32-21-server (recovery mode)'' --class ubuntu --class gnu-linux
--class gnu --class os {	recordfail	insmod ext2	set
root=''(hd0,1)''	search --no-floppy --fs-uuid --set
a2f031e5-cdce-440f-a736-64fd0e4ec43e	echo	''Loading Linux
2.6.32-21-server ...''	linux	/boot/vmlinuz-2.6.32-21-server
 root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro single 	echo
''Loading initial ramdisk ...''	initrd
/boot/initrd.img-2.6.32-21-server}### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_memtest86+ ###menuentry "Memory test
(memtest86+)" {	insmod ext2	set root=''(hd0,1)''	search
--no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e
	linux16	/boot/memtest86+.bin}menuentry "Memory test (memtest86+, serial
console 115200)" {	insmod ext2	set root=''(hd0,1)''	search
--no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e	linux16
/boot/memtest86+.bin console=ttyS0,115200n8}### END /etc/grub.d/20_memtest86+
###
### BEGIN /etc/grub.d/30_os-prober ###### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom #### This file
 provides an
 easy way to add custom
 menu entries.  Simply type the# menu entries you want to add after this
comment.  Be careful not to change# the ''exec tail'' line
above.menuentry "Xen 4 / Ubuntu 10.04 kernel 2.6.32.15" {insmod
ext2set root=''(hd0,1)''multiboot (hd0,1)/boot/xen.gz
dom0_mem=1024M loglvl=all guest_loglvl=allmodule (hd0,1)/boot/vmlinuz-2.6.32.15
root=/dev/sda1 ro nomodesetmodule (hd0,1)/boot/initrd.img-2.6.32.15}#menuentry
"Xen 4 / Ubuntu 10.04 kernel 2.6.32.15a" {#insmod ext2#set
root=''(hd0,1)''#multiboot (hd0,1)/boot/xen.gz
dummy=dummy#module (hd0,1)/boot/vmlinuz-2.6.32.15 dummy=dummy nopat
root=/dev/sdc2 ro console=tty0 #module
(hd0,1)/boot/initrd.img-2.6.32.15#}#menuentry "Xen 4 / Ubuntu 10.04 kernel
2.6.32.15b" {#insmod ext2#set
 root=''(hd0,1)''#multiboot (hd0,1)/boot/xen-4.0.1-rc4-pre.gz
dummy=dummy#module (hd0,1)/boot/vmlinuz-2.6.32.15 dummy=dummy nopat
root=/dev/sdc2 ro console=tty0 #module
(hd0,1)/boot/initrd.img-2.6.32.15#}menuentry "Xen 4 / Ubuntu 10.04 kernel
2.6.32.15 config 2" {insmod ext2set
root=''(hd0,1)''multiboot (hd0,1)/boot/xen.gz dummy=dummymodule
(hd0,1)/boot/vmlinuz-2.6.32.15 dummy=dummy nopat root=/dev/sdb5 ro
console=tty0module (hd0,1)/boot/initrd.img-2.6.32.15}### END
/etc/grub.d/40_custom ###
 Murray Thomson
From: Boris Derzhavets <bderzhavets@yahoo.com>
To: xen-users@lists.xensource.com; Murray Thomson
<murray_thomson7788@yahoo.com>
Sent: Tue, July 13, 2010 9:54:49 AM
Subject: Re: [Xen-users] Xen 4 Ubuntu Lucid panics
1. I would suggest you to obtain a serial log and escalate the problem to
xen-devel.
2. Could you post yours /usr/src/linux-2.6-xen/.config ( gzipped)
,/boot/grub/grub.cfg,
"df -h" output.
Boris.
--- On Tue, 7/13/10, Murray Thomson <murray_thomson7788@yahoo.com> wrote:
From: Murray Thomson
 <murray_thomson7788@yahoo.com>
Subject: [Xen-users] Xen 4 Ubuntu Lucid panics
To: xen-users@lists.xensource.com
Date: Tuesday, July 13, 2010, 9:41 AM
I have tried 4 time unsuccessfully to install Xen 4 on Ubuntu Lucid (10.4) 64
bit version using the
 tutorial
at http://bderzhavets.wordpress.com/2010/04/24/set-up-ubuntu-10-04-server-pv-domu-at-xen-4-0-dom0-pvops-2-6-32-10-kernel-dom0-on-top-of-ubuntu-10-04-server/
on a Lenovo thinkcentre workstation.
When I boot I get a kernel panic. If I boot the Linux kernel that I compiled
using the tutorial on it''s own it boots fine. 
Is the likely cause hardware? is there a common error made in this tutorial that
would
 cause a panic on boot. 
Murray
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
      
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
      
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
      
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Boris Derzhavets
2010-Jul-13  20:05 UTC
Re: [Xen-users] Xen 4 Ubuntu Lucid panics (HTML typos fixed)
Tried to fix "CR" coming from HTML cat and paste
Create entry like this :-
menuentry "Xen 4 / Ubuntu 10.04 kernel 2.6.32.16-xen" {
insmod ext2
set root=''(hd0,1)''
multiboot (hd0,1)/boot/xen.gz dummy=dummy
module (hd0,1)/boot/vmlinuz-2.6.32.16-xen dummy=dummy root=/dev/sda1 ro nopat
console=tty0
module (hd0,1)/boot/initrd.img-2.6.32.16-xen
}
Entry dummy=dummy is important at kernel line. It was skipped.
It causes a crash. Build 2.6.32.16 kernel with submitted config (64 bit)  :-
# cd /usr/src/linux-2.6-xen
# git pull
# cp ../config.071310   .config
# aptitude install kernel-package fakeroot
# export CONCURRENCY_LEVEL=(number_of_cores) +1
# make-kpkg clean
# fakeroot make-kpkg --initrd --append-to-version=-xen kernel-image
kernel-headers
# update-initramfs -c -k 2.6.32.16-xen
and see what happens
Boris.
--- On Tue, 7/13/10, Murray Thomson <murray_thomson7788@yahoo.com> wrote:
From: Murray Thomson <murray_thomson7788@yahoo.com>
Subject: Re: [Xen-users] Xen 4 Ubuntu Lucid panics
To: "Boris Derzhavets" <bderzhavets@yahoo.com>,
xen-users@lists.xensource.com
Date: Tuesday, July 13, 2010, 3:20 PM
(! 211)-> df -hFilesystem            Size  Used Avail Use% Mounted
on/dev/sda1             286G   13G  258G   5% /none                  1.5G  196K
 1.5G   1% /devnone                  1.5G     0  1.5G   0% /dev/shmnone        
         1.5G   68K  1.5G   1% /var/runnone                  1.5G     0  1.5G  
0% /var/locknone                  1.5G     0  1.5G   0% /lib/init/rw
grub entry:
Tried a bunch of different configs. This is the one I am using.
menuentry "Xen 4 / Ubuntu 10.04 kernel 2.6.32.15" {insmod ext2set
root=''(hd0,1)''multiboot
 (hd0,1)/boot/xen.gz dom0_mem=1024M loglvl=all guest_loglvl=allmodule
(hd0,1)/boot/vmlinuz-2.6.32.15 root=/dev/sda1 ro nomodesetmodule
(hd0,1)/boot/initrd.img-2.6.32.15}
 Murray Thomson
From: Boris Derzhavets <bderzhavets@yahoo.com>
To: xen-users@lists.xensource.com;
 Murray Thomson <murray_thomson7788@yahoo.com>
Sent: Tue, July 13, 2010 12:31:09 PM
Subject: Re: [Xen-users] Xen 4 Ubuntu Lucid panics
1. First 
Yours tuning backends ( right ?)
                 <M> Xen /dev/xen/evtchn
device                                                       
 
                  [*] Backend driver
 support                                           
                  < >   Xen backend network
device                                   
                  < >   Block-device backend
 driver                                                      
                  < >   Block-device tap backend
driver                                                 
                  <*>   PCI-device backend
 driver                                                        
                          PCI Backend Mode (Virtual PCI) 
--->                                          
                  [ ]     PCI Backend
 Debugging                                                          
                 <M> Xen
filesystem                                                                    
 
                 [*]   Create compatibility mount point
/proc/xen                                      
                 [*] Create xen entries under
/sys/hypervisor                                          
                 < > xen platform pci device
 driver                                                     
                 < > userspace grant access device driver  
Per tutorial :-
  <*> Xen /dev/xen/evtchn
device                                                       
 
                  [*] Backend driver
support                                          
                  <*>   Xen backend network
device                                   
                  <*>   Block-device backend
 driver                                                      
                  <*>   Block-device tap backend
driver                                                 
                  <*>   PCI-device backend
 driver                                                        
                          PCI Backend Mode (Virtual PCI) 
--->                                          
                  [ ]     PCI Backend
 Debugging                                                          
                 <*> Xen
filesystem                                                                    
 
                 [*]   Create compatibility mount point
/proc/xen                                      
                 [*] Create xen entries under
/sys/hypervisor                                          
                 <*> xen platform pci device
 driver                                                     
                 <*> userspace grant access device driver 
Now 
# diff -auN config.received config.071310  > conf.patch
# cat conf.patch
. . . . . .
-# CONFIG_XEN_NETDEV_BACKEND is not set
-# CONFIG_XEN_BLKDEV_BACKEND is not set
-# CONFIG_XEN_BLKDEV_TAP is not set
+CONFIG_XEN_NETDEV_BACKEND=y
+CONFIG_XEN_BLKDEV_BACKEND=y
+CONFIG_XEN_BLKDEV_TAP=y
+CONFIG_XEN_BLKBACK_PAGEMAP=y
I attached mine config and config.patch.
Make diff one more time on your box and watch errors for yourself
The
 best option - just use config attached after git pull ( 2.6.32.16 )
2. Second.
Please submit your working grub entry for Xen (just one)  and "df  -h"
for corresponding vanilla entry. /dev/sdb5 and (hd0,1) seem strange to me.
Boris.
--- On Tue, 7/13/10, Murray Thomson <murray_thomson7788@yahoo.com> wrote:
From: Murray Thomson <murray_thomson7788@yahoo.com>
Subject: Re: [Xen-users] Xen 4 Ubuntu Lucid panics
To: "Boris Derzhavets" <bderzhavets@yahoo.com>,
xen-users@lists.xensource.com
Date: Tuesday, July 13, 2010, 10:52 AM
grub.cfg
## DO NOT EDIT THIS
 FILE## It is automatically generated by /usr/sbin/grub-mkconfig using
templates# from /etc/grub.d and settings from /etc/default/grub#
### BEGIN /etc/grub.d/00_header ###if [ -s $prefix/grubenv ];
then  load_envfiset default="2"if [ ${prev_saved_entry} ]; then  set
saved_entry=${prev_saved_entry}  save_env saved_entry  set
prev_saved_entry=  save_env prev_saved_entry  set boot_once=truefi
function savedefault {  if [
 -z ${boot_once} ]; then    saved_entry=${chosen}    save_env saved_entry  fi}
function recordfail {  set recordfail=1  if [ -n ${have_grubenv} ]; then if [ -z
${boot_once} ]; then save_env recordfail; fi; fi}insmod ext2set
root=''(hd0,1)''search --no-floppy --fs-uuid --set
a2f031e5-cdce-440f-a736-64fd0e4ec43eif loadfont /usr/share/grub/unicode.pf2 ;
then  set gfxmode=640x480  insmod gfxterm  insmod vbe  if terminal_output
gfxterm ; then true ; else    # For backward compatibility with versions of
terminal.mod that don''t    # understand terminal_output    terminal
 gfxterm  fifiinsmod ext2set root=''(hd0,1)''search --no-floppy
--fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43eset
locale_dir=($root)/boot/grub/localeset lang=eninsmod gettextif [ ${recordfail} =
1 ]; then  set timeout=-1else  set timeout=10fi### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###set menu_color_normal=white/blackset
menu_color_highlight=black/light-gray### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###menuentry ''Ubuntu, with Linux
2.6.32.15'' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail	insmod ext2	set root=''(hd0,1)''	search --no-floppy
--fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e	linux
/boot/vmlinuz-2.6.32.15 root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro  
quiet	initrd	/boot/initrd.img-2.6.32.15}menuentry ''Ubuntu, with Linux
2.6.32.15 (recovery mode)'' --class ubuntu --class gnu-linux --class gnu
--class os {	recordfail
	insmod
 ext2	set root=''(hd0,1)''	search --no-floppy --fs-uuid --set
a2f031e5-cdce-440f-a736-64fd0e4ec43e	echo	''Loading Linux 2.6.32.15
...''	linux	/boot/vmlinuz-2.6.32.15
root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro single 	echo	''Loading
initial ramdisk ...''	initrd
	/boot/initrd.img-2.6.32.15}menuentry ''Ubuntu, with Linux
2.6.32-21-server'' --class ubuntu --class gnu-linux --class gnu --class
os {	recordfail	insmod ext2	set root=''(hd0,1)''	search
--no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e	linux
/boot/vmlinuz-2.6.32-21-server root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro
  quiet	initrd
	/boot/initrd.img-2.6.32-21-server}menuentry ''Ubuntu, with Linux
2.6.32-21-server (recovery mode)'' --class ubuntu --class gnu-linux
--class gnu --class os {	recordfail	insmod ext2	set
root=''(hd0,1)''	search --no-floppy --fs-uuid --set
a2f031e5-cdce-440f-a736-64fd0e4ec43e	echo	''Loading Linux
2.6.32-21-server ...''	linux	/boot/vmlinuz-2.6.32-21-server
 root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro single 	echo
''Loading initial ramdisk ...''	initrd
/boot/initrd.img-2.6.32-21-server}### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_memtest86+ ###menuentry "Memory test
(memtest86+)" {	insmod ext2	set root=''(hd0,1)''	search
--no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e
	linux16	/boot/memtest86+.bin}menuentry "Memory test (memtest86+, serial
console 115200)" {	insmod ext2	set root=''(hd0,1)''	search
--no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e	linux16
/boot/memtest86+.bin console=ttyS0,115200n8}### END /etc/grub.d/20_memtest86+
###
### BEGIN /etc/grub.d/30_os-prober ###### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom #### This file
 provides an
 easy way to add custom
 menu entries.  Simply type the# menu entries you want to add after this
comment.  Be careful not to change# the ''exec tail'' line
above.menuentry "Xen 4 / Ubuntu 10.04 kernel 2.6.32.15" {insmod
ext2set root=''(hd0,1)''multiboot (hd0,1)/boot/xen.gz
dom0_mem=1024M loglvl=all guest_loglvl=allmodule (hd0,1)/boot/vmlinuz-2.6.32.15
root=/dev/sda1 ro nomodesetmodule (hd0,1)/boot/initrd.img-2.6.32.15}#menuentry
"Xen 4 / Ubuntu 10.04 kernel 2.6.32.15a" {#insmod ext2#set
root=''(hd0,1)''#multiboot (hd0,1)/boot/xen.gz
dummy=dummy#module (hd0,1)/boot/vmlinuz-2.6.32.15 dummy=dummy nopat
root=/dev/sdc2 ro console=tty0 #module
(hd0,1)/boot/initrd.img-2.6.32.15#}#menuentry "Xen 4 / Ubuntu 10.04 kernel
2.6.32.15b" {#insmod ext2#set
 root=''(hd0,1)''#multiboot (hd0,1)/boot/xen-4.0.1-rc4-pre.gz
dummy=dummy#module (hd0,1)/boot/vmlinuz-2.6.32.15 dummy=dummy nopat
root=/dev/sdc2 ro console=tty0 #module
(hd0,1)/boot/initrd.img-2.6.32.15#}menuentry "Xen 4 / Ubuntu 10.04 kernel
2.6.32.15 config 2" {insmod ext2set
root=''(hd0,1)''multiboot (hd0,1)/boot/xen.gz dummy=dummymodule
(hd0,1)/boot/vmlinuz-2.6.32.15 dummy=dummy nopat root=/dev/sdb5 ro
console=tty0module (hd0,1)/boot/initrd.img-2.6.32.15}### END
/etc/grub.d/40_custom ###
 Murray Thomson
From: Boris Derzhavets <bderzhavets@yahoo.com>
To: xen-users@lists.xensource.com; Murray Thomson
<murray_thomson7788@yahoo.com>
Sent: Tue, July 13, 2010 9:54:49 AM
Subject: Re: [Xen-users] Xen 4 Ubuntu Lucid panics
1. I would suggest you to obtain a serial log and escalate the problem to
xen-devel.
2. Could you post yours /usr/src/linux-2.6-xen/.config ( gzipped)
,/boot/grub/grub.cfg,
"df -h" output.
Boris.
--- On Tue, 7/13/10, Murray Thomson <murray_thomson7788@yahoo.com> wrote:
From: Murray Thomson
 <murray_thomson7788@yahoo.com>
Subject: [Xen-users] Xen 4 Ubuntu Lucid panics
To: xen-users@lists.xensource.com
Date: Tuesday, July 13, 2010, 9:41 AM
I have tried 4 time unsuccessfully to install Xen 4 on Ubuntu Lucid (10.4) 64
bit version using the
 tutorial
at http://bderzhavets.wordpress.com/2010/04/24/set-up-ubuntu-10-04-server-pv-domu-at-xen-4-0-dom0-pvops-2-6-32-10-kernel-dom0-on-top-of-ubuntu-10-04-server/
on a Lenovo thinkcentre workstation.
When I boot I get a kernel panic. If I boot the Linux kernel that I compiled
using the tutorial on it''s own it boots fine. 
Is the likely cause hardware? is there a common error made in this tutorial that
would
 cause a panic on boot. 
Murray
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
      
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
      
      
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Boris Derzhavets
2010-Jul-13  20:17 UTC
Re: [Xen-users] Xen 4 Ubuntu Lucid panics ( Xen >=4.0.1-rc2)
I forgot kernel >=2.6.32.15 requires Xen 4.0.1-rc2 at least
So build Xen as follows :-
# cd /usr/src
# hg clone http://xenbits.xensource.com/xen-4.0-testing.hg
# cd xen-4.0-testing.hg
# make xen
# make tools
# make install-xen
# make install-tools PYTHON_PREFIX_ARG
Boris.
--- On Tue, 7/13/10, Murray Thomson <murray_thomson7788@yahoo.com> wrote:
From: Murray Thomson <murray_thomson7788@yahoo.com>
Subject: Re: [Xen-users] Xen 4 Ubuntu Lucid panics
To: "Boris Derzhavets" <bderzhavets@yahoo.com>,
xen-users@lists.xensource.com
Date: Tuesday, July 13, 2010, 3:20 PM
(! 211)-> df -hFilesystem            Size  Used Avail Use% Mounted
on/dev/sda1             286G   13G  258G   5% /none                  1.5G  196K
 1.5G   1% /devnone                  1.5G     0  1.5G   0% /dev/shmnone        
         1.5G   68K  1.5G   1% /var/runnone                  1.5G     0  1.5G  
0% /var/locknone                  1.5G     0  1.5G   0% /lib/init/rw
grub entry:
Tried a bunch of different configs. This is the one I am using.
menuentry "Xen 4 / Ubuntu 10.04 kernel 2.6.32.15" {insmod ext2set
root=''(hd0,1)''multiboot
 (hd0,1)/boot/xen.gz dom0_mem=1024M loglvl=all guest_loglvl=allmodule
(hd0,1)/boot/vmlinuz-2.6.32.15 root=/dev/sda1 ro nomodesetmodule
(hd0,1)/boot/initrd.img-2.6.32.15}
 Murray Thomson
From: Boris Derzhavets <bderzhavets@yahoo.com>
To: xen-users@lists.xensource.com;
 Murray Thomson <murray_thomson7788@yahoo.com>
Sent: Tue, July 13, 2010 12:31:09 PM
Subject: Re: [Xen-users] Xen 4 Ubuntu Lucid panics
1. First 
Yours tuning backends ( right ?)
                 <M> Xen /dev/xen/evtchn
device                                                       
 
                  [*] Backend driver
 support                                           
                  < >   Xen backend network
device                                   
                  < >   Block-device backend
 driver                                                      
                  < >   Block-device tap backend
driver                                                 
                  <*>   PCI-device backend
 driver                                                        
                          PCI Backend Mode (Virtual PCI) 
--->                                          
                  [ ]     PCI Backend
 Debugging                                                          
                 <M> Xen
filesystem                                                                    
 
                 [*]   Create compatibility mount point
/proc/xen                                      
                 [*] Create xen entries under
/sys/hypervisor                                          
                 < > xen platform pci device
 driver                                                     
                 < > userspace grant access device driver  
Per tutorial :-
  <*> Xen /dev/xen/evtchn
device                                                       
 
                  [*] Backend driver
support                                          
                  <*>   Xen backend network
device                                   
                  <*>   Block-device backend
 driver                                                      
                  <*>   Block-device tap backend
driver                                                 
                  <*>   PCI-device backend
 driver                                                        
                          PCI Backend Mode (Virtual PCI) 
--->                                          
                  [ ]     PCI Backend
 Debugging                                                          
                 <*> Xen
filesystem                                                                    
 
                 [*]   Create compatibility mount point
/proc/xen                                      
                 [*] Create xen entries under
/sys/hypervisor                                          
                 <*> xen platform pci device
 driver                                                     
                 <*> userspace grant access device driver 
Now 
# diff -auN config.received config.071310  > conf.patch
# cat conf.patch
. . . . . .
-# CONFIG_XEN_NETDEV_BACKEND is not set
-# CONFIG_XEN_BLKDEV_BACKEND is not set
-# CONFIG_XEN_BLKDEV_TAP is not set
+CONFIG_XEN_NETDEV_BACKEND=y
+CONFIG_XEN_BLKDEV_BACKEND=y
+CONFIG_XEN_BLKDEV_TAP=y
+CONFIG_XEN_BLKBACK_PAGEMAP=y
I attached mine config and config.patch.
Make diff one more time on your box and watch errors for yourself
The
 best option - just use config attached after git pull ( 2.6.32.16 )
2. Second.
Please submit your working grub entry for Xen (just one)  and "df  -h"
for corresponding vanilla entry. /dev/sdb5 and (hd0,1) seem strange to me.
Boris.
--- On Tue, 7/13/10, Murray Thomson <murray_thomson7788@yahoo.com> wrote:
From: Murray Thomson <murray_thomson7788@yahoo.com>
Subject: Re: [Xen-users] Xen 4 Ubuntu Lucid panics
To: "Boris Derzhavets" <bderzhavets@yahoo.com>,
xen-users@lists.xensource.com
Date: Tuesday, July 13, 2010, 10:52 AM
grub.cfg
## DO NOT EDIT THIS
 FILE## It is automatically generated by /usr/sbin/grub-mkconfig using
templates# from /etc/grub.d and settings from /etc/default/grub#
### BEGIN /etc/grub.d/00_header ###if [ -s $prefix/grubenv ];
then  load_envfiset default="2"if [ ${prev_saved_entry} ]; then  set
saved_entry=${prev_saved_entry}  save_env saved_entry  set
prev_saved_entry=  save_env prev_saved_entry  set boot_once=truefi
function savedefault {  if [
 -z ${boot_once} ]; then    saved_entry=${chosen}    save_env saved_entry  fi}
function recordfail {  set recordfail=1  if [ -n ${have_grubenv} ]; then if [ -z
${boot_once} ]; then save_env recordfail; fi; fi}insmod ext2set
root=''(hd0,1)''search --no-floppy --fs-uuid --set
a2f031e5-cdce-440f-a736-64fd0e4ec43eif loadfont /usr/share/grub/unicode.pf2 ;
then  set gfxmode=640x480  insmod gfxterm  insmod vbe  if terminal_output
gfxterm ; then true ; else    # For backward compatibility with versions of
terminal.mod that don''t    # understand terminal_output    terminal
 gfxterm  fifiinsmod ext2set root=''(hd0,1)''search --no-floppy
--fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43eset
locale_dir=($root)/boot/grub/localeset lang=eninsmod gettextif [ ${recordfail} =
1 ]; then  set timeout=-1else  set timeout=10fi### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###set menu_color_normal=white/blackset
menu_color_highlight=black/light-gray### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###menuentry ''Ubuntu, with Linux
2.6.32.15'' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail	insmod ext2	set root=''(hd0,1)''	search --no-floppy
--fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e	linux
/boot/vmlinuz-2.6.32.15 root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro  
quiet	initrd	/boot/initrd.img-2.6.32.15}menuentry ''Ubuntu, with Linux
2.6.32.15 (recovery mode)'' --class ubuntu --class gnu-linux --class gnu
--class os {	recordfail
	insmod
 ext2	set root=''(hd0,1)''	search --no-floppy --fs-uuid --set
a2f031e5-cdce-440f-a736-64fd0e4ec43e	echo	''Loading Linux 2.6.32.15
...''	linux	/boot/vmlinuz-2.6.32.15
root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro single 	echo	''Loading
initial ramdisk ...''	initrd
	/boot/initrd.img-2.6.32.15}menuentry ''Ubuntu, with Linux
2.6.32-21-server'' --class ubuntu --class gnu-linux --class gnu --class
os {	recordfail	insmod ext2	set root=''(hd0,1)''	search
--no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e	linux
/boot/vmlinuz-2.6.32-21-server root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro
  quiet	initrd
	/boot/initrd.img-2.6.32-21-server}menuentry ''Ubuntu, with Linux
2.6.32-21-server (recovery mode)'' --class ubuntu --class gnu-linux
--class gnu --class os {	recordfail	insmod ext2	set
root=''(hd0,1)''	search --no-floppy --fs-uuid --set
a2f031e5-cdce-440f-a736-64fd0e4ec43e	echo	''Loading Linux
2.6.32-21-server ...''	linux	/boot/vmlinuz-2.6.32-21-server
 root=UUID=a2f031e5-cdce-440f-a736-64fd0e4ec43e ro single 	echo
''Loading initial ramdisk ...''	initrd
/boot/initrd.img-2.6.32-21-server}### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_memtest86+ ###menuentry "Memory test
(memtest86+)" {	insmod ext2	set root=''(hd0,1)''	search
--no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e
	linux16	/boot/memtest86+.bin}menuentry "Memory test (memtest86+, serial
console 115200)" {	insmod ext2	set root=''(hd0,1)''	search
--no-floppy --fs-uuid --set a2f031e5-cdce-440f-a736-64fd0e4ec43e	linux16
/boot/memtest86+.bin console=ttyS0,115200n8}### END /etc/grub.d/20_memtest86+
###
### BEGIN /etc/grub.d/30_os-prober ###### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom #### This file
 provides an
 easy way to add custom
 menu entries.  Simply type the# menu entries you want to add after this
comment.  Be careful not to change# the ''exec tail'' line
above.menuentry "Xen 4 / Ubuntu 10.04 kernel 2.6.32.15" {insmod
ext2set root=''(hd0,1)''multiboot (hd0,1)/boot/xen.gz
dom0_mem=1024M loglvl=all guest_loglvl=allmodule (hd0,1)/boot/vmlinuz-2.6.32.15
root=/dev/sda1 ro nomodesetmodule (hd0,1)/boot/initrd.img-2.6.32.15}#menuentry
"Xen 4 / Ubuntu 10.04 kernel 2.6.32.15a" {#insmod ext2#set
root=''(hd0,1)''#multiboot (hd0,1)/boot/xen.gz
dummy=dummy#module (hd0,1)/boot/vmlinuz-2.6.32.15 dummy=dummy nopat
root=/dev/sdc2 ro console=tty0 #module
(hd0,1)/boot/initrd.img-2.6.32.15#}#menuentry "Xen 4 / Ubuntu 10.04 kernel
2.6.32.15b" {#insmod ext2#set
 root=''(hd0,1)''#multiboot (hd0,1)/boot/xen-4.0.1-rc4-pre.gz
dummy=dummy#module (hd0,1)/boot/vmlinuz-2.6.32.15 dummy=dummy nopat
root=/dev/sdc2 ro console=tty0 #module
(hd0,1)/boot/initrd.img-2.6.32.15#}menuentry "Xen 4 / Ubuntu 10.04 kernel
2.6.32.15 config 2" {insmod ext2set
root=''(hd0,1)''multiboot (hd0,1)/boot/xen.gz dummy=dummymodule
(hd0,1)/boot/vmlinuz-2.6.32.15 dummy=dummy nopat root=/dev/sdb5 ro
console=tty0module (hd0,1)/boot/initrd.img-2.6.32.15}### END
/etc/grub.d/40_custom ###
 Murray Thomson
From: Boris Derzhavets <bderzhavets@yahoo.com>
To: xen-users@lists.xensource.com; Murray Thomson
<murray_thomson7788@yahoo.com>
Sent: Tue, July 13, 2010 9:54:49 AM
Subject: Re: [Xen-users] Xen 4 Ubuntu Lucid panics
1. I would suggest you to obtain a serial log and escalate the problem to
xen-devel.
2. Could you post yours /usr/src/linux-2.6-xen/.config ( gzipped)
,/boot/grub/grub.cfg,
"df -h" output.
Boris.
--- On Tue, 7/13/10, Murray Thomson <murray_thomson7788@yahoo.com> wrote:
From: Murray Thomson
 <murray_thomson7788@yahoo.com>
Subject: [Xen-users] Xen 4 Ubuntu Lucid panics
To: xen-users@lists.xensource.com
Date: Tuesday, July 13, 2010, 9:41 AM
I have tried 4 time unsuccessfully to install Xen 4 on Ubuntu Lucid (10.4) 64
bit version using the
 tutorial
at http://bderzhavets.wordpress.com/2010/04/24/set-up-ubuntu-10-04-server-pv-domu-at-xen-4-0-dom0-pvops-2-6-32-10-kernel-dom0-on-top-of-ubuntu-10-04-server/
on a Lenovo thinkcentre workstation.
When I boot I get a kernel panic. If I boot the Linux kernel that I compiled
using the tutorial on it''s own it boots fine. 
Is the likely cause hardware? is there a common error made in this tutorial that
would
 cause a panic on boot. 
Murray
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
      
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
      
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
      
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Possibly Parallel Threads
- Xen not seeing all the memory in the box
- how should I go for Xen 4.0.1 with a non pv-ops Dom0 kernel
- installing xen on a vmware work station
- Installing Xen4.0.1 on Ubuntu 10.04 LTS issues (VGA crashes at boot-up)
- Xen doesn't boot on grub2 or xend doesn't start