This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 1223] New: domU Domain Console not Working

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1223] New: domU Domain Console not Working
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 23 Apr 2008 03:22:11 -0700
Delivery-date: Wed, 23 Apr 2008 03:22:25 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: domU Domain Console not Working
           Product: Xen
           Version: unspecified
          Platform: x86
        OS/Version: Linux-2.6
            Status: NEW
          Severity: blocker
          Priority: P1
         Component: Unspecified
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: tiger1986sg@xxxxxxxxx

I've recently upgraded from Xen 3.1.3 to Xen 3.2.0. On 3.1.3 it didn't have any
issue. On 3.2.0 I see the following after I did "xm create -c dom01.cfg"

i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
XENBUS: Device with no driver: device/console/0
Freeing unused kernel memory: 140k freed
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
EXT3 FS on hda1, internal journal

Then it stopped. The console totally freezes and it does not respond to any
input. I could CTRL+] out. When I tried to go back to the console via "xm
console", nothing shows up and it does not respond to any input.

The domain actually booted up and is responding. I can ping to it and even SSH

All configurations, including kernel configs, are the same as 3.1.3.

I tried the same thing on another x86_64 machine with the same problem.

Note the OS is Debian 4.0 Etch for all.

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list