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


Re: [XenPPC] fixed bad swap of console and store event channels

To: xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [XenPPC] fixed bad swap of console and store event channels
From: hollisb@xxxxxxxxxxxxx
Date: Sun, 6 Aug 2006 19:27:21 -0400
Delivery-date: Sun, 06 Aug 2006 17:03:00 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <E4627F05-5F27-4402-9E58-E42EAB5F6E25@xxxxxxxxxxxxxx>
List-help: <mailto:xen-ppc-devel-request@lists.xensource.com?subject=help>
List-id: Xen PPC development <xen-ppc-devel.lists.xensource.com>
List-post: <mailto:xen-ppc-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=unsubscribe>
References: <E1G97GH-0005zh-BW@xxxxxxxxxxxxxxxxxxxxx> <E4627F05-5F27-4402-9E58-E42EAB5F6E25@xxxxxxxxxxxxxx>
Sender: xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Internet Messaging Program (IMP) H3 (4.1.1)
Quoting Jimi Xenidis <jimix@xxxxxxxxxxxxxx>:

I cannot how embarrassed I am by this.
watching evtchn's fly everywhere seen the wrong one get delivered and
the right one go no where and the whole time I was swapping the 2

Glad you caught it. :)

anyway, using the two files from:

Using the command:
  $ xm create -c dom1
you should be able to boot a DomU and see its output, all the way until
it says it cannot find its rootfs.

Unfortunately this isn't working for me: my output stops after
    PID hash table entries: 512 (order: 9, 4096 bytes)

When I bang keys, I can see events going on dom0 evtchn 10/domU evtchn 2: dom0/10 sends an event to domU/2 (presumably to notify domU of the input), and domU/2 sends an event to dom0/10 (presumably to notify dom0 that there is new console output to display). Strace on the "xm console" process seems to confirm that the incoming event does not wake xm console from its select() call.

I'm pretty sure I've rebuilt/reinstalled the various components cleanly, twice. Could there be an outstanding diff still?

Hollis Blanchard
IBM Linux Technology Center

Xen-ppc-devel mailing list