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-bugs] [Bug 1168] New: On an eight cpu system domU 'cap' can only be

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1168] New: On an eight cpu system domU 'cap' can only be set to 100
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 14 Feb 2008 07:02:15 -0800
Delivery-date: Thu, 14 Feb 2008 07:02:25 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: On an eight cpu system domU 'cap' can only be set to 100
           Product: Xen
           Version: 3.0.3
          Platform: x86-64
        OS/Version: Linux-2.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Guest-OS
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: td-ifs@xxxxxx

On a 8 Core system only dom0 can set cap > 100 and vcpus > 1. On a domU 

'xm sched-credit -d <domU> -c 200'

says "Error: cap is out of range". Vcpu cannot be set higher than 1 -
regardless of boot/config/command line. Low performance is equivalent to the
cap setting.

See 'xm list --long':

    (domid 0)
    (uuid 00000000-0000-0000-0000-000000000000)
    (vcpus 8)
    (cpu_weight 1.0)
    (memory 256)
    (shadow_memory 0)
    (maxmem 256)
    (features )
    (name Domain-0)
    (on_poweroff destroy)
    (on_reboot restart)
    (on_crash restart)
    (state r-----)
    (shutdown_reason poweroff)
    (cpu_time 458.198750944)
    (online_vcpus 8)
    (domid 5)
    (uuid f9070996-4ae2-bbc6-ad88-80e0da1a13f1)
    (vcpus 1)
    (cpu_weight 1.0)
    (memory 1024)
    (shadow_memory 0)
    (maxmem 2048)
    (features )
    (name dev-services)
    (on_poweroff destroy)
    (on_reboot restart)
    (on_crash restart)
            (kernel /boot/vmlinuz-2.6.18-5-xen-amd64)
            (ramdisk /boot/initrd.img-2.6.18-5-xen-amd64)
            (root '/dev/sda1 ro')
            (args 'mem=2048M')
            (backend 0)
            (script vif-bridge)
            (bridge xenbr1)
            (mac 00:16:3e:00:00:01)
            (backend 0)
            (dev sda1:disk)
            (uname phy:server/dev-services-root)
            (mode w)
    (state -b----)
    (shutdown_reason poweroff)
    (cpu_time 5.184650252)
    (online_vcpus 1)
    (up_time 1186.54874301)
    (start_time 1202999946.85)
    (store_mfn 628537)
    (console_mfn 628536)

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>