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-devel] bootloader (pygrub) broken in unstable?

To: Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] bootloader (pygrub) broken in unstable?
From: Brendan Cully <brendan@xxxxxxxxx>
Date: Wed, 25 Nov 2009 16:45:53 -0800
Delivery-date: Wed, 25 Nov 2009 16:46:18 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Mail-followup-to: xen-devel@xxxxxxxxxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-08-27)
I just tried out pygrub again for the first time in a while, and it is
not working for me on xen-unstable. It looks like the connection
between the bootloader and the console is not getting set up.

 I added a bit of logging and found that although
XendBootloader.bootloader is creating an entry for
/local/domain/n/console/tty, xenconsoled never picks up on it to
create serial/0/tty, which is what xenconsole seems to want.

It looks like this is because xenconsoled is waiting for
@introduceDomain to rescan the domain list, but in
XendDomainInfo._initDomain the new domain is not introduced until
_after_ the bootloader has run.

How is this supposed to work? Am I missing something obvious?

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] bootloader (pygrub) broken in unstable?, Brendan Cully <=