Xen users - May 2009 - Problem in xen-hypervisor-3.2-1-amd64 installation on Debian Lenny 2.6.26-1-amd64

Hi,

Forgive my bad english.
I try to find some information about this problem in the internet, but with no
success.

I’m experiencing some problems in xen instalation, and I need some help.
The system is Debian Lenny -2.6.26-1-amd64 #1 SMP Sat Jan 10 17:57:00 UTC 2009
x86_64 GNU/Linux

After install the packges xen-hypervisor-3.2-1-amd64
xen-linux-system-2.6.26-1-xen-amd64 xen-utils-3.2-1 xenstore-utils xenwatch
xen-shell xen-tools from ftp://ftp.br.debian.org/
When I try to boot from xen the system reboots.

This is the Menu.lst from grub:

title Xen 3.2-1-amd64 / Debian GNU/Linux, kernel 2.6.26-1-xen-amd64
root (hd0,0)
kernel /boot/xen-3.2-1-amd64.gz
module /boot/vmlinuz-2.6.26-1-xen-amd64 root=/dev/sda1 ro console=tty0
module /boot/initrd.img-2.6.26-1-xen-amd64

title Debian GNU/Linux, kernel 2.6.26-2-amd64
root (hd0,0)
kernel /boot/vmlinuz-2.6.26-2-amd64 root=/dev/sda1 ro quiet
initrd /boot/initrd.img-2.6.26-2-amd64

title Debian GNU/Linux, kernel 2.6.26-2-amd64 (single-user mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.26-2-amd64 root=/dev/sda1 ro single
initrd /boot/initrd.img-2.6.26-2-amd64

title Debian GNU/Linux, kernel 2.6.26-1-xen-amd64
root (hd0,0)
kernel /boot/vmlinuz-2.6.26-1-xen-amd64 root=/dev/sda1 ro quiet
initrd /boot/initrd.img-2.6.26-1-xen-amd64

title Debian GNU/Linux, kernel 2.6.26-1-xen-amd64 (single-user mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.26-1-xen-amd64 root=/dev/sda1 ro single
initrd /boot/initrd.img-2.6.26-1-xen-amd64

title Debian GNU/Linux, kernel 2.6.26-1-amd64
root (hd0,0)
kernel /boot/vmlinuz-2.6.26-1-amd64 root=/dev/sda1 ro quiet
initrd /boot/initrd.img-2.6.26-1-amd64

title Debian GNU/Linux, kernel 2.6.26-1-amd64 (single-user mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.26-1-amd64 root=/dev/sda1 ro single
initrd /boot/initrd.img-2.6.26-1-amd64


Every options from booting from xen are failing. The system stops in the
messagem:

"Starting MTA: exim4.
Starting Kerneloops:
Starting NFS common utilities: statd.
Not starting internet superserver: no services enabled.
Starting XEN control daemon: xend [ 145.403666] suspend: event channel 21
[ 145.515778] SMP alternatives: switching to UP code "
And then reboots.
The hardware is: Processor: Turion X2 64 TL50, 4GB RAM DDR2 667Mhz, Vídeo
Geforce 6100, 80GB SATA Drive.
Debian system still works fine, the problem is only when I try to boot from xen.

Thanks,

Luana.

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

Hi,
perhaps your dom0 kernel missing some module
can you give us your both .config (xen and non-xen-bootable kernels)
and an lspci ?

regards
yves


Le Mon, 4 May 2009 09:01:59 -0300,
Luana Celeida Rocha <luanac_rocha@yahoo.com.br> a écrit :
> Starting XEN control daemon: xend [ 145.403666] suspend: event
> channel 21
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Mon, May 4, 2009 at 7:01 PM, Luana Celeida Rocha
<luanac_rocha@yahoo.com.br> wrote:
> Starting XEN control daemon: xend [ 145.403666] suspend: event channel 21
> [ 145.515778] SMP alternatives: switching to UP code "
> And then reboots.
That line actually seems suspicous.
How many CPU cores do you have?
Do you have a line in /etc/xen/xend-config.sxp that says

(dom0-cpus 1)

If yes, try changing it to

(dom0-cpus 0)

and see if it still reboots.

Regards,

Fajar

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

Hi Fajar,

I check the file /etc/xen/xend-config.sxp and it''s alredy configured
like you mentioned: (dom0-cpus 0)

Thank you.

Luana

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

On Wed, May 6, 2009 at 5:33 PM, Luana Celeida Rocha
<luanac_rocha@yahoo.com.br> wrote:
> Hi Fajar,
>
> I check the file /etc/xen/xend-config.sxp and it''s alredy
configured like you mentioned: (dom0-cpus 0)
That makes it even weirder then. The lines you posted
> Starting XEN control daemon: xend [ 145.403666] suspend: event channel 21
> [ 145.515778] SMP alternatives: switching to UP code "
> And then reboots.
Indicates that :
- the kernel selects uni processor mode (which should not happen when
you have two cores on the default config)
- it seems to happen when xend is started (which suggest its
configuration file selects that mode)
- it immediately reboots, which suggest a bug in your system probably
doesn''t handle a missing cpu nicely.

At this point perhaps you can try :
- disabling xend startup (using whatever method you like. Usually I
use sysv-rc-conf to enable/disable services). See if it''s able to boot
- do "cat /proc/cpuinfo" after that
- start xend manually

If my guess is right, starting xend will cause your system to reboot.
If that''s the case then you can try:
- finding out which part of your system sets dom0 cpu to 1 and disable it, or
- compile xen from source

Regards,

Fajar

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

> If my guess is right, starting xend will cause your system to reboot.
> If that''s the case then you can try:
> - finding out which part of your system sets dom0 cpu to 1 and disable it,
> or
> - compile xen from source
> 
Can you please guide me how to check which part of my system is setting dom0
cpu to 1. I have booted into xen kernel (i386), whenever I start xend system
reboots!
-- 
View this message in context:
http://www.nabble.com/Problem-in-xen-hypervisor-3.2-1-amd64-installation-on-Debian-Lenny-2.6.26-1-amd64-tp23367359p24528096.html
Sent from the Xen - User mailing list archive at Nabble.com.


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