|
|
|
|
|
|
|
|
|
|
xen-users
Re: [Xen-users] Hypervisor hangs on startup
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I can confirm this problem on a Dell R710 running Debian Squeeze on
AMD64. The really strange thing is, we operate roughly 20 more R710
without such problems. The only notable difference is the hardware in
detail.
That is a Intel( Xeon( CPUE5530 @ 2.40GHz and a 2,4T storage array on a
H700 controller (thus using gpt!). So it seems to be either related to
large disk sizes (using GPT as said) or the CPU type (having in total 16
cores/SMT units).
Moreover the default kernel from Debian boots fine, as does the
xen-enabled pv_ops dom0 kernel running on bare metal (thus without
hypervisor).
I tried to enable serial output from Xen (console=com2) through the
onboard DRAC serial port forwarding. This returns some garbage only
though for the hypervisor wheras BIOS/POST + grub are fine (see below):
���f����▒f���▒~f����f�����▒��▒�▒▒�`fx▒f���▒��▒�����▒▒�~f�`f�xf��f
The grub.cfg is this:
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by 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="3"
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 load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}
serial --unit=1 --speed=57600
terminal_input serial
terminal_output serial
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64' --class
debian --class gnu-linux --class gnu --class os {
insmod part_gpt
insmod ext2
set root='(hd0,gpt1)'
search --no-floppy --fs-uuid --set
4346c332-863c-4482-b9a1-f3d45dffc1e7
echo 'Loading Linux 2.6.32-5-xen-amd64 ...'
linux /boot/vmlinuz-2.6.32-5-xen-amd64
root=UUID=4346c332-863c-4482-b9a1-f3d45dffc1e7 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-xen-amd64
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64' --class debian
- --class gnu-linux --class gnu --class os {
insmod part_gpt
insmod ext2
set root='(hd0,gpt1)'
search --no-floppy --fs-uuid --set
4346c332-863c-4482-b9a1-f3d45dffc1e7
echo 'Loading Linux 2.6.32-5-amd64 ...'
linux /boot/vmlinuz-2.6.32-5-amd64
root=UUID=4346c332-863c-4482-b9a1-f3d45dffc1e7 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-amd64
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN
4.0-amd64' --class debian --class gnu-linux --class gnu --class os
- --class xen {
insmod part_gpt
insmod ext2
set root='(hd0,gpt1)'
search --no-floppy --fs-uuid --set
4346c332-863c-4482-b9a1-f3d45dffc1e7
echo 'Loading Linux 2.6.32-5-xen-amd64 ...'
multiboot /boot/xen-4.0-amd64.gz console=com2 com2=57600,8n1
module /boot/vmlinuz-2.6.32-5-xen-amd64 placeholder
root=UUID=4346c332-863c-4482-b9a1-f3d45dffc1e7 ro console=ttyS1
echo 'Loading initial ramdisk ...'
module /boot/initrd.img-2.6.32-5-xen-amd64
}
### END /etc/grub.d/20_linux_xen ###
### 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.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
Please note that "console=com2 com2=57600,8n1" produces the given
garbage followed by an immediate reboot. Without this arguments to the
hypervisor the serial output indicates that the actual dom0 kernel is
never booted. The output of the virtual console shows exactly the same
as Klaus reported.
Maybe you can point out how to enable/fix my issue with the console or
denote me what to do next in order to provide you more useful debugging
output.
Wavecon GmbH | Frankenstrasse 9 | 90762 Fuerth
Web: wavecon.de | Mail + Jabber at@xxxxxxxxxx
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk0K14IACgkQBWM6U4QI1MQj0wCfUNwz9DAYWYWj1ZP+ZUzuCtKY
nPwAn3n0UFHPLSGySLgphCrnJHe3ijbo
=iy7p
-----END PGP SIGNATURE-----
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-users] Hypervisor hangs on startup, Klaus Darilion
- Re: [Xen-users] Hypervisor hangs on startup,
Arno Toell <=
- Re: [Xen-users] Hypervisor hangs on startup, Arno Toell
- Re: [Xen-users] Hypervisor hangs on startup, Pasi Kärkkäinen
- Re: [Xen-users] Hypervisor hangs on startup, Arno Toell
- [Xen-devel] Re: [Xen-users] Hypervisor hangs on startup, 2.6.32-5-xen dom0 kernel panic, Pasi Kärkkäinen
- Re: [Xen-users] Hypervisor hangs on startup, 2.6.32-5-xen dom0 kernel panic, Arno Toell
- Re: [Xen-devel] Re: [Xen-users] Hypervisor hangs on startup, 2.6.32-5-xen dom0 kernel panic, Ian Campbell
- Re: [Xen-devel] Re: [Xen-users] Hypervisor hangs on startup, 2.6.32-5-xen dom0 kernel panic, Arno Toell
- Re: [Xen-devel] Re: [Xen-users] Hypervisor hangs on startup, 2.6.32-5-xen dom0 kernel panic, Konrad Rzeszutek Wilk
|
|
|
|
|