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


[XenPPC] new dom1 script, ok.. we are back to normal functionality,

To: xen-ppc-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [XenPPC] new dom1 script, ok.. we are back to normal functionality,
From: Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
Date: Sun, 20 Aug 2006 13:33:20 -0400
Delivery-date: Sun, 20 Aug 2006 10:33:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx
I managed to introduce a bug during my first merge, and we have shadow ops to deal with.

Sorry for the inconvenience, Here is my latest dom1 script.

Attachment: dom1
Description: Binary data

you can get the ramdisk.image.gz from:
http://wiki.xensource.com/xenwiki/XenPPC/Build? action=AttachFile&do=get&target=ramdisk.image.gz

after you make sure that dom1 and amdisk.image.gz are in /root, simply (as root, in /root):
  # xm create -c dom1


Xen-ppc-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>