<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Thomas,<br>
<br>
Thanks for your fast response.<br>
<br>
On 2012-03-28 12:11, Thomas Goirand wrote:
<blockquote cite="mid:4F72E3D5.9010006@goirand.fr" type="cite">
<pre wrap="">On 03/27/2012 03:08 AM, Roland Lammel wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> * What was the outcome of this action?
Xen guests did not boot correctly (CentOS 4.9 hang on hardware
initialization) and xm console is not working (hangs without any
output)
</pre>
</blockquote>
<pre wrap="">
IMO, this is a typical miss-configuration of the guest. What did you
configure in /etc/inittab as console? What is your domU kernel command
line options (especially those regarding the console)? What kernel do
you run for this CentOS guest? Are you using pygrub, and the kernel
inside the domU, or the 3.2 Linux kernel from dom0?
</pre>
</blockquote>
No, I'm pretty sure it is not. The guest have been running before
with Xen 4.0.1 and Linux 2.3.32 (from stable) on the same host. We
just upgraded to Xen 4.1 (tools and hypervisor) and Linux 3.2.12
(from testing) before, nothing has changed in the guests. During my
analysis of the issue I also checked the console device
configuration, which seemed pretty fine and the devices itself were
there in the guest (/dev/xvc0 on CentOS 4.9, /dev/hvc0 for the newer
debian guests). None of the consoles where working, but the Debian
(hey, that's why we love debian) booted fine without the console and
where reachable on the network, so the missing console was not that
critical.<br>
<br>
Without changing any configuration, just loading the module
xen_gntdev on the host fixed the issue. After loading it, I could
exec xm console for all guests and get to my console.<br>
<br>
None the less here is the requested information.<br>
<br>
The debian based guests are already using hvc0. Yes we are using
pygrub<br>
<br>
Host (dom0) Xen Info:<br>
<blockquote>host : s2.office.neotel.at<br>
release : 3.2.0-2-amd64<br>
version : #1 SMP Tue Mar 20 18:36:37 UTC 2012<br>
machine : x86_64<br>
nr_cpus : 8<br>
nr_nodes : 1<br>
cores_per_socket : 4<br>
threads_per_core : 1<br>
cpu_mhz : 2127<br>
hw_caps :
bfebfbff:20100800:00000000:00000940:000ce3bd:00000000:00000001:00000000<br>
virt_caps : hvm<br>
total_memory : 16383<br>
free_memory : 7499<br>
free_cpus : 0<br>
xen_major : 4<br>
xen_minor : 1<br>
xen_extra : .2<br>
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p
hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 <br>
xen_scheduler : credit<br>
xen_pagesize : 4096<br>
platform_params : virt_start=0xffff800000000000<br>
xen_changeset : unavailable<br>
xen_commandline : placeholder dom0_mem=4194304<br>
cc_compiler : gcc version 4.6.2 (Debian 4.6.2-6) <br>
cc_compile_by : waldi<br>
cc_compile_domain : debian.org<br>
cc_compile_date : Sat Dec 10 19:58:21 UTC 2011<br>
xend_config_format : 4<br>
</blockquote>
<br>
Guest Xen Config:<br>
<blockquote>bootloader = "/usr/bin/pygrub"<br>
memory = "512"<br>
name = "s1"<br>
vif = ['mac=00:16:3e:55:33:01, bridge=br20, vifname=s1.eth0,
script=vif-bridge-tap', ]<br>
disk = ['phy:vg1/s1_root,xvda1,w',]<br>
apic=1<br>
acpi=1<br>
pae=0<br>
vcpus=1<br>
cpus = "2-7"<br>
on_reboot = 'restart'<br>
on_crash = 'restart'<br>
on_shutdown = 'destroy'<br>
vnc = 1<br>
vfb = [ 'type=vnc,vncdisplay=3,vnclisten=0.0.0.0' ]<br>
usbdevice = 'mouse'<br>
keymap = 'de'<br>
serial = 'pty' # enable serial console<br>
sdl=0<br>
<br>
</blockquote>
In the guest (CentOS release 4.9 (Final)):<br>
<blockquote>[root@s1 ~]# uname -a<br>
Linux s1.office.neotel.at 2.6.9-101.ELxenU #1 SMP Thu Jul 21
17:58:34 EDT 2011 i686 i686 i386 GNU/Linux<br>
[root@s1 ~]# grep tty /etc/inittab<br>
# Run gettys in standard runlevels<br>
co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav<br>
1:2345:respawn:/sbin/mingetty tty1<br>
2:2345:respawn:/sbin/mingetty tty2<br>
3:2345:respawn:/sbin/mingetty tty3<br>
4:2345:respawn:/sbin/mingetty tty4<br>
5:2345:respawn:/sbin/mingetty tty5<br>
6:2345:respawn:/sbin/mingetty tty6<br>
</blockquote>
<br>
<blockquote cite="mid:4F72E3D5.9010006@goirand.fr" type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap=""> * What outcome did you expect instead?
Xen guests boot and xm console works
</pre>
</blockquote>
<pre wrap="">
Well, since the console device has been renamed in newer Linux kernels,
you do have some manual work to do, and I don't think you should write
that this is a Xen bug.</pre>
</blockquote>
See above, guest devices were named correctly.<br>
<blockquote cite="mid:4F72E3D5.9010006@goirand.fr" type="cite">
<pre wrap="">
Please include your domU startup file in this bug report.
Thomas
</pre>
</blockquote>
<br>
Would be interesting if you can reproduce the issue, by unloading
the xen_gntdev module (or making sure it's not loaded on the host on
boot).<br>
<br>
Thanks and Cheers<br>
<br>
Roland<br>
<pre class="moz-signature" cols="72">--
Roland Lammel
NeoTel Telefonservice GmbH & Co KG
Esterhazygasse 18a/15
A-1060 Wien
T: +43 1 4094181 - 86
M: +43 660 88866 - 86
F: +43 1 4094181 - 986</pre>
</body>
</html>