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] RE: xm-test results on Unisys ES7000

To: "Krysan, Susan" <KRYSANS@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] RE: xm-test results on Unisys ES7000
From: "Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>
Date: Thu, 11 May 2006 17:18:34 -0400
Cc: "Vessey, Bruce A" <Bruce.Vessey@xxxxxxxxxx>, "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>, "Carb, Brian A" <Brian.Carb@xxxxxxxxxx>
Delivery-date: Thu, 11 May 2006 14:19:00 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZ1PLL7uPQpaJwxQHuqixf4t1Qn8gAADbiw
Thread-topic: xm-test results on Unisys ES7000
FAIL: 01_enforce_dom0_cpus_basic_pos
         /proc/cpuinfo says xend didn't enforce dom0_cpus (31 != 1)

This issue happens because it takes a few seconds for the /proc/cpuinfo
to be reduced from 32 to 1 after dom0_cpus have been reset to 1. We will
be sending in a path shortly to monitor /proc/cpuinfo in a loop with a
20 second timeout.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] RE: xm-test results on Unisys ES7000, Subrahmanian, Raj <=