[Pkg-xen-devel] Bug#665882: Bug#665882: xen-utils-common: Xen console for guest not working, hangs

[Roland Lammel]

Hi Thomas,

Thanks for your fast response.

On 2012-03-28 12:11, Thomas Goirand wrote:
> On 03/27/2012 03:08 AM, Roland Lammel wrote:
>>    * 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)
> 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?
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.

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.

None the less here is the requested information.

The debian based guests are already using hvc0. Yes we are using pygrub

Host (dom0) Xen Info:

    host                   : s2.office.neotel.at
    release                : 3.2.0-2-amd64
    version                : #1 SMP Tue Mar 20 18:36:37 UTC 2012
    machine                : x86_64
    nr_cpus                : 8
    nr_nodes               : 1
    cores_per_socket       : 4
    threads_per_core       : 1
    cpu_mhz                : 2127
    hw_caps                :
    bfebfbff:20100800:00000000:00000940:000ce3bd:00000000:00000001:00000000
    virt_caps              : hvm
    total_memory           : 16383
    free_memory            : 7499
    free_cpus              : 0
    xen_major              : 4
    xen_minor              : 1
    xen_extra              : .2
    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
    xen_scheduler          : credit
    xen_pagesize           : 4096
    platform_params        : virt_start=0xffff800000000000
    xen_changeset          : unavailable
    xen_commandline        : placeholder dom0_mem=4194304
    cc_compiler            : gcc version 4.6.2 (Debian 4.6.2-6)
    cc_compile_by          : waldi
    cc_compile_domain      : debian.org
    cc_compile_date        : Sat Dec 10 19:58:21 UTC 2011
    xend_config_format     : 4


Guest Xen Config:

    bootloader = "/usr/bin/pygrub"
    memory = "512"
    name = "s1"
    vif = ['mac=00:16:3e:55:33:01, bridge=br20, vifname=s1.eth0,
    script=vif-bridge-tap', ]
    disk = ['phy:vg1/s1_root,xvda1,w',]
    apic=1
    acpi=1
    pae=0
    vcpus=1
    cpus = "2-7"
    on_reboot   = 'restart'
    on_crash    = 'restart'
    on_shutdown = 'destroy'
    vnc = 1
    vfb = [ 'type=vnc,vncdisplay=3,vnclisten=0.0.0.0' ]
    usbdevice = 'mouse'
    keymap    = 'de'
    serial    = 'pty' # enable serial console
    sdl=0

In the guest (CentOS release 4.9 (Final)):

    [root at s1 ~]# uname -a
    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
    [root at s1 ~]# grep tty /etc/inittab
    # Run gettys in standard runlevels
    co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav
    1:2345:respawn:/sbin/mingetty tty1
    2:2345:respawn:/sbin/mingetty tty2
    3:2345:respawn:/sbin/mingetty tty3
    4:2345:respawn:/sbin/mingetty tty4
    5:2345:respawn:/sbin/mingetty tty5
    6:2345:respawn:/sbin/mingetty tty6


>>    * What outcome did you expect instead?
>>
>>    Xen guests boot and xm console works
> 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.
See above, guest devices were named correctly.
>
> Please include your domU startup file in this bug report.
>
> Thomas

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).

Thanks and Cheers

Roland

-- 
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20120329/e2c2e401/attachment.html>