Roland Lammel
2012-Mar-26 19:08 UTC
[Pkg-xen-devel] Bug#665882: xen-utils-common: Xen console for guest not working, hangs
Package: xen-utils-common Version: 4.1.2-1 Severity: important Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Roland Lammel <lammelr at pc09.NeoTel.local> To: Debian Bug Tracking System <submit at bugs.debian.org> Subject: xen-utils-common: Xen console for guest not working, hangs Bcc: Roland Lammel <lammelr at pc09.NeoTel.local> Package: xen-utils-common Version: 4.1.2-1 Severity: important Dear Maintainer, * What led up to the situation? Upgrade of Linux kernel to 3.2 (testing) and Xen to 4.1 (testing) from Debian Stable (Squeeze) * What exactly did you do (or not do) that was effective (or ineffective)? Upgrading Xen to 4.1 (from 4.0.1) and Linux kernel to 3.2 (from stable 2.6.32) by using apt-pinning to select the packages for linux-image and xen. * 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) * What outcome did you expect instead? Xen guests boot and xm console works It appears the cause of this issue is a missing loaded module named xen-gntdev. Patching /etc/init.d/xend to modprobe for xen-gntdev fixes this issue. (Sorry, patch inline) diff --git a/init.d/xend b/init.d/xend index 2b55623..852cfe4 100755 --- a/init.d/xend +++ b/init.d/xend @@ -34,6 +34,7 @@ modules_setup() { modprobe xenfs 2>/dev/null modprobe xen-evtchn 2>/dev/null + modprobe xen-gntdev 2>/dev/null } xenfs_setup() -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (400, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xen-utils-common depends on: ii gawk 1:3.1.8+dfsg-0.1 ii lsb-base 3.2+Debian31 ii udev 175-3.1 ii xenstore-utils 4.1.2-2 xen-utils-common recommends no packages. xen-utils-common suggests no packages. -- no debconf information -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (400, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xen-utils-common depends on: ii gawk 1:3.1.8+dfsg-0.1 ii lsb-base 3.2+Debian31 ii udev 175-3.1 ii xenstore-utils 4.1.2-2 xen-utils-common recommends no packages. xen-utils-common suggests no packages. -- no debconf information
Thomas Goirand
2012-Mar-28 10:11 UTC
[Pkg-xen-devel] Bug#665882: Bug#665882: xen-utils-common: Xen console for guest not working, hangs
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?> * What outcome did you expect instead? > > Xen guests boot and xm console worksWell, 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. Please include your domU startup file in this bug report. Thomas
Debian Bug Tracking System
2012-Apr-14 17:03 UTC
[Pkg-xen-devel] Bug#665882: marked as done (xen-utils-common: Xen console for guest not working, hangs)
Your message dated Sat, 14 Apr 2012 19:02:17 +0200 with message-id <20120414170217.GB24776 at wavehammer.waldi.eu.org> and subject line Re: [Pkg-xen-devel] Bug#665882: xen-utils-common: Xen console for guest not working, hangs has caused the Debian Bug report #665882, regarding xen-utils-common: Xen console for guest not working, hangs to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 665882: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665882 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Roland Lammel <rl at neotel.at> Subject: xen-utils-common: Xen console for guest not working, hangs Date: Mon, 26 Mar 2012 21:08:40 +0200 Size: 4889 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20120414/28fbe211/attachment.mht> -------------- next part -------------- An embedded message was scrubbed... From: Bastian Blank <waldi at debian.org> Subject: Re: [Pkg-xen-devel] Bug#665882: xen-utils-common: Xen console for guest not working, hangs Date: Sat, 14 Apr 2012 19:02:17 +0200 Size: 1864 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20120414/28fbe211/attachment-0001.mht>
Seemingly Similar Threads
- Error: Device 2049 (vbd) could not be connected. Backend device not found.
- Permission denied of usershares statfile in Samba 3.0.28a-1ubuntu4.7
- Re: [Bug 299306] [NEW] Permission denied of usershares statfile in Samba 3.0.28a-1ubuntu4.7
- SIP message routed back to mysql
- Re: [Xen-changelog] [linux-2.6.18-xen] xen: make gntdev code configurable