[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] xen 4.1.3, EFI boot and "no console to OS" problem
Good news is if Xen recognizes all your memory the patch I mentioned is unrelated and I can think of no reason to modify the source. ÂHowever that brings us back to the console not accepting input.
--- Based on what you've said, the KDM login is not frozen (cursor is actively blinking?), but the input is not in the right place somehow. If I am understanding this right, the Java applet sits between the real VGA output and the Matrox adapter, as a layer? ÂIf so maybe some connection is belong list in transit when Xen hands VGA over to the Dom0.
From the tail you posted the only line not in my xl dmesg is this one: (XEN) physdev.c:172: dom0: wrong map_pirq type 3 Google only has a series of unrelated links, a wide range of Dom0's and generally paravirtualization questions, so possibly an unrelated error. --- Here are some questions and tests you can try:
Does your VNC connection take you strait to the same KDM login or a new one? ÂIf it is the same one can you watch it change from the matrox adapter while using it? Can you kill the KDM instance from SSH? ÂDoes it return you to terminal, and does the keyboard work after?
Can you unplug and reconnect the USB keyboard, and when you do what does `tail /var/log/messages` contain? Does the VNC run through the Java applet as well? Finally, is there any configuration options for the Java applet? ÂBecause if it is a layer then I am guessing something is happening at that stage of the system. The only other thoughts I have at the moment are whether the grub.cfg contains any special configuration settings that are different than the Xen version or that might be related to the Java applet.
On Tue, Mar 19, 2013 at 2:07 PM, Janno Loide <janno@xxxxxxx> wrote:
_______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |