11 messages in com.xensource.lists.xen-bugs[Xen-bugs] [Bug 1223] New: domU Domai...
FromSent OnAttachments
bugz...@lists.xensource.com23 Apr 2008 03:21 
bugz...@lists.xensource.com23 Apr 2008 03:26 
bugz...@lists.xensource.com23 Apr 2008 03:33 
bugz...@lists.xensource.com23 Apr 2008 03:35 
bugz...@lists.xensource.com23 Apr 2008 03:40 
bugz...@lists.xensource.com23 Apr 2008 03:47 
bugz...@lists.xensource.com23 Apr 2008 03:50 
bugz...@lists.xensource.com23 Apr 2008 06:06 
bugz...@lists.xensource.com23 Apr 2008 06:55 
bugz...@lists.xensource.com23 Apr 2008 07:29 
bugz...@lists.xensource.com23 Apr 2008 07:39 
Subject:[Xen-bugs] [Bug 1223] New: domU Domain Console not Working
From:bugz...@lists.xensource.com (bugz@lists.xensource.com)
Date:04/23/2008 03:21:48 AM
List:com.xensource.lists.xen-bugs

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1223

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-@lists.xensource.com ReportedBy: tige@yahoo.com

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

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.