similar to: AW: VCPU amount

# HG changeset patch # User Lutz.Dube # Node ID ca2c8c262dbaa6b2521cec60af7cd688dabdf850 # Parent 8992134dcfd0b9e1e86f4111e68a8aa48bd33c3c Values of cpu_weight and cpu_cap are lost after xend restart For managed domains in state ''halted'' I always get default values for cpu_cap / cpu_weight after xend restart. This is because the names of parameters differ between a SXP file to

Currently with the credit scheduler, cpu_weight cannot be assigned to guest domains at boot time.(it can be set with xm sched-weight after booting) This patch allows CPU weight, and CAP to be set by the Xen configuration files. Specification: The following can be added to the Xen configuration files. 1.CPU WEIGHT [OPTIONAL] cpu_weight = cpu weight value -sets the cpu time ratio to be

Hi, This patch fixes the Bug:835 issue. # xm create /home/kanno/smp-domU.conf cpu_weight=512 cpu_cap=150 Using config file "/home/kanno/smp-domU.conf". Started domain vm1-smp # xm sched-credit -d vm1-smp {''cap'': 150, ''weight'': 512} Signed-off-by: Masaki Kanno <kanno.masaki@jp.fujitsu.com> Best regards, Kan

Hi, I did accidentally discover a quite useful feature in the Xen HVM configuration file. I here by suggest it to be added in the example file located at </usr/share/doc/xen-utils-common/examples/xmexample.hvm.gz>. It seems that you can configure Xen 3.1's Credit-Based CPU Scheduler by adding settings cpu_weight=128 and cpu_cap=20 in the configuration file itself. Though I

Package: xen-utils-common Version: 4.4.0-5 Severity: important Tags: patch Hello, xen-init-list fails to parse output of xen list -l when using XM toolstack. Therefore, /etc/init.d/xendomains stop fails to shutdown any guests still running on shutdown. xen-init-list fails with the following message: /usr/lib/xen-common/bin/xen-init-list Traceback (most recent call last): File

Shouldn''t RESTART be semantically the same as SHUTDOWN && CREATE ?! Regards, Volker > > > That may well be the case, but it probably takes a bit more digging > > before that can be solved. > > It actually works. It was my fault. > > I tested it by setting cpu_weight in the config and the RESTARTING the > domain. This did not read the new value

Jup, 64 Bit Kernel build is done now and works, but 32 Bit kernel config is different, as I use 64 Bit in Dom0 and DomU, 32 Bit only in DomU incl. DomU with DVB etc. XEN options are the same, it''s only the selection of drivers... Andrew, any idea? Boris, do you know a safe way to create a 64 Bit config out of a 32 Bit one? Sorry, I am not so used to kernel building... BR, Carsten.

Hi all, I''ve a linux dom0, a dom1 winxp sp2 (WinXP) and another winxp sp2 with 2 vcpu (WinXP_02) Dom2 uses all the dom0 idle: I mean this vm uses too much resources, it seems something wrong in configuration. This is strange because the other win xp uses very few resources I''ll attach some useful output.. Suggestions? (domain (domid 4) (on_crash restart) (uuid

Hi, I don''t understand something about the vcpu-set function. My configuration: *memory = 2048 cpu = ''1-2'' maxvcpu = 4 vcpus = 1* When the DomU is running, and when i try to set 2 or 3 vpcu i get the error : xm vcpu-set domain_name 2 *Error: Cannot set vcpus greater than max vcpus on running domain Usage: xm vcpu-set <Domain> <vCPUs> Set the number of

Hi, I have set maxvcpus and vcpus options in my domU configuration file, and I can see that X number of vcpu are set for the domU. I tried to activate all the vpcus by using vpcu_avail option (using decimal to represent vpcu bitmask e.g. 24=11000) but it doesn''t seem to work, and only the first vpcu is activated (i.e. has -b- state) while all other vpcu''s set for the domU are

Hi, I have set maxvcpus and vcpus options in my domU configuration file, and I can see that X number of vcpu are set for the domU. I tried to activate all the vpcus by using vpcu_avail option (using decimal to represent vpcu bitmask e.g. 24=11000) but it doesn''t seem to work, and only the first vpcu is activated (i.e. has -b- state) while all other vpcu''s set for the domU are

Hi, I''m running Xen 3.0.4 with suse (kernel 2.6.16.46-0.12-xen). I''ve a problem with a "ghost" (paravirt) domain that appear in the output of xm list. As an example: # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1024 4 r----- 29.0 vm-xyz

Yesterday, I had a PV OpenSolaris DomU stop responding. I looked on my xen machine and it was in a paused state. I ended up destroying it and then doing xm create to bring it back up. It won''t boot, and I think PyGrub is hanging. Not sure how to resolve this, there aren''t any errors being presented in xen/xm itself. If I try ''xm create config.conf'' it just

Hello! after update of GPLPV drivers from 0.9.12-pre13 to 0.10.0.86 on windows 2008 server domU I cant use xm shutdown <domU> in dom0 (nothing happens exactly for this domU, other domU with old drivers shutdowns normally), how to fix? opensuse11.1x64 xen 3.3.1 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

System config:- bash-3.2# ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 rge0: flags=201004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS> mtu 1500 index 2 inet 192.168.1.53 netmask ffffff00 broadcast 192.168.1.255 ether 0:1e:8c:25:cc:a5 lo0:

Hi, It seems to be a very basic question, but need confirmation. I am using Centos as my Dom0, running xen, using paravirtualization. Can I run NON-CentOS (more specifically Debian) operating system on domU, -- Regards, Meghanand N. Acharekar " A proud Linux User " Reg Linux User #397975 ------------------------------------------ I was born free! No Gates and Windows can restrict

Hi, i read the xenpm wiki page, but i cannot use the "p-states". xenpm shows: xenpm cpu id : 0 total C-states : 2 idle time(ms) : 1776034 C0 : transition [00000000000000000000] residency [00000000000000000000 ms] C1 : transition [00000000000000260278] residency

Hello all ;) Tell I have a Xeon server with 4 vcpus If on this box I have some guets, tell 10, what is the best solutions : - Set all guests to 1 vcpu ? - Set all guests to 4 vcpus ? I well understand that if I set a guest with 4 vcpus and all others only with one vpcus, then the one with 4 vcpus will have more "cpu time" available than others guests. But in case I''d like

I found a "feature" or a bug in metaflac (and possibly libflac) metadata handling. If you try to add some tags to file, and padding field is not big enough, padding size doesn't get increased automaticly, so you receive an error about corrupted file (tried both with foobar2k and metaflac). But if you previously add more padding with "--add-padding=", everything goes

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 first of all, thank you for a great project i really enjoy! ok, now here comes the bug report... i''m trying to test xen migration capabilities, with xen-3.1, hand compilled, fetched from mercurial repository. my setup looks like this - x86_64 dom0, x86_32p dom0, x86_32p domU. when trying to migrate from 64 to 32 bit dom0 i''m